Error

SeverityCategory

ACLMIB-3-INIT_ERROR

3 ACL

ACLMIB-7-INIT_DEBUG

7 ACL

APPS_ES_ACLMGR-7-ERROR

7 ACL

COMMON_ACL-3-EPERM

3 ACL

COMMON_ACL-7-INIT

7 ACL

ES_ACL-6-ESACCESSLOGV

6 ACL

IP_ACL_PARSE-7-ERR_MEM_ALLOC

7 ACL

IP_ACL_PARSE-7ERR_THREAD_MUTEX_LOCK

7 ACL

IPV4_ACL-4-IPACCESSRLIMIT

4 ACL

IPV4_ACL-4-IPACCESSUNSUPPORTED

4 ACL

IPV4_ACL-6-IPACCESSLOGDP

6 ACL

IPV4_ACL-6-IPACCESSLOGDP

6 ACL

IPV4_ACL-6-IPACCESSLOGNP

6 ACL

IPV4_ACL-6-IPACCESSLOGNP

6 ACL

IPV4_ACL-6-IPACCESSLOGP

6 ACL

IPV4_ACL-6-IPACCESSLOGP

6 ACL

IPV4_ACL-6-IPACCESSLOGRP

6 ACL

IPV4_ACL-6-IPACCESSLOGRP

6 ACL

IPV4_ACL-6-IPACCESSLOGS

6 ACL

IPV4_ACL-6-IPACCESSLOGS

6 ACL

IPV4_ACL-7-INIT

7 ACL

IPV4_ACL-7-IPACCESSPTHREAD

7 ACL

IPV4_ACL-7-IPACCESSPTHREAD

7 ACL

IPV6_ACL_DAEMON-7-INIT

7 ACL

IPV6_ACL-1-IPACCESSDLLOPEN

1 ACL

IPV6_ACL-1-IPACCESSDLLOPEN

1 ACL

IPV6_ACL-1-IPACCESSDLSYM

1 ACL

IPV6_ACL-1-IPACCESSDLSYM

1 ACL

IPV6_ACL-1-IPACCESSNOMEM

1 ACL

IPV6_ACL-1-IPACCESSNOMEM

1 ACL

IPV6_ACL-3-IPACCESSPTHREAD

3 ACL

IPV6_ACL-3-IPACCESSPTHREAD

3 ACL

IPV6_ACL-3-LTRACEINIT

3 ACL

IPV6_ACL-4-IPACCESSRLIMIT

4 ACL

IPV6_ACL-4-IPACCESSUNSUPPORTED

4 ACL

IPV6_ACL-6-IPACCESSLOGDP

6 ACL

IPV6_ACL-6-IPACCESSLOGDP

6 ACL

IPV6_ACL-6-IPACCESSLOGNP

6 ACL

IPV6_ACL-6-IPACCESSLOGNP

6 ACL

IPV6_ACL-6-IPACCESSLOGP

6 ACL

IPV6_ACL-6-IPACCESSLOGP

6 ACL

IPV6_ACL-6-IPACCESSLOGRP

6 ACL

IPV6_ACL-6-IPACCESSLOGRP

6 ACL

IPV6_ACL-6-IPACCESSLOGS

6 ACL

IPV6_ACL-6-IPACCESSLOGS

6 ACL

LI-3-NETIO_INIT

3 ACL

PFILTER_NETIO_LTRACE-7-INIT

7 ACL

OBJ_MGR-3-CLEANUP

3 APP_INFRA

OBJ_MGR-3-INIT

3 APP_INFRA

PLMGR_UI-3-CLI

3 APP_INFRA

PLMGR_UI-3-NOMEM

3 APP_INFRA

PLMGR_UI-4-DEBUG

4 APP_INFRA

PLMGR_UI-4-INVAL_DATA

4 APP_INFRA

PLMGR_UI-4-LTRACE

4 APP_INFRA

POLICYMGR-3-APP_NAME_FAILURE

3 APP_INFRA

POLICYMGR-3-GO_ACTIVE

3 APP_INFRA

POLICYMGR-7-INIT

7 APP_INFRA

DIAG-3-CARD_ABSENT

3 DIAG

DIAG-3-ENQUEUE_FAIL

3 DIAG

DIAG-3-GOLDXR_FAIL

3 DIAG

DIAG-3-MAJOR

3 DIAG

DIAG-3-MINOR

3 DIAG

DIAG-3-SW_FAIL

3 DIAG

DIAG-3-TEST_FAIL

3 DIAG

DIAG-3-TIMER_FAIL

3 DIAG

DIAG-4-ALWAYS_ENABLE_TEST

4 DIAG

DIAG-4-DIAG_RUNNING

4 DIAG

DIAG-4-FIXED_INTERVAL_TEST

4 DIAG

DIAG-4-INVALID_DEVICE

4 DIAG

DIAG-4-INVALID_MONITORING_INTERVAL

4 DIAG

DIAG-4-INVALID_PORT

4 DIAG

DIAG-4-INVALID_TEST

4 DIAG

DIAG-4-MONITOR_DISABLE

4 DIAG

DIAG-4-MONITOR_INTERVAL_ZERO

4 DIAG

DIAG-4-NOT_MONITORING_TEST

4 DIAG

DIAG-4-TEST_NOT_SUPPORT

4 DIAG

DIAG-6-BYPASS

6 DIAG

DIAG-6-DIAG_OK

6 DIAG

DIAG-6-DIAG_STOPPED

6 DIAG

DIAG-6-GOLDXR_GENERAL

6 DIAG

DIAG-6-NO_DIAG_RUNNING

6 DIAG

DIAG-6-NO_TEST

6 DIAG

DIAG-6-RUN_COMPLETE

6 DIAG

DIAG-6-RUN_MINIMUM

6 DIAG

DIAG-6-SCHED_COMPLETE

6 DIAG

DIAG-6-SCHED_RUNNING

6 DIAG

DIAG-6-SCHED_STOPPED

6 DIAG

DIAG-6-SCHEDULE_IS_REMOVED

6 DIAG

DIAG-6-TEST_NOT_ONDEMAND

6 DIAG

DIAG-6-TEST_OK

6 DIAG

DIAG-6-TEST_RUNNING

6 DIAG

DIAG-6-TEST_SKIPPED

6 DIAG

DIAG-6-TEST_SKIPPED_FROM_ACTIVE

6 DIAG

DIAG-6-TEST_SKIPPED_FROM_STANDBY

6 DIAG

PFDIAGBASE-3-CHKSUM_ERROR

3 DIAG

PFDIAGBASE-3-CONN_FAIL

3 DIAG

PFDIAGBASE-3-CTX_ERROR

3 DIAG

PFDIAGBASE-3-INIT_ERROR

3 DIAG

PFDIAGBASE-3-INIT_FAIL

3 DIAG

PFDIAGBASE-3-MSG_ERROR

3 DIAG

PFDIAGBASE-3-PAYLOAD_ERROR

3 DIAG

PFDIAGBASE-3-PKT_ERROR

3 DIAG

PFDIAGBASE-3-QUEUE_ERROR

3 DIAG

PFDIAGBASE-3-STATE_ERROR

3 DIAG

PFDIAGBASE-3-SW_ERROR

3 DIAG

PFDIAGBASE-3-SW_ERROR

3 DIAG

PFDIAGBASE-4-WARNING

4 DIAG

PFDIAGBASE-4-WARNING

4 DIAG

XR_DIAG-2-ERR_PLANE_FAILURE_NOTIFY

2 DIAG

XR_DIAG-3-CE_SWITCH_FAILURE

3 DIAG

XR_DIAG-3-FAB_ERR

3 DIAG

XR_DIAG-3-FAB_SRCC_FAILURE

3 DIAG

XR_DIAG-3-FABRIC_PING_FAILURE

3 DIAG

XR_DIAG-3-FILESYS_BASIC_FAILURE

3 DIAG

XR_DIAG-3-IFD_ETHSVR_MSG_ERR

3 DIAG

XR_DIAG-3-SCRATCH_REG_FAILURE

3 DIAG

XR_DIAG-6-INFO

6 DIAG

XR_DIAG-6-PKT_SEND_FAILURE

6 DIAG

CCSQ_DLL-2-DEVICE_HALT

2 FABRIC

CCSQ_DLL-2-ERR_EIO_TRAIN

2 FABRIC

CCSQ_DLL-2-TAKING_NODE_DOWN

2 FABRIC

CCSQ_DLL-3-ERR_ASIC_GENERIC

3 FABRIC

CCSQ_DLL-3-ERR_ASIC_MBE

3 FABRIC

CCSQ_DLL-3-ERR_INIT

3 FABRIC

CCSQ_DLL-3-ERR_MEM_ALLOC

3 FABRIC

CCSQ_DLL-3-RESET

3 FABRIC

CCSQ_DLL-4-ERR_ASIC_CRC

4 FABRIC

CCSQ_DLL-4-ERR_ASIC_SN_LINK

4 FABRIC

CCSQ_DLL-4-INTR_ENABLE_FAIL

4 FABRIC

CCSQ_DLL-5-ERR_ASIC_PARITY

5 FABRIC

CCSQ_DLL-5-ERR_ASIC_SBE

5 FABRIC

CCSQ_DLL-7-ERR_REGISTER_GET

7 FABRIC

CCSQ_LIB-7-ERR_LWM_SEND

7 FABRIC

CCSQ_MGR-3-ERR_INIT

3 FABRIC

CCSQ_MGR-3-ERR_MEM_ALLOC

3 FABRIC

CCSQ_MGR-7-ERR_BAG_REG

7 FABRIC

CCSQ_MGR-7-ERR_CLIENT_REG

7 FABRIC

CCSQ_MGR-7-ERR_DLL_INIT

7 FABRIC

CCSQ_MGR-7-ERR_EVM_CREATE

7 FABRIC

CCSQ_MGR-7-ERR_EVM_NOTIFY

7 FABRIC

CCSQ_MGR-7-ERR_LWM_EVENT_BLOCK

7 FABRIC

CCSQ_MGR-7-ERR_LWM_REPLY

7 FABRIC

CCSQ_MGR-7-ERR_SYSDB_EDM_REG

7 FABRIC

CMN_DSTRIB_GSP_FBRC-3ERR_DEBUG_INIT

3 FABRIC

FAB_LC-3-NH_SHM_INIT

3 FABRIC

FAB_LC-3-NH_SHM_MALLOC

3 FABRIC

FAB_LC-3-SHM_POOL_CREATE

3 FABRIC

FAB_PROXY-3-ERR_CONN_INIT

3 FABRIC

FAB_PROXY-3-ERR_EVM_CREATE

3 FABRIC

FAB_PROXY-3-ERR_SYSDB_THREAD

3 FABRIC

FAB_PROXY-3-ERR_THREAD_CREATE

3 FABRIC

FAB_PROXY-3-EXIT_PROCESS

3 FABRIC

FAB_PROXY-4-ERR_LTRACE_INIT

4 FABRIC

FAB_SVR_HFR-7-ERR_ASIC_INIT

7 FABRIC

FAB_SVR_HFR-7ERR_EVENT_CONN_EVM_HANDLER

7 FABRIC

FAB_SVR_HFR-7-ERR_EVENT_CONN_NOTIFY

7 FABRIC

FAB_SVR_HFR-7-ERR_EVENT_CONN_OPEN

7 FABRIC

FAB_SVR_HFR-7-ERR_EVM_CREATE

7 FABRIC

FAB_SVR_HFR-7-ERR_FSM_STATE

7 FABRIC

FAB_SVR_HFR-7-ERR_HEARTBEAT_FAILURE

7 FABRIC

FAB_SVR_HFR-7ERR_HEARTBEAT_FSM_STATE

7 FABRIC

FAB_SVR_HFR-7-ERR_INIT

7 FABRIC

FAB_SVR_HFR-7-ERR_RRW_LOCK

7 FABRIC

FAB_SVR_HFR-7-ERR_RRW_UNLOCK

7 FABRIC

FAB_SVR_HFR-7-ERR_THREAD_ATTRIBUTE

7 FABRIC

FAB_SVR_HFR-7-ERR_THREAD_MUTEX_INIT

7 FABRIC

FAB_SVR_HFR-7-INFO_SHM

7 FABRIC

FAB_SVR_TOPAZ-7-ERR_ASIC_INIT

7 FABRIC

FAB_SVR_TOPAZ-7ERR_EVENT_CONN_EVM_HANDLER

7 FABRIC

FAB_SVR_TOPAZ-7ERR_EVENT_CONN_NOTIFY

7 FABRIC

FAB_SVR_TOPAZ-7ERR_EVENT_CONN_OPEN

7 FABRIC

FAB_SVR_TOPAZ-7-ERR_EVM_CREATE

7 FABRIC

FAB_SVR_TOPAZ-7-ERR_FSM_STATE

7 FABRIC

FAB_SVR_TOPAZ-7ERR_HEARTBEAT_FAILURE

7 FABRIC

FAB_SVR_TOPAZ-7ERR_HEARTBEAT_FSM_STATE

7 FABRIC

FAB_SVR_TOPAZ-7-ERR_INIT

7 FABRIC

FAB_SVR_TOPAZ-7-ERR_RRW_LOCK

7 FABRIC

FAB_SVR_TOPAZ-7-ERR_RRW_UNLOCK

7 FABRIC

FAB_SVR_TOPAZ-7ERR_THREAD_ATTRIBUTE

7 FABRIC

FAB_SVR_TOPAZ-7ERR_THREAD_MUTEX_INIT

7 FABRIC

FAB_SVR_TOPAZ-7-INFO_SHM

7 FABRIC

FAB_SVR-4-LTRACE_INIT_FAIL

4 FABRIC

FAB_SVR-7-ERR_ASIC_INIT

7 FABRIC

FAB_SVR-7ERR_EVENT_CONN_EVM_HANDLER

7 FABRIC

FAB_SVR-7-ERR_EVENT_CONN_NOTIFY

7 FABRIC

FAB_SVR-7-ERR_EVENT_CONN_OPEN

7 FABRIC

FAB_SVR-7-ERR_EVM_CREATE

7 FABRIC

FAB_SVR-7-ERR_FSM_STATE

7 FABRIC

FAB_SVR-7-ERR_HEARTBEAT_FAILURE

7 FABRIC

FAB_SVR-7-ERR_HEARTBEAT_FSM_STATE

7 FABRIC

FAB_SVR-7-ERR_INIT

7 FABRIC

FAB_SVR-7-ERR_RRW_LOCK

7 FABRIC

FAB_SVR-7-ERR_RRW_UNLOCK

7 FABRIC

FAB_SVR-7-ERR_THREAD_ATTRIBUTE

7 FABRIC

FAB_SVR-7-ERR_THREAD_MUTEX_INIT

7 FABRIC

FAB_SVR-7-INFO_SHM

7 FABRIC

FABQ-0-PRP3_FAULT_RECOVERY_ERR

--

FABRIC

FABQ-2-PRP3_DRVR_INIT_ERROR

2 FABRIC

FABQ-2-PRP3_PKT_INIT_ERROR

2 FABRIC

FABQ-3-FATAL

3 FABRIC

FABQ-3-INIT_ERROR

3 FABRIC

FABQ-3-PKT_INIT_ERROR

3 FABRIC

FABQ-3-PKT_INIT_FAIL

3 FABRIC

FABQ-3-PKT_INIT_POOL

3 FABRIC

FABQ-3-PRP3_FABMSG

3 FABRIC

FABQ-3-PRP3_FRFAB_PKT_NO_STREAM

3 FABRIC

FABQ-3-PRP3_FRFAB_PKT_STARTOFFSET

3 FABRIC

FABQ-3-PRP3_FRFAB_TAIL_PAR_ERR

3 FABRIC

FABQ-3-PRP3_HW_IRQ_ERR

3 FABRIC

FABQ-3-PRP3_IRQ_ERR

3 FABRIC

FABQ-3-PRP3_PORT_DISABLE_ERR

3 FABRIC

FABQ-3-PRP3_PORT_ENABLE_ERR

3 FABRIC

FABQ-3-PRP3_REUSE_NO_BUFFER

3 FABRIC

FABQ-3-PRP3_SHM

3 FABRIC

FABQ-3PRP3_TOFAB_CREDIT_CNT_EXCEEDED

3 FABRIC

FABQ-3-PRP3_TOFAB_QUEUE_BLOCKED

3 FABRIC

FABQ-3-PRP3_TX_DONE_RING

3 FABRIC

FABQ-3-SHOW_ERR

3 FABRIC

FABQ-6-PKT_INIT_INFO

6 FABRIC

FABQ-7-PKT_INIT_INFO

7 FABRIC

FABQ-7-PRP3_PKT_INIT_INFO

7 FABRIC

FABRIC_140G_POD-2-TX_CH_FAULT

2 FABRIC

FABRIC_140G_POD-3-ASIC_ERR_INIT

3 FABRIC

FABRIC_140G_POD-3-ERR_GASPP_INIT

3 FABRIC

FABRIC_140G_POD-3-ERR_INTERNAL_SW

3 FABRIC

FABRIC_140G_POD-3-HIGH_2_5VCC

3 FABRIC

FABRIC_140G_POD-3-HIGH_3_3VCC

3 FABRIC

FABRIC_140G_POD-3-HIGH_TEMP

3 FABRIC

FABRIC_140G_POD-3-LOW_2_5VCC

3 FABRIC

FABRIC_140G_POD-3-LOW_3_3VCC

3 FABRIC

FABRIC_140G_POD-3-LOW_TEMP

3 FABRIC

FABRIC_140G_POD-3-RX_CH_HI_PWR

3 FABRIC

FABRIC_140G_POD-3-RX_CH_LO_PWR

3 FABRIC

FABRIC_140G_POD-3-RX_CH_LOS_ERR

3 FABRIC

FABRIC_140G_POD-3-SPUR_INTR

3 FABRIC

FABRIC_140G_POD-3TX_CH_HI_BIAS_CURRENT

3 FABRIC

FABRIC_140G_POD-3-TX_CH_HI_PWR

3 FABRIC

FABRIC_140G_POD-3TX_CH_LO_BIAS_CURRENT

3 FABRIC

FABRIC_140G_POD-3-TX_CH_LO_PWR

3 FABRIC

FABRIC_140G_POD-3-TX_CH_LOS_ERR

3 FABRIC

FABRIC_140G_POD-3-UNSUPP_RX_CH

3 FABRIC

FABRIC_140G_POD-3-UNSUPP_RX_NON_CH

3 FABRIC

FABRIC_140G_POD-3-UNSUPP_TX_CH

3 FABRIC

FABRIC_140G_POD-3-UNSUPP_TX_NON_CH

3 FABRIC

FABRIC_140G_POD-6-RX_ALL_CH_LOP_ERR

6 FABRIC

FABRIC_140G_POD-6-RX_ALL_CH_LOS_ERR

6 FABRIC

FABRIC_400G_POD-2-TX_CH_FAULT

2 FABRIC

FABRIC_400G_POD-3-ASIC_ERR_INIT

3 FABRIC

FABRIC_400G_POD-3-ERR_GASPP_INIT

3 FABRIC

FABRIC_400G_POD-3-ERR_INTERNAL_SW

3 FABRIC

FABRIC_400G_POD-3-HIGH_2_5VCC

3 FABRIC

FABRIC_400G_POD-3-HIGH_3_3VCC

3 FABRIC

FABRIC_400G_POD-3-HIGH_TEMP

3 FABRIC

FABRIC_400G_POD-3-LOW_2_5VCC

3 FABRIC

FABRIC_400G_POD-3-LOW_3_3VCC

3 FABRIC

FABRIC_400G_POD-3-LOW_TEMP

3 FABRIC

FABRIC_400G_POD-3-RX_CH_HI_PWR

3 FABRIC

FABRIC_400G_POD-3-RX_CH_LO_PWR

3 FABRIC

FABRIC_400G_POD-3-RX_CH_LOS_ERR

3 FABRIC

FABRIC_400G_POD-3-SPUR_INTR

3 FABRIC

FABRIC_400G_POD-3TX_CH_HI_BIAS_CURRENT

3 FABRIC

FABRIC_400G_POD-3-TX_CH_HI_PWR

3 FABRIC

FABRIC_400G_POD-3TX_CH_LO_BIAS_CURRENT

3 FABRIC

FABRIC_400G_POD-3-TX_CH_LO_PWR

3 FABRIC

FABRIC_400G_POD-3-TX_CH_LOS_ERR

3 FABRIC

FABRIC_400G_POD-3-UNSUPP_RX_CH

3 FABRIC

FABRIC_400G_POD-3-UNSUPP_RX_NON_CH

3 FABRIC

FABRIC_400G_POD-3-UNSUPP_TX_CH

3 FABRIC

FABRIC_400G_POD-3-UNSUPP_TX_NON_CH

3 FABRIC

FABRIC_COMM_DRVR-3-ERR_DRV_INIT

3 FABRIC

FABRIC_COMM_DRVR-3-ERR_EVM_CREATE

3 FABRIC

FABRIC_COMM_DRVR-3-ERR_INTERNAL_SW

3 FABRIC

FABRIC_COMM_DRVR-3-ERR_MEM_ALLOC

3 FABRIC

FABRIC_COMM_DRVR-7-ERR_LTRACE_INIT

7 FABRIC

FABRIC_COMM_DRVR-7-ERR_SHM_INIT

7 FABRIC

FABRIC_DRIVER_LITE-3ERR_ASIC_ACCESS_EXCEPTION

3 FABRIC

FABRIC_DRIVER_LITE-3-ERR_DRIVER_INIT

3 FABRIC

FABRIC_DRIVER_LITE-3-ERR_EVM_CREATE

3 FABRIC

FABRIC_DRIVER_LITE-3-ERR_SHMEM_INIT

3 FABRIC

FABRIC_DRIVER_LITE-3ERR_THREAD_ATTRIBUTE

3 FABRIC

FABRIC_DRIVER_LITE-4-ERR_LTRACE_INIT

4 FABRIC

FABRIC_DRIVER_LITE-6-ASIC_INITIALIZED

6 FABRIC

FABRIC_DRVR_SHARED-2-ERR_SHMEM_INIT

2 FABRIC

FABRIC_DRVR-1-ERR_BOARD_FAULT

1 FABRIC

FABRIC_DRVR-1-ERR_BOARD_FAULT

1 FABRIC

FABRIC_DRVR-1-ERR_BOARD_POWER_FAULT

1 FABRIC

FABRIC_DRVR-1-ERR_BOARD_POWER_FAULT

1 FABRIC

FABRIC_DRVR-1-ERR_CCTL_POWER_FAULT

1 FABRIC

FABRIC_DRVR-1-ERR_CCTL_POWER_FAULT

1 FABRIC

FABRIC_DRVR-1-ERR_HALT_VIA_CPLD

1 FABRIC

FABRIC_DRVR-1-ERR_HALT_VIA_FPGA

1 FABRIC

FABRIC_DRVR-1-ERR_HW_HEALTH_MON

1 FABRIC

FABRIC_DRVR-1-ERR_HW_HEALTH_MON

1 FABRIC

FABRIC_DRVR-1-ERR_HW_HEALTH_MON

1 FABRIC

FABRIC_DRVR-1-ERR_HW_INIT

1 FABRIC

FABRIC_DRVR-1-ERR_HW_INIT

1 FABRIC

FABRIC_DRVR-1-ERR_LOCALBUS_FAULT

1 FABRIC

FABRIC_DRVR-1-ERR_LOCALBUS_FAULT

1 FABRIC

FABRIC_DRVR-1ERR_THRESHOLD_ASIC_RESETS_REACHED

1 FABRIC

FABRIC_DRVR-1ERR_THRESHOLD_ASIC_RESETS_REACHED

1 FABRIC

FABRIC_DRVR-1RX_MACRO_SPEED_MISMATCH

1 FABRIC

FABRIC_DRVR-1TX_MACRO_SPEED_MISMATCH

1 FABRIC

FABRIC_DRVR-2-ERR_MAINTENANCE_MODE

2 FABRIC

FABRIC_DRVR-2-ERR_SHUTDOWN

2 FABRIC

FABRIC_DRVR-2-ERR_SYSDB_BIND

2 FABRIC

FABRIC_DRVR-2-ERR_SYSDB_BIND

2 FABRIC

FABRIC_DRVR-2-ERR_SYSDB_REGS

2 FABRIC

FABRIC_DRVR-2-ERR_SYSDB_REGS

2 FABRIC

FABRIC_DRVR-3-BM_DEAD_NODE_FAILURE

3 FABRIC

FABRIC_DRVR-3-BM_DEAD_NODE_FAILURE

3 FABRIC

FABRIC_DRVR-3BM_DEAD_NODE_RECOVERY_FAILURE

3 FABRIC

FABRIC_DRVR-3BM_DEAD_NODE_RECOVERY_FAILURE

3 FABRIC

FABRIC_DRVR-3-CCI_INTR_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-CCI_INTR_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-CCI_LIB_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-CCI_LIB_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-CDR_DISPATCH_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-CDR_HW_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-CDR_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-CDR_MSG_REPLY_FAIL

3 FABRIC

FABRIC_DRVR-3-CDR_REG_NOTIF_FAIL

3 FABRIC

FABRIC_DRVR-3-CDR_SHM_ERR

3 FABRIC

FABRIC_DRVR-3-CIH_LIB_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-CIH_LIB_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-DBG_TCAM_LIB_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-DBG_TCAM_LIB_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-ERR_ASIC_FAULT

3 FABRIC

FABRIC_DRVR-3-ERR_ASIC_FAULT

3 FABRIC

FABRIC_DRVR-3ERR_ASIC_FGID_SRAM_BIST_DONE

3 FABRIC

FABRIC_DRVR-3ERR_ASIC_FGID_SRAM_BIST_PASS

3 FABRIC

FABRIC_DRVR-3-ERR_ASIC_HARD_RESET

3 FABRIC

FABRIC_DRVR-3-ERR_ASIC_HARD_RESET

3 FABRIC

FABRIC_DRVR-3-ERR_ASIC_PON_RESET

3 FABRIC

FABRIC_DRVR-3-ERR_ASIC_PON_RESET

3 FABRIC

FABRIC_DRVR-3ERR_ASIC_SCAN_UNSUPPORTED

3 FABRIC

FABRIC_DRVR-3ERR_ASIC_SCAN_UNSUPPORTED

3 FABRIC

FABRIC_DRVR-3-ERR_ASIC_SYSLOG

3 FABRIC

FABRIC_DRVR-3-ERR_ASIC_SYSLOG

3 FABRIC

FABRIC_DRVR-3-ERR_BOARD_ALERT

3 FABRIC

FABRIC_DRVR-3-ERR_BOARD_ALERT

3 FABRIC

FABRIC_DRVR-3-ERR_BOARD_PLD_VERSION

3 FABRIC

FABRIC_DRVR-3-ERR_DISPATCH_PULSE

3 FABRIC

FABRIC_DRVR-3-ERR_DRV_INIT

3 FABRIC

FABRIC_DRVR-3-ERR_DRV_INIT

3 FABRIC

FABRIC_DRVR-3-ERR_DRV_INIT

3 FABRIC

FABRIC_DRVR-3-ERR_EVM_CREATE

3 FABRIC

FABRIC_DRVR-3-ERR_EVM_CREATE

3 FABRIC

FABRIC_DRVR-3-ERR_EVM_CREATE

3 FABRIC

FABRIC_DRVR-3-ERR_FGID_ACCESS

3 FABRIC

FABRIC_DRVR-3-ERR_FGID_REFRESH

3 FABRIC

FABRIC_DRVR-3-ERR_FGID_REFRESH_RETRY

3 FABRIC

FABRIC_DRVR-3-ERR_FGID_WRITE

3 FABRIC

FABRIC_DRVR-3-ERR_INVALID_INSTANCE

3 FABRIC

FABRIC_DRVR-3-ERR_INVALID_INSTANCE

3 FABRIC

FABRIC_DRVR-3-ERR_INVALID_MACRO

3 FABRIC

FABRIC_DRVR-3-ERR_LIB_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-ERR_LIB_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-ERR_MAX_TOPO_TIME_OUT

3 FABRIC

FABRIC_DRVR-3-ERR_MAX_TOPO_TIME_OUT

3 FABRIC

FABRIC_DRVR-3-ERR_MAX_TOPO_TIME_OUT

3 FABRIC

FABRIC_DRVR-3-ERR_MEM_ALLOC

3 FABRIC

FABRIC_DRVR-3-ERR_MEM_ALLOC

3 FABRIC

FABRIC_DRVR-3-ERR_MEM_ALLOC

3 FABRIC

FABRIC_DRVR-3-ERR_POD_INIT

3 FABRIC

FABRIC_DRVR-3-ERR_POD_INIT

3 FABRIC

FABRIC_DRVR-3-ERR_POD_INIT

3 FABRIC

FABRIC_DRVR-3-ERR_RE_INIT_ASIC

3 FABRIC

FABRIC_DRVR-3-ERR_RE_INIT_ASIC

3 FABRIC

FABRIC_DRVR-3-ERR_RELOAD

3 FABRIC

FABRIC_DRVR-3-ERR_RMA_CARD

3 FABRIC

FABRIC_DRVR-3-ERR_RMA_CARD

3 FABRIC

FABRIC_DRVR-3-ERR_SELF_RELOAD

3 FABRIC

FABRIC_DRVR-3-ERR_SELF_RELOAD

3 FABRIC

FABRIC_DRVR-3-ERR_SELF_RELOAD

3 FABRIC

FABRIC_DRVR-3-ERR_SPURIOUS_INTERRUPT

3 FABRIC

FABRIC_DRVR-3-ERR_SPURIOUS_INTERRUPT

3 FABRIC

FABRIC_DRVR-3-ERR_SPURIOUS_INTERRUPT

3 FABRIC

FABRIC_DRVR-3ERR_STUCK_BARRIER_FLOW

3 FABRIC

FABRIC_DRVR-3-ERR_THREAD_ATTRIBUTE

3 FABRIC

FABRIC_DRVR-3-ERR_THREAD_ATTRIBUTE

3 FABRIC

FABRIC_DRVR-3-ERR_THREAD_ATTRIBUTE

3 FABRIC

FABRIC_DRVR-3-ERR_TIMER_START

3 FABRIC

FABRIC_DRVR-3ERR_WAITING_FOR_TOPO_TIMED_OUT

3 FABRIC

FABRIC_DRVR-3ERR_WAITING_FOR_TOPO_TIMED_OUT

3 FABRIC

FABRIC_DRVR-3ERR_WAITING_FOR_TOPO_TIMED_OUT

3 FABRIC

FABRIC_DRVR-3-ERRRATE_EXCEED_GLACIAL

3 FABRIC

FABRIC_DRVR-3-ERRRATE_EXCEED_GLACIAL

3 FABRIC

FABRIC_DRVR-3-ERRRATE_EXCEED_GLACIAL

3 FABRIC

FABRIC_DRVR-3ERRRATE_EXCEED_NO_LIMIT

3 FABRIC

FABRIC_DRVR-3ERRRATE_EXCEED_NO_LIMIT

3 FABRIC

FABRIC_DRVR-3-ERRRATE_EXCEED_SLOW

3 FABRIC

FABRIC_DRVR-3-ERRRATE_EXCEED_SLOW

3 FABRIC

FABRIC_DRVR-3-FIT_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-FIT_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-GASP_INIT_ACC_ERR

3 FABRIC

FABRIC_DRVR-3-LINK_SHUT_DOWN_PERM

3 FABRIC

FABRIC_DRVR-3-LINK_SHUT_DOWN_PERM

3 FABRIC

FABRIC_DRVR-3-LM_DRAIN_QUEUE_FAILURE

3 FABRIC

FABRIC_DRVR-3-LM_DRAIN_QUEUE_FAILURE

3 FABRIC

FABRIC_DRVR-3-RCC_HW_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-RCC_HW_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-RCC_LIB_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-RCC_LIB_INIT_FAIL

3 FABRIC

FABRIC_DRVR-3-TRACE_INIT_ERR

3 FABRIC

FABRIC_DRVR-4CCTL_LTC2978_ALERT_DAMPENING

4 FABRIC

FABRIC_DRVR-4CCTL_LTC2978_ALERT_DAMPENING

4 FABRIC

FABRIC_DRVR-4-ERR_LTRACE_INIT

4 FABRIC

FABRIC_DRVR-4-ERR_LTRACE_INIT

4 FABRIC

FABRIC_DRVR-4-ERR_LTRACE_INIT

4 FABRIC

FABRIC_DRVR-4-GASP_INIT_FAIL

4 FABRIC

FABRIC_DRVR-4-RCC_INIT_INCOMPLETE

4 FABRIC

FABRIC_DRVR-4-RCC_INIT_INCOMPLETE

4 FABRIC

FABRIC_DRVR-4-WARN_HW_HEALTH_MON

4 FABRIC

FABRIC_DRVR-4-WARN_HW_HEALTH_MON

4 FABRIC

FABRIC_DRVR-5-POST_FPD_OP

5 FABRIC

FABRIC_DRVR-5-POST_FPD_OP

5 FABRIC

FABRIC_DRVR-5-PRE_FPD_OP

5 FABRIC

FABRIC_DRVR-5-PRE_FPD_OP

5 FABRIC

FABRIC_DRVR-6-ABORT_FGID_WRITE

6 FABRIC

FABRIC_DRVR-6-ABORT_FGID_WRITE

6 FABRIC

FABRIC_DRVR-6-ASIC_FREEZE_PRE_SCAN

6 FABRIC

FABRIC_DRVR-6-ASIC_FREEZE_PRE_SCAN

6 FABRIC

FABRIC_DRVR-6-ASIC_HALTED_VIA_CPLD

6 FABRIC

FABRIC_DRVR-6-ASIC_HALTED_VIA_FPGA

6 FABRIC

FABRIC_DRVR-6-ASIC_INITIALIZED

6 FABRIC

FABRIC_DRVR-6-ASIC_INITIALIZED

6 FABRIC

FABRIC_DRVR-6-ASIC_INITIALIZED

6 FABRIC

FABRIC_DRVR-6ASIC_PON_RESET_POST_SCAN

6 FABRIC

FABRIC_DRVR-6ASIC_PON_RESET_POST_SCAN

6 FABRIC

FABRIC_DRVR-6-ASIC_READ_ACCESS

6 FABRIC

FABRIC_DRVR-6-ASIC_READ_ACCESS

6 FABRIC

FABRIC_DRVR-6-ASIC_RESET_REASONS

6 FABRIC

FABRIC_DRVR-6-ASIC_RESET_REASONS

6 FABRIC

FABRIC_DRVR-6-ASIC_RESET_REASONS

6 FABRIC

FABRIC_DRVR-6-ASIC_WRITE_ACCESS

6 FABRIC

FABRIC_DRVR-6-ASIC_WRITE_ACCESS

6 FABRIC

FABRIC_DRVR-6-AWAIT_FGID_DOWNLOAD

6 FABRIC

FABRIC_DRVR-6-AWAIT_FGID_DOWNLOAD

6 FABRIC

FABRIC_DRVR-6-BARRIER_FLOW_STARTED

6 FABRIC

FABRIC_DRVR-6BUS_STALL_ADDR_TRACEBACK

6 FABRIC

FABRIC_DRVR-6BUS_STALL_ADDR_TRACEBACK

6 FABRIC

FABRIC_DRVR-6-CARD_RELOAD_POST_SCAN

6 FABRIC

FABRIC_DRVR-6-CARD_RELOAD_POST_SCAN
FABRIC_DRVR-6-DLL_LOAD

6 FABRIC
6 FABRIC

FABRIC_DRVR-6ERR_ASIC_ACCESS_TIMED_OUT

6 FABRIC

FABRIC_DRVR-6ERR_ASIC_ACCESS_TIMED_OUT

6 FABRIC

FABRIC_DRVR-6-FIT_HARD_RESET

6 FABRIC

FABRIC_DRVR-6-FIT_HARD_RESET

6 FABRIC

FABRIC_DRVR-6-FIT_POWER_ON_RESET

6 FABRIC

FABRIC_DRVR-6-FIT_POWER_ON_RESET

6 FABRIC

FABRIC_DRVR-6-INFO_HW_HEALTH_MON

6 FABRIC

FABRIC_DRVR-6-MISSING_PLANE_CONFIG

6 FABRIC

FABRIC_DRVR-6-MISSING_PLANE_CONFIG

6 FABRIC

FABRIC_DRVR-6-MISSING_PLANE_CONFIG

6 FABRIC

FABRIC_DRVR-6-NODE_OIRED

6 FABRIC

FABRIC_DRVR-6-NODE_RELOAD_PENDING

6 FABRIC

FABRIC_DRVR-7-ERR_BP_CFG

7 FABRIC

FABRIC_DRVR-7-ERR_BP_CFG

7 FABRIC

FABRIC_DRVR-7-ERR_BP_CFG

7 FABRIC

FABRIC_DRVR-7-ERR_DEBUG_REG

7 FABRIC

FABRIC_DRVR-7-ERR_DEBUG_REG

7 FABRIC

FABRIC_DRVR-7-ERR_DEBUG_REG

7 FABRIC

FABRIC_DRVR-7-ERR_INTERNAL_SW

7 FABRIC

FABRIC_DRVR-7-ERR_INTERNAL_SW

7 FABRIC

FABRIC_DRVR-7-ERR_INTERNAL_SW

7 FABRIC

FABRIC_DRVR-7-ERR_LINK_TOPO

7 FABRIC

FABRIC_DRVR-7-ERR_LINK_TOPO

7 FABRIC

FABRIC_DRVR-7-ERRRATE_EXCEED_DEBUG

7 FABRIC

FABRIC_DRVR-7-ERRRATE_EXCEED_DEBUG

7 FABRIC

FABRIC_DRVR-7-ERRRATE_EXCEED_DEBUG

7 FABRIC

FABRIC_DRVR-7-LINK_SHUT_DOWN

7 FABRIC

FABRIC_DRVR-7-LINK_SHUT_DOWN

7 FABRIC

FABRIC_DRVR-7-LINK_SHUT_DOWN

7 FABRIC

FABRIC_SRVR-1-ERR_WRONG_CHASSIS

1 FABRIC

FABRIC_SRVR-2ERR_BOARD_NOT_POWERED

2 FABRIC

FABRIC_SRVR-2-ERR_SHUTDOWN

2 FABRIC

FABRIC_SRVR-3-ERR_ANNOUNCE

3 FABRIC

FABRIC_SRVR-3ERR_DLL_API_INVALID_PARAM

3 FABRIC

FABRIC_SRVR-3ERR_DLL_API_UNSUPPORTED

3 FABRIC

FABRIC_SRVR-3-ERR_DRV_INIT

3 FABRIC

FABRIC_SRVR-3-ERR_EES_REG

3 FABRIC

FABRIC_SRVR-3-ERR_ENABLE

3 FABRIC

FABRIC_SRVR-3-ERR_EVM_CREATE

3 FABRIC

FABRIC_SRVR-3-ERR_FGID_CONS_THREAD

3 FABRIC

FABRIC_SRVR-3ERR_FGID_DOWNLOAD_FAILED

3 FABRIC

FABRIC_SRVR-3-ERR_MEM_ALLOC

3 FABRIC

FABRIC_SRVR-3-SIGNAL

3 FABRIC

FABRIC_SRVR-4-ERR_ECM_CREATE

4 FABRIC

FABRIC_SRVR-4-ERR_ECM_NOTIFY

4 FABRIC

FABRIC_SRVR-4-ERR_FGID_DOWNLOAD

4 FABRIC

FABRIC_SRVR-4-ERR_LTRACE_INIT

4 FABRIC

FABRIC_SRVR-6-ASIC_RESET_REASONS

6 FABRIC

FABRIC_SRVR-6-FAB_MODULE

6 FABRIC

FABRIC_SRVR-6-FABRIC_DISCOVERY

6 FABRIC

FABRIC_SRVR-6INVALID_CARD_TYPE_ERROR

6 FABRIC

FABRIC_SRVR-6-RESET_ALL_ASICS

6 FABRIC

FABRIC_SRVR-7-ERR_BAG_REG

7 FABRIC

FABRIC_SRVR-7-ERR_DEBUG_INIT

7 FABRIC

FABRIC_SRVR-7-ERR_DEBUG_REG

7 FABRIC

FABRIC_SRVR-7-ERR_INTERNAL_SW

7 FABRIC

FABRIC_SRVR-7-ERR_PCDS_SUPPORT

7 FABRIC

FABRIC_SRVR-7-ERR_SYSDB_EDM_REG

7 FABRIC

FABRICQ_MGR-3-ERR_FBP_CFG

3 FABRIC

FABRICQ_MGR-3-ERR_INIT

3 FABRIC

FABRICQ_MGR-3-ERR_MEM_ALLOC

3 FABRIC

FABRICQ_MGR-3-IMDR_ABORT

3 FABRIC

FABRICQ_MGR-4-ERR_CHKPT_INIT

4 FABRIC

FABRICQ_MGR-4-ERR_IMDR_NOTIFY

4 FABRIC

FABRICQ_MGR-4-WARN_INIT

4 FABRIC

FABRICQ_MGR-7-ERR_BAG_REG

7 FABRIC

FABRICQ_MGR-7-ERR_CLIENT_REG

7 FABRIC

FABRICQ_MGR-7-ERR_DLL_INIT

7 FABRIC

FABRICQ_MGR-7-ERR_EVM_CREATE

7 FABRIC

FABRICQ_MGR-7-ERR_EVM_NOTIFY

7 FABRIC

FABRICQ_MGR-7-ERR_LWM_EVENT_BLOCK

7 FABRIC

FABRICQ_MGR-7-ERR_LWM_REPLY

7 FABRIC

FABRICQ_MGR-7-ERR_SYSDB_EDM_REG

7 FABRIC

FABRICQ_MGR-7-INFO_IMDR

7 FABRIC

FABRICQ-1-ERR_ASIC_ERROR

1 FABRIC

FABRICQ-1-ERR_ASIC_ERROR

1 FABRIC

FABRICQ-1-ERR_ASIC_GENERIC

1 FABRIC

FABRICQ-1-ERR_ASIC_GENERIC

1 FABRIC

FABRICQ-1-ERR_HW_DLL

1 FABRIC

FABRICQ-1-ERR_HW_DLL

1 FABRIC

FABRICQ-1-ERR_SW_DLL

1 FABRIC

FABRICQ-1-ERR_SW_DLL

1 FABRIC

FABRICQ-1-FFI_LINK_BRINGDOWN

1 FABRIC

FABRICQ-1-FFI_LINK_BRINGDOWN

1 FABRIC

FABRICQ-1-IO_ERROR

1 FABRIC

FABRICQ-1-IO_ERROR

1 FABRIC

FABRICQ-3-EEPROM_ERR

3 FABRIC

FABRICQ-3-ERR_ASIC_FCRAM_ASSERT

3 FABRIC

FABRICQ-3-ERR_ASIC_INIT

3 FABRIC

FABRICQ-3-ERR_ASIC_INIT

3 FABRIC

FABRICQ-3-ERR_BIST

3 FABRIC

FABRICQ-3-ERR_DEBUG_INIT

3 FABRIC

FABRICQ-3-ERR_DEBUG_INIT

3 FABRIC

FABRICQ-3-ERR_DEBUG_REGS

3 FABRIC

FABRICQ-3-ERR_DEBUG_REGS

3 FABRIC

FABRICQ-3-ERR_DMA

3 FABRIC

FABRICQ-3-ERR_DMA

3 FABRIC

FABRICQ-3-ERR_INIT

3 FABRIC

FABRICQ-3-ERR_NULL_INPUT_ARGS

3 FABRIC

FABRICQ-3-ERR_NULL_INPUT_ARGS

3 FABRIC

FABRICQ-3-ERR_RX_FBP

3 FABRIC

FABRICQ-3-ERR_RX_FBP

3 FABRIC

FABRICQ-3-ERR_RX_FBP

3 FABRIC

FABRICQ-3-PCL_CCNT_ERR

3 FABRIC

FABRICQ-3-PCL_CSLOT_SYNC

3 FABRIC

FABRICQ-3-PCL_PKT

3 FABRIC

FABRICQ-3-PCL_XCELL_ERR

3 FABRIC

FABRICQ-3-RESET

3 FABRIC

FABRICQ-4-ERR_ASIC_MBE

4 FABRIC

FABRICQ-4-ERR_ASIC_PARITY

4 FABRIC

FABRICQ-4-ERR_ASIC_SN_LINK

4 FABRIC

FABRICQ-4-FI_LINK_ALARM

4 FABRIC

FABRICQ-4-FI_LINK_BRINGDOWN

4 FABRIC

FABRICQ-4-FI_TOPOLOGY

4 FABRIC

FABRICQ-4-HEALTH_MONITOR

4 FABRIC

FABRICQ-4-MI_WEDGE

4 FABRIC

FABRICQ-4-PSN_WRAP

4 FABRIC

FABRICQ-5-ERR_RES_PROG

5 FABRIC

FABRICQ-5-MI_BPDECODE

5 FABRIC

FABRICQ-6-ERR_ASIC_EOP

6 FABRIC

FABRICQ-6-ERR_ASIC_GENERIC

6 FABRIC

FABRICQ-6-ERR_ASIC_OOR

6 FABRIC

FABRICQ-6-ERR_ASIC_RESET_DEFERRAL

6 FABRIC

FABRICQ-6-ERR_ASIC_SBE

6 FABRIC

FABRICQ-6-SPI_FBP

6 FABRIC

FABRICQ-6-URG_CTX

6 FABRIC

FABRICQ-7-ERR_DMA

7 FABRIC

FDI-3-EES_ANNOUNCEMENT_ERR

3 FABRIC

FDI-3-ERR_SEND_FAIL

3 FABRIC

FDI-3-ERR_TLV_HDR

3 FABRIC

FDI-3-ERR_TLV_TYPE

3 FABRIC

FEATURE_LPTS-3-DOUBLE_FREE

3 FABRIC

FEATURE_LPTS-3FGID_DB_RETRIES_EXCEEDED

3 FABRIC

FEATURE_LPTS-3-UNALLOCATED_FREE

3 FABRIC

FEATURE_LPTS-3UNKNOWN_FGID_DB_ERROR

3 FABRIC

FGID_AGG-3-ERR_DEBUG_INIT

3 FABRIC

FGID_AGG-3-ERR_EVM_CREATE

3 FABRIC

FGID_AGG-3-ERR_EVM_SYNC_ATTACH

3 FABRIC

FGID_AGG-3-ERR_GSP

3 FABRIC

FGID_AGG-3-ERR_INTERNAL_SW

3 FABRIC

FGID_AGG-3-ERR_MEM_ALLOC

3 FABRIC

FGID_AGG-3-ERR_SYSMGR

3 FABRIC

FGID_AGG-7-ERR_LTRACE_INIT

7 FABRIC

FGID_ALLOC-3-ERR_EVM_CREATE

3 FABRIC

FGID_ALLOC-3-ERR_GSP

3 FABRIC

FGID_ALLOC-3-ERR_INTERNAL_SW

3 FABRIC

FGID_ALLOC-3-ERR_MEM_ALLOC

3 FABRIC

FGID_ALLOC-3-ERR_SYSMGR

3 FABRIC

FGID_ALLOC-7-ERR_BAG_REG

7 FABRIC

FGID_ALLOC-7-ERR_CHKPT_INIT

7 FABRIC

FGID_ALLOC-7-ERR_CHKPT_ITERATE_START

7 FABRIC

FGID_ALLOC-7-ERR_CHKPT_REG

7 FABRIC

FGID_ALLOC-7-ERR_DEBUG_INIT

7 FABRIC

FGID_ALLOC-7-ERR_LTRACE_INIT

7 FABRIC

FGID_ALLOC-7-ERR_SYSDB_BIND

7 FABRIC

FGID_ALLOC-7-ERR_SYSDB_EDM_REG

7 FABRIC

FGID_BCDL_CONSUMER-3-ERR_BCDL

3 FABRIC

FGID_BCDL_CONSUMER-3ERR_BOARD_TYPE

3 FABRIC

FGID_BCDL_CONSUMER-3-ERR_DEBUG_INIT

3 FABRIC

FGID_BCDL_CONSUMER-3-ERR_EVM

3 FABRIC

FGID_BCDL_CONSUMER-3ERR_FDI_CLIENT_REG

3 FABRIC

FGID_BCDL_CONSUMER-3ERR_FGID_DOWNLOAD_DONE_NOTIF

3 FABRIC

FGID_BCDL_CONSUMER-3-ERR_FGID_SET

3 FABRIC

FGID_BCDL_CONSUMER-3-ERR_RACK_NUM

3 FABRIC

FGID_BCDL_CONSUMER-7-ERR_LTRACE_INIT

7 FABRIC

FGID_LIB-7-ERR_DEBUG_INIT

7 FABRIC

FGID_LIB-7-ERR_LTRACE_INIT

7 FABRIC

FGID_SVR-2-ERR_EES_INIT

2 FABRIC

FGID_SVR-3-ERR_BCDL

3 FABRIC

FGID_SVR-3-ERR_DSC

3 FABRIC

FGID_SVR-3-ERR_EES

3 FABRIC

FGID_SVR-3-ERR_EES_REQ

3 FABRIC

FGID_SVR-3-ERR_EVM_CREATE

3 FABRIC

FGID_SVR-3-ERR_EVM_SYNC_ATTACH

3 FABRIC

FGID_SVR-3-ERR_GSP

3 FABRIC

FGID_SVR-3-ERR_INTERNAL_SW

3 FABRIC

FGID_SVR-3-ERR_INV_FGID

3 FABRIC

FGID_SVR-3-ERR_INVALID_CARD_TYPE

3 FABRIC

FGID_SVR-3-ERR_MEM_ALLOC

3 FABRIC

FGID_SVR-3-ERR_USAGE

3 FABRIC

FGID_SVR-4-WARNING_INTERNAL_SW

4 FABRIC

FGID_SVR-7-ERR_LTRACE_INIT

7 FABRIC

FGID_SVR-7-ERR_SYSMGR

7 FABRIC

FIA_API-7-ERR_ECM

7 FABRIC

FIA_CLIENT-3-GEN_ERR

3 FABRIC

FIA_CLIENT-3-GEN_ERR_1

3 FABRIC

FIA_CLIENT-3-GEN_ERR_2

3 FABRIC

FIA_CLIENT-3-GEN_ERR_3

3 FABRIC

FIA_CLIENT-6-GEN_INFO

6 FABRIC

FIA_DRVR-3-AMBA_INIT_FAILURE

3 FABRIC

FIA_DRVR-3-CIH_INIT_FAILURE

3 FABRIC

FIA_DRVR-3-CLIENT_REGISTRATION_FAILED

3 FABRIC

FIA_DRVR-3-ERR_ECM_OPEN

3 FABRIC

FIA_DRVR-3-ERR_EVM_CREATE

3 FABRIC

FIA_DRVR-3-ERR_MSGQ_CREATE

3 FABRIC

FIA_DRVR-3-ERR_SERVICE_CONN_INIT

3 FABRIC

FIA_DRVR-3-ERR_THREAD_CREATE

3 FABRIC

FIA_DRVR-3-ERR_VENDOR_SDK_INIT

3 FABRIC

FIA_DRVR-3-EXIT_DRVR

3 FABRIC

FIA_DRVR-3-FSDB_RESPONSE_FAILURE

3 FABRIC

FIA_DRVR-3-FSDB_SERVICE_FAILURE

3 FABRIC

FIA_DRVR-3-PCI_ATTACH_FAIL

3 FABRIC

FIA_DRVR-3-SERVICE_FAILURE

3 FABRIC

FIA_DRVR-3-TM_INIT_FAILURE

3 FABRIC

FIA_DRVR-4-ERR_LTRACE_INIT

4 FABRIC

FIA-0-ASIC_FATAL_FAULT

--

FABRIC

FIA-1-ARB_SERDES_0_FAIL_0

1 FABRIC

FIA-1-ARB_SERDES_0_FAIL_1

1 FABRIC

FIA-1-ARB_SERDES_1_FAIL_0

1 FABRIC

FIA-1-ARB_SERDES_1_FAIL_1

1 FABRIC

FIA-1-ASIC_INIT_ERR_0

1 FABRIC

FIA-1-ASIC_INIT_ERR_1

1 FABRIC

FIA-1-DATA_NB_SERDES_0_FAIL_0

1 FABRIC

FIA-1-DATA_NB_SERDES_1_FAIL_0

1 FABRIC

FIA-1-DATA_NB_SERDES_2_FAIL_0

1 FABRIC

FIA-1-DATA_NB_SERDES_3_FAIL_0

1 FABRIC

FIA-1-DATA_SB_SERDES_0_FAIL_0

1 FABRIC

FIA-1-DATA_SB_SERDES_1_FAIL_0

1 FABRIC

FIA-1-DATA_SERDES_0_FAIL_0

1 FABRIC

FIA-1-DATA_SERDES_0_FAIL_1

1 FABRIC

FIA-1-DATA_SERDES_1_FAIL_0

1 FABRIC

FIA-1-DATA_SERDES_1_FAIL_1

1 FABRIC

FIA-1-DATA_SERDES_2_FAIL_0

1 FABRIC

FIA-1-DATA_SERDES_2_FAIL_1

1 FABRIC

FIA-1-DATA_SERDES_3_FAIL_0

1 FABRIC

FIA-1-DATA_SERDES_3_FAIL_1

1 FABRIC

FIA-1-PKT_INT_ERR_AT_DDRIF_0_0

1 FABRIC

FIA-1-PKT_INT_ERR_AT_DDRIF_0_1

1 FABRIC

FIA-1-PKT_INT_ERR_AT_DDRIF_1_0

1 FABRIC

FIA-1-PKT_INT_ERR_AT_DDRIF_1_1

1 FABRIC

FIA-1-PKT_INT_ERR_AT_ILIF_0_0

1 FABRIC

FIA-1-PKT_INT_ERR_AT_ILIF_1_0

1 FABRIC

FIA-1-SKT_AB_INTR_FIFO_ORUN_0

1 FABRIC

FIA-1-SKT_AB_INTR_FIFO_URUN_0

1 FABRIC

FIA-1-SKT_AB_INTR_IFIFO_ORUN0_0

1 FABRIC

FIA-1-SKT_AB_INTR_IFIFO_ORUN1_0

1 FABRIC

FIA-1-SKT_BA_INTR_PA_STALLED_0

1 FABRIC

FIA-1-SKT_BA_INTR_QUEUE_LEN_URUN_0

1 FABRIC

FIA-1-SKT_CR_INTR_CR_AB_FC_0

1 FABRIC

FIA-1-SKT_DM_INTR_FIFO_URUN_0

1 FABRIC

FIA-1-SKT_DM_INTR_VM_IFIFO_ORUN_0

1 FABRIC

FIA-1SKT_ED_SCH_INTR_MC_BUFFER_HANG_0

1 FABRIC

FIA-1SKT_ED_SCH_INTR_MC_QTYPE_HANG_0

1 FABRIC

FIA-1SKT_ED_SCH_INTR_UC_QTYPE_HANG_0

1 FABRIC

FIA-1-SKT_ET0_INTR_CRC16_CHK_ERR_0

1 FABRIC

FIA-1-SKT_ET0_INTR_CRC32_CHK_ERR_0

1 FABRIC

FIA-1-SKT_ET0_INTR_HDR_CSUM_ERR_0

1 FABRIC

FIA-1-SKT_ET0_INTR_MISSING_EOP_0

1 FABRIC

FIA-1-SKT_ET0_INTR_MISSING_SOP_0

1 FABRIC

FIA-1-SKT_ET0_INTR_SOP_ERR_0

1 FABRIC

FIA-1-SKT_ET1_INTR_CRC16_CHK_ERR_0

1 FABRIC

FIA-1-SKT_ET1_INTR_CRC32_CHK_ERR_0

1 FABRIC

FIA-1-SKT_ET1_INTR_HDR_CSUM_ERR_0

1 FABRIC

FIA-1-SKT_ET1_INTR_MISSING_EOP_0

1 FABRIC

FIA-1-SKT_ET1_INTR_MISSING_SOP_0

1 FABRIC

FIA-1-SKT_ET1_INTR_SOP_ERR_0

1 FABRIC

FIA-1-SKT_FI_INTR_RCTL0_HI_EOP_ERR_0

1 FABRIC

FIA-1-SKT_FI_INTR_RCTL0_HI_OVERRUN_0

1 FABRIC

FIA-1-SKT_FI_INTR_RCTL0_LO_EOP_ERR_0

1 FABRIC

FIA-1-SKT_FI_INTR_RCTL0_LO_OVERRUN_0

1 FABRIC

FIA-1-SKT_FI_INTR_RCTL1_HI_EOP_ERR_0

1 FABRIC

FIA-1-SKT_FI_INTR_RCTL1_HI_OVERRUN_0

1 FABRIC

FIA-1-SKT_FI_INTR_RCTL1_LO_EOP_ERR_0

1 FABRIC

FIA-1-SKT_FI_INTR_RCTL1_LO_OVERRUN_0

1 FABRIC

FIA-1SKT_IR0_INTR_ACCPT_TBL_DROP_ERR_0

1 FABRIC

FIA-1-SKT_IR0_INTR_DC3_MAX_DROP_ERR_0

1 FABRIC

FIA-1-SKT_IR0_INTR_DC3_MIN_DROP_ERR_0

1 FABRIC

FIA-1-SKT_IR0_INTR_FC_BUF_OVFLOW_0

1 FABRIC

FIA-1-SKT_IR0_INTR_FIFO_ORUN_0

1 FABRIC

FIA-1-SKT_IR0_INTR_FIFO_URUN_0

1 FABRIC

FIA-1-SKT_IR0_INTR_PKT_EOP_ERR_0

1 FABRIC

FIA-1-SKT_IR0_INTR_SHORTKT_DROP_ERR_0

1 FABRIC

FIA-1SKT_IR1_INTR_ACCPT_TBL_DROP_ERR_0

1 FABRIC

FIA-1-SKT_IR1_INTR_DC3_MAX_DROP_ERR_0

1 FABRIC

FIA-1-SKT_IR1_INTR_DC3_MIN_DROP_ERR_0

1 FABRIC

FIA-1-SKT_IR1_INTR_FC_BUF_OVFLOW_0

1 FABRIC

FIA-1-SKT_IR1_INTR_FIFO_ORUN_0

1 FABRIC

FIA-1-SKT_IR1_INTR_FIFO_URUN_0

1 FABRIC

FIA-1-SKT_IR1_INTR_PKT_EOP_ERR_0

1 FABRIC

FIA-1-SKT_IR1_INTR_SHORTKT_DROP_ERR_0

1 FABRIC

FIA-1-SKT_NI_INTR_BA_STALLED_0

1 FABRIC

FIA-1-SKT_NI_INTR_CRC_ERR0_0

1 FABRIC

FIA-1-SKT_NI_INTR_CRC_ERR1_0

1 FABRIC

FIA-1-SKT_NI_INTR_CRC_ERR2_0

1 FABRIC

FIA-1-SKT_NI_INTR_CRC_ERR3_0

1 FABRIC

FIA-1-SKT_NI_INTR_CRC_ERR4_0

1 FABRIC

FIA-1-SKT_NI_INTR_PW_STALLED_0

1 FABRIC

FIA-1-SKT_PA_INTR_MAX_SZ_ERR_0

1 FABRIC

FIA-1-SKT_PA_INTR_UCFF_UDR_ERR_0

1 FABRIC

FIA-1SKT_PR_INTR_PR_BA_PROTOCOL_ERR_0

1 FABRIC

FIA-1SKT_PW_INTR_HDR_PRS_CHDR_VQI_VLD_ER
R_0

1 FABRIC

FIA-1SKT_PW_INTR_HDR_PRS_EOP_SOP_ERR_0

1 FABRIC

FIA-1SKT_PW_INTR_HDR_PRS_HDR_TYPE_ERR_0

1 FABRIC

FIA-1SKT_PW_INTR_HDR_PRS_SOP_EOP_ERR_0

1 FABRIC

FIA-1SKT_PW_INTR_HDR_PRS_SOP_SEEN_SOP_ER
R_0

1 FABRIC

FIA-1-SKT_PW_INTR_LEN_DROP_CNT_ERR_0

1 FABRIC

FIA-1SKT_PW_INTR_SRC_PT_MISMATCH_ERR_0

1 FABRIC

FIA-1-SKT_RA_INTR_VQI_DEQ_QERR_0

1 FABRIC

FIA-1-SKT_RA_INTR_VQI_ENQ_QERR_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_0_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_1_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_10_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_11_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_12_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_13_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_14_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_15_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_2_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_3_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_4_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_5_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_6_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_7_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_8_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_9_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_0_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_1_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_10_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_11_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_12_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_13_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_14_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_15_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_2_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_3_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_4_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_5_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_6_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_7_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_8_0

1 FABRIC

FIA-1SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_9_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_0_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_1_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_10_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_11_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_12_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_13_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_14_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_15_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_2_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_3_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_4_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_5_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_6_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_7_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_8_0

1 FABRIC

FIA-1SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_9_0

1 FABRIC

FIA-1-SKT_SMC0_INTR_CRC_TRANS_ERR_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_0_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_1_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_10_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_11_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_12_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_13_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_14_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_15_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_2_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_3_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_4_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_5_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_6_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_7_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_8_0

1 FABRIC

FIA-1SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_9_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_0_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_1_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_10_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_11_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_12_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_13_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_14_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_15_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_2_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_3_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_4_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_5_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_6_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_7_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_8_0

1 FABRIC

FIA-1SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_9_0

1 FABRIC

FIA-1-SKT_SMC0_INTR_RX_DESKEW_ERR_0

1 FABRIC

FIA-1SKT_SMC0_INTR_TSF_SOT_MISS_ERROR_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_0_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_1_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_10_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_11_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_12_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_13_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_14_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_15_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_2_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_3_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_4_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_5_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_6_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_7_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_8_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_9_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_0_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_1_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_10_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_11_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_12_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_13_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_14_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_15_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_2_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_3_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_4_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_5_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_6_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_7_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_8_0

1 FABRIC

FIA-1SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_9_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_0_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_1_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_10_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_11_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_12_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_13_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_14_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_15_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_2_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_3_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_4_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_5_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_6_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_7_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_8_0

1 FABRIC

FIA-1SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_9_0

1 FABRIC

FIA-1-SKT_SMC1_INTR_CRC_TRANS_ERR_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_0_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_1_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_10_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_11_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_12_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_13_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_14_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_15_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_2_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_3_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_4_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_5_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_6_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_7_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_8_0

1 FABRIC

FIA-1SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_9_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_0_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_1_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_10_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_11_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_12_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_13_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_14_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_15_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_2_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_3_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_4_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_5_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_6_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_7_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_8_0

1 FABRIC

FIA-1SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_9_0

1 FABRIC

FIA-1-SKT_SMC1_INTR_RX_DESKEW_ERR_0

1 FABRIC

FIA-1SKT_SMC1_INTR_TSF_SOT_MISS_ERROR_0

1 FABRIC

FIA-1-SKT_SP0_INTR_ALIGN_FAIL_0

1 FABRIC

FIA-1-SKT_SP0_INTR_BAD_ALIGN_0

1 FABRIC

FIA-1-SKT_SP0_INTR_BAD_CODE_0

1 FABRIC

FIA-1-SKT_SP0_INTR_CW_CRC_ERR_0

1 FABRIC

FIA-1-SKT_SP0_INTR_LANE_CRC_ERR_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE_ERR_0_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE_ERR_1_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE_ERR_2_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE_ERR_3_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE_ERR_4_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE_ERR_5_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE_ERR_6_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE_ERR_7_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE0_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE0_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE0_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE0_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE1_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE1_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE1_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE1_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE2_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE2_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE2_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE2_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE3_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE3_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE3_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE3_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE4_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE4_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE4_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE4_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE5_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE5_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE5_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE5_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE6_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE6_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE6_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE6_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP0_INTR_SLICE7_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE7_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE7_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP0_INTR_SLICE7_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP1_INTR_ALIGN_FAIL_0

1 FABRIC

FIA-1-SKT_SP1_INTR_BAD_ALIGN_0

1 FABRIC

FIA-1-SKT_SP1_INTR_BAD_CODE_0

1 FABRIC

FIA-1-SKT_SP1_INTR_CW_CRC_ERR_0

1 FABRIC

FIA-1-SKT_SP1_INTR_LANE_CRC_ERR_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE_ERR_0_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE_ERR_1_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE_ERR_2_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE_ERR_3_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE_ERR_4_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE_ERR_5_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE_ERR_6_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE_ERR_7_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE0_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE0_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE0_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE0_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE1_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE1_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE1_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE1_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE2_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE2_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE2_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE2_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE3_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE3_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE3_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE3_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE4_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE4_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE4_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE4_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE5_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE5_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE5_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE5_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE6_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE6_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE6_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE6_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SP1_INTR_SLICE7_CODE_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE7_CODE_ERR_HIGH_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE7_LANE_CRC_ERR_0

1 FABRIC

FIA-1SKT_SP1_INTR_SLICE7_WORD_OUTSYNC_0

1 FABRIC

FIA-1-SKT_SSP_INTR_SFIFO_FULL_IF0_0

1 FABRIC

FIA-1-SKT_SSP_INTR_SFIFO_FULL_IF1_0

1 FABRIC

FIA-1-SKT_SSP_INTR_SP0_RX_EOP_ERR_P_0

1 FABRIC

FIA-1SKT_SSP_INTR_SP0_RX_NEOP_ERR_P_0

1 FABRIC

FIA-1-SKT_SSP_INTR_SP1_RX_EOP_ERR_P_0

1 FABRIC

FIA-1SKT_SSP_INTR_SP1_RX_NEOP_ERR_P_0

1 FABRIC

FIA-1-SKT_TF_INTR_FIFO_0HI_EXT_ERR_0

1 FABRIC

FIA-1-SKT_TF_INTR_FIFO_0HI_OVFL_0

1 FABRIC

FIA-1-SKT_TF_INTR_FIFO_0LO_OVFL_0

1 FABRIC

FIA-1-SKT_TF_INTR_FIFO_1HI_EXT_ERR_0

1 FABRIC

FIA-1-SKT_TF_INTR_FIFO_1HI_OVFL_0

1 FABRIC

FIA-1-SKT_TF_INTR_FIFO_1LO_OVFL_0

1 FABRIC

FIA-1-SKT_VM_INTR_AB_REQ_TOUT_ERR_0

1 FABRIC

FIA-1-SKT_VM_INTR_DM_REQ_TOUT_ERR_0

1 FABRIC

FIA-1-SKT_VM_INTR_DM_UNEXP_GNT_ERR_0

1 FABRIC

FIA-1-SKT_VM_INTR_PA_SOF_EOF_ERR_0

1 FABRIC

FIA-1-SUSTAINED_CRC_ERR

1 FABRIC

FIA-1-TEMP_TOO_HIGH_0

1 FABRIC

FIA-1-TEMP_TOO_HIGH_1

1 FABRIC

FIA-2-ERR_MUTEX_LOCK

2 FABRIC

FIA-2-ERR_MUTEX_UNLOCK

2 FABRIC

FIA-2-FIAHW_INT_FIFO

2 FABRIC

FIA-2-FIAHW_INT_PARITY

2 FABRIC

FIA-3-ERR_BRIDGE

3 FABRIC

FIA-3-ERR_BRIDGE_EVM

3 FABRIC

FIA-3-ERR_BRIDGE_INIT

3 FABRIC

FIA-3-ERR_BRIDGE_OS

3 FABRIC

FIA-3-ERR_CLIENT_EVM

3 FABRIC

FIA-3-ERR_CLIENT_INIT

3 FABRIC

FIA-3-ERR_ECM_CREATE

3 FABRIC

FIA-3-ERR_ECM_REG

3 FABRIC

FIA-3-ERR_EIO_TRAIN

3 FABRIC

FIA-3-ERR_ENS_LIB

3 FABRIC

FIA-3-ERR_ENS_MSG

3 FABRIC

FIA-3-ERR_EVM_CREATE

3 FABRIC

FIA-3-ERR_EVM_INIT

3 FABRIC

FIA-3-ERR_FIA__EVT_MGR_INIT

3 FABRIC

FIA-3-ERR_FIA_DRV_INIT

3 FABRIC

FIA-3-ERR_INIT

3 FABRIC

FIA-3-ERR_INIT

3 FABRIC

FIA-3-ERR_INIT_XAUI

3 FABRIC

FIA-3-ERR_LTRACE_INIT

3 FABRIC

FIA-3-ERR_MEM

3 FABRIC

FIA-3-ERR_MEM_ALLOC

3 FABRIC

FIA-3-ERR_MEM_ALLOC

3 FABRIC

FIA-3-ERR_MEM_MAP

3 FABRIC

FIA-3-ERR_PLL

3 FABRIC

FIA-3-ERR_REGISTER

3 FABRIC

FIA-3-ERR_RESTART

3 FABRIC

FIA-3-ERR_SHELFMGR_INIT

3 FABRIC

FIA-3-FFIAHW_ERR_FIFO

3 FABRIC

FIA-3-FFIAHW_ERR_PARITY

3 FABRIC

FIA-3-FIAHW_CHIP

3 FABRIC

FIA-3-FIAHW_CRC16

3 FABRIC

FIA-3-FIAHW_CRC16

3 FABRIC

FIA-3-FIAHW_DEVCTL

3 FABRIC

FIA-3-FIAHW_EMPTY_DEST_SOFTREQ

3 FABRIC

FIA-3-FIAHW_EXT_FIFO

3 FABRIC

FIA-3-FIAHW_EXT_PARITY

3 FABRIC

FIA-3-FIAHW_INT

3 FABRIC

FIA-3-FIAHW_LOS

3 FABRIC

FIA-3-FIAHW_LOS

3 FABRIC

FIA-3-FIAHW_LOS_CLEAR

3 FABRIC

FIA-3-FIAHW_LOS_CLEAR

3 FABRIC

FIA-3-FIAHW_MULTI_DEST_SOFTREQ

3 FABRIC

FIA-3-FIAHW_NOHALT

3 FABRIC

FIA-3-FIAHW_RATE

3 FABRIC

FIA-3-FIAHW_RATE

3 FABRIC

FIA-3-FIAHW_TMR

3 FABRIC

FIA-3-FIAHW_TMR

3 FABRIC

FIA-3-FIAHW_UNHANDLED

3 FABRIC

FIA-3-FIAHW_UNHANDLED

3 FABRIC

FIA-3-GEN_ERR

3 FABRIC

FIA-3-GEN_ERR_1

3 FABRIC

FIA-3-GEN_ERR_2

3 FABRIC

FIA-3-GEN_ERR_3

3 FABRIC

FIA-3-LIBENS_ERR

3 FABRIC

FIA-3-LIBENS_INIT

3 FABRIC

FIA-3-LIBENS_PRODUCER

3 FABRIC

FIA-3-TFIAHW_ERR_PACKET

3 FABRIC

FIA-3-TFIAHW_ERR_PARITY

3 FABRIC

FIA-4-ERR_CHKPT

4 FABRIC

FIA-4-ERR_SYSDB_CONN_TO_COID

4 FABRIC

FIA-4-ERR_SYSDB_EDM_REG

4 FABRIC

FIA-4FIAHW_WARNING_UNSUPPORTED_CARD

4 FABRIC

FIA-5-ERR_DEV_NOT_FOUND

5 FABRIC

FIA-6-FABRIC_ISOLATE

6 FABRIC

FIA-6-PCDS_STATS_TIMESTAMP_FAILURE

6 FABRIC

FIA-6-PCDS_STATS_TIMESTAMP_FAILURE

6 FABRIC

FIA-7-ERR_CHKPT_INIT

7 FABRIC

FIA-7-ERR_CHKPT_REG

7 FABRIC

FIA-7-ERR_EVM

7 FABRIC

FIA-7-ERR_EVM_ASYNC_ATTACH

7 FABRIC

FIA-7-ERR_EVM_CREATE

7 FABRIC

FIA-7-ERR_LWM_EVENT_BLOCK

7 FABRIC

FIA-7-ERR_LWM_REPLY

7 FABRIC

FIA-7-ERR_MEM_ALLOC

7 FABRIC

FIA-7-ERR_SYSDB_EDM_DATALIST

7 FABRIC

FIA-7-ERR_SYSDB_EDM_OPEN

7 FABRIC

FIA-7-ERR_THREAD_CREATE

7 FABRIC

FIFO-2-SW_FATAL_ERROR

2 FABRIC

FSDB_FADB_MAIN-3-EVT_MGR_CREATE_FAIL

3 FABRIC

FSDB_FADB_MAIN-3EXTRACT_NODE_ID_FAIL

3 FABRIC

FSDB_FADB_MAIN-3-GET_NODE_ID_FAIL

3 FABRIC

FSDB_FADB_MAIN-3RESPAWN_COUNT_GET_FAIL

3 FABRIC

FSDB_FADB_MAIN-3SYNC_HDLR_ATTACH_FAIL

3 FABRIC

FSDB_FADB_MAIN-3-SYSDB_BIND_FAIL

3 FABRIC

FSDB_FADB_MAIN-3-SYSDB_LIST_FREE_FAIL

3 FABRIC

FSDB_FADB-3-SHM_CREATE_FAIL

3 FABRIC

FSDB_FADB-3-SHM_OPEN_FAIL

3 FABRIC

FSDB_FADB-4-SHM_FILE_TRUNCATE_FAIL

4 FABRIC

FSDB_FADB-4-SHM_MMAP_FAIL

4 FABRIC

FSDB-0-BARRIER_STALL_RACK_RELOAD

--

FABRIC

FSDB-0-BARRIER_STALL_ROUTER_RELOAD

--

FABRIC

FSDB-0-FABRIC_LOSS_LC_RELOAD

--

FABRIC

FSDB-1-ERR_PLANE_CONFIG

1 FABRIC

FSDB-1-FABRIC_ADMIN_CFG

1 FABRIC

FSDB-1-FABRIC_UPDOWN

1 FABRIC

FSDB-1-PLANE_UPDOWN

1 FABRIC

FSDB-2-CONN_ERR

2 FABRIC

FSDB-2-ERR_CONTROL_MSG

2 FABRIC

FSDB-2-INVALID_PLANE_SHUT_REQ

2 FABRIC

FSDB-2-MSG_TO_FSDB_FAILED_CONNECT

2 FABRIC

FSDB-2-MSG_TO_FSDB_FAILED_SEND

2 FABRIC

FSDB-2-RACK_DOWN

2 FABRIC

FSDB-3-AIPC_CLIENT_ERR_INTERNAL

3 FABRIC

FSDB-3-ASERVER_DOWNLOAD

3 FABRIC

FSDB-3-ASIC_RESET_INVALID_ST

3 FABRIC

FSDB-3-DEVCTL_FAIL

3 FABRIC

FSDB-3-ERR_BUNDLE_LINK

3 FABRIC

FSDB-3-ERR_BUNDLE_STATE

3 FABRIC

FSDB-3-ERR_CHKPT

3 FABRIC

FSDB-3-ERR_CHKPT_INIT

3 FABRIC

FSDB-3-ERR_DEBUG

3 FABRIC

FSDB-3-ERR_DSC

3 FABRIC

FSDB-3-ERR_ECM_CREATE

3 FABRIC

FSDB-3-ERR_ECM_NOTIFY

3 FABRIC

FSDB-3-ERR_EVM_CREATE

3 FABRIC

FSDB-3-ERR_GET_NODEID

3 FABRIC

FSDB-3-ERR_INTERNAL

3 FABRIC

FSDB-3-ERR_PARSE_FILE

3 FABRIC

FSDB-3-ERR_RESYNC_ASSERT

3 FABRIC

FSDB-3-ERR_RESYNC_TIMEOUT

3 FABRIC

FSDB-3-ERR_SYSDB

3 FABRIC

FSDB-3-ERR_SYSDB_BIND

3 FABRIC

FSDB-3-ERR_SYSDB_EDM_NOTIF_GEN

3 FABRIC

FSDB-3-ERR_SYSDB_EDM_REG

3 FABRIC

FSDB-3-ERR_SYSDB_REG_NOTIF

3 FABRIC

FSDB-3-ERR_UNKNOWN_FAB_DEF

3 FABRIC

FSDB-3-INVAL_ST_DRVR_HNDL

3 FABRIC

FSDB-3-OOO_INGRESSQ_HW_ENT

3 FABRIC

FSDB-3-OPEN_FAIL

3 FABRIC

FSDB-3UNSUPPORTED_RACK_NUM_FOR_CONFIG

3 FABRIC

FSDB-4-ERR_DEST_CONN

4 FABRIC

FSDB-4-ERR_FLED

4 FABRIC

FSDB-4-ERR_INTERNAL_WARN

4 FABRIC

FSDB-4-ERR_THREAD_COND_SIGNAL

4 FABRIC

FSDB-4-ERR_THREAD_COND_WAIT

4 FABRIC

FSDB-4-ERR_THREAD_MUTEX_LOCK

4 FABRIC

FSDB-4-ERR_THREAD_MUTEX_UNLOCK

4 FABRIC

FSDB-4-INVALID_FAB_MODE

4 FABRIC

FSDB-4-PLANE_SHUTDOWN

4 FABRIC

FSDB-6-BOOT_WITHOUT_FABRIC

6 FABRIC

FSDB-6-PLANE_DEST_UNREACHABLE

6 FABRIC

FSDB-6-PLANE_GROUP_DISABLED

6 FABRIC

FSDB-6-PLANE_GROUP_UNREACHABLE

6 FABRIC

FSDB-6-PLANE_RACK_MCAST_DOWN

6 FABRIC

FSDB-7-ERR_MEM_ALLOC

7 FABRIC

FSDB-7-ERR_SYSDB_BAG_ENCODE

7 FABRIC

FSTATSA-3-ERR_BAG_REG

3 FABRIC

FSTATSA-3-ERR_CLEAR_FSTATS

3 FABRIC

FSTATSA-3-ERR_CLEAR_FSTATS_ALL

3 FABRIC

FSTATSA-3-ERR_DEBUG_INIT_EVENT

3 FABRIC

FSTATSA-3-ERR_DEBUG_REGISTER

3 FABRIC

FSTATSA-3-ERR_EVM_CREATE

3 FABRIC

FSTATSA-3-ERR_GSP_GROUP_CREATE

3 FABRIC

FSTATSA-3-ERR_INTERNAL

3 FABRIC

FSTATSA-3-ERR_SYSDB_BIND

3 FABRIC

FSTATSA-3-ERR_SYSDB_EDM_REG

3 FABRIC

FSTATSA-3-ERR_SYSMGR_PROC_READY

3 FABRIC

FSTATSC-3-ERR_GSP_GROUP_CREATE

3 FABRIC

FSTATSC-7-ERR_DEBUG_CLEANUP

7 FABRIC

FSTATSC-7-ERR_DEBUG_INIT_EVENT

7 FABRIC

FSTATSC-7-ERR_DEBUG_REG

7 FABRIC

FSTATSC-7-ERR_GSP_LOOKUP

7 FABRIC

FSTATSS-3-ERR_BAG_REG

3 FABRIC

FSTATSS-3-ERR_DEBUG_INIT_EVENT

3 FABRIC

FSTATSS-3-ERR_DEBUG_REGISTER

3 FABRIC

FSTATSS-3-ERR_EVM_CREATE

3 FABRIC

FSTATSS-3-ERR_GSP_GROUP_CREATE

3 FABRIC

FSTATSS-3-ERR_INTERNAL

3 FABRIC

FSTATSS-3-ERR_MEM_ALLOC

3 FABRIC

FSTATSS-3-ERR_SYSDB_BIND

3 FABRIC

FSTATSS-3-ERR_SYSDB_EDM_REG

3 FABRIC

FSTATSS-3-ERR_SYSMGR_PROC_READY

3 FABRIC

FSTATSS-7ERR_RSC_REG_INCONSISTENT_VALUE

7 FABRIC

HFR_FSDB_FADB_LTRACE-3ERROR_INIT_FAIL

3 FABRIC

HFR_FSDB_FADB_LTRACE-3EVENT_INIT_FAIL

3 FABRIC

HFR_FSDB_FADB_LTRACE-3INTERNAL_INIT_FAIL

3 FABRIC

INGRESSQ_ALARM-2-DEVICE_HALT

2 FABRIC

INGRESSQ_DLL-1BRM_BARRIER_SYNCUP_FAILED

1 FABRIC

INGRESSQ_DLL-1BRM_BARRIER_SYNCUP_FAILED

1 FABRIC

INGRESSQ_DLL-1-ERR_ASIC_GENERIC

1 FABRIC

INGRESSQ_DLL-1-ERR_ASIC_GENERIC

1 FABRIC

INGRESSQ_DLL-1-ERR_BIST

1 FABRIC

INGRESSQ_DLL-1-ERR_BIST

1 FABRIC

INGRESSQ_DLL-1-ERR_INIT

1 FABRIC

INGRESSQ_DLL-1-ERR_INIT

1 FABRIC

INGRESSQ_DLL-1-ERROR_HW_ACCESS

1 FABRIC

INGRESSQ_DLL-1-ERROR_HW_ACCESS

1 FABRIC

INGRESSQ_DLL-1-ERROR_HW_IMDR

1 FABRIC

INGRESSQ_DLL-1-FATAL_ERR

1 FABRIC

INGRESSQ_DLL-1-TAKING_NODE_DOWN

1 FABRIC

INGRESSQ_DLL-1-TAKING_NODE_DOWN

1 FABRIC

INGRESSQ_DLL-2-ERR_EIO_TRAIN

2 FABRIC

INGRESSQ_DLL-2-TAKING_NODE_DOWN

2 FABRIC

INGRESSQ_DLL-3BRM_BARRIER_SYNCUP_FAILED

3 FABRIC

INGRESSQ_DLL-3ERR_ASIC_FCRAM_ASSERT

3 FABRIC

INGRESSQ_DLL-3-ERR_ASIC_MBE

3 FABRIC

INGRESSQ_DLL-3-ERR_BIST

3 FABRIC

INGRESSQ_DLL-3-ERR_INIT

3 FABRIC

INGRESSQ_DLL-3-ERR_MEM_ALLOC

3 FABRIC

INGRESSQ_DLL-3-ERR_MEM_ALLOC

3 FABRIC

INGRESSQ_DLL-3-ERR_MEM_ALLOC

3 FABRIC

INGRESSQ_DLL-3-RESET

3 FABRIC

INGRESSQ_DLL-3-RESET

3 FABRIC

INGRESSQ_DLL-3-RESET

3 FABRIC

INGRESSQ_DLL-3SEQ_STATE_POST_OP_FAILED

3 FABRIC

INGRESSQ_DLL-3SEQ_STATE_POST_OP_FAILED

3 FABRIC

INGRESSQ_DLL-3SEQ_STATE_POST_OP_FAILED

3 FABRIC

INGRESSQ_DLL-3SEQ_STATE_PRE_OP_FAILED

3 FABRIC

INGRESSQ_DLL-3SEQ_STATE_PRE_OP_FAILED

3 FABRIC

INGRESSQ_DLL-3SEQ_STATE_PRE_OP_FAILED

3 FABRIC

INGRESSQ_DLL-3-SHM_INIT_FAILED

3 FABRIC

INGRESSQ_DLL-3-UNKNOWN_FAB_DEST

3 FABRIC

INGRESSQ_DLL-3-WDG_SEG_HUNG

3 FABRIC

INGRESSQ_DLL-3-WDG_SEG_HUNG

3 FABRIC

INGRESSQ_DLL-3-WDG_SEG_HUNG

3 FABRIC

INGRESSQ_DLL-4BRM_AGGR_DELTA_THRSHLD

4 FABRIC

INGRESSQ_DLL-4BRM_AGGR_DELTA_THRSHLD

4 FABRIC

INGRESSQ_DLL-4BRM_AGGR_DELTA_THRSHLD

4 FABRIC

INGRESSQ_DLL-4-BRM_DELTA_THRSHLD

4 FABRIC

INGRESSQ_DLL-4-BRM_DELTA_THRSHLD

4 FABRIC

INGRESSQ_DLL-4-BRM_DELTA_THRSHLD

4 FABRIC

INGRESSQ_DLL-4-BRM_DID_CULPRIT

4 FABRIC

INGRESSQ_DLL-4-BRM_DID_CULPRIT

4 FABRIC

INGRESSQ_DLL-4-BRM_DID_CULPRIT

4 FABRIC

INGRESSQ_DLL-4-BRM_INVALID_INPUT

4 FABRIC

INGRESSQ_DLL-4-BRM_INVALID_INPUT

4 FABRIC

INGRESSQ_DLL-4-BRM_INVALID_INPUT

4 FABRIC

INGRESSQ_DLL-4BRM_PHASE_CHANGE_COUNTER

4 FABRIC

INGRESSQ_DLL-4BRM_PHASE_CHANGE_COUNTER

4 FABRIC

INGRESSQ_DLL-4BRM_PHASE_CHANGE_COUNTER

4 FABRIC

INGRESSQ_DLL-4-CDMA_REQ_ERROR

4 FABRIC

INGRESSQ_DLL-4-CDMA_REQ_ERROR

4 FABRIC

INGRESSQ_DLL-4-CDMA_REQ_ERROR

4 FABRIC

INGRESSQ_DLL-4-CONFIG_ERR

4 FABRIC

INGRESSQ_DLL-4-ERR_ASIC_CRC

4 FABRIC

INGRESSQ_DLL-4-ERR_ASIC_CRC

4 FABRIC

INGRESSQ_DLL-4-ERR_ASIC_CRC

4 FABRIC

INGRESSQ_DLL-4-ERR_ASIC_DROP

4 FABRIC

INGRESSQ_DLL-4-ERR_ASIC_LENGTH

4 FABRIC

INGRESSQ_DLL-4-ERR_ASIC_LENGTH

4 FABRIC

INGRESSQ_DLL-4-ERR_ASIC_LENGTH

4 FABRIC

INGRESSQ_DLL-4-ERR_ASIC_SN_LINK

4 FABRIC

INGRESSQ_DLL-4-ERR_ASIC_SN_LINK

4 FABRIC

INGRESSQ_DLL-4-ERR_ASIC_SN_LINK

4 FABRIC

INGRESSQ_DLL-4-ERR_CHKPT_INIT

4 FABRIC

INGRESSQ_DLL-4-ERR_CHKPT_INIT

4 FABRIC

INGRESSQ_DLL-4-ERR_CHKPT_INIT

4 FABRIC

INGRESSQ_DLL-4-ERR_CHKPT_INSERT

4 FABRIC

INGRESSQ_DLL-4-ERR_CHKPT_INSERT

4 FABRIC

INGRESSQ_DLL-4-ERR_CHKPT_INSERT

4 FABRIC

INGRESSQ_DLL-4-HEALTH_MONITOR

4 FABRIC

INGRESSQ_DLL-4-INTR_ENABLE_FAIL

4 FABRIC

INGRESSQ_DLL-4-INTR_ENABLE_FAIL

4 FABRIC

INGRESSQ_DLL-4-INTR_ENABLE_FAIL

4 FABRIC

INGRESSQ_DLL-4LNS_CCDF_OVERFLOW_ERROR

4 FABRIC

INGRESSQ_DLL-4LNS_CCDF_OVERFLOW_ERROR

4 FABRIC

INGRESSQ_DLL-4LNS_CCDF_OVERFLOW_ERROR

4 FABRIC

INGRESSQ_DLL-4-LNS_LOP_DROP

4 FABRIC

INGRESSQ_DLL-4-LNS_LOP_DROP

4 FABRIC

INGRESSQ_DLL-4-LNS_LOP_DROP

4 FABRIC

INGRESSQ_DLL-4-PFI_PARITY_ERROR

4 FABRIC

INGRESSQ_DLL-4-PFI_PARITY_ERROR

4 FABRIC

INGRESSQ_DLL-4-PFI_PARITY_ERROR

4 FABRIC

INGRESSQ_DLL-5-ERR_ASIC_PARITY

5 FABRIC

INGRESSQ_DLL-5-ERR_ASIC_PARITY

5 FABRIC

INGRESSQ_DLL-5-ERR_ASIC_PARITY

5 FABRIC

INGRESSQ_DLL-5-ERR_ASIC_SBE

5 FABRIC

INGRESSQ_DLL-6BRM_BARRIER_SYNCED_UP

6 FABRIC

INGRESSQ_DLL-6-ERR_ASIC_GENERIC

6 FABRIC

INGRESSQ_DLL-6-ERR_ASIC_OOR

6 FABRIC

INGRESSQ_DLL-6-ERR_ASIC_OOR

6 FABRIC

INGRESSQ_DLL-6-ERR_ASIC_OOR

6 FABRIC

INGRESSQ_DLL-6-ERR_TX_CONN

6 FABRIC

INGRESSQ_DLL-6-HEALTH_MONITOR

6 FABRIC

INGRESSQ_DLL-6-HEALTH_MONITOR

6 FABRIC

INGRESSQ_DLL-6-INFO

6 FABRIC

INGRESSQ_DLL-6-INFO

6 FABRIC

INGRESSQ_DLL-6SEQ_STATE_THRESHOLD_EXCEEDED

6 FABRIC

INGRESSQ_DLL-6SEQ_STATE_THRESHOLD_EXCEEDED

6 FABRIC

INGRESSQ_DLL-6SEQ_STATE_THRESHOLD_EXCEEDED

6 FABRIC

INGRESSQ_DLL-6WDG_BARRIER_STALL_CLEARED

6 FABRIC

INGRESSQ_DLL-6WDG_BARRIER_STALL_CLEARED

6 FABRIC

INGRESSQ_DLL-6WDG_BARRIER_STALL_CLEARED

6 FABRIC

INGRESSQ_DLL-6-WDG_BARRIER_STALLED

6 FABRIC

INGRESSQ_DLL-6-WDG_BARRIER_STALLED

6 FABRIC

INGRESSQ_DLL-6-WDG_BARRIER_STALLED

6 FABRIC

INGRESSQ_DLL-7-ERR_REGISTER_GET

7 FABRIC

INGRESSQ_DLL-7-ERR_REGISTER_GET

7 FABRIC

INGRESSQ_DLL-7-ERR_REGISTER_GET

7 FABRIC

INGRESSQ_DLL-7-ERR_REGISTER_SET

7 FABRIC

INGRESSQ_DLL-7-ERR_REGISTER_SET

7 FABRIC

INGRESSQ_DLL-7-ERR_RES_PROG

7 FABRIC

INGRESSQ_DLL-7-ERR_RES_PROG

7 FABRIC

INGRESSQ_DLL-7-ERR_RES_PROG

7 FABRIC

INGRESSQ_LIB-7-ERR_LWM_SEND

7 FABRIC

INGRESSQ-2-ASIC_RESET_FAILED

2 FABRIC

INGRESSQ-3-ERR_INIT

3 FABRIC

INGRESSQ-3-ERR_MEM_ALLOC

3 FABRIC

INGRESSQ-3-ERR_UNKNOWN_EVENT

3 FABRIC

INGRESSQ-3-GENERAL_ERROR

3 FABRIC

INGRESSQ-3-IMDR_ABORT

3 FABRIC

INGRESSQ-3-IMDR_CONN_ERROR

3 FABRIC

INGRESSQ-3-IMDR_EOC_ERROR

3 FABRIC

INGRESSQ-3-INVALID_PARAM

3 FABRIC

INGRESSQ-4-ERR_CHKPT_INIT

4 FABRIC

INGRESSQ-4-WARN_INIT

4 FABRIC

INGRESSQ-6-LINK_DOWN

6 FABRIC

INGRESSQ-7-ERR_BAG_REG

7 FABRIC

INGRESSQ-7-ERR_CHKPT_DELETE

7 FABRIC

INGRESSQ-7-ERR_CHKPT_INSERT

7 FABRIC

INGRESSQ-7-ERR_CLIENT_REG

7 FABRIC

INGRESSQ-7-ERR_DLL_REG

7 FABRIC

INGRESSQ-7-ERR_EVM_CREATE

7 FABRIC

INGRESSQ-7-ERR_EVM_NOTIFY

7 FABRIC

INGRESSQ-7-ERR_LWM_CREATE

7 FABRIC

INGRESSQ-7-ERR_LWM_EVENT_BLOCK

7 FABRIC

INGRESSQ-7-ERR_LWM_REPLY

7 FABRIC

INGRESSQ-7-ERR_RES_PROG

7 FABRIC

INGRESSQ-7-ERR_SYSDB_BIND

7 FABRIC

INGRESSQ-7-ERR_SYSDB_EDM_REG

7 FABRIC

INGRESSQ-7-ERR_SYSDB_REG_VERIFY

7 FABRIC

INGRESSQ-7-ERR_SYSDB_SET

7 FABRIC

AIB_NETIO-3-GET_EVM

3 FORWARDING

AIB_NETIO-3-UIDB_BIND

3 FORWARDING

EDGE_BOOSTER-0-SHM_ALLOC

--

FORWARDING

EDGE_BOOSTER-0-SHM_FREE

--

FORWARDING

EDGE_BOOSTER-0-SHM_PLAT_INFO

--

FORWARDING

EDGE_BOOSTER-3-ADJ_ALLOC

3 FORWARDING

EDGE_BOOSTER-3-ARG

3 FORWARDING

EDGE_BOOSTER-3-BAG_REG

3 FORWARDING

EDGE_BOOSTER-3-BASE_ADDR

3 FORWARDING

EDGE_BOOSTER-3-BITMAP_ALLOC

3 FORWARDING

EDGE_BOOSTER-3-GET_SHM_HEADER

3 FORWARDING

EDGE_BOOSTER-3-INDEX

3 FORWARDING

EDGE_BOOSTER-3-MNODE_ALLOC

3 FORWARDING

EDGE_BOOSTER-3-MNODE_DEL

3 FORWARDING

EDGE_BOOSTER-3-NULL

3 FORWARDING

EDGE_BOOSTER-3-PCI_READ_BURST

3 FORWARDING

EDGE_BOOSTER-3-PCI_WRITE

3 FORWARDING

EDGE_BOOSTER-3-PCI_WRITE_BURST

3 FORWARDING

EDGE_BOOSTER-3-RM_ADJ_ALLOC

3 FORWARDING

EDGE_BOOSTER-3-RM_LSPA_ALLOC

3 FORWARDING

EDGE_BOOSTER-3-SYSDB_BIND

3 FORWARDING

EDGE_BOOSTER-3-SYSDB_CLEAR_COUNTER

3 FORWARDING

EDGE_BOOSTER-3-SYSDB_COID

3 FORWARDING

EDGE_BOOSTER-3-SYSDB_CONN

3 FORWARDING

EDGE_BOOSTER-3-SYSDB_REG

3 FORWARDING

EDGE_BOOSTER-3-TBM_NODE

3 FORWARDING

EDGE_BOOSTER-3-UTIL_ASSERT

3 FORWARDING

EDGE_FIB_IP-3-UTIL_ASSERT

3 FORWARDING

EDGE_MPLS_HW_DRIVER-3-UTIL_ASSERT

3 FORWARDING

FWD_EDGE_ADJ-2-EDGE_ADJ_ERR

2 FORWARDING

FWD_EDGE_ADJ-3-UTIL_ASSERT

3 FORWARDING

FWD_HAL-2-ACCESSOR

2 FORWARDING

FWD_HAL-2-ADJ_ERR

2 FORWARDING

FWD_HAL-2-BACKWALK_ERR

2 FORWARDING

FWD_HAL-2-ECD_ERR

2 FORWARDING

FWD_HAL-2-ECD_TRKR_ERR

2 FORWARDING

FWD_HAL-2-FASTCONV_CLI_ERR

2 FORWARDING

FWD_HAL-2-FRR_OBJECT_FAIL

2 FORWARDING

FWD_HAL-2-HASH_INDEX

2 FORWARDING

FWD_HAL-2-IDB_ERR

2 FORWARDING

FWD_HAL-2-INIT

2 FORWARDING

FWD_HAL-2-INVALID_PARENT_OBJ

2 FORWARDING

FWD_HAL-2-LDI_ERR

2 FORWARDING

FWD_HAL-2-LI_ERR

2 FORWARDING

FWD_HAL-2-LOCAL_PATH

2 FORWARDING

FWD_HAL-2-MTRIE_MODE_CLI_ERR

2 FORWARDING

FWD_HAL-2-PAK_NETIO_WRITE

2 FORWARDING

FWD_HAL-2-PAK_OFFSET

2 FORWARDING

FWD_HAL-2-PBTS_NULL_LDI

2 FORWARDING

FWD_HAL-2-PFX_ERR

2 FORWARDING

FWD_HAL-2-SHMWIN_ERR

2 FORWARDING

FWD_HAL-2-STATS_INTF_REGISTER

2 FORWARDING

FWD_HAL-2-STATS_INTF_UNREGISTER

2 FORWARDING

FWD_HAL-2-STATS_VALIDATION

2 FORWARDING

FWD_HAL-2-TUNNEL_NH_ERR

2 FORWARDING

FWD_HAL-2-TX_NULL

2 FORWARDING

FWD_HAL-2-TX_PATH_MAP

2 FORWARDING

FWD_HAL-2-UNSUPT_TERMINATE

2 FORWARDING

FWD_HAL-2USED_BY_BGP_STATUS_CHANGE

2 FORWARDING

FWD_HAL-3-FILE_OPEN

3 FORWARDING

FWD_HAL-3-FILL_INFO

3 FORWARDING

FWD_HAL-3-GET_CTX

3 FORWARDING

FWD_HAL-3-GET_PREFIX_DATA

3 FORWARDING

FWD_HAL-3-LI_TYPE

3 FORWARDING

FWD_HAL-3-MALLOC

3 FORWARDING

FWD_HAL-3-MPI_PTR

3 FORWARDING

FWD_HAL-3-NH_SHM_INIT

3 FORWARDING

FWD_HAL-3-NH_SHM_MALLOC

3 FORWARDING

FWD_HAL-3-NODEID_SLOT

3 FORWARDING

FWD_HAL-3-NULL

3 FORWARDING

FWD_HAL-3-PARENT_OBJ_TYPE

3 FORWARDING

FWD_HAL-3-PM_ERR

3 FORWARDING

FWD_HAL-3-PP_NFN_LIB_GET_INFO

3 FORWARDING

FWD_HAL-3-PP_NFN_MSG_HDLR

3 FORWARDING

FWD_HAL-3-SHM_FREE

3 FORWARDING

FWD_HAL-3-SHM_INIT

3 FORWARDING

FWD_HAL-3-SHM_MALLOC

3 FORWARDING

FWD_HAL-3-SHM_POOL_CREATE

3 FORWARDING

FWD_HAL-6CHANGE_MTRIE_MODE_CLI_INFO

6 FORWARDING

FWD_HAL-6-FASTCONVERGENCE_CLI_INFO

6 FORWARDING

FWD_HAL-6-PD_UPDATE_TXLIST

6 FORWARDING

FWD_HAL-7-HW_OCE_NULL

7 FORWARDING

FWD_L2HAL-2-ACCESSOR

2 FORWARDING

FWD_L2HAL-2-ACTION_FAILED

2 FORWARDING

FWD_L2HAL-2-BACKWALK_ERR

2 FORWARDING

FWD_L2HAL-2-CONFIG_NOT_SUPPORTED

2 FORWARDING

FWD_L2HAL-2-CONFIG_NOT_VALID

2 FORWARDING

FWD_L2HAL-2-HW_OCE_NULL

2 FORWARDING

FWD_L2HAL-2-INIT

2 FORWARDING

FWD_L2HAL-2-INVALID_PARENT_OBJ

2 FORWARDING

FWD_L2HAL-2-MQOS

2 FORWARDING

FWD_L2HAL-2-SHMWIN_ERR

2 FORWARDING

FWD_L2HAL-6-DUPLICATE_BIND

6 FORWARDING

FWD_L2HAL-6-INIT_RETRY

6 FORWARDING

GSR_AIB-3-PRINT_FUNC

3 FORWARDING

HAL_PDFIB-3-PCI_LIB_INIT

3 FORWARDING

HAL_PDFIB-4-PD_UPDATE_IFH

4 FORWARDING

HAL_PDFIB-6-PD_UPDATE

6 FORWARDING

IP_TUNNEL_MA_LTRACE-7-INIT

7 FORWARDING

IP_TUNNEL-3-BW_NOTIFY

3 FORWARDING

IP_TUNNEL-3-CHKPT

3 FORWARDING

IP_TUNNEL-3-DB_ADD

3 FORWARDING

IP_TUNNEL-3-DEST_LOCAL

3 FORWARDING

IP_TUNNEL-3-DEST_TUNL

3 FORWARDING

IP_TUNNEL-3-DLL_INIT

3 FORWARDING

IP_TUNNEL-3-EA_NOMEM

3 FORWARDING

IP_TUNNEL-3-EA_RETRY_FAILED

3 FORWARDING

IP_TUNNEL-3-EAIDB

3 FORWARDING

IP_TUNNEL-3-EAINIT

3 FORWARDING

IP_TUNNEL-3-ENS_READ

3 FORWARDING

IP_TUNNEL-3-EVENTMGR

3 FORWARDING

IP_TUNNEL-3-FEA

3 FORWARDING

IP_TUNNEL-3-IF_CREATE

3 FORWARDING

IP_TUNNEL-3-IF_DELETE

3 FORWARDING

IP_TUNNEL-3-IMPSERVER

3 FORWARDING

IP_TUNNEL-3-IPT_DEBUG

3 FORWARDING

IP_TUNNEL-3-KA_CFG_ENQUEUE

3 FORWARDING

IP_TUNNEL-3-KA_ERR

3 FORWARDING

IP_TUNNEL-3-MA_NOMEM

3 FORWARDING

IP_TUNNEL-3-MA_STATE

3 FORWARDING

IP_TUNNEL-3-MA_STATE_BULK

3 FORWARDING

IP_TUNNEL-3-MAINIT

3 FORWARDING

IP_TUNNEL-3-MEM

3 FORWARDING

IP_TUNNEL-3-NETIOIDB

3 FORWARDING

IP_TUNNEL-3-P2MP_TUNNEL

3 FORWARDING

IP_TUNNEL-3-SRC_DST_CONFLICT

3 FORWARDING

IP_TUNNEL-4-DECAP

4 FORWARDING

IP_TUNNEL-4-EA_INIT

4 FORWARDING

IP_TUNNEL-4-EA_RETRY

4 FORWARDING

IP_TUNNEL-4-ENCAP

4 FORWARDING

IP_TUNNEL-4-FIB_CONNECTION

4 FORWARDING

IP_TUNNEL-4-INIT

4 FORWARDING

IP_TUNNEL-5-EA_SHM_RESET

5 FORWARDING

IPT_EA_LTRACE-3-INIT

3 FORWARDING

PBR-3-EA_ALLOC

3 FORWARDING

PBR-3-EA_DROP

3 FORWARDING

PBR-3-EA_EVM

3 FORWARDING

PBR-3-EA_INIT

3 FORWARDING

PBR-3-EA_SHUTDOWN

3 FORWARDING

PBR-3-MA_ALLOC

3 FORWARDING

PBR-3-MA_EVM

3 FORWARDING

PBR-3-MA_INIT

3 FORWARDING

PBR-3-MA_SHUTDOWN

3 FORWARDING

CDM_CLI-7-BAD_BUFFER

7 HA

CDM_CLI-7-BUFFER_MISMATCH

7 HA

CDM_CLI-7-INVALID_ARG

7 HA

CDM_MEMMGR_HEAP-7-BAD_HEAPIDX

7 HA

CDM_MEMMGR_HEAP-7-BAD_HEAPPAGE

7 HA

CDM_MEMMGR_HEAP-7-BAD_HEAPPTR

7 HA

CDM_MEMMGR_HEAP-7-BAD_NCTDELETE

7 HA

CDM_MEMMGR_HEAP-7-CORRUPTION

7 HA

CDM_MEMMGR_HEAP-7-DATA_CORRUPTION

7 HA

CDM_MEMMGR_HEAP-7-MUNMAP

7 HA

CDM_MEMMGR_HEAP-7-NCT_BIGNEW

7 HA

CDM_MEMMGR_HEAP-7-OBJ_NOT_FOUND

7 HA

CDM_MEMMGR_HEAP-7-PROC_RUNNING

7 HA

CDM_MEMMGR_HEAP-7SEGMENT_RENAMED

7 HA

CDM_MEMMGR_HEAP-7TBL_OBJ_SEG_MISMATCH

7 HA

CDM_MEMMGR_UTIL-3-ASSERT_MSG

3 HA

CDM_MEMMGR_UTIL-3-MQ_OPEN

3 HA

CDM_MEMMGR_UTIL-3-MQ_SEND

3 HA

CDM_MEMMGR_UTIL-5-LTRACE_INIT2

5 HA

CDM_MEMMGR_UTIL-7-COLD_RESTART

7 HA

CDM_MEMMGR_UTIL-7COLD_RESTART_IGNORED

7 HA

CDM_MEMMGR_UTIL-7-DEBUG_REGISTER

7 HA

CDM_MEMMGR_UTIL-7-DUP_KEY

7 HA

CDM_MEMMGR_UTIL-7-INIT_ERROR

7 HA

CDM_MEMMGR_UTIL-7-NOT_IMPLEMENTED

7 HA

CDM_MEMMGR_UTIL-7-REGISTRATION

7 HA

CDM_MEMMGR_UTIL-7-SYSERR

7 HA

CDM_MEMMGR_UTIL-7-UNEXPECTED

7 HA

CDM_MEMMGR_UTIL-7-WARNING

7 HA

CDM_TDM-7-BAD_ALIGNMENT

7 HA

CDM_TDM-7-COLD_RESTART

7 HA

CDM_TDM-7-DUP_TABLE

7 HA

CDM_TDM-7-NO_TRANSLATOR

7 HA

CDM_TDM-7-NOT_INDEXED

7 HA

CDM_TDM-7-OBJ_COUNT

7 HA

CDM_TDM-7-OBJ_LEN

7 HA

CDM_TDM-7-REG_MISMATCH

7 HA

CDM_TDM-7-TRANSLATION_FATAL

7 HA

CHKPT_BASIC-3-ASSERT_MSG

3 HA

CHKPT_BASIC-3-SHM_SEGMENTS

3 HA

CHKPT_BASIC-5-LTRACE_INIT2

5 HA

CHKPT_BASIC-6-MUTEX_DESTROY

6 HA

CHKPT_BASIC-7-COLD_RESTART

7 HA

CHKPT_BASIC-7-COLD_RESTART_IGNORED

7 HA

CHKPT_BASIC-7-DEBUG_REGISTER

7 HA

CHKPT_BASIC-7-DUP_KEY

7 HA

CHKPT_BASIC-7-INCONSISTENT_VERSIONS

7 HA

CHKPT_BASIC-7-INIT_ERROR

7 HA

CHKPT_BASIC-7-NOT_IMPLEMENTED

7 HA

CHKPT_BASIC-7-RAW_SEGMENTS

7 HA

CHKPT_BASIC-7-REGISTRATION

7 HA

CHKPT_BASIC-7-REMOVING_SHM

7 HA

CHKPT_BASIC-7-REUSING_SHM

7 HA

CHKPT_BASIC-7-SYSERR

7 HA

CHKPT_BASIC-7-UNEXPECTED

7 HA

CHKPT_BASIC-7-WARNING

7 HA

CHKPT_CLI-7-BAD_BUFFER

7 HA

CHKPT_CLI-7-BUFFER_MISMATCH

7 HA

CHKPT_CLI-7-INVALID_ARG

7 HA

CHKPT_CLIENT-3-CONFLICT_ISSU_FLAG

3 HA

CHKPT_CLIENT-3-DLL_NOT_PROVIDED

3 HA

CHKPT_CLIENT-7CALLBACK_NOT_REQUIRED

7 HA

CHKPT_HEAP-7-BAD_HEAPIDX

7 HA

CHKPT_HEAP-7-BAD_HEAPPAGE

7 HA

CHKPT_HEAP-7-BAD_HEAPPTR

7 HA

CHKPT_HEAP-7-BAD_NCTDELETE

7 HA

CHKPT_HEAP-7-CORRUPTION

7 HA

CHKPT_HEAP-7-DATA_CORRUPTION

7 HA

CHKPT_HEAP-7-MUNMAP

7 HA

CHKPT_HEAP-7-NCT_BIGNEW

7 HA

CHKPT_HEAP-7-OBJ_NOT_FOUND

7 HA

CHKPT_HEAP-7-PROC_RUNNING

7 HA

CHKPT_HEAP-7-SEGMENT_RENAMED

7 HA

CHKPT_HEAP-7-TBL_OBJ_SEG_MISMATCH

7 HA

CHKPT_LIB_COMMS-3-SYSTEM_ERROR
CHKPT_LIB_COMMS-6-INFO
CHKPT_LIB_COMMS-7-DEBUG

3 HA
6 HA
7 HA

CHKPT_MESSAGING-3-COMMS_INIT_FAIL

3 HA

CHKPT_MESSAGING-3-IDT_FAILED

3 HA

CHKPT_MESSAGING-7-BAD_MSGLEN

7 HA

CHKPT_MESSAGING-7-BAD_MSGTYPE

7 HA

CHKPT_MESSAGING-7-BAD_REQUEST

7 HA

CHKPT_MESSAGING-7-BAD_SEQNO

7 HA

CHKPT_MESSAGING-7-BAD_TOTALSIZE

7 HA

CHKPT_MESSAGING-7-BUFFER_TOO_SMALL

7 HA

CHKPT_MESSAGING-7-DUPLICATE_PROCESS

7 HA

CHKPT_MESSAGING-7-EVENT_MANAGER

7 HA

CHKPT_MESSAGING-7EVENT_MANAGER_CHANNEL

7 HA

CHKPT_MESSAGING-7-GET_MSGLEN

7 HA

CHKPT_MESSAGING-7-IDT_ALL_FAILED

7 HA

CHKPT_MESSAGING-7-IDT_DIFF_NODE_TYPE

7 HA

CHKPT_MESSAGING-7IDT_XFORM_COMPLETED

7 HA

CHKPT_MESSAGING-7-LWM_FAILURE

7 HA

CHKPT_MESSAGING-7-MALLOC_FAILED

7 HA

CHKPT_MESSAGING-7-MSG_READ

7 HA

CHKPT_MESSAGING-7-MSG_REPLY

7 HA

CHKPT_MESSAGING-7-MSG_SEND_EVENT

7 HA

CHKPT_MESSAGING-7-NON_CHKPT_MSG

7 HA

CHKPT_MESSAGING-7-PTHREAD_FAILURE

7 HA

CHKPT_MESSAGING-7-REPLICA_NAME

7 HA

CHKPT_MESSAGING-7STANDBY_OPEN_TIMEOUT

7 HA

CHKPT_MESSAGING-7STANDBY_PROXY_SPAWN

7 HA

CHKPT_MESSAGING-7-STBY_CAPABLE

7 HA

CHKPT_MESSAGING-7SYSMGR_GET_PROC_ROLE

7 HA

CHKPT_MESSAGING-7-X86_XFORM_AFTER

7 HA

CHKPT_MESSAGING-7-X86_XFORM_BEFORE

7 HA

CHKPT_MESSAGING-7-X86_XFORM_DBG

7 HA

CHKPT_PROXY-7-BAD_IPC_LENGTH

7 HA

CHKPT_PROXY-7-BAD_IPC_REQUEST

7 HA

CHKPT_PROXY-7-DEBUG

7 HA

CHKPT_PROXY-7-GROUP_CREATE_ERROR

7 HA

CHKPT_PROXY-7-IPC_ERROR

7 HA

CHKPT_PROXY-7-NO_MEMORY

7 HA

CHKPT_PROXY-7-PUTENV

7 HA

CHKPT_PROXY-7-STDBY_NOPROXY

7 HA

CHKPT_PROXY-7-SYSTEM_ERROR

7 HA

CHKPT_TDM-4-OOS

4 HA

CHKPT_TDM-7-BAD_ALIGNMENT

7 HA

CHKPT_TDM-7-COLD_RESTART

7 HA

CHKPT_TDM-7-DUP_TABLE

7 HA

CHKPT_TDM-7-NATIVE_VERSION

7 HA

CHKPT_TDM-7-NO_TRANSLATOR

7 HA

CHKPT_TDM-7-NOT_INDEXED

7 HA

CHKPT_TDM-7-OBJ_COUNT

7 HA

CHKPT_TDM-7-OBJ_LEN

7 HA

CHKPT_TDM-7-REG_MISMATCH

7 HA

CHKPT_TDM-7-TRANSLATION_FATAL

7 HA

DCL_LIB-2-NULL_PTR

2 HA

DCL_LIB-4-CERR_REGISTER

4 HA

DCL_LIB-4-NONFATAL_INTERNAL

4 HA

DCL_LIB-4-UNEXPECTED

4 HA

HA_EEM-0-ACTION_SYSLOG_LOG_EMERG

--

HA

HA_EEM-1-ACTION_SYSLOG_LOG_ALERT

1 HA

HA_EEM-2-ACTION_SYSLOG_LOG_CRIT

2 HA

HA_EEM-3-ACTION_SYSLOG_LOG_ERR

3 HA

HA_EEM-4-ACTION_SYSLOG_LOG_WARNING

4 HA

HA_EEM-5-ACTION_SYSLOG_LOG_NOTICE

5 HA

HA_EEM-6-ACTION_SYSLOG_LOG_INFO

6 HA

HA_EEM-7-ACTION_SYSLOG_LOG_DEBUG

7 HA

HA_EM-7-EEMED_EA_ATTACH

7 HA

HA_EM-7-EEMED_EA_ATTACH

7 HA

HA_EM-7-EEMED_EI_EVENT

7 HA

HA_EM-7-EEMED_EI_EVENT

7 HA

HA_EM-7-EEMED_EM_ATTACH

7 HA

HA_EM-7-EEMED_EM_ATTACH

7 HA

HA_EM-7-EEMED_EVM_CREATE

7 HA

HA_EM-7-EEMED_EVM_CREATE

7 HA

HA_EM-7-EEMED_EVM_EVENT_BLOCK

7 HA

HA_EM-7-EEMED_EVM_EVENT_BLOCK

7 HA

HA_EM-7-EEMS_FILE_OPEN

7 HA

HA_EM-7-EEMS_GET_CHAN_CHAN

7 HA

HA_EM-7-EEMS_GUARD_WORD_VER

7 HA

HA_EM-7-EEMS_MEM_ALLOC

7 HA

HA_EM-7-FMS_ASYNC_ATTACH_FD

7 HA

HA_EM-7-FMS_EVM_FILE_ATTACH

7 HA

HA_EM-7-FMS_EVM_INIT_EVENT

7 HA

HA_EM-7-FMS_LWM_ATTACH

7 HA

HA_EM-7-FMS_LWM_ATTACH_SYNC

7 HA

HA_EM-7-FMS_LWM_CONNECT

7 HA

HA_EM-7-FMS_LWM_DISCONNECT

7 HA

HA_EM-7-FMS_LWM_SEND

7 HA

HA_EM-7-FMS_LWM_SEND_ASYNC

7 HA

HA_EM-7-FMS_LWM_SEND_EVENT

7 HA

HA_EM-7-FMS_QSM_REG_NOTIF

7 HA

HA_SS-7-DEBUG

7 HA

HA_WD_LIB-3-DEBUG_REGISTER_FAIL

3 HA

HA_WD_LIB-3-DEBUG_REGISTER_FAIL

3 HA

HA_WD_LIB-7-CLIENT_MONITOR

7 HA

HA_WD_LIB-7-CLIENT_MONITOR

7 HA

HA_WD_LIB-7-CLIENT_UNMONITOR

7 HA

HA_WD_LIB-7-CLIENT_UNMONITOR

7 HA

HA_WD_LIB-7-INVALID_ARG

7 HA

HA_WD_LIB-7-INVALID_ARG

7 HA

HA_WD_LIB-7-MISSING_CTX

7 HA

HA_WD_LIB-7-MISSING_CTX

7 HA

HA_WD_LIB-7-NO_MEM

7 HA

HA_WD_LIB-7-NO_MEM

7 HA

HA_WD_LIB-7-SVR_MEMINFO

7 HA

HA_WD_LIB-7-SVR_MEMINFO

7 HA

HA_WD_LIB-7-SVR_REG

7 HA

HA_WD_LIB-7-SVR_REG

7 HA

HA_WD_LIB-7-SVR_RSC_UNREG

7 HA

HA_WD_LIB-7-SVR_RSC_UNREG

7 HA

HA_WD_LIB-7-SVR_UNREG

7 HA

HA_WD_LIB-7-SVR_UNREG

7 HA

HA_WD_LIB-7-SYSCALL

7 HA

HA_WD_LIB-7-SYSCALL

7 HA

HA_WD_LIB-7-THREAD_CTX_INIT

7 HA

HA_WD_LIB-7-THREAD_CTX_INIT

7 HA

HA_WD-1-ABORTING

1 HA

HA_WD-1-ABORTING

1 HA

HA_WD-1-CPU_HOG_5

1 HA

HA_WD-1-CPU_HOG_5

1 HA

HA_WD-1-CPU_HOG_ALERT

1 HA

HA_WD-1-CPU_HOG_ALERT

1 HA

HA_WD-1-CURRENT_STATE

1 HA

HA_WD-1-CURRENT_STATE

1 HA

HA_WD-1-DISK_ALERT

1 HA

HA_WD-1-DISK_ALERT

1 HA

HA_WD-2-DISK_CRIT

2 HA

HA_WD-2-DISK_CRIT

2 HA

HA_WD-3-DEBUG_REGISTER_FAIL

3 HA

HA_WD-3-DEBUG_REGISTER_FAIL

3 HA

HA_WD-3-DEVCTL

3 HA

HA_WD-3-DEVCTL

3 HA

HA_WD-3-EVM_ASYNC_ATTACH

3 HA

HA_WD-3-EVM_ASYNC_ATTACH

3 HA

HA_WD-3-EVM_CREATE

3 HA

HA_WD-3-EVM_CREATE

3 HA

HA_WD-3-EVM_EVENT_BLOCK

3 HA

HA_WD-3-EVM_EVENT_BLOCK

3 HA

HA_WD-3-EVM_INIT_EVENT

3 HA

HA_WD-3-EVM_INIT_EVENT

3 HA

HA_WD-3-EVM_MSG_ATTACH

3 HA

HA_WD-3-EVM_MSG_ATTACH

3 HA

HA_WD-3-EVM_THREAD_INIT

3 HA

HA_WD-3-EVM_THREAD_INIT

3 HA

HA_WD-3-EVM_TM_ATTACH

3 HA

HA_WD-3-EVM_TM_ATTACH

3 HA

HA_WD-3-EVM_TM_DETACH

3 HA

HA_WD-3-EVM_TM_DETACH

3 HA

HA_WD-3-EVM_TM_LEAF_NEW

3 HA

HA_WD-3-EVM_TM_LEAF_NEW

3 HA

HA_WD-3-FD_CRIT_LIM

3 HA

HA_WD-3-FD_CRIT_LIM

3 HA

HA_WD-3-FD_INIT

3 HA

HA_WD-3-FD_INIT

3 HA

HA_WD-3-FREE_MEM_ADDR

3 HA

HA_WD-3-FREE_MEM_ADDR

3 HA

HA_WD-3-HELPER_INIT_FAIL

3 HA

HA_WD-3-HELPER_INIT_FAIL

3 HA

HA_WD-3-MSG_GET_CHAN_CHAN

3 HA

HA_WD-3-MSG_GET_CHAN_CHAN

3 HA

HA_WD-3-NOTIF_THREAD_INIT

3 HA

HA_WD-3-NOTIF_THREAD_INIT

3 HA

HA_WD-3-OPEN_PROCFS

3 HA

HA_WD-3-OPEN_PROCFS

3 HA

HA_WD-3-PLATFORM_NODENAME

3 HA

HA_WD-3-PLATFORM_NODENAME

3 HA

HA_WD-3-PLATFORM_SLOT

3 HA

HA_WD-3-PLATFORM_SLOT

3 HA

HA_WD-3-POP

3 HA

HA_WD-3-POP

3 HA

HA_WD-3-PTHRD_CREATE

3 HA

HA_WD-3-PTHRD_CREATE

3 HA

HA_WD-3-SERVICE_CREATE

3 HA

HA_WD-3-SERVICE_CREATE

3 HA

HA_WD-3-WATCHER_THREAD_INIT

3 HA

HA_WD-3-WATCHER_THREAD_INIT

3 HA

HA_WD-4-CFG_FAILED

4 HA

HA_WD-4-CFG_FAILED

4 HA

HA_WD-4-DISK_ALARM

4 HA

HA_WD-4-DISK_ALARM

4 HA

HA_WD-4-DISK_WARN

4 HA

HA_WD-4-DISK_WARN

4 HA

HA_WD-4-DSC_REG_FAILED

4 HA

HA_WD-4-DSC_REG_FAILED

4 HA

HA_WD-4-FD_MAJ_LIM

4 HA

HA_WD-4-FD_MAJ_LIM

4 HA

HA_WD-4-FD_MIN_LIM

4 HA

HA_WD-4-FD_MIN_LIM

4 HA

HA_WD-4-FD_NORMAL_LIM

4 HA

HA_WD-4-FD_NORMAL_LIM

4 HA

HA_WD-4-MEM_POLL

4 HA

HA_WD-4-MEM_POLL

4 HA

HA_WD-4-MEMORY_ALARM

4 HA

HA_WD-4-MEMORY_ALARM

4 HA

HA_WD-4-MEMORY_LIMIT_EXCEEDED

4 HA

HA_WD-4-MEMORY_LIMIT_EXCEEDED

4 HA

HA_WD-4-MEMORY_STATE_CHANGE

4 HA

HA_WD-4-MEMORY_STATE_CHANGE

4 HA

HA_WD-4-TOP_MEMORY_USER_WARNING

4 HA

HA_WD-4-TOP_MEMORY_USER_WARNING

4 HA

HA_WD-4-TOP_MEMORY_USERS_WARNING

4 HA

HA_WD-4-TOP_MEMORY_USERS_WARNING

4 HA

HA_WD-4-TOP_SHMEM_USER_WARNING

4 HA

HA_WD-4-TOP_SHMEM_USER_WARNING

4 HA

HA_WD-4-TOP_SHMEM_USERS_WARNING

4 HA

HA_WD-4-TOP_SHMEM_USERS_WARNING

4 HA

HA_WD-5-NO_TIMEOUT

5 HA

HA_WD-5-NO_TIMEOUT

5 HA

HA_WD-5-SYSCALL

5 HA

HA_WD-5-TIMEOUT

5 HA

HA_WD-5-TIMEOUT

5 HA

HA_WD-5-TIMEOUT_CANCELLED

5 HA

HA_WD-5-TIMEOUT_CANCELLED

5 HA

HA_WD-5-TIMEOUT_EXIT

5 HA

HA_WD-5-TIMEOUT_EXIT

5 HA

HA_WD-6-CPU_HOG_1

6 HA

HA_WD-6-CPU_HOG_1

6 HA

HA_WD-6-CPU_HOG_2

6 HA

HA_WD-6-CPU_HOG_2

6 HA

HA_WD-6-CPU_HOG_3

6 HA

HA_WD-6-CPU_HOG_3

6 HA

HA_WD-6-CPU_HOG_4

6 HA

HA_WD-6-CPU_HOG_4

6 HA

HA_WD-6-DISK_NORMAL

6 HA

HA_WD-6-DISK_NORMAL

6 HA

HA_WD-6-DISK_UNMONITOR

6 HA

HA_WD-6-DISK_UNMONITOR

6 HA

HA_WD-6-GI_FILES_CREATED

6 HA

HA_WD-6-GI_FILES_CREATED

6 HA

HA_WD-6-IN_DEP_LIST

6 HA

HA_WD-6-IN_DEP_LIST

6 HA

HA_WD-6-KNOWN_HOG

6 HA

HA_WD-6-KNOWN_HOG

6 HA

HA_WD-6-MEMORY_RECOVERY_DISABLED

6 HA

HA_WD-6-MEMORY_RECOVERY_DISABLED

6 HA

HA_WD-6MEMORY_RECOVERY_KILL_NON_PROCESSM
GR

6 HA

HA_WD-6MEMORY_RECOVERY_KILL_NON_SYSMGR

6 HA

HA_WD-6MEMORY_RECOVERY_KILL_PROCESSMGR

6 HA

HA_WD-6MEMORY_RECOVERY_KILL_SYSMGR

6 HA

HA_WD-6-MEMORY_RECOVERY_RESTART

6 HA

HA_WD-6-MEMORY_RECOVERY_RESTART

6 HA

HA_WD-6-PROC_KILL_DISABLED

6 HA

HA_WD-6-PROC_KILL_DISABLED

6 HA

HA_WD-6-TOP_MEMORY_USER_INFO

6 HA

HA_WD-6-TOP_MEMORY_USER_INFO

6 HA

HA_WD-6-TOP_MEMORY_USERS_INFO

6 HA

HA_WD-6-TOP_MEMORY_USERS_INFO

6 HA

HA_WD-6-TOP_SHMEM_USER_INFO

6 HA

HA_WD-6-TOP_SHMEM_USER_INFO

6 HA

HA_WD-6-TOP_SHMEM_USERS_INFO

6 HA

HA_WD-6-TOP_SHMEM_USERS_INFO

6 HA

HA_WD-7-CISCOSHMEM

7 HA

HA_WD-7-CISCOSHMEM

7 HA

HA_WD-7-CLINFO_GET_DATUM

7 HA

HA_WD-7-CLINFO_GET_DATUM

7 HA

HA_WD-7-CLINFO_M_PID

7 HA

HA_WD-7-CLINFO_M_PID

7 HA

HA_WD-7-CLINFO_SAVE_DATUM

7 HA

HA_WD-7-CLINFO_SAVE_DATUM

7 HA

HA_WD-7-CLINFO_UNHOLD

7 HA

HA_WD-7-CLINFO_UNHOLD

7 HA

HA_WD-7-CONTEXT_CREATE

7 HA

HA_WD-7-CONTEXT_CREATE

7 HA

HA_WD-7-GET_EVM_CTX_BY_TIMER

7 HA

HA_WD-7-GET_EVM_CTX_BY_TIMER

7 HA

HA_WD-7-MSG_CHAN_CONNECT

7 HA

HA_WD-7-MSG_CHAN_CONNECT

7 HA

HA_WD-7-MSG_CHAN_DISCONN

7 HA

HA_WD-7-MSG_CHAN_DISCONN

7 HA

HA_WD-7-MSG_SEND

7 HA

HA_WD-7-MSG_SEND

7 HA

HA_WD-7-MSG_SEND_EVENT

7 HA

HA_WD-7-MSG_SEND_EVENT

7 HA

HA_WD-7-MSG_TYPE

7 HA

HA_WD-7-MSG_TYPE

7 HA

HA_WD-7-NO_MEM

7 HA

HA_WD-7-NO_MEM

7 HA

HA_WD-7-SCHED_GET_PRIORITY_MAX

7 HA

HA_WD-7-SCHED_GET_PRIORITY_MAX

7 HA

HA_WD-7-SCHED_SETSCHEDULER

7 HA

HA_WD-7-SCHED_SETSCHEDULER

7 HA

HA_WD-7-SYSCALL

7 HA

HA_WD-7-UNEXPECTED

7 HA

HA_WD-7-UNEXPECTED

7 HA

HM-3-FPING_FAILED

3 HA

HM-3-FPING_MISMATCH

3 HA

HM-4-FAILED_INIT

4 HA

HM-4-FPING_INCOMPLETE

4 HA

HM-4-FPING_RETRY_FAILED

4 HA

IRM_CHKPT-7-INIT_ERROR

7 HA

LRD_inv-3-BAG_REGISTRATION

3 HA

LRD_inv-3-BAG_REGISTRATION

3 HA

LRD_inv-3-MEM_ALLOC_FAIL

3 HA

LRD_inv-3-MEM_ALLOC_FAIL

3 HA

LRD_inv-3-MEM_ALLOC_FAIL

3 HA

LRD_inv-3-MEM_ALLOC_FAIL

3 HA

LRD_inv-3-MLR_CONF_INFO

3 HA

LRD_inv-3-MSG_CERR_REGISTER_DLL

3 HA

LRD_inv-3-MSG_CERR_REGISTER_DLL

3 HA

LRD_inv-3-MSG_CERR_REGISTER_DLL

3 HA

LRD_inv-3-MSG_CERR_REGISTER_DLL

3 HA

LRD_inv-3-MSG_INVENTORY_FWD

3 HA

LRD_inv-3-MSG_INVENTORY_FWD

3 HA

LRD_inv-3-REDUNDANCY_STATE

3 HA

LRD_inv-3-REDUNDANCY_STATE

3 HA

LRD_inv-3-SYSDB_ITEM_ERROR

3 HA

LRD_inv-3-SYSDB_ITEM_ERROR

3 HA

LRD_inv-4-CANT_FIND_DSC

4 HA

LRD_inv-4-CANT_FIND_DSC

4 HA

LRD_inv-4-UNEXPECTED

4 HA

LRD_inv-4-UNEXPECTED

4 HA

LRD_inv-4-UNEXPECTED

4 HA

LRD_inv-4-UNEXPECTED

4 HA

LRD_inv-6-NON_DRP_PRIMARY

6 HA

LRD_inv-6-RESET_CARD_FOR_PAIRING

6 HA

LRD_inv-6-RESET_CARD_FOR_PAIRING

6 HA

LRD_inv-6-RESET_CARD_LR_CHANGE

6 HA

LRD_inv-6-UNPAIRED_DRP

6 HA

LRD-2-EVENTATTACHFAIL

2 HA

LRD-2-GET_EVENT_STATE_ERROR

2 HA

LRD-2-REMOVE_PAIR_OR_NODE_ERROR

2 HA

LRD-2-SYSMGR_GET_NODE_STATE

2 HA

LRD-2-SYSMGR_REGISTER

2 HA

LRD-2-UNHANDLED_EVENT

2 HA

LRD-3-BAG_REGISTRATION

3 HA

LRD-3-BINDING_ERROR

3 HA

LRD-3-ERROR_MESSAGE

3 HA

LRD-3-EXTRACT_FIELDS_FAILURE

3 HA

LRD-3-GET_LR_INVENTORY_ERROR

3 HA

LRD-3-GS_VECTOR_INIT_FAILURE

3 HA

LRD-3-MEM_ALLOC_FAIL

3 HA

LRD-3-MSG_CERR_REGISTER_DLL

3 HA

LRD-3-MSG_CERR_REGISTER_DLL

3 HA

LRD-3-MSG_CERR_REGISTER_DLL

3 HA

LRD-3-NODEID_CREATION_FAILURE

3 HA

LRD-3-SYSDB_ITEM_ERROR

3 HA

LRD-3-UNHANDLED_DEBUG_OPTION

3 HA

LRD-3-WRONG_LR_ID

3 HA

LRD-4-CANT_FIND_DSC

4 HA

LRD-4-CANT_FIND_DSC

4 HA

LRD-4-CANT_FIND_DSC

4 HA

LRD-4-HEADLESS_SDR_STATE

4 HA

LRD-4-SDR_PLANE_READY_TIMEOUT

4 HA

LRD-4-UNEXPECTED

4 HA

LRD-4-UNEXPECTED

4 HA

LRD-4-UNEXPECTED

4 HA

LRD-4-UNEXPECTED

4 HA

LRD-6-LATE_MGMT_NODE

6 HA

REDCON_CLIENT-3-ERROR

3 HA

REDCON_CLIENT-7-MSG_SEND

7 HA

REDCON-1-BACKUP_NOT_READY

1 HA

REDCON-1-BACKUP_READY

1 HA

REDCON-1-STANDBY_NOT_READY

1 HA

REDCON-1-STANDBY_NOT_READY

1 HA

REDCON-1-STANDBY_READY

1 HA

REDCON-1-STANDBY_READY

1 HA

REDCON-3-DRIVER_INIT_FAILED

3 HA

REDCON-3-DRIVER_INIT_FAILED

3 HA

REDCON-3-PCDS_INIT_FAILED

3 HA

REDCON-3-PCDS_INIT_FAILED

3 HA

REDCON-3-UNEXPECTED_ERROR

3 HA

REDCON-4-BACKUP_NOT_READY_ALARM

4 HA

REDCON-4-BACKUP_NOT_READY_REASON

4 HA

REDCON-4-CONN_RETRY

4 HA

REDCON-4-FAILOVER_DISABLED

4 HA

REDCON-4-FAILOVER_REQUESTED

4 HA

REDCON-4-FAILOVER_REQUESTED

4 HA

REDCON-4-SRP_NR_CLIENT_UNREG

4 HA

REDCON-4-SRP_NR_REASON_UNREG

4 HA

REDCON-4-STANDBY_NOT_READY_ALARM

4 HA

REDCON-4-STANDBY_NOT_READY_ALARM

4 HA

REDCON-4-STANDBY_NOT_READY_REASON

4 HA

REDCON-4-STANDBY_NOT_READY_REASON

4 HA

REDCON-4-STBY_ACTIVE_NOT_READY

4 HA

REDCON-4-STBY_ACTIVE_NOT_READY

4 HA

REDCON-4-STBY_CONN_RETRY

4 HA

REDCON-4-STBY_FORCE_GO_ACTIVE

4 HA

REDCON-4-STBY_FORCE_GO_ACTIVE

4 HA

REDCON-5-INIT_FAILED

5 HA

REDCON-6-BACKUP_CONNECTION_DOWN

6 HA

REDCON-6-BACKUP_CONNECTION_UP

6 HA

REDCON-6-GO_ACTIVE

6 HA

REDCON-6-GO_ACTIVE

6 HA

REDCON-6-GO_BACKUP

6 HA

REDCON-6-GO_PRIMARY

6 HA

REDCON-6-GO_STANDBY

6 HA

REDCON-6-GO_STANDBY

6 HA

REDCON-6-STANDBY_CONNECTION_DOWN

6 HA

REDCON-6-STANDBY_CONNECTION_DOWN

6 HA

REDCON-6-STANDBY_CONNECTION_UP

6 HA

REDCON-6-STANDBY_CONNECTION_UP

6 HA

REDCON-6-STBY_BACKUP_NOT_READY

6 HA

REDCON-6-STBY_BACKUP_READY

6 HA

REDCON-6-STBY_STANDBY_NOT_READY

6 HA

REDCON-6-STBY_STANDBY_READY

6 HA

REDCON-6-STBY_STANDBY_READY

6 HA

REDCON-7-FAILOVER_ENABLED

7 HA

REDCON-7-MSG_SEND_FAILED

7 HA

REDCON-7-UNEXPECTED

7 HA

REDCON-7-UNEXPECTED

7 HA

REDSTATS-3-SERVICE_CREATE

3 HA

REDSTATS-7-SYSCALL

7 HA

REDSTATS-7-UNEXPECTED

7 HA

RMF_CLIENT-3-ERROR

3 HA

RMF_CLIENT-7-MSG_SEND

7 HA

WD_STAT_PUB-3-SHM_EDM_ERR

3 HA

WD_STAT_PUB-3-SHM_ERR

3 HA

WD_STAT_PUB-3-SHMEM

3 HA

WD_STAT_PUB-7-SYSCALL

7 HA

DSR-2-DS_ADVT_REPLICATION_FAILURE

2 INFRA

ICCP-5-ISOLATION

5 INFRA

ICCP-5-ISOLATION_CLR

5 INFRA

ICCP-5-NEIGHBOR_STATE

5 INFRA

ICCP-6-BACKBONE_INTERFACE_STATE

6 INFRA

RGMGR-3-ERR_RIB_BATCH_BUFFER

3 INFRA

RGMGR-3-INIT

3 INFRA

RGMGR-4-ERR_RIB_BATCH_SEND

4 INFRA

SLA-3-CAPABILITIES_CONFLICT

3 INFRA

SLA-3-PM_INIT_FAILED

3 INFRA

SLA-3-PROFILE_CREATE_FAILED

3 INFRA

SLA-3-PROFILE_OP_SETUP_FAILED

3 INFRA

SLA-3-PROFILE_OP_UPDATE_FAILED

3 INFRA

SLA-3-PROFILE_UPDATE_FAILED

3 INFRA

SLA-4-DISTRIB_RECONNECT_FAILED

4 INFRA

SLA-4-DISTRIB_SEND_FAILED

4 INFRA

SLA-4-EXITING

4 INFRA

SLA-4-MESSAGING_FAILED

4 INFRA

SLA-4-MUTEX_FAIL

4 INFRA

SLA-4-OD_OPERATION_CLEANUP_FAILED

4 INFRA

SLA-4-PM_CLEANUP_FAILED

4 INFRA

SLA-4-PROBE_RESULTS_DROPPED

4 INFRA

SLA-4-PROBE_SCHEDULE_FAILURE

4 INFRA

SLA-4-PROBE_TRACKING_LIMIT_HIT

4 INFRA

SLA-4-SYSMGR_FAIL

4 INFRA

SLA-4-UNEXPECTED_PROTOCOL_DATA

4 INFRA

SLA-6-CONFIG_ERROR_SET

6 INFRA

SLA-6-OD_OPERATION_FINISHED

6 INFRA

SLA-6-OP_DB_NON_EMPTY

6 INFRA

SLA-6-PROFILE_VERIFY_FAILED

6 INFRA

SLA-6-RESYNC_PROFILE_INVALID

6 INFRA

SLA-6-SHMWIN_RESET

6 INFRA

BOOTVAR-7-CANT_OPEN

7 INSTALL

BOOTVAR-7-CANT_WRITE

7 INSTALL

BOOTVAR-7-CERR_REGISTER_DLL

7 INSTALL

BOOTVAR-7-INVALID_ARG

7 INSTALL

BOOTVAR-7-NULL_PTR

7 INSTALL

BOOTVAR-7-VAR_TOO_BIG

7 INSTALL

FC-3-FW_OPERATION_ERROR

3 INSTALL

FC-6-FW_OPERATION_INFO

6 INSTALL

FC-6-FWFILE_COPY_INFO

6 INSTALL

FC-6-FWFILE_INFO

6 INSTALL

INST_IO-3-NULL_POINTER

3 INSTALL

INST_IO-7-DEVICE_FULL

7 INSTALL

INSTDIR_INVENTORY-7-LTRACE_INIT

7 INSTALL

INSTDIR_INVENTORY-7-NULL_PTR

7 INSTALL

INSTHELPER-3DSDRSC_UNAVAILABLE_FOR_SW_DWNLD

3 INSTALL

INSTHELPER-3-DUMPIFS_ERR

3 INSTALL

INSTHELPER-3-EXIT_ERROR

3 INSTALL

INSTHELPER-3-FAILED_MDR_NODE

3 INSTALL

INSTHELPER-3-FAILED_PKG_DOWNLOAD

3 INSTALL

INSTHELPER-3-IFC_ERR

3 INSTALL

INSTHELPER-3INIT_ERROR_INSUFFICIENT_DISKSPACE

3 INSTALL

INSTHELPER-3INSTALL_DEVICE_UNAVAILABLE

3 INSTALL

INSTHELPER-3-INSUFFICIENT_DISKSPACE

3 INSTALL

INSTHELPER-3-MBI_COPY_FAIL

3 INSTALL

INSTHELPER-3-NOMEMORY

3 INSTALL

INSTHELPER-3RUNNING_ON_NON_PERSISTENT_DEVICE

3 INSTALL

INSTHELPER-3-SYS_ERR

3 INSTALL

INSTHELPER-3USES_MEM_FOR_PERSISTENT_DEVICE

3 INSTALL

INSTHELPER-3-WRONG_IMAGE

3 INSTALL

INSTHELPER-4-DEVICE_FORMAT_FAIL

4 INSTALL

INSTHELPER-6-DEVICE_FORMAT

6 INSTALL

INSTHELPER-6-DISKSPACE_CHECK_PASS

6 INSTALL

INSTHELPER-6FAILED_BOOT_DURING_INSTALL_PAUSE

6 INSTALL

INSTHELPER-6FAILED_BOOT_DURING_INSTALL_RESET

6 INSTALL

INSTHELPER-6-INCORRECT_LOADPATH

6 INSTALL

INSTHELPER-6-INCORRECT_MBI

6 INSTALL

INSTHELPER-6MBI_BOOTING_HOLD_BOOT_IN_MBI

6 INSTALL

INSTHELPER-6-MBI_BOOTING_MID_INSTALL

6 INSTALL

INSTHELPER-6-MBI_DOWNLOAD_COMPLETE

6 INSTALL

INSTHELPER-6-RELOAD_NODE_INFO

6 INSTALL

INSTHELPER-6-SELF_RESET

6 INSTALL

INSTHELPER-7-CLEAN_INVALID_DEVICE

7 INSTALL

INSTHELPER-7-COMPLETE_PACKAGE_CLEAN

7 INSTALL

INSTHELPER-7-COMPLETE_SYNC

7 INSTALL

INSTHELPER-7-DIGEST_BK_INTEGRITY

7 INSTALL

INSTHELPER-7-EVENT_FAIL

7 INSTALL

INSTHELPER-7-FAIL_ACTIVE_SYNC

7 INSTALL

INSTHELPER-7-FAIL_COPY

7 INSTALL

INSTHELPER-7-FAIL_FILE_IO

7 INSTALL

INSTHELPER-7-FAIL_LDPATH_UPDATE

7 INSTALL

INSTHELPER-7-FAIL_LWM_DISCONNECT

7 INSTALL

INSTHELPER-7-FAIL_PACKAGE_CLEAN

7 INSTALL

INSTHELPER-7-FAIL_STAT

7 INSTALL

INSTHELPER-7-FAIL_SYNC

7 INSTALL

INSTHELPER-7-FAIL_SYSMGR_NOTIFY

7 INSTALL

INSTHELPER-7-FAIL_THREAD_CREATE

7 INSTALL

INSTHELPER-7-FAILED_MEM_CACHE_INIT

7 INSTALL

INSTHELPER-7-FAILED_SDS_CONNECT

7 INSTALL

INSTHELPER-7-FAILED_SYSDB_CONNECT

7 INSTALL

INSTHELPER-7-FILE_OPEN_FAIL

7 INSTALL

INSTHELPER-7-INIT

7 INSTALL

INSTHELPER-7-INTERNALERR

7 INSTALL

INSTHELPER-7-INTERNALERR_INT

7 INSTALL

INSTHELPER-7-INVALID_NODEID_RETURNED

7 INSTALL

INSTHELPER-7-INVALID_NOTIF_INFO

7 INSTALL

INSTHELPER-7-LOCKING

7 INSTALL

INSTHELPER-7-MBI_DOWNLOAD

7 INSTALL

INSTHELPER-7-NULL_PTR

7 INSTALL

INSTHELPER-7-PKG_DOWNLOAD

7 INSTALL

INSTHELPER-7-PKGFS_INIT_BOOT

7 INSTALL

INSTHELPER-7-PREPARATION_COMPLETE

7 INSTALL

INSTHELPER-7-START_PACKAGE_CLEAN

7 INSTALL

INSTHELPER-7-START_SYNC

7 INSTALL

INSTHELPER-7-SYSDB_BIND

7 INSTALL

INSTMGR_CMD-3-NOMEMORY

3 INSTALL

INSTMGR_CMD-7-NULL_PTR

7 INSTALL

INSTMGR_CMD-7-PLATFORM_TYPE_FAIL

7 INSTALL

INSTMGR_LIB-2-FAILED_RELOAD_NODE

2 INSTALL

INSTMGR_LIB-2RELOAD_SAVE_CONFIG_FAILED

2 INSTALL

INSTMGR_LIB-3-FAILED_STATE_FILE_UPDATE

3 INSTALL

INSTMGR_LIB-3-FAILED_SYNC

3 INSTALL

INSTMGR_LIB-3-REPLY_MSG_SENDING

3 INSTALL

INSTMGR_LIB-6MESSAGE_NOT_PROCESSED

6 INSTALL

INSTMGR_LIB-6PARTIAL_DOWNLOAD_OCCURRED

6 INSTALL

INSTMGR_LIB-7-CLIENT_ERROR

7 INSTALL

INSTMGR_LIB-7CONFIG_POSTINSTALL_NOTIFICATION

7 INSTALL

INSTMGR_LIB-7CONFIG_PREINSTALL_NOTIFICATION

7 INSTALL

INSTMGR_LIB-7-DBADD

7 INSTALL

INSTMGR_LIB-7-DBCREATE

7 INSTALL

INSTMGR_LIB-7-DBFORMAT

7 INSTALL

INSTMGR_LIB-7-DBNAME

7 INSTALL

INSTMGR_LIB-7-DBOPEN

7 INSTALL

INSTMGR_LIB-7-DBOPERATION

7 INSTALL

INSTMGR_LIB-7-DBPATH

7 INSTALL

INSTMGR_LIB-7-DBRECORD

7 INSTALL

INSTMGR_LIB-7-DBSUBDIRECTORY

7 INSTALL

INSTMGR_LIB-7ENS_CONSUMER_RESPONSE

7 INSTALL

INSTMGR_LIB-7ENS_UNKNOWN_PAYLOAD_MSG_TYPE

7 INSTALL

INSTMGR_LIB-7-ERROR_REG

7 INSTALL

INSTMGR_LIB-7-FAIL_LWM_REPLY_TOO_BIG

7 INSTALL

INSTMGR_LIB-7-FAIL_LWM_SEND

7 INSTALL

INSTMGR_LIB-7-FAILED_OUTPUT_ERROR

7 INSTALL

INSTMGR_LIB-7-FILE_CHECK

7 INSTALL

INSTMGR_LIB-7-FILE_INFO

7 INSTALL

INSTMGR_LIB-7-FILE_OPEN_FAIL

7 INSTALL

INSTMGR_LIB-7-FILE_READ

7 INSTALL

INSTMGR_LIB-7-INFRA_BLOB

7 INSTALL

INSTMGR_LIB-7-INTERNALERR

7 INSTALL

INSTMGR_LIB-7-LIST

7 INSTALL

INSTMGR_LIB-7-LOAD_PIE

7 INSTALL

INSTMGR_LIB-7-LTRACE_INIT

7 INSTALL

INSTMGR_LIB-7-MEMORY

7 INSTALL

INSTMGR_LIB-7-NODE_CLASS_GET

7 INSTALL

INSTMGR_LIB-7-PACKAGE

7 INSTALL

INSTMGR_LIB-7-PARAMETER_NULL

7 INSTALL

INSTMGR_LIB-7-PATH

7 INSTALL

INSTMGR_LIB-7-PATH_CLEANUP

7 INSTALL

INSTMGR_LIB-7-PIE_FORMAT

7 INSTALL

INSTMGR_LIB-7-PIE_INFO_CONSTRUCT

7 INSTALL

INSTMGR_LIB-7-PKG_LOAD

7 INSTALL

INSTMGR_LIB-7-PLATFORM_TYPE_FAIL

7 INSTALL

INSTMGR_LIB-7RELOAD_MEMBOOTED_MANAGEMENT_NOD
E

7 INSTALL

INSTMGR_LIB-7-STACK

7 INSTALL

INSTMGR_LIB-7-SYSMGR

7 INSTALL

INSTMGR_LIB-7TEST_ISSU_RUN_MDR_COMPLETE_SLEEP

7 INSTALL

INSTMGR_LIB-7TEST_ISSU_RUN_RELOAD_SLEEP

7 INSTALL

INSTMGR-2-AUTO_ABORT_TIMER_EXPIRED

2 INSTALL

INSTMGR-2-AUTO_ABORT_TIMER_EXPIRING

2 INSTALL

INSTMGR-2-FAILED_RELOAD_NODE

2 INSTALL

INSTMGR-2INSTALL_CRITICAL_AUTO_ABORT

2 INSTALL

INSTMGR-2INSTALL_OP_SYS_ERR_GLOBAL_NODES_INC
ONSISTENT

2 INSTALL

INSTMGR-2INSTALL_OP_SYS_ERR_SPECIFIC_NODES_IN
CONSISTENT

2 INSTALL

INSTMGR-2INSTALL_OP_SYS_ERR_SPECIFIC_NODES_IN
CONSISTENT_HDR

2 INSTALL

INSTMGR-2-INSTALL_SYS_ERR_FAILURE

2 INSTALL

INSTMGR-2-ISM_PD_LIB_INIT_FAIL

2 INSTALL

INSTMGR-2-ISM_PD_LIB_INIT_FAIL

2 INSTALL

INSTMGR-2ISSU_OP_ABORT_DSC_SWITCHOVER

2 INSTALL

INSTMGR-2ISSU_OP_ABORT_FABRIC_RELOADED

2 INSTALL

INSTMGR-2ISSU_OP_ABORT_FABRIC_REMOVED

2 INSTALL

INSTMGR-2ISSU_OP_ABORT_STANDBY_RELOADED

2 INSTALL

INSTMGR-2ISSU_OP_ABORT_STANDBY_REMOVED

2 INSTALL

INSTMGR-3-ABORT_INCOMPLETE_INSTALL

3 INSTALL

INSTMGR-3ABORT_INCOMPLETE_INSTALL_ADD

3 INSTALL

INSTMGR-3AUTO_ABORT_TIMER_RUNNING_WARN

3 INSTALL

INSTMGR-3-BAD_OP_TYPE

3 INSTALL

INSTMGR-3-BUILD_TABLE_FAIL

3 INSTALL

INSTMGR-3-CORRUPT_CHECKPOINT

3 INSTALL

INSTMGR-3-FAILED_ENS_INIT

3 INSTALL

INSTMGR-3-FAILED_ENS_REQUEST

3 INSTALL

INSTMGR-3-INIT

3 INSTALL

INSTMGR-3INSTALL_ERROR_BUT_NO_CLI_CONNECTION

3 INSTALL

INSTMGR-3INSTALL_OPERATION_SYSTEM_ERROR_GLOB
AL_NODES

3 INSTALL

INSTMGR-3INSTALL_OPERATION_SYSTEM_ERROR_SPEC
IFIC_NODES

3 INSTALL

INSTMGR-3INSTALL_OPERATION_SYSTEM_ERROR_SPEC
IFIC_NODES_HDR

3 INSTALL

INSTMGR-3INSTALL_OPERATION_USER_ERROR

3 INSTALL

INSTMGR-3INSTALL_SYSTEM_ERROR_GLOBAL_NODES

3 INSTALL

INSTMGR-3INSTALL_SYSTEM_ERROR_SPECIFIC_NODES

3 INSTALL

INSTMGR-3INSTALL_SYSTEM_ERROR_SPECIFIC_NODES_
HDR

3 INSTALL

INSTMGR-3-ISM_PD_LIB_ERROR

3 INSTALL

INSTMGR-3-ISM_PD_LIB_ERROR

3 INSTALL

INSTMGR-3-ISM_PD_LIB_SPA_RELOADED

3 INSTALL

INSTMGR-3-ISM_PD_LIB_SPA_RELOADED

3 INSTALL

INSTMGR-3-ISM_PD_LIB_SPA_SHUT_ERR

3 INSTALL

INSTMGR-3-ISM_PD_LIB_SPA_SHUT_ERR

3 INSTALL

INSTMGR-3-ISM_PD_LIB_SPA_UNSHUT_ERR

3 INSTALL

INSTMGR-3-ISM_PD_LIB_SPA_UNSHUT_ERR

3 INSTALL

INSTMGR-3ISSU_FSM_TIMER_EXPIRED_ABORT

3 INSTALL

INSTMGR-3-ISSU_MARKED_NODE_NC

3 INSTALL

INSTMGR-3-ISSU_RELOAD_NODE

3 INSTALL

INSTMGR-3-MEMORY_CONDITION

3 INSTALL

INSTMGR-3-NOMEMORY

3 INSTALL

INSTMGR-3-REPLY_MSG_SENDING

3 INSTALL

INSTMGR-3-ROLL_BACK_FAILURE

3 INSTALL

INSTMGR-3-SAM_CERTIFICATE_EXPIRED

3 INSTALL

INSTMGR-3-SYSDB

3 INSTALL

INSTMGR-3-SYSDBREG

3 INSTALL

INSTMGR-3-SYSMGR_SPAWN_SCRIPT_EBUSY

3 INSTALL

INSTMGR-3-TIMER_ABORT

3 INSTALL

INSTMGR-3UNABLE_TO_DETERMINE_PREREQUISITE_O
RDERING

3 INSTALL

INSTMGR-4ABORTING_FORCE_RELOAD_NODE

4 INSTALL

INSTMGR-4ACTIVE_SOFTWARE_COMMITTED_INFO

4 INSTALL

INSTMGR-4-AUTO_ABORT_TIMER_RUNNING

4 INSTALL

INSTMGR-4-AUTO_ABORT_TIMER_STARTED

4 INSTALL

INSTMGR-4-AUTO_ABORT_TIMER_STOPPED

4 INSTALL

INSTMGR-4CALLING_PLATFORM_RELOAD_NODES_ALL

4 INSTALL

INSTMGR-4CALLING_PLATFORM_RELOAD_NODES_SPEC
IFIC

4 INSTALL

INSTMGR-4FAILED_CALL_PLATFORM_RELOAD_NODES_
ALL

4 INSTALL

INSTMGR-4FAILED_CALL_PLATFORM_RELOAD_NODES_S
PECIFIC

4 INSTALL

INSTMGR-4-INSTALL_IS_TO_SUSPEND

4 INSTALL

INSTMGR-4INSTALL_ISSU_AUTO_ABORT_TIMER_NOT_F
OUND

4 INSTALL

INSTMGR-4-INSTALL_OPERATION_WARNING

4 INSTALL

INSTMGR-4INSTALL_WARNING_AUTO_ABORT

4 INSTALL

INSTMGR-4-ISM_PD_LIB_CE_CONN_ERR

4 INSTALL

INSTMGR-4-ISM_PD_LIB_CE_CONN_WARN

4 INSTALL

INSTMGR-4ISSU_NODE_BOOT_NOT_ALLOWED

4 INSTALL

INSTMGR-4ISSU_NODE_BOOT_NOT_ALLOWED_PRE_RU
N

4 INSTALL

INSTMGR-4ISSU_UNEXPECTED_NODE_BOOT

4 INSTALL

INSTMGR-4-LARGE_INSTALL_HISTORY_LOG

4 INSTALL

INSTMGR-4-LRD_CALL_STILL_TRYING

4 INSTALL

INSTMGR-4-RELOAD_NODE_DELAY

4 INSTALL

INSTMGR-4-ROLLBACK_FILE_FAILURE

4 INSTALL

INSTMGR-4-STANDBY_NOT_READY

4 INSTALL

INSTMGR-6-IMDR_COMPLETION_TIMEOUT

6 INSTALL

INSTMGR-6INSTALL_COMPLETE_PHASE_FINISHED

6 INSTALL

INSTMGR-6INSTALL_COMPLETE_PHASE_STARTED

6 INSTALL

INSTMGR-6-INSTALL_ISSU_NEXT_COMMAND

6 INSTALL

INSTMGR-6INSTALL_LOAD_PHASE_FINISHED

6 INSTALL

INSTMGR-6-INSTALL_LOAD_PHASE_STARTED

6 INSTALL

INSTMGR-6-INSTALL_OPERATION_ABORTED

6 INSTALL

INSTMGR-6INSTALL_OPERATION_ABORTING_ON_ERROR

6 INSTALL

INSTMGR-6INSTALL_OPERATION_CANCELLED

6 INSTALL

INSTMGR-6INSTALL_OPERATION_COMPLETED_SUCCES
SFULLY

6 INSTALL

INSTMGR-6INSTALL_OPERATION_COMPLETED_WITH_FAI
LURE

6 INSTALL

INSTMGR-6-INSTALL_OPERATION_FAILED

6 INSTALL

INSTMGR-6-INSTALL_OPERATION_STARTED

6 INSTALL

INSTMGR-6INSTALL_OPERATION_USER_ABORTED

6 INSTALL

INSTMGR-6-INSTALL_RESUMED

6 INSTALL

INSTMGR-6-INSTALL_RUN_PHASE_FINISHED

6 INSTALL

INSTMGR-6-INSTALL_RUN_PHASE_STARTED

6 INSTALL

INSTMGR-6-ISM_PD_LIB_CE_CONN_INFO

6 INSTALL

INSTMGR-6-ISM_PD_LIB_RELOAD_DATA

6 INSTALL

INSTMGR-6-ISM_PD_LIB_RELOAD_DATA

6 INSTALL

INSTMGR-6-ISM_PD_LIB_SPA_SHUTDOWN

6 INSTALL

INSTMGR-6-ISM_PD_LIB_SPA_SHUTDOWN

6 INSTALL

INSTMGR-6-ISM_PD_LIB_SPA_UNSHUTDOWN

6 INSTALL

INSTMGR-6-ISM_PD_LIB_SPA_UNSHUTDOWN

6 INSTALL

INSTMGR-6-ISSU_DATA

6 INSTALL

INSTMGR-6-ISSU_DSC_SWITCHOVER

6 INSTALL

INSTMGR-6-ISSU_FSM_TIMER_EXPIRED

6 INSTALL

INSTMGR-6-ISSU_NODE_OUT_OF_MBI

6 INSTALL

INSTMGR-6-ISSU_NOT_RELOADING_NODE

6 INSTALL

INSTMGR-6ISSU_ON_ABORT_NO_RELOAD_INSTDIR

6 INSTALL

INSTMGR-6ISSU_ON_ABORT_NO_RELOAD_ISM

6 INSTALL

INSTMGR-6-ISSU_PHASE_INFO

6 INSTALL

INSTMGR-6-ISSU_STATE_MACHINE_FROZEN

6 INSTALL

INSTMGR-6-ISSU_STATE_MACHINE_THAWED

6 INSTALL

INSTMGR-6-NODE_BOOT_OPTIONS

6 INSTALL

INSTMGR-6-NODE_BOOT_OPTIONS_CLEAR

6 INSTALL

INSTMGR-6-PAUSED_AT_CONFIG_LOCK

6 INSTALL

INSTMGR-6-PAUSED_BEFORE_RELOAD

6 INSTALL

INSTMGR-6-WAIT_FOR_STANDBY

6 INSTALL

INSTMGR-6-WAIT_FOR_TARGET_NODES

6 INSTALL

INSTMGR-7-DSC_MIGRATED

7 INSTALL

INSTMGR-7-FAILED_OUTPUT_ERROR

7 INSTALL

INSTMGR-7FAILED_OUTPUT_USEFUL_INFORMATION

7 INSTALL

INSTMGR-7-FAILED_OUTPUT_WARNING

7 INSTALL

INSTMGR-7-FAILMSG

7 INSTALL

INSTMGR-7-FILE_OPEN_FAIL

7 INSTALL

INSTMGR-7-INTERNALERR

7 INSTALL

INSTMGR-7-LTRACE_INIT

7 INSTALL

INSTMGR-7-NO_LOG_STORED

7 INSTALL

INSTMGR-7-NULL_PTR

7 INSTALL

INSTMGR-7-PATH

7 INSTALL

INSTMGR-7-RDS_SYNC_WAIT

7 INSTALL

INSTMGR-7-RELOAD_NODE_INFO

7 INSTALL

INSTMGR-7-REQ_MSG_PROCESSING

7 INSTALL

INSTMGR-7-REQUEST_RETRIEVE

7 INSTALL

INSTMGR-7-RESUME_INCOMPLETE_INSTALL

7 INSTALL

INSTMGR-7-SOFTWARE_CHANGE_RELOAD

7 INSTALL

INSTMGR-7-SWITCHOVER_DATA_LOST

7 INSTALL

INSTMGR-7TEST_ISSU_RUN_SWITCHOVER_SLEEP

7 INSTALL

INSTMGR-7-TIMEOUT_ALMOST_EXPIRED

7 INSTALL

INSTMGR-7-TIMER

7 INSTALL

INSTMGR-7-UNKNOWN_ERROR_TYPE

7 INSTALL

INSTREPL-7DOWNLOADED_BADLY_SIZED_FILE

7 INSTALL

INSTREPL-7DOWNLOADED_BADLY_SIZED_FILE_FROM_N
ODE

7 INSTALL

INSTREPL-7-FILE_OPEN_FAILED

7 INSTALL

IOR-7-INTERNALERR

7 INSTALL

IOR-7-LTRACE_INIT

7 INSTALL

IOR-7-NOMEMORY

7 INSTALL

IOR-7-NULL_PTR

7 INSTALL

LIBINST_DEBUG-3-INIT

3 INSTALL

LIBINST_DEBUG-3-INTERNAL

3 INSTALL

LIBINST_DEBUG-3-MUTEX

3 INSTALL

LIBINST_DEBUG-4-CERR_REGISTER_DLL

4 INSTALL

LIBNOTIFY-7-ARCH_NOT_SUPPORTED

7 INSTALL

LIBNOTIFY-7-ARCH_NOT_SUPPORTED

7 INSTALL

LIBNOTIFY-7-BAD_TOOLS_VERSION

7 INSTALL

LIBNOTIFY-7-BAD_TOOLS_VERSION

7 INSTALL

LIBNOTIFY-7-BLOBBIFIER_ERROR

7 INSTALL

LIBNOTIFY-7-BLOBBIFIER_ERROR

7 INSTALL

LIBNOTIFY-7CANNOT_GET_BLOB_SIZE_IN_A2STRUCT

7 INSTALL

LIBNOTIFY-7CANNOT_GET_BLOB_SIZE_IN_A2STRUCT

7 INSTALL

LIBNOTIFY-7CANNOT_GET_BLOB_SIZE_IN_STRUCT

7 INSTALL

LIBNOTIFY-7CANNOT_GET_BLOB_SIZE_IN_STRUCT

7 INSTALL

LIBNOTIFY-7-CANNOT_GET_PROCNAME

7 INSTALL

LIBNOTIFY-7-CANNOT_GET_PROCNAME

7 INSTALL

LIBNOTIFY-7-DEBLOBBIFIER_ERROR

7 INSTALL

LIBNOTIFY-7-DEBLOBBIFIER_ERROR

7 INSTALL

LIBNOTIFY-7-EVENT_CONN_CREATE

7 INSTALL

LIBNOTIFY-7-EVENT_CONN_CREATE

7 INSTALL

LIBNOTIFY-7-EVENT_CONN_NOTIFY

7 INSTALL

LIBNOTIFY-7-EVENT_CONN_NOTIFY

7 INSTALL

LIBNOTIFY-7-EVENT_CONN_OPEN

7 INSTALL

LIBNOTIFY-7-EVENT_CONN_OPEN

7 INSTALL

LIBNOTIFY-7-FAILED_INIT_LTRACE

7 INSTALL

LIBNOTIFY-7-FAILED_INIT_LTRACE

7 INSTALL

LIBNOTIFY-7-INTERNAL

7 INSTALL

LIBNOTIFY-7-INTERNAL

7 INSTALL

LIBNOTIFY-7INTERNAL_DATA_INCONSISTENCY

7 INSTALL

LIBNOTIFY-7INTERNAL_DATA_INCONSISTENCY

7 INSTALL

LIBNOTIFY-7-ITEM_NOT_FOUND

7 INSTALL

LIBNOTIFY-7-ITEM_NOT_FOUND

7 INSTALL

LIBNOTIFY-7-LIST_IS_FULL

7 INSTALL

LIBNOTIFY-7-LIST_IS_FULL

7 INSTALL

LIBNOTIFY-7-LIST_ITEM_NOT_FOUND

7 INSTALL

LIBNOTIFY-7-LIST_ITEM_NOT_FOUND

7 INSTALL

LIBNOTIFY-7-MEMORY

7 INSTALL

LIBNOTIFY-7-MEMORY

7 INSTALL

LIBNOTIFY-7-NOT_A_MANAGEMENT_NODE

7 INSTALL

LIBNOTIFY-7-NOT_A_MANAGEMENT_NODE

7 INSTALL

LIBNOTIFY-7-PARAMETER_BAD_EVENT

7 INSTALL

LIBNOTIFY-7-PARAMETER_BAD_EVENT

7 INSTALL

LIBNOTIFY-7-PARAMETER_BAD_TRANSID

7 INSTALL

LIBNOTIFY-7-PARAMETER_BAD_TRANSID

7 INSTALL

LIBNOTIFY-7PARAMETER_DYNAMIC_TYPE_CHECK_FAILUR
E

7 INSTALL

LIBNOTIFY-7PARAMETER_DYNAMIC_TYPE_CHECK_FAILUR
E

7 INSTALL

LIBNOTIFY-7-PARAMETER_INCOMPLETE

7 INSTALL

LIBNOTIFY-7-PARAMETER_INCOMPLETE

7 INSTALL

LIBNOTIFY-7PARAMETER_MISSING_BLOBBIFIER

7 INSTALL

LIBNOTIFY-7PARAMETER_MISSING_BLOBBIFIER

7 INSTALL

LIBNOTIFY-7PARAMETER_MISSING_OR_NULL

7 INSTALL

LIBNOTIFY-7PARAMETER_MISSING_OR_NULL

7 INSTALL

LIBNOTIFY-7-PARAMETER_NULL

7 INSTALL

LIBNOTIFY-7-PARAMETER_NULL

7 INSTALL

LIBNOTIFY-7-PARAMETER_RANGE

7 INSTALL

LIBNOTIFY-7-PARAMETER_RANGE

7 INSTALL

LIBNOTIFY-7PARAMETER_REFERENCES_NULL

7 INSTALL

LIBNOTIFY-7PARAMETER_REFERENCES_NULL

7 INSTALL

LIBNOTIFY-7PARAMETER_WRONG_BLOB_TYPE

7 INSTALL

LIBNOTIFY-7PARAMETER_WRONG_BLOB_TYPE

7 INSTALL

LIBNOTIFY-7-RESOURCE_LOCKED

7 INSTALL

LIBNOTIFY-7-RESOURCE_LOCKED

7 INSTALL

LIBNOTIFY-7-SYSDB_BIND

7 INSTALL

LIBNOTIFY-7-SYSDB_BIND

7 INSTALL

LIBNOTIFY-7-SYSDB_COMMIT

7 INSTALL

LIBNOTIFY-7-SYSDB_COMMIT

7 INSTALL

LIBNOTIFY-7-SYSDB_DELETE

7 INSTALL

LIBNOTIFY-7-SYSDB_DELETE

7 INSTALL

LIBNOTIFY-7-SYSDB_GET

7 INSTALL

LIBNOTIFY-7-SYSDB_GET

7 INSTALL

LIBNOTIFY-7-SYSDB_LIST

7 INSTALL

LIBNOTIFY-7-SYSDB_LIST

7 INSTALL

LIBNOTIFY-7SYSDB_NOTIFICATION_UNREGISTER

7 INSTALL

LIBNOTIFY-7SYSDB_NOTIFICATION_UNREGISTER

7 INSTALL

LIBNOTIFY-7-SYSDB_SET

7 INSTALL

LIBNOTIFY-7-SYSDB_SET

7 INSTALL

LIBNOTIFY-7-SYSDB_START

7 INSTALL

LIBNOTIFY-7-SYSDB_START

7 INSTALL

LIBNOTIFY-7-SYSDB_UNBIND

7 INSTALL

LIBNOTIFY-7-SYSDB_UNBIND

7 INSTALL

LIBNOTIFY-7-SYSMGR_TROUBLE

7 INSTALL

LIBNOTIFY-7-SYSMGR_TROUBLE

7 INSTALL

LIBNOTIFY-7-TIMEOUT_RESET_LIMIT

7 INSTALL

LIBNOTIFY-7-TIMEOUT_RESET_LIMIT

7 INSTALL

LIBNOTIFY-7-TYPE_MISMATCH_FOR_KEY

7 INSTALL

LIBNOTIFY-7-TYPE_MISMATCH_FOR_KEY

7 INSTALL

LOADPATH_UPGRADE-7CANT_ACTIVATE_ON_NODE_TYPES

7 INSTALL

LOADPATH_UPGRADE-7-NULL_PTR

7 INSTALL

LOADPATH_UPGRADE-7PACKAGE_SUPPORTS_NO_NODE_TYPES

7 INSTALL

LOADPATH-3-LIB_INIT_FAIL

3 INSTALL

LOADPATH-3-LTRACE_INIT_FAIL

3 INSTALL

LOADPATH-7-CORRUPT_ARG

7 INSTALL

LOADPATH-7-CORRUPT_LDPATH

7 INSTALL

LOADPATH-7-EMPTY_LOADPATH_STR

7 INSTALL

LOADPATH-7FAILED_REMOVE_IGNORE_COMMIT_LDPATH
_FILE

7 INSTALL

LOADPATH-7-FILE_CLOSE_FAIL

7 INSTALL

LOADPATH-7-FILE_OPEN_FAIL

7 INSTALL

LOADPATH-7-FILE_READ_FAIL

7 INSTALL

LOADPATH-7-FILE_RENAME_FAIL

7 INSTALL

LOADPATH-7-FILE_SEEK_FAIL

7 INSTALL

LOADPATH-7-NULL_PTR

7 INSTALL

LOADPATH-7-PACKAGE_OUTPUT_SORT

7 INSTALL

PKG_PLAT_MEM_CACHE-7-NULL_PTR

7 INSTALL

PKG_PLAT-7-INTERNALERR

7 INSTALL

PKG_PLAT-7-INTERNALERR

7 INSTALL

PKG_PLAT-7-IO_FAIL

7 INSTALL

PKG_PLAT-7-IO_FAIL

7 INSTALL

PKG_PLAT-7-IO_FAIL

7 INSTALL

PKG_PLAT-7-IO_FAIL

7 INSTALL

PKG_PLAT-7-IO_FAIL

7 INSTALL

PKG_PLAT-7-IO_FAIL

7 INSTALL

PKG_PLAT-7-MY_NODE_TYPE

7 INSTALL

PKG_PLAT-7-MY_NODE_TYPE

7 INSTALL

PKG_PLAT-7-NO_MEM

7 INSTALL

PKG_PLAT-7-NO_MEM

7 INSTALL

PKG_PLAT-7-NO_MEM

7 INSTALL

PKG_PLAT-7-NO_MEM

7 INSTALL

PKG_PLAT-7-NO_MEM

7 INSTALL

PKG_PLAT-7-NO_MEM

7 INSTALL

PKG_PLAT-7-NO_MEM

7 INSTALL

PKG_PLAT-7-NULL_PTR

7 INSTALL

PKG_PLAT-7-NULL_PTR

7 INSTALL

PKG_PLAT-7-NULL_PTR

7 INSTALL

PKG_PLAT-7-NULL_PTR

7 INSTALL

PKG_PLAT-7-NULL_PTR

7 INSTALL

PKG_PLAT-7-NULL_PTR

7 INSTALL

PKG_PLAT-7-NULL_PTR

7 INSTALL

PKG_PLAT-7-OPEN_FAIL

7 INSTALL

PKG_PLAT-7-OPEN_FAIL

7 INSTALL

PKG_PLAT-7-OPEN_FAIL

7 INSTALL

PKG_PLAT-7-OPEN_FAIL

7 INSTALL

PKG_PLAT-7-OPEN_FAIL

7 INSTALL

PKG_PLAT-7-OPEN_FAIL

7 INSTALL

PKG_PLAT-7-OPEN_FAIL

7 INSTALL

PKG_PLAT-7-UNKNOWN_NODE_TYPE

7 INSTALL

PKG_PLAT-7-UNKNOWN_NODE_TYPE

7 INSTALL

PKG_PLAT-7-UNKNOWN_NODE_TYPE

7 INSTALL

PKG_PLAT-7-UNKNOWN_NODE_TYPE

7 INSTALL

PKG_PLAT-7-UNKNOWN_NODE_TYPE

7 INSTALL

PKG_PLAT-7-UNKNOWN_NODE_TYPE

7 INSTALL

PKG_PLAT-7-UNKNOWN_NODE_TYPE

7 INSTALL

PKG-3-CORRUPT_INSTALL_FILE

3 INSTALL

PKG-3-CORRUPT_INSTALL_FILE

3 INSTALL

PKG-3-NOMEMORY

3 INSTALL

PKG-3-NOMEMORY

3 INSTALL

PKG-4-LRD_CALL_STILL_TRYING

4 INSTALL

PKG-4-LRD_CALL_STILL_TRYING

4 INSTALL

PKG-7-BAD_DEVICE_INDEX_ENTRY

7 INSTALL

PKG-7-BAD_DEVICE_INDEX_ENTRY

7 INSTALL

PKG-7-BAD_DIR_PREFIX

7 INSTALL

PKG-7-BAD_DIR_PREFIX

7 INSTALL

PKG-7-BAD_INSTDB_FORMAT

7 INSTALL

PKG-7-BAD_INSTDB_FORMAT

7 INSTALL

PKG-7-BAD_PIE_FORMAT

7 INSTALL

PKG-7-BAD_PIE_FORMAT

7 INSTALL

PKG-7-BAD_SORT_TYPE

7 INSTALL

PKG-7-BAD_SORT_TYPE

7 INSTALL

PKG-7-CANT_ADD_FILE_INTO_TABLE

7 INSTALL

PKG-7-CANT_ADD_FILE_INTO_TABLE

7 INSTALL

PKG-7-CANT_CD

7 INSTALL

PKG-7-CANT_CD

7 INSTALL

PKG-7-CANT_GET_FILES

7 INSTALL

PKG-7-CANT_GET_FILES

7 INSTALL

PKG-7-CANT_GET_INSTALL_PATH

7 INSTALL

PKG-7-CANT_GET_INSTALL_PATH

7 INSTALL

PKG-7-CANT_GET_NODE_TABLE

7 INSTALL

PKG-7-CANT_GET_NODE_TABLE

7 INSTALL

PKG-7-CANT_GET_RELATIVE_PATH

7 INSTALL

PKG-7-CANT_GET_RELATIVE_PATH

7 INSTALL

PKG-7-CANT_GET_SIGNATURE

7 INSTALL

PKG-7-CANT_GET_SIGNATURE

7 INSTALL

PKG-7-CANT_MKDIR

7 INSTALL

PKG-7-CANT_MKDIR

7 INSTALL

PKG-7-CANT_READ

7 INSTALL

PKG-7-CANT_READ

7 INSTALL

PKG-7-CANT_RMDIR

7 INSTALL

PKG-7-CANT_RMDIR

7 INSTALL

PKG-7-CANT_SORT_NODE_TABLE

7 INSTALL

PKG-7-CANT_SORT_NODE_TABLE

7 INSTALL

PKG-7-CANT_UNCOMPRESS

7 INSTALL

PKG-7-CANT_UNCOMPRESS

7 INSTALL

PKG-7-CERR_REGISTER_DLL

7 INSTALL

PKG-7-CERR_REGISTER_DLL

7 INSTALL

PKG-7-CLOSE_FILE

7 INSTALL

PKG-7-CLOSE_FILE

7 INSTALL

PKG-7-COPY_FILE

7 INSTALL

PKG-7-COPY_FILE

7 INSTALL

PKG-7-CORRUPT_ARG

7 INSTALL

PKG-7-CORRUPT_ARG

7 INSTALL

PKG-7-CORRUPT_PIE

7 INSTALL

PKG-7-CORRUPT_PIE

7 INSTALL

PKG-7-CREATE_SYMLINK

7 INSTALL

PKG-7-CREATE_SYMLINK

7 INSTALL

PKG-7-DELETE_FILE

7 INSTALL

PKG-7-DELETE_FILE

7 INSTALL

PKG-7-FAILED_REPAIR_INDEX_FILE

7 INSTALL

PKG-7-FAILED_REPAIR_INDEX_FILE

7 INSTALL

PKG-7-FILE_NOT_IN_LOADPATH

7 INSTALL

PKG-7-FILE_NOT_IN_LOADPATH

7 INSTALL

PKG-7-GET_APINAME_REPORT

7 INSTALL

PKG-7-GET_APINAME_REPORT

7 INSTALL

PKG-7-GET_FILE_INFO

7 INSTALL

PKG-7-GET_FILE_INFO

7 INSTALL

PKG-7-GET_PROVIDERS_REPORT

7 INSTALL

PKG-7-GET_PROVIDERS_REPORT

7 INSTALL

PKG-7-INSTDB_BUILD_ERROR

7 INSTALL

PKG-7-INSTDB_BUILD_ERROR

7 INSTALL

PKG-7-INTERNALERR

7 INSTALL

PKG-7-INTERNALERR

7 INSTALL

PKG-7-INVALID_ARG

7 INSTALL

PKG-7-INVALID_ARG

7 INSTALL

PKG-7-LTRACE_INIT

7 INSTALL

PKG-7-LTRACE_INIT

7 INSTALL

PKG-7MBI_CONFIG_INCORRECTLY_CHANGED

7 INSTALL

PKG-7MBI_CONFIG_INCORRECTLY_CHANGED

7 INSTALL

PKG-7-MD5_GET_PACKAGE_SIGNATURE

7 INSTALL

PKG-7-MD5_GET_PACKAGE_SIGNATURE

7 INSTALL

PKG-7-MD5_TO_STRING

7 INSTALL

PKG-7-MD5_TO_STRING

7 INSTALL

PKG-7-MD5_VERIFY_FILES

7 INSTALL

PKG-7-MD5_VERIFY_FILES

7 INSTALL

PKG-7-MEMORY_FAILURE_MINOR

7 INSTALL

PKG-7-MEMORY_FAILURE_MINOR

7 INSTALL

PKG-7-MISSING_PIE_ATTRIBUTE

7 INSTALL

PKG-7-MISSING_PIE_ATTRIBUTE

7 INSTALL

PKG-7-NO_CWD

7 INSTALL

PKG-7-NO_CWD

7 INSTALL

PKG-7-NON_RELOAD_MDR_ISSU

7 INSTALL

PKG-7-NON_RELOAD_MDR_ISSU

7 INSTALL

PKG-7-NON_RELOAD_PARALLEL_LR

7 INSTALL

PKG-7-NON_RELOAD_PARALLEL_LR

7 INSTALL

PKG-7-NOT_DIR

7 INSTALL

PKG-7-NOT_DIR

7 INSTALL

PKG-7-NOT_PIE_FILE

7 INSTALL

PKG-7-NOT_PIE_FILE

7 INSTALL

PKG-7-NOT_SINGLE_PIE_ATTRIBUTE

7 INSTALL

PKG-7-NOT_SINGLE_PIE_ATTRIBUTE

7 INSTALL

PKG-7-NULL_PTR

7 INSTALL

PKG-7-NULL_PTR

7 INSTALL

PKG-7-OPEN_FILE

7 INSTALL

PKG-7-OPEN_FILE

7 INSTALL

PKG-7-PIE_LIST_MISMATCH

7 INSTALL

PKG-7-PIE_LIST_MISMATCH

7 INSTALL

PKG-7-PREDICT_AVL_TREE

7 INSTALL

PKG-7-PREDICT_AVL_TREE

7 INSTALL

PKG-7-READ_FILE

7 INSTALL

PKG-7-READ_FILE

7 INSTALL

PKG-7-RENAME_FILE

7 INSTALL

PKG-7-RENAME_FILE

7 INSTALL

PKG-7-RETIRED_PIE_FORMAT

7 INSTALL

PKG-7-RETIRED_PIE_FORMAT

7 INSTALL

PKG-7-UNKNOWN_NODE_TYPE

7 INSTALL

PKG-7-UNKNOWN_NODE_TYPE

7 INSTALL

PKG-7-UNLINK_FILE

7 INSTALL

PKG-7-UNLINK_FILE

7 INSTALL

PKG-7-WRITE_FILE

7 INSTALL

PKG-7-WRITE_FILE

7 INSTALL

PKG-7-WRONG_PIE_LOADER

7 INSTALL

PKG-7-WRONG_PIE_LOADER

7 INSTALL

PKGFS-3-FILE_WRITE

3 INSTALL

PKGFS-4-LOADPATH_STR

4 INSTALL

SDS_LIB-3-INIT

3 INSTALL

SDS_LIB-7-INTERNALERR

7 INSTALL

SDS_LIB-7-MEMORY

7 INSTALL

SDS-3-INIT

3 INSTALL

SDS-3-PKG_MEM_CACHE

3 INSTALL

SDS-7-DB_CHKPT_CORRUPTION

7 INSTALL

SDS-7-FAILED_PARTNER_NODE_STATE

7 INSTALL

SDS-7-INVALID_CLIENT_NODEID

7 INSTALL

SDS-7-LWM

7 INSTALL

SM-3-CALLBACK

3 INSTALL

SM-3-CANNOT_DO_DLL

3 INSTALL

SM-3-COMMUNICATION

3 INSTALL

SM-3-INTERNAL

3 INSTALL

SM-3-UNABLE_TO_PROCEED

3 INSTALL

SM-4-NONFATAL_ERROR

4 INSTALL

TURBOBOOT-3-DISK_TOO_SMALL

3 INSTALL

TURBOBOOT-3-INVALID_DEVICE

3 INSTALL

TURBOBOOT-4ROMMON_VARIABLE_NOT_SET

4 INSTALL

TURBOBOOT-7-CANNOT_RESET_BOOTENV

7 INSTALL

TURBOBOOT-7-DISK_INACCESSIBLE

7 INSTALL

TURBOBOOT-7-DUAL_DEVICE_INIT_SPEC

7 INSTALL

TURBOBOOT-7-DUAL_DEVICE_SPEC

7 INSTALL

VERSMGR_LIB-7-FILESYSTEM

7 INSTALL

VERSMGR_LIB-7-MEMORY

7 INSTALL

VERSMGR_LIB-7-PARAMETER

7 INSTALL

VERSMGR_LIB-7-SYSDB_BIND

7 INSTALL

VERSMGR_LIB-7-SYSDB_GET

7 INSTALL

VERSMGR_LIB-7-SYSDB_REGISTER

7 INSTALL

VERSMGR_LIB-7-SYSDB_SET

7 INSTALL

VERSMGR_LIB-7-SYSDB_UNBIND

7 INSTALL

VS_CLIENT-3-CACHE_LOOKUP

3 INSTALL

VS_CLIENT-3CACHE_LOOKUP_NOT_PRESENT

3 INSTALL

VS_CLIENT-3-FAILURE

3 INSTALL

VS_CLIENT-3-NOMEM

3 INSTALL

VS_CLIENT-3-NOTIFICATION

3 INSTALL

VS_CLIENT-3-NOTIFICATION

3 INSTALL

VS_CLIENT-3-NOTIFICATION_NOT_PRESENT

3 INSTALL

VS_CLIENT-4-RESPONSE

4 INSTALL

VS_CLIENT-7-INIT_SUCCESSFUL

7 INSTALL

VS_PUBLISHER-3-HANDLER

3 INSTALL

VS_PUBLISHER-3-TIMEOUT

3 INSTALL

ANCP-3-CHKPT_INIT_FAIL

3 IP

ANCP-3-IM_INIT_FAIL

3 IP

ANCP-3-IM_RATE_UPD_FAIL

3 IP

ANCP-3-INIT_FAIL

3 IP

ANCP-3-PORT_ERR

3 IP

ANCP-3-RP_REDUNDANCY_INIT_FAIL

3 IP

ANCP-3-SEND_ERR

3 IP

ANCP-3-SOCKET_INIT_FAIL

3 IP

ANCP-3-SYSDB_INIT_FAIL

3 IP

ANCP-4-MEM_THROTTLE

4 IP

ANCP-4-MEM_THROTTLE_EVENT_UNKNOWN

4 IP

ANCP-5-ADJ_DONE

5 IP

ANCP-5-ADJ_RESET

5 IP

ANCP-5-BAD_PKT_RCV

5 IP

ANCP-5-FSM_DISCARD

5 IP

ANCP-5-MEM_UNTHROTTLE

5 IP

ANCP-5-PORT_MOVE

5 IP

ANCP-5-PORT_WRONG_ADJ

5 IP

ARP_GMP-4-WARN_EVENT

4 IP

ARP_GMP-4-WARN_INIT

4 IP

ARP-3-CACHE_FAIL

3 IP

ARP-3-COMMS_INIT_FAIL

3 IP

ARP-3-MEDIA_FAIL

3 IP

ARP-3-NO_MEM

3 IP

ARP-4-WARN_CLIENT_OVERWRITE

4 IP

ARP-4-WARN_CLIENT_RESYNC

4 IP

ARP-4-WARN_CONN

4 IP

ARP-4-WARN_INIT

4 IP

ARP-4-WARN_REGISTER

4 IP

ARP-4-WARN_SPIO_ATTACH_FAIL

4 IP

ARP-4-WARN_THREAD

4 IP

ARP-4-WARN_WAIT

4 IP

ARP-6-INFO_DUPADDR

6 IP

ARP-6-INFO_DUPMAC

6 IP

ARP-6-INFO_IF_MISMATCH

6 IP

ARP-6-INFO_MAC

6 IP

CE_TFTP-3-ASYNC_GET_BFR_FAIL

3 IP

CE_TFTP-3-ASYNC_GET_CLIENT_FAIL

3 IP

CE_TFTP-3-ASYNC_WRITE_FAIL

3 IP

CE_TFTP-3-CE_TFTP_EXIT

3 IP

CE_TFTP-3-DATA_SEND_FAIL

3 IP

CE_TFTP-3-DATA_XFER_ERR

3 IP

CE_TFTP-3-EDM_INIT_FAIL

3 IP

CE_TFTP-3-EDM_SYSDB_REG_FAIL

3 IP

CE_TFTP-3-ERR

3 IP

CE_TFTP-3-EVENT_MGR_CE_TFTP

3 IP

CE_TFTP-3-EVENT_MGR_DEBUG_FAIL

3 IP

CE_TFTP-3-EVENT_MGR_TFTP_TIMER_FAIL

3 IP

CE_TFTP-3-FAILURE_MUTEX_INIT

3 IP

CE_TFTP-3-FILE_ACCESS_FAIL

3 IP

CE_TFTP-3-FILE_NOT_FOUND

3 IP

CE_TFTP-3-GET_MY_NODEID_FAIL

3 IP

CE_TFTP-3-INVALID_FILENAME

3 IP

CE_TFTP-3-MAC_ADDRESS_INIT_FAIL

3 IP

CE_TFTP-3-MEM_ALLOC_ERR

3 IP

CE_TFTP-3-MEM_ALLOC_FAIL

3 IP

CE_TFTP-3NODEID_TO_ETHER_IPADDR_FAIL

3 IP

CE_TFTP-3-SOCKLITE_INIT_FAIL

3 IP

CE_TFTP-3-SYSDB_BIND_FAIL

3 IP

CE_TFTP-3-SYSDB_ERR

3 IP

CE_TFTP-3-SYSDB_REG_VERIFY_FAIL

3 IP

CE_TFTP-3-TFTP_DEBUG_INIT_FAIL

3 IP

CE_TFTP-3-TFTP_TIMER_INIT_FAIL

3 IP

CE_TFTP-3-TFTPSERVER_BAG_ENCODE_FAIL

3 IP

CE_TFTP-3-TFTPSERVER_BAG_REG_FAIL

3 IP

CE_TFTP-3-TFTPSERVER_SOCKET_FAIL

3 IP

CE_TFTP-6EVENT_MGR_UNKNOWN_EVENT_RCVD

6 IP

CE_TFTP-6-FILE_ACCESS_ERR

6 IP

CE_TFTP-6-INVALID_PKT

6 IP

CE_TFTP-6-INVALID_PKT

6 IP

CE_TFTP-6-INVALID_PROTOCOL_FIELD

6 IP

CE_TFTP-6-INVALID_PROTOCOL_FIELD

6 IP

CE_TFTP-6-KERNEL_DUMP_MSG

6 IP

CE_TFTP-6-KERNEL_DUMP_MSG

6 IP

CE_TFTP-7-TFTP_DEBUG_REG_FAIL

7 IP

DAPS-4-INIT_FAIL

4 IP

DAPS-4-RANGE_MISMATCH

4 IP

DAPS-5-POOL_UTIL_HIGH

5 IP

DAPS-5-UTIL_HIGH

5 IP

DAPS-6-POOL_UTIL_LOW

6 IP

DAPS-6-UTIL_LOW

6 IP

DHCPD-3-ASSERT_FAIL

3 IP

DHCPD-3-CHKPT_FAILED

3 IP

DHCPD-3-CONN_DOWN

3 IP

DHCPD-3-FETCH_ERR

3 IP

DHCPD-3-INIT

3 IP

DHCPD-3-NOPACKET

3 IP

DHCPD-3-SYSDBINIT

3 IP

DHCPD-4-ERR_INIT

4 IP

DHCPD-4-INVALID_DEFAULT_GATEWAY

4 IP

DHCPD-4-NO_ADDR_ASSIGN

4 IP

DHCPV6-3-DBNOTLOADED

3 IP

DHCPV6-3-DBNOTLOADED

3 IP

DHCPV6-3-DBOPEN

3 IP

DHCPV6-3-DBOPEN

3 IP

DHCPV6-3-DBREAD

3 IP

DHCPV6-3-DBREAD

3 IP

DHCPV6-3-DBWRITE

3 IP

DHCPV6-3-DBWRITE

3 IP

DHCPV6-3-INIT

3 IP

DHCPV6-3-INIT

3 IP

DHCPV6-3-MCASTJOIN

3 IP

DHCPV6-3-MCASTJOIN

3 IP

DHCPV6-3-MUTEXLOCK

3 IP

DHCPV6-3-MUTEXLOCK

3 IP

DHCPV6-3-NOPACKET

3 IP

DHCPV6-3-NOPACKET

3 IP

DHCPV6-3-SYSDBINIT

3 IP

DHCPV6-3-SYSDBINIT

3 IP

DHCPV6-4-RIB_SEND

4 IP

DHCPV6-4-RIB_SEND

4 IP

DHCPV6-5-RELAYOUTIF

5 IP

DHCPV6-5-RELAYOUTIF

5 IP

DHCPV6-6SUSPICIOUS_PD_DELETE_REQUEST

6 IP

DHCPV6-6SUSPICIOUS_PD_DELETE_REQUEST

6 IP

DOMAIN_SERVICES-3-ATTACH_HANDLER

3 IP

DOMAIN_SERVICES-3-CREATE_CHANNEL

3 IP

DOMAIN_SERVICES-3-CREATE_CHUNK

3 IP

DOMAIN_SERVICES-3CREATE_EVENT_CONN

3 IP

DOMAIN_SERVICES-3-CREATE_TIMER

3 IP

DOMAIN_SERVICES-3-EDM_SERVER

3 IP

DOMAIN_SERVICES-3-END_PROC

3 IP

DOMAIN_SERVICES-3-GET_COID

3 IP

DOMAIN_SERVICES-3-OPEN_EVENT_CONN

3 IP

DOMAIN_SERVICES-3-REGISTER_DEBUG

3 IP

DOMAIN_SERVICES-3-REGISTER_EVM

3 IP

DOMAIN_SERVICES-3-REGISTER_RPC

3 IP

DOMAIN_SERVICES-3SYSMGR_PROC_READY

3 IP

DOMAIN_SERVICES-6-BSD_INFO_MSG

6 IP

DOMAIN_SERVICES-7-BSD_DEBUG_MSG

7 IP

DOMAIN_SERVICES-7-BSD_DEBUG_MSG_V2

7 IP

DOMAIN_SERVICES-7-REGISTER_CERRNO

7 IP

FHRP_OUTPUT-2-CRIT_PKT_THREAD_SIGNAL

2 IP

FHRP_OUTPUT-3ERR_CLIENT_OUT_OF_SYNC

3 IP

FHRP_OUTPUT-3-ERR_EVM_CREATE

3 IP

FHRP_OUTPUT-3-ERR_MAIN_QUEUE

3 IP

FHRP_OUTPUT-3-ERR_NO_MEM

3 IP

FHRP_OUTPUT-3-ERR_PKT_QUEUE

3 IP

FHRP_OUTPUT-3-WARN_COMMS_INIT

3 IP

FHRP-3-ERR_MAX_MAC

3 IP

FHRP-3-ERR_NO_MEM

3 IP

FHRP-4-WARN_INIT

4 IP

HFR_IPv4-2-BGP_PA_CONFIG_IFH

2 IP

HFR_IPv4-2-MSTATS_ALLOC_ERR

2 IP

HFR_IPv4-2-SYSTEM_FAIL

2 IP

HFR_IPv4-2-TRANS_ERR

2 IP

HFR_IPv4-4-LTRACE

4 IP

HFR_IPv4-4-TRANS_WARNING

4 IP

HFR_IPv4-6-INFO

6 IP

IEP-3-DAEMON_ERR_EVM_CREATE

3 IP

IEP-3-DAEMON_ERR_EVM_EVENT_BLOCK

3 IP

IEP-3-DAEMON_ERR_SYSDB_BIND

3 IP

IEP-3-DAEMON_ERR_SYSDB_BSCAN

3 IP

IEP-3-DAEMON_ERR_SYSDB_REG_VERIFY

3 IP

IEP-3-DAEMON_ERR_SYSDB_UNBIND

3 IP

IEP-3-DAEMON_ERR_SYSMGR_PROC_READY

3 IP

IEP-3-ERR_SYSDB_BIND

3 IP

IEP-3-ERR_SYSDB_UNBIND

3 IP

IEP-7-ERR_INTERNAL

7 IP

IP_APS-6-ADDR_THRESHOLD_XCED

6 IP

IP_APS-6-RANGE_THRESHOLD_XCED

6 IP

IP_ARM_CLIB-3-MSG_FREE_NODE_FAIL

3 IP

IP_ARM_CLIB-3-MSG_GENERIC_FUNC

3 IP

IP_ARM_CLIB-3-MSG_INVALID_REG

3 IP

IP_ARM_CLIB-3-MSG_MALLOC_FAIL

3 IP

IP_ARM_CLIB-3-TLV_DECODE_ERROR

3 IP

IP_ARM_PLIB-3-EVENT_SET_RETRY_FAILED

3 IP

IP_ARM_TEST-6-RCVD_UPDATE

6 IP

IP_ARM-3-BAD_VISIBLE_COUNT

3 IP

IP_ARM-3-CFLCT_FORCED_DOWN

3 IP

IP_ARM-3-CFLCT_NOT_FOUND

3 IP

IP_ARM-3-MHOST_DEFAULT_PIM

3 IP

IP_ARM-3-TLV_DECODE

3 IP

IP_ARM-3-UNNUM_CFLCT

3 IP

IP_ARM-6-CFGED_MHOST_DEFAULT_MGMT

6 IP

IP_ARM-6-CFLCT_NO_LONGER

6 IP

IP_ARM-6-RTRID_CFG_DEPRECATED

6 IP

IP_ARM-6-RTRID_GLOBAL_UNAVAILABLE

6 IP

IP_ARM-6-UNNUM_CFLCT_NO_LONGER

6 IP

IP_ARM-7-ERR_SYSDB_BIND

7 IP

IP_ARM-7-INIT_FAILED

7 IP

IP_ARM-7-LTRACE_INIT_ERR

7 IP

IP_EA-3-BLOCKAGE

3 IP

IP_EA-3-PLATFORM_UPDATE

3 IP

IP_EA-3-PLATFORM_UPDATE_BULK

3 IP

IP_ICMP-7-EVM_CREATE_FAILURE

7 IP

IP_ICMP-7-LIB_INIT_FAILED

7 IP

IP_ICMP-7-SYSDB_BIND_FAILURE

7 IP

IP_ICMP-7-SYSDB_REG_NOTIFY_FAILURE

7 IP

IP_ICMP-7-SYSDB_REG_VERIFY_FAILURE

7 IP

IP_NTP_LIB-7-EXIT_MESSAGE

7 IP

IP_NTP_LIB-7-EXIT_MESSAGES

7 IP

IP_NTP-3-CALENDAR_UPDATE_FAILED

3 IP

IP_NTP-3-CLOCK_UPDATE_FAILED

3 IP

IP_NTP-3-DRIFT_UPDATE_FAILED

3 IP

IP_NTP-3-EXCEED_MAXFREQ

3 IP

IP_NTP-5-ALL_CONN_LOST

5 IP

IP_NTP-5-HP_CONN_LOST

5 IP

IP_NTP-5-HP_CONN_RECOVERED

5 IP

IP_NTP-5-LP_CONN_RECOVERED

5 IP

IP_NTP-5-STATE_CHANGE_TO_SYNC

5 IP

IP_NTP-5-STATE_CHANGE_TO_UNSYNC

5 IP

IP_NTP-5-SYNC_LOSS

5 IP

IP_NTP-5-UNUSUAL_OFFSET

5 IP

IPV4_EDM-3-DECODE_FAILED

3 IP

IPV4_EDM-3-ENCODE_FAILED

3 IP

IPV4_EDM-3-SYSDB_BAG_ENCODE_FAILED

3 IP

IPV4_EDM-3-SYSDB_BIND_FAILED

3 IP

IPV4_EDM-3-SYSDB_REG_EDM_FAILED

3 IP

IPV4_EDM-6-BAGREG_FAILED

6 IP

IPV4_EDM-7-BAG_REG_FAILED

7 IP

IPV4_IO-3-NOMEM

3 IP

IPV4_IO-3-OPTION_UPDATE_FAIL

3 IP

IPV4_IO-3-PA_BIND

3 IP

IPV4_IO-3-PA_NULL_HANDLE

3 IP

IPV4_IO-3-UNHANDLED

3 IP

IPV4_IO-4-UNKNOWN_MESSAGE

4 IP

IPV4_IO-7-INIT_FAILED

7 IP

IPV4_MA-3-ADD_GROUP_FAILED

3 IP

IPV4_MA-3-CREATE_REGISTER_FAILED

3 IP

IPV4_MA-3-EVM_ASYNC_ATTACH

3 IP

IPV4_MA-3-EVM_ATTACH_FAILED

3 IP

IPV4_MA-3-EVM_CREATE_FAILED

3 IP

IPV4_MA-3-GET_FINT_NAME_FAILED

3 IP

IPV4_MA-3-REMOVE_GROUP_FAILED

3 IP

IPV4_MA-3-SYSDB_BIND_FAILED

3 IP

IPV4_MA-3-SYSDB_REG_NOTIFY_FAILED

3 IP

IPV4_MA-3-SYSDB_REG_VERIFY

3 IP

IPV4_MA-4-AVLBL_MTU_MISMATCH

4 IP

IPV4_MA-4-INTERFACE_EXIST

4 IP

IPV4_MA-4-LOG_MTU

4 IP

IPV4_MA-4-PRI_IP_ADDR_DIFF

4 IP

IPV4_MA-5-IFH_MISMATCHED

5 IP

IPV4_MA-7-INIT_FAILED

7 IP

IPV4_MA-7REPLICATE_DPC_INVALID_COOKIE

7 IP

IPV4_MA-7-UNKNOWN_MESSAGE

7 IP

IPV6_MA-3-ADD_GROUP_FAILED

3 IP

IPV6_MA-3-CONFIG_INIT

3 IP

IPV6_MA-3-EVENT_CONN_FAIL

3 IP

IPV6_MA-3-EVENTMGR_CREATE_FAILED

3 IP

IPV6_MA-3-LAS_P_INIT

3 IP

IPV6_MA-3-LL_CFG

3 IP

IPV6_MA-3-REMOVE_GROUP_FAILED

3 IP

IPV6_MA-3-SETUP_HANDLERS

3 IP

IPV6_MA-3-SYSDB_BIND_FAILED

3 IP

IPV6_MA-4-ADDRSVR_INIT

4 IP

IPV6_MA-4-DB_INIT

4 IP

IPV6_MA-4-DEBUG_INIT

4 IP

IPV6_MA-4-INIT_FAIL

4 IP

IPV6_MA-4-INTERFACE_EXIST

4 IP

IPV6_MA-4-INVALID_MTU

4 IP

IPV6_MA-4-LOG_MTU

4 IP

IPV6_MA-4-LTRACE_INIT_FAIL

4 IP

IPV6_MA-4-REMOVE_ENCAP

4 IP

IPV6_MA-4-TIMER_ADDL_CTXT

4 IP

IPV6_MA-4-TIMER_INIT_FAILED

4 IP

IPV6_MA-6-IM_FAIL

6 IP

IPV6_MA-7ADDRESS_DUPLICATE_RECOVERY

7 IP

IPV6_MA-7-INIT_FAILED

7 IP

IPV6_ND-3-ADDRESS_DUPLICATE

3 IP

IPV6_ND-3-ERR_AIB_ADJ

3 IP

IPV6_ND-3-ERR_AIB_CONN

3 IP

IPV6_ND-3-ERR_EVENT_MGR_CREATE

3 IP

IPV6_ND-3-ERR_EXTERNAL_FAIL

3 IP

IPV6_ND-3-ERR_IFH_CONN

3 IP

IPV6_ND-3-ERR_IM_BIND

3 IP

IPV6_ND-3ERR_IM_MEDIA_NOT_SUPPORTED

3 IP

IPV6_ND-3-ERR_INVALID_RA_INTERVAL

3 IP

IPV6_ND-3-ERR_SYSDB

3 IP

IPV6_ND-4-WARNING_CACHE_LIMIT_HIT

4 IP

IPV6_SW-3-CLEAR_MAPPING_FAILED

3 IP

IPV6_SW-3-ERR_ATTACH_FSV

3 IP

IPV6_SW-3-ERR_MEDIA_REGISTER

3 IP

IPV6_SW-3-ERR_NETIO_MUTEX_LOCK

3 IP

IPV6_SW-3-ERR_NO_INTERFACE

3 IP

IPV6_SW-3-ERR_PAK_REDIRECT

3 IP

IPV6_SW-3-ERR_PROTO_INIT

3 IP

IPV6_SW-3ERR_READ_PUNT_REASON_FAILED

3 IP

IPV6_SW-3-NEED_SLOW_ROUTINE

3 IP

IPV6_SW-3-SET_MAPPING_FAILED

3 IP

IPV6_SW-4-ERR_DEBUG_INIT

4 IP

IPV6-3-ADD_ENCAP

3 IP

IPV6-3-DEBUG_INIT_FAILED

3 IP

IPV6-3-EDM_OPEN_FAILED

3 IP

IPV6-3-IM_FAIL

3 IP

IPV6-3-INIT_FAILED

3 IP

IPV6-3-LTRACE_INIT_FAIL

3 IP

IPV6-3-NULL_HANDLE_ALLOC

3 IP

IPV6-3-PACKETMGR_CONNECT_FAILED

3 IP

IPV6-3-PAK_SEND_TO_TRANSPORT_FAILED

3 IP

IPV6-3-SYSDB_BIND_FAILED

3 IP

IPV6-3-SYSDB_CONNECT_FAILED

3 IP

IPV6-4-EVENTCONN_CREATE_FAILED

4 IP

IPV6-4-PA_BIND

4 IP

IPV6-4-PA_BIND_RETVAL

4 IP

IPV6-4-SYSDB_CREATEITEM_FAILED

4 IP

IPV6-5-INVALID_INPUT

5 IP

IPV6-6-EDM_DECODE_FAILED

6 IP

IPV6-6-EDM_ENCODE_FAILED

6 IP

IPV6-6-EDM_REGISTER_FAILED

6 IP

IPV6-6-PACKET_DISCARD

6 IP

IPV6-6-PAK_FSV_WRITE_FAILED

6 IP

IPV6-6-STATS_SHM_INIT_FAILED

6 IP

L2SNOOP-3-DEBUG_INIT

3 IP

L2SNOOP-3-INIT_ERR

3 IP

L2SNOOP-3-INIT_RETRY

3 IP

L2SNOOP-3-NO_MEM

3 IP

L2SNOOP-3-RED_INIT

3 IP

L2SNOOP-3-REG_NETWORK

3 IP

L2SNOOP-3-SOCKET_INIT

3 IP

L2SNOOP-3-SOFTWARE_INSTALL

3 IP

L2SNOOP-3-TIMER_INIT

3 IP

L2SNOOP-3-VRF_INIT

3 IP

L2SNOOP-7-SYSDB_INIT

7 IP

LIBIPPIMDLL-3-PIM_LIB_SYSDB

3 IP

LIBIPV4-3-CONV_ITEM_FAIL

3 IP

LIBIPV4-7-DATALIST_FAIL

7 IP

LIBIPV4-7-HSSD_REG_FAIL

7 IP

LIBIPV4PROTO-6-PAKHDR

6 IP

LIBIPV4PROTO-6-PAKHDR_ERROR

6 IP

LIBIPV4PROTO-7-GET_PAK_HDR_COUNT

7 IP

LIBIPV4PROTO-7-PLIB_INIT

7 IP

LIBIPV6PROTO-3-CONNECT_IO_STATS_FAIL

3 IP

LIBIPV6PROTO-3-FSV_REG_FAIL

3 IP

LIBIPV6PROTO-3-FSV_WRITE_FAIL

3 IP

LIBIPV6PROTO-3-GET_MTU_FAIL

3 IP

LIBIPV6PROTO-3-IPSEC_HANDLE

3 IP

LIBIPV6PROTO-3-LAS_INIT_FAIL

3 IP

LIBIPV6PROTO-3-NETIO_CONN_INIT_FAIL

3 IP

LIBIPV6PROTO-3-NETWORK_GONE_FAIL

3 IP

LIBIPV6PROTO-3-NO_MEM_FAIL

3 IP

LIBIPV6PROTO-7-SEND_PACKET_FAIL

7 IP

LISP-3-NO_MAP_REQUEST_SOURCE

3 IP

LISP-4-ASSERT

4 IP

LISP-4-LOCAL_EID_NO_ROUTE

4 IP

LISP-4-LOCAL_EID_RLOC_INCONSISTENCY

4 IP

LISP-4-ROUTE_IMPORT_WARN

4 IP

LISP-4-SITE_XTR_RLOC_INCONSISTENCY

4 IP

LISP-4-UNSUPPORTED_LOCAL_RLOC

4 IP

LISP-6-DDT_BAD_XTR_NONCE

6 IP

LISP-6-OS_HMAC_MISSING

6 IP

MPA_CONSUMER-3-MEM_ALLOC_FAILED

3 IP

MPA-3-DOWNLOAD_FAIL

3 IP

MPA-3-ERR_MEM_ALLOC

3 IP

MPA-3-GROUP_SEND_NODE

3 IP

MPA-3-MGII_MUTEX

3 IP

MPA-3-RADIX_FAIL

3 IP

MPA-3-RTINSERT_FAIL

3 IP

MPA-7-DELETE_FAIL

7 IP

MPA-7-INIT_FAILED

7 IP

PFILTER_MA-7-INIT

7 IP

PIM_MLDP_LIB-3-MLDP_FAIL

3 IP

PIM_MLDP_LIB-3-MLDP_PROD_FAIL

3 IP

PROTO_NPMB_LIB-3-SHMSTATS_MAP_ERR

3 IP

PRRT-3-ERR_CHUNK_CREATE

3 IP

PRRT-3-ERR_CONN

3 IP

PRRT-3-ERR_EVM

3 IP

PRRT-3-ERR_INIT

3 IP

PRRT-3-ERR_PTHREAD_CREATE

3 IP

PRRT-3-ERR_TIMER

3 IP

PRRT-6-ERR_NETIO_CONNECT

6 IP

RAW-3-DEBUG_INIT

3 IP

RAW-3-INIT_ERR

3 IP

RAW-3-INIT_RETRY

3 IP

RAW-3-NO_MEM

3 IP

RAW-3-REG_NETWORK

3 IP

RAW-3-SOFTWARE_INSTALL

3 IP

RAW-3-TIMER_INIT

3 IP

RAW-3-VRF_INIT

3 IP

RAW-7-SOCKET_INIT

7 IP

RAW-7-SYSDB_INIT

7 IP

rlogin-3-CHILD_PID

3 IP

rlogin-3-CHILD_STOPPED

3 IP

rlogin-3-CHILD_TERMINATED

3 IP

rlogin-3-ERR_BEST_ROUTE

3 IP

rlogin-3-ERR_CREATE_EVENTMGR

3 IP

rlogin-3-ERR_FLUSH

3 IP

rlogin-3-ERR_FORK

3 IP

rlogin-3-ERR_SOCKET

3 IP

rlogin-3-WAIT

3 IP

rlogin-6-ERR_GENRAL

6 IP

RLOGIND-3-ERR_CREATE_EVENTMGR

3 IP

RLOGIND-3-ERR_DEBUG_INIT

3 IP

RLOGIND-3-ERR_FATAL

3 IP

RLOGIND-3-ERR_MALLOC

3 IP

RLOGIND-3-ERR_OPEN

3 IP

RLOGIND-3-ERR_SPAWN

3 IP

RLOGIND-3-ERR_SYSDB

3 IP

RLOGIND-3-ERR_TTY_DETAILS
RLOGIND-3-ERR_USAGE

3 IP
3 IP

RLOGIND-3-ERR_VTY_CONNECT

3 IP

RLOGIND-4-ERR_SOCKET

4 IP

RLOGIND-6-INFO_GENERAL

6 IP

RSHD-2-ILLEGAL_PORT

2 IP

RSHD-3-ERR_AUTH

3 IP

RSHD-3-ERR_CREATE_EVENTMGR

3 IP

RSHD-3-ERR_MALLOC

3 IP

RSHD-3-ERR_REGISTER_DEBUG

3 IP

RSHD-3-ERR_SOCKET
RSHD-3-ERR_USAGE

3 IP
3 IP

SCTP-3-INIT_ERR

3 IP

SMIAP-2-INIT_FAILED

2 IP

SMIAP-3-CHKPT_FAIL

3 IP

SMIAP-4-ADDR_CFLCT

4 IP

SMIAP-4-IM_ATTR_FIND_IF_FAILED

4 IP

SMIAP-4-INVALID_NETWORK

4 IP

SMIAP-4-SYSMGR_FAILURE

4 IP

SMIAP-4-VIRTUAL_IP_CFLCT

4 IP

SOCKET-3-ASYNC_ABORTED

3 IP

SOCKET-3-ASYNC_LISTEN_CLOSE_FAIL

3 IP

SOCKET-3-ASYNC_PULSE_FAILURE

3 IP

SOCKET-3-ASYNC_SEQNO_MISMATCH

3 IP

SOCKET-3-ASYNC_SHMWIN_FAIL

3 IP

SOCKET-3-ASYNC_SOCKETS_ABORTED

3 IP

SOCKET-3-ASYNC_SOCKETS_DISALLOWED

3 IP

SOCKET-4-DOUBLE_CLOSE

4 IP

SOCKET-6-ASYNC_XIPC

6 IP

SOCKET-6-ASYNC_XIPC_THROTTLE

6 IP

SOCKET-7-DEBUG_INIT_EVENT

7 IP

SOCKET-7-DEBUG_REGISTER

7 IP

SOCKET-7-EVM_CREATE_FAIL

7 IP

SOCKET-7-NOFDREF

7 IP

STANDBY-3-ERR_EDM_NOTIFY

3 IP

STANDBY-3-ERR_IM

3 IP

STANDBY-3-ERR_JOIN

3 IP

STANDBY-3-ERR_MAC

3 IP

STANDBY-3-ERR_MAX_MAC

3 IP

STANDBY-3-ERR_NO_MEM

3 IP

STANDBY-3-ERR_REGISTER

3 IP

STANDBY-4-WARN_BADAUTH

4 IP

STANDBY-4-WARN_BADVIP

4 IP

STANDBY-4-WARN_DEBUG

4 IP

STANDBY-4-WARN_INIT

4 IP

STANDBY-4-WARN_TRAFFIC_SLAVE

4 IP

STANDBY-6-INFO_HOLDTIME

6 IP

STANDBY-6-INFO_REDIRECTS_DISABLED

6 IP

STANDBY-6-INFO_REDIRECTS_SECONDARY

6 IP

STANDBY-6-INFO_STATECHANGE

6 IP

TCP_NSR-3-FO_INITIATED

3 IP

TCP_NSR-3-FO_NOT_INITIATED

3 IP

TCP_NSR-3-INIT_FAIL

3 IP

TCP_NSR-3-OUT_OF_SYNC

3 IP

TCP_NSR-5-DISABLED

5 IP

TCP_NSR-6-KEEPALIVE_MISS

6 IP

TCP-3-BADAUTH

3 IP

TCP-3-CONNECTION_ABORT

3 IP

TCP-3-DEBUG_INIT

3 IP

TCP-3-EAOPT_KEYMAX

3 IP

TCP-3-EAOPT_RECV_UNSUPPORTED_MAC

3 IP

TCP-3-EAOPT_SEND_INVALID_KEY

3 IP

TCP-3-EAOPT_SEND_NOKEY

3 IP

TCP-3-EAOPT_SEND_UNSUPPORTED_MAC

3 IP

TCP-3-IM_INIT

3 IP

TCP-3-INIT_FAIL

3 IP

TCP-3-MISSING_AUTH

3 IP

TCP-3-NO_MEM

3 IP

TCP-3-TIMER_INIT

3 IP

TCP-7-SOCKET_INIT

7 IP

TCP-7-SYSDB_INIT

7 IP

telnet-3-ERR_SYSDB

3 IP

telnet-3-IMC_BIND

3 IP

telnet-3-INVALID_ADDR_FAMILY

3 IP

telnet-3-INVALID_PORT

3 IP

telnet-3-RIB_BIND_FAILURE

3 IP

telnet-3-RIB_SRC_ADDRESS_ERROR

3 IP

telnet-3-SYSDB_GET

3 IP

telnet-3-SYSTEM_ERROR

3 IP

telnet-3-TCP_NETWORK_COMMS

3 IP

telnet-3-TTY_DETAILS

3 IP

telnet-3-TTY_NMSPC_PATH

3 IP

telnet-4-DSCP_EXTRACT

4 IP

telnet-4-DSCP_SET

4 IP

telnet-4-SETSOCKOPT_BADF

4 IP

telnet-6-ARM_ADDRESS

6 IP

telnet-6-BIND

6 IP

telnet-6-CONNECT

6 IP

telnet-6-INTF_DOWN

6 IP

telnet-6-INTF_HANDLE

6 IP

telnet-6-INVALID_ADDRESS

6 IP

telnet-6-INVALID_INTF
telnet-6-IP_ARM

6 IP
6 IP

telnet-6-SETSOCKOPT

6 IP

telnet-6-SETSOCKOPT_EDOM

6 IP

telnet-6-SETSOCKOPT_FAULT

6 IP

telnet-6-SETSOCKOPT_INVAL

6 IP

telnet-6-SETSOCKOPT_NOPROTOOPT

6 IP

telnet-6-SOCKET

6 IP

telnet-6-TCP_NODELAY

6 IP

telnet-6-TCP_SO_OOBINLINE

6 IP

TELNETD-2-SYSTEM_FAIL

2 IP

TELNETD-3-ADDRESS_ERROR

3 IP

TELNETD-3-CON_TIMEOUT

3 IP

TELNETD-3-ERR_ADDRESS_FAMILY

3 IP

TELNETD-3-ERR_BAD_PORT

3 IP

TELNETD-3-ERR_CONNECT

3 IP

TELNETD-3-ERR_CREATE_EVENTMGR

3 IP

TELNETD-3-ERR_DEBUG_INIT

3 IP

TELNETD-3-ERR_EXITING

3 IP

TELNETD-3-ERR_KERNEL

3 IP

TELNETD-3-ERR_MALLOC

3 IP

TELNETD-3-ERR_OPEN

3 IP

TELNETD-3-ERR_PANIC

3 IP

TELNETD-3-ERR_SYSDB

3 IP

TELNETD-3-ERR_TTY_DETAILS

3 IP

TELNETD-3-ERR_USAGE

3 IP

TELNETD-3-SYSTEM_ERROR

3 IP

TELNETD-3-TCP_NETWORK_COMMS

3 IP

TELNETD-4-CONFIGURATION_CHECK

4 IP

TELNETD-4-DSCP_EXTRACT

4 IP

TELNETD-4-TCP_KEEPALIVE

4 IP

TELNETD-4-TCP_NAGLE

4 IP

TELNETD-7-EVENT_CREATE

7 IP

TELNETD-7-MAP_STAT

7 IP

TELNETD-7-SYSMGR_REGISTER

7 IP

TELNETD-7-THREAD_CREATE

7 IP

telnetdscp-4-DSCP_EXTRACT

4 IP

telnetdscp-4-DSCP_SET

4 IP

telnetmgmt-4-DSCP_VERIFY

4 IP

TFTP_FS-3-ETIMEOUT_THRESHOLD

3 IP

TFTP_FS-3-KEEPALIVE_THRESHOLD

3 IP

TTS-3-INIT_FAIL

3 IP

TTS-3-IO_FAIL

3 IP

TTS-3-TSS_CMD_FAIL

3 IP

TTS-6-INFO

6 IP

UDP-3-DEBUG_INIT

3 IP

UDP-3-INIT_ERR

3 IP

UDP-3-INIT_RETRY

3 IP

UDP-3-NO_MEM

3 IP

UDP-3-TIMER_INIT

3 IP

UDP-3-VRF_INIT

3 IP

UDP-7-SOCKET_INIT

7 IP

UDP-7-SYSDB_INIT

7 IP

VRRP-3-ERR_INDEX

3 IP

VRRP-3-ERR_MAX_MAC

3 IP

VRRP-3-ERR_NO_MEM

3 IP

VRRP-4-WARN_BADAUTH

4 IP

VRRP-4-WARN_BFD_MISCONFIG

4 IP

VRRP-4-WARN_DEBUG

4 IP

VRRP-4-WARN_INIT

4 IP

VRRP-4-WARN_REGISTER

4 IP

VRRP-4-WARN_SHMEM_RESET

4 IP

VRRP-4-WARN_TRAFFIC_SLAVE

4 IP

VRRP-6-INFO_STATECHANGE

6 IP

EAGLE-7-ERR_MSG

7 L1

PLIM_OC3-2-ERR_HW_RESTART

2 L1

PLIM_OC3-3-ERR_INIT

3 L1

PLIM_OC3-3-ERR_TIMER

3 L1

PLIM_OC3-4-ERR_DEBUG

4 L1

PMENGINE-4-TCA

4 L1

TREX_LIB-3-MSG_SEND_FAILED

3 L1

TREX_LIB-7-DEBUG

7 L1

TREX-2-HW_FATAL_ERROR

2 L1

TREX-2-SW_FATAL_ERROR

2 L1

TREX-3-BOARD_PLL_ERROR

3 L1

TREX-3-HW_NONFATAL_ERROR

3 L1

TREX-3-PLL_ERROR

3 L1

TREX-5-NOTICE

5 L1

TREX-6-INFO

6 L1

UT2-7-ERR_MSG

7 L1

XENA-2-HW_FATAL_ERROR

2 L1

XENA-2-SW_FATAL_ERROR

2 L1

XENA-3-ERR_SPA_UNSUPPORTED

3 L1

XENA-5-NOTICE

5 L1

10GE_PLIM-2-RX_FAULT

2 L2

10GE_PLIM-2-RX_UNKNOWN

2 L2

10GE_PLIM-2-STARTUP

2 L2

10GE_PLIM-2-UNSUP

2 L2

10GE_PLIM-2-XGXS_RX_SYNC

2 L2

10GE_PLIM-2-XGXS_TX_SYNC

2 L2

10GE_PLIM-3-FAULTY_XFP

3 L2

10GE_PLIM-3-OIM_ERR

3 L2

10GE_PLIM-4-INVALID_MAC

4 L2

10GE_PLIM-4-RX_LOSS

4 L2

10GE_PLIM-4-RX_RF

4 L2

10GE_PLIM-6-ERR_UPGRADE

6 L2

10GE_PLIM-6-OIM_OIR

6 L2

10GE_PLIM-6-UNSUPPORTED_XENPAK

6 L2

10GE_PLIM-6-UNSUPPORTED_XFP

6 L2

10GE_PLIM-6-XFP_RETRY_READ

6 L2

ACCT_SVR-3-ADDRESS_MOVED

3 L2

ACCT_SVR-3-ERR_INIT

3 L2

ACCT_SVR-3-ERR_INTERNAL

3 L2

ACCT_SVR-3-INIT

3 L2

ACCT_SVR-3-INTERNAL

3 L2

ACCT_SVR-3-NH_SHM_INIT

3 L2

ACCT_SVR-3-NH_SHM_MALLOC

3 L2

ACCT_SVR-3-SHM_POOL_CREATE

3 L2

ACCT_SVR-4-HFA_CLK_DELTA_FAIL

4 L2

ACCT_SVR-4-HFA_CLK_DELTA_FAIL

4 L2

ACCT_SVR-7-ISR_FIFO_USAGE_FLAG

7 L2

ACCT_SVR-7-ISR_FIFO_USAGE_FLAG

7 L2

ALPHA_TCAM-3-ERROR_MSG

3 L2

ALPHA-3-ERR_ACCESS

3 L2

ALPHA-3-ERROR_MSG

3 L2

ALPHA-3-SDRAM_ASSERT

3 L2

ALPHA-4-THREAD_INFO_MSG

4 L2

ALPHA-5-MCAST_DISABLE_INFO_MSG

5 L2

ALPHA-6-TUPLE_WARNING

6 L2

ALPHA-6-VERSION_WARNING

6 L2

ALPHA-7-INFO_MSG

7 L2

ALPHA-7-PHB_DUMP

7 L2

ALPHA-7-REG_DUMP

7 L2

ASIC_ERRORS-7-ERR_ECM_CREATE

7 L2

ASIC_ERRORS-7-ERR_ECM_CREATE

7 L2

ASIC_ERRORS-7-ERR_ECM_CREATE

7 L2

ASIC_ERRORS-7-ERR_ECM_CREATE

7 L2

ASIC_ERRORS-7-ERR_ECM_REG

7 L2

ASIC_ERRORS-7-ERR_ECM_REG

7 L2

ASIC_ERRORS-7-ERR_ECM_REG

7 L2

ASIC_ERRORS-7-ERR_ECM_REG

7 L2

ASIC_ERRORS-7-ERR_SYSDB

7 L2

ASIC_ERRORS-7-ERR_SYSDB

7 L2

ASIC_ERRORS-7-ERR_SYSDB

7 L2

ASIC_ERRORS-7-ERR_SYSDB

7 L2

ASIC_ERRORS-7-ERR_SYSDB_BAG_ENCODE

7 L2

ASIC_ERRORS-7-ERR_SYSDB_BAG_ENCODE

7 L2

ASIC_ERRORS-7-ERR_SYSDB_BAG_ENCODE

7 L2

ASIC_ERRORS-7-ERR_SYSDB_BAG_ENCODE

7 L2

ASIC_ERRORS-7-ERR_SYSDB_EDM_REG

7 L2

ASIC_ERRORS-7-ERR_SYSDB_EDM_REG

7 L2

ASIC_ERRORS-7-ERR_SYSDB_EDM_REG

7 L2

ASIC_ERRORS-7-ERR_SYSDB_EDM_REG

7 L2

ASIC_SCAN_EXEC-2-START

2 L2

ASIC_SCAN_SERVER-2-COMPLETE

2 L2

ASIC_SCAN_SERVER-2-EXIT

2 L2

ASIC_SCAN_SERVER-2-NODE_BRINGDOWN

2 L2

ASIC_SCAN_SERVER-2-START

2 L2

ASIC_SCAN_SERVER-2-XSVF_ERROR

2 L2

ASIC_SCAN_SERVER-7-ERR_EVM_CREATE

7 L2

ASIC_SCAN_SERVER-7ERR_GET_CARD_TYPE

7 L2

ASIC_SCAN_SERVER-7-ERR_INIT

7 L2

ASIC_SCAN_SERVER-7-ERR_IO

7 L2

ATM_ILMI-2-IM_MSG

2 L2

ATM_ILMI-2-INTERNAL_MSG

2 L2

ATM_ILMI-2-SYSDB_MSG

2 L2

ATM_INARP-2-INTERNAL_FAILURE

2 L2

ATM_INARP-2-NOMEM

2 L2

ATM_NETIO-3-CARD_DLL

3 L2

ATM_NETIO-3-INSERT_DICT

3 L2

ATM_NETIO-3-INVALID_DLL

3 L2

ATM_NETIO-3-LOAD_PATH

3 L2

ATM_NETIO-3-MEMORY

3 L2

ATM_NETIO-3-PARSE_FAILURE

3 L2

ATM_NETIO-3-PARSER_NULL_PATH

3 L2

ATM_NETIO-6-DEBUG_REG

6 L2

ATM_OAM-2-IM_ERR

2 L2

ATM_OAM-2-INTERNAL_ERR

2 L2

ATM_OAM-2-SYSDB_ERR

2 L2

ATM_RM-1-SYSDB_MSG

1 L2

ATM_RM-2-INTERNAL_MSG

2 L2

ATM_RM-2-NOMEM

2 L2

ATM_RM-4-BANDWIDTH_MSG

4 L2

ATM_SAAR-2-INIT

2 L2

ATM_SAAR-6-DEBUG_REG

6 L2

ATM_SOCKET-2-EVM_ERR_INIT

2 L2

ATM_SOCKET-2-MSG_ERR_GET

2 L2

ATM_SOCKET-2-NOMEM

2 L2

ATM_SOCKET-2-PAK_CLNT_ERR_CLNUP

2 L2

ATM_SOCKET-3-RESMGR_ATTACH

3 L2

ATM_SOP-3-INTR

3 L2

ATM_SOP-7-DEBUG

7 L2

ATM_VCM-2-DEMUX_LIMIT

2 L2

ATM_VCM-2-IM_ERR

2 L2

ATM_VCM-2-INTERNAL_ERR

2 L2

ATM_VCM-2-SYSDB_ERR

2 L2

ATM_VCM-3-SYSDB_REG

3 L2

ATM_VCM-4-SIGFAULT

4 L2

ATM_VCM-5-CTT_MGR_INIT

5 L2

ATM_VCM-6-ATM_PCI

6 L2

ATM_VCM-6-FUNC_ENTRY

6 L2

ATM_VCM-6-IM_IFTYPE

6 L2

atmdrv-2-ERR

2 L2

atmdrv-2-ERR

2 L2

atmdrv-2-ERR_ENCAP

2 L2

atmdrv-2-ERR_STS

2 L2

atmdrv-2-ERR_STS

2 L2

atmdrv-2-ERR_VC

2 L2

atmdrv-2-INIT_FAILURE

2 L2

atmdrv-2-STS_DLL_FAILURE

2 L2

atmdrv-3-cpk_err

3 L2

atmdrv-4-warning

4 L2

atmdrv-7-db_dump

7 L2

ATMGCMGR-2-DBG_INIT

2 L2

ATMGCMGR-2-INIT

2 L2

atmnetio-3-DATAGRAM_ADJUST_FAILURE

3 L2

AUTO_IP_RING-5-DUPL_AUTOIP_ADDRESS

5 L2

AUTO_IP_RING-5-EQUAL_AUTOIP_PRIORITY

5 L2

B_SHIM_PARTNER-3-CAP_ADD_ERR

3 L2

B_SHIM_PARTNER-3-CAP_CNTL_ERR

3 L2

B_SHIM_PARTNER-3-ECM_INIT_FAILED

3 L2

B_SHIM_PARTNER-3-SET_CALLBACK_ERR

3 L2

B_SHIM_PARTNER-3-SVR_BIND_ERR

3 L2

B_SHIM_PARTNER-3-SVR_UBIND_ERR

3 L2

BFD_SSE-3-ERR_AIB_INIT

3 L2

BFD_SSE-3-ERR_CCI_INIT

3 L2

BFD_SSE-3-ERR_CERR_REG

3 L2

BFD_SSE-3-ERR_ECM_CREATE

3 L2

BFD_SSE-3-ERR_ECM_NOTIFY

3 L2

BFD_SSE-3-ERR_INTERNAL

3 L2

BFD_SSE-3-ERR_ISB_INIT

3 L2

BFD_SSE-3-ERR_LTRACE

3 L2

BFD_SSE-3-ERR_MEM_ALLOC

3 L2

BFD_SSE-3-ERR_SYSDB

3 L2

BFD_SSE-3-ERR_SYSDB_BIND

3 L2

BFD_SSE-3-ERR_SYSDB_EDM_REG

3 L2

BFD_SSE-4-ERR_INTERNAL_WARN

4 L2

BFD_SSE-7-ERR_SYSDB_BAG_ENCODE

7 L2

BFD-3CHANGE_ECHO_SOURCE_ADDRESS_FAILED

3 L2

BFD-3PROT_BFD_SESSION_DOWN_MESSAGE_LOS
T

3 L2

BFD-3-PROT_SERVER_INIT_FAILURE

3 L2

BFD-3REVERT_ECHO_SOURCE_ADDRESS_FAILED

3 L2

BFD-3REVERT_ECHO_SOURCE_ADDRESS_SUCCES
S

3 L2

BFD-4ASYNC_DETECT_TIMER_FAULTY_EXPIRY

4 L2

BFD-4RATE_LIMIT_WARNING_HIGH_WATERMARK

4 L2

BFD-4RATE_LIMIT_WARNING_LOW_WATERMARK

4 L2

BFD-4RATE_LIMIT_WARNING_MP_HIGH_WATERMA
RK

4 L2

BFD-4RATE_LIMIT_WARNING_MP_LOW_WATERMAR
K

4 L2

BFD-4-RESOURCE_LEAK

4 L2

BFD-6-ADJACENCY_DELETE

6 L2

BFD-6-FIB_NOT_READY

6 L2

BFD-6-MAX_AGENT_SESSIONS_EXCEEDED

6 L2

BFD-6-PROT_SERVER_INIT_SUCCESS

6 L2

BFD-6-SESSION_BUNDLE_ALL_MEMBER_OFF

6 L2

BFD-6-SESSION_BUNDLE_ALL_MEMBER_ON

6 L2

BFD-6-SESSION_BUNDLE_NO_ECHO

6 L2

BFD-6-SESSION_BUNDLE_NO_ECHO_CLR

6 L2

BFD-6-SESSION_DAMPENING_CLR

6 L2

BFD-6-SESSION_INHERIT_OFF

6 L2

BFD-6-SESSION_INHERIT_ON

6 L2

BFD-6-SESSION_NO_RESOURCES

6 L2

BFD-6-SESSION_NO_RESOURCES_CLR

6 L2

BFD-6-SESSION_REMOVED

6 L2

BFD-6-SESSION_STATE_DOWN
BFD-6-SESSION_STATE_UP

6 L2
6 L2

BFD-6-SESSION_VERSION_CHANGE

6 L2

BGP_AD-3-OUT_OF_LABEL

3 L2

BM_PD-3-DLL_CERRNO

3 L2

BM_PD-3-DLL_CERRNO

3 L2

BM_PD-3-DLL_CERRNO

3 L2

BM_PD-3-DLL_CERRNO

3 L2

BM_PD-3-DLL_CERRNO_REG_FAIL

3 L2

BM_PD-3-DLL_INIT

3 L2

BM_PD-3-DLL_INIT

3 L2

BM_PD-3-DLL_INIT

3 L2

BM_PD-3-DLL_INIT

3 L2

BM_PD-3-DLL_INIT

3 L2

BM_PD-3-DLL_INIT_FAIL

3 L2

BM_PD-3-DLL_TRACE

3 L2

BM_PD-3-DLL_TRACE

3 L2

BM_PD-3-DLL_TRACE

3 L2

BM_PD-3-DLL_TRACE

3 L2

BM_PD-3-DLL_TRACE

3 L2

BM_PD-3-DLL_TRACE_FAIL

3 L2

BM_PD-4-BASE_MAC

4 L2

BM_PD-4-ERR_ADJ_CMPL_DLL_INIT

4 L2

BM_PD-4-ERR_ADJ_DLL_INIT

4 L2

BM_PD-4-ERR_ADJ_DLL_INIT

4 L2

BM_PD-4-ERR_ADJ_DLL_INIT

4 L2

BM_PD-4-ERR_ADJ_DLL_INIT

4 L2

BM_PD-4-ERR_ADJ_DLL_INIT

4 L2

BM_PD-4-ERR_INIT

4 L2

BM_PD-4-ERR_INIT

4 L2

BM_PD-4-ERR_INIT

4 L2

BM_PD-4-ERR_INIT

4 L2

BM_PD-4-ERR_INT

4 L2

BM_PD-6-INFO_MSG

6 L2

BM-3-ERR_ATTR_DECODE

3 L2

BM-4-ERR_ACTIVATE

4 L2

BM-4-ERR_BDL_DATA

4 L2

BM-4-ERR_DB_CHKPT_RECOVER

4 L2

BM-4-ERR_ERRDIS_NOTSUPPORTED

4 L2

BM-4-ERR_EVM_EVENT_BLOCK

4 L2

BM-4-ERR_GLOBAL_OP_RETRY_THRESHOLD

4 L2

BM-4-ERR_GROUP_CREATE

4 L2

BM-4-ERR_IIR_OP

4 L2

BM-4-ERR_INIT

4 L2

BM-4-ERR_LINK_ATTACHED

4 L2

BM-4-ERR_MEM_ALLOC

4 L2

BM-4-ERR_MIB_CLEANUP

4 L2

BM-4-ERR_MIB_INIT

4 L2

BM-4-ERR_NETIO_INIT

4 L2

BM-4-ERR_OP_RETRY_THRESHOLD

4 L2

BM-4-ERR_PAKMAN

4 L2

BM-4-ERR_RECREATE_BUNDLE

4 L2

BM-4-ERR_REPAIR_BUNDLE

4 L2

BM-4-ERR_REPAIR_DATABASE

4 L2

BM-4-ERR_REPLICATE

4 L2

BM-4-ERR_RESYNC_EXCEED_IIR

4 L2

BM-4-ERR_RESYNC_SCHED_IIR

4 L2

BM-4-ERR_RETRY_EXCEED

4 L2

BM-4-ERR_RETRY_EXCEED_GSP

4 L2

BM-4-ERR_RETRY_EXCEED_IMP

4 L2

BM-4-ERR_RETRY_EXCEED_PROTECT

4 L2

BM-4-ERR_RETRY_EXCEED_SYSTEM_MAC

4 L2

BM-4-ERR_SUB_PARENT

4 L2

BM-4-ERR_SYSMGR

4 L2

BM-4-ERR_SYSTEM_MAC_RESET

4 L2

BM-4-ERR_TX_HEAP_LOOKUP

4 L2

BM-4-ERR_TX_TIMER

4 L2

BM-4-ERR_UNREPLICATE

4 L2

BM-4-ERR_VLAN_TAGS

4 L2

BM-4-LINK_ORDER_MISMATCH

4 L2

BM-4-LINK_ORDER_NOT_CONVERGED

4 L2

BM-4-LRD_RESYNC

4 L2

BM-4-SELECTION

4 L2

BM-4-THREAD_PRIORITY

4 L2

BM-5-ACTOR_CHURN

5 L2

BM-5-BUNDLE_COMPATIBILITY

5 L2

BM-5-ERR_MAC_RELEASE

5 L2

BM-5-ERR_TX_ENQUEUE

5 L2

BM-5-LACP_PKT_DELAYED

5 L2

BM-5-LACP_PKT_DROPPED

5 L2

BM-5-LACP_PKT_DROPPED_PTNR

5 L2

BM-5MBR_BFD_NEIGHBOR_UNCONFIGURED

5 L2

BM-5-MBR_BFD_SESSION_DOWN

5 L2

BM-5-MIN_MAX

5 L2

BM-5-MLACP_BUFFER_PARSE_FAILED

5 L2

BM-5-MLACP_CANNOT_SWITCHOVER

5 L2

BM-5-MLACP_CONNECT_FAILED

5 L2

BM-5-MLACP_CORE_ISOLATION

5 L2

BM-5-MLACP_DEVICE_MISCONFIGURATION

5 L2

BM-5MLACP_ITEM_LOCAL_MISCONFIGURATION

5 L2

BM-5MLACP_ITEM_PEER_MISCONFIGURATION

5 L2

BM-5MLACP_RESYNC_INCONSISTENCY_DISCONN
ECT

5 L2

BM-5-MLACP_ROID_MISMATCH

5 L2

BM-5MLACP_UNRESOLVABLE_MISCONFIG_DISCO
NNECT

5 L2

BM-5-PARTNER_CHURN

5 L2

BM-5-RED_MGMT

5 L2

BM-6-ACTIVE

6 L2

BM-6-MBR_BFD_SESSION_UP

6 L2

BM-6-MBR_BFD_STARTING

6 L2

BM-6-MEMBER_COMPATIBILITY

6 L2

BM-6-MLACP_BDL_SYSID_IGNORED

6 L2

BM-6-MLACP_BUNDLE_ACTIVE

6 L2

BM-6-MLACP_BUNDLE_MAC_ARBITRATION

6 L2

BM-6-MLACP_BUNDLE_PEERING

6 L2

BM-6-MLACP_CONNECT

6 L2

BM-6-MLACP_DISCONNECT

6 L2

BM-6-MLACP_INVALID_PRIORITY_REQUEST

6 L2

BM-6-MLACP_SYSTEM_ID_ARBITRATION

6 L2

BM-6-SATELLITE_COMPATIBILITY

6 L2

BM-7-MLACP_TLV_CAPTURE_STOPPED

7 L2

BMP-3-DLL_INIT

3 L2

BMP-3-DLL_TRACE

3 L2

BMP-4-BASE_MAC

4 L2

BMP-4-DB_ATTACH

4 L2

BMP-4-ERR_ADJ_DLL_INIT

4 L2

BMP-4-ERR_INIT

4 L2

BVI_MA-3-INIT_ERR

3 L2

C_SHIM_PARTNER-3-AIB_INIT_FAILED

3 L2

C_SHIM_PARTNER-3-AIB_INIT_FAILED

3 L2

C_SHIM_PARTNER-3-CAP_ADD_ERR

3 L2

C_SHIM_PARTNER-3-CAP_ADD_ERR

3 L2

C_SHIM_PARTNER-3-CAP_CNTL_ERR

3 L2

C_SHIM_PARTNER-3-CAP_CNTL_ERR

3 L2

C_SHIM_PARTNER-3-CAP_LKP_ERR

3 L2

C_SHIM_PARTNER-3-CAP_LKP_ERR

3 L2

C_SHIM_PARTNER-3-ECM_INIT_FAILED

3 L2

C_SHIM_PARTNER-3-ECM_INIT_FAILED

3 L2

C_SHIM_PARTNER-3-SET_CALLBACK_ERR

3 L2

C_SHIM_PARTNER-3-SET_CALLBACK_ERR

3 L2

C_SHIM_PARTNER-3-SVR_UBIND_ERR

3 L2

C_SHIM_PARTNER-3-SVR_UBIND_ERR

3 L2

C_SHIM_PARTNER-4-SVR_BIND_ERR

4 L2

C_SHIM_PARTNER-4-SVR_BIND_ERR

4 L2

C_SHIM_PARTNER-7-IFH_ERR

7 L2

C_SHIM_PARTNER-7-IFH_ERR

7 L2

C_SHIM_PARTNER-7-IM_CALLBACK_ERR

7 L2

C_SHIM_PARTNER-7-IM_CALLBACK_ERR

7 L2

C12000_FR-3-SUBIF_COUNT

3 L2

CCL-3-INIT_ERROR

3 L2

CDP-3-ERR_CONN

3 L2

CDP-3-ERR_IM_ATTR_REGISTRATION

3 L2

CDP-3-ERR_IM_CAPS_ADD

3 L2

CDP-3-ERR_IM_CAPS_REMOVE

3 L2

CDP-3-ERR_IM_MTU_REGISTER

3 L2

CDP-3-ERR_IM_STATE_REGISTER

3 L2

CDP-3-ERR_INTF_INIT

3 L2

CDP-3-ERR_INTF_STATS

3 L2

CDP-3-ERR_IPV4_ADDRESS_SCAN

3 L2

CDP-3-ERR_IPV4_REGISTRATION

3 L2

CDP-3-ERR_IPV6_ADDRESS_SCAN

3 L2

CDP-3-ERR_IPV6_REGISTRATION

3 L2

CDP-3-ERR_NO_MEM

3 L2

CDP-3-ERR_STATS

3 L2

CDP-3-STALE_TLV

3 L2

CDP-4-DUPLEX_MISMATCH

4 L2

CDP-4-ERR_MULTICAST_ADDR_SET

4 L2

CDP-4-ERR_TABLE_RESIZE

4 L2

CDP-4-NEIGHBOR_LIMIT

4 L2

CDP-4-NO_KNOWN_MEDIA

4 L2

CDP-4-NO_KNOWN_MEDIA_DRIVERS

4 L2

CDP-4-WARN_INIT

4 L2

CDP-4-WARN_TERM

4 L2

CDP-6-DELETED_NEIGHBOR

6 L2

CDP-6-NEW_NEIGHBOR

6 L2

CEM_PLATFORMS-2-ERR

2 L2

CEM_PLATFORMS-2-ERR_HEX

2 L2

CEM_PLATFORMS-2-ERR_IFH_STS

2 L2

CEM_PLATFORMS-2-ERR_INT

2 L2

CEM_PLATFORMS-2-ERR_STR

2 L2

CEM_PLATFORMS-2-ERR_STS

2 L2

CEM-2-WAVL_DELETE_FAILED

2 L2

CEM-3-CLASS_FAIL

3 L2

CEM-3-INIT

3 L2

CEM-3-STATS_CALLOC_FAILED

3 L2

CEM-6-CNTRLR_INHERITED

6 L2

CEM-6-PARAM_NOT_COMPATIBLE

6 L2

CEM-6-PARAM_NOT_IN_RANGE

6 L2

CEM-6-PAYLOAD_NOT_MULTIPLE

6 L2

CEMA-3-FATAL_ERR

3 L2

CEMA-3-MISMATCH_ERR

3 L2

CEMA-3-UNSUPPORTED_ERR

3 L2

CEMA-4-GEN_ERR

4 L2

CFM-3-AIS_GEN_ERROR

3 L2

CFM-3-AIS_GEN_TIMER

3 L2

CFM-3-CCI_TIMER

3 L2

CFM-3-CCM_GEN_ERROR

3 L2

CFM-3-CCM_SEND_ERROR

3 L2

CFM-3-CFG_APPLY_FAILED

3 L2

CFM-3-CFG_ATTR_UPDATE_FAILED

3 L2

CFM-3-CFG_DELETED_INTF_OP

3 L2

CFM-3-CFG_MP_CREATE_FAILED

3 L2

CFM-3-CFG_MP_UPDATE_INCONSISTENCY

3 L2

CFM-3-CFG_SLA_INST_FAILED

3 L2

CFM-3-CFG_XC_MEP_CREATE_FAILED

3 L2

CFM-3-DB_DELETE_FAILED

3 L2

CFM-3-DB_INCONSISTENT

3 L2

CFM-3-DB_LOCK_ERROR

3 L2

CFM-3-EA_ERROR

3 L2

CFM-3-ECM_RETRY_ERROR

3 L2

CFM-3-ELO_LB_STATE

3 L2

CFM-3-ENCAP_ERROR

3 L2

CFM-3-ENGINE_TIMER

3 L2

CFM-3-FAULT_NOTIFICATION

3 L2

CFM-3-INV_DEBUG_FLTR

3 L2

CFM-3-L2FIB_ERROR

3 L2

CFM-3-LWM_ERROR

3 L2

CFM-3-MEPS_DELETE_CCM_GEN

3 L2

CFM-3-MP_DB_ALLOC

3 L2

CFM-3-OUT_OF_MEMORY

3 L2

CFM-3-OUT_OF_MEMORY_UNKNOWN_SIZE

3 L2

CFM-3-PAK_ERROR

3 L2

CFM-3-RETRY_EXCEEDED

3 L2

CFM-3-STATE_UPDATE_DROPPED

3 L2

CFM-3-WL_QUEUE_FAILED

3 L2

CFM-4-AIS_EXPIRY_TIMER

4 L2

CFM-4-BD_BATCH_DELETE_FAILED

4 L2

CFM-4-CCM_PARSE_FAILED

4 L2

CFM-4-CFG_INCONSISTENT

4 L2

CFM-4-EFD_SHUTDOWN_ERROR

4 L2

CFM-4-ELMI_UPDATE_FAILED

4 L2

CFM-4-ENCAP_CHANGE

4 L2

CFM-4-ENCAP_CONFLICT

4 L2

CFM-4-EXIT_FAILED

4 L2

CFM-4-INIT_FAILED

4 L2

CFM-4-LOSS_TIMER_FAILED

4 L2

CFM-4-LOST_EVENT

4 L2

CFM-4-MIB_CHKPT_BATCH_ERROR

4 L2

CFM-4-MIB_CHKPT_ITEM_ERROR

4 L2

CFM-4-NOTIFY_AIS_FAILED

4 L2

CFM-4-NOTIFY_LOSS_FAILED

4 L2

CFM-4-OFFLOAD_DECODE_FAILED

4 L2

CFM-4-PACKET_DECODE_FAILED

4 L2

CFM-4-PACKET_DECODE_UNEXPECTED_TLV

4 L2

CFM-4-RCV_REGISTER

4 L2

CFM-4-SATELLITE_LMEP_CREATE_FAILED

4 L2

CFM-4-SATELLITE_LMEP_DELETE_FAILED

4 L2

CFM-4-SATELLITE_LMEP_UNPROG_FAILED

4 L2

CFM-4-SLR_FAILED

4 L2

CFM-4-SPIO_WARNING

4 L2

CFM-5-CCM_ERROR_CCMS_MISSED

5 L2

CFM-5-CCM_ERROR_COUNTER_WRAPPED

5 L2

CFM-5-SOME_SATELLITES_NOT_RESYNCED

5 L2

CFM-6-AIS_LCK_CHANGE

6 L2

CFM-6-CC_ERROR

6 L2

CFM-6-EFD_CHANGE

6 L2

CFM-6-MEP_CHANGE

6 L2

CFM-6-SHMWIN_RESET

6 L2

CFM-6-TOO_MANY_TLVS

6 L2

CFM-6-XC_ERROR

6 L2

CFMMIB-3-NO_DEBUG

3 L2

CFMMIB-3-NO_STACK

3 L2

CFMMIB-3-NO_TRAP

3 L2

CHDLC_EA-4-ERR_EVM_EVENT_BLOCK

4 L2

CHDLC_EA-4-ERR_INIT

4 L2

CHDLC_EA-6-ERR_IMC_MULTIPLE_NTFCNS

6 L2

CHDLC_MA-3-INTF_UP_DOWN

3 L2

CHDLC_MA-3-SYSMGR_SOCK_FEAT_START

3 L2

CHDLC_MA-4-ERR_EVM_EVENT_BLOCK

4 L2

CHDLC_MA-4-ERR_INIT

4 L2

CHDLC_MA-4-ERR_PKT_API_HANDLER

4 L2

CHDLC_MA-4-ERR_PKT_HANDLER

4 L2

CHDLC_MA-4-ERR_THREAD

4 L2

CHDLC_MA-6-ERR_IM_MULTIPLE_NTFCNS

6 L2

CHDLC_SOCK-4-ERR_EVM_EVENT_BLOCK

4 L2

CHDLC_SOCK-4-ERR_INIT

4 L2

CHDLC_SOCK-4-ERR_PAKMAN_CORRUPTION

4 L2

CHDLCDLL-3-ERR_DEBUG_REGISTER

3 L2

CHDLCDLL-3-ERR_PKT_ENCAP

3 L2

CHDLCDLL-3-ERR_TRACE_REGISTER

3 L2

CHIPs-2-error

2 L2

CHNLZD_EFCM-3ERROR_CFG_BUFF_MAP_MEMORY

3 L2

CHNLZD_EFCM-3ERROR_CFG_BUFF_OPEN_MEMORY

3 L2

CHNLZD_EFCM-3ERROR_COMM_ERR_SET_EFC_ENTRY

3 L2

CHNLZD_EFCM-3ERROR_COMM_SPA_CLIENT_INIT

3 L2

CHNLZD_EFCM-3ERROR_EINVAL_SET_CALENDAR_ENTRY

3 L2

COMMS-3-MSG_DROPPED

3 L2

COMMS-3-MY_ID_MISMATCH

3 L2

COMMS-3-MY_SAVE_FAILED

3 L2

COMMS-3-SAVE_FAILED

3 L2

COMMS-4-DUPLICATE_ENTRY

4 L2

CPP_EXMEM-6-THRESHOLD_CLEAR

6 L2

CPP_EXMEM-6-THRESHOLD_DECLARE

6 L2

cpp_sbs-3-BLOCK_SERVC_FAILR

3 L2

CPP_TCAM_RM-3-LOG_FAILURE

3 L2

CPP_TCAM_RM-3-MSG_SEND_FAILED

3 L2

CPP_TCAM_RM-3-NONFATAL_ERR

3 L2

CPP_TCAM_RM-6-INFO_MSG

6 L2

CPPHA-3-CDMDONE

3 L2

CPPHA-3-FAILURE

3 L2

CPPHA-3-FAULT

3 L2

CPPHA-3-FAULTCRASH

3 L2

CPPHA-3-FAULTRATE

3 L2

CPPHA-3-INITFAIL

3 L2

CPPHA-3-NOCDM

3 L2

cpposlib-3-CLEAN_NOTIFY

3 L2

cpposlib-3-ERROR_NOTIFY

3 L2

cpposlib-3-INIT_NOTIFY

3 L2

CRS_PAK_BUFHDR-3PACKET_LENGTH_EXCEED_FABRIC_LIMIT

3 L2

d1qnetio-3-CHAIN_BUILDER_FAILED

3 L2

d1qnetio-3-IDB_NOT_FOUND

3 L2

d1qnetio-3-REGISTRY_CREATION_FAILED

3 L2

d1qnetio-3-SUBBLOCK_REG_FAILED

3 L2

d1qnetio-3-TRACE_INIT_ERROR

3 L2

d1qnetio-4-CHAIN_UNBUILDER_FAILED

4 L2

d1qnetio-4-DEBUG_INIT_ERROR

4 L2

d1qnetio-4-DEVCTL_NOT_SUP

4 L2

d1qnetio-4-TERM_FAILED

4 L2

DATAPATH_FPGA_API-7-ERR

7 L2

DATAPATH_FPGA_API-7-ERROR

7 L2

DIV2_DM-3-INFO

3 L2

DIV2_DM-3-INIT

3 L2

DIV2_DM-3-NO_MEM

3 L2

DRIVERS_UTIL-3-TUPLE_READ_FAILED

3 L2

DWDM-3-DEBUG_INIT_FAILED

3 L2

DWDM-3-INFO

3 L2

DWDM-3-NODEID

3 L2

DWDM-3-NOT_YET_IMPLEMENTED

3 L2

DWDM-4-FORCED_MAINTENANCE

4 L2

DWDM-5-MAINTENANCE_DISABLED

5 L2

DWDM-5-SRLG_OVERFLOW

5 L2

DWDM-6-CLEAR_COUNTERS

6 L2

DWDM-6-PP_EVENT_INJECT

6 L2

DWDM-7-SET_WAVELENGTH

7 L2

DWDM-7-STALE_WAVELENGTH

7 L2

DYNNIC_API-3-MULTIPLE_DRIVER_CFG

3 L2

DYNNIC-2-INIT_FAILED

2 L2

E3EGRESSQ-3-ERR_MEM_ALLOC

3 L2

E3EGRESSQ-3-ERR_THREAD_MUTEX_LOCK

3 L2

E3EGRESSQ-3ERR_THREAD_MUTEX_UNLOCK

3 L2

E3EGRESSQ-3-MEM_MAP

3 L2

E3EGRESSQ-3-RECONFIG

3 L2

E3EGRESSQ-4-ERR_MEM_ALLOC_SHMWIN

4 L2

E3EGRESSQ-4-ERR_MEM_FREE

4 L2

E3EGRESSQ-4ERR_MEM_MQS_COUNTER_THR_EXCEEDED

4 L2

E3EGRESSQ-4-ERR_MUTEX_INIT

4 L2

E3EGRESSQ-4-ERR_MUTEX_REVIVE

4 L2

E3EGRESSQ-4-ERR_PLATFORM_INFO

4 L2

E3EGRESSQ-4-INTERRUPT

4 L2

E3EGRESSQ-4MEM_INVALID_MQS_COUNTER_MAXTHR

4 L2

E3EGRESSQ-4MEM_INVALID_MQS_COUNTER_MINTHR

4 L2

E3EGRESSQ-4MEM_MQS_MAXTHR_NOT_MATCHING_CURR
_MINTHR

4 L2

E3EGRESSQ-4MEM_MQS_MINTHR_NOT_MATCHING_CURR_
MAXTHR

4 L2

E3EGRESSQ-6ERR_MEM_MQS_COUNTER_THR_NORMAL

6 L2

E3INGRESSQ-3-RECONFIG

3 L2

E3INGRESSQ-4-INTERRUPT

4 L2

E5EGRESSQ-3-RECONFIG

3 L2

E5EGRESSQ-4ERR_MEM_MQS_COUNTER_THR_EXCEEDED

4 L2

E5EGRESSQ-4-ERROR

4 L2

E5EGRESSQ-4-INTERRUPT

4 L2

E5EGRESSQ-4MEM_INVALID_MQS_COUNTER_MAXTHR

4 L2

E5EGRESSQ-4MEM_INVALID_MQS_COUNTER_MINTHR

4 L2

E5EGRESSQ-4MEM_MQS_MAXTHR_NOT_MATCHING_CURR
_MINTHR

4 L2

E5EGRESSQ-4MEM_MQS_MINTHR_NOT_MATCHING_CURR_
MAXTHR

4 L2

E5EGRESSQ-6ERR_MEM_MQS_COUNTER_THR_NORMAL

6 L2

E5INGRESSQ-3-RECONFIG

3 L2

E5INGRESSQ-4-INTERRUPT

4 L2

edge_l2fwd_rewrite-2-FM_ADD_FEAT_ERR

2 L2

edge_l2fwd_rewrite-2-FM_DEL_FEAT_ERR

2 L2

edge_l2fwd_rewrite-2FWD_FEAT_NOT_SUPPORTED

2 L2

edge_l2fwd_rewrite-2FWD_MEMMGR_READ_ERR

2 L2

edge_l2fwd_rewrite-2-HFA_CREATE_ERR

2 L2

edge_l2fwd_rewrite-2-HFA_PROG_ERR

2 L2

edge_l2fwd_rewrite-2-HFA_REGISTER_ERR

2 L2

edge_l2fwd_rewrite-2INSERT_ENCAP_STRING_ERR

2 L2

edge_l2fwd_rewrite-2-MEM_REG_ERR

2 L2

edge_l2fwd_rewrite-2-PLU_FREE_ERR

2 L2

edge_l2fwd_rewrite-2-PLU_MALLOC_ERR

2 L2

edge_l2fwd_rewrite-2-PLU_WRITE_ERR

2 L2

edge_l2fwd_rewrite-2REMOVE_ENCAP_STRING_ERR

2 L2

edge_l2fwd_rewrite-2-RM_INIT_ERR

2 L2

edge_l2fwd_rewrite-2-TLU_FREE_ERR

2 L2

edge_l2fwd_rewrite-2-TLU_MALLOC_ERR

2 L2

edge_l2fwd_rewrite-2-TLU_SIZE_ERR

2 L2

edge_l2fwd_rewrite-2-TLU_WRITE_ERR

2 L2

edge_l2fwd_rewrite-2-UIDB_READ_ERR

2 L2

edge_l2fwd_rewrite-2-UIDB_SET_ERR

2 L2

edge_l2fwd_rewrite-2-XBMA_ADD_ERR

2 L2

edge_l2fwd_rewrite-2-XBMA_CONN_ERR

2 L2

edge_l2fwd_rewrite-2-XBMA_DEL_ERR

2 L2

edge_l2fwd_rewrite-2-XBMA_INIT_ERR

2 L2

edge_l2fwd_rewrite-3-UTIL_ASSERT

3 L2

edge_l2fwd_table-2-FAD_DEL_ERR

2 L2

edge_l2fwd_table-2-FAD_INIT_ERR

2 L2

edge_l2fwd_table-2-FAD_INSERT_ERR

2 L2

edge_l2fwd_table-2FAD_REGION_PROG_ERR

2 L2

edge_l2fwd_table-2FAD_TCAM_FORMAT_PROG_ERR

2 L2

edge_l2fwd_table-2-FAD_UPDATE_ERR

2 L2

edge_l2fwd_table-2-FM_CONFIG_ERR

2 L2

edge_l2fwd_table-2-PLU_MALLOC_ERR

2 L2

edge_l2fwd_table-2-PLU_WRITE_ERR

2 L2

edge_l2fwd_table-2-reg_err

2 L2

edge_l2fwd_table-2-TABLE_MALLOC_ERR

2 L2

edge_l2fwd_table-2-TLU_MALLOC_ERR

2 L2

edge_l2fwd_table-2-TLU_WRITE_ERR

2 L2

edge_l2fwd_table-3-ERR

3 L2

edge_l2fwd_table-3-UTIL_ASSERT

3 L2

EGRESSQ_HW_DLL-3ENQ_PKT_LOGIC_ERROR

3 L2

EGRESSQ_HW_DLL-3-ERR_MEM_ALLOC

3 L2

EGRESSQ_HW_DLL-3-ERR_MEM_ALLOC

3 L2

EGRESSQ_HW_DLL-3FAIL_TO_GET_BP_MAP_FROM_PLIM_AISC

3 L2

EGRESSQ_HW_DLL-3-FCRAM_BIST_FAILURE

3 L2

EGRESSQ_HW_DLL-3FORWARD_PACKET_TO_UNALLOCATED_QUE
UE

3 L2

EGRESSQ_HW_DLL-3-HW_ERROR

3 L2

EGRESSQ_HW_DLL-3-HW_ERROR

3 L2

EGRESSQ_HW_DLL-3-IMDR_MAP_ERROR

3 L2

EGRESSQ_HW_DLL-3-IO_ERROR

3 L2

EGRESSQ_HW_DLL-3NON_ZERO_Q0_COUNTER

3 L2

EGRESSQ_HW_DLL-3-QUEUE_STUCK

3 L2

EGRESSQ_HW_DLL-3QUEUE_STUCK_STATUS_INFO

3 L2

EGRESSQ_HW_DLL-3RLDRAM_BIST_FAILURE

3 L2

EGRESSQ_HW_DLL-3SBE_THRESHOLD_EXCEED

3 L2

EGRESSQ_HW_DLL-3UNALLOCATED_QUEUE_NOT_EMPTY

3 L2

EGRESSQ_HW_DLL-3UNALLOCATED_QUEUE_NOT_EMPTY

3 L2

EGRESSQ_HW_DLL-6-INFO_MSG

6 L2

EGRESSQ_HW_DLL-6-INFO_MSG

6 L2

EGRESSQ_HW_DLL-6-QDR_BIST_FAILURE

6 L2

EGRESSQ_HW_DLL-7-ERR_EVM_FAIL

7 L2

EGRESSQ_HW_DLL-7-ERR_INTERNAL

7 L2

EGRESSQ_HW_DLL-7-ERR_INTERNAL

7 L2

EGRESSQ_HW_DLL-7-ERR_LWM_FAIL

7 L2

EGRESSQ-3-ERR_CLIENT_REG

3 L2

EGRESSQ-3-ERR_EVM_FAIL

3 L2

EGRESSQ-3-ERR_INCOMPATIBLE_API

3 L2

EGRESSQ-3-ERR_INTERNAL_ASIC

3 L2

EGRESSQ-3-ERR_LWM_FAIL

3 L2

EGRESSQ-3-ERR_MEM_ALLOC

3 L2

EGRESSQ-3-INTERFACE_FAIL

3 L2

EGRESSQ-3-QUEUE_GROUP_FAIL

3 L2

EGRESSQ-3-QUEUE_STUCK

3 L2

EIP-4-DB_ATTACH

4 L2

EIP-4-ERR_INIT

4 L2

EIP-4-LOST_EVENT

4 L2

EIP-4-NOT_SUPP

4 L2

ELMI-4-AIPC

4 L2

ELMI-4-BAG

4 L2

ELMI-4-DEBUG

4 L2

ELMI-4-EVENT

4 L2

ELMI-4-IM

4 L2

ELMI-4-LTRACE

4 L2

ELMI-4-MEM_ALLOC

4 L2

ELMI-4-MGD_TIMER

4 L2

ELMI-4-MTU_WARNING

4 L2

ELMI-4-PROTOCOL_GENERIC

4 L2

ELMI-4-PROTOCOL_INVALID_IE

4 L2

ELMI-4-PROTOCOL_INVALID_MSG_TYPE

4 L2

ELMI-4-PROTOCOL_INVALID_PROTO_VER

4 L2

ELMI-4-RELIABILITY_INVALID_REPORT_TYPE

4 L2

ELMI-4-RELIABILITY_INVALID_SEQ_NUM

4 L2

ELMI-4-RELIABILITY_STATUS_ENQ_TIMEOUT

4 L2

ELMI-4-SYSDB

4 L2

ELMI-4-SYSMGR

4 L2

ELMI-4-WAVL_INIT

4 L2

ELMI-5-EVC_ENCAP_CONFLICT

5 L2

ELMI-5-EVC_IGNORED

5 L2

ELMI-6-PROTOCOL_START_STOP

6 L2

ELMI-6-PROTOCOL_STATE_CHANGE

6 L2

ELO_COMMON-3-SYSMGR_FAIL

3 L2

ELO_COMMON-4-BLOCK_UNTIL_ACTIVE

4 L2

ELO_COMMON-4-PROC_READY_FAILED

4 L2

ELO_COMMON-4-VERIFY_CLEANUP_FAILED

4 L2

ELO_COMMON-4-VERIFY_INIT_FAILED

4 L2

ELO-3-BAD_CONFIG

3 L2

ELO-3-CFG_APPLY_FAILED

3 L2

ELO-3-COULD_NOT_GET_NODEID

3 L2

ELO-3-COULD_NOT_REMOVE_CAPS

3 L2

ELO-3-DAEMON_INIT_FAILED

3 L2

ELO-3-ERRDIS_FAILED

3 L2

ELO-3-EXITING

3 L2

ELO-3-INTF_CAPABILITIES_LOOKUP_FAILED

3 L2

ELO-3-INTF_INIT_FAIL

3 L2

ELO-3-LOOPBACK_SET_FAILED

3 L2

ELO-3-LWM_REPLY_ERROR

3 L2

ELO-3-PACKET_LOCK_ERROR

3 L2

ELO-3PFI_CLEANUP_FAILED_ATTR_UNREGISTER

3 L2

ELO-3-RECEIVE_OAMPDU_FAILED

3 L2

ELO-3-RESYNC_END_ERROR

3 L2

ELO-3-SPIO_MODULE_INIT

3 L2

ELO-4-CHKPT_SAVE_FAILED

4 L2

ELO-4-DAEMON_CLEANUP_FAILED

4 L2

ELO-4-EFD_SHUTDOWN_ERROR

4 L2

ELO-4-INVALID_PLATFORM_EVENT_IFH

4 L2

ELO-4-INVALID_PLATFORM_EVENT_TYPE

4 L2

ELO-4-LOOPBACK_FAILED

4 L2

ELO-4-NOT_IN_LOOPBACK

4 L2

ELO-4-PFI_ERROR

4 L2

ELO-4-SEND_FAILED

4 L2

ELO-4-UNEXPECTED_OAMPDU_RECEIVED

4 L2

ELO-6-CPU_STARVED

6 L2

ELO-6-EFD_CHANGE

6 L2

ELO-6-INTF_CAPABILITIES_CONFLICT

6 L2

ELO-6-INTF_DISCOVERY_TIMEOUT

6 L2

ELO-6-INTF_REMOTE_CRITICAL_EVENT

6 L2

ELO-6-INTF_REMOTE_DYING_GASP

6 L2

ELO-6-INTF_REMOTE_LINK_FAULT

6 L2

ELO-6-INTF_REMOTE_LOOPBACK

6 L2

ELO-6-INTF_SESSION_DOWN

6 L2

ELO-6-INTF_SESSION_UP

6 L2

ELO-6-INTF_THRESHOLD_BREACHED

6 L2

ELO-6-LOOPBACK_CANCEL

6 L2

ELO-6-MISCONFIGURED_INTERFACE

6 L2

ELO-6-MISWIRED

6 L2

ELO-6-NO_PROFILE

6 L2

ELO-6-REMOTE_MASTER_LEFT_LOOPBACK

6 L2

ELO-6-REMOTE_SLAVE_LEFT_LOOPBACK

6 L2

ELO-6-UNEXPECTED_LOOPBACK_STATE

6 L2

ELO-6-UNEXPECTED_STATE

6 L2

ELOGM-4-DEBUG_CLEANUP_FAILED

4 L2

ELOGM-4-DEBUG_INIT_FAILED

4 L2

ELOGM-4-EXITING

4 L2

ELOGM-4-INIT_FAILED

4 L2

EMA-4-ERR_ACTIVATE

4 L2

EMA-4-ERR_EVM_EVENT_BLOCK

4 L2

EMA-4-ERR_INIT

4 L2

EMA-4-ERR_SYSMGR

4 L2

EMA-4-WARN_INVALID_ADDR

4 L2

EMA-4-WARN_INVALID_RANGE

4 L2

EMA-4-WARN_RANGE_RETRIEVAL

4 L2

EMA-5-WARN_INSUF_MAC

5 L2

EPI-3-ATTR_NOTIFY_FAILED

3 L2

EPI-3-DEBUG_INIT_FAILED

3 L2

EPI-3-PKT_OVERFLOW

3 L2

eth_gl-4-EVENT_BLOCK

4 L2

eth_gl-4-INIT_FAILED

4 L2

ETH_LB-3-INITIALIZATION_FAILED

3 L2

ETH_LB-3-INTERNAL_PROBLEM

3 L2

ETH_LB-3-NO_MEMORY_AVAILABLE

3 L2

ETH_LB-4-CONFIG_FAIL_RESUME

4 L2

ETH_LB-4-CONFIG_REMOVAL_FAILED

4 L2

ETH_LB-4-DB_CLEANED_UP_PREMATURELY

4 L2

ETH_LB-4-LOOPBACK_FAIL_RESUME

4 L2

ETH_LB-4-LOST_EVENT

4 L2

ETH_LB-4-SESSION_EXPIRY_FAILED

4 L2

ETH_LB-4-SESSION_IDS_EXHAUSTED

4 L2

ETH_LB-4-SESSION_NOT_STARTED

4 L2

ETH_LB-4-SESSION_NOT_STOPPED

4 L2

ETH_LB-6-SESSION_EXTENDED

6 L2

ETH_LB-6-SESSION_STARTED

6 L2

ETH_LB-6-SESSION_STOPPED

6 L2

ETHER_EA_PLATFORM-3PD_DLL_INIT_FAILED

3 L2

ETHER_NETIO-4-DEBUG_REG

4 L2

ether_spa_dwdm-3-DWDM_ERROR

3 L2

ether_spa_dwdm-3-MALLOC_FAILED

3 L2

ether_spa_dwdm-3-PLL_NOT_LOCKED

3 L2

ether_spa_intr-6-BURST_EVENT

6 L2

ether_spa_mac_error-1-RECOVERY_FAILED

1 L2

ether_spa_mac_error-1-SPA_SHUTDOWN

1 L2

ether_spa_plugin-6-SPARECOVER

6 L2

ether_spa_plugin-6-UNSUPPORTED_OPTICS

6 L2

ETHER-1-CONFIGERROR

1 L2

ETHER-1-IMERROR

1 L2

ETHER-2-CALLOC_FAILED

2 L2

ETHER-2-DEVCTLFAILED

2 L2

ETHER-2-OUTOFMEMORY

2 L2

ETHER-2-SYSDBREGISTERFAILED

2 L2

ETHER-3-BADASYNCEVENT

3 L2

ETHER-3-BDL_IIR_OP_FAILED

3 L2

ETHER-3-DILBFAILED

3 L2

ETHER-3-DPCFAILED

3 L2

ETHER-3-DR_DP83800_IO_INIT_FAILED

3 L2

ETHER-3-EDMERROR

3 L2

ETHER-3-INITFAILED

3 L2

ETHER-3-INVALIDARGSIZE

3 L2

ETHER-3-INVALIDTIMER

3 L2

ETHER-3-RESTARTFAILED

3 L2

ETHER-3-TIMERINITFAILED

3 L2

ETHER-3-UNSUPPORTEDSTATS

3 L2

ETHER-4BUNDLE_MAC_ADDRESS_WARNING

4 L2

ETHER-4-ERR_EVM_EVENT_BLOCK

4 L2

ETHER-4-INIT

4 L2

ETHER-7-BAD_RX_PACKET

7 L2

ETHER-7-BAD_TX_PACKET

7 L2

ETHER-7-INTERRUPT_WITHOUT_VECTOR

7 L2

ETHER-7-MIB_COUNTER_OVERFLOW

7 L2

ETHER-7-RX_FIFO

7 L2

ETHER-7-RX_THRESHOLD

7 L2

ETHER-7-TX_FIFO

7 L2

ETHER-7UNEXPECTED_SOFTWARE_INTERRUPT

7 L2

ETHER-7-UNKNOWN_IRQ

7 L2

ETHERNET-3-INTERFACE_INITIAL

3 L2

ETHERNET-3MAC_ACC_STATS_REGISTRATION

3 L2

ETHERNET-3-MIB_ERROR

3 L2

ETHERNET-3-MIB_INIT_ERROR

3 L2

ETHERNET-3-MTU_IMPOSE_FAILED

3 L2

ETHERNET-3-STATE_FSM

3 L2

ETHERNET-3-TX_DISABLE

3 L2

ETHERNET-4-BER_ALARM

4 L2

ETHERNET-4-INITIALIZATION

4 L2

ETHERNET-4-INTERFACE_CREATE

4 L2

ETHERNET-6-MAC_ACC_NOT_PROGRAMMED

6 L2

ETHERNET-6-MTU_NEAR_HW_LIMIT

6 L2

FB_PLIM-3-ERROR

3 L2

FB_PLIM-3-ERROR_NO_RC

3 L2

FB_PLIM-3-FAIL_READ_CARD

3 L2

FB_PLIM-3-INIT_ERROR

3 L2

FB_PLIM-3-ML_ERROR

3 L2

FB_PLIM-3-ML_PULSE_ERROR

3 L2

FB_SHIM_ENCAP-3-EINVAL

3 L2

FB_SHIM_ENCAP-3-INVALID_CMD

3 L2

FB_SHIM_ENCAP-3-NO_SHIM

3 L2

FB_SHIM_ENCAP-3-UNEXPECTED

3 L2

FHRP_COMMS-3-MSG_DROPPED

3 L2

FHRP_COMMS-3-MY_ID_MISMATCH

3 L2

FHRP_COMMS-3-MY_SAVE_FAILED

3 L2

FHRP_COMMS-3-SAVE_FAILED

3 L2

FHRP_COMMS-4-DUPLICATE_ENTRY

4 L2

FIB_IPV4-3-ADJ_ERROR

3 L2

FIB_IPV4-3-ADJ_ERROR

3 L2

FIB_IPV4-3-ADJ_ERROR

3 L2

FIB_IPV4-3-ADJ_WARNING

3 L2

FIB_IPV4-3-ERR_INFO

3 L2

FIB_IPV4-3-ERR_INFO

3 L2

FIB_IPV4-3-ERR_INFO

3 L2

FIB_IPV4-3-ERR_INFO

3 L2

FIB_IPV4-3-ERR_STR

3 L2

FIB_IPV4-3-ERR_STR

3 L2

FIB_IPV4-3-ERR_STR

3 L2

FIB_IPV4-3-ERR_STR

3 L2

FIB_IPV4-3-ERROR

3 L2

FIB_IPV4-3-ERROR

3 L2

FIB_IPV4-3-ERROR

3 L2

FIB_IPV4-3-ERROR

3 L2

FIB_IPV4-3-GEN_ERR

3 L2

FIB_IPV4-3-OOR_OPER_FAIL

3 L2

FIB_IPV4-3-RDTREE_OPER_FAIL

3 L2

FIB_IPV4-3-TRACE_ERR

3 L2

FIB_IPV4-3-WARNING

3 L2

FIB_IPV4-3-WARNING_INFO

3 L2

FIB_IPV4-3-WARNING_STR

3 L2

FIB_IPV4-5-RECURSIVE_LOOP

5 L2

FIB_IPV4-6-INFO

6 L2

FIB_IPV4-6-INFO

6 L2

FIB_IPV6-3-ADJ_ERROR

3 L2

FIB_IPV6-3-ADJ_WARNING

3 L2

FIB_IPV6-3-ERR_INFO

3 L2

FIB_IPV6-3-ERR_INFO

3 L2

FIB_IPV6-3-ERR_INFO

3 L2

FIB_IPV6-3-ERR_INFO
FIB_IPV6-3-ERR_INFO_VERBOSE

3 L2
3 L2

FIB_IPV6-3-ERR_INFO_VERBOSE

3 L2

FIB_IPV6-3-ERR_INFO_VERBOSE

3 L2

FIB_IPV6-3-ERR_STR

3 L2

FIB_IPV6-3-ERR_STR

3 L2

FIB_IPV6-3-ERR_STR

3 L2

FIB_IPV6-3-ERROR

3 L2

FIB_IPV6-3-ERROR

3 L2

FIB_IPV6-3-ERROR

3 L2

FIB_IPV6-3-ERROR

3 L2

FIB_IPV6-3-GEN_ERR

3 L2

FIB_IPV6-3-WARNING

3 L2

FIB_IPV6-3-WARNING_INFO

3 L2

FIB_IPV6-3-WARNING_STR

3 L2

FIB_IPV6-5-RECURSIVE_LOOP

5 L2

FIB_IPV6-6-INFO

6 L2

FIB_IPV6-6-INFO

6 L2

FIB_MPLS-3-ERR_INFO

3 L2

FIB_MPLS-3-ERR_STR

3 L2

FIB_MPLS-3-ERROR

3 L2

FIB_MPLS-3-WARNING

3 L2

FIB_MPLS-3-WARNING_INFO

3 L2

FIB_MPLS-3-WARNING_STR

3 L2

FR_EDM-2-INIT

2 L2

FR_EDM-3-NO_STATS

3 L2

FR_EDM-3-NOMEM

3 L2

FR_INARP-2-CONNECT_IM

2 L2

FR_INARP-2-INIT

2 L2

FR_INARP-3-IF_VC_CLASS

3 L2

FR_INARP-3-INVALID_FD

3 L2

FR_INARP-3-NOMEM

3 L2

FR_INARP-3-PVC_VC_CLASS

3 L2

FR_INARP-3-SOCKET_SEND

3 L2

FR_INARP-3-UNKNOWN_EVENT

3 L2

FR_INARP-3-UNKNOWN_IDB

3 L2

FR_INARP-4-UNKNOWN_INTFTYPE

4 L2

FR_INARP-4-UNKNOWN_MSG

4 L2

FR_LMI-2-INIT

2 L2

FR_LMI-3-CODEP_ERROR

3 L2

FR_LMI-3-ENCAP

3 L2

FR_LMI-3-FSM_T391_EXPIRY

3 L2

FR_LMI-3-IDB_INIT

3 L2

FR_LMI-3-IDB_SEARCH

3 L2

FR_LMI-3-IM_ERR

3 L2

FR_LMI-3-INVALID_VC

3 L2

FR_LMI-3-KEEPALIVES

3 L2

FR_LMI-3-LINE_STATE

3 L2

FR_LMI-3-MALLOC

3 L2

FR_LMI-3-RECVFROM

3 L2

FR_LMI-3-SENDTO

3 L2

FR_LMI-3-SET_DLCI_STATUS

3 L2

FR_LMI-3-VC_CREATE

3 L2

FR_LMI-3-VCM_VC_STATES

3 L2

FR_LMI-6-CODEP_CHANGE

6 L2

FR_NETIO-3-MEMORY

3 L2

FR_NETIO-6-DEBUG_REG

6 L2

FR_SFRAR-2-INIT

2 L2

FR_SFRAR-3-SYSMGR

3 L2

FR_SOCKET-2-INIT

2 L2

FR_SOCKET-3-CONN

3 L2

FR_SOCKET-3-DPC_FAIL

3 L2

FR_SOCKET-3-NETIO_OUTPUT_FAIL

3 L2

FR_SOCKET-3-NOMEM

3 L2

FR_SOCKET-3-PACKET_CONN

3 L2

FR_SOCKET-3-RESMGR_ATTACH

3 L2

FR_SOCKET-3-SEND_ASYNC

3 L2

FR_SOCKET-3-SYSMGR

3 L2

FR_UV-3-ABORT_ENCAP_FAIL

3 L2

FR_UV-3-EVENT

3 L2

FR_UV-3-INIT

3 L2

FR_UV-3-MISCONFIG

3 L2

FR_UV-3-SYSMGR

3 L2

FR_VCM_EA-2-INIT

2 L2

FR_VCM_EA-2-INTERNAL_ERR

2 L2

FR_VCM_EA-3-AIB_INIT_FAILED

3 L2

FR_VCM_EA-3-BATCH_INTERFACE_ERROR

3 L2

FR_VCM_EA-3-DATABASE_KEY_MISSING

3 L2

FR_VCM_EA-3-DLCI_MATCH_FAILED

3 L2

FR_VCM_EA-3-NO_STATS

3 L2

FR_VCM-2-CONFIG_INIT

2 L2

FR_VCM-2-CONNS

2 L2

FR_VCM-3-CONNECT_TO_L2VPN

3 L2

FR_VCM-3-ENCAPS_TYPE

3 L2

FR_VCM-3-IDB

3 L2

FR_VCM-3-IM_OP

3 L2

FR_VCM-3-INTF_NOTFOUND

3 L2

FR_VCM-3-MAIN_IF

3 L2

FR_VCM-3-NOMEM

3 L2

FR_VCM-3-PTP_VC

3 L2

FR_VCM-3-SUB_IF

3 L2

FR_VCM-3-SYSDB_OP

3 L2

FR_VCM-3-VC_EXISTS

3 L2

FR_VCM-3-VC_NOTFOUND

3 L2

FR_VCM-6-DEBUG_REG

6 L2

FRMIB-3-SYSDB

3 L2

FSYNC-3-COMMS_ERROR

3 L2

FSYNC-3-ESMC_SEND_TIMER

3 L2

FSYNC-4-COMMS_RETRY_FAILED

4 L2

FSYNC-4-ESMC_RECEIVE_TIMER

4 L2

FSYNC-4-INIT_FAILED

4 L2

FSYNC-4-INPUT_PROGRAMMING_FAILED

4 L2

FSYNC-4-INTF_IM_ERROR

4 L2

FSYNC-4-INTF_STATUS_ERROR

4 L2

FSYNC-4-LOST_EVENT

4 L2

FSYNC-4-MIB_DLL_ERROR

4 L2

FSYNC-4-MIB_INDEX_CHKPT_FAIL

4 L2

FSYNC-4-MIB_INDICES_EXHAUSTED

4 L2

FSYNC-4-QLT_TIMER

4 L2

FSYNC-4-SELECTION_ERROR

4 L2

FSYNC-4-SHUTDOWN_CHECK_FAILED

4 L2

FSYNC-4-SIGNAL_UPDATE_FAILED

4 L2

FSYNC-4-TIMER_FAILED

4 L2

FSYNC-6-SELECTION_CHANGE

6 L2

FSYNC-6-SELECTION_FALLBACK

6 L2

FWD_EDGE_COMMON-3-EDGE_ADJ_ERR

3 L2

FWD_EDGE_COMMON-3-EDGE_ADJ_NULL

3 L2

FWD_EDGE_COMMON-3-EDGE_IP_ERR

3 L2

FWD_EDGE_COMMON-3-SHM_INIT

3 L2

FWD_EDGE_COMMON-3-UTIL_ASSERT

3 L2

G709-4-ALARM

4 L2

G709-4-ERROR

4 L2

G709-4-log_overflow

4 L2

G709-6-INFO

6 L2

G709-6-PP_SM_TRIGGER

6 L2

G709-7-DEBUG_MSG

7 L2

G8032-3-APS_CHANNEL_INACTIVE

3 L2

G8032-3-PORT_STATE_ACK_TIMEOUT

3 L2

G8032-4-EXIT_FAILED

4 L2

G8032-4-FOP_PM_LOWER_LEVEL

4 L2

G8032-4-FOP_PM_MULTIPLE_RPL_OWNER

4 L2

G8032-4-INIT_FAILED

4 L2

G8032-4-INVALID_TCN_CONFIG

4 L2

G8032-6-APS_CHANNEL_ACTIVE

6 L2

G8032-6-CLEAR_REMINDER

6 L2

G8032-6-STATE_CHANGED

6 L2

GATM-2-AIB_MSG

2 L2

GATM-2-ERR

2 L2

GATM-2-ERR_HEX

2 L2

GATM-2-ERR_IFH_STS

2 L2

GATM-2-ERR_INT

2 L2

GATM-2-ERR_STR

2 L2

GATM-2-ERR_STS

2 L2

GATM-6-ADMN_STATE_INFO

6 L2

GATM-6-SUBIF_STATE_CHANGE

6 L2

GDO-5-L2PORT_FAULT_NOTIFY

5 L2

GDO-7-DEBUG

7 L2

GE_ASIC_PRP3-3-INIT_ERR

3 L2

GE_ASIC_PRP3-3-PKT_ERR

3 L2

GE_ASIC-3-INIT_ERR

3 L2

GE-3-INIT_ERR

3 L2

GSR_aib-3-RES_ERROR

3 L2

GSR_aib-6-INFO_MSG

6 L2

GSR_edge_fwd_lib-3-NULL

3 L2

GSR_edge_fwd_lib-3-RES_ERROR

3 L2

GSR_edge_fwd_lib-3-UTIL_ASSERT

3 L2

GSR-3-ERR_MEM_ALLOC

3 L2

GSR-3-ERR_SF_RESET

3 L2

GSR-3-ERR_THREAD_CREATE

3 L2

GSR-3-ERR_THREAD_CREATE

3 L2

GSR-3-FIA_CHKPT

3 L2

GSR-3-FIA_CHKPT_DATA_EXISTS

3 L2

GSR-3-FIA_CHKPT_RECOVERY_NODATA

3 L2

GSR-3-FIA_DEVCTL_ERR

3 L2

GSR-3-FIA_DLOPEN

3 L2

GSR-3-FIA_INT_ATTACH

3 L2

GSR-3-FIA_MEM_CHIP_ERR

3 L2

GSR-3-FIA_MEM_ERROR

3 L2

GSR-3-FIA_MMAP_ERROR

3 L2

GSR-3-FIA_NOT_RESET

3 L2

GSR-3-FIA_STARTUP_DATA

3 L2

GSR-3-FIA_SYNC_ERROR

3 L2

GSR-3-FIA_UNHALT

3 L2

GSR-3-FIA_UNSUPPORTED_CDB

3 L2

GSR-3-FIA_UNSUPPORTED_OPAQUE_DATA

3 L2

GSR-3-FS_ERR1

3 L2

GSR-3-SPABRG_ERR_HW

3 L2

GSR-3-SPABRG_ERR2_HW

3 L2

GSR-3-SPABRG_ERR3_HW

3 L2

GSR-3-SPABRG_ERR4_HW

3 L2

GSR-3-SPABRG_ERR5_HW

3 L2

GSR-3-SPABRG_ERR6_HW

3 L2

GSR-3-SPABRG_ERR7_HW

3 L2

GSR-4-ERR_SYSDB_SET

4 L2

GSR-4-FIA_EDM

4 L2

GSR-6-DEBUG_INIT_FAILED

6 L2

GSR-6-DEBUG_REGISTER_FAILED

6 L2

GSR-6-FIA_INFO_MSG

6 L2

GSR-6-FIA_PCDS_FAILURE

6 L2

GSR-6-PCDS_STATS_TIMESTAMP_FAILURE

6 L2

GSR-6-RECVD_TEST_LWM

6 L2

GSR-6-SPABRG_CRIT_INFO

6 L2

GSR-6-SPABRG_INFO1_HW

6 L2

GSR-6-SPABRG_INFO2_HW

6 L2

GSR-6-SPABRG_INFO3_HW

6 L2

GSR-7-FIA_FCTL

7 L2

GT64115-2-PCI_CONFIG

2 L2

GT64115-2-PCI_INIT

2 L2

GT64115-3-PCI_BRIDGE_INTR

3 L2

gulf-3-FATAL_ERROR

3 L2

gulf-3-UNDERRUN_ON_PORT

3 L2

gulf-4-WARNING

4 L2

gulf-6-INFO_MSG

6 L2

gulf-7-DEBUG_MSG

7 L2

HALE_MQS-3-ERR_MEM_ALLOC

3 L2

HALE_QOS-3-ERR_COMMIT

3 L2

HALE_QOS-3-ERR_MEM_ALLOC

3 L2

HALE_REPLICORD-3-ERR_MEM_ALLOC

3 L2

HALE_REPLICORD-3-UTIL_ASSERT

3 L2

HALE_TCAM-3-ERR_MEM_ALLOC

3 L2

HALE_TCAM-3-ERROR

3 L2

HALE_TCAM-3-UTIL_ASSERT

3 L2

HALE_TLU-3-ASSERT_FAIL_BCC

3 L2

HALE_TLU-3-ASSERT_FAIL_BCC_QC

3 L2

HALE_TLU-3-ASSERT_FAIL_DEF_CLUSTER

3 L2

HALE_TLU-3-ERR_MEM_ALLOC

3 L2

HALE_TLU-3-UTIL_ASSERT

3 L2

HFA_COMMON-3-FATAL_ERR

3 L2

HFA_COMMON-3-HWQ_MAP

3 L2

HFA_COMMON-3-PUBLISH_HWQ

3 L2

HFA_COMMON-4-ANOMALY

4 L2

HFA_COMMON-6-INFO_MSG

6 L2

HFA_COMMON-6-INFO_WARNING

6 L2

HFA_LIB-3-ANOMALY

3 L2

HFA_LIB-3-BLWM_CLIENT_CONF_FAILED

3 L2

HFA_LIB-3-BLWM_CLIENT_REBIND_FAILED

3 L2

HFA_LIB-3-BLWM_MSG_SEND_FAILED

3 L2

HFA_LIB-3-BLWM_RECVD_REPLY_FAIL

3 L2

HFA_LIB-3-MSG_SEND_FAILED

3 L2

HFA_LIB-3-PARAM

3 L2

HFA_LIB-4-BLWM_REPLAY_REQUEST

4 L2

HFA_LIB-4-ERR_LOCK

4 L2

HFA_LIB-6-INFO_WARNING

6 L2

if_discovery-3-FATAL_ERROR

3 L2

if_discovery-6-INFO_MSG

6 L2

if_discovery-7-DEBUG_MSG

7 L2

IGMPSN_POLICY-3-ORA_INSTBUILD

3 L2

IGMPSN_POLICY-3-ORA_ORABUILD

3 L2

IGMPSN_POLICY-3-ORA_RUN

3 L2

IGMPSN-3-DP_CONGESTION

3 L2

IGMPSN-3-INIT

3 L2

IGMPSN-3-INIT_FAIL

3 L2

IGMPSN-3-NET_FAIL

3 L2

IGMPSN-3-SYSDBINIT

3 L2

IGMPSN-5-DP_CONGESTION_CLEAR

5 L2

IMA-3-INCORRECT_BW_UPDATE

3 L2

IMA-3-LINK_GROUP_FAILURE

3 L2

IMA-3-MTU_IMPOSE_FAILED

3 L2

IMA-4-ALARM

4 L2

IMACTRLR-2-NOMEM

2 L2

IMACTRLR-3-ERROR

3 L2

IMACTRLR-4-ALARM

4 L2

IMACTRLR-4-UPDOWN

4 L2

IMACTRLR-4-WARNING

4 L2

IOB-3-INTR

3 L2

IOB-5-UNKNOWN_INTR

5 L2

IPV6_EA-3-INIT

3 L2

IPV6_EA-3-INIT_FAILED

3 L2

IPV6_EA-3-NOMEM

3 L2

IPV6_EA-3-PLAT_UPD_FAILED

3 L2

IPV6_EA-3-PLAT_UPD_FAILED_GL
IXP2800_FWD-3-IPCP_FAILURE

3 L2
3 L2

IXP2800_FWD-3-NONFATAL_ERROR

3 L2

IXP2800_FWD-7-LOG_FILE_ERROR

7 L2

IXP2800_FWD-7UNEXPECTED_FUNC_INVOC

7 L2

IXP2800_HW-2-NOMEM

2 L2

IXP2800_HW-3-FATAL_ERROR

3 L2

IXP2800_HW-4-WARNING

4 L2

IXP2800_HW-6-INFO

6 L2

IXP2800_HW-7-LOG_FILE_ERROR

7 L2

IXP2800_SERVICE-2-NOMEM

2 L2

IXP2800_SERVICE-3-FATAL_ERROR

3 L2

IXP2800_SERVICE-3-HOST_SPU_ERROR

3 L2

IXP2800_SERVICE-3-IPCP_FAILURE

3 L2

IXP2800_SERVICE-4-WARNING

4 L2

IXP2800_SERVICE-6-INFO

6 L2

IXP2800_SERVICE-7-LOG_FILE_ERROR

7 L2

JACKET-2-SPA_FPGA_IMG_ERR

2 L2

JACKET-2-SPA_FPGA_SW_REV_MISMATCH

2 L2

JACKET-3-API_FAILURE

3 L2

JACKET-3-CPU_CTRL_INIT

3 L2

JACKET-3-CPU_CTRL_INTS

3 L2

JACKET-3-CPU_CTRL_REG_ACCESS

3 L2

JACKET-3-CPU_CTRL_REG_LOCK

3 L2

JACKET-3-CRITICAL_ERROR

3 L2

JACKET-3-FAILURE

3 L2

JACKET-3-IMDR

3 L2

JACKET-3-INTERNAL_FAILURE

3 L2

JACKET-3-PIO_CRITICAL_ERROR

3 L2

JACKET-3-RULES_CRITICAL_ERROR

3 L2

JACKET-3-SPA_DISABLE

3 L2

JACKET-3-SPA_PIO_ERROR

3 L2

JACKET-3-SPA_REMOVE

3 L2

JACKET-3-SPA_SELF_DESTRUCT

3 L2

JACKET-3-SPABRG_BAY

3 L2

JACKET-3-SPABRG_INIT

3 L2

JACKET-4-QFP_FAILURE_BRIDGE_BIND

4 L2

JACKET-4-QFP_FAILURE_GIC_BIND

4 L2

JACKET-4-QFP_FAILURE_HA_ACK

4 L2

JACKET-4-QFP_FAILURE_HA_BIND

4 L2

JACKET-4-QFP_FAILURE_MEM_ALLOC

4 L2

JACKET-4-QFP_FAILURE_NO_CONNECTION

4 L2

JACKET-4QFP_FAILURE_SPA_BRIDGE_CONFIG

4 L2

JACKET-4QFP_FAILURE_SPA_BRIDGE_PRESENCE

4 L2

JACKET-4QFP_FAILURE_SPA_BRIDGE_REMOVAL

4 L2

JACKET-4QFP_FAILURE_SPA_BRIDGE_UPDATE

4 L2

JACKET-4-QFP_FAILURE_SPA_DISCOVERY

4 L2

JACKET-4QFP_FAILURE_SPA_UPDATE_NULL_BAY

4 L2

JACKET-4-QFP_FAILURE_SPI_RX_PHY_RESET

4 L2

JACKET-4-QFP_FAILURE_SPI4_CNTRL

4 L2

JACKET-4QFP_FAILURE_SPI4_INTERRUPT_CNTRL

4 L2

JACKET-4-QFP_FAILURE_SPI4_SYNC

4 L2

JACKET-4-QFP_FAILURE_SPI4_SYNC_CHECK

4 L2

JACKET-6-EVENT_INFO

6 L2

JACKET-6-INFO

6 L2

JACKET-6-SPARULE

6 L2

JACKET-6-UPGRADE_FPGA

6 L2

JACKET-7-DEBUG_MSG

7 L2

JDAM-3-CALLOC_FAILED

3 L2

JDAM-3-FAIL

3 L2

JDAM-3-FATAL_ERROR

3 L2

JDAM-3-INVALID_VC_TYPE_4

3 L2

JDAM-3-MEMORY_EXHAUSTED

3 L2

JDAM-3-NULL_VLAN_TABLE_PTR

3 L2

JDAM-3-PORT_FAILED

3 L2

JDAM-3-PORT_MAPPING_FAILED

3 L2

JDAM-3-PORT_NUMBER_OUT_OF_RANGE

3 L2

JDAM-3-TCAM_INVALID_SHARED_INDEX

3 L2

JDAM-3-TCAM_INVALID_SHARED_MEMORY

3 L2

JDAM-3-VLAN_INVALID_SHARED_MEMORY

3 L2

JDAM-3VLAN_SHARED_MEMORY_EXHAUSTED

3 L2

JDAM-3VLAN_TCAM_SHARED_MEMORY_EXHAUSTE
D

3 L2

JDAM-6-INFO_MSG

6 L2

JDAM-6-PRINT_SB

6 L2

JDAM-6-PRINT_TCAM

6 L2

JDAM-6-PRINT_TCAM_ELEMENT

6 L2

JDAM-7-DEBUG_MSG

7 L2

L2C-3-ERR_MISCONFIG

3 L2

L2C-4-WARN_EVENT

4 L2

L2C-4-WARN_INIT

4 L2

L2FIB_DEBUG-2-L2FIB_SHM_ERR

2 L2

L2FIB_LIB-2-OOR

2 L2

L2FIB_LIB-2-OOR_PROC_RESTART

2 L2

L2FIB_LIB-3-ERR_SHM

3 L2

L2FIB_LIB-3-L2FIB_API_ERR

3 L2

L2FIB_LIB-4-RSRC_LOW

4 L2

L2FIB_LIB-6-BDXC_SEND

6 L2

L2FIB_SHM-3-ERR_L2FIB_SHM

3 L2

L2FIB-2-INIT_L2FIB

2 L2

L2FIB-2-INVALID_MSG

2 L2

L2FIB-2-SHM_INIT

2 L2

L2FIB-3-BDXC_CERR

3 L2

L2FIB-3-GEN_INFO_CERR

3 L2

L2FIB-3-GEN_INFO_ERR

3 L2

L2FIB-3-IRB_CERR

3 L2

L2FIB-3-MCAST_GTRIE_CERR

3 L2

L2FIB-3-PULSE_HDLR_CERR

3 L2

L2FIB-3-ROUTE_HDLR_CERR

3 L2

L2FIB-3-SHM_ERR

3 L2

L2FIB-3-SHM_FREE_ERR

3 L2

L2FIB-3-STATS_CERR

3 L2

L2FIB-5-SECURITY_DAI_VIOLATION_AC

5 L2

L2FIB-5-SECURITY_IPSG_VIOLATION_AC

5 L2

L2FIB-5SECURITY_MAC_SECURE_VIOLATION_AC

5 L2

L2FIB-5SECURITY_MAC_SECURE_VIOLATION_PBB

5 L2

L2FIB-5SECURITY_MAC_SECURE_VIOLATION_PW

5 L2

L2FIB-6-MAC_TABLE_RESYNC_COMPLETE

6 L2

L2FIB-6-XC_MOD

6 L2

L2TP-2-INIT

2 L2

L2TP-3-DIFF_L2TP_CLASS

3 L2

L2TP-3-ERRMSG

3 L2

L2TP-3-GEN_ERR

3 L2

L2TP-3-IPC_ERR

3 L2

L2TP-3-L2TP_CC_ACCT_NO_ACK

3 L2

L2TP-3-NO_SRCIP

3 L2

L2TP-6-PACKET
L2VPN_DEBUG-3-CLEANUP_ERR

6 L2
3 L2

L2VPN_DEBUG-3-INIT_ERR

3 L2

L2VPN_DEBUG-3-LTRACE_INIT_ERR

3 L2

L2VPN_ICCP_SM-3-CONFIG_ERROR_CLEAR

3 L2

L2VPN_ICCP_SM-3CONFIG_INVALID_NODEID

3 L2

L2VPN_ICCP_SM-3CONFIG_INVALID_NODEID_CLEAR

3 L2

L2VPN_ICCP_SM-3-CONFIG_LOCAL_ERROR

3 L2

L2VPN_ICCP_SM-3-CONFIG_REMOTE_ERROR

3 L2

L2VPN_ICCP_SM-4-CONFIG_CONFLICT

4 L2

L2VPN_ICCP_SM-4CONFIG_CONFLICT_CLEAR

4 L2

L2VPN_ICCP_SM-4LOCAL_ACCESS_MAIN_PORT_FAILURE

4 L2

L2VPN_ICCP_SM-4LOCAL_ACCESS_MAIN_PORT_FAILURE_CLEA
R

4 L2

L2VPN_ICCP_SM-4-LOCAL_CORE_ISOLATION

4 L2

L2VPN_ICCP_SM-4LOCAL_CORE_ISOLATION_CLEAR

4 L2

L2VPN_ICCP_SM-4MCLAG_CONFIG_CONFLICT

4 L2

L2VPN_ICCP_SM-4MCLAG_CONFIG_CONFLICT_CLEAR

4 L2

L2VPN_ICCP_SM-4PEER_REACHABILITY_CLEAR

4 L2

L2VPN_ICCP_SM-4PEER_REACHABILITY_FAILURE

4 L2

L2VPN_ICCP_SM-4REMOTE_ACCESS_MAIN_PORT_FAILURE

4 L2

L2VPN_ICCP_SM-4REMOTE_ACCESS_MAIN_PORT_FAILURE_CLE
AR

4 L2

L2VPN_ICCP_SM-4REMOTE_CORE_ISOLATION

4 L2

L2VPN_ICCP_SM-4REMOTE_CORE_ISOLATION_CLEAR

4 L2

L2VPN_MA_PWHE-3-INIT_ERR

3 L2

L2VPN_MA_PWHE-3-REPLICATION_FAILED

3 L2

L2VPN_MA_PWHE-3REPLICATION_SUCCESSFUL

3 L2

L2VPN_PW-3-UPDOWN

3 L2

L2VPN_PW-4-ATOM_MERGE_ERR

4 L2

L2VPN_PW-6-STANDBY

6 L2

L2VPN_PW-6-STANDBY_READY

6 L2

L2VPN_PWHE-3-EA_RETRY_FAILED

3 L2

L2VPN_PWHE-3-EA_STATE

3 L2

L2VPN_PWHE-4-EA_ERR_INIT

4 L2

L2VPN_PWHE-4-EA_RETRY

4 L2

L2VPN-2-CRIT_MEM_SHUT

2 L2

L2VPN-3-BAG_REG_ERR

3 L2

L2VPN-3-ID_MGR_INVALID_REMOVE

3 L2

L2VPN-3-INIT_ERR

3 L2

L2VPN-3-INTERNAL_ERROR

3 L2

L2VPN-3-SYSDB_BIND_ERR

3 L2

L2VPN-3-SYSDB_ERR

3 L2

L2VPN-4-BD_BVI_VMAC

4 L2

L2VPN-4-BD_MST_LOOP

4 L2

L2VPN-4-BRIDGE_MTU_MISMATCH

4 L2

L2VPN-4-ENCAP_REMOVED_PW

4 L2

L2VPN-4-ENS_RESYNC_FAILURE

4 L2

L2VPN-4-MAC_LIMIT_AC_SHUT

4 L2

L2VPN-4-MAC_LIMIT_BD_SHUT

4 L2

L2VPN-4-MAC_LIMIT_PW_SHUT

4 L2

L2VPN-4-NSR_SYNC_SESSION_FAILURE

4 L2

L2VPN-4-PROVISIONING_WARNING

4 L2

L2VPN-5-BD_STATE_CHANGED

5 L2

L2VPN-5EVPN_RD_AUTO_RD_STATIC_CONFLICT

5 L2

L2VPN-5-EVPN_RECV_LACP_MAC_TWICE

5 L2

L2VPN-5-EVPN_RECV_LACP_MCAST_MAC

5 L2

L2VPN-5-ID_MGR_OOR

5 L2

L2VPN-5-MSTP_CONFIG_CONFLICT

5 L2

L2VPN-5-NO_LICENSE

5 L2

L2VPN-5-NSR_STATE_CHANGED

5 L2

L2VPN-5-VFI_STATE_CHANGED

5 L2

L2VPN-6-BRIDGE_MTU_MISMATCH_CLEAR

6 L2

L2VPN-6-CAPABILITY_CHANGE

6 L2

L2VPN-6-ENCAP_REMOVED_PW_CLEAR

6 L2

L2VPN-6-MAC_LIMIT_AC_CLEAR

6 L2

L2VPN-6-MAC_LIMIT_AC_SET

6 L2

L2VPN-6-MAC_LIMIT_BD_CLEAR

6 L2

L2VPN-6-MAC_LIMIT_BD_SET

6 L2

L2VPN-6-MAC_LIMIT_PW_CLEAR

6 L2

L2VPN-6-MAC_LIMIT_PW_SET

6 L2

LACP_LITE-3ERR_LL_DLL_ASYNC_SEND_FAIL

3 L2

LACP_LITE-3ERR_LL_DLL_CHAN_CONNECT_FAIL

3 L2

LACP_LITE-3-ERR_SHMEM_MMAP_FAIL

3 L2

LACP_LITE-3-ERR_SHMEM_OPEN_FAIL

3 L2

LACP_LITE-3-ERR_SHMEM_TRNC_FAIL

3 L2

LACP_LITE-3-ERR_SHMEM_UNAVAILABLE

3 L2

LACP_LITE-3-ERR_UNSUPPORTED_FLAG

3 L2

LI_EA-3-ERR_IM_CAPS

3 L2

LI_EA-7-INIT

7 L2

LI_EA-7-INIT

7 L2

MARVEL-3-CHAN_CREATE

3 L2

MARVEL-3-DEBUG_INIT

3 L2

MARVEL-3-DEBUG_REG

3 L2

MARVEL-3-EVENT_MGR_FAIL

3 L2

MARVEL-3-MMAP

3 L2

MARVEL-3-MSG_REPLY

3 L2

MARVEL-3-NOMEM

3 L2

MARVEL-3-OPEN

3 L2

MARVEL-6-RX_ASYNC_MSG

6 L2

METRO_STATS_API-7-DEBUG_MSG

7 L2

METRO_STATS_API-7-ERR_DLL_INIT

7 L2

METRO_STATS_API-7-ERR_THREAD

7 L2

METRO_STATS_API-7-RESERVE_LMT_MSG

7 L2

METRO_STATS-7-ERR_EXHAUST

7 L2

METRO_STATS-7-ERR_INIT

7 L2

METRO_STATS-7-ERR_MEM

7 L2

MFR_EA_LTRACE_DLL-3-OPER_FAIL

3 L2

MFR_EA_LTRACE-3-ERR_INIT_FAIL

3 L2

MFR_EA_LTRACE-3-EVENT_INIT_FAIL

3 L2

MFR_EA_LTRACE-3-INTERNAL_INIT_FAIL

3 L2

MFR_EA-2-DPC_CALL_FAILED

2 L2

MFR_EA-2-INTERNAL_ERR

2 L2

MFR_EA-3-AIB_INIT_FAILED

3 L2

MFR_EA-3-INTERFACE_OPERATION_FAILED

3 L2

MFR_EA-3-MALLOC

3 L2

MFR_EA-3-MEMBER_AIB_REMOVE_FAILED

3 L2

MFR_EA-3-MEMBER_AIB_SET_FAILED

3 L2

MFR_EA-3-MEMBER_CAPS_ADD_FAILED

3 L2

MFR_EA-3-MEMBER_CAPS_REMOVE_FAILED

3 L2

MFR_EA-3MEMBER_ENCAP_REMOVE_FAILED

3 L2

MFR_EA-3-MEMBER_ENCAP_SET_FAILED

3 L2

MFR_EA-3-MEMBER_INFO_COLLECT_FAILED

3 L2

MFR_EA-3-NO_STATS

3 L2

MFR_EA-3-STATE_CHANGE_FAILED

3 L2

MFR_MA-2-PROC_FAIL

2 L2

MFR_MA-3-DELETE_IDB

3 L2

MFR_MA-3-DPC_FAIL

3 L2

MFR_MA-3-ENCAP

3 L2

MFR_MA-3-ERR_IMC

3 L2

MFR_MA-3-ERR_INTERNAL

3 L2

MFR_MA-3-ERR_LIST_CREATE

3 L2

MFR_MA-3-ERR_MEMBER_ADD

3 L2

MFR_MA-3-ERR_MUTEX_LOCK

3 L2

MFR_MA-3-ERR_PULSE

3 L2

MFR_MA-3-ERR_SYSDB_BIND

3 L2

MFR_MA-3-INCORRECT_COUNT

3 L2

MFR_MA-3-MAKE_IDB

3 L2

MFR_MA-3-MALLOC

3 L2

MFR_MA-3-RECVFROM

3 L2

MFR_MA-3-THREAD

3 L2

MFR_MA-4-ERR_CHKPT

4 L2

MFR_MA-4-ERR_CHKPT_CORRUPT

4 L2

MFR_MA-4-ERR_CHKPT_DUPLICATE

4 L2

MFR_MA-4-ERR_EVC

4 L2

MFR_MA-4-ERR_MEM_ALLOC

4 L2

MFR_MA-4-ERR_MGD_TIMER

4 L2

MFR_MA-4-ERR_THREAD_CREATE

4 L2

MFR_MA-6-SENDTO

6 L2

MICKEY-2-INTR

2 L2

MICKEY-5-UNKNOWN_INTR

5 L2

MLCTRLR-2-NOMEM

2 L2

MLCTRLR-3-ERROR

3 L2

MLCTRLR-4-ALARM
MLCTRLR-4-FEAC

4 L2
4 L2

MLCTRLR-4-LOOPSTATUS

4 L2

MLCTRLR-4-UPDOWN

4 L2

MLCTRLR-4-WARNING

4 L2

MMRP-3-FATAL_PROTOCOL_FAILURE

3 L2

MMRP-3-REG_CREATE_FAILURE

3 L2

MMRP-3-ROUTE_ADD_FAILURE

3 L2

MMRP-4-ROUTE_DELETE_FAILURE

4 L2

MMSMLIB-3-EXIT_ON_ERR

3 L2

MOTHRA-3-FATAL_ERROR

3 L2

MOTHRA-3-PIO_FATAL_ERROR

3 L2

MOTHRA-6-INFO_MSG

6 L2

MOTHRA-7-DEBUG_MSG

7 L2

MOUSE-2-INTR

2 L2

MOUSE-5-UNKNOWN_INTR

5 L2

MRP_MAD-3-INVALID_DMAC

3 L2

MRP_MAD-3-INVALID_MRPDU_DIR

3 L2

MRP_MAD-3-INVALID_MRPDU_INTERFACE

3 L2

MRP_MAD-3-INVALID_MRPDU_PARSE

3 L2

MRP_MAD-3INVALID_MRPDU_PARSE_ATTRIBUTE

3 L2

MRP_MAD-3-INVALID_MRPDU_PAYLOAD

3 L2

MRP_MAD-3-MALLOC_FAILURE

3 L2

MRP_MAD-3-PARTICIPANT_NOT_FOUND

3 L2

MULTILINK_UV-3-ERR_MISCONFIG

3 L2

MULTILINK_UV-3-EVENT

3 L2

MULTILINK_UV-3-INIT

3 L2

MULTILINK_UV-3-SYSMGR

3 L2

Multilink-3-INCORRECT_BW_UPDATE

3 L2

Multilink-3-ML_GROUP_FAILURE

3 L2

Multilink-3-MTU_IMPOSE_FAILED

3 L2

Multilink-4-ALARM

4 L2

MVRP-4-INITIALISATION_FAILURE

4 L2

MVRP-4-L2VPN_FLUSH

4 L2

MVRP-4-MAD_INIT_FAILED

4 L2

MVRP-4-PROBLEM_EXITING

4 L2

ND-3-INIT

3 L2

NPU_CLIENT-4-EXIT_ON_ERR

4 L2

NPU-2-CRIT_EXIT

2 L2

NPU-2-DRAM_INIT_FAILURE

2 L2

NPU-2-DUI_VTP_FAILURE

2 L2

NPU-2-NODE_BRINGDOWN

2 L2

NPU-3-DMA_ERROR_MSG

3 L2

NPU-3-ERR_EXIT

3 L2

NPU-3-ERROR_MSG

3 L2

NPU-3-HEALTH_MONITOR_ERROR_MSG

3 L2

NPU-3-INIT_ERROR_MSG

3 L2

NPU-4-COLD_RESET_FAILED

4 L2

NPU-4-WARM_RESET_FAILED

4 L2

NPU-6-INFO_MSG

6 L2

OAMMIB-3-NO_DEBUG

3 L2

OAMMIB-3-NO_IFTABLE

3 L2

OAMMIB-3-NO_TRAP

3 L2

OC768_FRAMER_ASIC-3-CRITICAL_ERROR

3 L2

OC768_FRAMER_ASIC-6-INFO

6 L2

OC768_FRAMER_ASIC-7-DEBUG_MSG

7 L2

OFA_PLUGIN-1-OVS_ALERT

1 L2

OFA_PLUGIN-3-BAG_ERR

3 L2

OFA_PLUGIN-3-BAG_REG_ERR

3 L2

OFA_PLUGIN-3-BD_ALREADY_ASSOCIATED

3 L2

OFA_PLUGIN-3-BD_INVALID_LS_LAYER

3 L2

OFA_PLUGIN-3-BUNDLE_INVALID_PIPELINE

3 L2

OFA_PLUGIN-3-CTRL_ALREADY_ASSOCIATED

3 L2

OFA_PLUGIN-3-DBG_ERR

3 L2

OFA_PLUGIN-3-EVENT_ERR

3 L2

OFA_PLUGIN-3-GEN_ERR

3 L2

OFA_PLUGIN-3-GEN_RC_ERR

3 L2

OFA_PLUGIN-3-HA_ABORT

3 L2

OFA_PLUGIN-3-IF_ALREADY_ASSOCIATED

3 L2

OFA_PLUGIN-3-IF_INVALID_LS_LAYER

3 L2

OFA_PLUGIN-3-IF_IS_PART_OF_BD

3 L2

OFA_PLUGIN-3-IF_IS_PART_OF_LS

3 L2

OFA_PLUGIN-3-IF_IS_PART_OF_VRF

3 L2

OFA_PLUGIN-3-LAYER_ERR

3 L2

OFA_PLUGIN-3LOOPBACK_ADDR_UNAVAILABLE

3 L2

OFA_PLUGIN-3LOOPBACK_ALREADY_ASSOCIATED

3 L2

OFA_PLUGIN-3-OVS_ERR

3 L2

OFA_PLUGIN-3-SYSDB_BIND_ERR

3 L2

OFA_PLUGIN-3-SYSDB_ERR

3 L2

OFA_PLUGIN-3-SYSMGR_ERR

3 L2

OFA_PLUGIN-3-VRF_ALREADY_ASSOCIATED

3 L2

OFA_PLUGIN-3-VRF_INVALID_LS_LAYER

3 L2

OFA_PLUGIN-4-GEN_RC_WARNING

4 L2

OFA_PLUGIN-4-OVS_WARNING
OFA_PLUGIN-6-OVS_INFO
OFA_PLUGIN-7-OVS_DEBUG

4 L2
6 L2
7 L2

OPTICS-2-ETHER_XCVR_CODE

2 L2

OPTICS-2-PID

2 L2

OPTICS-2-PN

2 L2

OPTICS-2-SFP_XCVR_TYPE

2 L2

OPTICS-2-SONET_XCVR_CODE

2 L2

OPTICS-2-TRANSCEIVER_LOC

2 L2

OPTICS-2-VID

2 L2

OPTICS-2-XCVR_CODE

2 L2

OPTICS-2-XFP_XCVR_TYPE

2 L2

OPTICS-3-CRITICAL_ERROR

3 L2

OPTICS-6-INFO

6 L2

OPTICS-7-DEBUG_MSG

7 L2

OTN_DRIVER-2-HW_ERR

2 L2

OTN_DRIVER-3-INIT

3 L2

OTN_DRIVER-3-SW_ERR

3 L2

OTN_DRIVER-6-INTERRUPT

6 L2

PAL_CGM-3-INIT_ERROR

3 L2

PAL_CGM-3-INIT_ERROR

3 L2

PAL_IPHC-2-EA_INIT_FAILURE

2 L2

PAL_IPHC-3-EA_FAILURE

3 L2

PAL_IPHC-6-EA_INFO

6 L2

PFILTER_EA-2-ERR_CHAIN

2 L2

PFILTER_EA-3-DEBUG_INIT

3 L2

PFILTER_EA-3-DEBUG_REG

3 L2

PFILTER_EA-3-ERR_IM_CAPS

3 L2

PFILTER_EA-3-ERR_IM_CAPS

3 L2

PFILTER_EA-3-ERR_IM_CAPS

3 L2

PFILTER_EA-3-ERR_IM_CAPS

3 L2

PFILTER_EA-3-IMP_SERVER_FAIL

3 L2

PFILTER_EA-3-INIT_ACL_CONF_MGR_FAIL

3 L2

PFILTER_EA-3-INIT_ACL_UPDATE_FAIL

3 L2

PFILTER_EA-3-INIT_ERROR

3 L2

PFILTER_EA-3-INIT_ERROR

3 L2

PFILTER_EA-3-INIT_ERROR

3 L2

PFILTER_EA-3-INIT_EVENT_BLOCK_FAIL

3 L2

PFILTER_EA-3-INIT_EVENT_MGR_FAIL

3 L2

PFILTER_EA-3-INIT_FEAT_CKPNT_FAIL

3 L2

PFILTER_EA-3-INIT_FEAT_EA_FAIL

3 L2

PFILTER_EA-3-INIT_LTRACE_FAIL

3 L2

PFILTER_EA-3-INIT_PERMIT_DENY_FAIL

3 L2

PFILTER_EA-3-INIT_REGISTER_DEBUG_FAIL

3 L2

PFILTER_EA-3-INIT_RLB_CKPNT_FAIL

3 L2

PFILTER_EA-3-INIT_SYSDB_CONNECT_FAIL

3 L2

PFILTER_EA-3-SHIP_INFRA

3 L2

PFILTER_EA-3-SYS_MGR

3 L2

PFILTER_EA-3-TLU_FAIL

3 L2

PFILTER_EA-7-EVENT_ERROR

7 L2

PFILTER_EA-7-EVENT_ERROR

7 L2

PFILTER_EA-7-EVENT_ERROR

7 L2

PFILTER_EA-7-INIT

7 L2

PFILTER_EA-7-INIT

7 L2

PFILTER_EA-7-INIT

7 L2

PFILTER_EA-7-INIT

7 L2

PIRD_INTF_EA-4-DB_ATTACH

4 L2

PIRD_INTF_EA-4-LOST_EVENT

4 L2

PIRD-3-DB_DELETE_FAILED

3 L2

PIRD-3-DB_INCONSISTENT

3 L2

PIRD-3-DB_INVALID_EPOCH

3 L2

PIRD-3-DB_INVALID_FREE

3 L2

PIRD-3-DB_LOCK_ERROR

3 L2

PIRD-3-DB_PTR_CORRUPT

3 L2

PIRD-3-ECM_RETRY_ERROR

3 L2

PIRD-3-IM_STATE_ERROR

3 L2

PIRD-3-INV_DEBUG_FLTR

3 L2

PIRD-3-MUTEX_REVIVED

3 L2

PIRD-4-BDL_LB_INIT_FAILED

4 L2

PIRD-4-DB_ATTACH

4 L2

PIRD-4-EXIT_FAILED

4 L2

PIRD-4-INIT_FAILED

4 L2

PIRD-4-INV_PKT_FIELD

4 L2

PIRD-4-LOST_EVENT

4 L2

PIRD-4-PLUGIN_ATTACH

4 L2

PLAOC768_API-3-CRITICAL_ERROR

3 L2

PLAOC768_API-7-DEBUG_MSG

7 L2

PLAOC768-3-ASIC_ERROR

3 L2

PLAOC768-3-CRITICAL_ERROR

3 L2

PLAOC768-3-PIO_CRITICAL_ERROR

3 L2

PLAOC768-6-INFO

6 L2

PLAOC768-7-DEBUG_MSG

7 L2

PLAT_L2FIB_VPLS-7-DEBUG_ERROR

7 L2

PLAT_L2FIB_VPLS-7-INIT_ERROR

7 L2

PLAT_L2FIB_VPLS-7-LTRACE_ERROR

7 L2

PLATFORM_ATM_OAM-3-PACKET_RX

3 L2

PLATFORM_ATM_OAM-3-PACKET_RX

3 L2

PLATFORM_ATM_OAM-7-PACKET_SIZE

7 L2

plim_4p_oc12-3-ALLOC_FAILED

3 L2

plim_4p_oc12-3-CREATE_THREAD_ERROR

3 L2

plim_4p_oc12-3-DEBUG_INIT_ERROR

3 L2

plim_4p_oc12-3-ERR_EVM_CREATE

3 L2

plim_4p_oc12-3-ERR_EVM_EVENT_BLOCK

3 L2

plim_4p_oc12-3-ERR_PORT_INIT

3 L2

plim_4p_oc12-3-FWD_REGISTER_ERROR

3 L2

plim_4p_oc12-3-PORT_AVAILABLE_FAILED

3 L2

plim_4p_oc12-3-RESET_FAILED

3 L2

plim_4p_oc12-3STATS_COLLECT_REGISTER_FAILED

3 L2

plim_4p_oc12-3-STATSD_COLL_INIT_ERROR

3 L2

plim_4p_oc12-3-TIMER_INIT_FAILED

3 L2

plim_4p_oc12-3TX_CLK_GET_INVALID_PORT_CTX

3 L2

plim_4p_oc12-3TX_CLK_SET_INVALID_PORT_CTX

3 L2

plim_4p_oc12-4-INVALID_TIMER

4 L2

PLIM_4P_OC192-3-DEVICE_INTR_CLEAR

3 L2

PLIM_4P_OC192-3-DEVICE_INTR_DISABLE

3 L2

PLIM_4P_OC192-3-DRV_INIT_ERR

3 L2

PLIM_4P_OC192-3-ERR

3 L2

PLIM_4P_OC192-3-GENERIC_ERROR

3 L2

PLIM_4P_OC192-3-GET_NODEID_ERR

3 L2

PLIM_4P_OC192-3-MEM_ERR
PLIM_ASIC_API-7-ERR

3 L2
7 L2

PLIM_ASIC-1HEALTH_MONITOR_PON_RECOVERY

1 L2

PLIM_ASIC-1-REQUEST_RELOAD_BOARD

1 L2

PLIM_ASIC-1-SW_ERR

1 L2

PLIM_ASIC-2-EIO_TRAIN

2 L2

PLIM_ASIC-3-ERR

3 L2

PLIM_ASIC-3HEALTH_MONITOR_PON_RECOVERY

3 L2

PLIM_ASIC-3-HW_ERR

3 L2

PLIM_ASIC-3-IMDR_ERR

3 L2

PLIM_ASIC-3-LTRACE_INIT

3 L2

PLIM_ASIC-3-PIO_ERROR

3 L2

PLIM_ASIC-3-PIO_ERROR

3 L2

PLIM_ASIC-3-SW_ERR

3 L2

PLIM_ASIC-3-XSN_TIMEOUT

3 L2

PLIM_ASIC-3-XSN_TIMEOUT

3 L2

PLIM_ASIC-4-HW_WARNING

4 L2

PLIM_ASIC-6-RESET_REJECT

6 L2

PLIM_ASIC-6-RESET_REJECT

6 L2

PLIM_CLKSEL-3-ERR_INIT

3 L2

PLIM_CLKSEL-4-ERR_DEBUG

4 L2

PLIM_ETHER-2-HW_ERROR

2 L2

PLIM_ETHER-2-RX_LF

2 L2

PLIM_ETHER-2-RX_LF

2 L2

PLIM_ETHER-2-RX_LOSS

2 L2

PLIM_ETHER-2-RX_RF

2 L2

PLIM_ETHER-2-RX_RF

2 L2

PLIM_ETHER-2-RX_UNKNOWN

2 L2

PLIM_ETHER-2-RX_UNKNOWN

2 L2

PLIM_ETHER-2-TRANSCEIVER_INSERTED

2 L2

PLIM_ETHER-2-TRANSCEIVER_REMOVED

2 L2

PLIM_ETHER-2XGXS_DTE_SYNC_ERROR_RECOVERED

2 L2

PLIM_ETHER-2XGXS_DTE_SYNC_ERROR_RECOVERED

2 L2

PLIM_ETHER-2XGXS_DTE_SYNC_ERROR_RECOVERY_FAILE
D

2 L2

PLIM_ETHER-2XGXS_DTE_SYNC_ERROR_RECOVERY_FAILE
D

2 L2

PLIM_ETHER-2XGXS_DTE_SYNC_ERROR_THRESHOLD

2 L2

PLIM_ETHER-2XGXS_DTE_SYNC_ERROR_THRESHOLD

2 L2

PLIM_ETHER-2XGXS_DTE_SYNC_POST_RECOVERY

2 L2

PLIM_ETHER-2XGXS_DTE_SYNC_POST_RECOVERY

2 L2

PLIM_ETHER-2XGXS_DTE_SYNC_POST_RECOVERY_FAILED

2 L2

PLIM_ETHER-2XGXS_DTE_SYNC_POST_RECOVERY_FAILED

2 L2

PLIM_ETHER-3-IMDR_ERR

3 L2

PLIM_ETHER-3-INCONSISTENT_CONFIG

3 L2

PLIM_ETHER-3-SW_ERR

3 L2

PLIM_ETHER-3-SW_ERROR

3 L2

PLIM_ETHER-3-SW_INIT

3 L2

PLIM_ETHER-3-SW_INIT

3 L2

PLIM_ETHER-3-SW_INTERFACE

3 L2

PLIM_ETHER-3-SW_INTERFACE

3 L2

PLIM_ETHER-6-MODE_CHANGE

6 L2

PLIM_ETHER-6-MODE_CHANGE

6 L2

PLIM_FPGA-1ERR_HW_ERR_DISABLE_INTERRUPT

1 L2

PLIM_FPGA-1ERR_HW_ERR_THRESHOLD_RELOAD

1 L2

PLIM_FPGA-1-ERR_HW_RELOAD_NODE

1 L2

PLIM_FPGA-2-EIO_TRAIN

2 L2

PLIM_FPGA-3-CRITICAL_ERROR

3 L2

PLIM_FPGA-3-ERR

3 L2

PLIM_FPGA-3-ERR_HW_HARD_RESET

3 L2

PLIM_FPGA-3ERR_HW_HARD_THRESHOLD_RESET

3 L2

PLIM_FPGA-3-HW_ERR

3 L2

PLIM_FPGA-3-IMDR_ERR

3 L2

PLIM_FPGA-3-LTRACE_INIT

3 L2

PLIM_FPGA-3-PIO_CRITICAL_ERROR

3 L2

PLIM_FPGA-4-HW_WARNING

4 L2

PLIM_FPGA-6-INFO

6 L2

PLIM_FPGA-7-DEBUG_MSG

7 L2

PLIM_IOX_4P_GE-3-INIT_ERR

3 L2

PLIM_IOX_4P_GE-6-INFO_MSG

6 L2

PLIM_IOX_4P_GE-6-RXLOS_INT

6 L2

PLIM_LIB-2-ERR_FM_REPLY

2 L2

PLIM_LIB-2-ERR_FM_REQUEST

2 L2

PLIM_LIB-3-ERR_INIT

3 L2

PLIM_LIB-3-ERROR

3 L2

PLIM_LIB-3-ERROR

3 L2

PLIM_LIB-3-SYSDB_ERROR

3 L2

PLIM_LIB-3-SYSDB_ERROR

3 L2

PLIM_LIB-4-ERR_MSG_RCV

4 L2

PLIM_LIB-6-INFO

6 L2

PLIM_LIB-6-INFO

6 L2

PLIM_LIB-7-DEBUG

7 L2

PLIM_LIB-7-DEBUG

7 L2

plim_oc48-3-ALLOC_FAILED

3 L2

plim_oc48-3-ALLOC_FAILED

3 L2

plim_oc48-3-CREATE_THREAD_ERROR

3 L2

plim_oc48-3-CREATE_THREAD_ERROR

3 L2

plim_oc48-3-E3_BW_CHNG_REJ

3 L2

plim_oc48-3-ERR_EVM_CREATE

3 L2

plim_oc48-3-ERR_EVM_CREATE

3 L2

plim_oc48-3-ERR_EVM_EVENT_BLOCK

3 L2

plim_oc48-3-ERR_EVM_EVENT_BLOCK

3 L2

plim_oc48-3-ERR_MBUS_OP

3 L2

plim_oc48-3-ERR_MBUS_OP

3 L2

plim_oc48-3-ERR_PORT_INIT

3 L2

plim_oc48-3-ERR_PORT_INIT

3 L2

plim_oc48-3-FWD_REGISTER_ERROR

3 L2

plim_oc48-3-FWD_REGISTER_ERROR

3 L2

plim_oc48-3-NOT_IM_INITIALIZED_YET

3 L2

plim_oc48-3-NULL_CHN_CTX

3 L2

plim_oc48-3-PORT_AVAILABLE_FAILED

3 L2

plim_oc48-3-PORT_AVAILABLE_FAILED

3 L2

plim_oc48-3-RESET_FAILED

3 L2

plim_oc48-3-RESET_FAILED

3 L2

plim_oc48-3STATS_COLLECT_REGISTER_FAILED

3 L2

plim_oc48-3-STATSD_COLL_INIT_ERROR

3 L2

plim_oc48-3-TIMER_INIT_FAILED

3 L2

plim_oc48-3-TIMER_INIT_FAILED

3 L2

plim_oc48-3TX_CLK_GET_INVALID_PORT_CTX

3 L2

plim_oc48-3TX_CLK_GET_INVALID_PORT_CTX

3 L2

plim_oc48-3TX_CLK_SET_INVALID_PORT_CTX

3 L2

plim_oc48-3TX_CLK_SET_INVALID_PORT_CTX

3 L2

plim_oc48-4-INVALID_TIMER

4 L2

plim_oc48-4-INVALID_TIMER

4 L2

plim_oc48-6-CHIP_NOT_SUPPORTED

6 L2

plim_oc48-6-LASER_DISABLE

6 L2

plim_oc48-6-LASER_ENABLE

6 L2

PLIM_OC768-3-CRITICAL_ERROR

3 L2

PLIM_OC768-6-INFO

6 L2

PLIM_OC768-7-DEBUG_MSG

7 L2

PLIM-1-ERR_HW_DISABLE_NODE

1 L2

PLIM-1-ERR_HW_RELOAD_NODE

1 L2

PLIM-1-ERR_HW_RELOAD_NODE

1 L2

PLIM-1-ERR_HW_RELOAD_NODE

1 L2

PLIM-1-ERR_HW_RELOAD_NODE

1 L2

PLIM-1-ERR_HW_RELOAD_NODE

1 L2

PLIM-1-ERR_HW_RELOAD_NODE

1 L2

PLIM-1-ERR_HW_RESET_PLL

1 L2

PLIM-1-ERR_HW_RESET_PLL_THRESHOLD

1 L2

PLIM-1ERR_HW_THRESHOLD_RELOAD_NODE

1 L2

PLIM-1ERR_HW_THRESHOLD_RELOAD_NODE

1 L2

PLIM-1ERR_HW_THRESHOLD_RELOAD_NODE

1 L2

PLIM-1ERR_HW_THRESHOLD_RELOAD_NODE

1 L2

PLIM-1ERR_HW_THRESHOLD_RELOAD_NODE

1 L2

PLIM-2-EIO_TRAIN

2 L2

PLIM-2-ERR_HW_HARD_RESET

2 L2

PLIM-2-ERR_HW_HARD_RESET

2 L2

PLIM-2-ERR_HW_HARD_RESET

2 L2

PLIM-2-ERR_HW_HARD_RESET

2 L2

PLIM-2-ERR_HW_HARD_RESET

2 L2

PLIM-2-ERR_HW_HARD_RESET

2 L2

PLIM-2-ERR_HW_HARD_RESET

2 L2

PLIM-2-ERR_HW_THRESHOLD_HARD_RESET

2 L2

PLIM-2-ERR_HW_THRESHOLD_HARD_RESET

2 L2

PLIM-2-ERR_HW_THRESHOLD_HARD_RESET

2 L2

PLIM-2-ERR_HW_THRESHOLD_HARD_RESET

2 L2

PLIM-2-ERR_HW_THRESHOLD_HARD_RESET

2 L2

PLIM-2-FPGA_IMG_ERR

2 L2

PLIM-2-FPGA_IMG_ERR

2 L2

PLIM-2-FPGA_IMG_ERR

2 L2

PLIM-2-FPGA_IMG_ERR

2 L2

PLIM-2-FPGA_IMG_ERR

2 L2

PLIM-2-FPGA_SW_REV_MISMATCH

2 L2

PLIM-2-FPGA_SW_REV_MISMATCH

2 L2

PLIM-2-FPGA_SW_REV_MISMATCH

2 L2

PLIM-2-FPGA_SW_REV_MISMATCH

2 L2

PLIM-2-HW_INIT_ERR

2 L2

PLIM-2-HW_INIT_ERR

2 L2

PLIM-2-HW_INIT_ERR

2 L2

PLIM-2-HW_INIT_ERR

2 L2

PLIM-2-OBI_EXCESS_SBE

2 L2

PLIM-2-OBI_EXCESS_WDT

2 L2

PLIM-2-PHY_CLOCK_PERSIST

2 L2

PLIM-2-PHY_CLOCK_PERSIST

2 L2

PLIM-2-PHY_CLOCK_PERSIST

2 L2

PLIM-2-PHY_XAUI_THRESH

2 L2

PLIM-2-PHY_XAUI_THRESH

2 L2

PLIM-2-PHY_XAUI_THRESH

2 L2

PLIM-2-PPS_ACCESS_PERSIST

2 L2

PLIM-2-PPS_ACCESS_PERSIST

2 L2

PLIM-2-PPS_ACCESS_PERSIST

2 L2

PLIM-2-XFP_ALARM_THRESH

2 L2

PLIM-2-XFP_ALARM_THRESH

2 L2

PLIM-2-XFP_ALARM_THRESH

2 L2

PLIM-2-XFP_NPOWER_THRESH

2 L2

PLIM-2-XFP_NPOWER_THRESH

2 L2

PLIM-2-XFP_NPOWER_THRESH

2 L2

PLIM-3-CHK_ERR

3 L2

PLIM-3-ERR

3 L2

PLIM-3-ERR_HW_SHUTDOWN_PORT

3 L2

PLIM-3-ERR_HW_SHUTDOWN_PORT

3 L2

PLIM-3-ERR_HW_SHUTDOWN_PORT

3 L2

PLIM-3-ERR_HW_SHUTDOWN_PORT

3 L2

PLIM-3-ERR_HW_SHUTDOWN_PORT

3 L2

PLIM-3ERR_HW_THRESHOLD_SHUTDOWN_PORT

3 L2

PLIM-3ERR_HW_THRESHOLD_SHUTDOWN_PORT

3 L2

PLIM-3ERR_HW_THRESHOLD_SHUTDOWN_PORT

3 L2

PLIM-3ERR_HW_THRESHOLD_SHUTDOWN_PORT

3 L2

PLIM-3ERR_HW_THRESHOLD_SHUTDOWN_PORT

3 L2

PLIM-3ERR_HW_THRESHOLD_SHUTDOWN_PORT

3 L2

PLIM-3-HW_ERR

3 L2

PLIM-3-HW_INIT_ERR

3 L2

PLIM-3-HW_INIT_ERR

3 L2

PLIM-3-HW_INIT_ERR

3 L2

PLIM-3-IMDR_ERR

3 L2

PLIM-3-INCONSISTENT_CONFIG

3 L2

PLIM-3-INTERRUPT_ERR

3 L2

PLIM-3-INTERRUPT_ERR

3 L2

PLIM-3-INTERRUPT_ERR

3 L2

PLIM-3-MEM_ERR

3 L2

PLIM-3-OPTICS_LINE_RATE_UNSUPPORTED

3 L2

PLIM-3-PHY_ACCESS_PERSIST

3 L2

PLIM-3-PHY_ACCESS_PERSIST

3 L2

PLIM-3-PHY_ACCESS_PERSIST

3 L2

PLIM-3-SFPPLUS_ACCESS_PERSIST

3 L2

PLIM-3-SQUID_ERR

3 L2

PLIM-3-SW_ERR

3 L2

PLIM-3-SW_ERR

3 L2

PLIM-3-SW_ERR

3 L2

PLIM-3-SW_ERR

3 L2

PLIM-3-SW_INIT_ERR

3 L2

PLIM-3-SW_INIT_ERR

3 L2

PLIM-3-SW_INIT_ERR

3 L2

PLIM-3-SW_INIT_ERR

3 L2

PLIM-3-SW_INIT_ERR

3 L2

PLIM-3-SW_INIT_ERR

3 L2

PLIM-3-SW_INIT_ERR

3 L2

PLIM-3-XFP_ACCESS_PERSIST

3 L2

PLIM-3-XFP_ACCESS_PERSIST

3 L2

PLIM-3-XFP_ACCESS_PERSIST

3 L2

PLIM-3-XFP_EEPROM_CORRUPTION

3 L2

PLIM-3-XFP_HOTSWAP_PERSIST

3 L2

PLIM-3-XFP_HOTSWAP_PERSIST

3 L2

PLIM-3-XFP_HOTSWAP_PERSIST

3 L2

PLIM-3-XFP_LINE_RATE_UNSUPPORTED

3 L2

PLIM-4-BER_ALARM

4 L2

PLIM-4-CFP_INFO

4 L2

PLIM-4-CFP_INFO

4 L2

PLIM-4-CFP_INFO

4 L2

PLIM-4-ERR_HW

4 L2

PLIM-4-ERR_HW

4 L2

PLIM-4-ERR_HW

4 L2

PLIM-4-ERR_HW

4 L2

PLIM-4-ERR_HW

4 L2

PLIM-4-ERR_HW

4 L2

PLIM-4-ERR_HW

4 L2

PLIM-4-ERR_HW_THRESHOLD

4 L2

PLIM-4-ERR_HW_THRESHOLD

4 L2

PLIM-4-ERR_HW_THRESHOLD

4 L2

PLIM-4-ERR_HW_THRESHOLD

4 L2

PLIM-4-ERR_HW_THRESHOLD

4 L2

PLIM-4-ERR_HW_THRESHOLD

4 L2

PLIM-4-ERR_HW_THRESHOLD

4 L2

PLIM-4-OPTICS_INFO

4 L2

PLIM-4-PHY_ACCESS

4 L2

PLIM-4-PHY_ACCESS

4 L2

PLIM-4-PHY_ACCESS

4 L2

PLIM-4-PHY_CLOCK

4 L2

PLIM-4-PHY_CLOCK

4 L2

PLIM-4-PHY_CLOCK

4 L2

PLIM-4-PHY_XAUI

4 L2

PLIM-4-PHY_XAUI

4 L2

PLIM-4-PHY_XAUI

4 L2

PLIM-4-PPS_ACCESS

4 L2

PLIM-4-PPS_ACCESS

4 L2

PLIM-4-PPS_ACCESS

4 L2

PLIM-4-SEU_INIT_ERR

4 L2

PLIM-4-SEU_INIT_ERR

4 L2

PLIM-4-SEU_INIT_ERR

4 L2

PLIM-4-SFPPLUS_ACCESS

4 L2

PLIM-4-SPA_HW_ERR

4 L2

PLIM-4-SPA_HW_ERR_THRESHOLD

4 L2

PLIM-4-XFP_ACCESS

4 L2

PLIM-4-XFP_ACCESS

4 L2

PLIM-4-XFP_ACCESS

4 L2

PLIM-4-XFP_ALARM

4 L2

PLIM-4-XFP_ALARM

4 L2

PLIM-4-XFP_ALARM

4 L2

PLIM-4-XFP_HOTSWAP

4 L2

PLIM-4-XFP_HOTSWAP

4 L2

PLIM-4-XFP_HOTSWAP

4 L2

PLIM-4-XFP_NPOWER

4 L2

PLIM-4-XFP_NPOWER

4 L2

PLIM-4-XFP_NPOWER

4 L2

PLIM-4-XFP_WARN_RX_PWR

4 L2

PLIM-4-XFP_WARN_RX_PWR

4 L2

PLIM-4-XFP_WARN_TX_PWR

4 L2

PLIM-4-XFP_WARN_TX_PWR

4 L2

PLIM-5-CFP_OIR

5 L2

PLIM-5-CFP_OIR

5 L2

PLIM-5-CFP_OIR

5 L2

PLIM-5-OPTICS_OIR

5 L2

PLIM-6-IMDR_INFO

6 L2

PLIM-6-NO_POWER_SFPPLUS

6 L2

PLIM-6-NO_POWER_XFP

6 L2

PLIM-6-NO_POWER_XFP

6 L2

PLIM-6-NO_POWER_XFP

6 L2

PLIM-6-UNSUPPORTED_OPTICS

6 L2

PLIM-6-UNSUPPORTED_XFP

6 L2

PLIM-6-UNSUPPORTED_XFP

6 L2

PLIM-6-UNSUPPORTED_XFP

6 L2

PLIM-6-XFP_OIR

6 L2

PLIM-6-XFP_OIR

6 L2

PLIM-6-XFP_OIR

6 L2

PLIM-6-XFP_RETRY_EEPROM_RD

6 L2

PLIM-6-XFP_RETRY_READ

6 L2

PLIM-6-XFP_RETRY_READ

6 L2

pm5315-3-FATAL_ERROR

3 L2

pm5315-6-INFO_MSG

6 L2

pm5315-7-DEBUG_MSG

7 L2

pm5316-3-FATAL_ERROR

3 L2

pm5316-4-WARNING

4 L2

PM622-2-error

2 L2

PMSAR-2-CFG_ERR

2 L2

PMSAR-2-CHAN_STATS_ERR

2 L2

PMSAR-2-CLOSE_VC_COSQ_ERR

2 L2

PMSAR-2-CLOSE_VC_ERR

2 L2

PMSAR-2-CMD_ACK_ERR

2 L2

PMSAR-2-CMD_ERR

2 L2

PMSAR-2-CMD_POLL_TIMEOUT

2 L2

PMSAR-2-CMD_POST_ERR

2 L2

PMSAR-2-INITERR

2 L2

PMSAR-2-MUTEX_TIMEOUT

2 L2

PMSAR-2-OPEN_VC_ERR

2 L2

PMSAR-2-OPEN_VP_ERR

2 L2

PMSAR-2-PORT_STATS_ERR

2 L2

PMSAR-3-ESYS_ERR

3 L2

PMSAR-3-ESYS_LOAD_ELF

3 L2

PMSAR-3-EVENT_INDICATE

3 L2

PMSAR-3-UNKNOWN_EVENT

3 L2

PMSAR-4-WARNING

4 L2

PMSAR-6-event_dump
PMSAR-6-INFO

6 L2
6 L2

PMSAR-7-DEBUG

7 L2

POS-2-ERR_CFGMGR_CONNECT

2 L2

POS-2-ERR_INTERFACE_CREATE

2 L2

POS-2-NOMEM

2 L2

POS-2-NOT_MAX_PORT

2 L2

POS-3-ERR_FIM_REG

3 L2

POS-3-LTRACE_INIT

3 L2

POS-3-MTU_IMPOSE_FAILED

3 L2

POS-4-DB_ATTACH

4 L2

POS-4-ERR_INIT

4 L2

POS-4-LOST_EVENT

4 L2

POS-4-NOT_SUPP

4 L2

POS-4-PORT_CREATE

4 L2

POS-4-PORT_ENABLE

4 L2

POS-4-PORT_NOT_FOUND

4 L2

POS-6-SOFT_BANDWIDTH_CHANGE

6 L2

PP_CNSMR-3-RSI_ERROR

3 L2

PP_PRODUCER-3-PPINDEX_GLOBAL_ERROR

3 L2

PPP_EA-3-INIT_ERROR

3 L2

PPP_EA-4-ERR_BATCH_ALLOC

4 L2

PPP_EA-4-ERR_EVM_EVENT_BLOCK

4 L2

PPP_EA-4-ERR_INIT

4 L2

PPP_EA-4-ERR_MEM_ALLOC

4 L2

PPP_EA-4-ERR_RWMGR

4 L2

PPP_EA-4-ERR_RWMGR_IF

4 L2

PPP_EA-6-ERR_IM_MULTIPLE_NTFCNS

6 L2

PPP_FSM-3-ERR_SOCKET

3 L2

PPP_GBL_CFG-4-ERR_INIT

4 L2

PPP_LCP-3-AAA_SESSION_CLEANUP_FAILED

3 L2

PPP_LCP-3-MTU_UNUSABLE

3 L2

PPP_LCP-4-L2_NOT_SUPPORTED

4 L2

PPP_LCP-4-MISSING_AUTHENTICATION_LIST

4 L2

PPP_LCP-4-MTU_WARNING

4 L2

PPP_LCP-4MULTILINK_PROVISION_NOT_IP_IW

4 L2

PPP_LCP-4-UNEXPECTED_AAA_RESPONSE

4 L2

PPP_LCP-4-UNRECOGNIZED_PROTO

4 L2

PPP_LCP-5-MTU_NEGOTIATED

5 L2

PPP_LCP-6-LOCAL_MTU_TOO_SMALL

6 L2

PPP_lite-3-ERR_PL_DLL_ASYNC_SEND_FAIL

3 L2

PPP_lite-3ERR_PL_DLL_CHAN_CONNECT_FAIL

3 L2

PPP_lite-3-ERR_SHMEM_MMAP_FAIL

3 L2

PPP_lite-3-ERR_SHMEM_OPEN_FAIL

3 L2

PPP_lite-3-ERR_SHMEM_TRNC_FAIL

3 L2

PPP_lite-3-ERR_SHMEM_UNAVAILABLE

3 L2

PPP_MA-3-ERR_DUPLICATE_IPV4_ADDRESS

3 L2

PPP_MA-4-ERR_AAA

4 L2

PPP_MA-4-ERR_AAA_ATTR

4 L2

PPP_MA-4-ERR_AAA_ATTR_IF

4 L2

PPP_MA-4-ERR_AAA_SESSION

4 L2

PPP_MA-4-ERR_AAA_SESSION_IF

4 L2

PPP_MA-4-ERR_AIB

4 L2

PPP_MA-4-ERR_BACKEND

4 L2

PPP_MA-4-ERR_BAG

4 L2

PPP_MA-4-ERR_CHKPT

4 L2

PPP_MA-4-ERR_CHKPT_CORRUPT

4 L2

PPP_MA-4-ERR_CHKPT_DUPLICATE

4 L2

PPP_MA-4-ERR_CLOCK

4 L2

PPP_MA-4-ERR_DAPS

4 L2

PPP_MA-4-ERR_DAPS_IF

4 L2

PPP_MA-4-ERR_DEBUG

4 L2

PPP_MA-4-ERR_EVC_CLOSE

4 L2

PPP_MA-4-ERR_EVC_CREATE

4 L2

PPP_MA-4-ERR_EVC_ERROR

4 L2

PPP_MA-4-ERR_EVC_EVM_HANDLER

4 L2

PPP_MA-4-ERR_EVC_GET_FD

4 L2

PPP_MA-4-ERR_EVC_NOTIFY

4 L2

PPP_MA-4-ERR_EVC_OPEN

4 L2

PPP_MA-4-ERR_EVM_ATTACH

4 L2

PPP_MA-4-ERR_EVM_CREATE

4 L2

PPP_MA-4-ERR_EVM_SEND

4 L2

PPP_MA-4-ERR_EVQ_CREATE

4 L2

PPP_MA-4-ERR_EVQ_DEQUEUE

4 L2

PPP_MA-4-ERR_EVQ_ENQUEUE

4 L2

PPP_MA-4-ERR_IMC

4 L2

PPP_MA-4-ERR_IMC_IF

4 L2

PPP_MA-4-ERR_IPCP_OPTS_INCONSISTENT

4 L2

PPP_MA-4-ERR_IPCP_SCAN_IF

4 L2

PPP_MA-4-ERR_IPCPIW_SCAN_IF

4 L2

PPP_MA-4-ERR_IPHC

4 L2

PPP_MA-4-ERR_IPHC_CONFIG

4 L2

PPP_MA-4ERR_IPV6CP_OPTS_INCONSISTENT

4 L2

PPP_MA-4-ERR_IPV6CP_SCAN_IF

4 L2

PPP_MA-4-ERR_L2VPN

4 L2

PPP_MA-4-ERR_LAS

4 L2

PPP_MA-4-ERR_LTRACE

4 L2

PPP_MA-4-ERR_MEM_ALLOC

4 L2

PPP_MA-4-ERR_MGD_TIMER

4 L2

PPP_MA-4-ERR_NCP_CAPS_STALE

4 L2

PPP_MA-4-ERR_PAK

4 L2

PPP_MA-4-ERR_PLAT_PROPS

4 L2

PPP_MA-4-ERR_RIB

4 L2

PPP_MA-4-ERR_SSO_ALERT

4 L2

PPP_MA-4-ERR_SSRP

4 L2

PPP_MA-4-ERR_SUBDB

4 L2

PPP_MA-4-ERR_SUBDB_IF

4 L2

PPP_MA-4-ERR_SYSDB

4 L2

PPP_MA-4-ERR_SYSMGR

4 L2

PPP_MA-4-ERR_SYSMGR_MDR

4 L2

PPP_MA-4-ERR_THREAD

4 L2

PPP_MA-4-ERR_THREAD_COND

4 L2

PPP_MA-4-ERR_THREAD_CREATE

4 L2

PPP_MA-4-ERR_THREAD_MUTEX

4 L2

PPP_MA-4-ERR_UNSUPPORTED_PROTOCOL

4 L2

PPP_MA-4-ERR_WAVL_INIT

4 L2

PPP_MA-6-ERR_EVC_DESTROY

6 L2

PPP_MA-6-ERR_EVM_EVENT_BLOCK

6 L2

PPP_MA-6-ERR_EVQ_DESTROY

6 L2

PPP_NETIO-3-ERR_INTF_INIT

3 L2

PPP_NETIO-4-ERR_INIT

4 L2

PPP_NETIO-4-PAK_DROP

4 L2

PPP_NETIO-5-SUBBLOCK_VERSION

5 L2

PPP_SOCK-3-ERR_MEM_ALLOC

3 L2

PPP_SOCK-3-ERR_SYSMGR

3 L2

PPP_SOCK-4-ERR_EVM_EVENT_BLOCK

4 L2

PPP_SOCK-4-ERR_LTRACE_INIT

4 L2

PPP_SOCK-4-ERR_PAKMAN

4 L2

PPP_SOCK-4-INIT

4 L2

PRECAM-2-HW_RESOURCE_FAILURE

2 L2

PREFIX_COMPR-3-EVT_CONN_CREATE

3 L2

PREFIX_COMPR-3-EVT_CONN_OPEN

3 L2

PREFIX_COMPR-3-SYSDB_BIND

3 L2

PREFIX_COMPR-3-SYSDB_COID

3 L2

PREFIX_COMPR-3-SYSDB_VERIFY

3 L2

PREFIX_COMPR-6-V6_ANCHOR_PREFIX

6 L2

PSE_UIDB-7-ERR_INIT

7 L2

PSE-2-CRIT_EXIT

2 L2

PSE-2-CRIT_EXIT

2 L2

PSE-2-MIPC_STUCK

2 L2

PSE-2-NODE_BRINGDOWN

2 L2

PSE-2-NODE_BRINGDOWN

2 L2

PSE-3-DMA_ERROR_MSG

3 L2

PSE-3-ERR_EXIT

3 L2

PSE-3-ERR_EXIT

3 L2

PSE-3-ERROR_MSG

3 L2

PSE-3-HEALTH_MONITOR_ERROR_MSG

3 L2

PSE-3-HEALTH_MONITOR_ERROR_MSG

3 L2

PSE-3-INIT_ERROR_MSG

3 L2

PSE-3-INTERNAL_ERR

3 L2

PSE-3-INVALID_COUNT

3 L2

PSE-3-MP_CORE

3 L2

PSE-3-MSG_REPLY

3 L2

PSE-4-COLD_RESET_FAILED

4 L2

PSE-4-COLD_RESET_FAILED

4 L2

PSE-4-ERRRATE_EXCEED_FAST

4 L2

PSE-4-ERRRATE_EXCEED_FAST

4 L2

PSE-4-ERRRATE_EXCEED_GLACIAL

4 L2

PSE-4-ERRRATE_EXCEED_GLACIAL

4 L2

PSE-4-IMDR_RESET_FAILED

4 L2

PSE-4-PROTO_HW_VERSION

4 L2

PSE-4-PROTO_HW_VERSION

4 L2

PSE-4-WARM_RESET_FAILED

4 L2

PSE-4-WARM_RESET_FAILED

4 L2

PSE-5-ERR_CONT

5 L2

PSE-5-ERR_CONT

5 L2

PSE-5-TCAM_MISMATCH_COMPLETED

5 L2

PSE-5-TCAM_MISMATCH_DETECTED

5 L2

PSE-5-TCAM_MISMATCH_REPAIRED

5 L2

PSE-6-INFO_MSG

6 L2

PSE-6-INFO_MSG

6 L2

PSE-6-INFO_MSG

6 L2

PSE-6-MP_INFO

6 L2

PSE-7-DEBUG_MSG

7 L2

PSE-7-DEBUG_MSG

7 L2

PSE-7-MP_CORE

7 L2

PSELIB-4-EXIT_ON_ERR

4 L2

PTP-4-COMMS_RETRY_FAILED

4 L2

PTP-4-INIT_FAILED

4 L2

PTP-4-IP_ARM

4 L2

PTP-4-LOST_EVENT

4 L2

PTP-4-MEM_ALLOC

4 L2

PTP-4-MGD_TIMER

4 L2

PTP-4-MIB_DLL_ERROR

4 L2

PTP-4-PEER_INDEX_EXHAUST

4 L2

PTP-4-PORT_NUM_CHECKPOINT_READ_FAIL

4 L2

PTP-4-PORT_NUM_CONFLICT

4 L2

PTP-4-PORT_NUM_EXHAUST

4 L2

PTP-4-PRF_CFG_IGNORED

4 L2

PTP-4-SHUTDOWN_CHECK_FAILED

4 L2

PTP-4-SPIO

4 L2

PTP-4-STATS_DB_ERROR

4 L2

PTP-4-TIMER

4 L2

PTP-4-VLAN_TAG_GEN_FAILED

4 L2

PTP-6-BEST_MASTER_CLOCK_CHANGE

6 L2

PTP-6-BEST_MASTER_CLOCK_REMOVED

6 L2

PVSTAG-3-INTERFACE_RECOVERY_FAIL

3 L2

PVSTAG-3-TIMER_FAILED

3 L2

PVSTAG-4-CFG_BATCH_FAIL

4 L2

PVSTAG-4-CFG_FAIL

4 L2

PVSTAG-4-CHKPT_INCONSISTENT

4 L2

PVSTAG-4-CHKPT_SAVE_FAIL

4 L2

PVSTAG-4-ERROR_DISABLING_PORT

4 L2

PVSTAG-4-INIT_FAIL

4 L2

PVSTAG-4-MALFORMED_PACKET

4 L2

PVSTAG-4-PREEMPT_TIMER_FAIL

4 L2

PVSTAG-4-PROBLEM_EXITING

4 L2

PVSTAG-4-RECEIVE_FAIL

4 L2

PVSTAG-4-SEND_FAIL

4 L2

PVSTAG-4-STANDBY_RESTART

4 L2

PVSTAG-4-SUBINTERFACE

4 L2

PVSTAG-4-UNEXPECTED_BPDU_RECEIVED

4 L2

PVSTAG-4-VLAN_INSTANCE_LIMIT

4 L2

QFP_BQS-6-SRTMEMLOW_CLEAR

6 L2

QFP_BQS-6-SRTMEMLOW_DECLARE

6 L2

QFP_DRIVER-2-HALT

2 L2

QFP_DRIVER-2-INTR

2 L2

QFP_DRIVER-2-LOCKDOWN

2 L2

QFP_DRIVER-3-ACQUIRE_LOCK_FAILED

3 L2

QFP_DRIVER-3-ALLOCATE_NOTIFY

3 L2

QFP_DRIVER-3-ATTACH_FAIL

3 L2

QFP_DRIVER-3-CLEANUP_NOTIFY

3 L2

QFP_DRIVER-3-CREATE_FAILED

3 L2

QFP_DRIVER-3-DESTROY_NOTIFY

3 L2

QFP_DRIVER-3-GET_DETAILS_FAILED

3 L2

QFP_DRIVER-3-HOT

3 L2

QFP_DRIVER-3-INIT_FAILED

3 L2

QFP_DRIVER-3-INIT_FAILURE

3 L2

QFP_DRIVER-3-INIT_NOTIFY

3 L2

QFP_DRIVER-3-INIT_NOTIFY_ID

3 L2

QFP_DRIVER-3-INTERNAL

3 L2

QFP_DRIVER-3-MEM_CLEAR_FAILED

3 L2

QFP_DRIVER-3-MEM_SIZE_FAILED

3 L2

QFP_DRIVER-3-MEM_WRITE_FAILED

3 L2

QFP_DRIVER-3-PLAT_DB_FAILURE

3 L2

QFP_DRIVER-3-RELEASE_LOCK_FAILED

3 L2

QFP_DRIVER-3-TCAM_PERR

3 L2

QFP_DRIVER-3-TCAM_PERR_FAILURE

3 L2

QFP_DRIVER-3-UNSUPPORT

3 L2

QFP_DRIVER-3-WARN_MESSAGE

3 L2

QFP_DRIVER-4-ADRSPC_LIMIT

4 L2

QFP_DRIVER-6-ACCTRC128B

6 L2

QFP_DRIVER-6-ACCTRC64B

6 L2

QFP_EXMEM-3-EXTRL_MEM_MGR_FAILURE

3 L2

QFP_EXMEM-7-DEBUG_MSG

7 L2

QFP_FM_LIB-6-V6_ANCHOR_PREFIX

6 L2

QFP_FM-6-FIELD_IGNORED

6 L2

QFP_IFM-3-LIB_FAILURE

3 L2

QFP_IFM-3-WARN_LIB_FAILURE

3 L2

QFP_LPTS_EA-3-INIT

3 L2

QFP_MDM-3-METADATA_FAILURE

3 L2

QFP_MDM-7-DEBUG_MSG

7 L2

QFP_PFILTER_EA-3-INIT

3 L2

QFP_SBS-3-STATS_BLOCK_FAILURE

3 L2

QFP_TCAM_RM-3-LOG_FAILURE

3 L2

QFP_TCAM_RM-6-HIGH_WATER_MARK

6 L2

QFP_TCAM_RM-6-LOW_WATER_MARK

6 L2

QFP_UIDB-3-MNGR_FAILURE

3 L2

QFP_UIDB-7-DEBUG_MSG

7 L2

QFP_XCONNECT-3-XCONNECT_CONFIG_ERR

3 L2

QM_E5-3-SANITY_HEAD_DUMP

3 L2

QM_E5-3-SANITY_RELOAD

3 L2

QM_E5-3-SANITY_TAIL_DUMP

3 L2

QM_E5-3-SANITY_WARNING

3 L2

QM_E5-4-INTERRUPT

4 L2

QM_E5-4-INTERRUPT2

4 L2

QM_E5-6-INFO_MSG_SBE

6 L2

QM_E5-7-INTERRUPT3

7 L2

QM_E5-7-INTERRUPT4

7 L2

QM_E5-7-INTERRUPT5

7 L2

QM_E5-7-INTERRUPT6

7 L2

QM-3-SANITY_RELOAD

3 L2

QM-3-SANITY_WARNING

3 L2

QM-4-INTERRUPT

4 L2

QUEUEING-3-FATAL_ERR

3 L2

RDM_CFG-1ERR_WARNING_RDM_CFG_MISMATCH_ALL

1 L2

RDM_CFG-1ERR_WARNING_RDM_CFG_MISMATCH_LOC

1 L2

RSMLIB-3-EXIT_ON_ERR

3 L2

RSMLIB-4-EXIT_ON_ERR

4 L2

Serial-3-MTU_IMPOSE_FAILED

3 L2

Serial-3-NULL_HW_FUNC

3 L2

Serial-4-ALARM

4 L2

SLARP_LITE-3ERR_CSL_DLL_ASYNC_SEND_FAIL

3 L2

SLARP_LITE-3ERR_CSL_DLL_CHAN_CONNECT_FAIL

3 L2

SLARP_LITE-3-ERR_SHMEM_MMAP_FAIL

3 L2

SLARP_LITE-3-ERR_SHMEM_OPEN_FAIL

3 L2

SLARP_LITE-3-ERR_SHMEM_TRNC_FAIL

3 L2

SLARP_LITE-3-ERR_SHMEM_UNAVAILABLE

3 L2

SLOGIC-4-ANOMALY

4 L2

SONET_APS-4-WARNING

4 L2

SONET_APS-4-WP_INFO

4 L2

SONET_APS-6-CONFLICT

6 L2

SONET_APS-6-CONTACT

6 L2

SONET_APS-6-K1K2_INFO

6 L2

SONET_APS-6-REQUEST_PREEMPTED

6 L2

SONET_APS-6-SWITCH_INFO

6 L2

SONET_APS-6-UPDOWN

6 L2

SONET_APS-7-ERROR

7 L2

SONET_APS-7-NOMEM

7 L2

SONET_LOCAL-3-ERROR

3 L2

SONET_LOCAL-4-ALARM

4 L2

SONET_LOCAL-5-AIS_PWFAULT

5 L2

SONET_LOCAL-6-CLEAR_COUNTERS

6 L2

SPA_192-3-ERR_SPA_UNSUPPORTED

3 L2

SPA_192-3-ERR_SPA_UNSUPPORTED

3 L2

SPA_192-3-JACKET_ERROR

3 L2

SPA_192-3-JACKET_V2_ERROR

3 L2

SPA_192-3-SPARULE_INT_ERROR

3 L2

SPA_192-4-FAIL_READ_CARD

4 L2

SPA_192-4-GET_CHASSIS_FAILED

4 L2

SPA_192-4-READ_FAIL_CARDTYPE

4 L2

SPA_192-4-SPARULE_FAIL

4 L2

SPA_192-6-INITIALIZE_FAILED

6 L2

SPA_192-6-JACKET_PROCESS

6 L2

SPA_192-6-QOSRM_SPA_ALLOC

6 L2

SPA_192-6-SPARULE_ERROR
SPA_192-6-UPGRADE_FPGA
SPA_192-6-UPGRADE_FPGA

6 L2
6 L2
6 L2

SPA_ATM_V2-2-DRIVER_CRIT_ERR

2 L2

SPA_ATM_V2-2-SOFTWARE_PARAM_ERROR

2 L2

SPA_ATM_V2-3-DRIVER_ERR

3 L2

SPA_ATM_V2-3-LTRACE_INIT_ERROR

3 L2

SPA_ATM_V2-3-SHEM_ERROR

3 L2

SPA_ATM_V2-4-DRIVER_WARN

4 L2

SPA_ATM_V2-6-INFO

6 L2

SPA_ATM_V2-7-DEBUG

7 L2

SPA_BARB-2-SAR_EXCEED_MAX_VALUE

2 L2

SPA_BARB-2-SAR_FAIL

2 L2

SPA_BARB-2-SAR_REPORT_ISSUE

2 L2

SPA_BARB-2-SPA_FAIL

2 L2

SPA_BARB-2-TCAM_CORRUPT

2 L2

SPA_BARB-3-LTRACE_INIT_FAIL

3 L2

SPA_BARB-3-SAR_INVALID_INFO

3 L2

SPA_BARB-3SHARED_MEMORY_INCONSISTENCY

3 L2

SPA_BARB-3-ZERO_VOLTAGE

3 L2

SPA_BARB-4-SAR_REPORT_LOCATION

4 L2

SPA_BARB-4-SAR_REPORT_TCAM_ISSUE

4 L2

SPA_BARB-6-DUMP_SAR

6 L2

SPA_BARB-6-SAR_REPORT_STATUS

6 L2

SPA_C_SHIM-3-AIB_INIT_FAILED

3 L2

SPA_C_SHIM-3-AIB_INIT_FAILED

3 L2

SPA_C_SHIM-3C_SHIM_QUERY_INTERNAL_FAILED

3 L2

SPA_C_SHIM-3C_SHIM_QUERY_INTERNAL_FAILED

3 L2

SPA_C_SHIM-3EVENT_MANAGER_CREATE_FAILED

3 L2

SPA_C_SHIM-3EVENT_MANAGER_CREATE_FAILED

3 L2

SPA_C_SHIM-3-FIND_SHIM_FAIL

3 L2

SPA_C_SHIM-3-FREE_FAIL

3 L2

SPA_C_SHIM-3-FREE_FAIL

3 L2

SPA_C_SHIM-3-GET_SHIM_INFO_FAIL

3 L2

SPA_C_SHIM-3-GET_SHIM_INFO_FAIL

3 L2

SPA_C_SHIM-3-INIT_CHECK_FAIL

3 L2

SPA_C_SHIM-3-INIT_CHECK_FAIL

3 L2

SPA_C_SHIM-3-MALLOC_FAIL

3 L2

SPA_C_SHIM-3-MALLOC_FAIL

3 L2

SPA_C_SHIM-3-MALLOC_FAIL1

3 L2

SPA_C_SHIM-3-NULL_SHIM_INFO

3 L2

SPA_C_SHIM-3-NULL_SHIM_INFO

3 L2

SPA_C_SHIM-3-PLATFORM_INFO_FAIL

3 L2

SPA_C_SHIM-3-PTHREAD_CREATE_FAILED

3 L2

SPA_C_SHIM-3-PTHREAD_CREATE_FAILED

3 L2

SPA_C_SHIM-3-QUERY_FAIL

3 L2

SPA_C_SHIM-3-QUERY_FAIL

3 L2

SPA_C_SHIM-3-RESET_FN_PTRS_FAIL

3 L2

SPA_C_SHIM-3-RESET_FN_PTRS_FAIL

3 L2

SPA_C_SHIM-3-SERVER_BAY_FAILED

3 L2

SPA_C_SHIM-3-SERVER_BAY_FAILED

3 L2

SPA_C_SHIM-3-SHWIN_OPEN_FAIL

3 L2

SPA_C_SHIM-3-SHWIN_OPEN_FAIL

3 L2

SPA_C_SHIM-3-SPA_SMLIB_CLIENT_FAILED

3 L2

SPA_C_SHIM-3-TREE_LOCK_FAIL

3 L2

SPA_C_SHIM-3-TREE_LOCK_FAIL

3 L2

SPA_C_SHIM-3-TREE_UNLOCK_FAIL

3 L2

SPA_C_SHIM-3-TREE_UNLOCK_FAIL

3 L2

SPA_C_SHIM-4-PLATFORM_INFO_FAIL

4 L2

SPA_C_SHIM-6C_SHIM_QUERY_INTERNAL_ENTERED

6 L2

SPA_C_SHIM-6C_SHIM_QUERY_INTERNAL_ENTERED

6 L2

SPA_C_SHIM-6-CREATE_SHIM_ENTRY

6 L2

SPA_C_SHIM-6-CREATE_SHIM_ENTRY

6 L2

SPA_C_SHIM-6-DELETE_SHIM_ENTRY

6 L2

SPA_C_SHIM-6-DELETE_SHIM_ENTRY

6 L2

SPA_C_SHIM-6-ENCAP_TYPE

6 L2

SPA_C_SHIM-6-ENCAP_TYPE

6 L2

SPA_C_SHIM-6-PLATFORM_FIX_SPA_ENCAP

6 L2

SPA_C_SHIM-6-PLATFORM_FIX_SPA_ENCAP

6 L2

SPA_C_SHIM-6-READ_FROM_SHM

6 L2

SPA_C_SHIM-6-READ_SHM_ENCAP

6 L2

SPA_C_SHIM-6-READ_SHM_INFO

6 L2

SPA_C_SHIM-6-READING_FROM_SHIM

6 L2

spa_cema_platform-3-AIB_INIT_FAILED

3 L2

SPA_CEOP-3-CEM_CONFIG_EXIST

3 L2

SPA_CEOP-3-INVALID_CARD_TYPE

3 L2

SPA_CEOP-3-L3QOS_CONFIGS_EXIST

3 L2

SPA_CEOP-3-SONET_CONFIG_EXIST

3 L2

SPA_CEOP-3-SPA_MODE_UNSUPPORTED

3 L2

SPA_CEOP-3-SYSDB_BIND_FAIL

3 L2

SPA_CEOP-6-REMOVE_CONFIG

6 L2

SPA_CEOP-6-SPA_RELOAD_CARD_TYPE

6 L2

SPA_CHOC_DSX-1-SPA_RESET

1 L2

SPA_CHOC_DSX-1-SPA_RESET_NEEDED

1 L2

SPA_CHOC_DSX-3-CTRL_NOT_INITIALIZED

3 L2

SPA_CHOC_DSX-3HDLC_ERR_CHNL_QUE_OV_STAT

3 L2

SPA_CHOC_DSX-3HDLC_ERR_CHNL_QUE_OV_STAT

3 L2

SPA_CHOC_DSX-3-INVALID_CMD

3 L2

SPA_CHOC_DSX-3-NULL_PD_FIELD

3 L2

SPA_CHOC3_DSX-1-SPA_RESET_NEEDED

1 L2

SPA_ETHER-1-LTRACE_INIT_ERR

1 L2

SPA_ETHER-2-LTRACE_RETRY_ERR

2 L2

SPA_ETHER-2-MODE_CHANGE

2 L2

SPA_ETHER-2-SPA_CTX_ERR

2 L2

SPA_ETHER-2-SPA_JKT_ERR

2 L2

SPA_ETHER-2-SPA_MAC_ERR

2 L2

SPA_ETHER-3ATTACH_ECM_NOTIFY_HANDLER_FOR_EDM_
FAILED

3 L2

SPA_ETHER-3-BAG_ENCODE_FAILED

3 L2

SPA_ETHER-3-BAG_REGISTRATION_FAILED

3 L2

SPA_ETHER-3CLOSING_ETHER_SHIM_CONTROL_SERVER_
FAILED

3 L2

SPA_ETHER-3CREATE_ECM_FOR_EDM_FAILED

3 L2

SPA_ETHER-3DESTROY_SYSDB_ECM_FAILED

3 L2

SPA_ETHER-3DESTROYING_EVENT_MANAGER_FAILED

3 L2

SPA_ETHER-3-EDM_ECM_OPEN_FAILED

3 L2

SPA_ETHER-3ETHER_HW_HELPER_INIT_FAILED

3 L2

SPA_ETHER-3ETHER_SHIM_CAPS_CONTROL_SERVER_OPE
N_BAY_FAILED

3 L2

SPA_ETHER-3ETHER_SPA_EVENT_MANAGER_CREATE_FAIL
ED

3 L2

SPA_ETHER-3-ETHER_SPA_INIT_FAILED

3 L2

SPA_ETHER-3ETHER_SPA_NAME_NOTMATCHING

3 L2

SPA_ETHER-3-GET_PORT_NODEID_FAILED

3 L2

SPA_ETHER-3-GET_PROCESS_NAME_FAILED

3 L2

SPA_ETHER-3-GET_RX_UIDB_FAILED

3 L2

SPA_ETHER-3GET_RX_UIDB_FOR_B_IFH_FAILED

3 L2

SPA_ETHER-3GET_SYSDB_FD_FOR_EDM_FAILED

3 L2

SPA_ETHER-3-GET_UIDB_FAILED

3 L2

SPA_ETHER-3GILA_FUGU_RECONFIG_NEEDED_FAILED

3 L2

SPA_ETHER-3-GILA_FUGU_RESTART_FAILED

3 L2

SPA_ETHER-3GILA_FUGU_TCAM_RECONFIG_NEEDED

3 L2

SPA_ETHER-3-GILA_TCAM_RESTART_FAILED

3 L2

SPA_ETHER-3-INCONSISTENT_CONFIG

3 L2

SPA_ETHER-3-INVALID_ARGUMENTS

3 L2

SPA_ETHER-3MAC_RECONFIG_NEEDED_FAILED

3 L2

SPA_ETHER-3-MAC_RESTART_FAILED

3 L2

SPA_ETHER-3-MAC_SET_PORTTYPE_FAILED

3 L2

SPA_ETHER-3NAMING_ETHER_SPA_THREAD_FOR_BAY_FAI
LED

3 L2

SPA_ETHER-3-NULL_ETHER_SPA

3 L2

SPA_ETHER-3-OUT_OF_MEMORY

3 L2

SPA_ETHER-3-PLUGIN_ANALYZE_FAILED

3 L2

SPA_ETHER-3-PLUGIN_CONTEXT_NULL

3 L2

SPA_ETHER-3-PORT_DEL_TIMEOUT

3 L2

SPA_ETHER-3-PORT_ENABLING_FAILED

3 L2

SPA_ETHER-3-PTHREAD_CANCEL_FAILED

3 L2

SPA_ETHER-3-PTHREAD_CREATE_FAILED

3 L2

SPA_ETHER-3QINQ_CONFIG_NOT_SUPPORTED

3 L2

SPA_ETHER-3-QINQ_CREATION_FAILED

3 L2

SPA_ETHER-3SERDES_RECONFIG_NEEDED_FAILED

3 L2

SPA_ETHER-3-SET_POLICY_FAILED

3 L2

SPA_ETHER-3-SET_TUNNEL_MODE_FAILED

3 L2

SPA_ETHER-3SYSDB_ALREADY_REGISTERED_FOR_THIS_P
ATH

3 L2

SPA_ETHER-3-SYSDB_BIND_FAILED

3 L2

SPA_ETHER-3-SYSDB_BIND_FAILURE

3 L2

SPA_ETHER-3-SYSDB_EDM_FNS_INIT_FAILED

3 L2

SPA_ETHER-3-SYSDB_ITEM_GET_FAILED

3 L2

SPA_ETHER-3SYSDB_REGISTER_EDM_FAILED

3 L2

SPA_ETHER-3-TENABO_RESTART_FAILED

3 L2

SPA_ETHER-3-UNSUCCESSFUL_ATTACH_PHY

3 L2

SPA_ETHER-3UNSUCCESSFUL_ATTACH_SERDES

3 L2

SPA_ETHER-3UNSUCCESSFUL_ATTACH_TENABO

3 L2

SPA_ETHER-3-UNSUCCESSFUL_ATTACH_UT2

3 L2

SPA_ETHER-3-UT2_RESTART_FAILED

3 L2

SPA_ETHER-3VLAN_CREATION_FOR_PORT_FAILED

3 L2

SPA_ETHER-3-VPA_DEBUG_INIT_FAILED

3 L2

SPA_ETHER-3-VPA_GILA_EDM_INIT_FAILED

3 L2

SPA_ETHER-3WAITING_FOR_WANPHY_CONFIG_RESTORE

3 L2

SPA_ETHER-3WANPHY_CONTROLLER_INIT_FAILED

3 L2

SPA_ETHER-3XCVR_GET_SHOW_DATA_NOT_PLUGGABLE_
OPTICS_SUCCESS

3 L2

SPA_ETHER-3XCVR_INITIALIZATION_ON_SPA_FAILED

3 L2

SPA_ETHER-3-XCVR_RESTART_FAILED

3 L2

SPA_ETHER-3XCVR_SM_CREATION_TIMER_FAILED

3 L2

SPA_ETHER-4-INVALID_MAC

4 L2

SPA_ETHER-4-PORT_DEL_WARNING

4 L2

SPA_ETHER-4-SPA_WARN_RX_PWR

4 L2

SPA_ETHER-4-WAIT_CONFIG

4 L2

SPA_ETHER-6-PORT_DEL_INFO
SPA_ETHER-6-PORTS

6 L2
6 L2

SPA_ETHER-6-SPA_POWER_CYCLED

6 L2

SPA_FPD-3-FATAL_ERROR

3 L2

SPA_FPD-3-GET_IMG_ERROR

3 L2

SPA_FPD-3-GET_VERSION_ERROR

3 L2

SPA_FPD-3-SW_ERROR

3 L2

SPA_FPD-3-UPDATE_FAILED

3 L2

SPA_FPD-3-WRONG_OIR_STATE

3 L2

SPA_FPD-5-OFFLINE_NOTICE

5 L2

SPA_FPD-5-RELOAD_NOTICE

5 L2

SPA_FPD-6-UPDATE_PASSED

6 L2

SPA_FPD-6-UPDATE_START

6 L2

SPA_OC3_OC12-3-DRV_INIT_ERR

3 L2

SPA_OC3_OC12-3-ERR_IF

3 L2

SPA_OC3_OC12-3-ERR_IF

3 L2

SPA_OC3_OC12-3-ERR_PLUGIN

3 L2

SPA_OC3_OC12-3-ERR_PLUGIN

3 L2

SPA_OC3_OC12-3-ERR_RESTART

3 L2

SPA_OC3_OC12-3-ERR_RESTART

3 L2

SPA_OC3_OC12-3-ERR_SFP

3 L2

SPA_OC3_OC12-3-ERR_SFP

3 L2

SPA_OC3_OC12-3-GENERIC_ERROR

3 L2

SPA_OC3_OC12-3-GET_NODEID_ERR

3 L2

SPA_OC3_OC12-3-LTRACE_INIT_ERR
SPA_OC3_OC12-6-INFO

3 L2
6 L2

SPA_OC3_OC12-6-INFO

6 L2

SPA_OC3_OC12-6-OPTICS_OIR

6 L2

SPA_OC48-3-DRV_INIT_ERR

3 L2

SPA_OC48-3-ERR_INIT

3 L2

SPA_OC48-3-ERR_INIT

3 L2

SPA_OC48-3-ERR_SFP_OIR

3 L2

SPA_OC48-3-ERR_SFP_OIR

3 L2

SPA_OC48-3-GENERIC_ERROR

3 L2

SPA_OC48-3-GET_NODEID_ERR

3 L2

SPA_OC48-6-INFO

6 L2

SPA_OC48-6-OPTICS_INSERTION

6 L2

SPA_OC48-6-OPTICS_INSERTION

6 L2

SPA_OC48-6-OPTICS_REMOVAL

6 L2

SPA_OC48-6-OPTICS_REMOVAL

6 L2

SPA_OC48-7-DEBUG

7 L2

SPA_PD_CEM-2-ERR

2 L2

SPA_PD_CEM-2-ERR_STS

2 L2

SPA_PLIM_SB-3-FPD_GETVER_FAIL

3 L2

SPA_PLIM_SB-3-FPD_IMG_DNLD_ERROR

3 L2

SPA_PLIM_SB-3-FPD_IMG_UPD_ERROR

3 L2

SPA_PLIM_SB-3-MSG_REPLY_FAIL

3 L2

SPA_PLIM_SB-3-MSG_SEND_FAIL

3 L2

SPA_PLIM_SB-3-OPEN_CH_FAIL

3 L2

SPA_PLIM_SB-3-SPA_FW_ERR

3 L2

SPA_PLIM_SB-3-SW_ERROR

3 L2

SPA_T3E3-6-SPA_RELOAD_INFO

6 L2

SPA-3-BOOT_IPSEC_FAIL

3 L2

SPA-3-BUS_CREATE_FAIL

3 L2

SPA-3-BUS_FAILURE

3 L2

SPA-3-CMD_TIMEOUT

3 L2

SPA-3-CREATE_TIMER_FAIL

3 L2

SPA-3-DEBUG_INIT_FAILED

3 L2

SPA-3-DOWNLOAD_FIRMWARE_TIMEOUT

3 L2

SPA-3-ECM_FAILED

3 L2

SPA-3-ECM_FAILED

3 L2

SPA-3-ERR

3 L2

SPA-3-EVENT_MANAGER_CREATE_FAIL

3 L2

SPA-3-EVENT_MANAGER_DESTROY_FAIL

3 L2

SPA-3-EVENT_MANAGER_FAIL

3 L2

SPA-3-FAIL_TO_GET_FPD

3 L2

SPA-3-FAIL_TO_GET_INFO

3 L2

SPA-3-FAILED

3 L2

SPA-3-FIRMWARE_DOWNLOAD_FAIL

3 L2

SPA-3-FLAG_VALUE

3 L2

SPA-3-FPD_RECEIVE_FAIL

3 L2

SPA-3-FPD_UPGRADE_FAIL

3 L2

SPA-3-FPD_VERSION_TIMEOUT

3 L2

SPA-3-FSM_CHECK_FAIL

3 L2

SPA-3-FSM_CREATE_FAIL

3 L2

SPA-3-FSM_EXEC_FAIL

3 L2

SPA-3-FSM_PUSH_FAIL

3 L2

SPA-3-FUD_ALLOC_FAIL

3 L2

SPA-3-HLPR_SYSDB_INIT_FAILED

3 L2

SPA-3-INVALID_BAY

3 L2

SPA-3-INVALID_CONSOLE_CONTEXT

3 L2

SPA-3-INVALID_DEVICE_PARAMETER

3 L2

SPA-3-INVALID_PLUGIN_PARAMETER

3 L2

SPA-3-INVALID_SLOT

3 L2

SPA-3-INVALID_SPA_PARAMETER

3 L2

SPA-3-IPSEC_SPA_CRASH

3 L2

SPA-3-KILL_PROCESS_FAIL

3 L2

SPA-3-LOCAL_SPI_CLOCK_TIMEOUT

3 L2

SPA-3-LRD_DLRSC_FAILED

3 L2

SPA-3-LWM_UNINITIALIZED

3 L2

SPA-3-MAP_FAILED

3 L2

SPA-3-MESSAGE_HEADER_ATTACH_FAIL

3 L2

SPA-3-MMAP_FAIL

3 L2

SPA-3-NO_MEMORY

3 L2

SPA-3-NO_SPACE_ALLOC_MEMORY

3 L2

SPA-3-NULL_EVM

3 L2

SPA-3-NULL_SPA

3 L2

SPA-3-PLIM_HEARTBEAT_ERR

3 L2

SPA-3-PM_ERR

3 L2

SPA-3-POST_FAIL

3 L2

SPA-3-POST_TIMEOUT

3 L2

SPA-3-POWER_FAILURE

3 L2

SPA-3-PROCESS_START_FAIL

3 L2

SPA-3-PROM_TIMEOUT

3 L2

SPA-3-PTHREAD_CREATE_FAIL

3 L2

SPA-3-REGISTRATION_TIMEOUT

3 L2

SPA-3-SHMEM_MAP_FAIL

3 L2

SPA-3-SHMEM_OPEN_FAIL

3 L2

SPA-3-SPA_SPI_CLOCK_TIMEOUT

3 L2

SPA-3-SPA_SPI_INITIALIZE_TIMEOUT

3 L2

SPA-3-SPACP_BUFFER_ALLOC_FAIL

3 L2

SPA-3-SPACP_INITIALIZE_FAIL

3 L2

SPA-3-SPACP_MSG_SEND_FAIL

3 L2

SPA-3-SPACP_OPCODE_UNKNOWN

3 L2

SPA-3-SPALM_CONFIG_FAIL

3 L2

SPA-3-SPALM_TIMEOUT

3 L2

SPA-3-SPASM_TIMEOUT

3 L2

SPA-3-SYSDB_ERROR

3 L2

SPA-3SYSMGR_BLOCK_UNTIL_PRIMARY_FAILED

3 L2

SPA-3-SYSMGR_DEF_ATTR_FAIL

3 L2

SPA-3-SYSMGR_GET_PROC_ROLE_FAILED

3 L2

SPA-3-SYSMGR_PROC_READY_FAILED

3 L2

SPA-3-THREAD_NAME_FAILED

3 L2

SPA-4-CERR_REGISTRATION_FAILURE

4 L2

SPA-4-WANPHY_SPA_TIMEOUT

4 L2

SPA-5-APPS_IMAGE_DOWNLOADING

5 L2

SPA-5-APPS_IMAGE_ERROR

5 L2

SPA-5-APPS_IMAGE_SIZE_ERR

5 L2

SPA-5-DOWNLOAD_METHOD_ERR

5 L2

SPA-5-FILE_SIZE_ERR

5 L2

SPA-5-OIR_ERROR
SPA-5-OIR_INSERTED
SPA-5-OIR_REMOVED

5 L2
5 L2
5 L2

SPA-5-OS_IMAGE_DOWNLOADING

5 L2

SPA-5-OS_IMAGE_ERROR

5 L2

SPA-5-OS_IMAGE_SIZE_ERR

5 L2

SPA-5-PLIM_EVENT_INIT_ERR
SPA-5-PLIM_KA_INIT_ERR

5 L2
5 L2

SPA-5-PLIM_RELOADING

5 L2

SPA-5-STATE_CHANGE

5 L2

SPA-6-CHAN_CONNECT

6 L2

SPA-6-CHAN_CONNECT

6 L2

SPA-6-COMMAND_TOO_LONG

6 L2

SPA-6-MSG_SEND_FAILED

6 L2

SPA-6-MSG_SEND_FAILED

6 L2

SPA-6-OPTICS_INSERTION

6 L2

SPA-6-OPTICS_INSERTION

6 L2

SPA-6-OPTICS_REMOVAL

6 L2

SPA-6-OPTICS_REMOVAL

6 L2

SPA-6-PLUGIN

6 L2

SPA-6-PLUGIN_EVENT

6 L2

SPA-6-PM_ERR

6 L2

SPA-6-PM_ERR

6 L2

SPABRG-3-HW_FAILURE

3 L2

SPABRG-3-HW_FAILURE1

3 L2

SPABRG-6-HW_INFO1

6 L2

SPABRG-6-HW_INFO2

6 L2

SPACHOP-3-VTWIN_TRACE1

3 L2

SPAJAV-3-BERT_HW_INTERVAL_SET

3 L2

SPAJAV-3-CABLELENGTH_SET_FAIL

3 L2

SPAJAV-3-CLEAR_MIB_FAIL

3 L2

SPAJAV-3-CLOCK_SET_FAIL

3 L2

SPAJAV-3-CONFIG_PORT_TYPE_FAIL

3 L2

SPAJAV-3-DATA_INVERT_FAIL

3 L2

SPAJAV-3-FAREND_ACTIVATION_BLOCKED

3 L2

SPAJAV-3-FAREND_ACTIVATION_FAILED

3 L2

SPAJAV-3-FAREND_DEACTIVATION_BLOCKED

3 L2

SPAJAV-3-FAREND_DEACTIVATION_FAILED

3 L2

SPAJAV-3-GET_JAV_PATTERN_FAIL

3 L2

SPAJAV-3-MTU_CONFIG_FAIL

3 L2

SPAJAV-3-RESYNC_FAIL

3 L2

SPAJAV-3-SET_BANDWIDTH_FAIL

3 L2

SPAJAV-3-SET_BERT_FAIL

3 L2

SPAJAV-3-SET_BIT_FAIL

3 L2

SPAJAV-3-SET_CRC_FAIL

3 L2

SPAJAV-3-SET_DSU_FAIL

3 L2

SPAJAV-3-SET_FRAMING_FAIL

3 L2

SPAJAV-3-SET_LOOPBACK_FAIL

3 L2

SPAJAV-3-SET_REMOTE_BANDWIDTH_FAIL

3 L2

SPAJAV-6-CLOCK_GET

6 L2

SPAJAV-6-CTRL_FUNC_GET_LOOP

6 L2

SPAJAV-6-HW_CONTEXT_DEBUG

6 L2

SPAJAV-6-REMOVE_CONFIGS

6 L2

SPAMAV-6-REMOVE_CONFIG

6 L2

SPAMSG-3-DEBUG_INIT_FAILED

3 L2

SPAMSG-3-DEBUG_INTERNAL_ERROR

3 L2

SPAMSG-3-DEBUG_REGISTER_FAILED
SPAMSG-3-ERR

3 L2
3 L2

SPAMSG-3-NULL_EVM
SPAMSG-6-INFO

3 L2
6 L2

SPAN-3-DST_REG_FAILED

3 L2

SPAN-3-IM_RECONNECT_FAILED

3 L2

SPAN-4-CHKPT_HW

4 L2

SPAN-4-CHKPT_HW_INVALID_DATA

4 L2

SPAN-4-CHKPT_SESSID

4 L2

SPAN-4-DB_DELETE_FAILED

4 L2

SPAN-4-DST_UPDATE_FAILED

4 L2

SPAN-4-EXIT_FAILED

4 L2

SPAN-4-IM_MSG_FAILED

4 L2

SPAN-4-INIT_FAILED

4 L2

SPAN-4-LOST_EVENT

4 L2

SPAN-4-PD_RESYNC_FAILED

4 L2

SPAN-4-STATS_CLEAR_FAILED

4 L2

SPAPRO-1-SPA_RESET

1 L2

SPIO-4-INV_PKT

4 L2

SPIO-4-NOT_SUPP

4 L2

SPU_LIB-3-MSG_SEND_FAILED

3 L2

SPU_LIB-6-INFO_WARNING

6 L2

SPU-3-COREDUMP_END_NOTIF

3 L2

SPU-3-COREDUMP_FP_NOTIF

3 L2

SPU-3-COREDUMP_START_NOTIF
SPU-3-FATAL_ERR

3 L2
3 L2

SPU-3-NONFATAL_ERR

3 L2

SPU-3-SER_NOTIF

3 L2

SPU-6-INFO_MSG

6 L2

SPU-6-MINOR_SBE_NOTIF

6 L2

SRP-3-DEBUG_TRACEBACK

3 L2

SRP-3-ERR_DUP_MAC_ADDR

3 L2

SRP-3-ERR_MEDIA_SINGLE_RING

3 L2

SRP-3-ERR_MEDIA_WRAP

3 L2

SRP-3-ERR_SRR_VER_MISMATCH

3 L2

SRP-3-MUTEX

3 L2

SRP-3-SW_INIT

3 L2

SRP-6-INFO_SINGLE_NODE_TOPO

6 L2

SSE_PFILTER_EA-3-ERR_APPLY_ACE_MOD

3 L2

SSE_PFILTER_EA-3-ERR_IM_CAPS

3 L2

SSE_PFILTER_EA-7-INIT

7 L2

SSE_TCAM_MGR-7-INIT

7 L2

SSE_UIDB-7-ERR_INIT

7 L2

SSRP-3-ERR_INIT

3 L2

SSRP-4-ERR_BACKEND

4 L2

SSRP-4-ERR_BAD_MAGIC

4 L2

SSRP-4-ERR_BAG

4 L2

SSRP-4-ERR_CREATE_CHANNELS

4 L2

SSRP-4-ERR_DEBUG

4 L2

SSRP-4-ERR_EVC_CLOSE

4 L2

SSRP-4-ERR_EVC_CREATE

4 L2

SSRP-4-ERR_EVC_ERROR

4 L2

SSRP-4-ERR_EVC_EVM_HANDLER

4 L2

SSRP-4-ERR_EVC_NOTIFY

4 L2

SSRP-4-ERR_EVC_OPEN

4 L2

SSRP-4-ERR_EVM_ATTACH

4 L2

SSRP-4-ERR_EVM_SEND

4 L2

SSRP-4-ERR_LOOPED

4 L2

SSRP-4-ERR_LTRACE

4 L2

SSRP-4-ERR_MEM_ALLOC

4 L2

SSRP-4-ERR_MGD_TIMER

4 L2

SSRP-4-ERR_REQUEST

4 L2

SSRP-4-ERR_SETSOCKOPT

4 L2

SSRP-4-ERR_SOCKET_QUEUE_FULL

4 L2

SSRP-4-ERR_STATE

4 L2

SSRP-4-ERR_SYSDB

4 L2

SSRP-6-ERR_EVC_DESTROY

6 L2

SSRP-6-SECOND_CONNECTION

6 L2

STP_IO-3-ATTACH_FAILED

3 L2

STP_IO-3-BPDU_DROPPED

3 L2

STP_IO-3-BPDU_INCORRECT_DIRECTION

3 L2

STP_IO-3-BPDU_INCORRECT_DMAC

3 L2

STP_IO-3-BPDU_INCORRECT_SAP

3 L2

STP_IO-3-BPDU_UNREADABLE

3 L2

STP_IO-3-INVALID_BPDU

3 L2

STP_IO-3-TIMER_FAILED

3 L2

STP_IO-4-CFG_FAILED

4 L2

STP_IO-4-ERR_PACKET_INVALID_MSTI

4 L2

STP_IO-4-ERROR_DISABLING_PORT

4 L2

STP_IO-4-INITIALISATION_FAILURE

4 L2

STP_IO-4-ISSU_START_FAILED

4 L2

STP_IO-4-OOM

4 L2

STP_IO-4-PROBLEM_EXITING

4 L2

STP_IO-4-PROVIDER_BRIDGE_MISMATCH

4 L2

STP_IO-4-RECONNECT_FAILED

4 L2

STP_IO-4-STANDBY_SYNC_FAILED

4 L2

STP_IO-4-UNEXPECTED_BPDU_RECEIVED

4 L2

STP_IO-4-UNEXPECTED_SYSDB_MESSAGE

4 L2

STP_LIB-3-PROTECT_STATE

3 L2

STP-3-ISSU_NOTIFICATION_NOT_SENT

3 L2

STP-3-PORT_STATE_UPDATES_BLOCKED

3 L2

STP-4-ERR_CHKPT_SAVE

4 L2

STP-4-ERR_DB_BATCH_END

4 L2

STP-4-ERR_PORT_ID_RECLAIM

4 L2

STP-4-INITIALISATION_FAILURE

4 L2

STP-4-INVALID_L2VPN_STATE

4 L2

STP-4-ISSU_START_FAILED

4 L2

STP-4-LOOP_INCONSISTENT

4 L2

STP-4-PORTFAST_CHANGES_PENDING

4 L2

STP-4-PROBLEM_EXITING

4 L2

STP-4-RECONNECT_FAILED

4 L2

STP-4-TIMER_FAILED

4 L2

STP-6-LOOP_CONSISTENT

6 L2

STP-6-PORT_LOOPBACK

6 L2

STREE-4-CONNECT_FAIL

4 L2

STREE-4-CREATE_FAIL

4 L2

STREE-4-MSGSEND_FAIL

4 L2

STREE-4-PORT_CREATE_FAIL

4 L2

STREE-4-SET_MACADDR_FAIL

4 L2

STREE-4-START_FAIL

4 L2

T1E1_LNM-2-REMFAILEDPUBLISH

2 L2

T1E1_LNM-3-GENEVENT

3 L2

T1E1_LNM-3-MAJWARNNOISE

3 L2

T1E1_LNM-3-MINWARNNOISE

3 L2

T1E1_LNM-3-REMWARNNOISE

3 L2

T1E1_LNM-5-DISABLED

5 L2

T1E1_LNM-5-ENABLED

5 L2

T1E1-2-NOMEM

2 L2

T1E1-3-ERROR

3 L2

T1E1-4-ALARM

4 L2

T1E1-4-LOOPSTATUS

4 L2

T1E1-4-UPDOWN

4 L2

T1E1-4-WARNING

4 L2

T3E3-2-NOMEM

2 L2

T3E3-3-ERROR

3 L2

T3E3-4-ALARM
T3E3-4-FEAC

4 L2
4 L2

T3E3-4-LOOPSTATUS

4 L2

T3E3-4-PM

4 L2

T3E3-4-UPDOWN

4 L2

T3E3-4-WARNING

4 L2

TCAM_RM_CARVE_VERIFY-3-FATAL_ERR

3 L2

TCAM_RM_CARVE_VERIFY-6-INFO_MSG

6 L2

TCAM_RM-3-BLWM_CLIENT_CONF_FAILED

3 L2

TCAM_RM-3-BLWM_CLIENT_REBIND_FAILED

3 L2

TCAM_RM-3-BLWM_FAILED_MSG_DUMP

3 L2

TCAM_RM-3BLWM_FAILED_MSG_MASK_DUMP

3 L2

TCAM_RM-3BLWM_FAILED_MSG_RESULT_DUMP

3 L2

TCAM_RM-3BLWM_FAILED_MSG_VALUE_DUMP

3 L2

TCAM_RM-3-BLWM_MSG_SEND_FAILED

3 L2

TCAM_RM-3-BLWM_RECVD_REPLY_FAIL

3 L2

TCAM_RM-3-FATAL_ERR

3 L2

TCAM_RM-3-MSG_SEND_FAILED

3 L2

TCAM_RM-3-NONFATAL_ERR

3 L2

TCAM_RM-3-RETURN_ERROR

3 L2

TCAM_RM-3TCAM_RM_RECVD_REPLY_NOMEM

3 L2

TCAM_RM-4-BLWM_REPLAY_REQUEST

4 L2

TCAM_RM-4-CACHE_ERR_COUNT

4 L2

TCAM_RM-4CACHE_UNSUPPORTED_OP_SEQUENCE

4 L2

TCAM_RM-4-REPLY_HDLR_ERR_COUNT

4 L2

TCAM_RM-5-PARITY_ERR

5 L2

TCAM_RM-6-INFO_MSG

6 L2

UDLD-2-DISABLE_PORT

2 L2

UDLD-3-DAEMON_INIT_FAILED

3 L2

UDLD-3-ERROR_LINK_NOT_DISABLED

3 L2

UDLD-3-OUT_OF_MEMORY

3 L2

UDLD-4-EXITING

4 L2

UDLD-4-MUTEX_LOCK_FAIL

4 L2

UDLD-4-MUTEX_UNLOCK_FAIL

4 L2

UDLD-5-NEIGHBOR_MISMATCH

5 L2

UDLD-5-NEIGHBOR_TIMEOUT

5 L2

UDLD-5-TX_RX_LOOPBACK

5 L2

UDLD-5-UNIDIRECTIONAL_LINK

5 L2

UDLD-6-NO_NEIGHBORS

6 L2

UDLD-6-PEERING

6 L2

UIDB_RM-3-GET_SPA_TYPE

3 L2

UIDB_RM-3-INIT_ERR

3 L2

UIDB_RM-3-MALLOC

3 L2

UIDB_RM-3-WAVL_INIT

3 L2

UIDB_RM-3-WAVL_INS

3 L2

VCM_EA-2-DEBUG_INIT

2 L2

VCM_EA-2-INTERNAL_ERR

2 L2

VCM-2-IM_ATTR_ERR

2 L2

VCM-2-IM_PROC_DOWN

2 L2

VCM-2-IM_PVC_FAILED

2 L2

VCM-2-IM_RETRY_CONN

2 L2

VIF_MA_DEBUG-3-DEBUG_INIT_ERR

3 L2

VIF_MA_DEBUG-3-LTRACE_INIT_ERR

3 L2

VIF_MA_MSG-4-CREATE_FAIL

4 L2

VIF_MA_MSG-4-REPL_FAIL

4 L2

VIRTIO-4-CTX_SHORTAGE

4 L2

VIRTIO-4-INIT_FAILED

4 L2

vlan_netio-4-DEBUG_INIT_ERROR

4 L2

vlea-3-NATIVE_VLAN_NOTIF

3 L2

vlea-3-NO_STATS

3 L2

vlea-4-EVENT_BLOCK

4 L2

vlea-4-IM_RESYNC_FAILURE

4 L2

vlea-4-INIT_FAILED

4 L2

vlea-6-NO_MEM

6 L2

vlma-3-IM_CONNECT_FAILED

3 L2

vlma-3-L2VPN_DISCONNECT_FAILED

3 L2

vlma-4-ASYNC_HANDLER

4 L2

vlma-4-EVENT_BLOCK

4 L2

vlma-4-INIT_FAILED

4 L2

vlma-4-RECOVERY_FAILED_BATCH

4 L2

vlma-4-RECOVERY_FAILED_SINGLE

4 L2

vlma-6-NO_MEM

6 L2

vlma-6-UNKNOWN_NODE_VLAN_LIMIT

6 L2

VPA_1P_OC192-3-DRV_INIT_ERR

3 L2

VPA_1P_OC192-3-GENERIC_ERROR

3 L2

VPA_1P_OC192-3-GET_NODEID_ERR

3 L2

VPA_1P_OC192-3-MEM_ERR

3 L2

VPA_1P_OC192-6-OPTICS_INSERTION

6 L2

VPA_1P_OC192-6-OPTICS_REMOVAL

6 L2

VPA_1P_OC192-6-PORT_DEL_INFO

6 L2

VPA_1P_OC192-7-DEBUG

7 L2

VPA_1P_OC192-7-ERR
VPA_1P_OC192-7-INFO

7 L2
7 L2

VPA_8P_GE-1-LTRACE_INIT_ERR

1 L2

VPA_8P_GE-2-LTRACE_RETRY_ERR

2 L2

VPA_8P_GE-2-SPA_CTX_ERR

2 L2

VPA_8P_GE-2-SPA_JKT_ERR

2 L2

VPA_8P_GE-2-SPA_MAC_ERR

2 L2

VPA_8P_GE-3-PORT_DEL_TIMEOUT

3 L2

VPA_8P_GE-4-INVALID_MAC

4 L2

VPA_8P_GE-6-PORT_DEL_INFO

6 L2

VPA_RULES-4-DEBUG_INIT_ERR

4 L2

VPLS-3-VPLS_ID_CONFLICT

3 L2

VTIO-4-CTX_SHORTAGE

4 L2

VTIO-4-INIT_FAILED

4 L2

VTIO-4-PORT_CREATE_FAILED

4 L2

VTIO-4-PULSE_FAILED

4 L2

VTIO-4-WRITE_FAILED

4 L2

VTIO-6-NO_PORTS

6 L2

WAHOO-3-ERR_ACCESS

3 L2

WAHOO-3-RX_QUIESCE

3 L2

WAHOO-3-TX_QUIESCE

3 L2

WAHOO-4-INTERRUPT_WARNING

4 L2

WAHOO-4-THREAD_INFO_MSG

4 L2

WAHOO-5-MCAST_DISABLE_INFO_MSG

5 L2

WAHOO-6-INFO_MSG

6 L2

WAHOO-6-INFO_MSG_SBE

6 L2

WAHOO-6-INTERRUPT_INFO

6 L2

WAHOO-6-STATS_INFO_MSG

6 L2

WAHOO-7-ERR_PIPE_STUCK

7 L2

WAHOO-7-PAIR_PCR_REG

7 L2

WAHOO-7-PAIR_REG

7 L2

WAHOO-7-PAIR_REG_LIST

7 L2

WAHOO-7-PHB_DUMP

7 L2

WAHOO-7-REG_DUMP

7 L2

WAN_INARP-2-INIT

2 L2

WAN_INARP-3-CONFIG

3 L2

WAN_INARP-3-NOMEM

3 L2

WAN_INARP-3-UNKNOWN_EVENT

3 L2

WAN_INARP-3-UNKNOWN_FSMSTATE

3 L2

WAN_INARP-3-UNKNOWN_IDB

3 L2

WAN_INARP-3-UNKNOWN_IDBTYPE

3 L2

WAN_INARP-3-UNKNOWN_IFSTATE

3 L2

WAN_INARP-3-VCCLASS_IDB

3 L2

WAN_INARP-4-UNKNOWN_INTF

4 L2

WAN_LIB_IFDB-3-NOMEM

3 L2

WAN_LIB_IFDB-3-UNKNOWN_IDBTYPE

3 L2

WAN_LIB_VCC-3-NOMEM

3 L2

WAN_LIB_VCC-3-UNKNOWN_IDBTYPE

3 L2

WANPHY-4-ALARM

4 L2

IPHC_MA-2-CLIENT_INIT

2 L3

IPHC_MA-3-MEM_ALLOC

3 L3

IPHC_MA-4-EVC_INIT

4 L3

IPHC_MA-6-INFO

6 L3

IPHC_PROFILE-2-MODULE_INIT

2 L3

IPHC_PROFILE-3-MEM_ALLOC

3 L3

IPV6_ND_LITE-3-ASYNC_PULSE_SEND_FAIL

3 L3

IPV6_ND_LITE-3-CONNECT_CHANNEL_FAIL

3 L3

IPV6_ND_LITE-3-SELF_GENERATE_FAIL

3 L3

IPV6_ND_LITE-3-SHMEM_GIP_UNAVAILABLE

3 L3

IPV6_ND_LITE-3-SHMEM_MMAP_FAIL

3 L3

IPV6_ND_LITE-3-SHMEM_MUNMAP_FAIL

3 L3

IPV6_ND_LITE-3-SHMEM_OPEN_FAIL

3 L3

IPV6_ND_LITE-3-SHMEM_TRNC_FAIL

3 L3

IPV6_ND_LITE-3-SHMEM_UNAVAILABLE

3 L3

IPV6_ND_LITE-3-SHMEM_UNLINK_FAIL

3 L3

RT_PROXY-3-ERR

3 L3

RT_PROXY-3-INIT

3 L3

RT_PROXY-3-SHM

3 L3

VMANCLNT-3-VMAN_ERROR

3 LIB

VMANCLNT-5-VMAN_NOTICE

5 LIB

VMANCLNT-6-VMAN_INFO

6 LIB

VMANCLNT-7-VMAN_DEBUG

7 LIB

REPLICATOR-3-BAD_HANDLENAME

3 LIBRARY

REPLICATOR-3-IDT_FAIL

3 LIBRARY

REPLICATOR-3-LARGE_HANDLE

3 LIBRARY

REPLICATOR-3-WRITE_OWNERSHIP_FAIL

3 LIBRARY

REPLICATOR-7-BAD_MAGIC

7 LIBRARY

REPLICATOR-7-CTX_NOT_FOUND

7 LIBRARY

REPLICATOR-7-INTERNAL

7 LIBRARY

REPLICATOR-7-LOCKING

7 LIBRARY

REPLICATOR-7-MEMORY

7 LIBRARY

REPLICATOR-7-NO_CB

7 LIBRARY

REPLICATOR-7-SEND_FAILED

7 LIBRARY

REPLICATOR-7-UPDATE_FAILED

7 LIBRARY

REPLICATOR-7-WRITE_OWNERSHIP

7 LIBRARY

ASR9K_LICENSE-2-ADV_IP_NEEDED

2 LICENSE

ASR9K_LICENSE-2-INFRA_VRF_NEEDED

2 LICENSE

ASR9K_LICENSE-2-OPTICS_NEEDED

2 LICENSE

ASR9K_LICENSE-2-VIDMON_NEEDED

2 LICENSE

ASR9K_LICENSE-3-OPERATION_FAIL

3 LICENSE

GSR_LCLM_SHOW-3-ERROR

3 LICENSE

LCLICMGR-2-ACQ

2 LICENSE

LCLICMGR-2-DEF_FAIL

2 LICENSE

LCLICMGR-2-FEW_LICENSES

2 LICENSE

LCLICMGR-2-HANDLE_EXISTS

2 LICENSE

LCLICMGR-2-NO_FEATURE

2 LICENSE

LCLICMGR-3-ERROR

3 LICENSE

LCLICMGR-3-RATE_MODE_SECURITY_AUTH

3 LICENSE

LCLICMGR-3-RATE_MODE_SECURITY_FAIL

3 LICENSE

LCLICMGR-5-NO_LICENSE

5 LICENSE

LCLICMGR-5-RATE_CHANGE

5 LICENSE

LICCMD-4-LACK_OF_ARG

4 LICENSE

LICCMD-4-TRACE_INIT_FAILED

4 LICENSE

LICLIB-4-DB_DIR_ERROR

4 LICENSE

LICLIB-4-NO_APP_MEDIA

4 LICENSE

LICLIB-4-TRACE_INIT_FAILED

4 LICENSE

LICLIB-6-DB_DIR_CREATE

6 LICENSE

LICMGR-3-CHASSIS_MISMATCH

3 LICENSE

LICMGR-3-DB_CORRUPT

3 LICENSE

LICMGR-3-DB_SAVE_ERROR

3 LICENSE

LICMGR-3-EXIT_ERROR

3 LICENSE

LICMGR-3-INIT

3 LICENSE

LICMGR-3-NO_SERIAL_NUM

3 LICENSE

LICMGR-4-ALARM

4 LICENSE

LICMGR-4-AUDIT_PROBLEM

4 LICENSE

LICMGR-4-DATASTORE_PROBLEM

4 LICENSE

LICMGR-4-EVENT_FAIL

4 LICENSE

LICMGR-4-IMPLICIT_EXPIRED

4 LICENSE

LICMGR-4-IMPLICIT_LICENSE_USED

4 LICENSE

LICMGR-4-IMPLICIT_WILL_EXPIRE

4 LICENSE

LICMGR-4-LICENSE_EXPIRED

4 LICENSE

LICMGR-4-LICENSE_FILE_PROBLEM

4 LICENSE

LICMGR-4-LICENSE_POOL_REMOVED

4 LICENSE

LICMGR-4-LICENSE_RMA_EXPIRED

4 LICENSE

LICMGR-4-LICENSE_RMA_WILL_EXPIRE

4 LICENSE

LICMGR-4-LICENSE_WILL_EXPIRE

4 LICENSE

LICMGR-4-NO_OPERATION_ID

4 LICENSE

LICMGR-4-PACKAGE_LICENSE_INVALID

4 LICENSE

LICMGR-4PACKAGE_LOCATION_LICENSE_INVALID

4 LICENSE

LICMGR-4-SYSDB

4 LICENSE

LICMGR-4-SYSDBREG

4 LICENSE

LICMGR-6-LICENSE_CLEAR_FEATURE

6 LICENSE

LICMGR-6-LICENSE_CLEAR_NO_FEATURE

6 LICENSE

LICMGR-6-LICENSE_CLEAR_NO_POOL

6 LICENSE

LICMGR-6-LICENSE_CLEAR_POOL

6 LICENSE

LICMGR-6-LOAD_LICENSE_FILE

6 LICENSE

LICMGR-6-LOAD_LICENSE_FILE_OK

6 LICENSE

LICMGR-6-READ_LICENSE_FILE

6 LICENSE

LICMGR-7-CLIENT_NORESPONSE

7 LICENSE

LICMGR-7-LICENSE_RECLAIMED

7 LICENSE

c12000_bflash_prp_driver-3-INIT_ERROR

3 MEDIA

DISKUTIL-3-INIT_ERROR

3 MEDIA

DISKUTIL-4-INIT_WARNING

4 MEDIA

FLASHFS_HES-1-BADDEVOPEN

1 MEDIA

FLASHFS_HES-1-BADOPTIONS

1 MEDIA

FLASHFS_HES-1-BADPATH

1 MEDIA

FLASHFS_HES-1-BADPERM

1 MEDIA

FLASHFS_HES-1-CARD_UNAVAILABLE

1 MEDIA

FLASHFS_HES-1-COND_PROBLEM

1 MEDIA

FLASHFS_HES-1-DRIVER_UNAVAILABLE

1 MEDIA

FLASHFS_HES-1-INIT_FAILED

1 MEDIA

FLASHFS_HES-1-MUTEX_PROBLEM

1 MEDIA

FLASHFS_HES-3-BAD_DEVICE_DATA

3 MEDIA

FLASHFS_HES-3BAD_DRIVER_WAIT_THREAD

3 MEDIA

FLASHFS_HES-3-BAD_PULSE_ATTACH

3 MEDIA

FLASHFS_HES-3-BAD_THREAD_CREATE

3 MEDIA

FLASHFS_HES-3-BADCARD

3 MEDIA

FLASHFS_HES-3-BADCHANNEL

3 MEDIA

FLASHFS_HES-3-BADDLLOPEN

3 MEDIA

FLASHFS_HES-3-BADDLSYM

3 MEDIA

FLASHFS_HES-3-BADHDR

3 MEDIA

FLASHFS_HES-3-BADSTATUS

3 MEDIA

FLASHFS_HES-3-BOOTFLASH_CORRUPTED

3 MEDIA

FLASHFS_HES-3-CONNECT_FAILED

3 MEDIA

FLASHFS_HES-3-DEBUG_INIT_FAILED

3 MEDIA

FLASHFS_HES-3-DRIVER_CHANGED

3 MEDIA

FLASHFS_HES-3-EVENT_BLOCK_ERROR

3 MEDIA

FLASHFS_HES-3EVENT_MGR_CREATE_FAILED

3 MEDIA

FLASHFS_HES-3-FAIL_DEBUG_REG

3 MEDIA

FLASHFS_HES-3RECOVERY_FROM_SQUEEZE_FAILED

3 MEDIA

FLASHFS_HES-3-SYMLINK_EXPORT

3 MEDIA

FLASHFS_HES-3SYSMGR_PROC_READY_FAILED

3 MEDIA

FLASHFS_HES-4BAD_DRIVER_PULSE_REGISTRATION
FLASHFS_HES-4-BAD_SECTOR_ERASE

4 MEDIA
4 MEDIA

FLASHFS_HES-4-CARD_WRITE_PROTECTED

4 MEDIA

FLASHFS_HES-4EXCLUSIVE_ACCESS_DENIED

4 MEDIA

FLASHFS_HES-4-UNKNOWN_PULSE

4 MEDIA

FLASHFS_HES-5-CARD_SWAPPED

5 MEDIA

FLASHFS_HES-6-DRIVER_BACK_UP

6 MEDIA

FLASHFS_HES-6RECOVERING_FROM_SQUEEZE

6 MEDIA

FLASHFS_HES-6RECOVERING_FROM_SQUEEZE_DONE

6 MEDIA

FLASHFS_HES-6-USAGE

6 MEDIA

FSDEVINFO-3-DBG_CLEANUP

3 MEDIA

FSDEVINFO-3-EVM_ERROR

3 MEDIA

FSDEVINFO-3-LWM_ERROR

3 MEDIA

FSDEVINFO-3-MAIN_INIT_ERROR

3 MEDIA

FSDEVINFO-3-NO_MEMORY

3 MEDIA

FSDEVINFO-3-REGISTER_ERROR

3 MEDIA

FSDEVINFO-3-SIGNAL_RELATED

3 MEDIA

FSDEVINFO-3-SYSMGR_READY

3 MEDIA

FSDEVINFO-3-THREAD_ERROR

3 MEDIA

FSDEVINFO-4-INVALID_PARM

4 MEDIA

GETMEDIA-4-INVALID_PARM

4 MEDIA

GETMEDIA-6-DEVFILE_READ_FAILED

6 MEDIA

HARDDISK-7-UNKNOWN_MACHINE

7 MEDIA

HARDDISK-7-UNSUPPORTED_BOARD

7 MEDIA

MB_FLASH_LIB-1-BADCHANNEL

1 MEDIA

MB_FLASH_LIB-1-BADPATH

1 MEDIA

MB_FLASH_LIB-7-VERIFYINFO

7 MEDIA

mbus_flash_driver-3-INIT_ERROR

3 MEDIA

MEDIAAPI-3-CORRUPT_FILE

3 MEDIA

MEDIAAPI-3-INVALID_PARM_DEVICE_INSERT

3 MEDIA

MEDIAAPI-3-INVALID_PARM_DRIVER_START

3 MEDIA

MEDIAAPI-3-INVALID_PARM_REDFS_ENABLE

3 MEDIA

MEDIAAPI-4-CHAN_CONNECT_FAILED

4 MEDIA

MEDIAAPI-4-INVALID_FSTYPE

4 MEDIA

MEDIAAPI-4INVALID_PARM_DEVICE_REMOVAL

4 MEDIA

MEDIAAPI-4-INVALID_PARM_DRIVER_EXIT

4 MEDIA

MEDIAAPI-4-INVALID_PARM_FORMAT_PART

4 MEDIA

MEDIAAPI-4-INVALID_PARM_REDFS_DISABLE

4 MEDIA

MEDIAAPI-4-INVALID_PARM_REDFS_ERROR

4 MEDIA

MEDIAAPI-4-INVALID_PARM_REDFS_PART

4 MEDIA

MEDIAAPI-4-INVALID_PARM_REDFS_QUERY

4 MEDIA

MEDIAAPI-4-INVALID_PARM_REPORT_ERROR

4 MEDIA

MEDIAAPI-4-MSG_SEND_FAILED

4 MEDIA

MEDIASVR_HELPER-4-INIT_ERROR

4 MEDIA

MEDIASVR_HELPER-4-SYSDB_ERROR

4 MEDIA

MEDIASVR-2-NODE_RELOADING

2 MEDIA

MEDIASVR-3-CORRUPT_FILE

3 MEDIA

MEDIASVR-3-INIT_SVR_ERROR

3 MEDIA

MEDIASVR-4-DEVICE_CORRUPT

4 MEDIA

MEDIASVR-4-DEVICE_EXIT_FAILED

4 MEDIA

MEDIASVR-4-DEVICE_FORMAT_FAILED

4 MEDIA

MEDIASVR-4-DEVICE_MOUNT_FAILED

4 MEDIA

MEDIASVR-4-FSTYPE_MISMATCH

4 MEDIA

MEDIASVR-4-INIT_BOOT_DEV_ERROR

4 MEDIA

MEDIASVR-4-INIT_LTRACE_ERROR

4 MEDIA

MEDIASVR-4-INIT_MEDIA_DEV_ERROR

4 MEDIA

MEDIASVR-4-NVRAM_WRITE

4 MEDIA

MEDIASVR-5-DEVICE_FORMATTED

5 MEDIA

MEDIASVR-5-DEVICE_INCONSISTENT

5 MEDIA

MEDIASVR-5-DEVICE_REPAIRED

5 MEDIA

MEDIASVR-5-DEVICE_UNFORMATTED

5 MEDIA

MEDIASVR-5-PARTITION_REASON

5 MEDIA

MEDIASVR-6BOOT_DEVICE_FORMAT_REQUESTED

6 MEDIA

MEDIASVR-6-DEVICE_FORMAT_COMPLETED

6 MEDIA

MEDIASVR-6-DEVICE_FORMAT_REQUESTED

6 MEDIA

MEDIASVR-6-DEVICE_PARTITION_NOT_EXIST

6 MEDIA

MEDIASVR-6-NVRAM_READ_FSTYPE

6 MEDIA

MEDIASVR-6-NVRAM_UNKNOWN_FSTYPE

6 MEDIA

NVRAM_PLATFORM_COMMON-3BAD_CHECKSUM

3 MEDIA

NVRAM_PLATFORM_COMMON-3BAD_CLASSIC_CONFIG

3 MEDIA

NVRAM_PLATFORM_COMMON-3BAD_CLASSIC_CONFIG_COMPRESS

3 MEDIA

NVRAM_PLATFORM_COMMON-3BAD_CLASSIC_CONFIG_MEM

3 MEDIA

NVRAM_PLATFORM_COMMON-3LOGGING_ERROR

3 MEDIA

NVRAM_PLATFORM_COMMON-4MOVE_FAILURE

4 MEDIA

NVRAM_PLATFORM_COMMON-4WRITE_ABORT

4 MEDIA

NVRAM_PLATFORM_COMMON-6MOVE_DONE

6 MEDIA

NVRAM_PLATFORM-2-NVRAM_SIZE_ZERO

2 MEDIA

NVRAM_PLATFORM-2-NVRAM_SIZE_ZERO

2 MEDIA

NVRAM_PLATFORM-2-NVRAM_SIZE_ZERO

2 MEDIA

NVRAM_PLATFORM-3-BAD_NVRAM_MAP

3 MEDIA

NVRAM_PLATFORM-3-BAD_NVRAM_MAP

3 MEDIA

NVRAM_PLATFORM-3-BAD_NVRAM_MAP

3 MEDIA

NVRAM_PLATFORM-3-BAD_NVRAM_MAP

3 MEDIA

NVRAM_PLATFORM-3-BAD_NVRAM_VAR

3 MEDIA

NVRAM_PLATFORM-3-BATTERY_LOW

3 MEDIA

NVRAM_PLATFORM-3-BATTERY_LOW

3 MEDIA

NVRAM_PLATFORM-3-BATTERY_LOW

3 MEDIA

NVRAM_PLATFORM-3-ERROR_REG_PM

3 MEDIA

NVRAM_PLATFORM-3-ERROR_REG_PM

3 MEDIA

NVRAM_PLATFORM-3-ERROR_RUN_BMON

3 MEDIA

NVRAM_PLATFORM-3-ERROR_RUN_BMON

3 MEDIA

NVRAM_PLATFORM-3-NO_SPACE

3 MEDIA

NVRAM_PLATFORM-3NVRAM_RAW_NOT_SUPPORTED

3 MEDIA

NVRAM_PLATFORM-3-NVRAM_SIZE_ZERO

3 MEDIA

NVRAM_PLATFORM-4-BAD_NVRAM_BYTES

4 MEDIA

NVRAM_PLATFORM-4-BAD_NVRAM_MAP

4 MEDIA

NVRAM_PLATFORM-4-BAD_NVRAM_MAP

4 MEDIA

NVRAM_PLATFORM-4-BAD_NVRAM_MAP

4 MEDIA

NVRAM_PLATFORM-4-ERROR_RUN_BMON

4 MEDIA

NVRAM_PLATFORM-7-BAD_NVRAM_VAR

7 MEDIA

NVRAM_PLATFORM-7-BAD_NVRAM_VAR

7 MEDIA

NVRAM_PLATFORM-7-BAD_NVRAM_VAR

7 MEDIA

NVRAM_PLATFORM-7-BAD_NVRAM_VAR

7 MEDIA

NVRAM_PLATFORM-7-BAD_NVRAM_VAR

7 MEDIA

NVRAM_PLATFORM-7-BAD_NVRAM_VAR

7 MEDIA

NVRAM_PLATFORM-7-ERROR_BOARD_READ

7 MEDIA

NVRAM_PLATFORM-7-ERROR_BOARD_READ

7 MEDIA

NVRAM_PLATFORM-7-ERROR_REG_PM

7 MEDIA

NVRAM_PLATFORM-7-ERROR_REG_PM

7 MEDIA

NVRAM_PLATFORM-7-ERROR_REG_PM

7 MEDIA

NVRAM_PLATFORM-7-NVRAM_SIZE_ZERO

7 MEDIA

NVRAM_PLATFORM-7-NVRAM_SIZE_ZERO

7 MEDIA

NVRAM_SIM-3-BATTERY_LOW

3 MEDIA

NVRAM_SIM-3-BATTERY_LOW

3 MEDIA

NVRAM_SIM-4-BAD_NVRAM_MAP

4 MEDIA

NVRAM_SIM-4-BAD_NVRAM_MAP

4 MEDIA

NVRAM_SIM-7-BAD_NVRAM_VAR

7 MEDIA

NVRAM_SIM-7-BAD_NVRAM_VAR

7 MEDIA

NVRAM_SIM-7-ERROR_REG_PM

7 MEDIA

NVRAM_SIM-7-ERROR_REG_PM

7 MEDIA

NVRAM_SIM-7-ERROR_RUN_BMON

7 MEDIA

NVRAM_SIM-7-ERROR_RUN_BMON

7 MEDIA

NVRAM_SIM-7-NVRAM_SIZE_ZERO

7 MEDIA

NVRAM_SIM-7-NVRAM_SIZE_ZERO

7 MEDIA

NVRAM_UTIL-3-DEBUG_INIT_FAILED

3 MEDIA

NVRAM_UTIL-3-FAIL_DEBUG_REG

3 MEDIA

NVRAM-3-ATTR_NVRAM_LOW_MEM

3 MEDIA

NVRAM-3-ATTR_ROMMON_LOW_MEM

3 MEDIA

NVRAM-3-BADDLLOPEN

3 MEDIA

NVRAM-3-BADDLSYM

3 MEDIA

NVRAM-3-BADFUNCTIONS

3 MEDIA

NVRAM-3-CORRUPT

3 MEDIA

NVRAM-3-ERASE_CONFIG_LOW_MEM

3 MEDIA

NVRAM-3-EVENT_BLOCK_ERROR

3 MEDIA

NVRAM-3-FORMAT_NVRAM_LOW_MEM

3 MEDIA

NVRAM-3-FORMATERROR

3 MEDIA

NVRAM-3-INIT_FAIL

3 MEDIA

NVRAM-3-IO_MNT_LOW_MEM

3 MEDIA

NVRAM-3-IO_MNT_ROMMON_LOW_MEM

3 MEDIA

NVRAM-3-LOOKUP_CACHE_LOW_MEM

3 MEDIA

NVRAM-3-NOSPACE

3 MEDIA

NVRAM-3-RAW_PART_ATTR_LOW_MEM

3 MEDIA

NVRAM-3-RAW_PART_IO_MNT_LOW_MEM

3 MEDIA

NVRAM-3-RECOVER_FAILED
NVRAM-3-RECOVERED

3 MEDIA
3 MEDIA

NVRAM-3-SANITIZE_INIT_FAIL

3 MEDIA

NVRAM-3-SHMEM_INIT_FAIL

3 MEDIA

NVRAM-3-UNMOUNT_FAILED

3 MEDIA

NVRAM-3-VALIDATE_BLOCKS_LOW_MEM

3 MEDIA

NVRAM-3-VALIDATE_FILE_FAIL_LOW_MEM

3 MEDIA

NVRAM-3-VALIDATE_FILE_LOW_MEM

3 MEDIA

NVRAM-4-BADFILES

4 MEDIA

NVRAM-4-MOVE_FAILURE

4 MEDIA

NVRAM-4-PD_COMPONENT_ERROR

4 MEDIA

NVRAM-6-DUMP_PATH

6 MEDIA

NVRAM-6-OPENERROR

6 MEDIA

NVRAM-6-UNMOUNT

6 MEDIA

NVRAM-6-UPGRADING

6 MEDIA

NVRAM-7-BADPATH

7 MEDIA

NVRAM-7-BADRAWINIT

7 MEDIA

NVRAM-7-EVENT_MGR_CREATE_FAILED

7 MEDIA

NVRAW_LIB-3-FILE_OPEN_FAILED

3 MEDIA

NVRAW_LIB-3-SEEK_TLV_OFF_FAILED

3 MEDIA

NVRAW_LIB-3-WRITE_FAILED

3 MEDIA

NVRAW_LIB-3-WRITE_TLV_OFF_FAILED

3 MEDIA

NVRAW_LIB-4-FAIL_ERASE_RBT_HIST

4 MEDIA

NVRAW_LIB-4-MUTEX_FAIL

4 MEDIA

NVRAW_LIB-4-REBOOT_HIST

4 MEDIA

NVRAW_LIB-4-REBOOT_INFO

4 MEDIA

REDFSAPI-4-INVALID_PARM_BOOT_PRI

4 MEDIA

REDFSAPI-4-INVALID_PARM_CFG_VERIFY

4 MEDIA

REDFSAPI-4-INVALID_PARM_LCL_PRI

4 MEDIA

REDFSAPI-4-INVALID_PARM_LCL_SEC

4 MEDIA

REDFSAPI-4-INVALID_PARM_MEDIA_ERR

4 MEDIA

REDFSAPI-4-INVALID_PARM_MIRROR_EN

4 MEDIA

REDFSAPI-4-INVALID_PARM_PART_AVAIL

4 MEDIA

REDFSAPI-4-INVALID_PARM_PART_DOWN

4 MEDIA

REDFSAPI-4-INVALID_PARM_PART_REM

4 MEDIA

REDFSAPI-4-LCL_CHAN_CONNECT_FAILED

4 MEDIA

REDFSAPI-4-MSG_SEND_FAILED

4 MEDIA

REDFSAPI-4-RMT_CHAN_CONNECT_FAILED

4 MEDIA

SYNCFS2-3-FAILURE

3 MEDIA

SYNCFS2-3-INIT_FAILED

3 MEDIA

SYNCFS2-3-REGISTER_NTFN

3 MEDIA

SYNCFS2-3-STBY_SYMLINK

3 MEDIA

SYNCFS2-3-STBY_SYMLINK_NOTYET

3 MEDIA

SYNCFS2-7-CLIENT_ERR

7 MEDIA

SYNCFS2-7-LOST_SYNC

7 MEDIA

SYNCFS2-7-LRD_AVAILABLE

7 MEDIA

SYNCFS2-7-LRD_NOTAVAILABLE

7 MEDIA

SYNCFS2-7-LRD_PARTNER_AVAILABLE

7 MEDIA

SYNCFS2-7-MUTEX_LOCK

7 MEDIA

SYNCFS2-7-MUTEX_TEST_LOCK

7 MEDIA

SYNCFS2-7-MUTEX_UNLOCK

7 MEDIA

SYNCFS2-7-REPLICATE_FAIL

7 MEDIA

SYNCFS2LIB-6-LOST_SYNC
SYNCFS2LIB-7-MUTEX_LOCK

6 MEDIA
7 MEDIA

SYNCFS2LIB-7-MUTEX_TEST_LOCK
SYNCFS2LIB-7-MUTEX_UNLOCK

7 MEDIA
7 MEDIA

adminexec-3-ACCT_ERR

3 MGBL

adminexec-3-AUTHORIZATION_ERR

3 MGBL

adminexec-3-EVENT_ATTACH

3 MGBL

adminexec-3-EVENT_BLOCK

3 MGBL

adminexec-3-EVENT_MANAGER_CREATE

3 MGBL

adminexec-3EVENT_MANAGER_DESTORY_FAILED

3 MGBL

adminexec-3-GETLINE_DATA

3 MGBL

adminexec-3-GETLINE_INIT

3 MGBL

adminexec-3-LTRACE_INIT

3 MGBL

adminexec-3-LWM

3 MGBL

adminexec-3-PTHREAD_CREATE

3 MGBL

adminexec-3-SYSDB_BIND_FAILED

3 MGBL

adminexec-3SYSDB_REGISTER_NOTIFICATION

3 MGBL

adminexec-4DISPLAYING_DEFAULT_HOSTNAME

4 MGBL

ALARM_LOC_TEST-4SIMPLE_NO_SOURCELOC

4 MGBL

ALARM_LOC_TEST-4SIMPLE_WITH_SOURCELOC

4 MGBL

ALARMS-6-CLEAR

6 MGBL

APP_OBJ-3-NULL_PARAM

3 MGBL

APP_OBJ-4-INVALID_ELEM_COUNT

4 MGBL

APP_OBJ-7-ERR

7 MGBL

ATM_VCCLASS-2-CONSUMER_INIT

2 MGBL

ATM_VCCLASS-2-MEM

2 MGBL

ATM_VCCLASS-2-PRODUCER_INIT

2 MGBL

ATM_VCCLASS-2-VCCLASS_LIB_INIT

2 MGBL

ATM_VCCLASS-3-ATTACH

3 MGBL

ATM_VCCLASS-3-CONSUMER

3 MGBL

ATM_VCCLASS-3-CONSUMER_ENS

3 MGBL

ATM_VCCLASS-3-CONSUMER_RCV_BUF

3 MGBL

ATM_VCCLASS-3-EDM

3 MGBL

ATM_VCCLASS-3-ENS

3 MGBL

ATM_VCCLASS-3-INVALID_ARG

3 MGBL

ATM_VCCLASS-3-PRODUCER_DATA

3 MGBL

ATM_VCCLASS-3-PRODUCER_HDLR

3 MGBL

ATM_VCCLASS-3-SYSDB

3 MGBL

ATM_VCCLASS-3-TREE

3 MGBL

CFGHLP-6-CONFIG_SAVE_DELAY

6 MGBL

CLEAR-3-ERR_MEM_ALLOC

3 MGBL

CLEAR-3-ERR_SYSDB_BIND

3 MGBL

CLEAR-3-ERR_SYSDB_SET

3 MGBL

CLEAR-3-ERR_SYSDB_UNBIND

3 MGBL

CONAUX-3-AUX_BLOCK_REG_ERROR

3 MGBL

CONAUX-3-AUX_REG_ERROR

3 MGBL

CONAUX-3-CONSOLE_BLOCK_REG_ERROR

3 MGBL

CONAUX-3-CONSOLE_REG_ERROR

3 MGBL

CONFIG_HIST_UPDATE-3-INET_NTOP_ERR

3 MGBL

CONFIG_HIST_UPDATE-3-SYSDB_BIND_ERR

3 MGBL

CONFIG_HIST_UPDATE-3-SYSDB_DELETE

3 MGBL

CONFIG_HIST_UPDATE-3-SYSDB_GET

3 MGBL

CONFIG_HIST_UPDATE-3-SYSDB_SET

3 MGBL

CONFIG_HIST_UPDATE-3TRANSACTION_START

3 MGBL

CONFIG_HIST_UPDATE-3-TTY_NMSPC_PATH

3 MGBL

CONFIG_HIST_UPDATE-3TUPLE_LOCK_ERROR

3 MGBL

CONFIG_HIST_UPDATE-3TUPLE_NULL_ON_SUCCESS

3 MGBL

CONFIG_HIST_UPDATE-3-TUPLE_PACK

3 MGBL

CONFIG_HIST_UPDATE-3TUPLE_UNLOCK_ERROR

3 MGBL

CONFIG_HIST_UPDATE-3-TUPLE_UNPACK

3 MGBL

CONFIG-0-INIT_FAILURE

--

MGBL

CONFIG-0-INIT_RETRY_SUCCEEDED

--

MGBL

CONFIG-3-ADMIN_INCONSISTENCY_ALARM

3 MGBL

CONFIG-3-CFS_NATIVITY_CLEANUP

3 MGBL

CONFIG-3-DB_CONSOLIDATE

3 MGBL

CONFIG-3-DB_DISK

3 MGBL

CONFIG-3-EVM_FAIL

3 MGBL

CONFIG-3-FILESAVE_ERROR

3 MGBL

CONFIG-3-INCONSISTENCY_ALARM

3 MGBL

CONFIG-3-INTERFACE_ERROR

3 MGBL

CONFIG-3-OIR_TIMEOUT

3 MGBL

CONFIG-3-PARSE

3 MGBL

CONFIG-3-READ

3 MGBL

CONFIG-3-STARTUP

3 MGBL

CONFIG-3-UNLOCK_ERR

3 MGBL

CONFIG-4-CFS_NATIVITY

4 MGBL

CONFIG-4-DB_DISK_FAILURE

4 MGBL

CONFIG-4-DB_INIT_FAILURE

4 MGBL

CONFIG-4-DIR_MODE_ERR

4 MGBL

CONFIG-4-FAILED

4 MGBL

CONFIG-4-INIT_ERROR

4 MGBL

CONFIG-4-INTERFACE_PORTS

4 MGBL

CONFIG-4-TRACE

4 MGBL

CONFIG-4-VERSION

4 MGBL

CONFIG-5-SESSION_CLEAR

5 MGBL

CONFIG-6-COMMITDB_SANITY

6 MGBL

CONFIG-6-DB_COMMIT

6 MGBL

CONFIG-6-DB_COMMIT_ADMIN

6 MGBL

CONFIG-6-OIR_RESTORE

6 MGBL

CONFIG-6-OIR_SAVE

6 MGBL

CONFIG-6-PKG

6 MGBL

CONFIG-6-STARTUP_ALTERNATE

6 MGBL

CONFIG-7-INTERNAL

7 MGBL

CONFIGCLI-2-STARTUP_ANNOUNCE_ERR

2 MGBL

CONFIGCLI-3-AAA_ERR

3 MGBL

CONFIGCLI-3-ADMIN_BATCH_CONFIG_FAIL

3 MGBL

CONFIGCLI-3-ADMIN_CONFIG_INIT_ERR

3 MGBL

CONFIGCLI-3-AUTOSAVE_INIT_ERR

3 MGBL

CONFIGCLI-3-BATCH_CONFIG_FAIL

3 MGBL

CONFIGCLI-3-CHILD_TERMINATED

3 MGBL

CONFIGCLI-3-CONFIG_ABORT

3 MGBL

CONFIGCLI-3-EVENT_ATTACH

3 MGBL

CONFIGCLI-3-EVH_INIT_ERR

3 MGBL

CONFIGCLI-3-FAILED_CREATE_THREAD

3 MGBL

CONFIGCLI-3-FILE_OPERATION

3 MGBL

CONFIGCLI-3-GETLINE_DATA

3 MGBL

CONFIGCLI-3-LTRACE_INIT

3 MGBL

CONFIGCLI-3-LTRACE_INIT

3 MGBL

CONFIGCLI-3-LWM

3 MGBL

CONFIGCLI-3-MALLOC_ERROR

3 MGBL

CONFIGCLI-3-MEMORY_INFO_ERROR

3 MGBL

CONFIGCLI-3-PIPE_FAILURE

3 MGBL

CONFIGCLI-3-PROGRESS_BAR

3 MGBL

CONFIGCLI-3-READ_FAILURE

3 MGBL

CONFIGCLI-3-SIGNAL_ATTACH

3 MGBL

CONFIGCLI-3-STARTUP_FILE_DIR_ERR

3 MGBL

CONFIGCLI-3-SYSDB

3 MGBL

CONFIGCLI-3-TARGET_CFG_CLEAR

3 MGBL

CONFIGCLI-3-TARGET_CFG_COMMIT

3 MGBL

CONFIGCLI-3-TARGET_CFG_COMMIT

3 MGBL

CONFIGCLI-3-TARGET_CFG_CREATE

3 MGBL

CONFIGCLI-3-TARGET_CFG_DESTROY

3 MGBL

CONFIGCLI-3-TARGET_CFG_LOCKERR

3 MGBL

CONFIGCLI-3-TARGET_CFG_UNLOCKERR

3 MGBL

CONFIGCLI-4DISPLAYING_DEFAULT_HOSTNAME

4 MGBL

CONFIGCLI-4FAILED_CONFIG_NOT_DELETED

4 MGBL

CONFIGCLI-4-SPAWN_FAILURE

4 MGBL

CONFIGCLI-4-STARTUP_FILE_OPEN_WRN

4 MGBL

CONFIGCLI-7-INFRA_READY

7 MGBL

CONFIGEDM-3-FAILEDLIST

3 MGBL

CONFIGEDM-3-FAILEDREGCOMP

3 MGBL

CONFIGEDM-3-FAILEDREGEXEC

3 MGBL

CONFIGEDM-3-REGISTER

3 MGBL

CONFIGEDM-3-UNREGISTER

3 MGBL

CORRELATOR-4-BUFFER_RECYCLE

4 MGBL

CVAC-2-INIT_FAILED

2 MGBL

CVAC-3-CONFIG_ERROR

3 MGBL

CVAC-3-FILE_ERROR

3 MGBL

CVAC-4-CONFIG_DONE

4 MGBL

CVAC-4-FILE_IGNORED

4 MGBL

EMORB_XMLAGENT-3-CRYPTO_DEACT

3 MGBL

EMORB_XMLAGENT-3-CRYPTO_INIT

3 MGBL

EMORB_XMLAGENT-6-PIPE_RESTART

6 MGBL

EMORB_XMLAGENT-6RESTART_WAIT_TIMEOUT

6 MGBL

EMORB_XMLAGENT-6-TCP_RESTART

6 MGBL

exec-3-ACCT_ERR

3 MGBL

exec-3-BAG_REGISTER

3 MGBL

exec-3-CHDIR_FAILED

3 MGBL

exec-3-DEBUG_DLL_HOOK_FAILED

3 MGBL

exec-3-DEBUGINIT

3 MGBL

exec-3-DEBUGREG

3 MGBL

exec-3-EVENT_ATTACH

3 MGBL

exec-3-EVENT_BLOCK

3 MGBL

exec-3-EVENT_INIT_EVENT

3 MGBL

exec-3-EVENT_MANAGER_CREATE

3 MGBL

exec-3-EVENT_MANAGER_DESTORY_FAILED

3 MGBL

exec-3-GET_ENVPATH

3 MGBL

exec-3-GETLINE_DATA

3 MGBL

exec-3-GETLINE_INIT

3 MGBL

exec-3-LOGIN_AUTHEN

3 MGBL

exec-3-LOGIN_ECM_CONN_SYSDB_FAILED

3 MGBL

exec-3-LTRACE_INIT

3 MGBL

exec-3-LWM

3 MGBL

exec-3-MUTEX_LOCK

3 MGBL

exec-3-PARSER_UNAVAIL

3 MGBL

exec-3-PTHREAD_CREATE

3 MGBL

exec-3-PTHREAD_MUTEX_LOCK

3 MGBL

exec-3-PTHREAD_MUTEX_UNLOCK

3 MGBL

exec-3-SETENV_FAILED

3 MGBL

exec-3-SYSDB_BIND_FAILED

3 MGBL

exec-3-SYSDB_ITEM_DELETE_FAILED

3 MGBL

exec-3-SYSDB_ITEM_GET_FAILED

3 MGBL

exec-3-SYSDB_REGISTER_EDM

3 MGBL

exec-3-SYSDB_REGISTER_NOTIFICATION

3 MGBL

exec-3-SYSDB_UNBIND_FAILED

3 MGBL

exec-3-TASKMAP_GET

3 MGBL

exec-3-TCGETATTR_FAIL

3 MGBL

exec-3-TCSETATTR_FAIL

3 MGBL

exec-3-TTY_DETAILS

3 MGBL

exec-3-TTY_MGMT_CONNECT

3 MGBL

exec-3-TTY_MGMT_DEREGISTER

3 MGBL

exec-3-TTY_MGMT_REG_SUBSET

3 MGBL

exec-3-TTY_MGMT_SCAN

3 MGBL

exec-3-TUPLE_PACK

3 MGBL

exec-3-TUPLE_UNPACK

3 MGBL

exec-3-TUPLE_UNPACK_MASK

3 MGBL

exec-6-TTY_MGMT_REG_OPTIONS

6 MGBL

GSR_NETFLOW-3-ERR_INIT

3 MGBL

GSR_NETFLOW-3-HW_PROG

3 MGBL

GSR_NETFLOW-7-ERR

7 MGBL

HTTP_CLI-3-AAA

3 MGBL

HTTP_CLI-3-AAA

3 MGBL

HTTP_CLI-3-EMWEB

3 MGBL

HTTP_CLI-3-EMWEB

3 MGBL

HTTP_CLI-3-FILE

3 MGBL

HTTP_CLI-3-FILE

3 MGBL

HTTP_CLI-3-INTERNAL

3 MGBL

HTTP_CLI-3-INTERNAL

3 MGBL

HTTP_CLI-3-INTERNAL_NULL

3 MGBL

HTTP_CLI-3-INTERNAL_NULL

3 MGBL

HTTP_CLI-3-INTERNAL_PARAMETER

3 MGBL

HTTP_CLI-3-INTERNAL_PARAMETER

3 MGBL

HTTP_CLI-3-MEMORY

3 MGBL

HTTP_CLI-3-MEMORY

3 MGBL

HTTP_CLI-3-PARSER

3 MGBL

HTTP_CLI-3-PARSER

3 MGBL

HTTP_CLI-3-SYSDB

3 MGBL

HTTP_CLI-3-SYSDB

3 MGBL

HTTP_CLI-3-SYSDB_CONN

3 MGBL

HTTP_CLI-3-SYSDB_CONN

3 MGBL

HTTP_CLI-3-SYSDB_GET

3 MGBL

HTTP_CLI-3-SYSDB_GET

3 MGBL

HTTP_CLI-3-THREAD

3 MGBL

HTTP_CLI-3-THREAD

3 MGBL

HTTP_CLI-5-WARN

5 MGBL

HTTP_CLI-5-WARN

5 MGBL

HTTP_ENA-3-AUTH

3 MGBL

HTTP_ENA-3-AUTH

3 MGBL

HTTP_ENA-3-BACKEND_SCAN

3 MGBL

HTTP_ENA-3-BACKEND_SCAN

3 MGBL

HTTP_ENA-3-CRYPTO_DEACT

3 MGBL

HTTP_ENA-3-CRYPTO_DEACT

3 MGBL

HTTP_ENA-3-EMWEB

3 MGBL

HTTP_ENA-3-EMWEB

3 MGBL

HTTP_ENA-3-EVENT_MGR

3 MGBL

HTTP_ENA-3-EVENT_MGR

3 MGBL

HTTP_ENA-3-FILE

3 MGBL

HTTP_ENA-3-FILE

3 MGBL

HTTP_ENA-3-INTERNAL_NULL

3 MGBL

HTTP_ENA-3-INTERNAL_NULL

3 MGBL

HTTP_ENA-3-MEMORY

3 MGBL

HTTP_ENA-3-MEMORY

3 MGBL

HTTP_ENA-3-SSL_INIT

3 MGBL

HTTP_ENA-3-SSL_INIT

3 MGBL

HTTP_ENA-3-SYSDB

3 MGBL

HTTP_ENA-3-SYSDB

3 MGBL

HTTP_ENA-3-SYSDB_CONN

3 MGBL

HTTP_ENA-3-SYSDB_CONN

3 MGBL

HTTP_ENA-6-TCP_FAIL

6 MGBL

HTTP_ENA-6-TCP_FAIL

6 MGBL

HTTP_ENA-7-TCP_UNKNOWN

7 MGBL

HTTP_ENA-7-TCP_UNKNOWN

7 MGBL

HTTP-3-EMWEB_ERROR

3 MGBL

HTTP-3-EMWEB_ERROR

3 MGBL

HTTP-6-CRYPTO_DEACT

6 MGBL

HTTP-7-DEBUGGING

7 MGBL

HTTP-7-DEBUGGING

7 MGBL

HTTP-7-INTERNAL

7 MGBL

HTTP-7-INTERNAL

7 MGBL

IFSTATS-3-CHKPT_INIT

3 MGBL

IFSTATS-3-COMMS_INIT

3 MGBL

IFSTATS-3-COUNTER_OVERRUN

3 MGBL

IFSTATS-3-ERR_NDT_QUEUE

3 MGBL

IFSTATS-3-EVM_REG_INIT

3 MGBL

IFSTATS-3-INIT

3 MGBL

IFSTATS-3-LOAD_INTERVAL_CONFIG

3 MGBL

IFSTATS-3-MESSAGE_SIZE

3 MGBL

IFSTATS-3-MISSING_STATS

3 MGBL

IFSTATS-3-SHMWIN_INIT

3 MGBL

IFSTATS-3-STATE_CHANGE

3 MGBL

IFSTATS-3-SYSDB_REG_INIT

3 MGBL

IFSTATS-3-THREAD_INIT

3 MGBL

IFSTATS-3-TYPE_LOOKUP

3 MGBL

IFSTATS-3-TYPE_UPDATE

3 MGBL

IFSTATS-4-COLLECTOR_TIMEOUT

4 MGBL

IFSTATS-4-ERR_EVENT_WAIT

4 MGBL

IFSTATS-6-CLEAR_COUNTERS

6 MGBL

INTERFACE-3-CI_GEN_ERROR

3 MGBL

INTERFACE-3-CI_NOMEM_ERROR

3 MGBL

INTERFACE-4-ERR_SYSDB_BAG_DECODE

4 MGBL

INTERFACE-4-ERR_SYSDB_BIND

4 MGBL

INVENTORYCI-3-INIT_ERROR

3 MGBL

IPSLA_TS_SVR-3-EVENT

3 MGBL

IPSLA_TS_SVR-3-INIT

3 MGBL

IPSLA-4-ERR_MEM

4 MGBL

IPSLA-4-ERR_MPLSLM

4 MGBL

IPSLA-4-ERR_OPER

4 MGBL

IPSLA-5-INTERNAL

5 MGBL

IPSLA-5-LPD_RESULT_CHG

5 MGBL

IPSLA-5-LSP_GROUP_CHG

5 MGBL

IPSLA-5-THRESHOLD_CLEAR

5 MGBL

IPSLA-5-THRESHOLD_SET

5 MGBL

IPSLA-6-DISC_LIMIT

6 MGBL

IPSLA-7-AGENT

7 MGBL

IPSLA-7-ERR_SYSDB

7 MGBL

LIBNVGEN-3-CIDR_API_ERR

3 MGBL

LIBNVGEN-3-ERR_MEM_ALLOC

3 MGBL

LIBNVGEN-3-ERR_SYSDB_BIND

3 MGBL

LIBNVGEN-3-ERR_SYSDB_ITEM_GET

3 MGBL

LIBNVGEN-3-ERR_THREAD_MUTEX_LOCK

3 MGBL

LIBNVGEN-3-ERR_THREAD_MUTEX_UNLOCK

3 MGBL

LIBNVGEN-3-GENERAL_ERR

3 MGBL

LIBNVGEN-3-LTRACE_INIT

3 MGBL

LIBNVGEN-3-LWM_API_ERR

3 MGBL

LIBPARSER-3-AAA_STRING_TASKID_CHECK

3 MGBL

LIBPARSER-3-ADD_SESSION

3 MGBL

LIBPARSER-3-API_FAIL

3 MGBL

LIBPARSER-3-COMMENT_LIMIT

3 MGBL

LIBPARSER-3-ERR_DLL_UNKNOWN

3 MGBL

LIBPARSER-3-ERR_DLL_UNKNOWN_FUNC

3 MGBL

LIBPARSER-3-ERR_ETIMEOUT

3 MGBL

LIBPARSER-3-ERR_INVALID_DATA

3 MGBL

LIBPARSER-3-ERR_MEM_ALLOC

3 MGBL

LIBPARSER-3-ERR_PARSE

3 MGBL

LIBPARSER-3-ERR_SYSDB_API

3 MGBL

LIBPARSER-3-ERR_SYSDB_BIND

3 MGBL

LIBPARSER-3ERR_SYSDB_CONDITIONAL_DELETE

3 MGBL

LIBPARSER-3-ERR_SYSDB_DATALIST

3 MGBL

LIBPARSER-3-ERR_SYSDB_DATALIST_NEXT

3 MGBL

LIBPARSER-3-ERR_SYSDB_DELETE

3 MGBL

LIBPARSER-3-ERR_SYSDB_SET

3 MGBL

LIBPARSER-3-ERR_THREAD_COND_WAIT

3 MGBL

LIBPARSER-3-ERR_THREAD_MUTEX_LOCK

3 MGBL

LIBPARSER-3ERR_THREAD_MUTEX_UNLOCK

3 MGBL

LIBPARSER-3-FAILEDREGCOMP

3 MGBL

LIBPARSER-3-FILE_IO

3 MGBL

LIBPARSER-3-FILE_SIZE

3 MGBL

LIBPARSER-3-INITIFMGR

3 MGBL

LIBPARSER-3IP_ADDR2_HEX_STRING_FAILED

3 MGBL

LIBPARSER-3-IPV46_COMPRESSION_ERROR

3 MGBL

LIBPARSER-3-LTRACE_INIT

3 MGBL

LIBPARSER-3-LWM_API_ERR

3 MGBL

LIBPARSER-3-TESTPOINT_LIMIT

3 MGBL

LIBPARSER-3-TOOMANYALIASES

3 MGBL

LIBPARSER-3-TTY_NMSPC_PATH

3 MGBL

LIBPARSER-3-TUPLE_UNPACK

3 MGBL

LIBPARSER-3WDSYSMON_REGISTER_ERROR

3 MGBL

LIBPARSER-7-ERR_DEBUG

7 MGBL

LIBPARSER-7-ERR_SYSDB_REG_NOTIFY

7 MGBL

LIBPARSER-7-ERR_SYSDB_UNREG_NOTIFY

7 MGBL

LIBPARSER-7-FDOPEN

7 MGBL

LIBSHELL-3-PTHREAD_MUTEX_LOCK

3 MGBL

LIBSHELL-3-WS_INIT

3 MGBL

MDACON-4-ABORTBULK

4 MGBL

MDACON-4-ABORTTRANS

4 MGBL

MDACON-4-ARRAYTOOBIG

4 MGBL

MDACON-4-BADCLASS

4 MGBL

MDACON-4-BADFILTER

4 MGBL

MDACON-4-BADFORMAT

4 MGBL

MDACON-4-BADHRCHY

4 MGBL

MDACON-4-BADOPTION

4 MGBL

MDACON-4-BIND

4 MGBL

MDACON-4-COMMITTRANS

4 MGBL

MDACON-4-COPY

4 MGBL

MDACON-4-CREATE

4 MGBL

MDACON-4-DATAARRAYLENGTH

4 MGBL

MDACON-4-DATAARRAYTYPE

4 MGBL

MDACON-4-DELETE

4 MGBL

MDACON-4-ENDBULK

4 MGBL

MDACON-4-ERR_MEM_ALLOC

4 MGBL

MDACON-4-ERRORLIST

4 MGBL

MDACON-4-EVENTLIST

4 MGBL

MDACON-4-EXCESS

4 MGBL

MDACON-4-FILEOPEN

4 MGBL

MDACON-4-FILEREAD

4 MGBL

MDACON-4-FINDDATA

4 MGBL

MDACON-4-GET

4 MGBL

MDACON-4-INSUFF_ARG

4 MGBL

MDACON-4-LIST

4 MGBL

MDACON-4-MISMATCH

4 MGBL

MDACON-4-MISSDESTNAME

4 MGBL

MDACON-4-MISSFILTER

4 MGBL

MDACON-4-MISSNUMBER

4 MGBL

MDACON-4-MISSSTARTOBJECT

4 MGBL

MDACON-4-MISSVALUE

4 MGBL

MDACON-4-NOTLEAF

4 MGBL

MDACON-4-READERINIT

4 MGBL

MDACON-4-SET

4 MGBL

MDACON-4-STARTBULK

4 MGBL

MDACON-4-STARTTRANS

4 MGBL

MDACON-4-SYSDBMATCH

4 MGBL

MDACON-4-TASKNAMES

4 MGBL

MDACON-4-TEST

4 MGBL

MDACON-4-UNKCMD

4 MGBL

MDACON-7-INTERNAL

7 MGBL

NETFLOW-3-ERR_CFG_APPLY

3 MGBL

NETFLOW-4-WARNING_CFG_APPLY

4 MGBL

NETFLOW-6-INFO_CACHE_SIZE_EXCEEDED

6 MGBL

NETFLOW-7-ERR

7 MGBL

NVGEN-3-ARG

3 MGBL

NVGEN-3-BASENAME

3 MGBL

NVGEN-3-BGCOPTIONMISSING1

3 MGBL

NVGEN-3-BLANKENTERTUPLE

3 MGBL

NVGEN-3-BUFFER

3 MGBL

NVGEN-3-CFS_INIT_ERR

3 MGBL

NVGEN-3-COPTIONNOTPRESENT

3 MGBL

NVGEN-3-DECODE_TUPLE

3 MGBL

NVGEN-3-DECODESTR

3 MGBL

NVGEN-3-DIR_IO

3 MGBL

NVGEN-3-ENDCOPTIONINCOMPLETE

3 MGBL

NVGEN-3-ENDCOPTIONMISSINGCOMMA

3 MGBL

NVGEN-3-ENDCOPTIONNOTPRESENT

3 MGBL

NVGEN-3-ENV

3 MGBL

NVGEN-3-ERR_DLL_UNKNOWN

3 MGBL

NVGEN-3-ERR_DLL_UNKNOWN_FUNC

3 MGBL

NVGEN-3-ERR_MEM_ALLOC

3 MGBL

NVGEN-3-ERR_MEM_ALLOC_2

3 MGBL

NVGEN-3-ERR_SYSDB_API

3 MGBL

NVGEN-3-ERR_SYSDB_BIND

3 MGBL

NVGEN-3-ERR_SYSDB_GET

3 MGBL

NVGEN-3-ERR_SYSDB_LIST

3 MGBL

NVGEN-3-ERR_SYSDB_SET

3 MGBL

NVGEN-3-ERR_THREAD_COND_WAIT

3 MGBL

NVGEN-3-ERR_THREAD_CREATE

3 MGBL

NVGEN-3-ERR_THREAD_JOIN

3 MGBL

NVGEN-3-ERR_THREAD_MUTEX_LOCK

3 MGBL

NVGEN-3-ERR_THREAD_MUTEX_UNLOCK

3 MGBL

NVGEN-3-EVENT_ATTACH

3 MGBL

NVGEN-3-EVENTBLOCK

3 MGBL

NVGEN-3-EVENTMGRCREATE

3 MGBL

NVGEN-3-FAILEDREGCOMP

3 MGBL

NVGEN-3-FILE_COMPRESS

3 MGBL

NVGEN-3-FILE_IO

3 MGBL

NVGEN-3-FILE_NOT_OPEN

3 MGBL

NVGEN-3-GENERAL_ERR

3 MGBL

NVGEN-3-ILLEGAL_TEMPLATE_TUPLE

3 MGBL

NVGEN-3-ILLEGALENTERSTR

3 MGBL

NVGEN-3-ILLEGALENTERTUPLE

3 MGBL

NVGEN-3-INSTALL_READY_FAILED

3 MGBL

NVGEN-3-INTF_NAME_NULL

3 MGBL

NVGEN-3-INTF_NAME_PARSE_ERROR

3 MGBL

NVGEN-3-INTFINFO

3 MGBL

NVGEN-3-INVALID_IPV4_6_FLAG

3 MGBL

NVGEN-3-INVALID_IPV6_FLAG

3 MGBL

NVGEN-3-INVALID_NOTIFICATION

3 MGBL

NVGEN-3-INVALID_ORDER

3 MGBL

NVGEN-3-INVALIDINPUT

3 MGBL

NVGEN-3-INVALIDINPUTFMT

3 MGBL

NVGEN-3-INVALIDNXCOPTION

3 MGBL

NVGEN-3-INVALIDTEMPLATE

3 MGBL

NVGEN-3-INVALIDVERSION
NVGEN-3-INVALTUPLEPATH

3 MGBL
3 MGBL

NVGEN-3-LOCK_ERR

3 MGBL

NVGEN-3-MASKFORMAT_REGISTER

3 MGBL

NVGEN-3-MASKFORMATINIT

3 MGBL

NVGEN-3-MINMSGLENGTH

3 MGBL

NVGEN-3-MISSINGBRACKET

3 MGBL

NVGEN-3-MISSINGEQUALSIGN

3 MGBL

NVGEN-3-MSGREADV

3 MGBL

NVGEN-3-NAMESPACE_ERR

3 MGBL

NVGEN-3-NESTEDCOPTION

3 MGBL

NVGEN-3-NULLCHARMISSING

3 MGBL

NVGEN-3-OBJINREPLACE

3 MGBL

NVGEN-3-OPEN

3 MGBL

NVGEN-3-PART_NAMES_GET_ERR

3 MGBL

NVGEN-3-PATTERN_NOT_FOUND

3 MGBL

NVGEN-3-READERR

3 MGBL

NVGEN-3-REGISTER_INSTMGR

3 MGBL

NVGEN-3-RESMGRATTACH

3 MGBL

NVGEN-3-RMINIT

3 MGBL

NVGEN-3-SHRINK_IPV4_6ADDRESS_FAILED

3 MGBL

NVGEN-3-SLOTORDER_REGISTER

3 MGBL

NVGEN-3-SLOTORDERINIT

3 MGBL

NVGEN-3-STAT

3 MGBL

NVGEN-3-SUBMODESTRING

3 MGBL

NVGEN-3-SYSDBOPERATION

3 MGBL

NVGEN-3-TARGET_CFG_CREATE

3 MGBL

NVGEN-3-TARGET_CFG_DESTROY

3 MGBL

NVGEN-3-TARGET_CFG_LOCKERR

3 MGBL

NVGEN-3-TARGET_CFG_UNLOCKERR

3 MGBL

NVGEN-3-TASKID_COMPARE_ERROR

3 MGBL

NVGEN-3-TASKID_EXCEEDED

3 MGBL

NVGEN-3-TASKID_MISMATCH

3 MGBL

NVGEN-3-TASKID_NOT_FOUND

3 MGBL

NVGEN-3-TOKENNUMBER

3 MGBL

NVGEN-3-TOKENTYPE

3 MGBL

NVGEN-3-UNMATCHEDCOPTIONS

3 MGBL

NVGEN-3-WRMEM_ABORT

3 MGBL

NVGEN-4-CONFIG_GEN_ERR

4 MGBL

PARSER-3-API_FAIL

3 MGBL

PARSER-3-BOGUS_HOOKPOINT

3 MGBL

PARSER-3-BOGUS_LINKPOINT

3 MGBL

PARSER-3-BUFFER_OVERFLOW

3 MGBL

PARSER-3CARD_MODULE_FROM_NODEID_FAILED

3 MGBL

PARSER-3-CREATETHREAD

3 MGBL

PARSER-3-ENV

3 MGBL

PARSER-3-ERR_GENERAL_ERR
PARSER-3-ERR_SYSDB_BAG_DECODE

3 MGBL
3 MGBL

PARSER-3-ERR_SYSDB_GET

3 MGBL

PARSER-3-ERR_SYSDB_STRING_ENCODE

3 MGBL

PARSER-3-EXTRACT_FAILED

3 MGBL

PARSER-3EXTRACT_NODEID_FIELDS_FAILED

3 MGBL

PARSER-3-INVALID_NOTIFICATION

3 MGBL

PARSER-3-INVALID_PARSERFILE

3 MGBL

PARSER-3-INVALIDDETAILS

3 MGBL

PARSER-3-INVALIDINPUTFMT

3 MGBL

PARSER-3-INVALIDOFFSET

3 MGBL

PARSER-3-INVALIDRANGE

3 MGBL

PARSER-3-INVALIDVERSION

3 MGBL

PARSER-3INVENTORY_DB_INTEGRITY_ERROR

3 MGBL

PARSER-3INVENTORY_DB_SIZE_INCREASE_FAILED

3 MGBL

PARSER-3-INVENTORY_DB_SIZE_ZERO

3 MGBL

PARSER-3-INVENTORY_DESCRIPTION_NULL

3 MGBL

PARSER-3-INVENTORY_FIELD_IS_NULL

3 MGBL

PARSER-3-INVENTORY_FIELD_NOT_NUMBER

3 MGBL

PARSER-3-LOCK_ERR

3 MGBL

PARSER-3-MMAP

3 MGBL

PARSER-3-NODE_CREATION_FAILED

3 MGBL

PARSER-3-NODEID_TO_STRING_ERROR

3 MGBL

PARSER-3-NOTIFICATION_PATH_NULL

3 MGBL

PARSER-3OBJECT_NOT_FOUND_FOR_RANGE

3 MGBL

PARSER-3-OVERFLOW

3 MGBL

PARSER-3-RACK_TO_STR_FAILED

3 MGBL

PARSER-3-REGEX_COMP_ERROR

3 MGBL

PARSER-3-RIGHTARG

3 MGBL

PARSER-3-SUBMODE

3 MGBL

PARSER-3-SYSDBOPERATION

3 MGBL

PARSER-3-TASKID_LIMIT

3 MGBL

PARSER-3-THREAD_LIMIT

3 MGBL

PARSER-3-TUPLEUNPACK

3 MGBL

PARSER-3-UNKNOWNTOKEN

3 MGBL

PARSER-3-UNRESOLVED_HOOKPOINT

3 MGBL

PARSER-3-UNRESOLVED_LINKPOINT

3 MGBL

PARSER-3-UNSUPPORTEDARG

3 MGBL

PARSER-7-ERR_LRD_EVENT

7 MGBL

PM-5-CHKPT

5 MGBL

PM-5-DUMP_FAIL

5 MGBL

PM-5-ERR_MEM

5 MGBL

PM-5-MEMORY_LIMITS

5 MGBL

PM-5-TFTP

5 MGBL

PM-6-DUMP
PM-6-TFTP_DISABLED

6 MGBL
6 MGBL

PM-6-TFTP_SEND

6 MGBL

PM-6-THRESHOLD

6 MGBL

PM-7-ERR_SYSDB

7 MGBL

PM-7-INTERNAL

7 MGBL

PM-7-WDSYSMON_ERROR

7 MGBL

PRP_UPGRADE-3-BOOTVAR_FILE_OPEN

3 MGBL

PRP_UPGRADE-3-CONF_SYNC_FAIL

3 MGBL

PRP_UPGRADE-3-MBI_BOOT_HOLD

3 MGBL

PRP_UPGRADE-3-MBI_BOOT_UNHOLD

3 MGBL

PRP_UPGRADE-3-PROC_AS_IO

3 MGBL

PRP_UPGRADE-3-SNMP_SYNC_FAIL

3 MGBL

PRP_UPGRADE-3-SPAWN_CP

3 MGBL

PRP_UPGRADE-3-SPAWN_RM

3 MGBL

PRP_UPGRADE-3-WAITPID_CP

3 MGBL

PRP_UPGRADE-3-WAITPID_RM

3 MGBL

PRP_UPGRADE-6-COMPLETE_SYNC

6 MGBL

PRP_UPGRADE-6-START_SYNC

6 MGBL

RS232-1-CONSOLE_SESSION_ANYWAY

1 MGBL

RS232-3-BAUD_RATE

3 MGBL

RS232-3-CABLE_MONITOR_DISABLED

3 MGBL

RS232-3-FRAMING_ERROR

3 MGBL

RS232-3-KERNEL

3 MGBL

RS232-3-LINE_CONNECT_FAILURE

3 MGBL

RS232-3-OVERRUN_ERROR

3 MGBL

RS232-3-PARITY_ERROR

3 MGBL

RS232-3-SESSION_DISCONNECT_FAILURE

3 MGBL

RS232-3-SESSION_NOTIFICATION_ABORT

3 MGBL

RS232-3-TTY_NOT_REGISTERED

3 MGBL

RS232-4-API_LOCATE_ERROR

4 MGBL

RS232-4-DLL_OPEN_ERROR

4 MGBL

RS232-4-MAPPING_ERROR

4 MGBL

RS232-4-MEM_ALLOC_ERROR

4 MGBL

RS232-4-NO_PACKET_MODE

4 MGBL

RS232-4-PDP_SET_ERROR

4 MGBL

RS232-4-SESSION_SETUP_ERROR

4 MGBL

RS232-4-TEMPLATE_APPLY_ERROR

4 MGBL

RS232-4-TEMPLATE_DEAPPLY_ERROR

4 MGBL

RS232-6-DCD_DISCOVERED

6 MGBL

RS232-6-DCD_LOST

6 MGBL

RTC-2-CAL_CHIP_MAP_FAIL

2 MGBL

RTC-2-CAL_CHIP_NMI_DISABLED

2 MGBL

RTC-2-CAL_CHIP_NOT_FOUND

2 MGBL

RTC-7-CAL_CHIP_MAP

7 MGBL

RTC-7-CAL_CHIP_PRINT_CURRENT_TIME

7 MGBL

RTC-7-CAL_CHIP_PRINT_OPTION

7 MGBL

RTC-7-CAL_CHIP_PRINT_OPTION_SET_VAL

7 MGBL

RTC-7-CAL_CHIP_PRINT_TIME_TYPE

7 MGBL

RTC-7-CAL_CHIP_PRINT_TIME_VAL

7 MGBL

RTC-7-CAL_CHIP_READ_CMOS

7 MGBL

RTC-7-CAL_CHIP_READ_CONF_REG

7 MGBL

RTC-7-CAL_CHIP_READ_RTC

7 MGBL

RTC-7-CAL_CHIP_READING

7 MGBL

RTC-7-CAL_CHIP_WRITE_CMOS

7 MGBL

RTC-7-CAL_CHIP_WRITE_RTC

7 MGBL

RTC-7-CAL_CHIP_WRITING

7 MGBL

S2681-3-COND_SIGNAL_ERROR

3 MGBL

S2681-3-INTERRUPT_UNMASK_ERROR

3 MGBL

S2681-3-IO_PERM_ERROR

3 MGBL

S2681-3-MUTEX_LOCK_ERROR

3 MGBL

S2681-3-MUTEX_UNLOCK_ERROR

3 MGBL

S2681-3-SCHED_PRIORITY_ERROR

3 MGBL

S2681-3-SCHEDPARAM_ERROR

3 MGBL

S2681-3-SCHEDPOLICY_ERROR

3 MGBL

S2681-3-STATUS_MUTEX_LOCK_ERROR

3 MGBL

S2681-3-STATUS_MUTEX_UNLOCK_ERROR

3 MGBL

S2681-3-THREAD_CREATE_ERROR

3 MGBL

S2681-6-STAT_CREATE_ERROR

6 MGBL

SCHBRO-7-ARRAYTOOBIG

7 MGBL

SCHBRO-7-AUTHENTICATE

7 MGBL

SCHBRO-7-BADCLASS

7 MGBL

SCHBRO-7-BADFORMAT

7 MGBL

SCHBRO-7-BADHRCHY

7 MGBL

SCHBRO-7-BADOPTION

7 MGBL

SCHBRO-7-BIND

7 MGBL

SCHBRO-7-DATAARRAYLENGTH

7 MGBL

SCHBRO-7-DATAARRAYTYPE

7 MGBL

SCHBRO-7-ERR_MEM_ALLOC

7 MGBL

SCHBRO-7-EXCESS

7 MGBL

SCHBRO-7-FILEOPEN

7 MGBL

SCHBRO-7-FILEREAD

7 MGBL

SCHBRO-7-FINDDATA

7 MGBL

SCHBRO-7-GET

7 MGBL

SCHBRO-7-INTERNAL

7 MGBL

SCHBRO-7-LIST

7 MGBL

SCHBRO-7-MISMATCH

7 MGBL

SCHBRO-7-NOTLEAF

7 MGBL

SCHBRO-7-READERINIT

7 MGBL

SCHBRO-7-UNKCMD

7 MGBL

SCHEMA-6-VERSIONCHANGE

6 MGBL

SCHEMA-7-INTERNAL

7 MGBL

SCONBKUP-3-INTERNAL_FATAL

3 MGBL

SCONBKUP-7-INTERNAL_ERR

7 MGBL

SCONBKUP-7-RELOAD_REPLY_ERR

7 MGBL

SCONBKUP-7-REPLY_ERR

7 MGBL

SLINUX-3-SERIAL_INTERFACE_ERROR

3 MGBL

ST16550-3-INTERRUPT_MASK_ERROR

3 MGBL

ST16550-3-INTERRUPT_UNMASK_ERROR

3 MGBL

ST16550-3-IO_PERM_ERROR

3 MGBL

ST16550-3-ISR_MSR_ERR

3 MGBL

ST16550-3-MUTEX_LOCK_ERROR

3 MGBL

ST16550-3-MUTEX_UNLOCK_ERROR

3 MGBL

ST16550-3-SCHED_PRIORITY_ERROR

3 MGBL

ST16550-3-SCHEDPARAM_ERROR

3 MGBL

ST16550-3-SCHEDPOLICY_ERROR

3 MGBL

ST16550-3-SEM_ERROR

3 MGBL

ST16550-3-STATUS_MUTEX_LOCK_ERROR

3 MGBL

ST16550-3STATUS_MUTEX_UNLOCK_ERROR

3 MGBL

ST16550-3-THREAD_CREATE_ERROR

3 MGBL

ST16550-6-STAT_CREATE_ERROR

6 MGBL

STATSD-3-EVENT_BLOCK

3 MGBL

STATSD-3-LTRACE_INIT

3 MGBL

STATSD-3-REGISTRATION_FAILED

3 MGBL

STATSD-3-SHMEM_CORRUPTED

3 MGBL

STATSD-3-SHMEM_LOCK

3 MGBL

STATSD-5-CFG_REG_FAILED

5 MGBL

SYS-3-ALREADY_THREADED_MSG

3 MGBL

SYS-3-COMPARE_ALREADY_SET

3 MGBL

SYS-3-FTRUNCATE

3 MGBL

SYS-3-ILLEGAL_THREAD

3 MGBL

SYS-3-MALLOCFAIL

3 MGBL

SYS-3-MMAPFAIL

3 MGBL

SYS-3-MMAPSHIFT

3 MGBL

SYS-3-MUTEX_OP_FAILED

3 MGBL

SYS-3-NODE_DEL_FAILED

3 MGBL

SYS-3-NOMEMORY

3 MGBL

SYS-3-NOT_THREADED_MSG

3 MGBL

SYS-3-NULL_HANDLE_MSG

3 MGBL

SYS-3-NULLREG

3 MGBL

SYS-3-REG_UNKNOWN_TYPE

3 MGBL

SYS-3-RN_ASC_DESC

3 MGBL

SYS-3-RN_DELINK_INODE

3 MGBL

SYS-3-RN_NDESC

3 MGBL

SYS-3-RN_PRNT_LINK

3 MGBL

SYS-3-RN_VPARENT

3 MGBL

SYS-3-ROOT_ALREADY_SET

3 MGBL

SYS-3-SHMEM_MIXUP

3 MGBL

SYS-3-SHMOPENFAIL

3 MGBL

SYS-3-THREAD_NOT_EXIST

3 MGBL

SYS-3-UNINIT_MSG

3 MGBL

SYS-5-CONFIG_I

5 MGBL

SYS-5-TABLEERR

5 MGBL

TTY_CONNECT-2-UNLOCKING

2 MGBL

TTY_CONNECT-3-INTERNAL

3 MGBL

TTY_CONNECT-3-LOCKING

3 MGBL

TTY_CONNECT-3-MEMORY

3 MGBL

TTY_CONNECT-7-LWM

7 MGBL

TTY_DB-2-PANIC

2 MGBL

TTY_DB-3-KERNEL_ERROR

3 MGBL

TTY_DB-3-LOCK_BUSY

3 MGBL

TTY_DB-3-LOCK_ERROR

3 MGBL

TTY-0-ISSU_STDBY_CON_AVAILABLE

--

MGBL

TTY-2-FATAL

2 MGBL

TTY-2-PHASE2_FATAL

2 MGBL

TTY-3-ACCESS_CHECK

3 MGBL

TTY-3-ACL

3 MGBL

TTY-3-CLOSE_DEVICE

3 MGBL

TTY-3-ENV_VARS

3 MGBL

TTY-3-EXEC

3 MGBL

TTY-3-GET_CLINFO_FAILED

3 MGBL

TTY-3-INTERNAL

3 MGBL

TTY-3-INVALID_PULSE

3 MGBL

TTY-3-INVALID_SRVR_HANDLE

3 MGBL

TTY-3-ISSU_NFN_REG_FAIL

3 MGBL

TTY-3-KERNEL

3 MGBL

TTY-3-MEMORY

3 MGBL

TTY-3-MGMT_HOST_IP_ERROR

3 MGBL

TTY-3-MGMT_NO_ATTR

3 MGBL

TTY-3-MGMT_NO_FEATURE

3 MGBL

TTY-3-MGMT_NOT_ENOUGH_VALUES

3 MGBL

TTY-3-MGMT_TOO_MANY_VALUES

3 MGBL

TTY-3-MGMT_TTY_DETAILS_ERROR

3 MGBL

TTY-3-MGMT_UNEXPECTED

3 MGBL

TTY-3-OPEN_OR_DUP_DEVICE

3 MGBL

TTY-3-PACKET

3 MGBL

TTY-3-PHASE2_NON_FATAL

3 MGBL

TTY-3-SET_PROCESS_GROUP

3 MGBL

TTY-3-SYS_CALL_FAILED

3 MGBL

TTY-3-SYSDB

3 MGBL

TTY-3-SYSDB_BIND_ERROR

3 MGBL

TTY-3-SYSDB_UNBIND_ERROR

3 MGBL

TTY-3-VERIFYD_EXIT

3 MGBL

TTY-3-WAIT_ON_SIGNAL

3 MGBL

TTY-6-CONNECTION_DENY_ACL_ERROR

6 MGBL

TTY-6-FILE_OPER

6 MGBL

TTY-6-ISSU_NFN_REG

6 MGBL

TTY-6-PHASE2_RETRY

6 MGBL

TTY-6-SESSION_STARTUP

6 MGBL

TTY-6-SYSDB_INTERN

6 MGBL

TTY-7-CERRNO

7 MGBL

TTY-7-ISSU_LOAD_DONE

7 MGBL

TTY-7-ISSU_LOAD_EXEC

7 MGBL

TTY-7-MGMT_STATE

7 MGBL

TTY-7-MGMT_TTY_ATTR_EXTRACT_ERROR

7 MGBL

TTY-7-SESSION_STARTUP_OK

7 MGBL

TTY-7-TTY_INTERNAL

7 MGBL

VTY-2-PANIC

2 MGBL

VTY-3-DB

3 MGBL

VTY-3-MEM

3 MGBL

VTY-3-OPERATION

3 MGBL

VTY-3-POOL_APPLY_FAILURE

3 MGBL

VTY-3-REGISTRATION

3 MGBL

VTY-3-SESSION

3 MGBL

VTY-3-SYSDB

3 MGBL

VTY-3-SYSTEM_LIB_ERROR

3 MGBL

VTY-3-TTY_MANAGEMENT

3 MGBL

VTY-6-COMMAND_LINE_ARGS

6 MGBL

VTY-6-SYSDB_TIMEOUT_SET

6 MGBL

VTY-7-CONTROL

7 MGBL

VTY-7-DATA_PATH

7 MGBL

VTY-7-SYSDB_BULKING

7 MGBL

XML_INFRA-7-INIT_ERR

7 MGBL

XML_INFRA-7-INTERNAL

7 MGBL

XML_TTY-7-INTERNAL

7 MGBL

XML_TTY-7-LOGIN

7 MGBL

XML_TTY-7-SSLINIT

7 MGBL

XML_TTY-7-TRANSPORT

7 MGBL

action-3-BISTATE_MSG

3 OS

action-3-NONE_MSG

3 OS

action-3-PEG1MSG

3 OS

action-3-PEG2MSG

3 OS

action-3-RESET_MSG

3 OS

action-3-RESTART_MSG

3 OS

action-3-TESTMSG

3 OS

ALARM_TEST-3-ALARM_GENERATE

3 OS

ALLOCATOR-3-LTRACE_INIT_FAILED

3 OS

ALLOCATOR-7-LOCKING

7 OS

ALLOCATOR-7-MEMORY

7 OS

ALLOCATOR-7-NULL

7 OS

ALLOCATOR-7-SIZE_MISMATCH

7 OS

ARBMGR-4-INIT_ERROR

4 OS

ARBMGR-4-MBI_BOOT_HOLD

4 OS

ARBMGR-7-UNEXPECTED

7 OS

AVPAIR-6-ADD_FAIL

6 OS

AVPAIR-6-BUFFER_TOO_SMALL

6 OS

AVPAIR-6-ERR_BAD_AVLIST

6 OS

AVPAIR-6-ERR_BAD_LIST

6 OS

BANNER-3-CERR_REGISTER_FAILED

3 OS

BANNER-3-CONFIG_INIT_FAILED

3 OS

BANNER-3-EVENT_BLOCK_ERROR

3 OS

BANNER-3-EVENT_MGR_CREATE_FAILED

3 OS

BANNER-3-SYSMGR_CALL

3 OS

BANNER-7-SYSDB_BIND_FAILURE

7 OS

BANNER-7-SYSDB_REGISTRATION_FAILURE

7 OS

BANNER-7SYSDB_UNREGISTRATION_FAILURE

7 OS

BANNER-7-UNKNOWNCARD

7 OS

BCDL2-3-MSG_GENERIC_FUNC

3 OS

BCDL2-3-MSG_NULL_CONTEXT

3 OS

BCDL2-3-MSG_SEND_FAIL

3 OS

BCDL2-6-MSG_GENERIC_ERROR

6 OS

BCDL2-7-MSG_DECODE_FAIL

7 OS

BCDL-3-MSG_AGENT_USAGE

3 OS

BCDL-3-MSG_BASE_NAME

3 OS

BCDL-3-MSG_CERR_REGISTER_DLL

3 OS

BCDL-3-MSG_DEBUG_INIT

3 OS

BCDL-3-MSG_DEBUG_INIT

3 OS

BCDL-3-MSG_DEBUG_SERVICES

3 OS

BCDL-3-MSG_DEBUG_SERVICES

3 OS

BCDL-3-MSG_DLL_OPEN

3 OS

BCDL-3-MSG_DLSYM

3 OS

BCDL-3-MSG_DOUBLE_AGENT

3 OS

BCDL-3-MSG_EVENT

3 OS

BCDL-3-MSG_EVENT_MANAGER

3 OS

BCDL-3-MSG_GENERIC_FUNC

3 OS

BCDL-3-MSG_GENERIC_FUNC

3 OS

BCDL-3-MSG_GROUP

3 OS

BCDL-3-MSG_GROUP

3 OS

BCDL-3-MSG_GROUP_CREATE

3 OS

BCDL-3-MSG_GROUP_CREATE_LWG

3 OS

BCDL-3-MSG_GROUP_NODESET

3 OS

BCDL-3-MSG_GROUP_NODESET

3 OS

BCDL-3-MSG_HB_MISS

3 OS

BCDL-3-MSG_INSTALLMGR

3 OS

BCDL-3-MSG_LWM

3 OS

BCDL-3-MSG_MALLOC

3 OS

BCDL-3-MSG_MALLOC

3 OS

BCDL-3-MSG_PTHREAD

3 OS

BCDL-3-MSG_PTHREAD

3 OS

BCDL-3-MSG_RINFO

3 OS

BCDL-3-MSG_TABLE_REF_COUNT

3 OS

BCDL-7-MSG_CRIT_NORM

7 OS

BCDL-7-MSG_READ_STALL

7 OS

BCDL-7-MSG_STALL

7 OS

BCDL-7-MSG_STALL_RESET

7 OS

BCDLC-6-MSG_BCDL_THROTTLED

6 OS

BCDLC-6MSG_BCDL_UNINITIALIZED_ERROR

6 OS

BCDLC-6-MSG_GENERIC_ERROR

6 OS

BCDLC-6-MSG_GENERIC_FUNC

6 OS

BCDLPROD-3-MSG_SEND_FAIL

3 OS

BCDLPROD-6-MSG_GENERIC_ERROR

6 OS

BCDLPROD-6-MSG_GENERIC_FUNC

6 OS

BCDLTLV-6-MSG_GENERIC_ERROR

6 OS

BCDLTLV-6-MSG_GENERIC_FUNC

6 OS

BLWM-4-BATCH_CONFIG_REPLY_FAILED

4 OS

BLWM-4-BATCHED_REPLY_FAILED

4 OS

BLWM-4-PULSED_FLUSH_FAILED

4 OS

BLWM-4-REPLY_PROCESSING_ERRORS

4 OS

BLWM-4-RESTART_PROCESSING_ERRORS

4 OS

BLWM-4-SHMEM_FAILURE

4 OS

BLWM-4-TIMED_FLUSH_FAILED

4 OS

BLWM-4-WARNING

4 OS

CDS_CONSUMER_LIB-3-NULL_CONSUMER

3 OS

CDS_DB-3-CHAN_CONNECT

3 OS

CDS_DB-3-CLINFO_HOLD

3 OS

CDS_DB-3-CLINFO_UNHOLD

3 OS

CDS_DB-3-COMPARE_CLIENT

3 OS

CDS_DB-3-CONN_CONNID

3 OS

CDS_DB-3-GET_DATUM

3 OS

CDS_DB-3-GET_PROC_ROLE

3 OS

CDS_DB-3-MSG_REPLY

3 OS

CDS_DB-3-MUTEX_LOCK

3 OS

CDS_DB-3-MUTEX_UNLOCK

3 OS

CDS_DB-3-PROC_AVAILABLE

3 OS

CDS_DB-3-PROC_READY

3 OS

CDS_DB-3-PROC_ROLE_CHANGE

3 OS

CDS_DB-3-RWLOCK_DESTROY

3 OS

CDS_PRODUCER_LIB-3-MEMORY

3 OS

CDS_PRODUCER_LIB-3-SEND_FAILED

3 OS

cds_proxy-2-USAGE

2 OS

cds_proxy-3-CLINFO_HOLD

3 OS

cds_proxy-3-CLINFO_UNHOLD

3 OS

cds_proxy-3-EVENT_MANAGER_CREATE

3 OS

cds_proxy-3-GET_PROC_ROLE

3 OS

cds_proxy-3-INTERNAL

3 OS

cds_proxy-3-MEMORY

3 OS

cds_proxy-3-MUTEX_LOCK

3 OS

cds_proxy-3-MUTEX_UNLOCK

3 OS

cds_proxy-3-NULLARG

3 OS

cds_proxy-3-PROC_AVAILABLE

3 OS

cds_proxy-3-PROC_READY

3 OS

cds_proxy-3-PROC_ROLE_CHANGE

3 OS

cds_proxy-3-RWLOCK_DESTROY

3 OS

cds_svr-2-USAGE

2 OS

cds_svr-3-INTERNAL

3 OS

cds_svr-3-MEMORY

3 OS

CDSUTILS-3-LTRACE_INIT

3 OS

CDSUTILS-3-RING_INIT

3 OS

CDSUTILS-7-INTERNAL_ERROR

7 OS

CDSUTILS-7-INVALID_ARG

7 OS

CERR_LIB-7-CORRUPT

7 OS

CERR_LIB-7-NOMEM

7 OS

CERR_LIB-7-PTHREADKEY

7 OS

CERR_LIB-7-SETSPECIFIC

7 OS

CERR_LIB-7-SHM_OPEN_ERR

7 OS

CERR_SVR-7-EVENT

7 OS

CERR_SVR-7-INIT

7 OS

CERR_SVR-7-INSTALL

7 OS

CERR_SVR-7-SYSMGR

7 OS

CHUNK-3-CREATE

3 OS

CHUNK-3-INIT

3 OS

CHUNK-3-PRIVMEM_SIZE

3 OS

CHUNK-7-BADELESIZE

7 OS

CHUNK-7-BADREFCOUNT

7 OS

CHUNK-7-BOUNDS

7 OS

CHUNK-7-DESTROY_NOTEMPTY

7 OS

CHUNK-7-FREE

7 OS

CHUNK-7-INVFREE

7 OS

CHUNK-7-LOCK

7 OS

CHUNK-7-NEG_FREE_COUNT

7 OS

CHUNK-7-NOSIBLING

7 OS

CHUNK-7-NULLCHUNK

7 OS

CHUNK-7-PARTIAL

7 OS

CHUNK-7-SIB_INDEX

7 OS

DATACORRUPTION-1-DATAINCONSISTENCY

1 OS

DEBUG_CERR-7-REGISTER

7 OS

DEBUG_CERR-7-REGISTER

7 OS

deflate-3-output_dir_error

3 OS

deflate-3-output_error

3 OS

deflate-3-output_non_directory

3 OS

deflate-3-process_file_error

3 OS

DISTRIB_LIB-3-ASYNC_HANDLER_FAILED

3 OS

DISTRIB_LIB-3-BAD_CANCEL_TYPE

3 OS

DISTRIB_LIB-3-BAD_MSG_TYPE

3 OS

DISTRIB_LIB-3-BAD_REPLY

3 OS

DISTRIB_LIB-3-COND_OP_FAILED

3 OS

DISTRIB_LIB-3-CONNECT_FAILED

3 OS

DISTRIB_LIB-3-CONNECT_GSP_FAILED

3 OS

DISTRIB_LIB-3-CORRUPT_HEAP

3 OS

DISTRIB_LIB-3-CREATE_GROUP_FAILURE

3 OS

DISTRIB_LIB-3-DEF_SYNC_HANDLER_FAILED

3 OS

DISTRIB_LIB-3EVENT_ASYNC_ATTACH_FAILED

3 OS

DISTRIB_LIB-3-EVENT_FILE_ATTACH_FAILED

3 OS

DISTRIB_LIB-3-GSP_FAILURE

3 OS

DISTRIB_LIB-3-gsp_msg_failed

3 OS

DISTRIB_LIB-3-GSP_MSG_RCV_FAILURE

3 OS

DISTRIB_LIB-3-GSP_TRACE_BACK

3 OS

DISTRIB_LIB-3-HEAP_CORRUPT

3 OS

DISTRIB_LIB-3-INCORRECT_GROUP_ID

3 OS

DISTRIB_LIB-3-INIT_MEM_MANAGER_FAILED

3 OS

DISTRIB_LIB-3-MALLOC_FAILED

3 OS

DISTRIB_LIB-3MSG_CHAN_DISCONNECT_FAIL

3 OS

DISTRIB_LIB-3-MSG_GET_CONN_FAILED

3 OS

DISTRIB_LIB-3-MSG_Q_MUTEX_OP_FAILED

3 OS

DISTRIB_LIB-3-MSG_SEND_FAILURE

3 OS

DISTRIB_LIB-3-MUNMAP_FAILED

3 OS

DISTRIB_LIB-3-MUTEX_OP_FAILED

3 OS

DISTRIB_LIB-3-NO_PRIV_MSG_HANDLER

3 OS

DISTRIB_LIB-3-SYNC_RESP_FAILURE

3 OS

DISTRIB_LIB-6-BAD_SEQ_CHAN

6 OS

DISTRIB_LIB-6-GROUP_SEQ_INFO

6 OS

DISTRIB_LIB-6-GSP_TRACE_HDR

6 OS

DISTRIB_LIB-6-MEM_TRACE_BLOCK

6 OS

DISTRIB_LIB-7-FUNCTION_DEBUG

7 OS

DISTRIB_LIB-7INCORRECT_CBP_ACCESS_COUNT

7 OS

DUMPER_MARK-4-NO_SLOT

4 OS

DUMPER_MARK-7-NOT_FOUND

7 OS

DUMPER_SNAP-3-INSANE

3 OS

DUMPER_SNAP-4-DUMP

4 OS

DUMPER_SNAP-4-NODUMP

4 OS

DUMPER_SNAP-6-DUMP_OK

6 OS

DUMPER_SNAP-6-LIMITED

6 OS

DUMPER-3-CORE_FILE_TOO_SMALL

3 OS

DUMPER-3-DLOPEN_FAILED

3 OS

DUMPER-3-GET_MAPPING_INFO_FAILED

3 OS

DUMPER-3-MAP_INFO_FAILED

3 OS

DUMPER-3-NO_PLATFORM_DATA_FILE

3 OS

DUMPER-3-PATH_FAILED

3 OS

DUMPER-3-PLATFORM_DATA_FILE_ERROR

3 OS

DUMPER-3-SELECT_SEGMENTS_FAILED

3 OS

DUMPER-3-SET_RLIMIT_FAIL

3 OS

DUMPER-3-STACK_SIZE_INVALID

3 OS

DUMPER-3-THREAD_POOL_ERROR

3 OS

DUMPER-3-TIMER_PROBLEM

3 OS

DUMPER-3-WRONG_COMP_MAGIC_NUMBER

3 OS

DUMPER-4-BUS_ADRALN

4 OS

DUMPER-4-BUS_ADRERR

4 OS

DUMPER-4-BUS_OBJERR

4 OS

DUMPER-4-CORE_INFO

4 OS

DUMPER-4-CORE_PAGE_LOST

4 OS

DUMPER-4-CRASH_INFO

4 OS

DUMPER-4-DEVCTL_FAILED

4 OS

DUMPER-4-DLL_HANG

4 OS

DUMPER-4-ERR_MEM_ALIGN

4 OS

DUMPER-4-ERR_MEM_ALLOC

4 OS

DUMPER-4-ERR_PATHMGR_SYMLINK

4 OS

DUMPER-4-ERR_QSM_ADD_SERVICE

4 OS

DUMPER-4-ERR_SP_INVAL

4 OS

DUMPER-4-ERR_SYSDB_APPLY

4 OS

DUMPER-4-ERR_SYSDB_BIND

4 OS

DUMPER-4-ERR_SYSDB_GET

4 OS

DUMPER-4-ERR_SYSDB_NOTIFY

4 OS

DUMPER-4-ERR_SYSDB_REG_NOTIFY

4 OS

DUMPER-4-ERR_SYSDB_REG_VERIFY

4 OS

DUMPER-4-ERR_SYSDB_SET

4 OS

DUMPER-4-ERR_SYSDB_UNBIND

4 OS

DUMPER-4-ERR_SYSMGR_REG_LREVT

4 OS

DUMPER-4-ERR_SYSMGR_REG_REDST

4 OS

DUMPER-4-FLT_STACK

4 OS

DUMPER-4-MEMORY_PROTECT_FAILED

4 OS

DUMPER-4-PARITY_ERROR

4 OS

DUMPER-4PROCESS_OPTIONS_INIT_FAILURE

4 OS

DUMPER-4-SHOW_REGISTERS_FAILED

4 OS

DUMPER-4-SIGBUS_INFO

4 OS

DUMPER-4-SIGEMT

4 OS

DUMPER-4-SIGFPE_INFO

4 OS

DUMPER-4-SIGILL

4 OS

DUMPER-4-SIGNAL_NUMBER

4 OS

DUMPER-4-SIGNALCORE_INFO

4 OS

DUMPER-4-SIGSEGV

4 OS

DUMPER-4-SIGSEGV_INFO

4 OS

DUMPER-4-UNKNOWNCORE_INFO

4 OS

DUMPER-5-CORE_FILE_NAME

5 OS

DUMPER-5-CORE_TRANSFER_STATUS

5 OS

DUMPER-5-DUMP_FAILURE
DUMPER-5-DUMP_SUCCESS

5 OS
5 OS

DUMPER-5-LOCAL_PATH_FULL

5 OS

DUMPER-5-LTRACE_INIT

5 OS

DUMPER-5-TIMEOUT

5 OS

DUMPER-5-TMP_PATH_FULL

5 OS

DUMPER-6-BAD_PATH

6 OS

DUMPER-6-BOOT_DEVICE_FAILURE

6 OS

DUMPER-6-COMPRESS_OFF

6 OS

DUMPER-6-CORE_DUMP_OFF

6 OS

DUMPER-6-CORE_FILE_NAME_UNAVAIL

6 OS

DUMPER-6-CORE_FILE_OPEN_FAILED

6 OS

DUMPER-6-CORE_MD5

6 OS

DUMPER-6-COREDUMP_TIMEOUT_CANCEL

6 OS

DUMPER-6-CORRUPT_CONTEXT

6 OS

DUMPER-6-DEFAULT_PATH_TMP

6 OS

DUMPER-6-ERR_SYSMGR_CORE_OPTIONS

6 OS

DUMPER-6-FALLBACK_CHOICE

6 OS

DUMPER-6-FALLBACK_CHOICE_BOOT_DEV

6 OS

DUMPER-6-GET_PROC_CISCO

6 OS

DUMPER-6-GET_PROC_CURTHREAD_FAILED

6 OS

DUMPER-6-GET_PROC_GETGREG_FAILED

6 OS

DUMPER-6-GET_PROC_TIDSTATUS_FAILED

6 OS

DUMPER-6-GET_PROCINFO_FAILED

6 OS

DUMPER-6-MSGREPLY_CONFIRMED

6 OS

DUMPER-6-NO_SP_INFO

6 OS

DUMPER-6-NODE_NAME_FAIL

6 OS

DUMPER-6-NODEID_FAIL

6 OS

DUMPER-6-ONLY_CONTEXT

6 OS

DUMPER-6PENDING_SEGMENT_FLUSH_FAILED

6 OS

DUMPER-6-POPULATE_FILTERS_FAILED

6 OS

DUMPER-6-READ_TEXT_DUMP_FAIL

6 OS

DUMPER-6-REMOVE_OLDEST

6 OS

DUMPER-6-SAVE_SEGINFO_FAILED

6 OS

DUMPER-6-SCAN_DLLDATA_FAILED

6 OS

DUMPER-6-SCAN_PROCDATA_FAILED

6 OS

DUMPER-6-SCAN_REGISTERS_FAILED

6 OS

DUMPER-6-SCAN_STACK_FAILED

6 OS

DUMPER-6-SPARSE_CORE_DUMP

6 OS

DUMPER-6-SYSTEM_CALL_TIMEOUT

6 OS

DUMPER-6-TREEWALK_FAILED
DUMPER-6-UNLINK_CORE_FAILED

6 OS
6 OS

DUMPER-6-USAGE

6 OS

DUMPER-6-WORKER_THREAD_BUSY

6 OS

DUMPER-6-WRITE_TEXT_DUMP_FAIL

6 OS

DUMPER-7-BAD_CORE_SIZE

7 OS

DUMPER-7-CLOSE_PROBLEM

7 OS

DUMPER-7-CORE_CONFLICT

7 OS

DUMPER-7-DEBUG_INIT_FAILED

7 OS

DUMPER-7-DLL_INFO

7 OS

DUMPER-7-DLL_INFO_HEAD

7 OS

DUMPER-7-DUMP_ATTRIBUTE

7 OS

DUMPER-7-DUMP_CORE_FAILURE

7 OS

DUMPER-7-DUMP_INFO_PROBLEM

7 OS

DUMPER-7-DUMP_REQUEST

7 OS

DUMPER-7-ERR_EVM_CREATE

7 OS

DUMPER-7-ERR_EVM_EVENT_BLOCK

7 OS

DUMPER-7-ERR_EVM_FILE_ATTACH

7 OS

DUMPER-7-ERR_EVM_MSG_ATTACH

7 OS

DUMPER-7-ERR_SYSDB_DATALIST

7 OS

DUMPER-7-ERR_SYSDB_ITEM

7 OS

DUMPER-7-ERR_SYSDB_ITEM_TYPE

7 OS

DUMPER-7-ERR_THREAD_ATTRIBUTE

7 OS

DUMPER-7-ERR_THREAD_COND

7 OS

DUMPER-7-ERR_THREAD_CREATE

7 OS

DUMPER-7-ERR_THREAD_JOIN

7 OS

DUMPER-7-ERR_THREAD_MUTEX_DESTROY

7 OS

DUMPER-7-ERR_THREAD_MUTEX_INIT

7 OS

DUMPER-7-ERR_THREAD_MUTEX_LOCK

7 OS

DUMPER-7-ERR_THREAD_MUTEX_UNLOCK

7 OS

DUMPER-7-ERROR

7 OS

DUMPER-7-FAIL_DEBUG_REG

7 OS

DUMPER-7-FILE_TOO_SMALL

7 OS

DUMPER-7-FILE_VERSION_MISMATCH

7 OS

DUMPER-7-GET_FSLIST_FAILED

7 OS

DUMPER-7-GET_MAPINFO_FAILED

7 OS

DUMPER-7-GET_PAGEDATA_FAILED

7 OS

DUMPER-7-INSTALL_PKG

7 OS

DUMPER-7-INSTALL_PKG_SHOW_FAILED

7 OS

DUMPER-7-INVALID_PATH

7 OS

DUMPER-7-KERNEL_INFO_MMAP_FAILURE

7 OS

DUMPER-7-MKDIR_FAILED

7 OS

DUMPER-7-MMAP_FAILED

7 OS

DUMPER-7-MSGERROR_FAILED

7 OS

DUMPER-7-MSGREPLY_FAILED

7 OS

DUMPER-7-MUNMAP_FAILED

7 OS

DUMPER-7-NO_FREE_SPACE_INFO

7 OS

DUMPER-7-NO_OS_DEBUG_INFO

7 OS

DUMPER-7-OPEN_FAILED

7 OS

DUMPER-7-OS_DEBUG_INFO_MAP_FAILED

7 OS

DUMPER-7-PROC_OPEN_FAILED

7 OS

DUMPER-7-PROC_OPTION_INDEX_ERROR

7 OS

DUMPER-7-PROC_OPTIONS_CORRUPTED

7 OS

DUMPER-7-PROC_PAGES

7 OS

DUMPER-7-PROCESS_NAME_FAILED

7 OS

DUMPER-7-READ_FAILED

7 OS

DUMPER-7-REGISTERS_INFO

7 OS

DUMPER-7-REMOVE_LOWMEM

7 OS

DUMPER-7-SEEK_FAILED

7 OS

DUMPER-7-SKIP_CPU_INFO

7 OS

DUMPER-7-SYSMGR_CALL
DUMPER-7-TRACE_BACK

7 OS
7 OS

DUMPER-7-TRACE_BACK_ERROR

7 OS

DUMPER-7-TRACE_BACK_FAILED

7 OS

DUMPER-7-UNKNOWNCARD

7 OS

DUMPER-7-UNLINK_FAILED

7 OS

DUMPER-7-WRITE_FAILED

7 OS

EVM-1-CORRUPT_MLIST

1 OS

EVM-1-FLAGS

1 OS

EVM-1-QSM

1 OS

EVM-1-SIGPATCH

1 OS

EVM-1-TIMEOUT

1 OS

EVM-3-MUTEX_LOCK

3 OS

EVM-3-MUTEX_UNLOCK

3 OS

EVM-4-EMPTY_PATH

4 OS

EVM-4-FATTACH

4 OS

EVM-4-HANDLE

4 OS

EVM-4-IONOTIFY_FAIL

4 OS

EVM-4-RMCONTEXT

4 OS

EVM-4-SIGACTION

4 OS

EVM-4-SIGHEAP

4 OS

EVM-7-HEAP

7 OS

FCD-5-INIT_FAILED

5 OS

FILECOPY_LIB-3-BAGDECODE

3 OS

FILECOPY_LIB-3-BAGENCODE

3 OS

FILECOPY_LIB-3-NOMEM

3 OS

FILECOPY_LIB-3-NULLARGS

3 OS

FILECOPY_LIB-3-SYSDBFAIL

3 OS

FILECOPY-3-BAGREGFAILED

3 OS

FILECOPY-3-EVMCREATE

3 OS

FILECOPY-3-NOMEM

3 OS

FILECOPY-3-SIGATTACH

3 OS

FILECOPY-3-SYSDBBIND

3 OS

FILECOPY-4-DEBUGINIT

4 OS

FILECOPY-4-NOTIFFAIL

4 OS

FILECOPY-4-SYSDBUNBIND

4 OS

FLOWTRAP-3BAD_ACTOR_INTF_NOT_CLEARED

3 OS

FLOWTRAP-3BAD_ACTOR_MAC_NOT_CLEARED

3 OS

FLOWTRAP-3DISABLED_DANGLING_BAD_ACTORS

3 OS

FLOWTRAP-3-INIT

3 OS

FLOWTRAP-4-BAD_ACTOR_INTF_CLEARED

4 OS

FLOWTRAP-4-BAD_ACTOR_INTF_DELETED

4 OS

FLOWTRAP-4-BAD_ACTOR_INTF_DETECTED

4 OS

FLOWTRAP-4-BAD_ACTOR_INTF_DISABLED

4 OS

FLOWTRAP-4-BAD_ACTOR_MAC_CLEARED

4 OS

FLOWTRAP-4-BAD_ACTOR_MAC_DELETED

4 OS

FLOWTRAP-4-BAD_ACTOR_MAC_DETECTED

4 OS

FLOWTRAP-4-BAD_ACTOR_MAC_DISABLED

4 OS

FSM-4-ANOMALY

4 OS

GSP_C12000-7-info

7 OS

GSP_NOTIF-3-msg_failed

3 OS

gsp-3-BAD_GRP_DELETE

3 OS

gsp-3-CLIENT_LOCK_ISSUE

3 OS

gsp-3-CONDVAR_OP_FAILED

3 OS

gsp-3-ENS_INVALIDATE_HANDLE_FAILED

3 OS

gsp-3-FILE_OP_FAILED

3 OS

gsp-3-GET_MEM_FAILED

3 OS

gsp-3-INCORRECT_RSI

3 OS

gsp-3-LTRACE_INIT

3 OS

gsp-3-MSG_ENQUEUE_ISSUE

3 OS

gsp-3-MUTEX_OP_FAILED

3 OS

gsp-3-node_insert_fail

3 OS

gsp-3-PTHREAD_OP_FAILED

3 OS

gsp-3-script_failed

3 OS

gsp-3-SPURIOUS_NODE_DOWN

3 OS

gsp-3-TRACEBACK

3 OS

gsp-3-UPDATE_ADDR

3 OS

gsp-3-WRONG_FLOW

3 OS

gsp-4-ETH_BUILDUP

4 OS

gsp-4-FAB_BUILDUP

4 OS

gsp-4-MEM_CRITICAL

4 OS

gsp-6-INFO

6 OS

gsp-7-DEBUG

7 OS

gsp-7-ENS_MULTIPLE_PUBLISHERS

7 OS

gsp-7-FUNC_DEBUG

7 OS

gsp-7-MSG_QUEUE_LONG

7 OS

gsp-7-RCV_OWN_MSG

7 OS

gsp-7-script_spawn

7 OS

gsp-7-send_mcast_failed

7 OS

IMDR-2-ABORT

2 OS

IMDR-5-NSF_START

5 OS

IMDR-5-NSF_STOP

5 OS

INIT-2-MBI_BOOT_HOLD_TIMEOUT

2 OS

INIT-4-INSTALL_TIMEOUT

4 OS

INIT-7-INSTALL_READY

7 OS

INIT-7-INSTALL_THRESHOLD_EXCEEDED

7 OS

INIT-7-MBI_STARTED

7 OS

INIT-7-MBI_THRESHOLD_EXCEEDED

7 OS

IOSXRV_LIC_MGR-2-INIT_FAILED

2 OS

IOSXRV_LIC_MGR-3-EULA_ACCEPTED

3 OS

IOSXRV_LIC_MGR-3-LISTENER_ERROR

3 OS

IOSXRV_LIC_MGR-6-EVENT_ERR

6 OS

ISIS_MIB-3-ERR_ALLOC

3 OS

ISIS_MIB-3-ERR_BAG_DECODE

3 OS

ISIS_MIB-3-ERR_INIT

3 OS

ISIS_MIB-3-ERR_MAKE_VAR_BIND

3 OS

ITAL_SHM-3-ERR_RESOURCE

3 OS

ITAL_SHM-7-ERR_GENERAL

7 OS

ITAL_SHM-7-ERR_INIT

7 OS

ITAL_SHM-7-ERR_INIT_DEBUG

7 OS

ITAL-2-INIT_FAILURE

2 OS

ITAL-2-THREAD_LOCK_FAILURE

2 OS

ITAL-2-THREAD_UNLOCK_FAILURE

2 OS

ITAL-3-DEBUG_INIT_FAILURE

3 OS

ITAL-3-IF_NOTIF_FAILURE

3 OS

ITAL-3-MEM_ALLOC_FAILURE

3 OS

ITAL-5-UNSUPPORTED

5 OS

ITAL-7-ERR_RETRY

7 OS

ITAL-7-GENERAL_FAILURE

7 OS

ITAL-7-REG_FAILURE

7 OS

KD_MBUS-3-DEBUG_INIT_FAILED

3 OS

KD_MBUS-3-INIT_FAILED

3 OS

KD_MBUS-3-KDUMPER_FILE_FAILED

3 OS

KD_MBUS-3-KDUMPER_TRUNCATED

3 OS

KD_MBUS-3-OPEN_FAILED

3 OS

KD_MBUS-3-RC_FAILED

3 OS

KD_MBUS-3-READ_FAILED

3 OS

KD_MBUS-3-REOPEN_FAILED

3 OS

KD_MBUS-3-WRITE_FAILED

3 OS

KD_MBUS-6-FORCED_EXIT

6 OS

KD_MBUS-6-KDUMPER_FILE_INFO
KD_MBUS-6-KDUMPER_INFO

6 OS
6 OS

KD_MBUS-7-DEBUG_REG_FAILED

7 OS

LIB_VMAN-3-ACTIVATION_STATE

3 OS

LIB_VMAN-3-ALLOC_VIRT_INST_RCS

3 OS

LIB_VMAN-3-COMMIT_VIRT_INST_RCS

3 OS

LIB_VMAN-3-CPUSHARES_LIMIT

3 OS

LIB_VMAN-3-CPUTUNES_INTERNAL_ERROR

3 OS

LIB_VMAN-3-CPUTUNES_SHARES_LIMIT

3 OS

LIB_VMAN-3-CREATE_VIRT_INST_ENTRY

3 OS

LIB_VMAN-3-DEFER_VIRT_INST_PROC

3 OS

LIB_VMAN-3-DISK_IMAGE_PATH

3 OS

LIB_VMAN-3-FIND_VIRT_INST_ENTRY

3 OS

LIB_VMAN-3-GENERAL_FAILURE

3 OS

LIB_VMAN-3INCONSISTENT_CPUTUNES_CONFIG

3 OS

LIB_VMAN-3-INCONSISTENT_MEM_CONFIG

3 OS

LIB_VMAN-3-INSERT_VIRT_INST_ENTRY

3 OS

LIB_VMAN-3-INSTALL_FAILURE

3 OS

LIB_VMAN-3-INSTALL_MEDIA_RETRY

3 OS

LIB_VMAN-3-INSTALL_STATE

3 OS

LIB_VMAN-3-INVALID_ACT_MSG

3 OS

LIB_VMAN-3-INVALID_DEACT_MSG

3 OS

LIB_VMAN-3-INVALID_PACKAGE

3 OS

LIB_VMAN-3-INVALID_UNPROV_MSG

3 OS

LIB_VMAN-3-MACH_PARSE_FAILURE

3 OS

LIB_VMAN-3MACHINE_TYPE_NOT_SUPPORTED

3 OS

LIB_VMAN-3-MEMORY_LIMIT

3 OS

LIB_VMAN-3-MEMORY_LIMIT_WARN

3 OS

LIB_VMAN-3MORETHANONE_CPUTUNES_CONFIG

3 OS

LIB_VMAN-3-NETWORK_CONFIG_ERROR

3 OS

LIB_VMAN-3-PROC_INT_LIST

3 OS

LIB_VMAN-3-PROCESS_PKG_DEF

3 OS

LIB_VMAN-3-PSS_ERR

3 OS

LIB_VMAN-3-PSS_SNAPSHOT_ERR

3 OS

LIB_VMAN-3-REMOVE_VIRT_INST_ENTRY

3 OS

LIB_VMAN-3-SDWRAP_ERR

3 OS

LIB_VMAN-3-SET_VTX_ROMVAR_SPACE

3 OS

LIB_VMAN-3-SET_VTX_ROMVAR_STRING

3 OS

LIB_VMAN-3-START_FAILED

3 OS

LIB_VMAN-3-VCPU_INVALID

3 OS

LIB_VMAN-3-VCPU_LIMIT

3 OS

LIB_VMAN-3-VIRT_INST_DISK

3 OS

LIB_VMAN-3-VIRT_INST_INTERFACE

3 OS

LIB_VMAN-3-VIRT_INST_MEMORY

3 OS

LIB_VMAN-3-VIRT_INST_MGMT_INTERFACE

3 OS

LIB_VMAN-3-VIRT_INST_STATE

3 OS

LIB_VMAN-5-AUX

5 OS

LIB_VMAN-5-UNSIGNED_PACKAGE

5 OS

LIB_VMAN-5-VIRT_INST

5 OS

LIBDLLMGR-4-OVERFLOW_DELETE

4 OS

LIBDLLMGR-4-POSSIBLE_MISSING_INFO

4 OS

LIBDLLMGR-4-SYSCALL

4 OS

LIBDLLMGR-4-UNEXPECTED_ARRAY_ADDR

4 OS

LIBDLLMGR-4-UNEXPECTED_MAGIC

4 OS

LIBDLLMGR-6-OVERFLOW_REPLACE

6 OS

LIBDLLMGR-7-OVERFLOW

7 OS

LIBDLLMGR-7-UNEXPECTED

7 OS

LIBSYSMGR-3-ALREADY_CALLED

3 OS

LIBSYSMGR-3-ALREADY_CALLED

3 OS

LIBSYSMGR-3-INST_ERR

3 OS

LIBSYSMGR-3-INST_ERR

3 OS

LIBSYSMGR-3-INTERNAL

3 OS

LIBSYSMGR-3-INTERNAL

3 OS

LIBSYSMGR-3-INVALID_ARG

3 OS

LIBSYSMGR-3-INVALID_ARG

3 OS

LIBSYSMGR-3-NOMEM

3 OS

LIBSYSMGR-3-NOMEM

3 OS

LIBSYSMGR-3-PARSE

3 OS

LIBSYSMGR-3-PARSE

3 OS

LIBSYSMGR-3-SYSCALL

3 OS

LIBSYSMGR-3-SYSCALL

3 OS

LIBSYSMGR-6-INFO

6 OS

LIBSYSMGR-6-INFO

6 OS

LIBSYSMGR-6-SCRIPT_TIMEOUT

6 OS

LIBSYSMGR-6-SCRIPT_TIMEOUT

6 OS

LIBSYSMGR-7-ERR

7 OS

LIBSYSMGR-7-ERR

7 OS

LPTS_LIB-7-DEBUG_CLEANUP

7 OS

LPTS_LIB-7-DEBUG_INIT_EVENT

7 OS

LPTS_LIB-7-DEBUG_REGISTER

7 OS

LPTS_MRT-7-DEBUG_CLEANUP

7 OS

LPTS_MRT-7-DEBUG_INIT_EVENT

7 OS

LPTS_MRT-7-DEBUG_REGISTER

7 OS

LPTS_NPMB-3-BAD_LISTENER_TAG

3 OS

LPTS_NPMB-3-NETWORK_START_FAIL

3 OS

LPTS_NPMB-6PROCESS_INGRESS_BUFFHDR_FAILED

6 OS

LPTS_PA_FF_CL-7-DEBUG_INIT_EVENT

7 OS

LPTS_PA_FF_CL-7-DEBUG_REGISTER

7 OS

LPTS_PA_FF-3-EVENT_UPDATE_FAIL

3 OS

LPTS_PA_FF-3-EVM_CREATE

3 OS

LPTS_PA_FF-3-INIT_FAILED

3 OS

LPTS_PA_FF-3-MALLOC

3 OS

LPTS_PA_FF-3-TLVLIB_INIT

3 OS

LPTS_PA_FF-4-CLIENT_NOT_FOUND

4 OS

LPTS_PA_FF-4-EVENT_BLOCK

4 OS

LPTS_PA_FF-4-EVENT_INIT_EVENT

4 OS

LPTS_PA_FF-4-EVM_ASYNC_ATTACH

4 OS

LPTS_PA_FF-4-GET_NODEID

4 OS

LPTS_PA_FF-4-LRD_FAIL

4 OS

LPTS_PA_FF-4-MSG_ATTACH_SYNC

4 OS

LPTS_PA_FF-4-MSG_CLINFO_GET_DATUM

4 OS

LPTS_PA_FF-4-MSG_SEND_EVENT

4 OS

LPTS_PA_FF-4-TIMER_CREATE

4 OS

LPTS_PA_FF-4-TIMER_SETTIME

4 OS

LPTS_PIFIB-7-DEBUG_CLEANUP

7 OS

LPTS_PIFIB-7-DEBUG_INIT_EVENT

7 OS

LPTS_PIFIB-7-DEBUG_REGISTER

7 OS

LPTS_PREIFIB-3-BACKEND_EDM

3 OS

LPTS_PREIFIB-3-DATAPATH_CMD

3 OS

LPTS_PREIFIB-3-EDM_UNREG

3 OS

LPTS_PREIFIB-3-EVENT_BLOCK

3 OS

LPTS_PREIFIB-3-EVENT_CONN_CREATE

3 OS

LPTS_PREIFIB-3-EVENT_CONN_NOTIFY

3 OS

LPTS_PREIFIB-3IM_CAPS_DATAPATH_CONTROL

3 OS

LPTS_PREIFIB-3-INVALID_ARGS

3 OS

LPTS_PREIFIB-3-MSG_CHAN_GLOBAL

3 OS

LPTS_PREIFIB-3-PIFIBM_INIT

3 OS

LPTS_PREIFIB-3-REASS_LIST

3 OS

LPTS_PREIFIB-4-BAG_FAIL

4 OS

LPTS_PREIFIB-4-BATCHING

4 OS

LPTS_PREIFIB-4-BLC_UPDATE

4 OS

LPTS_PREIFIB-4-ENTRY_UPDATE

4 OS

LPTS_PREIFIB-4-EVENT_CONN_OPEN_ALL

4 OS

LPTS_PREIFIB-4-EVM_CREATE

4 OS

LPTS_PREIFIB-4-EVM_TM_ATTACH

4 OS

LPTS_PREIFIB-4-EVM_TM_LEAF_NEW

4 OS

LPTS_PREIFIB-4-HW_RETRY

4 OS

LPTS_PREIFIB-4-IIR_QUERY

4 OS

LPTS_PREIFIB-4-LRD_FAIL

4 OS

LPTS_PREIFIB-4-NOMEM

4 OS

LPTS_PREIFIB-4-SYSDB

4 OS

LPTS_PREIFIB-4-TLVLIB_INIT

4 OS

LPTS_PREIFIB-4-VRF_UPDATE

4 OS

LPTS_PREIFIB-5-INVALID_FLOW_TYPE

5 OS

LPTS_PREIFIB-6-NETIO_DOWN

6 OS

LPTS_PREIFIB-6-NETIO_UP

6 OS

LPTS_PREIFIB-6-PA_FF_OPEN

6 OS

LPTS_PREIFIB-6-PA_FF_RESET

6 OS

LPTS_PREIFIB-6-PA_UPDATE

6 OS

LPTS_PREIFIB-6-PARSE_INFLOW_CONFIG

6 OS

LPTS_PREIFIB-6-SYSMGR_PROC_READY

6 OS

LPTS_PREIFIB-7-DEBUG_CLEANUP

7 OS

LPTS_PREIFIB-7-DEBUG_INIT_EVENT

7 OS

LPTS_PREIFIB-7-DEBUG_REGISTER

7 OS

LPTS_PREIFIB-7-LTRACE_INIT

7 OS

LPTS-3-BAD_LISTENER_TAG

3 OS

LPTS-3-BAG_ENCODE_FAILED

3 OS

LPTS-3-BAG_REG_FAILED

3 OS

LPTS-3-ECM_CREATE_FAIL

3 OS

LPTS-3-ECM_OPEN_FAIL

3 OS

LPTS-3-EDM_DATALIST_ADD_FAILED

3 OS

LPTS-3-EDM_DATALIST_CREATE_FAILED

3 OS

LPTS-3-EDM_REG_FAILED

3 OS

LPTS-3-EVM_CREATE_FAIL

3 OS

LPTS-3-HSSD_GET_DATA_FAILED

3 OS

LPTS-3-INVALID_ARGS

3 OS

LPTS-3-NETWORK_START_FAIL

3 OS

LPTS-3-NULL_TRANSPORT_CALLBACK

3 OS

LPTS-3-PA_CONN_FAIL

3 OS

LPTS-3-PAK_DUP

3 OS

LPTS-4-DATAPATH_INPUT_LEN

4 OS

LPTS-4-FINT_MEDIA_REG_FAILED

4 OS

LPTS-4-HSSD_FAILED

4 OS

LPTS-4-IFIB_FAILED

4 OS

LPTS-4-IFIB_RES_ALLOC_FAILED

4 OS

LPTS-4-LTRACE_INIT_FAIL

4 OS

LPTS-4-NULL_FINT_IDB

4 OS

LPTS-4-PA_CLOSE_FAIL

4 OS

LPTS-4-PAK_NETIO_MUTEX_LOCK_FAILED

4 OS

LPTS-4-PAK_NETIO_MUTEX_UNLOCK_FAILED

4 OS

LPTS-4-PAK_NETIO_UINT8_GET

4 OS

LPTS-4-PLATFORM_GET_MY_NODEID_FAILED

4 OS

LPTS-4-PUNT_FAIL

4 OS

LPTS-6-IFIB_RES_SET_FAILED

6 OS

LPTS-6-INFO_GENERAL

6 OS

LPTS-6-INFO_INTERNAL_TABLE

6 OS

LPTS-6-MALLOC_FAILED

6 OS

LPTS-6-PAK_NETIO_RETURN_BUFFER

6 OS

LPTS-6-PREPARE_EGRESS_BUFFHDR_FAILED

6 OS

LPTS-6PROCESS_INGRESS_BUFFHDR_FAILED

6 OS

LPTS-6-SYSDB_CONN_TO_COID_FAILED

6 OS

LPTS-6-SYSDB_NS_NODE_TO_STR_FAILED

6 OS

LPTS-7-DEBUG_REGISTER_FAIL

7 OS

LPTS-7-NETIO_DEBUG_INIT

7 OS

LTRACE_CONFIG-3-ERR_MUTEX_INIT

3 OS

LTRACE_CONFIG-3-ERR_MUTEX_LOCK

3 OS

LTRACE_CONFIG-3-ERR_MUTEX_UNLOCK

3 OS

LTRACE_CONFIG-3-ERR_TUPLE_UNPACK

3 OS

LTRACE_CONFIG-3-EXTERNAL_API_ERROR

3 OS

LTRACE_CONFIG-3-NODE_NAME_FAIL

3 OS

LTRACE_CONFIG-4-ERR_CHAN_CON

4 OS

LTRACE_CONFIG-4-ERR_EVENT_CREATE

4 OS

LTRACE_CONFIG-4-ERR_EVENT_NOTIFY

4 OS

LTRACE_CONFIG-4-ERR_EVENT_OPEN

4 OS

LTRACE_CONFIG-4-ERR_EXTRACT_FIELDS
LTRACE_CONFIG-4-ERR_MEM_ALLOC

4 OS
4 OS

LTRACE_CONFIG-4-ERR_NODE_VALIDATE

4 OS

LTRACE_CONFIG-4-ERR_OPEN_DIR

4 OS

LTRACE_CONFIG-4-ERR_SEND_MSG

4 OS

LTRACE_CONFIG-4-ERR_SYSDB_BIND

4 OS

LTRACE_CONFIG-4-ERR_SYSDB_REG_VERIFY

4 OS

LTRACE_CONFIG-4-LTRACE_INIT_ERROR

4 OS

LTRACE_CONFIG-7-ERR_CHAN_CON

7 OS

LTRACE_CONFIG-7-ERR_EVENT_CREATE

7 OS

LTRACE_CONFIG-7-ERR_EVENT_NOTIFY

7 OS

LTRACE_CONFIG-7-ERR_EVENT_OPEN

7 OS

LTRACE_CONFIG-7-ERR_EXTRACT_FIELDS
LTRACE_CONFIG-7-ERR_MEM_ALLOC

7 OS
7 OS

LTRACE_CONFIG-7-ERR_MUTEX_DESTROY

7 OS

LTRACE_CONFIG-7-ERR_MUTEX_DESTROY

7 OS

LTRACE_CONFIG-7-ERR_MUTEX_INIT

7 OS

LTRACE_CONFIG-7-ERR_MUTEX_LOCK

7 OS

LTRACE_CONFIG-7-ERR_MUTEX_UNLOCK

7 OS

LTRACE_CONFIG-7-ERR_NODE_VALIDATE

7 OS

LTRACE_CONFIG-7-ERR_OPEN_DIR

7 OS

LTRACE_CONFIG-7-ERR_SEND_MSG

7 OS

LTRACE_CONFIG-7-ERR_SYSDB_BIND

7 OS

LTRACE_CONFIG-7-ERR_SYSDB_REG_VERIFY

7 OS

LTRACE_CONFIG-7-ERR_TUPLE_UNPACK

7 OS

LTRACE_CONFIG-7-EXTERNAL_API_ERROR

7 OS

LTRACE_CONFIG-7-LTRACE_INIT_ERROR

7 OS

LTRACE_CONFIG-7-NODE_NAME_FAIL

7 OS

LTRACE_SDT_SHOW-4-EXTEND_FAIL

4 OS

LTRACE_SDT_SHOW-4-GROUP_CALLOC

4 OS

LTRACE_SDT_SHOW-4-NODE_PRINT

4 OS

LTRACE_SDT_SHOW-4-STR_CALLOC

4 OS

LTRACE_SDT_SHOW-4-STR_SEQ

4 OS

LTRACE_SDT_SHOW-4-TRACE_FIND

4 OS

LTRACE_SDT_SHOW-4-TRACE_INSERT

4 OS

LTRACE_SDT_SHOW-7-EXTEND_FAIL

7 OS

LTRACE_SDT_SHOW-7-GROUP_CALLOC

7 OS

LTRACE_SDT_SHOW-7-NODE_PRINT

7 OS

LTRACE_SDT_SHOW-7-STR_CALLOC

7 OS

LTRACE_SDT_SHOW-7-STR_SEQ

7 OS

LTRACE_SDT_SHOW-7-TRACE_FIND

7 OS

LTRACE_SDT_SHOW-7-TRACE_INSERT

7 OS

LTRACE_SDT-4-BTREE_FIND

4 OS

LTRACE_SDT-4-BTREE_INSERT

4 OS

LTRACE_SDT-7-BTREE_FIND

7 OS

LTRACE_SDT-7-BTREE_INSERT

7 OS

LTRACE_SERVER-3-CFG_THR_INIT_ERR

3 OS

LTRACE_SERVER-3-ERR_ATTR_DETACH

3 OS

LTRACE_SERVER-3-ERR_ATTR_INIT

3 OS

LTRACE_SERVER-3-EXTERNAL_API_ERROR

3 OS

LTRACE_SERVER-3-NODE_NAME_FAIL

3 OS

LTRACE_SERVER-7-CFG_THR_INIT_ERR

7 OS

LTRACE_SERVER-7-ERR_ATTR_DETACH

7 OS

LTRACE_SERVER-7-ERR_ATTR_INIT

7 OS

LTRACE_SERVER-7-EXTERNAL_API_ERROR

7 OS

LTRACE_SERVER-7-NODE_NAME_FAIL

7 OS

LTRACE_SYNC-3-EXTERNAL_API_ERROR

3 OS

LTRACE_SYNC-3-FILE_BAD_MAGIC

3 OS

LTRACE_SYNC-3-MEMORY_UNMAP_ERROR

3 OS

LTRACE_SYNC-3-PTHREAD_API_ERROR

3 OS

LTRACE_SYNC-3-RWLOCK_ERROR

3 OS

LTRACE_SYNC-4-FILE_SIZE_CHANGE

4 OS

LTRACE_SYNC-4-LTRACE_INIT_ERROR

4 OS

LTRACE_SYNC-4-MEMORY_MAP_ERROR

4 OS

LTRACE_SYNC-4-SHMEM_ERROR

4 OS

LTRACE_SYNC-6-FILE_TOO_SHORT

6 OS

LTRACE_SYNC-6-FILE_WRONG_VERSION

6 OS

LTRACE_SYNC-7-EXTERNAL_API_ERROR

7 OS

LTRACE_SYNC-7-FILE_BAD_MAGIC

7 OS

LTRACE_SYNC-7-FILE_SIZE_CHANGE

7 OS

LTRACE_SYNC-7-FILE_TOO_SHORT

7 OS

LTRACE_SYNC-7-FILE_WRONG_VERSION

7 OS

LTRACE_SYNC-7-LTRACE_INIT_ERROR

7 OS

LTRACE_SYNC-7-MEMORY_MAP_ERROR

7 OS

LTRACE_SYNC-7-MEMORY_UNMAP_ERROR

7 OS

LTRACE_SYNC-7-PTHREAD_API_ERROR

7 OS

LTRACE_SYNC-7-RWLOCK_ERROR

7 OS

LTRACE_SYNC-7-SHMEM_ERROR

7 OS

LTRACE-3-ERROR

3 OS

LTRACE-3-FTRUNCATE_ERROR

3 OS

LTRACE-3-MMAP_ERROR

3 OS

LTRACE-3-MUTEXINIT_ERROR

3 OS

LTRACE-3-OPEN_ERROR

3 OS

LTRACE-7-BADMAGIC

7 OS

LTRACE-7-BLK_BADMAGIC

7 OS

LTRACE-7-CTRL_BADMAGIC
LTRACE-7-DEBUG
LTRACE-7-DEBUG

7 OS
7 OS
7 OS

LTRACE-7-ERROR

7 OS

LTRACE-7-FTRUNCATE_ERROR

7 OS

LTRACE-7-MMAP_ERROR

7 OS

LTRACE-7-MUTEXINIT_ERROR

7 OS

LTRACE-7-OPEN_ERROR

7 OS

LTRACE-7-STRING_SCALE

7 OS

LTRACE-7-STRING_SCALE

7 OS

LTRACE-7-UNLINK_ERROR

7 OS

LTRACE-7-WRAP_SCALE

7 OS

LTRACE-7-WRAP_SCALE

7 OS

LWMESS-7-CORRUPT_CLI

7 OS

LWMESS-7-CORRUPT_CLI

7 OS

LWMESS-7-CORRUPT_CLI_SKIP

7 OS

LWMESS-7-CORRUPT_CLI_SKIP

7 OS

LWMESS-7-INVALID_MSG_ERROR_CODE

7 OS

LWMESS-7-INVALID_MSG_ERROR_CODE

7 OS

LWMESS-7-LOCK_CONN

7 OS

LWMESS-7-LOCK_CONN

7 OS

LWMESS-7-UNLOCK_CONN

7 OS

LWMESS-7-UNLOCK_CONN

7 OS

MEMLOG-3-ERRCHECK

3 OS

MEMLOG-3-FREE

3 OS

MEMLOG-3-HEADER

3 OS

MEMLOG-3-MALLOC

3 OS

MEMLOG-3-MEMALIGN

3 OS

MEMLOG-3-SIGERR

3 OS

MEMLOG-3-TOOBIG

3 OS

MEMPOOL_EDM-1-EVENT_BLOCK_ERROR

1 OS

MEMPOOL_EDM-1SYSDB_REGISTRATION_FAILURE

1 OS

MEMPOOL_EDM-3-MALLOC_FAILED

3 OS

MEMPOOL_EDM-3-SYSDB_BIND_FAILURE

3 OS

MGII_API-3-INFRA_FAIL

3 OS

MMAP_PEER-3-MMAP

3 OS

MMAP_PEER-3-MUNMAP

3 OS

MMAP_PEER-3-READLINK

3 OS

MMAP_PEER-3-RECV_SIZE

3 OS

MMAP_PEER-3-SHM_OPEN

3 OS

MMAP_PEER-6-CONNECT

6 OS

MMAP_PEER-6-RECV

6 OS

MMAP_PEER-6-SEND

6 OS

MMAP_PEER-7-DEBUG

7 OS

MPLS_VPN_MIB-3-ERR_DLL_LOAD

3 OS

MPLS_VPN_MIB-3-ERR_DLL_SYMBOL_ERROR

3 OS

MPLS_VPN_MIB-3-ERR_INIT

3 OS

MPLS_VPN_MIB-3-ERR_TRACE_INIT

3 OS

NCD-3-INIT_FAIL

3 OS

NCD-3-PAK_CSUM_MISMATCH

3 OS

NPL-3-PAK_CSUM_MISMATCH

3 OS

NPL-3-PAK_OPERATION_FAIL

3 OS

NQC-3-ISOLATION_FAILED

3 OS

NQC-3-PAK_CSUM_MISMATCH

3 OS

NQC-3-PAK_OPERATION_FAIL

3 OS

NQC-6-ISOLATION_NOTSUP

6 OS

NRS_LIB-7-ERROR

7 OS

NRS_LIB-7-REG_ERROR

7 OS

nrs-2-USAGE

2 OS

nrs-3-CHKPT_ATTR_CREATE

3 OS

nrs-3-CHKPT_ATTR_SAVE

3 OS

nrs-3-CHKPT_CREATE

3 OS

nrs-3-CHKPT_DEBUG

3 OS

nrs-3-CHKPT_DELETE_BYKEY

3 OS

nrs-3-CHKPT_ITERATE

3 OS

nrs-3-CHKPT_ITERATE_NEXT

3 OS

nrs-3-CHKPT_REGISTER

3 OS

nrs-3-CHKPT_RESTORE_ATTR

3 OS

nrs-3-CHKPT_RESTORE_CLASS

3 OS

nrs-3-CHKPT_RESTORE_DATA

3 OS

nrs-3-CHKPT_RESTORE_DEBUG

3 OS

nrs-3-CHKPT_RESTORE_DEBUG_SUCCESS

3 OS

nrs-3-CHKPT_RESTORE_SET

3 OS

nrs-3-CHKPT_SAVE

3 OS

nrs-3-CHKPT_UNREGISTER

3 OS

nrs-3-ENS_PUBLISH

3 OS

nrs-3-ENS_WRITE

3 OS

nrs-3-EVENT_MESSAGE_ATTACH_ERR

3 OS

nrs-3-INIT

3 OS

nrs-3-INTERNAL

3 OS

nrs-3-LOCKING

3 OS

nrs-3-MEMORY

3 OS

nrs-3-MSG_REPLY_ERR

3 OS

nrs-3-NULLARG

3 OS

nrs-3-REGCOMP

3 OS

nrs-3REGISTER_EXTERNAL_PUBLISH_DIFF_ID

3 OS

nrs-3-REPLY

3 OS

nrs-3-SHUTDOWN

3 OS

nrs-7-EDM_INTERNAL

7 OS

nrs-7-LTRACE_INIT

7 OS

NRSUTILS-3-INTERNAL

3 OS

NRSUTILS-3-MEMORY

3 OS

NRSUTILS-3-NULLARG

3 OS

OBFLINFRA_CLI-3-NO_MEMORY

3 OS

OBFLINFRA_CLI-7-FAIL_TO_GET_SDD

7 OS

OBFLINFRA_CLI-7-FILE_GARBAGE

7 OS

OBFLINFRA_CLI-7invalid_historical_file_format

7 OS

OBFLINFRA_CLI-7-INVALID_RECORD_TYPE

7 OS

OBFLINFRA_CLI-7-JID_GET_ERROR

7 OS

OBFLINFRA_CLI-7STRING_LENGTH_TOO_LONG

7 OS

OBFLINFRA_CLI-7-SYMBOL_NOT_FOUND

7 OS

OBFLINFRA_CLI-7UNABLE_TO_GET_NODENAME

7 OS

OBFLINFRA_CLIENT-7-APPLICATION_ERROR

7 OS

OBFLINFRA_CLIENT-7APPLICATION_REGIST_ERROR

7 OS

OBFLINFRA_CLIENT-7-ID_INVALID

7 OS

OBFLINFRA_CLIENT-7-JID_GET_ERROR

7 OS

OBFLINFRA_CLIENT-7-NO_MEMORY

7 OS

OBFLINFRA_CLIENT-7-NODEID_FAILURE

7 OS

OBFLINFRA_CLIENT-7NUM_OF_SENSORS_OVERFLOW

7 OS

OBFLINFRA_CLIENT-7-SENSOR_NOT_FOUND

7 OS

OBFLINFRA_CLIENT-7TOO_LONG_FEATURE_NAME

7 OS

OBFLINFRA_DRIVER-3-JID_GET_ERROR

3 OS

OBFLINFRA_DRIVER-7-NODEID_FAILURE

7 OS

OBFLINFRA_DRIVER-7TOO_LONG_DEVICE_NAME

7 OS

OBFLINFRA_INT-3-EVM_ERROR

3 OS

OBFLINFRA_INT-3INVALID_RECORD_MAGIC_NUM

3 OS

OBFLINFRA_INT-3-MSG_ERROR

3 OS

OBFLINFRA_INT-3-NO_MEMORY

3 OS

OBFLINFRA_INT-3-NO_PLATFORM_DATA_FILE

3 OS

OBFLINFRA_INT-3-NO_SERVER_FOUND

3 OS

OBFLINFRA_INT-3-NODEID_FAILURE

3 OS

OBFLINFRA_INT-3-NODEID_GET_FAILURE

3 OS

OBFLINFRA_INT-3PLATFORM_DATA_FILE_ERROR

3 OS

OBFLINFRA_INT-3-PTHREAD_ERROR

3 OS

OBFLINFRA_INT-3-RECORD_TOO_SHORT

3 OS

OBFLINFRA_INT-3-RECORD_TYPE_MISMATCH

3 OS

OBFLINFRA_INT-3RECORD_VERSION_MISMATCH

3 OS

OBFLINFRA_INT-3-SYSCALL

3 OS

OBFLINFRA_INT-3-TIMER_ERROR

3 OS

OBFLINFRA_INT-4-JID_GET_ERROR

4 OS

OBFLINFRA_INT-4-MSG_RESEND_ERROR

4 OS

OBFLINFRA_INT-4-UNSUPPORTED_API

4 OS

OBFLINFRA_INT-5MSG_CKSUM_DATA_ERROR

5 OS

OBFLINFRA_INT-5MSG_CKSUM_HDR_ERROR

5 OS

OBFLINFRA_INT-5-MSG_REPLY_ERROR

5 OS

OBFLINFRA_INT-6-EXIT

6 OS

OBFLINFRA_INT-7-BUFFER_GARBAGE

7 OS

OBFLINFRA_INT-7-DEBUG_CONNECT

7 OS

OBFLINFRA_INT-7-DEBUG_QSM

7 OS

OBFLINFRA_INT-7-DEBUG_SENDV

7 OS

OBFLINFRA_INT-7-FILE_ERROR

7 OS

OBFLINFRA_INT-7-RECORD_TOO_LONG

7 OS

OBFLINFRA_INT-7-SLOT_DECODE_FAILURE

7 OS

OBFLINFRA_INT-7-TOO_LONG_NAME

7 OS

OBFLMGR-3-CHECKSUM_ERROR

3 OS

OBFLMGR-3-ENV_STATIC_DATA_ERROR

3 OS

OBFLMGR-3EVENT_CONN_CREATION_ERROR

3 OS

OBFLMGR-3-EVENT_CONN_NOTIFY_ERROR

3 OS

OBFLMGR-3-EVENT_CONN_OPEN_ERROR

3 OS

OBFLMGR-3-EVENT_TIMER_ERROR

3 OS

OBFLMGR-3-EVM_ERROR

3 OS

OBFLMGR-3-FILE_SIZE_GET_FAILURE

3 OS

OBFLMGR-3-FILELIMIT_TOO_SMALL

3 OS

OBFLMGR-3-HISTGROUP_TOO_LARGE

3 OS

OBFLMGR-3-LWM_ERROR

3 OS

OBFLMGR-3-MSG_VER_MISMATCH

3 OS

OBFLMGR-3-MUTEX_RESET_ERROR

3 OS

OBFLMGR-3-NO_FINAL_CLEAR_RECORD

3 OS

OBFLMGR-3-RECORD_LENGTH_UNMATCH

3 OS

OBFLMGR-3-RECORD_TOO_SHORT

3 OS

OBFLMGR-3-RECORD_VERSION_MISMATCH

3 OS

OBFLMGR-3-REDUNDANCY_INIT_ERROR

3 OS

OBFLMGR-3-SM_CALLBACK_ERROR

3 OS

OBFLMGR-3-SYMBOL_NOT_FOUND

3 OS

OBFLMGR-3-SYSDB_BIND_ERROR

3 OS

OBFLMGR-3-SYSDB_EDM_INIT_ERROR

3 OS

OBFLMGR-3-SYSDB_REG_EDM_ERROR

3 OS

OBFLMGR-3-SYSDB_REG_NOTIFY_ERROR

3 OS

OBFLMGR-3-SYSDB_REG_VERIFY_ERROR

3 OS

OBFLMGR-3-THREAD_POOL_ERROR

3 OS

OBFLMGR-3-UNLOAD_DLL_FAILED

3 OS

OBFLMGR-4-CLI_MSG_ERROR

4 OS

OBFLMGR-4-CLIENTID_ERROR

4 OS

OBFLMGR-4-DEVCTL_ERROR

4 OS

OBFLMGR-4DEVICE_CREATED_AND_DISABLED

4 OS

OBFLMGR-4-DEVICE_DEACTIVATED

4 OS

OBFLMGR-4-DEVICE_DISABLED

4 OS

OBFLMGR-4-FEATURE_DEACTIVATED

4 OS

OBFLMGR-4-FILE_ERROR

4 OS

OBFLMGR-4-FILE_OPEN_ERROR

4 OS

OBFLMGR-4-FILE_WRITE_ERROR

4 OS

OBFLMGR-4-QSM_ADD_SERVICE_ERROR

4 OS

OBFLMGR-4-QUEUE_CLEAR_ERROR

4 OS

OBFLMGR-4-SYSMGR_API_FAILURE

4 OS

OBFLMGR-4-UNSUPPORTED_FEATURE

4 OS

OBFLMGR-4-UPTIME_RR_NOT_SET

4 OS

OBFLMGR-5-CORRUPTED_MSG

5 OS

OBFLMGR-5-MSG_CKSUM_ERROR

5 OS

OBFLMGR-6-DEVICE_ACTIVATED

6 OS

OBFLMGR-6-DEVICE_ENABLED

6 OS

OBFLMGR-6-FEATURE_ACTIVATED

6 OS

OBFLMGR-7-COALESCE_ERROR

7 OS

OBFLMGR-7-COALESCER_NOT_FOUND

7 OS

OBFLMGR-7-DEVICE_INACTIVE

7 OS

OBFLMGR-7-DEVICE_NOT_READY

7 OS

OBFLMGR-7-DEVICE_NOT_REGISTERED

7 OS

OBFLMGR-7-DEVICE_UNAVAILABLE

7 OS

OBFLMGR-7-ENV_STATE_UNKNOWN

7 OS

OBFLMGR-7-ERRMSG_HIST_FULL

7 OS

OBFLMGR-7-JID_GET_ERROR

7 OS

OBFLMGR-7-MAGIC_NUM_INVALID

7 OS

OBFLMGR-7-META_OPER_WRITE_ERROR

7 OS

OBFLMGR-7-MSG_ERROR

7 OS

OBFLMGR-7-NO_MEMORY

7 OS

OBFLMGR-7-NODEID_DECODE_FAILURE

7 OS

OBFLMGR-7-NODEID_FAILURE

7 OS

OBFLMGR-7-QUEUE_LIMIT_OVER

7 OS

OBFLMGR-7-RACK_DECODE_FAILURE

7 OS

OBFLMGR-7-RECORD_TOO_LONG

7 OS

OBFLMGR-7-RECORD_TYPE_UNKNOWN

7 OS

OBFLMGR-7-REDUNDANCY_STANDBY

7 OS

OBFLMGR-7-SLOT_DECODE_FAILURE

7 OS

OBFLMGR-7-SYSDB_TUPLE_ERROR

7 OS

OBFLMGR-7-UNREGISTERED_FEATURE

7 OS

OBFLMGR-7-UPTIME_CONT_TOO_LARGE

7 OS

OBFLMGR-7-UPTIME_HIST_INVALID_TASKID

7 OS

OBFLMGR-7-UPTIME_HIST_TOO_LARGE

7 OS

OBFLMGR-7-UPTIME_RECORD_NOT_FOUND

7 OS

PA-2-CTX_CREATE

2 OS

PA-2-INFRA_FAIL

2 OS

PA-2-RSI_INIT_FAILED

2 OS

PA-2-RSI_UNKNOWN_EVENT

2 OS

PA-3-BAG_FAILED

3 OS

PA-3-ECM_SETRETRY_FAIL

3 OS

PA-3-SYSDB_FAIL

3 OS

PA-4-ADD_SLICE

4 OS

PA-4-ERR_BACKEND

4 OS

PA-4-EVENT_REGISTRATION_FAILED

4 OS

PA-4-FM_MSG_TIMEOUT

4 OS

PA-4-LOCK_FAILED

4 OS

PA-4-UNLOCK_FAILED

4 OS

PA-6-INFO_GENERAL

6 OS

PA-6-PIFIB_MSG_TIMEOUT

6 OS

PCDS-3-ERROR
PCDS-7-DEBUG

3 OS
7 OS

PLACED_LIB-3-LRD_GET_DLRSC_ERROR

3 OS

PLACED_LIB-3-PLATFORM_GET_ERROR

3 OS

PLACED_LIB-7-MSG_CONNECT

7 OS

PLACED_LIB-7-MSG_SEND

7 OS

PLACED_LIB-7-STARTUP_POLICY

7 OS

PLACED_LIB-7-VECTOR_OVERFLOW

7 OS

PLACED-2-MIGRATE_DONE

2 OS

PLACED-3-ADR_CONSUME

3 OS

PLACED-3-ADR_INIT

3 OS

PLACED-3-ADR_PRODUCE

3 OS

PLACED-3-BAD_MESSAGE

3 OS

PLACED-3-CARD_TYPE

3 OS

PLACED-3-CDM_OPEN

3 OS

PLACED-3-COND_WAIT

3 OS

PLACED-3-CONDVAR_INIT

3 OS

PLACED-3-CONDVAR_SIGNAL

3 OS

PLACED-3-DBG_ON

3 OS

PLACED-3-DBG_REG

3 OS

PLACED-3-ECM_CREATE

3 OS

PLACED-3-ECM_NOTIFY

3 OS

PLACED-3-ECM_OPEN

3 OS

PLACED-3-ECM_SETRETRY

3 OS

PLACED-3-EVENT_CREATE

3 OS

PLACED-3-EVENT_HANDLER

3 OS

PLACED-3-EVM_NULL

3 OS

PLACED-3-FAILED_EOI

3 OS

PLACED-3-GROUP_COUNT

3 OS

PLACED-3-GROUP_CREATE

3 OS

PLACED-3-GROUP_NOTIFY

3 OS

PLACED-3-GROUP_SEND

3 OS

PLACED-3-INCORRECT_COMPONENT

3 OS

PLACED-3-JID_MISSING

3 OS

PLACED-3-JID_UPDATE

3 OS

PLACED-3-LR_PLANE_TIMER_FIRED

3 OS

PLACED-3-MALLOC_FAIL

3 OS

PLACED-3-MUTEX_INIT

3 OS

PLACED-3-MY_NODE

3 OS

PLACED-3-NODE_MISSING

3 OS

PLACED-3-NODE_NAME

3 OS

PLACED-3-NODE_ROLE

3 OS

PLACED-3-NOTIF_REGN

3 OS

PLACED-3-PARENT_CREATE

3 OS

PLACED-3-PARTNER_NODE

3 OS

PLACED-3-PI_PLANE_TIMER_FIRED

3 OS

PLACED-3-PROCESS_EXHAUSTED

3 OS

PLACED-3-PROCEVENT_REGISTER

3 OS

PLACED-3-PTHREAD_CREATE

3 OS

PLACED-3-PTHREAD_DETACH

3 OS

PLACED-3-SYSDB_BIND

3 OS

PLACED-3-SYSDB_STARTUPLIST

3 OS

PLACED-3-SYSDB_UNBIND

3 OS

PLACED-3-SYSMGR_REGN

3 OS

PLACED-3-TABLE_DELETE

3 OS

PLACED-3-TABLE_DUPE

3 OS

PLACED-3-TABLE_EMPTY

3 OS

PLACED-3-TABLE_FIND

3 OS

PLACED-3-TABLE_INIT

3 OS

PLACED-3-TABLE_INSERT

3 OS

PLACED-3-TABLE_READ

3 OS

PLACED-3-TIMER_CREATE

3 OS

PLACED-3-TREE_CREATE

3 OS

PLACED-3-TUPLE_MISSING

3 OS

PLACED-3-TUPLE_UNKNOWN

3 OS

PLACED-3-UNEXPECTED_MSG

3 OS

PLACED-3-UNEXPECTED_REQ

3 OS

PLACED-3-UNKNOWN_TIMER

3 OS

PLACED-3-VS_NOTIF

3 OS

PLACED-3-VS_REGN

3 OS

PLACED-3-ZERO_LEVEL

3 OS

PLACED-3-ZERO_RECORDS

3 OS

PLACED-7-DLRSC_UNKNOWN

7 OS

PLACED-7-EVENT_BLOCK

7 OS

PLACED-7-PROC_READY

7 OS

PLACED-7-TLV_INIT

7 OS

PLACED-7-UNKNOWN_REQTYPE

7 OS

PLATFORM_LPTS_COM_IFIB-3CONFIG_MISSING_FLOW

3 OS

PLATFORM_LPTS_COM_IFIB-3CONFIG_MISSING_FLOW

3 OS

PLATFORM_LPTS_COM_IFIB-3CONFIG_MISSING_PARAMETER

3 OS

PLATFORM_LPTS_COM_IFIB-3CONFIG_MISSING_PARAMETER

3 OS

PLATFORM_LPTS_COM_IFIB-3CONFIG_UNKNOWN_KEYWORD

3 OS

PLATFORM_LPTS_COM_IFIB-3CONFIG_UNKNOWN_KEYWORD

3 OS

PLATFORM_LPTS_COM_IFIB-3CONFIG_UNKNOWN_PARAMETER

3 OS

PLATFORM_LPTS_COM_IFIB-3CONFIG_UNKNOWN_PARAMETER

3 OS

PLATFORM_LPTS_COM_IFIB-3-MEM_ALLOC

3 OS

PLATFORM_LPTS_COM_IFIB-3-NO_CONFIG

3 OS

PLATFORM_LPTS_COM_IFIB-3-NO_CONFIG

3 OS

PLATFORM_LPTS_COM_IFIB-3NO_CONFIG_MEMORY

3 OS

PLATFORM_LPTS_COM_IFIB-3NO_CONFIG_MEMORY

3 OS

PLATFORM_LPTS_COM_IFIB-7DEBUG_CLEANUP

7 OS

PLATFORM_LPTS_COM_IFIB-7DEBUG_CLEANUP

7 OS

PLATFORM_LPTS_COM_IFIB-7-DEBUG_INIT

7 OS

PLATFORM_LPTS_COM_IFIB-7DEBUG_INIT_EVENT

7 OS

PLATFORM_LPTS_COM_IFIB-7DEBUG_INIT_EVENT

7 OS

PLATFORM_LPTS_COM_IFIB-7DEBUG_REGISTER

7 OS

PLATFORM_LPTS_COM_IFIB-7DEBUG_REGISTER

7 OS

PLATFORM_LPTS_COM_NETIO-7DEBUG_CLEANUP

7 OS

PLATFORM_LPTS_COM_NETIO-7DEBUG_CLEANUP

7 OS

PLATFORM_LPTS_COM_NETIO-7DEBUG_CLEANUP

7 OS

PLATFORM_LPTS_COM_NETIO-7DEBUG_CLEANUP

7 OS

PLATFORM_LPTS_COM_NETIO-7DEBUG_INIT_EVENT

7 OS

PLATFORM_LPTS_COM_NETIO-7DEBUG_INIT_EVENT

7 OS

PLATFORM_LPTS_COM_NETIO-7DEBUG_INIT_EVENT

7 OS

PLATFORM_LPTS_COM_NETIO-7DEBUG_INIT_EVENT

7 OS

PLATFORM_LPTS_COM_NETIO-7DEBUG_REGISTER

7 OS

PLATFORM_LPTS_COM_NETIO-7DEBUG_REGISTER

7 OS

PLATFORM_LPTS_COM_NETIO-7DEBUG_REGISTER

7 OS

PLATFORM_LPTS_COM_NETIO-7DEBUG_REGISTER

7 OS

PLATFORM_LPTS_LIB-7-ERR_DEBUG_INIT

7 OS

PLATFORM_LPTS_LIB-7-ERR_DEBUG_INIT

7 OS

PLATFORM_LPTS_PIFIB-3-BACKEND_EDM

3 OS

PLATFORM_LPTS_PIFIB-3-BACKEND_EDM

3 OS

PLATFORM_LPTS_PIFIB-3-BAG

3 OS

PLATFORM_LPTS_PIFIB-3-BAG

3 OS

PLATFORM_LPTS_PIFIB-3-CGM_INIT

3 OS

PLATFORM_LPTS_PIFIB-3-CGM_INIT

3 OS

PLATFORM_LPTS_PIFIB-3-CHKPT_INIT

3 OS

PLATFORM_LPTS_PIFIB-3-CHKPT_INIT

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_FLOW_MEMORY

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_FLOW_MEMORY

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_MISSING_FLOW

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_MISSING_FLOW

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_MISSING_PARAMETER

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_MISSING_PARAMETER

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_POLICER_MEMORY

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_POLICER_MEMORY

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_POLICER_PARAMETER_INVALID

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_POLICER_PARAMETER_INVALID

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_POLICER_PARAMETER_MISSING

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_POLICER_PARAMETER_MISSING

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_POLICER_UNKNOWN_KEYWORD

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_POLICER_UNKNOWN_KEYWORD

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_UNDEFINED_POLICER

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_UNDEFINED_POLICER

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_UNKNOWN_KEYWORD

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_UNKNOWN_KEYWORD

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_UNKNOWN_PARAMETER

3 OS

PLATFORM_LPTS_PIFIB-3CONFIG_UNKNOWN_PARAMETER

3 OS

PLATFORM_LPTS_PIFIB-3CPP_LPTS_EA_REGISTER

3 OS

PLATFORM_LPTS_PIFIB-3-ERR_GENTRY_GET

3 OS

PLATFORM_LPTS_PIFIB-3ERR_GET_NODE_TYPE

3 OS

PLATFORM_LPTS_PIFIB-3ERR_IFH_UIDB_INDEX

3 OS

PLATFORM_LPTS_PIFIB-3ERR_INVALID_SHADOW_ENTRY_STATE

3 OS

PLATFORM_LPTS_PIFIB-3-ERR_MEM_ALLOC

3 OS

PLATFORM_LPTS_PIFIB-3ERR_NOTIF_Q_FULL

3 OS

PLATFORM_LPTS_PIFIB-3ERR_PROCE_NODEID

3 OS

PLATFORM_LPTS_PIFIB-3ERR_PROG_BFD_DISC_TBL

3 OS

PLATFORM_LPTS_PIFIB-3ERR_PROG_STATIC_PUNT

3 OS

PLATFORM_LPTS_PIFIB-3ERR_RACK_CLUSTER_UNSUPPORTED

3 OS

PLATFORM_LPTS_PIFIB-3-ERR_SYSDB

3 OS

PLATFORM_LPTS_PIFIB-3ERR_TCAM_NOT_READY

3 OS

PLATFORM_LPTS_PIFIB-3ERR_TCAM_ODS_DELETE

3 OS

PLATFORM_LPTS_PIFIB-3ERR_TCAM_ODS_DESTROY

3 OS

PLATFORM_LPTS_PIFIB-3ERR_TCAM_ODS_GET_FREE

3 OS

PLATFORM_LPTS_PIFIB-3ERR_TCAM_ODS_INSERT

3 OS

PLATFORM_LPTS_PIFIB-3ERR_TCAM_ODS_INVALIDATE

3 OS

PLATFORM_LPTS_PIFIB-3ERR_TCAM_ODS_RD_IDS

3 OS

PLATFORM_LPTS_PIFIB-3ERR_TCAM_ODS_WRITE

3 OS

PLATFORM_LPTS_PIFIB-3ERR_TCAM_ODS_WRITE_BFD

3 OS

PLATFORM_LPTS_PIFIB-3ERR_TCAM_ODS_WRITE_PORT_ID

3 OS

PLATFORM_LPTS_PIFIB-3ERR_TCAM_ODS_WRITE_WITH_FMT

3 OS

PLATFORM_LPTS_PIFIB-3EVENT_CONN_CREATE

3 OS

PLATFORM_LPTS_PIFIB-3EVENT_CONN_CREATE

3 OS

PLATFORM_LPTS_PIFIB-3EVENT_CONN_OPEN

3 OS

PLATFORM_LPTS_PIFIB-3EVENT_CONN_OPEN

3 OS

PLATFORM_LPTS_PIFIB-3-EVM_INIT

3 OS

PLATFORM_LPTS_PIFIB-3-EVM_TM_ATTACH

3 OS

PLATFORM_LPTS_PIFIB-3EVM_TM_LEAF_NEW

3 OS

PLATFORM_LPTS_PIFIB-3FM_ADD_FEAT2GRP

3 OS

PLATFORM_LPTS_PIFIB-3FM_ADD_FEAT2GRP

3 OS

PLATFORM_LPTS_PIFIB-3-FM_ADD_IFH2GRP

3 OS

PLATFORM_LPTS_PIFIB-3-FM_ADD_IFH2GRP

3 OS

PLATFORM_LPTS_PIFIB-3FM_CREATE_GROUP

3 OS

PLATFORM_LPTS_PIFIB-3FM_CREATE_GROUP

3 OS

PLATFORM_LPTS_PIFIB-3FM_FEAT_PROCESSING

3 OS

PLATFORM_LPTS_PIFIB-3FM_FEAT_PROCESSING

3 OS

PLATFORM_LPTS_PIFIB-3-FM_REGISTER

3 OS

PLATFORM_LPTS_PIFIB-3-FM_REGISTER

3 OS

PLATFORM_LPTS_PIFIB-3-GET_NODE_TYPE

3 OS

PLATFORM_LPTS_PIFIB-3-HA_WAIT

3 OS

PLATFORM_LPTS_PIFIB-3-HA_WAIT

3 OS

PLATFORM_LPTS_PIFIB-3-HFA_REGISTER

3 OS

PLATFORM_LPTS_PIFIB-3-HFA_REGISTER

3 OS

PLATFORM_LPTS_PIFIB-3-IFH_UIDB_INDEX

3 OS

PLATFORM_LPTS_PIFIB-3-IPV6_COMPRESS

3 OS

PLATFORM_LPTS_PIFIB-3-IPV6_COMPRESS

3 OS

PLATFORM_LPTS_PIFIB-3-LTRACE_INIT

3 OS

PLATFORM_LPTS_PIFIB-3-LTRACE_INIT

3 OS

PLATFORM_LPTS_PIFIB-3-MEM_ALLOC

3 OS

PLATFORM_LPTS_PIFIB-3-MSG_ATTACH

3 OS

PLATFORM_LPTS_PIFIB-3-MSG_ATTACH

3 OS

PLATFORM_LPTS_PIFIB-3-NO_CONFIG

3 OS

PLATFORM_LPTS_PIFIB-3-NO_CONFIG

3 OS

PLATFORM_LPTS_PIFIB-3-NOTIF_Q_FULL

3 OS

PLATFORM_LPTS_PIFIB-3-SHM_INIT

3 OS

PLATFORM_LPTS_PIFIB-3-SHM_INIT

3 OS

PLATFORM_LPTS_PIFIB-3SHOW_EDM_CLOSE

3 OS

PLATFORM_LPTS_PIFIB-3SHOW_EDM_CLOSE

3 OS

PLATFORM_LPTS_PIFIB-3-SHOW_EDM_INIT

3 OS

PLATFORM_LPTS_PIFIB-3-SHOW_EDM_INIT

3 OS

PLATFORM_LPTS_PIFIB-3-SYSDB

3 OS

PLATFORM_LPTS_PIFIB-3-SYSDB

3 OS

PLATFORM_LPTS_PIFIB-3TCAM_FMT_TO_HFA_MAP

3 OS

PLATFORM_LPTS_PIFIB-3TCAM_FMT_TO_HFA_MAP

3 OS

PLATFORM_LPTS_PIFIB-3-UIDB_INDEX

3 OS

PLATFORM_LPTS_PIFIB-4-CONN_INIT

4 OS

PLATFORM_LPTS_PIFIB-4ERR_NON_EXISTS_ACL

4 OS

PLATFORM_LPTS_PIFIB-4ERR_SECURITY_TTL_OPT

4 OS

PLATFORM_LPTS_PIFIB-4-INIT_POLICERS

4 OS

PLATFORM_LPTS_PIFIB-4-MIPC_INIT

4 OS

PLATFORM_LPTS_PIFIB-4-MIPC_NOTIF_ACK

4 OS

PLATFORM_LPTS_PIFIB-4-MSTATS_INIT

4 OS

PLATFORM_LPTS_PIFIB-4-NOTIF_HANDLE

4 OS

PLATFORM_LPTS_PIFIB-4PROGRAM_ERRORED_POLICER

4 OS

PLATFORM_LPTS_PIFIB-4REPROGRAM_POLICERS

4 OS

PLATFORM_LPTS_PIFIB-4SYSDB_DATALIST_CREATE

4 OS

PLATFORM_LPTS_PIFIB-4-TCAM_INIT

4 OS

PLATFORM_LPTS_PIFIB-5ERR_PRM_STATS_ALLOC

5 OS

PLATFORM_LPTS_PIFIB-5ERR_TCAM_INVALID_REG_NAME

5 OS

PLATFORM_LPTS_PIFIB-5ERR_TCAM_OVERFLOW

5 OS

PLATFORM_LPTS_PIFIB-5ERR_TCAM_PREFIX_COMPRESS

5 OS

PLATFORM_LPTS_PIFIB-5-MSTATS_ALLOC

5 OS

PLATFORM_LPTS_PIFIB-5TCAM_INVALID_REG_NAME

5 OS

PLATFORM_LPTS_PIFIB-5-TCAM_OVERFLOW

5 OS

PLATFORM_LPTS_PIFIB-5TCAM_PREFIX_COMPRESS

5 OS

PLATFORM_LPTS_PIFIB-6IS_TOS_SUPPORTED

6 OS

PLATFORM_LPTS_PIFIB-7-DEBUG_CLEANUP

7 OS

PLATFORM_LPTS_PIFIB-7-DEBUG_CLEANUP

7 OS

PLATFORM_LPTS_PIFIB-7DEBUG_INIT_EVENT

7 OS

PLATFORM_LPTS_PIFIB-7DEBUG_INIT_EVENT

7 OS

PLATFORM_LPTS_PIFIB-7-DEBUG_REGISTER

7 OS

PLATFORM_LPTS_PIFIB-7-DEBUG_REGISTER

7 OS

PLATFORM_LPTS_PIFIB-7-ERR_CONN_INIT

7 OS

PLATFORM_LPTS_PIFIB-7-ERR_DEBUG_INIT

7 OS

PLATFORM_LPTS_PIFIB-7-ERR_DEBUG_INIT

7 OS

PLATFORM_LPTS_PIFIB-7-ERR_DEBUG_INIT

7 OS

PLATFORM_LPTS_PIFIB-7-ERR_EVM_INIT

7 OS

PLATFORM_LPTS_PIFIB-7ERR_EVM_TM_ATTACH

7 OS

PLATFORM_LPTS_PIFIB-7ERR_EVM_TM_LEAF_NEW

7 OS

PLATFORM_LPTS_PIFIB-7ERR_INIT_POLICERS

7 OS

PLATFORM_LPTS_PIFIB-7-ERR_LTRACE_INIT

7 OS

PLATFORM_LPTS_PIFIB-7-ERR_MIPC_INIT

7 OS

PLATFORM_LPTS_PIFIB-7ERR_MIPC_NOTIF_ACK

7 OS

PLATFORM_LPTS_PIFIB-7ERR_NO_OPERATION

7 OS

PLATFORM_LPTS_PIFIB-7ERR_NOTIF_HANDLE

7 OS

PLATFORM_LPTS_PIFIB-7ERR_PRM_STATS_INIT

7 OS

PLATFORM_LPTS_PIFIB-7ERR_PROGRAM_ERRORED_POLICER

7 OS

PLATFORM_LPTS_PIFIB-7ERR_REPROGRAM_POLICERS

7 OS

PLATFORM_LPTS_PIFIB-7ERR_SHADOW_WRITE_LIMIT

7 OS

PLATFORM_LPTS_PIFIB-7ERR_SYSDB_DATALIST_CREATE

7 OS

PLATFORM_LPTS_PIFIB-7-ERR_TCAM_INIT

7 OS

PLATFORM_LPTS_PIFIB-7-ERR_USAGE

7 OS

PLATFORM_LPTS_PIFIB-7-LTRACE_INIT

7 OS

PMHAC-7-ERR_DLL_INIT

7 OS

PMHAD-3-ERR_NOMEM

3 OS

PMHAD-4-ERR_NOMEM_WARNING

4 OS

PMHAD-7-ERR_DLL_INIT

7 OS

PMHAD-7-ERR_INIT

7 OS

PROCFIND-4-NODETYPE

4 OS

PROCFIND-6-EVENT_BLOCK

6 OS

PROCFIND-6-PROC_INFO

6 OS

PROCFIND-6-PROC_OPEN

6 OS

PROCFIND-6-READY

6 OS

PROCFIND-7-EVENT_MGR

7 OS

PROCFIND-7-MEMORY

7 OS

PROCFIND-7-NODEID

7 OS

PROCFIND-7-SYSDB_BIND

7 OS

PROCFIND-7-SYSDB_EDM_INIT

7 OS

PROCFIND-7-SYSDB_EDM_REG

7 OS

PUF-4-MCAST_MSG

4 OS

QAD_LIB-3-ERROR

3 OS

QAD_LIB-3-SHMWIN_ERROR

3 OS

QAD_LIB-6-INFO

6 OS

QAD_QUEUE_MODEL-3-ERROR

3 OS

QAD_QUEUE_MODEL-3-SHMWIN_ERROR

3 OS

QAD_SERVER-3-ERROR

3 OS

QAD_SERVER-3-SHMWIN_ERROR

3 OS

QAD_SERVER-3-SYSMGR_ERROR

3 OS

QAD_SERVER-7-EVM_ERROR

7 OS

QNET_LC-7-BASE_BAD_CHAIN_TYPE

7 OS

QNET_LC-7-BASE_CONTROL_FUNC_ERR

7 OS

QNET_LC-7-CAPS_BAD_CHAIN_TYPE

7 OS

QNET_LC-7-CAPS_CONTROL_FUNC_ERR

7 OS

QNET_LC-7-DUPLICATE_BMA_PAK

7 OS

QNET_LC-7-ENCAPS_FUNC_ERR

7 OS

QNET_LC-7-LOST_QNET_CONN

7 OS

QNET_LC-7-PAK_INPUT_FAIL

7 OS

QNET_LC-7-UINT32_GET

7 OS

QNET-0-EMG

--

OS

QNET-1-ALT

1 OS

QNET-2-CRT

2 OS

QNET-2-PRP3FAB_INIT_DEVICE

2 OS

QNET-3-DEBUG_EVENT_LOOP

3 OS

QNET-3-DEBUG_THREAD_CREATE

3 OS

QNET-3-DISCONN_ATTACH

3 OS

QNET-3-ERR

3 OS

QNET-3-EVM_CREATE

3 OS

QNET-3-EVM_THREAD

3 OS

QNET-3-PRP3FAB_QNET_TX_PAK

3 OS

QNET-3-SET_RLIMIT

3 OS

QNET-4-DEBUG_EVM_CREATE

4 OS

QNET-4-DUMPER_SNAP_DUMP

4 OS

QNET-4-DUMPER_SNAP_NODUMP

4 OS

QNET-4-WRN

4 OS

QNET-5-NOT

5 OS

QNET-6-DUMPER_SNAP_DUMP_OK

6 OS

QNET-6-INF

6 OS

QNET-7-DEB

7 OS

QNET-7-SIO_Q_PROD

7 OS

QSM-3-ADD_SYMLINKS_DIR

3 OS

QSM-3-ADD_SYMLINKS_FILE

3 OS

QSM-3-BAD_DBDUMP_MESSAGE

3 OS

QSM-3-BAD_MESSAGE

3 OS

QSM-3-BAD_UPDATE_MESSAGE

3 OS

QSM-3-CERR_REGISTER

3 OS

QSM-3-CHECKPOINT_CANT_OPEN

3 OS

QSM-3-CHECKPOINT_CANT_RELOAD

3 OS

QSM-3CHECKPOINT_CANT_RELOAD_NOTIFY

3 OS

QSM-3-CHECKPOINT_CANT_RENAME

3 OS

QSM-3-CHECKPOINT_CANT_SEEK

3 OS

QSM-3-CHECKPOINT_CANT_TRUNCATE

3 OS

QSM-3-CHECKPOINT_CANT_WRITE

3 OS

QSM-3-CHECKPOINT_FORMAT

3 OS

QSM-3-CHECKPOINT_LOCK_FAILURE

3 OS

QSM-3-CHECKPOINT_NOSPACE

3 OS

QSM-3-INITIALIZATION_FAILURE

3 OS

QSM-3-INVALID_PLATFORM_TYPE

3 OS

QSM-3-INVALID_SYMLINKS_FILE

3 OS

QSM-3-LINK_BAD_MODE

3 OS

QSM-3-LINK_CREATE_FAILURE

3 OS

QSM-3-LINK_DELETE_FAILURE_INUM

3 OS

QSM-3-LINK_DELETE_FAILURE_PATH

3 OS

QSM-3-LINK_FREE_ZERO_INUM

3 OS

QSM-3-LINK_INVALID_CUR_INDEX

3 OS

QSM-3-LINK_LOCK_FAILURE

3 OS

QSM-3-LINK_WRONG_RESULT

3 OS

QSM-3-LOCATE_SYMLINKS_FILE

3 OS

QSM-3-LOCK_FAILURE

3 OS

QSM-3-LOCK_FAILURE_LOCKTEST

3 OS

QSM-3-NO_MEMORY

3 OS

QSM-3-NON_ADMIN_ADD

3 OS

QSM-3-NOTIFY_LOCK_FAILURE

3 OS

QSM-3-NOTIFY_WRITE_FAILED

3 OS

QSM-3-OPEN_SYMLINKS_FILE

3 OS

QSM-3-SEND_DATABASE_MESSAGE

3 OS

QSM-7-ADMIN_ADD

7 OS

QSM-7-BAD_LWM_MSG

7 OS

QSM-7-BAD_LWM_VERSION

7 OS

QSM-7-DEBUG_KEY_CREATE

7 OS

QSM-7-DEBUG_SPECIFIC_ALLOC

7 OS

QSM-7-DEBUG_SPECIFIC_SET

7 OS

QSM-7-LINK_BAD_THREAD_INUM

7 OS

QSM-7-LINK_BAD_THREAD_PATH

7 OS

QSM-7-LINK_LOST_EMPTY_DIRECTORY

7 OS

QSM-7-LOCK_HELD

7 OS

QSM-7-LOCK_NOTFOUND

7 OS

QSM-7-LOCK_WRONG_COUNT

7 OS

QSM-7-LOCKORDER_FAILURE

7 OS

QSM-7-LOCKORDER_UPGRADE

7 OS

QSM-7-NODE_DELETE_FAILURE

7 OS

QSM-7-NODE_LOOKUP_FAILURE

7 OS

QSM-7-NON_LOCAL

7 OS

QSM-7-NOTIFY_REGISTER_FAILED

7 OS

QSM-7-NOTIFY_UNREGISTER_FAILED

7 OS

QUEUE-7-LINKED

7 OS

QUEUE-7-NOTQ

7 OS

QUEUE-7-QCOUNT

7 OS

RDS-2-IDT_FAILED

2 OS

RDS-3-ALLOC_FAILURE_MSG

3 OS

RDS-3-ASSERT_MSG

3 OS

RDS-3-BAD_READ

3 OS

RDS-3-BAD_SEQNUM

3 OS

RDS-3-LOCK_FAILURE

3 OS

RDS-3-SNAP_DUMP

3 OS

RDS-3-WRITE_TIMEDOUT

3 OS

RDS-4-COND_TIMED_WAIT

4 OS

RDS-4-RING_LOOKUP

4 OS

RDS-7-BAD_RDSTYPE

7 OS

RDS-7-DUPLICATE_TICKET_NOTIF

7 OS

RDS-7-ENS_BULK_REGISTER

7 OS

RDS-7-ENS_PRODUCER_RELEASE

7 OS

RDS-7-ENS_PUBLISH

7 OS

RDS-7-ENS_REGISTER_CLASS

7 OS

RDS-7-GENERIC_FAILURE_MSG

7 OS

RDS-7-GET_DH_ENTRY

7 OS

RDS-7-GET_REPLICA

7 OS

RDS-7-GROUP_CREATE

7 OS

RDS-7-GROUP_SEND_RINFO

7 OS

RDS-7-GSM_FAIL

7 OS

RDS-7-INVALID_ARGS

7 OS

RDS-7-INVALID_RHDR

7 OS

RDS-7-NO_PREQ_ENTRY

7 OS

RDS-7-NRS_CREATE_CLASS

7 OS

RDS-7-NRS_DECODE

7 OS

RDS-7-NRS_REGISTER_BULK

7 OS

RDS-7-NRS_SEARCH

7 OS

RDS-7-PENDING_MSG

7 OS

RDS-7-QUERY_PEERS_TIMED_OUT

7 OS

RDS-7-READ_FAILED

7 OS

RDS-7-SEARCH_HDLS_FAILED

7 OS

RDS-7-SYNC_CREATE

7 OS

RDS-7-SYNC_RELEASE_FAILED

7 OS

RDS-7-SYNC_REQUEST

7 OS

RDS-7-SYNC_REQUEST_TIMED_OUT

7 OS

RDS-7-SYNC_REQUEST_UNEXPECTED

7 OS

RDS-7-WRONG_PLANE

7 OS

RDSFS-4-BAD_REPLICA

4 OS

RDSFS-7-DEBUG

7 OS

RDSFS-7-EDM_INTERNAL

7 OS

RDSFS-7-FAILURE

7 OS

RDSFS-7-INIT_FAILED

7 OS

REDFS_HELPER-4-INIT_ERROR

4 OS

REDFS_HELPER-4-SYSDB_ERROR

4 OS

REDFS-2-CORRUPT_FILE_SYNC_NOBACKUP

2 OS

REDFS-3-CORRUPT_FILE

3 OS

REDFS-3-CORRUPT_FILE_RECOVERY_FAILED

3 OS

REDFS-4-MIRROR_DISABLED

4 OS

REDFS-5-CORRUPT_FILE_RECOVERED

5 OS

REDFS-5-DLLLOAD_FAILED

5 OS

REDFS-5-HDD_MIRROR_NOT_START

5 OS

REDFS-5-HDD_MIRROR_OVERRIDEN

5 OS

REDFS-5-INIT_FAILED

5 OS

REDFS-5-MIRROR_ERROR

5 OS

REDFS-5-MIRROR_NOT_REDUNDANT

5 OS

REDFS-5-MIRROR_NOT_START

5 OS

REDFS-5-MIRROR_PAUSED

5 OS

REDFS-5-MIRROR_SYNC_FAILED

5 OS

REDFS-6-CORRUPT_FILE_SYNC_COPY

6 OS

REDFS-6-CORRUPT_FILE_SYNC_SINGLE

6 OS

REDFS-6-MIRROR_ENABLED

6 OS

REDFS-6-MIRROR_REDUNDANT

6 OS

REDFS-6-MIRROR_RESUMED

6 OS

REDFS-6-MIRROR_UPGRADE

6 OS

REGEXP-6-ENOMEM

6 OS

REGEXP-6-ENOMEM

6 OS

REGEXP-6-INTERNAL

6 OS

REGEXP-6-INTERNAL

6 OS

REGEXP-6-INVALID

6 OS

REGEXP-6-INVALID

6 OS

REGEXP-6-REGERROR

6 OS

REGEXP-6-REGERROR

6 OS

RSI_AGENT-2-OBJ_CREATE

2 OS

RSI_AGENT-2-RESOURCE_DOWN

2 OS

RSI_AGENT-3-CONSISTENCY_CHECK

3 OS

RSI_AGENT-3-CONSISTENCY_CHECK_LTBL

3 OS

RSI_AGENT-3-GENERAL_FAILURE

3 OS

RSI_AGENT-3-INIT_FAILURE

3 OS

RSI_AGENT-3-INTF_MAPPING_CHANGE

3 OS

RSI_AGENT-3-INVALID_CLIENT_TDL_INPUT

3 OS

RSI_AGENT-3-NONRESPONSIVE_CLIENT

3 OS

RSI_AGENT-6-CARD_ROLE_CHANGE

6 OS

RSI_MASTER-2-INVALID_THREAD

2 OS

RSI_MASTER-2-MEM_ALLOC_FAILURE

2 OS

RSI_MASTER-3-GENERAL_FAILURE

3 OS

RSI_MASTER-3-GENERAL_FAILURE_NO_RC

3 OS

RSI_MASTER-6-INFO_SVD

6 OS

RSVDPMEM-3-BAD_DATAFILE_VALUES

3 OS

RSVDPMEM-3-BAD_RETURN_VALUES

3 OS

RSVDPMEM-3-INVALID_PARAMS

3 OS

RSVDPMEM-3-MEMUTIL_FIND_FAIL

3 OS

RSVDPMEM-3-OPEN_FAIL

3 OS

RSVDPMEM-3-SSCANF_FAIL

3 OS

RSVDPMEM-7-NO_MATCHING_STRING

7 OS

RT_CHECK_LIB-3-CERR_REGISTER_DLL

3 OS

RT_CHECK_LIB-3-DEBUG_SERVICES

3 OS

RT_CHECK_LIB-3-EVENT_MANAGER

3 OS

RT_CHECK_LIB-3-GEN_ERR

3 OS

RT_CHECK_LIB-3-MGD_TIMER

3 OS

RT_CHECK_LIB-3-PTHREAD

3 OS

RT_CHECK_LIB-3-SYSDB

3 OS

RT_CHECK_LIB-6-GSP_CONN

6 OS

RT_CHECK_LIB-6-GSP_LOOKUP

6 OS

RT_CHECK_LIB-6-GSP_NOTIFY

6 OS

RT_CHECK_LIB-6-GSP_SEND

6 OS

RT_CHECK-3-CHAN_CONN

3 OS

RT_CHECK-3-DEBUG_SERVICES

3 OS

RT_CHECK-3-EDM_DATALIST_ADD_FAILED

3 OS

RT_CHECK-3EDM_DATALIST_CREATE_FAILED

3 OS

RT_CHECK-3-EDM_ENCODE_FAILED

3 OS

RT_CHECK-3-EDM_LIST_ADD_FAILED

3 OS

RT_CHECK-3-EDM_LIST_CREATE_FAILED

3 OS

RT_CHECK-3-EDM_REGISTER_FAILED

3 OS

RT_CHECK-3-EVENT_MANAGER

3 OS

RT_CHECK-3-GROUP

3 OS

RT_CHECK-3-INCONSISTENCY_DETECTED

3 OS

RT_CHECK-3-MEMORY

3 OS

RT_CHECK-3-MGD_TIMER

3 OS

RT_CHECK-3-PRODUCER_REQ

3 OS

RT_CHECK-3-PTHREAD

3 OS

RT_CHECK-3-PTHREAD_MUTEX

3 OS

RT_CHECK-3-RSI_INIT

3 OS

RT_CHECK-3-RSI_TBL_ID

3 OS

RT_CHECK-3-RSI_VRF_NAME

3 OS

RT_CHECK-3-SYSDB

3 OS

RT_CHECK-3-SYSMGR

3 OS

RT_CHECK-3-TIMER_INIT

3 OS

RT_CHECK-3-USAGE

3 OS

RT_CHECK-4-NODE_FAILED

4 OS

RT_CHECK-6EDM_BAG_REGISTRATION_FAILED

6 OS

SEIPC-3-INVALID_OBJECT

3 OS

SEIPC-3-OPERATION_FAILURE

3 OS

SEIPC-3-OPERATION_FAILURE_STR

3 OS

SEIPC-3-RECV_BUF_ERROR

3 OS

SHMWIN_SVR-3-EVM_IMDR_ERROR

3 OS

SHMWIN_SVR-3-EVM_INIT_ERROR

3 OS

SHMWIN_SVR-3-GLOBAL_MUTEX_ERR

3 OS

SHMWIN_SVR-3-INVALID_ID

3 OS

SHMWIN_SVR-3-LWM_ERROR

3 OS

SHMWIN_SVR-3-MAIN_INIT

3 OS

SHMWIN_SVR-3-MMAP_IMDR_FAIL

3 OS

SHMWIN_SVR-3-MMAP_SHM_FAIL

3 OS

SHMWIN_SVR-3-MMAP_STATS_FAIL

3 OS

SHMWIN_SVR-3-MSG_ERROR

3 OS

SHMWIN_SVR-3-NO_MEMORY

3 OS

SHMWIN_SVR-3-NOVMEM

3 OS

SHMWIN_SVR-3-PLATFORM_FILE

3 OS

SHMWIN_SVR-3-QSM_ERROR

3 OS

SHMWIN_SVR-3-REMAP_ERR

3 OS

SHMWIN_SVR-3-SHM_INIT_ERR

3 OS

SHMWIN_SVR-3-SHM_MAP_ERR

3 OS

SHMWIN_SVR-3-SHM_POOL_ERR

3 OS

SHMWIN_SVR-3-SHMWIN_SIZE

3 OS

SHMWIN_SVR-3-WINDOW_MUTEX_ERR

3 OS

SHMWIN_SVR-4-SHM_DIR_ERR

4 OS

SHMWIN_SVR-4-SHM_LOGGING_ERR

4 OS

SHMWIN_SVR-4-SHOW_ERR

4 OS

SHMWIN_SVR-6-SHARED_MUTEX_REVIVED

6 OS

SHMWIN-2-ERROR_ENCOUNTERED

2 OS

SHMWIN-2-SHARED_PAGE_ERROR

2 OS

SHMWIN-3-ALLOC_ARENA_FAILED

3 OS

SHMWIN-3-APPLICATION_TRANSLATE_ERR

3 OS

SHMWIN-3-FREE_ARENA_FAILED

3 OS

SHMWIN-3-FSTAT_FAILED

3 OS

SHMWIN-3-FTRUNCATE_FAILED

3 OS

SHMWIN-3-LIST_NODE_INCONSISTENCY

3 OS

SHMWIN-3-MMAP_ABORT

3 OS

SHMWIN-3-MMAP_FAILED

3 OS

SHMWIN-3-MMAP_PEER_FAILED

3 OS

SHMWIN-3-MUNMAP_FAILED

3 OS

SHMWIN-3-MUNMAP_PEER_FAILED

3 OS

SHMWIN-3-MUTEXOP_FAILED

3 OS

SHMWIN-3-OPEN_FAILED

3 OS

SHMWIN-3-SYS_MUTEXOP_FAILED

3 OS

SHMWIN-3-UNLINK_FAILED

3 OS

SHMWIN-3-WIN_MUTEXOP_FAILED

3 OS

SHMWIN-6-FILE_EXISTS

6 OS

SMGR-3-ARTIFACTS_COPY_FAIL

3 OS

SMGR-3-ARTIFACTS_SYNC_FAIL

3 OS

SMGR-3-EVM_CREATE

3 OS

SMGR-3-INCORRECT_PATH

3 OS

SMGR-3-MALLOC_FAILED

3 OS

SMGR-3-MSG_SEND_PULSE

3 OS

SMGR-3-VM_ACTIVATE_FAIL

3 OS

SMGR-3-VM_INSTALL_FAIL

3 OS

SMGR-3-VM_LICENSING_FAIL

3 OS

SMGR-4-CFG_FAILED

4 OS

SMGR-6-OVA_COPY_DONE

6 OS

SMGR-6-OVA_COPY_START

6 OS

SMGR-6-VM_ACTIVATE_STATUS

6 OS

SMGR-6-VM_INSTALL_STATUS

6 OS

SMGR-7-SYSCALL

7 OS

SMGR-7-UNEXPECTED

7 OS

SPAIPC_NETIO-7-BASE_BAD_CHAIN_TYPE

7 OS

SPAIPC_NETIO-7BASE_CONTROL_FUNC_ERR

7 OS

SPAIPC_NETIO-7-CAPS_BAD_CHAIN_TYPE

7 OS

SPAIPC_NETIO-7-DEBUG_INIT_FAILED

7 OS

SPAIPC_NETIO-7-ENCAPS_FUNC_ERR

7 OS

SPAIPC_NETIO-7-PAK_INPUT_FAIL

7 OS

SPAIPC_NETIO-7-UINT32_GET

7 OS

SSM_LIB-3-BLOCKED

3 OS

SSM_LIB-3-ERROR

3 OS

SSM_LIB-3-MUTEX_REVIVAL

3 OS

SSM_LIB-3-SERVICE_ENTRY_NOT_AVAILABLE

3 OS

SSM_LIB-3-STRING_LENGTH

3 OS

SSM_LIB-6-INVALID_REQUEST

6 OS

SSM_LIB-6-INVALID_REQUEST_ID

6 OS

SSM_LIB-6-OTHER_LIBRARY_ERROR

6 OS

SSM_LIB-6-WAITING

6 OS

SSM_LIB-7-DEBUG

7 OS

SSM-3-CONNECT_ATTACH

3 OS

SSM-3-CONNECT_DETACH

3 OS

SSM-3-EVM_CREATE

3 OS

SSM-3-MALLOC_FAILED

3 OS

SSM-3-MDR_RECOVERY

3 OS

SSM-3-MSG_SEND_PULSE

3 OS

SSM-3-PULSE_FAILED

3 OS

SSM-3-RESTART_FAIL

3 OS

SSM-3-SHM_OPEN_FAIL

3 OS

SSM-3-SYSDB_BLOCK_DETECT

3 OS

SSM-4-CFG_FAILED

4 OS

SSM-4-MDR_RECOVERY_UNSUPPORTED

4 OS

SSM-5-CARD_RELOAD

5 OS

SSM-6-ALARM_CHANGE

6 OS

SSM-6-NODAL_SERVICE_STATE_CHANGE

6 OS

SSM-6-RECOVER_FAIL

6 OS

SSM-6-SERVICE_UNAVAIL

6 OS

SSM-6-STATE_CHANGE

6 OS

SSM-6-SYSDB_BLOCK_RECOVER

6 OS

SSM-6-SYSDB_BLOCK_RECOVER_WAIT

6 OS

SSM-6-SYSDB_BLOCK_SERVICE

6 OS

SSM-7-SYSCALL

7 OS

SSM-7-UNEXPECTED

7 OS

SYSLOG-0-LOG_EMERG

--

OS

SYSLOG-0-LOG_EMERG_OWNER_PLANE

--

OS

SYSLOG-1-LOG_ALERT

1 OS

SYSLOG-1-LOG_ALERT_OWNER_PLANE

1 OS

SYSLOG-2-LOG_CRIT

2 OS

SYSLOG-2-LOG_CRIT_OWNER_PLANE

2 OS

SYSLOG-3-LOG_ERR

3 OS

SYSLOG-3-LOG_ERR_OWNER_PLANE

3 OS

SYSLOG-4-LOG_WARNING

4 OS

SYSLOG-4-LOG_WARNING_OWNER_PLANE

4 OS

SYSLOG-5-LOG_NOTICE

5 OS

SYSLOG-5-LOG_NOTICE_OWNER_PLANE

5 OS

SYSLOG-6-LOG_INFO

6 OS

SYSLOG-6-LOG_INFO_OWNER_PLANE

6 OS

SYSLOG-7-EVM_CREATE

7 OS

SYSLOG-7-EVM_EVENT_BLOCK

7 OS

SYSLOG-7-LOG_DEBUG

7 OS

SYSLOG-7-LOG_DEBUG_OWNER_PLANE

7 OS

SYSLOG-7-MISC_ERR

7 OS

SYSLOG-7-RM_ATTACH

7 OS

SYSLOG-7-THREAD_CREATE

7 OS

SYSMGR-0-EMERGENCY

--

OS

SYSMGR-0-EMERGENCY

--

OS

SYSMGR-1-ABORT_WARM_RELOAD

1 OS

SYSMGR-1-ABORT_WARM_RELOAD

1 OS

SYSMGR-1-ALERT

1 OS

SYSMGR-1-ALERT

1 OS

SYSMGR-2-CRITICAL

2 OS

SYSMGR-2-CRITICAL

2 OS

SYSMGR-2-MANAGED_REBOOT

2 OS

SYSMGR-2-MANAGED_REBOOT

2 OS

SYSMGR-2-REBOOT

2 OS

SYSMGR-2-REBOOT

2 OS

SYSMGR-3-ERROR

3 OS

SYSMGR-3-ERROR

3 OS

SYSMGR-3-FUNCTION

3 OS

SYSMGR-3-FUNCTION

3 OS

SYSMGR-3-GET_PLACEMENT_LIST

3 OS

SYSMGR-3-GET_PLACEMENT_LIST

3 OS

SYSMGR-3-UNEXPECTED

3 OS

SYSMGR-3-UNEXPECTED

3 OS

SYSMGR-4-MANDATORY_OFF

4 OS

SYSMGR-4-MANDATORY_OFF

4 OS

SYSMGR-4-MANDATORY_ON

4 OS

SYSMGR-4-MANDATORY_ON

4 OS

SYSMGR-4-MANDATORY_REBOOT_ABORTED

4 OS

SYSMGR-4-MANDATORY_REBOOT_ABORTED

4 OS

SYSMGR-4-MANDATORY_REBOOT_ENABLE

4 OS

SYSMGR-4-MANDATORY_REBOOT_ENABLE

4 OS

SYSMGR-4MANDATORY_REBOOT_OVERRIDE

4 OS

SYSMGR-4MANDATORY_REBOOT_OVERRIDE

4 OS

SYSMGR-4-PROC_CRASH_JID

4 OS

SYSMGR-4-PROC_CRASH_JID

4 OS

SYSMGR-4-PROC_CRASH_NAME

4 OS

SYSMGR-4-PROC_CRASH_NAME

4 OS

SYSMGR-4-PROC_RESTART_JID

4 OS

SYSMGR-4-PROC_RESTART_JID

4 OS

SYSMGR-4-PROC_RESTART_NAME

4 OS

SYSMGR-4-PROC_RESTART_NAME

4 OS

SYSMGR-4-PROC_SHUTDOWN_JID

4 OS

SYSMGR-4-PROC_SHUTDOWN_JID

4 OS

SYSMGR-4-PROC_SHUTDOWN_NAME

4 OS

SYSMGR-4-PROC_SHUTDOWN_NAME

4 OS

SYSMGR-4-PROC_START_JID

4 OS

SYSMGR-4-PROC_START_JID

4 OS

SYSMGR-4-PROC_START_NAME

4 OS

SYSMGR-4-PROC_START_NAME

4 OS

SYSMGR-4-UNLINK_NVLOG

4 OS

SYSMGR-4-UNLINK_NVLOG

4 OS

SYSMGR-4-WARNING

4 OS

SYSMGR-4-WARNING

4 OS

SYSMGR-5-NOTICE

5 OS

SYSMGR-5-NOTICE
SYSMGR-6-INFO
SYSMGR-6-INFO

5 OS
6 OS
6 OS

SYSMGR-7-CHECK_LOG

7 OS

SYSMGR-7-CHECK_LOG
SYSMGR-7-DEBUG
SYSMGR-7-DEBUG

7 OS
7 OS
7 OS

SYSMGR-7-FUNCTION_PATH

7 OS

SYSMGR-7-FUNCTION_PATH
SYSMGR-7-INSTALL_FINISHED
SYSMGR-7-INSTALL_FINISHED

7 OS
7 OS
7 OS

SYSMGR-7-INSTALL_NOTIFICATION

7 OS

SYSMGR-7-INSTALL_NOTIFICATION

7 OS

TIMER-3-MGDTIMER

3 OS

TIMER-3-NO_CHILD

3 OS

TIMER-3-TIMERNEG

3 OS

TIMER-3TW_CREATE_TIMESLICE_TOO_SMALL

3 OS

TIMER-3-TWCHUNKALLOC

3 OS

TIMER-3-TWCHUNKFREE

3 OS

TIMER-3-TWEVMERROR

3 OS

TIMER-3-TWMUTEXLOCKERROR

3 OS

TIMER-3-TWMUTEXUNLOCKERROR

3 OS

TIMER-3-TWNOMEM

3 OS

TIMER-3-TWOSERROR

3 OS

TIMER-3-TWTIMERALLOC

3 OS

TIMER-3-TWTIMERERROR

3 OS

TZ-3-INTERNAL

3 OS

TZ-3-INTERNAL

3 OS

TZ-3-LRD

3 OS

TZ-3-LRD

3 OS

TZ-3-PUF_CFGSTR_LOOKUP_ERR

3 OS

TZ-3-PUF_CFGSTR_LOOKUP_ERR

3 OS

TZ-3-PUF_INVALID_TOKEN_TYPE

3 OS

TZ-3-PUF_INVALID_TOKEN_TYPE

3 OS

TZ-3-PUF_MAGIC_CHK_ERR

3 OS

TZ-3-PUF_MAGIC_CHK_ERR

3 OS

TZ-3-PUF_MAGIC_LOOKUP_ERR

3 OS

TZ-3-PUF_MAGIC_LOOKUP_ERR

3 OS

TZ-3-PUF_MEDIA_ACCESS_ERR

3 OS

TZ-3-PUF_MEDIA_ACCESS_ERR

3 OS

TZ-3-PUF_READ_ERR

3 OS

TZ-3-PUF_READ_ERR

3 OS

TZ-3-PUF_WRITE_ERR

3 OS

TZ-3-PUF_WRITE_ERR

3 OS

TZ-3-SYSDB

3 OS

TZ-3-SYSDB

3 OS

TZ-3-TIMEZONE_CFGSTR_SET_ERR

3 OS

TZ-3-TIMEZONE_CFGSTR_SET_ERR

3 OS

BFD_PD-3-ERROR

3 PKT_INFRA

BFD_PD-3-NO_SYM

3 PKT_INFRA

BFM_API-3-LOCKING_ERROR

3 PKT_INFRA

BFM_API-3-MALLOC_FAILED

3 PKT_INFRA

BFM_API-4-PTCL_TYPE_WRONG

4 PKT_INFRA

BFM_API-7-DEBUG

7 PKT_INFRA

BFM-2-UNKNOWN_PLATFORM

2 PKT_INFRA

BFM-3-BCAST_FAILED

3 PKT_INFRA

BFM-3-EDM

3 PKT_INFRA

BFM-3-INTERNAL

3 PKT_INFRA

BFM-3-LOCKING_ERROR

3 PKT_INFRA

BFM-3-LSR

3 PKT_INFRA

BFM-3-MALLOC_FAILED

3 PKT_INFRA

BFM-3-MSGRPLY_FAILED

3 PKT_INFRA

BFM-3-POOL_CONFIG_FAILED

3 PKT_INFRA

BFM-3-POOL_STATUS_UNKNOWN

3 PKT_INFRA

BFM-3-REG_ERROR

3 PKT_INFRA

BFM-3-REGION

3 PKT_INFRA

BFM-3-STATUS_UNKNOWN

3 PKT_INFRA

BFM-3-SYSMGR_ERROR

3 PKT_INFRA

BFM-3-VER_SET_FAILED

3 PKT_INFRA

BFM-3-WARNING

3 PKT_INFRA

BFM-4-INIT_ERROR

4 PKT_INFRA

C12000_FWD_CLIENT_DLL-3-ERR

3 PKT_INFRA

CFM_OFFLOAD-4-STATS_DROP

4 PKT_INFRA

CFM_OFFLOAD-4-TIMEOUT_DROP

4 PKT_INFRA

DM-7-INFO

7 PKT_INFRA

EINT_NETIO_DLL-3-ATTACH_FAILED

3 PKT_INFRA

EINT_NETIO_DLL-3-BAD_COMMAND_RESULT

3 PKT_INFRA

EINT_NETIO_DLL-3BMA_OUT_OF_SEQUENCE

3 PKT_INFRA

EINT_NETIO_DLL-3-FATAL

3 PKT_INFRA

EINT_NETIO_DLL-3-FATAL_2

3 PKT_INFRA

EINT_NETIO_DLL-3-GET_CTX_ERR

3 PKT_INFRA

EINT_NETIO_DLL-3-IDB_CTX_NULL

3 PKT_INFRA

EINT_NETIO_DLL-3-INCORRECT_IDB

3 PKT_INFRA

EINT_NETIO_DLL-3-INFO

3 PKT_INFRA

EINT_NETIO_DLL-3-INVALID_PLIM_PORT

3 PKT_INFRA

EINT_NETIO_DLL-3-MALLOC_FAILED

3 PKT_INFRA

EINT_NETIO_DLL-3-MISSING_IDB

3 PKT_INFRA

EINT_NETIO_DLL-3-MUTEXOPFAIL

3 PKT_INFRA

EINT_NETIO_DLL-3NETIO_IDB_UNAVAILABLE

3 PKT_INFRA

EINT_NETIO_DLL-3NO_OUTSTANDING_BMA_REQ

3 PKT_INFRA

EINT_NETIO_DLL-3-NOT_YET_IMPLEMENTED

3 PKT_INFRA

EINT_NETIO_DLL-3-PKT_DROP

3 PKT_INFRA

EINT_NETIO_DLL-3QAD_EGRESS_Q_LOOKUP_ERR

3 PKT_INFRA

EINT_NETIO_DLL-3QAD_Q_PRODUCE_FAILED

3 PKT_INFRA

EINT_NETIO_DLL-3-QAD_RX_THREAD_ERR

3 PKT_INFRA

EINT_NETIO_DLL-3-SET_INPUT_IF_ERR

3 PKT_INFRA

ENCAP_RM-3-FATAL_ERR

3 PKT_INFRA

ENCAP_RM-3-MSG_SEND_FAILED

3 PKT_INFRA

ENCAP_RM-3-NONFATAL_ERR

3 PKT_INFRA

ENCAP_RM-3-OOR

3 PKT_INFRA

ENCAP_RM-6-INFO_MSG

6 PKT_INFRA

ERRDIS-3-AUTO_RECOVERY_RETRY_FAILED

3 PKT_INFRA

ERRDIS-3-DEBUG_INIT_FAILED

3 PKT_INFRA

ERRDIS-3-EVENT_BLOCK

3 PKT_INFRA

ERRDIS-3-MISCONFIGURED

3 PKT_INFRA

ERRDIS-3-SYSMGR_FAIL

3 PKT_INFRA

ERRDIS-4AUTO_RECOVERY_RETRY_DISABLED

4 PKT_INFRA

ERRDIS-4-BLOCK_UNTIL_ACTIVE

4 PKT_INFRA

ERRDIS-4-CFG_CLEANUP_FAILED

4 PKT_INFRA

ERRDIS-4-CFG_INIT_FAILED

4 PKT_INFRA

ERRDIS-4-DEBUG_CLEANUP_FAILED

4 PKT_INFRA

ERRDIS-4-DEBUG_CLEANUP_FAILED

4 PKT_INFRA

ERRDIS-4-EVM_CLEANUP_FAILED

4 PKT_INFRA

ERRDIS-4-EVM_INIT_FAILED

4 PKT_INFRA

ERRDIS-4-PROC_READY_FAILED

4 PKT_INFRA

ERRDIS-6-ERROR_DISABLE

6 PKT_INFRA

FEA_DLL-3-CHKPT_ERR

3 PKT_INFRA

FEA_DLL-3-MSTATS_ALLOC_ERR

3 PKT_INFRA

FEA_DLL-3-MSTATS_ERR

3 PKT_INFRA

FEA_DLL-3-PRM_INIT_ERR

3 PKT_INFRA

FEA_DLL-3-PRM_SSH_ERR

3 PKT_INFRA

FEA_DLL-3-REPRGM_ERROR

3 PKT_INFRA

FEA_DLL-3-REPRGM_ERROR

3 PKT_INFRA

FEA_DLL-3-STATS_ALLOC_ERR

3 PKT_INFRA

FEA_DLL-3-STATS_ERR

3 PKT_INFRA

FEA_DLL-3-TCAM_ERR

3 PKT_INFRA

FEA_DLL-3-TCAM_LIMIT

3 PKT_INFRA

FEA_DLL-3-UIDB_ERR

3 PKT_INFRA

FEA_DLL-3-UIDB_ERR

3 PKT_INFRA

FEA_DLL-4-TCAM_ERR

4 PKT_INFRA

FEAT_MGR-3DENY_IN_ACL_NOT_SUPPORTED

3 PKT_INFRA

FEAT_MGR-3MATCH_TYPE_IN_ACL_NOT_SUPPORTED

3 PKT_INFRA

FEAT_MGR-3-MSTATS_ALLOC_ERR

3 PKT_INFRA

FEAT_MGR-3-MSTATS_ERR

3 PKT_INFRA

FEAT_MGR-3-REPRGM_ERROR

3 PKT_INFRA

FEAT_MGR-3-TCAM_LIMIT

3 PKT_INFRA

FEAT_MGR-3-UIDB_ERR

3 PKT_INFRA

FEAT_MGR-4-TCAM_ERR

4 PKT_INFRA

FINT_N2N_NETIO-3-SET_MAPPING_FAILED

3 PKT_INFRA

FM-2-ALARM_CRIT

2 PKT_INFRA

FM-2-INFRA_FAIL

2 PKT_INFRA

FM-3-ALARM_ERR

3 PKT_INFRA

FM-3-EDM_REGISTER_FAILED

3 PKT_INFRA

FM-3-EVENT_CONN_CREATE

3 PKT_INFRA

FM-3-EVENT_CONN_OPEN_ALL

3 PKT_INFRA

FM-3-FAULT_ERROR

3 PKT_INFRA

FM-3-IM_API_FAILED

3 PKT_INFRA

FM-3-INIT_ERROR

3 PKT_INFRA

FM-3-MALLOC_FAILED

3 PKT_INFRA

FM-4-ALARM_WARNING

4 PKT_INFRA

FM-4-BACKEND_EDM_DATALIST_FAILED

4 PKT_INFRA

FM-4-BACKEND_EDM_GET_FAILED

4 PKT_INFRA

FM-4-BAG_FAILED

4 PKT_INFRA

FM-4-EVENT_CONN_NOTIFY

4 PKT_INFRA

FM-4-INVALID_ARGS

4 PKT_INFRA

FM-4-SYSDB_FAILED

4 PKT_INFRA

FM-6-DATAPATH_CONTROL_FAILED
FM-6-FAULT_DEBUG

6 PKT_INFRA
6 PKT_INFRA

FM-6-FAULT_INFO

6 PKT_INFRA

FM-6-INFO_GENERAL

6 PKT_INFRA

FMGR-3-DENY_IN_ACL_NOT_SUPPORTED

3 PKT_INFRA

FMGR-3-DENY_IN_ACL_NOT_SUPPORTED

3 PKT_INFRA

FMGR-3MATCH_TYPE_IN_ACL_NOT_SUPP_AFMON

3 PKT_INFRA

FMGR-3MATCH_TYPE_IN_ACL_NOT_SUPPORTED

3 PKT_INFRA

FMGR-3MATCH_TYPE_IN_ACL_NOT_SUPPORTED

3 PKT_INFRA

FMGR-3-SUB_ID_MSG_TOO_LARGE

3 PKT_INFRA

FMGR-3-SUPP_UDP_ONLY_AFMON

3 PKT_INFRA

FMGR-3-TCAM_MGR_ERROR

3 PKT_INFRA

FMGR-3-TCAM_MGR_QOSID_ALLOC_ERROR

3 PKT_INFRA

FMGR-3-V6_SRC_CMPR_ERR

3 PKT_INFRA

FMGR-4-UIDB_SET_WARNING

4 PKT_INFRA

FMGR-7-INIT_ERROR

7 PKT_INFRA

FWD_BASE_NETIO-3-MEM_ALLOC_FAILED

3 PKT_INFRA

FWD_BASE_NETIO-5INCORRECT_SAVE_DATA_LEN

5 PKT_INFRA

FWD_BASE_NETIO-5UNSUP_MAJOR_VERSION

5 PKT_INFRA

FWD_NETIO_DLL-3-ATTACH_FAILED

3 PKT_INFRA

FWD_NETIO_DLL-3-ATTACH_FAILED

3 PKT_INFRA

FWD_NETIO_DLL-3-BAD_COMMAND_RESULT

3 PKT_INFRA

FWD_NETIO_DLL-3BMA_OUT_OF_SEQUENCE

3 PKT_INFRA

FWD_NETIO_DLL-3EGRESSQ_CREATE_FAILED

3 PKT_INFRA

FWD_NETIO_DLL-3-ERR_MEM_ALLOC

3 PKT_INFRA

FWD_NETIO_DLL-3-ERROR

3 PKT_INFRA

FWD_NETIO_DLL-3FABRICQ_CREATE_FAILED

3 PKT_INFRA

FWD_NETIO_DLL-3-FATAL

3 PKT_INFRA

FWD_NETIO_DLL-3-FATAL_2

3 PKT_INFRA

FWD_NETIO_DLL-3-GET_CTX_ERR

3 PKT_INFRA

FWD_NETIO_DLL-3-IDB_CTX_NULL

3 PKT_INFRA

FWD_NETIO_DLL-3-INCORRECT_IDB

3 PKT_INFRA

FWD_NETIO_DLL-3-INCORRECT_IDB

3 PKT_INFRA

FWD_NETIO_DLL-3-INFO

3 PKT_INFRA

FWD_NETIO_DLL-3INGRESSQ_CREATE_FAILED

3 PKT_INFRA

FWD_NETIO_DLL-3-INVALID_PLIM_PORT

3 PKT_INFRA

FWD_NETIO_DLL-3-INVALID_PORT

3 PKT_INFRA

FWD_NETIO_DLL-3-MALLOC_FAILED

3 PKT_INFRA

FWD_NETIO_DLL-3-MISSING_IDB

3 PKT_INFRA

FWD_NETIO_DLL-3-MUTEXOPFAIL

3 PKT_INFRA

FWD_NETIO_DLL-3NETIO_IDB_UNAVAILABLE

3 PKT_INFRA

FWD_NETIO_DLL-3NO_OUTSTANDING_BMA_REQ

3 PKT_INFRA

FWD_NETIO_DLL-3-NOT_YET_IMPLEMENTED

3 PKT_INFRA

FWD_NETIO_DLL-3-PAK_PROC_ERR

3 PKT_INFRA

FWD_NETIO_DLL-3QAD_EGRESS_Q_LOOKUP_ERR

3 PKT_INFRA

FWD_NETIO_DLL-3QAD_Q_PRODUCE_FAILED

3 PKT_INFRA

FWD_NETIO_DLL-3-QAD_RX_THREAD_ERR

3 PKT_INFRA

FWD_NETIO_DLL-3-SET_INPUT_IF_ERR

3 PKT_INFRA

FWD_NETIO_DLL-5-UNEXPECTED_PKT

5 PKT_INFRA

FWD_NETIO_DLL-7-TXM_API_INFO

7 PKT_INFRA

FWD_NETIO_TOPAZ_DLL-3-ATTACH_FAILED

3 PKT_INFRA

FWD_NETIO_TOPAZ_DLL-3EGRESSQ_CREATE_FAILED

3 PKT_INFRA

FWD_NETIO_TOPAZ_DLL-3ERR_MEM_ALLOC

3 PKT_INFRA

FWD_NETIO_TOPAZ_DLL-3-ERROR

3 PKT_INFRA

FWD_NETIO_TOPAZ_DLL-3FABRICQ_CREATE_FAILED

3 PKT_INFRA

FWD_NETIO_TOPAZ_DLL-3-INCORRECT_IDB

3 PKT_INFRA

FWD_NETIO_TOPAZ_DLL-3INGRESSQ_CREATE_FAILED

3 PKT_INFRA

FWD_NETIO_TOPAZ_DLL-3-INVALID_PORT

3 PKT_INFRA

FWD_NETIO_TOPAZ_DLL-3-PAK_PROC_ERR

3 PKT_INFRA

FWD_TP_NETIO-3-DEBUG_FAIL

3 PKT_INFRA

FWD_TP_NETIO-3-DEBUG_GET_EVM_FAIL

3 PKT_INFRA

FWD_TP_NETIO-5-DEBUG_CLEANUP_FAIL

5 PKT_INFRA

FWD-3-CAPS_ADD_FAIL

3 PKT_INFRA

FWD-3-CHKPT_SAVE_FAILED

3 PKT_INFRA

FWD-3-FAILED

3 PKT_INFRA

FWD-3-USAGE

3 PKT_INFRA

FWD-4-NOT_YET_IMPLEMENTED

4 PKT_INFRA

FWD-6-IFMGR_REPLY_FAIL

6 PKT_INFRA

FWD-7SPECIFY_PLIM_INTERFACE_RETRIES_COMPL
ETE

7 PKT_INFRA

FWD-7SPECIFY_PLIM_INTERFACE_RETRY_QUEUED

7 PKT_INFRA

GIRO-4-CFG_RESTORE

4 PKT_INFRA

GIRO-4-CFG_RESTORE_SINGLE_INTF

4 PKT_INFRA

GIRO-4-CFG_SAVE

4 PKT_INFRA

GIRO-4-CFG_SAVE_SINGLE_INTF

4 PKT_INFRA

GIRO-6-ERROR_EXISTS

6 PKT_INFRA

HFR_PFI-3-INFRA_ERROR

3 PKT_INFRA

HFR_PFI-3SET_GLOBALS_FTRUNCATE_FAILED

3 PKT_INFRA

HFR_PFI-3-SET_GLOBALS_MMAP_FAILED

3 PKT_INFRA

HFR_PFI-3SET_GLOBALS_SHM_OPEN_FAILED

3 PKT_INFRA

ICPE_DPM-3-FAILED_TYPE_GET

3 PKT_INFRA

ICPE_DPM-3-INVALID_MSG

3 PKT_INFRA

ICPE_DPM-3-UDLD

3 PKT_INFRA

ICPE_DPM-7-CORRUPT_PERSISTENT_DATA

7 PKT_INFRA

ICPE_GCO-4-AUTHENTICATION_FAILURE

4 PKT_INFRA

ICPE_GCO-4-SATELLITE_LOGIN_FAILED

4 PKT_INFRA

ICPE_GCO-5-FAILED_TO_SET_PASSWORD

5 PKT_INFRA

ICPE_GCO-5-SATELLITE_STATUS

5 PKT_INFRA

ICPE_GCO-5-TRANSFER_INTERRUPT

5 PKT_INFRA

ICPE_GCO-5-VERSION_NOTCOMPATIBLE

5 PKT_INFRA

ICPE_GCO-6-INSTALL_DONE

6 PKT_INFRA

ICPE_GCO-6-SATELLITE_LOGIN_SUCCESS

6 PKT_INFRA

ICPE_GCO-6-TRANSFER_DONE

6 PKT_INFRA

ICPE_GCO-6VERSION_AUTO_UPGRADE_FAILED

6 PKT_INFRA

ICPE_GCO-6-VERSION_NOTCURRENT

6 PKT_INFRA

ICPE_LCO-5CROSSLINK_CONFIGURATION_REJECTED

5 PKT_INFRA

ICPE_LCO-5-SATELLITE_PORT_STATUS

5 PKT_INFRA

ICPE_OPM-4-CANNOT_SYNC

4 PKT_INFRA

ICPE_OPM-4-MEMBER_INCONSISTENCY

4 PKT_INFRA

IFMGR_ENCAP-3-BC_ERR

3 PKT_INFRA

IFMGR_ENCAP-3-INIT_ERR

3 PKT_INFRA

IFMGR_ENCAP-3-INIT_EVM_CREATE_ERR

3 PKT_INFRA

IFMGR_ENCAP-3INIT_IFMGR_CONN_CREATE_ERR

3 PKT_INFRA

IFMGR_ENCAP-3INIT_IFMGR_CONN_OPEN_ERR

3 PKT_INFRA

IFMGR_ENCAP-3-INIT_MALLOC_ERR

3 PKT_INFRA

IFMGR_ENCAP-3-INIT_SYSDB_BIND_ERR

3 PKT_INFRA

IFMGR_ENCAP-3-INIT_SYSDB_REG_ERR

3 PKT_INFRA

IFMGR_ENCAP-3-SYSDB_CREATE_SET_ERR

3 PKT_INFRA

IFMGR_ENCAP-3-SYSDB_DELETE_ERR

3 PKT_INFRA

IFMGR_ENCAP-3-SYSDB_ERR

3 PKT_INFRA

IFMGR_ENCAP-3-SYSDB_SET_ERR

3 PKT_INFRA

IFMGR-3-CAPS_DELETE

3 PKT_INFRA

IFMGR-3-INIT

3 PKT_INFRA

IFMGR-3-INVALID_TYPE_CONVERSION

3 PKT_INFRA

IFMGR-3-MISSING_RULES

3 PKT_INFRA

IFMGR-3-RULES_DUPLICATE_FEATURE_STR

3 PKT_INFRA

IFMGR-3-RULES_DUPLICATE_ID

3 PKT_INFRA

IFMGR-3-RULES_NO_ID

3 PKT_INFRA

IFMGR-3-RULES_PARSE_ERROR

3 PKT_INFRA

IFMGR-4-CAPS_NOT_ALLOWED

4 PKT_INFRA

IFMGR-4-CLIENT_API_ABUSE

4 PKT_INFRA

IFMGR-4-DROPPED_MSG

4 PKT_INFRA

IFMGR-4-LWM_UNEXPECTED_ERROR

4 PKT_INFRA

IFMGR-4-MAX_PACKET_SIZE_RANGE

4 PKT_INFRA

IFMGR-4-MTU_RANGE

4 PKT_INFRA

IFMGR-4-NOTIF_DELIVERY_FAILED

4 PKT_INFRA

IFMGR-6-IMPLICIT_DOWNLOAD_COMPLETE

6 PKT_INFRA

IFMGR-6-IMPLICIT_DOWNLOAD_FAIL

6 PKT_INFRA

IFMGR-6IMPLICIT_DOWNLOAD_IN_PROGRESS

6 PKT_INFRA

IFMGR-6-LWM_UNEXPECTED_PULSE

6 PKT_INFRA

IFMGR-6MUTEX_MONITOR_EVENT_REGISTER

6 PKT_INFRA

IFMGR-6-OUT_OF_MEMORY

6 PKT_INFRA

IFMGR-6-PREMATURE_OP

6 PKT_INFRA

IFMGR-6-SYSTEM_ERR

6 PKT_INFRA

IFO_EA_PD_STUB-7-INTF_CREATE_CALLED

7 PKT_INFRA

IFO_EA_PD_STUB-7-INTF_DELETE_CALLED

7 PKT_INFRA

IFO_EA_PD_STUB-7-INTF_UPDATE_CALLED

7 PKT_INFRA

IFO_EA-6-PD_ERROR_UL_INTF_REMOVAL

6 PKT_INFRA

IMAEDM-3-EVENT_CONN_CREATE_FAILED

3 PKT_INFRA

IMAEDM-3-EVENT_CONN_NOTIFY_FAILED

3 PKT_INFRA

IMAEDM-3-EVENT_CONN_OPEN_ALL_FAILED

3 PKT_INFRA

IMAEDM-3-INTERNAL_ERR

3 PKT_INFRA

IMAEDM-3-SYSMGR_PROC_READY_FAILED

3 PKT_INFRA

IMAEDM-3-TIMER_CREATE_FAILED

3 PKT_INFRA

IMAEDM-7-BAG_REG_FAILED

7 PKT_INFRA

IMAEDM-7-DEBUG_INIT_EVENT

7 PKT_INFRA

IMAEDM-7-DEBUG_REGISTER

7 PKT_INFRA

IMAEDM-7-EDM_INIT_FAILED

7 PKT_INFRA

IMAEDM-7-EVM_CREATE_FAILED

7 PKT_INFRA

IMATTR-3-DUPLICATE

3 PKT_INFRA

IMATTR-3-NOTIFY_FAILED

3 PKT_INFRA

IMATTR-3-SET_REPLY_FAILED

3 PKT_INFRA

IMATTR-3-UNKNOWN_PULSE

3 PKT_INFRA

INTF_MGBL-7-INIT_FAILED

7 PKT_INFRA

LINEPROTO-5-DAMPENING

5 PKT_INFRA

LINEPROTO-5-UPDOWN

5 PKT_INFRA

LINK-3-UPDOWN

3 PKT_INFRA

LINK-4-BERTADMINDOWN
LINK-4-BERTNOTRUNNING

4 PKT_INFRA
4 PKT_INFRA

LINK-4-BERTRESTART
LINK-4-BERTSTART
LINK-4-BERTSTATUS

4 PKT_INFRA
4 PKT_INFRA
4 PKT_INFRA

LINK-5-CHANGED

5 PKT_INFRA

LINK-5-DAMPENING

5 PKT_INFRA

LPTS_PA_FGID_DB-3-INFRA_FGID_ERR

3 PKT_INFRA

netio_debug-3-INIT_FAILED

3 PKT_INFRA

netio_debug-4-ASYNC_HANDLER

4 PKT_INFRA

netio_debug-4-EVENT_BLOCK

4 PKT_INFRA

NETIO-1-HSSD_SIZE_MISMATCH

1 PKT_INFRA

NETIO-1-HSSD_UNKNOWN

1 PKT_INFRA

NETIO-3-BAD_PUNT_NODE

3 PKT_INFRA

NETIO-3-DELETE_FINT

3 PKT_INFRA

NETIO-3-DLL_AUTOLOAD_FAILED

3 PKT_INFRA

NETIO-3-ERR_ARP

3 PKT_INFRA

NETIO-3-ERR_INIT

3 PKT_INFRA

NETIO-3-ERR_MEDIA_REGISTER

3 PKT_INFRA

NETIO-3-LTRACE_INIT

3 PKT_INFRA

NETIO-3-NULL_CALLBACKS

3 PKT_INFRA

NETIO-3-PAK_NETIO_MUTEX_LOCK

3 PKT_INFRA

NETIO-3-RESYNC_FAILED

3 PKT_INFRA

NETIO-3-SCRIPT_ERR_MEM_ALLOC

3 PKT_INFRA

NETIO-3-SCRIPT_FAIL

3 PKT_INFRA

NETIO-3-SELFMANAGE_FAILURE

3 PKT_INFRA

NETIO-3-STATS_SHM

3 PKT_INFRA

NETIO-4-BAD_PACKET

4 PKT_INFRA

NETIO-4-ERR_PACKET_INPUT

4 PKT_INFRA

NETIO-4-SCRIPT_WARNING

4 PKT_INFRA

NETIO-5-SELFMANAGE_CALLBACK_FAILED

5 PKT_INFRA

NETIO-5-SELFMANAGE_UPGRADE_NOTICE

5 PKT_INFRA

NETIO-6-SELFMANAGE_INFO

6 PKT_INFRA

NETIO-6-THREAD_MUTEX_FAILED

6 PKT_INFRA

NETIO-7-CREATE_IDB_FAILED

7 PKT_INFRA

NETIO-7DELETE_IDB_SUBINTF_ASSOC_FAILED

7 PKT_INFRA

NETIO-7-DELETE_IDB_SUBINTF_FAILED

7 PKT_INFRA

NETIO-7-INIT_FAILED

7 PKT_INFRA

PAK_CAPTURE-4-ECC_ERROR

4 PKT_INFRA

PAK-3-DEBUGINITFAIL

3 PKT_INFRA

PAK-3-MUTEX_DISALLOWED

3 PKT_INFRA

PAK-3-OWNERSHIP_PROCESS

3 PKT_INFRA

PAK-3-OWNERSHIP_PROCESS_FREE

3 PKT_INFRA

PAK-3-OWNERSHIP_QUEUE

3 PKT_INFRA

PAK-3-PTCL_LIST_NOT_NULL

3 PKT_INFRA

PAK-7-EXCEPTION_LITE

7 PKT_INFRA

PAK-7-GETNODENAMEFAIL

7 PKT_INFRA

PAK-7-SPP_TRYMAP

7 PKT_INFRA

PAKPLATFORM-3-CONNECTFAIL

3 PKT_INFRA

PAKPLATFORM-6-REGION_TOO_BIG

6 PKT_INFRA

PAKPLATFORM-6-SENDFAIL

6 PKT_INFRA

PAKSRV-2-MUTEX_REVIVAL_FAILED

2 PKT_INFRA

PAKSRV-3-BADPAK

3 PKT_INFRA

PAKSRV-3-DIAGFAIL

3 PKT_INFRA

PAKSRV-3-INITFAIL

3 PKT_INFRA

PAKSRV-3-MEM_ALLOC_FAILED

3 PKT_INFRA

PAKSRV-5-CLEAR_CORRUPT

5 PKT_INFRA

PAKSRV-7-BADPTCL_DUMP

7 PKT_INFRA

PAKSRV-7-BCASTFAIL

7 PKT_INFRA

PAKSRV-7-CHANCREATEFAIL

7 PKT_INFRA

PAKSRV-7-CHKPT_OP_FAILED

7 PKT_INFRA

PAKSRV-7-CHUNKCREATEFAIL

7 PKT_INFRA

PAKSRV-7-CONDWAITFAIL

7 PKT_INFRA

PAKSRV-7-DEBUGINITFAIL

7 PKT_INFRA

PAKSRV-7-DEQUEUEFAIL

7 PKT_INFRA

PAKSRV-7-ENQUEUEFAIL

7 PKT_INFRA

PAKSRV-7-EVM_ATTACH_FAILED

7 PKT_INFRA

PAKSRV-7-FSVFAIL

7 PKT_INFRA

PAKSRV-7-GET_RENDEZVOUS

7 PKT_INFRA

PAKSRV-7-GETPIDFAIL

7 PKT_INFRA

PAKSRV-7-HSSDFAIL

7 PKT_INFRA

PAKSRV-7-MEMUTILMAPFAIL

7 PKT_INFRA

PAKSRV-7-MSGREPLYFAIL

7 PKT_INFRA

PAKSRV-7-MUTEX_INIT_FAILED

7 PKT_INFRA

PAKSRV-7-MUTEX_MONREG_FAILED

7 PKT_INFRA

PAKSRV-7-MUTEX_OP_FAILED

7 PKT_INFRA

PAKSRV-7-PAKBCASTFAIL

7 PKT_INFRA

PAKSRV-7-PARTICLEINITFAIL

7 PKT_INFRA

PAKSRV-7-QSM_ADD_SERVICE

7 PKT_INFRA

PAKSRV-7-SIGALRM

7 PKT_INFRA

PAKSRV-7-SIGNAL

7 PKT_INFRA

PAKSRV-7-SYSMGR_GET_NODE_STATE

7 PKT_INFRA

PAKSRV-7-THREAD_ATTR_SET_FAILED

7 PKT_INFRA

PAKSRV-7-THREAD_CREATE_FAILED

7 PKT_INFRA

PAKSRV-7-THREAD_DETACH_FAILED

7 PKT_INFRA

PAKSRV-7-TIMER

7 PKT_INFRA

PAKWATCH-2-DEPLETION_CATASTROPHIC

2 PKT_INFRA

PAKWATCH-3-DEPLETION_CRITICAL

3 PKT_INFRA

PAKWATCH-3-PAK_DOUBLE_FREE

3 PKT_INFRA

PAKWATCH-3-PTCL_DOUBLE_FREE

3 PKT_INFRA

PAKWATCH-4-DEPLETION_WARNING

4 PKT_INFRA

PAKWATCH-4-PAK_HDR_INVALID

4 PKT_INFRA

PAKWATCH-6-DEPLETION_INFO

6 PKT_INFRA

PAKWATCH-6-HEADER_CORRUPTION

6 PKT_INFRA

PAKWATCH-6-INFO_BODY

6 PKT_INFRA

PAKWATCH-6-INFO_BODY2

6 PKT_INFRA

PAKWATCH-6-INFO_HEAD

6 PKT_INFRA

PAKWATCH-6-INFO_HEAD2

6 PKT_INFRA

PAKWATCH-6-LOC_INFO

6 PKT_INFRA

PAKWATCH-6-LOC_INFO2

6 PKT_INFRA

PAKWATCH-6-TRACEBACK

6 PKT_INFRA

PAKWATCH-6-USER_INFO

6 PKT_INFRA

PAKWATCH-6-USER_INFO2

6 PKT_INFRA

PLATFORM_ASR9K_NETIO_LIB-4FINT_IDB_NOT_FOUND

4 PKT_INFRA

PLATFORM_ASR9K_NETIO_LIB-4GET_MYNODEID_FAIL

4 PKT_INFRA

PLATFORM_ASR9K_PFI_LIB-3SET_GLOBALS_FAILED

3 PKT_INFRA

PLATFORM_C12000_NETIO_LIB-4FINT_IDB_NOT_FOUND

4 PKT_INFRA

PLATFORM_C12000_NETIO_LIB-4GET_MYNODEID_FAIL

4 PKT_INFRA

PLATFORM_C12000_NETIO_LIB-4GET_PPINDEX_INFO_FAIL

4 PKT_INFRA

PLATFORM_FWD-2-LOGICAL_PORT

2 PKT_INFRA

PLATFORM_FWD-3-ERROR

3 PKT_INFRA

PLATFORM_HFR_NETIO_LIB-4FINT_IDB_NOT_FOUND

4 PKT_INFRA

PLATFORM_HFR_NETIO_LIB-4GET_MYNODEID_FAIL

4 PKT_INFRA

PLATFORM_PFI-4-IFHANDLE_DECODE

4 PKT_INFRA

PLATFORM_PFI-4-INIT

4 PKT_INFRA

PLATFORM_SSE_NETIO_LIB-4FINT_IDB_NOT_FOUND

4 PKT_INFRA

PLATFORM_SSE_NETIO_LIB-4GET_MYNODEID_FAIL

4 PKT_INFRA

PQMON-6-QUEUE_DROP

6 PKT_INFRA

PQMON-6-QUEUE_HIGH_THRESH

6 PKT_INFRA

PQMON-6-QUEUE_LOW_THRESH

6 PKT_INFRA

PREF_COMPR_LIB-3-INTERNAL_ERR

3 PKT_INFRA

PREF_COMPR_LIB-6-V6_ANCHOR_PREFIX

6 PKT_INFRA

PREF_COMPR_LIB-6-V6_CMPR_FAILED

6 PKT_INFRA

protect_debug-3-INIT_FAILED

3 PKT_INFRA

protect_debug-7-DUMP_HANDLE

7 PKT_INFRA

protect_debug-7-DUMP_HANDLE_FTR

7 PKT_INFRA

protect_debug-7-DUMP_HANDLE_HDR

7 PKT_INFRA

PTP_OFFLOAD-3-PACKET_DROP

3 PKT_INFRA

PTP_OFFLOAD-4-STATS_DROP

4 PKT_INFRA

spp-0-EMERG

--

PKT_INFRA

spp-1-ALERT

1 PKT_INFRA

spp-2CLIENT_NOTIFY_FAILED_MAX_THRESHOLD

2 PKT_INFRA

spp-2-CRIT

2 PKT_INFRA

spp-2-SHM_ALLOC

2 PKT_INFRA

spp-3-CLIENT_LOCK_FAILURE

3 PKT_INFRA

spp-3-CLIENT_NOTIFY_FAILED

3 PKT_INFRA

spp-3-ERR

3 PKT_INFRA

spp-3-UNEXP_INT

3 PKT_INFRA

spp-3-UNEXP_PULSE

3 PKT_INFRA

spp-4-INIT_FAILED

4 PKT_INFRA

spp-4-MUTEX_MON

4 PKT_INFRA

spp-4-PKT_ALLOC_FAIL

4 PKT_INFRA

spp-4-PLUGIN_LOAD_FAILED

4 PKT_INFRA

spp-4-TIMER_FAILED

4 PKT_INFRA

spp-4-WARNING

4 PKT_INFRA

spp-5-NOTICE

5 PKT_INFRA

spp-6-INFO

6 PKT_INFRA

spp-6-INFO_TRACEBACK

6 PKT_INFRA

spp-7-DEBUG

7 PKT_INFRA

SVII_ADJ_LIB-3-ADJ_DATA_CORRUPT

3 PKT_INFRA

SVII_ADJ_LIB-3FOLLOW_STANDBY_MISMATCH

3 PKT_INFRA

SVII_ADJ_LIB-3-INIT_FAILED

3 PKT_INFRA

SVII_ADJ_LIB-3-SERVICE_FAILED

3 PKT_INFRA

SVII_ADJ_LIB-4-INTF_DB_INCONSISTENT

4 PKT_INFRA

SVII_ADJ_LIB-4-REFRESH_FAILED

4 PKT_INFRA

SVII_ADJ_LIB-4-RESTART_FAILED

4 PKT_INFRA

SVII_ADJ_LIB-4-SDIR_INVALID

4 PKT_INFRA

SVII_ADJ_LIB-4-SRV_CLEANUP_FAILED

4 PKT_INFRA

SVII_ADJ_MGR-3-ADJ_FAILED

3 PKT_INFRA

SVII_ADJ_MGR-3-ECM_ERROR_FAILED

3 PKT_INFRA

SVII_ADJ_MGR-3-INIT_FAILED

3 PKT_INFRA

SVII_ADJ_MGR-3-LOOP_FAILED

3 PKT_INFRA

SVII_ADJ_MGR-3-RECEIVE_MESSAGE

3 PKT_INFRA

SVII_ADJ_MGR-3-SYSMGR

3 PKT_INFRA

SVII_ADJ_MGR-4-RESTART

4 PKT_INFRA

SVII_ADJ_MGR-6-CERRNO_FAILED

6 PKT_INFRA

SW_OFFLOAD-4PROTOCOL_UPDATE_FAILED

4 PKT_INFRA

TCAM_MGR_LIB-3-INTERNAL_ERR

3 PKT_INFRA

TCAM_MGR_LIB-6-V6_CMPR_FAILED

6 PKT_INFRA

TCAM_MGR-2-INIT_INTERNAL_DATA

2 PKT_INFRA

TCAM_MGR-3-INTERNAL_ERR

3 PKT_INFRA

TCAM_MGR-6-V6_ANCHOR_PREFIX

6 PKT_INFRA

TOPAZ_PFI-3-INFRA_ERROR

3 PKT_INFRA

TOPAZ_PFI-3SET_GLOBALS_FTRUNCATE_FAILED

3 PKT_INFRA

TOPAZ_PFI-3-SET_GLOBALS_MMAP_FAILED

3 PKT_INFRA

TOPAZ_PFI-3SET_GLOBALS_SHM_OPEN_FAILED

3 PKT_INFRA

tunnel_ea-3-ACCOUNTING_ERROR

3 PKT_INFRA

tunnel_ea-3-DEBUG_INIT_FAILED

3 PKT_INFRA

tunnel_ea-3-DEBUG_INIT_FAILED

3 PKT_INFRA

tunnel_ea-3-EVENT_BLOCK_FAILED

3 PKT_INFRA

tunnel_ea-3-EVENT_BLOCK_FAILED

3 PKT_INFRA

tunnel_ea-3-EVM_CREATE_FAILED

3 PKT_INFRA

tunnel_ea-3-EVM_CREATE_FAILED

3 PKT_INFRA

tunnel_ea-3-IMP_INIT_FAILED

3 PKT_INFRA

tunnel_ea-3-IMP_INIT_FAILED

3 PKT_INFRA

tunnel_ea-3-PLATFORM_MANAGER_ERROR

3 PKT_INFRA

tunnel_ea-3-PLATFORM_MANAGER_ERROR

3 PKT_INFRA

tunnel_ea-3-PROC_READY_FAILED

3 PKT_INFRA

tunnel_ea-3-PROC_READY_FAILED

3 PKT_INFRA

tunnel_ea-3-STATS_INIT_FAILED

3 PKT_INFRA

tunnel_ea-3-STATS_INIT_FAILED

3 PKT_INFRA

TUNNEL-3-API_ERROR

3 PKT_INFRA

TUNNEL-3-API_ERROR_2

3 PKT_INFRA

TUNNEL-3-BAD_CHAIN

3 PKT_INFRA

TUNNEL-3-CONFIG_SCAN_FAILED

3 PKT_INFRA

TUNNEL-3-CURRENT_MAXIMUM_HIGH

3 PKT_INFRA

TUNNEL-3-CURRENT_MAXIMUM_LOW

3 PKT_INFRA

TUNNEL-3-CURRENT_MAXIMUM_REACHED

3 PKT_INFRA

TUNNEL-3-EVMGR_API_ERR

3 PKT_INFRA

TUNNEL-3-GENERIC

3 PKT_INFRA

TUNNEL-3-IM_ERR

3 PKT_INFRA

TUNNEL-3-INFRA_ERR

3 PKT_INFRA

TUNNEL-3-INIT_FAIL

3 PKT_INFRA

TUNNEL-3-NEGATIVE_CURRENT_COUNT

3 PKT_INFRA

TUNNEL-3-NO_INTERFACE

3 PKT_INFRA

TUNNEL-3-NULL_DPC

3 PKT_INFRA

TUNNEL-3-SYSDB_API_ERR

3 PKT_INFRA

TUNNEL-3-THREAD_API_ERR

3 PKT_INFRA

TUNNEL-3-UNKNOWN_HANDLE

3 PKT_INFRA

TUNNEL-3-UNKNOWN_MSG

3 PKT_INFRA

TUNNEL-6-DEBUG_ERROR

6 PKT_INFRA

TUNNEL-7-IFACE_NOT_UP

7 PKT_INFRA

UTIL_ASSERT-6-DUMPING_CORE

6 PKT_INFRA

VI_REPL-3-ISSU

3 PKT_INFRA

VI_REPL-3-REPLICATE

3 PKT_INFRA

VI_REPL-4-REPLICATOR_MSG

4 PKT_INFRA

VI_REPL-7-EVENT

7 PKT_INFRA

VI_REPL-7-INIT

7 PKT_INFRA

AFMON_EA_OOR-4-LC_FLOWS_OOR_GREEN

4 PLATFORM

AFMON_EA_OOR-4-LC_FLOWS_OOR_RED

4 PLATFORM

AFMON_EA_OOR-4-NP_FLOWS_OOR_GREEN

4 PLATFORM

AFMON_EA_OOR-4-NP_FLOWS_OOR_GREEN

4 PLATFORM

AFMON_EA_OOR-4-NP_FLOWS_OOR_RED

4 PLATFORM

AFMON_EA_OOR-4-NP_FLOWS_OOR_RED

4 PLATFORM

AFMON_EA_VERIFY-6-POLICY_ERROR

6 PLATFORM

AFMON_EA_VERIFY-6-POLICY_ERROR

6 PLATFORM

AFMON-3-AVL_TREE_CORRUPT

3 PLATFORM

AFMON-3-EA_DEBUG_INIT_FAIL

3 PLATFORM

AFMON-3-EA_LTRACE_INIT_FAIL

3 PLATFORM

AFMON-3-EA_POL_MOD_ROLLBACK_FAIL

3 PLATFORM

AFMON-3-ERR_EVENT_ATTACH

3 PLATFORM

AFMON-3-ERR_EVENT_INIT

3 PLATFORM

AFMON-3-ERR_EVM_CREATE

3 PLATFORM

AFMON-3-FAM_CONNECT_FAIL

3 PLATFORM

AFMON-3-IM_CONNECT_FAIL

3 PLATFORM

AFMON-3-MAX_FLOW_LIMIT

3 PLATFORM

AFMON-4-ERR_EVM_EVENT_BLOCK

4 PLATFORM

AHCI-2-DEV_HD0_NOT_RESPONDING

2 PLATFORM

AHCI-2-DEV_HD1_NOT_RESPONDING

2 PLATFORM

AIPC-5-EM_DEBUG_INIT_FAIL

5 PLATFORM

AIPC-6-EM_FABRIC_MEDIA_DISABLED

6 PLATFORM

ALPHA_DISPLAY-3-INIT

3 PLATFORM

ALPHA_DISPLAY-6-CHANGE

6 PLATFORM

ALPHA_DISPLAY-6-CHANGE

6 PLATFORM

ALPHA_DISPLAY-6-CHANGE

6 PLATFORM

ALPHA_DISPLAY-7-EVENT_ERROR

7 PLATFORM

APIV-3-LTRACE_DISPLAY_FAIL

3 PLATFORM

APIV-3-MODULE_INCOMPATIBLE

3 PLATFORM

APIV-3-SW_ERROR

3 PLATFORM

APIV-5-API_INCOMPATIBLE

5 PLATFORM

ARB_CLIENT-3-GEN_ERR

3 PLATFORM

ARB_CLIENT-3-GEN_ERR_1

3 PLATFORM

ARB_CLIENT-3-GEN_ERR_2

3 PLATFORM

ARB-3-ERR_INIT

3 PLATFORM

ARB-3-ERR_INIT

3 PLATFORM

ARB-3-ERR_MEM_ALLOC

3 PLATFORM

ARB-3-ERR_MEM_ALLOC

3 PLATFORM

ARB-5-ERR_CONT

5 PLATFORM

ARB-5-ERR_CONT

5 PLATFORM

ARB-7-ERR_EVM_CREATE

7 PLATFORM

ARB-7-ERR_EVM_CREATE

7 PLATFORM

ARB-7-ERR_EVM_NOTIFY

7 PLATFORM

ARB-7-ERR_EVM_NOTIFY

7 PLATFORM

ARB-7-ERR_EXIT

7 PLATFORM

ARB-7-ERR_EXIT

7 PLATFORM

ARB-7-ERR_LWM_EVENT_BLOCK

7 PLATFORM

ARB-7-ERR_LWM_EVENT_BLOCK

7 PLATFORM

ARB-7-ERR_LWM_REPLY

7 PLATFORM

ARB-7-ERR_LWM_REPLY

7 PLATFORM

ASM-0-FAULT_RECOVERY_ERR

--

PLATFORM

ASM-0-SW_INIT_ERR

--

PLATFORM

ASM-3-BADDESC_ERR

3 PLATFORM

ASM-3-CRC_ERR

3 PLATFORM

ASM-3-DEVICE_HALT

3 PLATFORM

ASM-3-FATAL

3 PLATFORM

ASM-3-FATAL_2

3 PLATFORM

ASM-3-FIA_INTFERR

3 PLATFORM

ASM-3-FIA_PARITYERR

3 PLATFORM

ASM-3-FQEMPTY_ERR

3 PLATFORM

ASM-3-FQEMPTY_ERR

3 PLATFORM

ASM-3-GEN_INFO

3 PLATFORM

ASM-3-HWINIT_INCOMPLETE

3 PLATFORM

ASM-3-INFO

3 PLATFORM

ASM-3-INTR_ENABLE_FAIL

3 PLATFORM

ASM-3-INTR_STATUS_GET_ERR

3 PLATFORM

ASM-3-MALLOC_FAILED

3 PLATFORM

ASM-3-NOT_AVAILABLE

3 PLATFORM

ASM-3-NOT_OPERATIONAL

3 PLATFORM

ASM-3-NOT_YET_IMPLEMENTED

3 PLATFORM

ASM-3-RESET_ERR

3 PLATFORM

ASM-4-BADDESC_ERR

4 PLATFORM

ASM-6-UNHANDLED_HALT

6 PLATFORM

ASM-6-UNHANDLED_INTR

6 PLATFORM

ASR9k_IFLX-5FRONT_PORT_SHARING_WARNING

5 PLATFORM

ASR9KPAGENT-3-ERROR_EXIT

3 PLATFORM

ASR9KPAGENT-6-OPERATION_INFO

6 PLATFORM

ASR9KPAGENT-7-OPERATION_DEBUG

7 PLATFORM

ASR9KPAGENT-7-OPERATION_FAIL

7 PLATFORM

AVSM_APIV-3-REGISTRATION_TIMEOUT

3 PLATFORM

AVSM_APIV-4-MOD_NOT_REGISTERED

4 PLATFORM

BCM_LOGGER-6-LOGGING_DEVICE

6 PLATFORM

BCM_LOGGER-7-COPY_FAILED

7 PLATFORM

BCM_LOGGER-7-DIR_NOT_FOUND

7 PLATFORM

BCM_LOGGER-7NO_STORAGE_DEVICE_FOUND

7 PLATFORM

BCM_SWITCH-2-LINK_SHUT_DOWN

2 PLATFORM

BCM_SWITCH-2-LINK_STATE_CHANGE

2 PLATFORM

BCM_SWITCH-2-MMU_ERR

2 PLATFORM

BCM_SWITCH-2-PCI_ERR

2 PLATFORM

BCM_SWITCH-2-PORT_HARDWARE_FAULT

2 PLATFORM

BCM_SWITCH-6-GBP_FULL

6 PLATFORM

BFD_HW_OFFLOAD-2-NO_MEMORY

2 PLATFORM

BFD_HW_OFFLOAD-4-CONFIG_WARNING

4 PLATFORM

BFD_HW_OFFLOAD-4-MODE_CHANGE

4 PLATFORM

BFD_HWOFFLOAD-4-LC_SCALE_LIMIT

4 PLATFORM

BFD_HWOFFLOAD-4-LC_TIMER_SCALE_LIMIT

4 PLATFORM

BFD_HWOFFLOAD-4-NP_SCALE_LIMIT

4 PLATFORM

BFD_HWOFFLOAD-4NP_TIMER_SCALE_LIMIT

4 PLATFORM

BMP_ALARM-3-EXCEED_LAG_ID_LIMIT_TRI

3 PLATFORM

BOOSTER_LIB-2-DMA_MMAP_FAIL

2 PLATFORM

BOOSTER_LIB-2-IPC_MMAP_FAIL

2 PLATFORM

BOOSTER_LIB-2-MMAP_FAIL

2 PLATFORM

BOOSTER_LIB-2-MMAP_FAILR

2 PLATFORM

BOOSTER_LIB-2-SHMEM_FAIL

2 PLATFORM

BOOSTER_LIB-2-SHUT_FAIL

2 PLATFORM

BOOSTER_LIB-2-SHUTDOWN

2 PLATFORM

BOOSTER_LIB-2-UBOOTSTAT_FAIL

2 PLATFORM

BOOSTER_LIB-6-INFO

6 PLATFORM

BOOSTER_SE-2-CONFIG_MALLOC_FAIL

2 PLATFORM

BOOSTER_SE-2-NULL_REQ_RESP

2 PLATFORM

BOOSTER-2-BFM_FAIL_ALLOC

2 PLATFORM

BOOSTER-2-BFM_FAIL_CHN

2 PLATFORM

BOOSTER-2-EVENT_HDLG_TFAIL

2 PLATFORM

BOOSTER-2-EVM_FAIL

2 PLATFORM

BOOSTER-2-EVNT_CHN_FAIL

2 PLATFORM

BOOSTER-2-LIC_INSTALL

2 PLATFORM

BOOSTER-2-MSGHDLR_FAIL

2 PLATFORM

BOOSTER-2-PIE_DEACT

2 PLATFORM

BOOSTER-2-SERVICE_PIE_DEACT

2 PLATFORM

BOOSTER-2-SHUT_FAIL

2 PLATFORM

BOOSTER-2-SHUT_SLEEP

2 PLATFORM

BOOSTER-2-SHUTDOWN

2 PLATFORM

BOOSTER-2-SYSMGR_BLK_FAIL

2 PLATFORM

BOOSTER-2-UPDPIE_FAIL

2 PLATFORM

BOOSTER-6-INFO

6 PLATFORM

BOOSTER-6-SHUT_CFG

6 PLATFORM

BP_SERVER-3-ERR_DSC_ELECTION

3 PLATFORM

BP_SERVER-3-ERR_INIT_DSC

3 PLATFORM

BP_SERVER-3-ERR_MAC_BLK_SIZE

3 PLATFORM

BP_SERVER-3-INVALID_BP_VERSION

3 PLATFORM

BP_SERVER-3-INVALID_CHASSIS_MODEL

3 PLATFORM

BP_SERVER-4-LOCAL_RQST_FAILED

4 PLATFORM

BP_SERVER-4-READ_NVRAM_FAILED

4 PLATFORM

BP_SERVER-4-REMOTE_RQST_FAILED

4 PLATFORM

BPE_CLIENT-3-ERR_CDI_BIND

3 PLATFORM

BPE_CLIENT-3-ERR_CDI_BIND_RACK

3 PLATFORM

BPE_CLIENT-3-ERR_CDI_UNBIND

3 PLATFORM

BPE-3-ERR

3 PLATFORM

BPE-3-ERR_INIT

3 PLATFORM

BPE-3-ERR_MEM_ALLOC

3 PLATFORM

BPE-5-ERR_CONT

5 PLATFORM

BPE-5-INFO

5 PLATFORM

BPE-7-DEBUG_CONT

7 PLATFORM

BPE-7-ERR_EVM_CREATE

7 PLATFORM

BPE-7-ERR_EVM_NOTIFY

7 PLATFORM

BPE-7-ERR_EXIT

7 PLATFORM

BPE-7-ERR_LWM_EVENT_BLOCK

7 PLATFORM

BPE-7-ERR_LWM_REPLY

7 PLATFORM

BRIDGE-1-DDR_BUS_BIT_STUCK_0

1 PLATFORM

BRIDGE-1-DDR_BUS_BIT_STUCK_1

1 PLATFORM

BRIDGE-1-DDR_BUS_BIT_STUCK_2

1 PLATFORM

BRIDGE-1-DDR_BUS_BIT_STUCK_3

1 PLATFORM

BRIDGE-1-DDR_LOSS_OF_SYNC_0

1 PLATFORM

BRIDGE-1-DDR_LOSS_OF_SYNC_1

1 PLATFORM

BRIDGE-1-DDR_LOSS_OF_SYNC_2

1 PLATFORM

BRIDGE-1-DDR_LOSS_OF_SYNC_3

1 PLATFORM

BRIDGE-1-FIFO_0_OFLOW_FIA2BR_0

1 PLATFORM

BRIDGE-1-FIFO_0_OFLOW_FIA2BR_1

1 PLATFORM

BRIDGE-1-FIFO_0_OFLOW_FIA2BR_2

1 PLATFORM

BRIDGE-1-FIFO_0_OFLOW_FIA2BR_3

1 PLATFORM

BRIDGE-1-FIFO_0_OFLOW_NPU2BR_0

1 PLATFORM

BRIDGE-1-FIFO_0_OFLOW_NPU2BR_1

1 PLATFORM

BRIDGE-1-FIFO_0_OFLOW_NPU2BR_2

1 PLATFORM

BRIDGE-1-FIFO_0_OFLOW_NPU2BR_3

1 PLATFORM

BRIDGE-1-FIFO_1_OFLOW_FIA2BR_0

1 PLATFORM

BRIDGE-1-FIFO_1_OFLOW_FIA2BR_1

1 PLATFORM

BRIDGE-1-FIFO_1_OFLOW_FIA2BR_2

1 PLATFORM

BRIDGE-1-FIFO_1_OFLOW_FIA2BR_3

1 PLATFORM

BRIDGE-1-FIFO_1_OFLOW_NPU2BR_0

1 PLATFORM

BRIDGE-1-FIFO_1_OFLOW_NPU2BR_1

1 PLATFORM

BRIDGE-1-FIFO_1_OFLOW_NPU2BR_2

1 PLATFORM

BRIDGE-1-FIFO_1_OFLOW_NPU2BR_3

1 PLATFORM

BRIDGE-1-MAC_0_TX_FIFO_OFLOW_0

1 PLATFORM

BRIDGE-1-MAC_0_TX_FIFO_OFLOW_1

1 PLATFORM

BRIDGE-1-MAC_0_TX_FIFO_OFLOW_2

1 PLATFORM

BRIDGE-1-MAC_0_TX_FIFO_OFLOW_3

1 PLATFORM

BRIDGE-1-MAC_1_TX_FIFO_OFLOW_0

1 PLATFORM

BRIDGE-1-MAC_1_TX_FIFO_OFLOW_1

1 PLATFORM

BRIDGE-1-MAC_1_TX_FIFO_OFLOW_2

1 PLATFORM

BRIDGE-1-MAC_1_TX_FIFO_OFLOW_3

1 PLATFORM

BRIDGE-1-NPU_0_EGR_Q_ERR_0

1 PLATFORM

BRIDGE-1-NPU_0_EGR_Q_ERR_1

1 PLATFORM

BRIDGE-1-NPU_0_EGR_Q_ERR_2

1 PLATFORM

BRIDGE-1-NPU_0_EGR_Q_ERR_3

1 PLATFORM

BRIDGE-1-NPU_0_LOSS_OF_SYNC_0

1 PLATFORM

BRIDGE-1-NPU_0_LOSS_OF_SYNC_1

1 PLATFORM

BRIDGE-1-NPU_0_LOSS_OF_SYNC_2

1 PLATFORM

BRIDGE-1-NPU_0_LOSS_OF_SYNC_3

1 PLATFORM

BRIDGE-1-NPU_0_SCH_MEMP_ERR_0

1 PLATFORM

BRIDGE-1-NPU_0_SCH_MEMP_ERR_1

1 PLATFORM

BRIDGE-1-NPU_0_SCH_MEMP_ERR_2

1 PLATFORM

BRIDGE-1-NPU_0_SCH_MEMP_ERR_3

1 PLATFORM

BRIDGE-1-NPU_0_XAUI_PLL_LOCK_0

1 PLATFORM

BRIDGE-1-NPU_0_XAUI_PLL_LOCK_1

1 PLATFORM

BRIDGE-1-NPU_0_XAUI_PLL_LOCK_2

1 PLATFORM

BRIDGE-1-NPU_0_XAUI_PLL_LOCK_3

1 PLATFORM

BRIDGE-1-NPU_0_XAUI_RDY_0

1 PLATFORM

BRIDGE-1-NPU_0_XAUI_RDY_1

1 PLATFORM

BRIDGE-1-NPU_0_XAUI_RDY_2

1 PLATFORM

BRIDGE-1-NPU_0_XAUI_RDY_3

1 PLATFORM

BRIDGE-1-NPU_1_EGR_Q_ERR_0

1 PLATFORM

BRIDGE-1-NPU_1_EGR_Q_ERR_1

1 PLATFORM

BRIDGE-1-NPU_1_EGR_Q_ERR_2

1 PLATFORM

BRIDGE-1-NPU_1_EGR_Q_ERR_3

1 PLATFORM

BRIDGE-1-NPU_1_LOSS_OF_SYNC_0

1 PLATFORM

BRIDGE-1-NPU_1_LOSS_OF_SYNC_1

1 PLATFORM

BRIDGE-1-NPU_1_LOSS_OF_SYNC_2

1 PLATFORM

BRIDGE-1-NPU_1_LOSS_OF_SYNC_3

1 PLATFORM

BRIDGE-1-NPU_1_SCH_MEMP_ERR_0

1 PLATFORM

BRIDGE-1-NPU_1_SCH_MEMP_ERR_1

1 PLATFORM

BRIDGE-1-NPU_1_SCH_MEMP_ERR_2

1 PLATFORM

BRIDGE-1-NPU_1_SCH_MEMP_ERR_3

1 PLATFORM

BRIDGE-1-NPU_1_XAUI_PLL_LOCK_0

1 PLATFORM

BRIDGE-1-NPU_1_XAUI_PLL_LOCK_1

1 PLATFORM

BRIDGE-1-NPU_1_XAUI_PLL_LOCK_2

1 PLATFORM

BRIDGE-1-NPU_1_XAUI_PLL_LOCK_3

1 PLATFORM

BRIDGE-1-NPU_1_XAUI_RDY_0

1 PLATFORM

BRIDGE-1-NPU_1_XAUI_RDY_1

1 PLATFORM

BRIDGE-1-NPU_1_XAUI_RDY_2

1 PLATFORM

BRIDGE-1-NPU_1_XAUI_RDY_3

1 PLATFORM

BRIDGE-1-QDR_DATABIT_STUCK_0

1 PLATFORM

BRIDGE-1-QDR_DATABIT_STUCK_1

1 PLATFORM

BRIDGE-1-QDR_DATABIT_STUCK_2

1 PLATFORM

BRIDGE-1-QDR_DATABIT_STUCK_3

1 PLATFORM

BRIDGE-1-QDR_M_FREE_EMPTY_0

1 PLATFORM

BRIDGE-1-QDR_M_FREE_EMPTY_1

1 PLATFORM

BRIDGE-1-QDR_M_FREE_EMPTY_2

1 PLATFORM

BRIDGE-1-QDR_M_FREE_EMPTY_3

1 PLATFORM

BRIDGE-1-QDR_MEM_ECC_FAIL_0

1 PLATFORM

BRIDGE-1-QDR_MEM_ECC_FAIL_1

1 PLATFORM

BRIDGE-1-QDR_MEM_ECC_FAIL_2

1 PLATFORM

BRIDGE-1-QDR_MEM_ECC_FAIL_3

1 PLATFORM

BRIDGE-1-QDR_MEM_SELFTEST_FAIL_0

1 PLATFORM

BRIDGE-1-QDR_MEM_SELFTEST_FAIL_1

1 PLATFORM

BRIDGE-1-QDR_MEM_SELFTEST_FAIL_2

1 PLATFORM

BRIDGE-1-QDR_MEM_SELFTEST_FAIL_3

1 PLATFORM

BRIDGE-1-REG_ACCESS_FAIL_0

1 PLATFORM

BRIDGE-1-REG_ACCESS_FAIL_1

1 PLATFORM

BRIDGE-1-REG_ACCESS_FAIL_2

1 PLATFORM

BRIDGE-1-REG_ACCESS_FAIL_3

1 PLATFORM

BRIDGE-1-STATEMC_0_ERR1_0

1 PLATFORM

BRIDGE-1-STATEMC_0_ERR1_1

1 PLATFORM

BRIDGE-1-STATEMC_0_ERR1_2

1 PLATFORM

BRIDGE-1-STATEMC_0_ERR1_3

1 PLATFORM

BRIDGE-1-STATEMC_0_ERR2_0

1 PLATFORM

BRIDGE-1-STATEMC_0_ERR2_1

1 PLATFORM

BRIDGE-1-STATEMC_0_ERR2_2

1 PLATFORM

BRIDGE-1-STATEMC_0_ERR2_3

1 PLATFORM

BRIDGE-1-STATEMC_0_ERR3_0

1 PLATFORM

BRIDGE-1-STATEMC_0_ERR3_1

1 PLATFORM

BRIDGE-1-STATEMC_0_ERR3_2

1 PLATFORM

BRIDGE-1-STATEMC_0_ERR3_3

1 PLATFORM

BRIDGE-1-STATEMC_1_ERR1_0

1 PLATFORM

BRIDGE-1-STATEMC_1_ERR1_1

1 PLATFORM

BRIDGE-1-STATEMC_1_ERR1_2

1 PLATFORM

BRIDGE-1-STATEMC_1_ERR1_3

1 PLATFORM

BRIDGE-1-STATEMC_1_ERR2_0

1 PLATFORM

BRIDGE-1-STATEMC_1_ERR2_1

1 PLATFORM

BRIDGE-1-STATEMC_1_ERR2_2

1 PLATFORM

BRIDGE-1-STATEMC_1_ERR2_3

1 PLATFORM

BRIDGE-1-STATEMC_1_ERR3_0

1 PLATFORM

BRIDGE-1-STATEMC_1_ERR3_1

1 PLATFORM

BRIDGE-1-STATEMC_1_ERR3_2

1 PLATFORM

BRIDGE-1-STATEMC_1_ERR3_3

1 PLATFORM

BRIDGE-1-XAUI_0_CHAN_SYNC_0

1 PLATFORM

BRIDGE-1-XAUI_0_CHAN_SYNC_1

1 PLATFORM

BRIDGE-1-XAUI_0_CHAN_SYNC_2

1 PLATFORM

BRIDGE-1-XAUI_0_CHAN_SYNC_3

1 PLATFORM

BRIDGE-1-XAUI_0_CHAR_ALIGN_0

1 PLATFORM

BRIDGE-1-XAUI_0_CHAR_ALIGN_1

1 PLATFORM

BRIDGE-1-XAUI_0_CHAR_ALIGN_2

1 PLATFORM

BRIDGE-1-XAUI_0_CHAR_ALIGN_3

1 PLATFORM

BRIDGE-1-XAUI_0_MGT_CV_0

1 PLATFORM

BRIDGE-1-XAUI_0_MGT_CV_1

1 PLATFORM

BRIDGE-1-XAUI_0_MGT_CV_2

1 PLATFORM

BRIDGE-1-XAUI_0_MGT_CV_3

1 PLATFORM

BRIDGE-1-XAUI_0_RX_ALIGN_LOSS_0

1 PLATFORM

BRIDGE-1-XAUI_0_RX_ALIGN_LOSS_1

1 PLATFORM

BRIDGE-1-XAUI_0_RX_ALIGN_LOSS_2

1 PLATFORM

BRIDGE-1-XAUI_0_RX_ALIGN_LOSS_3

1 PLATFORM

BRIDGE-1-XAUI_0_STAT_VEC_0

1 PLATFORM

BRIDGE-1-XAUI_0_STAT_VEC_1

1 PLATFORM

BRIDGE-1-XAUI_0_STAT_VEC_2

1 PLATFORM

BRIDGE-1-XAUI_0_STAT_VEC_3

1 PLATFORM

BRIDGE-1-XAUI_0_TX_FIFO_OFLOW_0

1 PLATFORM

BRIDGE-1-XAUI_0_TX_FIFO_OFLOW_1

1 PLATFORM

BRIDGE-1-XAUI_0_TX_FIFO_OFLOW_2

1 PLATFORM

BRIDGE-1-XAUI_0_TX_FIFO_OFLOW_3

1 PLATFORM

BRIDGE-1-XAUI_1_CHAN_SYNC_0

1 PLATFORM

BRIDGE-1-XAUI_1_CHAN_SYNC_1

1 PLATFORM

BRIDGE-1-XAUI_1_CHAN_SYNC_2

1 PLATFORM

BRIDGE-1-XAUI_1_CHAN_SYNC_3

1 PLATFORM

BRIDGE-1-XAUI_1_CHAR_ALIGN_0

1 PLATFORM

BRIDGE-1-XAUI_1_CHAR_ALIGN_1

1 PLATFORM

BRIDGE-1-XAUI_1_CHAR_ALIGN_2

1 PLATFORM

BRIDGE-1-XAUI_1_CHAR_ALIGN_3

1 PLATFORM

BRIDGE-1-XAUI_1_MGT_CV_0

1 PLATFORM

BRIDGE-1-XAUI_1_MGT_CV_1

1 PLATFORM

BRIDGE-1-XAUI_1_MGT_CV_2

1 PLATFORM

BRIDGE-1-XAUI_1_MGT_CV_3

1 PLATFORM

BRIDGE-1-XAUI_1_RX_ALIGN_LOSS_0

1 PLATFORM

BRIDGE-1-XAUI_1_RX_ALIGN_LOSS_1

1 PLATFORM

BRIDGE-1-XAUI_1_RX_ALIGN_LOSS_2

1 PLATFORM

BRIDGE-1-XAUI_1_RX_ALIGN_LOSS_3

1 PLATFORM

BRIDGE-1-XAUI_1_STAT_VEC_0

1 PLATFORM

BRIDGE-1-XAUI_1_STAT_VEC_1

1 PLATFORM

BRIDGE-1-XAUI_1_STAT_VEC_2

1 PLATFORM

BRIDGE-1-XAUI_1_STAT_VEC_3

1 PLATFORM

BRIDGE-1-XAUI_1_TX_FIFO_OFLOW_0

1 PLATFORM

BRIDGE-1-XAUI_1_TX_FIFO_OFLOW_1

1 PLATFORM

BRIDGE-1-XAUI_1_TX_FIFO_OFLOW_2

1 PLATFORM

BRIDGE-1-XAUI_1_TX_FIFO_OFLOW_3

1 PLATFORM

BRIDGE-1-XAUI_A_DATABUS_STUCK_0

1 PLATFORM

BRIDGE-1-XAUI_A_DATABUS_STUCK_1

1 PLATFORM

BRIDGE-1-XAUI_A_DATABUS_STUCK_2

1 PLATFORM

BRIDGE-1-XAUI_A_DATABUS_STUCK_3

1 PLATFORM

BRIDGE-2-DEC_A_CRC_ERR_0

2 PLATFORM

BRIDGE-2-DEC_A_CRC_ERR_1

2 PLATFORM

BRIDGE-2-DEC_A_FRAME_ERR_0

2 PLATFORM

BRIDGE-2-DEC_A_FRAME_ERR_1

2 PLATFORM

BRIDGE-2-DEC_A_PKT_LEN_ERR_0

2 PLATFORM

BRIDGE-2-DEC_A_PKT_LEN_ERR_1

2 PLATFORM

BRIDGE-2-DEC_A_PWM_ERR_0

2 PLATFORM

BRIDGE-2-DEC_A_PWM_ERR_1

2 PLATFORM

BRIDGE-2-DEC_A_TYPE_DISABLED_0

2 PLATFORM

BRIDGE-2-DEC_A_TYPE_DISABLED_1

2 PLATFORM

BRIDGE-2-EGR_LONG_PKT_0_0

2 PLATFORM

BRIDGE-2-EGR_LONG_PKT_0_1

2 PLATFORM

BRIDGE-2-EGR_LONG_PKT_1_0

2 PLATFORM

BRIDGE-2-EGR_LONG_PKT_1_1

2 PLATFORM

BRIDGE-2-EGR_NPH_LEN_0_0

2 PLATFORM

BRIDGE-2-EGR_NPH_LEN_0_1

2 PLATFORM

BRIDGE-2-EGR_NPH_LEN_1_0

2 PLATFORM

BRIDGE-2-EGR_NPH_LEN_1_1

2 PLATFORM

BRIDGE-2EGR_SEG_DATA_FIFO_OFLOW_0_0

2 PLATFORM

BRIDGE-2EGR_SEG_DATA_FIFO_OFLOW_0_1

2 PLATFORM

BRIDGE-2EGR_SEG_DATA_FIFO_OFLOW_1_0

2 PLATFORM

BRIDGE-2EGR_SEG_DATA_FIFO_OFLOW_1_1

2 PLATFORM

BRIDGE-2EGR_SEG_HDR_EXT_FIFO_OFLOW_0_0

2 PLATFORM

BRIDGE-2EGR_SEG_HDR_EXT_FIFO_OFLOW_0_1

2 PLATFORM

BRIDGE-2EGR_SEG_HDR_EXT_FIFO_OFLOW_1_0

2 PLATFORM

BRIDGE-2EGR_SEG_HDR_EXT_FIFO_OFLOW_1_1

2 PLATFORM

BRIDGE-2-EGR_SEG_HDR_FIFO_OFLOW_0_0

2 PLATFORM

BRIDGE-2-EGR_SEG_HDR_FIFO_OFLOW_0_1

2 PLATFORM

BRIDGE-2-EGR_SEG_HDR_FIFO_OFLOW_1_0

2 PLATFORM

BRIDGE-2-EGR_SEG_HDR_FIFO_OFLOW_1_1

2 PLATFORM

BRIDGE-2-EGR_SGT_FIFO_OFLOW_0_0

2 PLATFORM

BRIDGE-2-EGR_SGT_FIFO_OFLOW_0_1

2 PLATFORM

BRIDGE-2-EGR_SGT_FIFO_OFLOW_1_0

2 PLATFORM

BRIDGE-2-EGR_SGT_FIFO_OFLOW_1_1

2 PLATFORM

BRIDGE-2EGR_SGT_HDR_EXT_FIFO_OFLOW_0_0

2 PLATFORM

BRIDGE-2EGR_SGT_HDR_EXT_FIFO_OFLOW_0_1

2 PLATFORM

BRIDGE-2EGR_SGT_HDR_EXT_FIFO_OFLOW_1_0

2 PLATFORM

BRIDGE-2EGR_SGT_HDR_EXT_FIFO_OFLOW_1_1

2 PLATFORM

BRIDGE-2-EGR_SGT2_FIFO_OFLOW_0_0

2 PLATFORM

BRIDGE-2-EGR_SGT2_FIFO_OFLOW_0_1

2 PLATFORM

BRIDGE-2-EGR_SGT2_FIFO_OFLOW_1_0

2 PLATFORM

BRIDGE-2-EGR_SGT2_FIFO_OFLOW_1_1

2 PLATFORM

BRIDGE-2-EGR_SP_NOT_ZERO_0_0

2 PLATFORM

BRIDGE-2-EGR_SP_NOT_ZERO_0_1

2 PLATFORM

BRIDGE-2-EGR_SP_NOT_ZERO_1_0

2 PLATFORM

BRIDGE-2-EGR_SP_NOT_ZERO_1_1

2 PLATFORM

BRIDGE-2-GST_JUMP_ERR_0

2 PLATFORM

BRIDGE-2-GST_JUMP_ERR_1

2 PLATFORM

BRIDGE-2-GST_PWM_TIMEOUT_0

2 PLATFORM

BRIDGE-2-GST_PWM_TIMEOUT_1

2 PLATFORM

BRIDGE-2-GST_SYNC_ERR_0

2 PLATFORM

BRIDGE-2-GST_SYNC_ERR_1

2 PLATFORM

BRIDGE-2-ING_INV_LEN_0

2 PLATFORM

BRIDGE-2-ING_INV_LEN_1

2 PLATFORM

BRIDGE-2-ING_L4_ARRAY_OFLOW_0

2 PLATFORM

BRIDGE-2-ING_L4_ARRAY_OFLOW_1

2 PLATFORM

BRIDGE-2-ING_L4_ARRAY_UFLOW_0

2 PLATFORM

BRIDGE-2-ING_L4_ARRAY_UFLOW_1

2 PLATFORM

BRIDGE-2-MAC_0_RX_FRAME_ERR_0

2 PLATFORM

BRIDGE-2-MAC_0_RX_FRAME_ERR_1

2 PLATFORM

BRIDGE-2-MAC_0_RX_FRAME_ERR_2

2 PLATFORM

BRIDGE-2-MAC_0_RX_FRAME_ERR_3

2 PLATFORM

BRIDGE-2-MAC_1_RX_FRAME_ERR_0

2 PLATFORM

BRIDGE-2-MAC_1_RX_FRAME_ERR_1

2 PLATFORM

BRIDGE-2-MAC_1_RX_FRAME_ERR_2

2 PLATFORM

BRIDGE-2-MAC_1_RX_FRAME_ERR_3

2 PLATFORM

BRIDGE-2-MCAST_PAGE_ERR_0

2 PLATFORM

BRIDGE-2-MCAST_PAGE_ERR_1

2 PLATFORM

BRIDGE-2-MCAST_PAGE_ERR_2

2 PLATFORM

BRIDGE-2-MCAST_PAGE_ERR_3

2 PLATFORM

BRIDGE-2-NPU_0_FC_DIP2_ERR_0

2 PLATFORM

BRIDGE-2-NPU_0_FC_DIP2_ERR_1

2 PLATFORM

BRIDGE-2-NPU_0_FC_DIP2_ERR_2

2 PLATFORM

BRIDGE-2-NPU_0_FC_DIP2_ERR_3

2 PLATFORM

BRIDGE-2-NPU_0_FC_OOS_0

2 PLATFORM

BRIDGE-2-NPU_0_FC_OOS_1

2 PLATFORM

BRIDGE-2-NPU_0_FC_OOS_2

2 PLATFORM

BRIDGE-2-NPU_0_FC_OOS_3

2 PLATFORM

BRIDGE-2-NPU_0_SCH_0_HANG_0

2 PLATFORM

BRIDGE-2-NPU_0_TS_UPDATE_ERR_0

2 PLATFORM

BRIDGE-2-NPU_0_TS_UPDATE_ERR_1

2 PLATFORM

BRIDGE-2-NPU_1_FC_DIP2_ERR_0

2 PLATFORM

BRIDGE-2-NPU_1_FC_DIP2_ERR_1

2 PLATFORM

BRIDGE-2-NPU_1_FC_DIP2_ERR_2

2 PLATFORM

BRIDGE-2-NPU_1_FC_DIP2_ERR_3

2 PLATFORM

BRIDGE-2-NPU_1_FC_OOS_0

2 PLATFORM

BRIDGE-2-NPU_1_FC_OOS_1

2 PLATFORM

BRIDGE-2-NPU_1_FC_OOS_2

2 PLATFORM

BRIDGE-2-NPU_1_FC_OOS_3

2 PLATFORM

BRIDGE-2-NPU_1_TS_UPDATE_ERR_0

2 PLATFORM

BRIDGE-2-NPU_1_TS_UPDATE_ERR_1

2 PLATFORM

BRIDGE-2-PAR_MERR_0

2 PLATFORM

BRIDGE-2-PAR_MERR_1

2 PLATFORM

BRIDGE-2-PAR_SERR_0

2 PLATFORM

BRIDGE-2-PAR_SERR_1

2 PLATFORM

BRIDGE-2-QDR_M_WR_ERR_0

2 PLATFORM

BRIDGE-2-QDR_M_WR_ERR_1

2 PLATFORM

BRIDGE-2-QDR_M_WR_ERR_2

2 PLATFORM

BRIDGE-2-QDR_M_WR_ERR_3

2 PLATFORM

BRIDGE-2-SCH_0_HANG_0

2 PLATFORM

BRIDGE-2-SCH_0_HANG_1

2 PLATFORM

BRIDGE-2-SCH_1_HANG_0

2 PLATFORM

BRIDGE-2-SCH_1_HANG_1

2 PLATFORM

BRIDGE-2-XAUI_0_HQ_FULL_0

2 PLATFORM

BRIDGE-2-XAUI_0_HQ_FULL_1

2 PLATFORM

BRIDGE-2-XAUI_0_HQ_OFLOW_0

2 PLATFORM

BRIDGE-2-XAUI_0_HQ_OFLOW_1

2 PLATFORM

BRIDGE-2-XAUI_0_HQ_PKT_LEN_0

2 PLATFORM

BRIDGE-2-XAUI_0_HQ_PKT_LEN_1

2 PLATFORM

BRIDGE-2-XAUI_0_HQ_SEQ_0

2 PLATFORM

BRIDGE-2-XAUI_0_HQ_SEQ_1

2 PLATFORM

BRIDGE-2-XAUI_0_LQ_FULL_0

2 PLATFORM

BRIDGE-2-XAUI_0_LQ_FULL_1

2 PLATFORM

BRIDGE-2-XAUI_0_LQ_OFLOW_0

2 PLATFORM

BRIDGE-2-XAUI_0_LQ_OFLOW_1

2 PLATFORM

BRIDGE-2-XAUI_0_LQ_PKT_LEN_0

2 PLATFORM

BRIDGE-2-XAUI_0_LQ_PKT_LEN_1

2 PLATFORM

BRIDGE-2-XAUI_0_LQ_SEQ_0

2 PLATFORM

BRIDGE-2-XAUI_0_LQ_SEQ_1

2 PLATFORM

BRIDGE-2-XAUI_0_MQ_FULL_0

2 PLATFORM

BRIDGE-2-XAUI_0_MQ_FULL_1

2 PLATFORM

BRIDGE-2-XAUI_0_MQ_OFLOW_0

2 PLATFORM

BRIDGE-2-XAUI_0_MQ_OFLOW_1

2 PLATFORM

BRIDGE-2-XAUI_0_MQ_PKT_LEN_0

2 PLATFORM

BRIDGE-2-XAUI_0_MQ_PKT_LEN_1

2 PLATFORM

BRIDGE-2-XAUI_0_MQ_SEQ_0

2 PLATFORM

BRIDGE-2-XAUI_0_MQ_SEQ_1

2 PLATFORM

BRIDGE-2-XAUI_1_HQ_FULL_0

2 PLATFORM

BRIDGE-2-XAUI_1_HQ_FULL_1

2 PLATFORM

BRIDGE-2-XAUI_1_HQ_OFLOW_0

2 PLATFORM

BRIDGE-2-XAUI_1_HQ_OFLOW_1

2 PLATFORM

BRIDGE-2-XAUI_1_HQ_PKT_LEN_0

2 PLATFORM

BRIDGE-2-XAUI_1_HQ_PKT_LEN_1

2 PLATFORM

BRIDGE-2-XAUI_1_HQ_SEQ_0

2 PLATFORM

BRIDGE-2-XAUI_1_HQ_SEQ_1

2 PLATFORM

BRIDGE-2-XAUI_1_LQ_FULL_0

2 PLATFORM

BRIDGE-2-XAUI_1_LQ_FULL_1

2 PLATFORM

BRIDGE-2-XAUI_1_LQ_OFLOW_0

2 PLATFORM

BRIDGE-2-XAUI_1_LQ_OFLOW_1

2 PLATFORM

BRIDGE-2-XAUI_1_LQ_PKT_LEN_0

2 PLATFORM

BRIDGE-2-XAUI_1_LQ_PKT_LEN_1

2 PLATFORM

BRIDGE-2-XAUI_1_LQ_SEQ_0

2 PLATFORM

BRIDGE-2-XAUI_1_LQ_SEQ_1

2 PLATFORM

BRIDGE-2-XAUI_1_MQ_FULL_0

2 PLATFORM

BRIDGE-2-XAUI_1_MQ_FULL_1

2 PLATFORM

BRIDGE-2-XAUI_1_MQ_OFLOW_0

2 PLATFORM

BRIDGE-2-XAUI_1_MQ_OFLOW_1

2 PLATFORM

BRIDGE-2-XAUI_1_MQ_PKT_LEN_0

2 PLATFORM

BRIDGE-2-XAUI_1_MQ_PKT_LEN_1

2 PLATFORM

BRIDGE-2-XAUI_1_MQ_SEQ_0

2 PLATFORM

BRIDGE-2-XAUI_1_MQ_SEQ_1

2 PLATFORM

BRIDGE-3-CHKSUM_ERR_0_FIA_0

3 PLATFORM

BRIDGE-3-CHKSUM_ERR_0_FIA_1

3 PLATFORM

BRIDGE-3-CHKSUM_ERR_0_FIA_2

3 PLATFORM

BRIDGE-3-CHKSUM_ERR_0_FIA_3

3 PLATFORM

BRIDGE-3-CHKSUM_ERR_1_FIA_0

3 PLATFORM

BRIDGE-3-CHKSUM_ERR_1_FIA_1

3 PLATFORM

BRIDGE-3-CHKSUM_ERR_1_FIA_2

3 PLATFORM

BRIDGE-3-CHKSUM_ERR_1_FIA_3

3 PLATFORM

BRIDGE-3-CRC_ERR_0_FIA_0

3 PLATFORM

BRIDGE-3-CRC_ERR_0_FIA_1

3 PLATFORM

BRIDGE-3-CRC_ERR_0_FIA_2

3 PLATFORM

BRIDGE-3-CRC_ERR_0_FIA_3

3 PLATFORM

BRIDGE-3-CRC_ERR_0_NPU_0

3 PLATFORM

BRIDGE-3-CRC_ERR_0_NPU_1

3 PLATFORM

BRIDGE-3-CRC_ERR_0_NPU_2

3 PLATFORM

BRIDGE-3-CRC_ERR_0_NPU_3

3 PLATFORM

BRIDGE-3-CRC_ERR_1_FIA_0

3 PLATFORM

BRIDGE-3-CRC_ERR_1_FIA_1

3 PLATFORM

BRIDGE-3-CRC_ERR_1_FIA_2

3 PLATFORM

BRIDGE-3-CRC_ERR_1_FIA_3

3 PLATFORM

BRIDGE-3-CRC_ERR_1_NPU_0

3 PLATFORM

BRIDGE-3-CRC_ERR_1_NPU_1

3 PLATFORM

BRIDGE-3-CRC_ERR_1_NPU_2

3 PLATFORM

BRIDGE-3-CRC_ERR_1_NPU_3

3 PLATFORM

BRIDGE-3-FIA2NPU_0_PKT_MAXLEN_ERR_0

3 PLATFORM

BRIDGE-3-FIA2NPU_0_PKT_MAXLEN_ERR_1

3 PLATFORM

BRIDGE-3-FIA2NPU_0_PKT_MAXLEN_ERR_2

3 PLATFORM

BRIDGE-3-FIA2NPU_0_PKT_MAXLEN_ERR_3

3 PLATFORM

BRIDGE-3-FIA2NPU_0_PKT_MINLEN_ERR_0

3 PLATFORM

BRIDGE-3-FIA2NPU_0_PKT_MINLEN_ERR_1

3 PLATFORM

BRIDGE-3-FIA2NPU_0_PKT_MINLEN_ERR_2

3 PLATFORM

BRIDGE-3-FIA2NPU_0_PKT_MINLEN_ERR_3

3 PLATFORM

BRIDGE-3-FIA2NPU_1_PKT_MAXLEN_ERR_0

3 PLATFORM

BRIDGE-3-FIA2NPU_1_PKT_MAXLEN_ERR_1

3 PLATFORM

BRIDGE-3-FIA2NPU_1_PKT_MAXLEN_ERR_2

3 PLATFORM

BRIDGE-3-FIA2NPU_1_PKT_MAXLEN_ERR_3

3 PLATFORM

BRIDGE-3-FIA2NPU_1_PKT_MINLEN_ERR_0

3 PLATFORM

BRIDGE-3-FIA2NPU_1_PKT_MINLEN_ERR_1

3 PLATFORM

BRIDGE-3-FIA2NPU_1_PKT_MINLEN_ERR_2

3 PLATFORM

BRIDGE-3-FIA2NPU_1_PKT_MINLEN_ERR_3

3 PLATFORM

BRIDGE-3-MISS_EOP_0_FIADDR_0

3 PLATFORM

BRIDGE-3-MISS_EOP_0_FIADDR_1

3 PLATFORM

BRIDGE-3-MISS_EOP_0_FIADDR_2

3 PLATFORM

BRIDGE-3-MISS_EOP_0_FIADDR_3

3 PLATFORM

BRIDGE-3-MISS_EOP_0_XAUI_0

3 PLATFORM

BRIDGE-3-MISS_EOP_0_XAUI_1

3 PLATFORM

BRIDGE-3-MISS_EOP_0_XAUI_2

3 PLATFORM

BRIDGE-3-MISS_EOP_0_XAUI_3

3 PLATFORM

BRIDGE-3-MISS_EOP_1_FIADDR_0

3 PLATFORM

BRIDGE-3-MISS_EOP_1_FIADDR_1

3 PLATFORM

BRIDGE-3-MISS_EOP_1_FIADDR_2

3 PLATFORM

BRIDGE-3-MISS_EOP_1_FIADDR_3

3 PLATFORM

BRIDGE-3-MISS_EOP_1_XAUI_0

3 PLATFORM

BRIDGE-3-MISS_EOP_1_XAUI_1

3 PLATFORM

BRIDGE-3-MISS_EOP_1_XAUI_2

3 PLATFORM

BRIDGE-3-MISS_EOP_1_XAUI_3

3 PLATFORM

BRIDGE-3-NPU_0_CONST_BP_0

3 PLATFORM

BRIDGE-3-NPU_0_CONST_BP_1

3 PLATFORM

BRIDGE-3-NPU_0_CONST_BP_2

3 PLATFORM

BRIDGE-3-NPU_0_CONST_BP_3

3 PLATFORM

BRIDGE-3-NPU_0_PKT_MAXLEN_ERR_0

3 PLATFORM

BRIDGE-3-NPU_0_PKT_MAXLEN_ERR_1

3 PLATFORM

BRIDGE-3-NPU_0_PKT_MAXLEN_ERR_2

3 PLATFORM

BRIDGE-3-NPU_0_PKT_MAXLEN_ERR_3

3 PLATFORM

BRIDGE-3-NPU_0_PKT_MINLEN_ERR_0

3 PLATFORM

BRIDGE-3-NPU_0_PKT_MINLEN_ERR_1

3 PLATFORM

BRIDGE-3-NPU_0_PKT_MINLEN_ERR_2

3 PLATFORM

BRIDGE-3-NPU_0_PKT_MINLEN_ERR_3

3 PLATFORM

BRIDGE-3-NPU_0_TS_CORE_ERR_0

3 PLATFORM

BRIDGE-3-NPU_0_TS_CORE_ERR_1

3 PLATFORM

BRIDGE-3-NPU_0_TS_CORE_ERR_2

3 PLATFORM

BRIDGE-3-NPU_0_TS_CORE_ERR_3

3 PLATFORM

BRIDGE-3-NPU_1_CONST_BP_0

3 PLATFORM

BRIDGE-3-NPU_1_CONST_BP_1

3 PLATFORM

BRIDGE-3-NPU_1_CONST_BP_2

3 PLATFORM

BRIDGE-3-NPU_1_CONST_BP_3

3 PLATFORM

BRIDGE-3-NPU_1_PKT_MAXLEN_ERR_0

3 PLATFORM

BRIDGE-3-NPU_1_PKT_MAXLEN_ERR_1

3 PLATFORM

BRIDGE-3-NPU_1_PKT_MAXLEN_ERR_2

3 PLATFORM

BRIDGE-3-NPU_1_PKT_MAXLEN_ERR_3

3 PLATFORM

BRIDGE-3-NPU_1_PKT_MINLEN_ERR_0

3 PLATFORM

BRIDGE-3-NPU_1_PKT_MINLEN_ERR_1

3 PLATFORM

BRIDGE-3-NPU_1_PKT_MINLEN_ERR_2

3 PLATFORM

BRIDGE-3-NPU_1_PKT_MINLEN_ERR_3

3 PLATFORM

BRIDGE-3-NPU_1_TS_CORE_ERR_0

3 PLATFORM

BRIDGE-3-NPU_1_TS_CORE_ERR_1

3 PLATFORM

BRIDGE-3-NPU_1_TS_CORE_ERR_2

3 PLATFORM

BRIDGE-3-NPU_1_TS_CORE_ERR_3

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_0_FIA_0

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_0_FIA_1

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_0_FIA_2

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_0_FIA_3

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_0_XAUI_0

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_0_XAUI_1

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_0_XAUI_2

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_0_XAUI_3

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_1_FIA_0

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_1_FIA_1

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_1_FIA_2

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_1_FIA_3

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_1_XAUI_0

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_1_XAUI_1

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_1_XAUI_2

3 PLATFORM

BRIDGE-3-PKT_LEN_ERR_1_XAUI_3

3 PLATFORM

BRIDGE-3-XAUI_0_FRAG_ERR_0

3 PLATFORM

BRIDGE-3-XAUI_0_FRAG_ERR_1

3 PLATFORM

BRIDGE-3-XAUI_0_FRAG_ERR_2

3 PLATFORM

BRIDGE-3-XAUI_0_FRAG_ERR_3

3 PLATFORM

BRIDGE-3-XAUI_1_FRAG_ERR_0

3 PLATFORM

BRIDGE-3-XAUI_1_FRAG_ERR_1

3 PLATFORM

BRIDGE-3-XAUI_1_FRAG_ERR_2

3 PLATFORM

BRIDGE-3-XAUI_1_FRAG_ERR_3

3 PLATFORM

c2c_iif-3-ERR_HW_INIT

3 PLATFORM

c2c_iif-3-ERR_SW

3 PLATFORM

c2c_pif-3-ERR_HW_INIT

3 PLATFORM

c2c_pif-3-ERR_SW

3 PLATFORM

CAIBIST-3-ERR_HW_BIST

3 PLATFORM

CAIBIST-3-ERR_HW_BIST

3 PLATFORM

CAIBIST-3-ERR_HW_BIST_INFO

3 PLATFORM

CAIBIST-3-ERR_HW_BIST_TIMEDOUT

3 PLATFORM

CAIBIST-3-ERR_HW_BIST_TIMEDOUT

3 PLATFORM

CAIBIST-3-ERR_SW_INIT

3 PLATFORM

CAIBIST-3-ERR_SW_INIT

3 PLATFORM

CANB_SERVER-3-ALARM_CLEARED

3 PLATFORM

CANB_SERVER-3-ALARM_INDICATION

3 PLATFORM

CANB_SERVER-3-CBC_UART_FILE_DESC

3 PLATFORM

CANB_SERVER-3-CBC_UART1_FILE_DESC

3 PLATFORM

CANB_SERVER-3-ERROR_EXIT

3 PLATFORM

CANB_SERVER-3IDPROM_CACHE_OVERFLOW

3 PLATFORM

CANB_SERVER-3-INVALID_SLOT

3 PLATFORM

CANB_SERVER-3-INVALID_SLOT_BUS

3 PLATFORM

CANB_SERVER-3MEM_CORRUPT_TX_REQUEST_ARRAY

3 PLATFORM

CANB_SERVER-3-MESSAGE_FAILED

3 PLATFORM

CANB_SERVER-3-OBFL_CACHE_OVERFLOW

3 PLATFORM

CANB_SERVER-3-OPERATION_FAIL

3 PLATFORM

CANB_SERVER-6-CRC_ERROR

6 PLATFORM

CANB_SERVER-6-ILLEGAL_CBC_VERSION

6 PLATFORM

CANB_SERVER-6-OPERATION_INFO

6 PLATFORM

CANB_SERVER-6-RP_ISOLATION

6 PLATFORM

CANB_SERVER-6-RP_ISOLATION_RESET_REQ

6 PLATFORM

CANB_SERVER-6-UPGRADE_COMPLETED

6 PLATFORM

CANB_SERVER-6-UPGRADE_IN_PROGRESS

6 PLATFORM

CANB_SERVER-6-UPGRADE_INFO

6 PLATFORM

CANB_SERVER-6-UPGRADE_STARTED

6 PLATFORM

CANB_SERVER-7CBC_POST_RESET_NOTIFICATION

7 PLATFORM

CANB_SERVER-7CBC_PRE_RESET_NOTIFICATION

7 PLATFORM

CANB_SERVER-7-OPERATION_DEBUG

7 PLATFORM

CARD-3-OVERCURRENT

3 PLATFORM

CARDMGR-3-BAD_CS_INFO

3 PLATFORM

CARDMGR-3-CHDIR_FAILED

3 PLATFORM

CARDMGR-3-MODULE_UNAVAILABLE

3 PLATFORM

CARDMGR-3-NO_CARDS_DEFINED

3 PLATFORM

CARDMGR-3-NO_DRIVERS_FOUND

3 PLATFORM

CARDMGR-3-NO_MEM

3 PLATFORM

CARDMGR-3-NO_SOCKETS

3 PLATFORM

CARDMGR-3-PCMCIA_INIT_ERROR

3 PLATFORM

CARDMGR-3-SELECT_FAILURE

3 PLATFORM

CARDMGR-3-UNSUPPORTED_CARD
CARDMGR-6-PRODUCT_INFO
CARDMGR-6-SOCKET_INFO

3 PLATFORM
6 PLATFORM
6 PLATFORM

CARDMGR-7-ADJ_RES_FAILED

7 PLATFORM

CARDMGR-7-BAD_OPEN

7 PLATFORM

CARDMGR-7-BIND_FAILED

7 PLATFORM

CARDMGR-7-BIND_MTD_REGION_FAILED

7 PLATFORM

CARDMGR-7-BIND_MTD_SOCKET_FAILED

7 PLATFORM

CARDMGR-7-CIS_DATA_PARSING_ERROR

7 PLATFORM

CARDMGR-7-CIS_DATA_READ_ERROR

7 PLATFORM

CARDMGR-7-CIS_REPLACE_ERROR

7 PLATFORM

CARDMGR-7-CS_REL_MISMATCH

7 PLATFORM

CARDMGR-7-GET_DEV_INFO_FAILED

7 PLATFORM

CARDMGR-7-OPEN_SOCK_FAILED

7 PLATFORM

CARDMGR-7-READ_FAILED

7 PLATFORM

CARDMGR-7-THREAD_CREATE_FAILED

7 PLATFORM

CARDMGR-7-UNBIND_FAILED

7 PLATFORM

CARDMGR-7-UNBIND_MTD_FAILED

7 PLATFORM

CATAPULT-3-ERR_EVM_CREATE

3 PLATFORM

CATAPULT-3-ERR_EXIT

3 PLATFORM

CATAPULT-3-ERR_INIT

3 PLATFORM

CATAPULT-5-ERR_CONT

5 PLATFORM

CBC-2-CANBUS_BOTH_FAILED

2 PLATFORM

CBC-2-CANBUS_PWR_SEQ_FAILED

2 PLATFORM

CBC-3-CANBUS_A_FAILED

3 PLATFORM

CBC-3-CANBUS_B_FAILED

3 PLATFORM

CBC-3-CANBUS_FANTRAY_INRUSH_FAILED

3 PLATFORM

CBC-3-CANBUS_PWR_FUSE_FAILED

3 PLATFORM

CBC-3-SLOT_ID_CHANGE

3 PLATFORM

CBC-3-VERSION_ERROR

3 PLATFORM

CCI_HAL_SATORI-3-ERR_TX_PKT

3 PLATFORM

CCI_SSTAR-3-ERR_DRV_INIT

3 PLATFORM

CCI_SSTAR-3-ERR_EVM_CREATE

3 PLATFORM

CCI_SSTAR-3ERR_INTERRUPT_THREAD_EXIT

3 PLATFORM

CCTL_ENS-3-ERROR_EXIT

3 PLATFORM

CCTL_ENS-7-OPERATION_FAIL

7 PLATFORM

CCTL-2-CARD_POWERUP_FAIL

2 PLATFORM

CCTL-2-CARD_SHUTDOWN_FAIL

2 PLATFORM

CCTL-2-CHASSIS_SHUTDOWN_FAIL

2 PLATFORM

CCTL-2-CPLD_POWER_ALARM

2 PLATFORM

CCTL-2-CPLD_POWER_CTRL_ALARM

2 PLATFORM

CCTL-2-CRS8_B_FANTRAY_MISMATCH

2 PLATFORM

CCTL-2-MB_POWERUP_CHECK_FAIL

2 PLATFORM

CCTL-2-PEARL_POWER_ALARM

2 PLATFORM

CCTL-2-PEARL_TEMP_ALARM

2 PLATFORM

CCTL-2-RESET_SP_FAIL

2 PLATFORM

CCTL-2-STANDBY_SHUTDOWN_FAILED

2 PLATFORM

CCTL-2-TAIKO_POWER_ALARM

2 PLATFORM

CCTL-2-TAIKO_TEMP_ALARM

2 PLATFORM

CCTL-3-BARBARIAN_VOLT_FIX_FAILED

3 PLATFORM

CCTL-3-ERROR_EXIT

3 PLATFORM

CCTL-3-I2C_FAILURE_CLEAR_LED

3 PLATFORM

CCTL-3-I2C_FAILURE_HANG

3 PLATFORM

CCTL-3-I2C_FAILURE_PM_CLEAR_FAULT

3 PLATFORM

CCTL-3-I2C_FAILURE_PM_FAULT

3 PLATFORM

CCTL-3-I2C_FAILURE_PM_LED

3 PLATFORM

CCTL-3-I2C_FAILURE_PM_PRESENCE

3 PLATFORM

CCTL-3-I2C_FAILURE_PM_SENSOR

3 PLATFORM

CCTL-3-I2C_FAILURE_SET_LED

3 PLATFORM

CCTL-3-I2C_FAILURE_ZONE

3 PLATFORM

CCTL-3-MASTERSHIP_EXIT

3 PLATFORM

CCTL-3READ_POWER_SHELF_TYPE_FAILURE

3 PLATFORM

CCTL-3-UNKNOWN_CHASSIS_ID

3 PLATFORM

CCTL-4-BARBARIAN_VOLT_FIX_ACTIVE

4 PLATFORM

CCTL-4CPLD_POWER_SEQUENCER_FAULT_OR_ALER
T

4 PLATFORM

CCTL-4-CPLD_POWER_WARN

4 PLATFORM

CCTL-4-UNKNOWN_SHELF_ID

4 PLATFORM

CCTL-6-OPERATION_SUCCESS

6 PLATFORM

CCTL-6-TEMP_ALARM

6 PLATFORM

CCTL-6-TEMP_READ_ERR

6 PLATFORM

CCTL-7-FMEA_BOARD_POWER_FAILED

7 PLATFORM

CCTL-7-OPERATION_FAIL

7 PLATFORM

CE_SWITCH-2-DEADLINE_MONITOR_FAILED

2 PLATFORM

CE_SWITCH-2-LINK_SHUT_DOWN

2 PLATFORM

CE_SWITCH-2-LINK_STATE_CHANGE

2 PLATFORM

CE_SWITCH-2-PORT_HARDWARE_FAULT

2 PLATFORM

CE_SWITCH-2-PORT_HARDWARE_FAULT

2 PLATFORM

CE_SWITCH-2-STACKING_LINK_DOWN

2 PLATFORM

CE_SWITCH-3-DMAC_LINK_STATE_CHANGE

3 PLATFORM

CE_SWITCH-5-LINK_SHUT_DOWN

5 PLATFORM

CE_SWITCH-6-BADSFP

6 PLATFORM

CE_SWITCH-6-ERRDIS

6 PLATFORM

CE_SWITCH-6-UPDN

6 PLATFORM

CEMGBL-2-CRIT

2 PLATFORM

CEMGBL-2-SFP_INVALID_TYPE

2 PLATFORM

CEMGBL-2-SFP_INVALID_TYPE

2 PLATFORM

CEMGBL-4-WARNING

4 PLATFORM

CEMGBL-5-LTRACE_INIT_FAIL

5 PLATFORM

CEMGBL-5-SFP_OIR

5 PLATFORM

CEMGBL-5-SFP_OIR

5 PLATFORM

CEMGBL-6-INFO

6 PLATFORM

CEMGBL-6-INV_TRACE_BUFF_INIT_FAILED

6 PLATFORM

CEMGBL-7-ERROR

7 PLATFORM

CEMGBL-7-REGISTER_NOTIFY_FAIL

7 PLATFORM

CEMGBL-7-REGISTER_NOTIFY_FAIL

7 PLATFORM

CETHHA-2-CRITICAL

2 PLATFORM

CETHHA-2-PORT_FAULT

2 PLATFORM

CETHHA-4-NOGE

4 PLATFORM

CETHHA-7-STATS_INFO

7 PLATFORM

CFM_CAP-1-CFM_RESTART_REQUIRED

1 PLATFORM

CFP-2-DEV_CFP_COMPLIANCE_ERROR

2 PLATFORM

CFP-2-DEV_CFP_OPTICS_PORT_UNSUP

2 PLATFORM

CFP-2-DEV_CFP_PID_NOT_SUPPORTED

2 PLATFORM

CFP-2-DEV_CFP_SUPPORTED_ERROR

2 PLATFORM

CFP-2-HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-HIGH_VOLTAGE_ALARM

2 PLATFORM

CFP-2-LANE_0_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_0_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_0_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_0_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_0_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_0_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_0_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_0_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_1_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_1_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_1_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_1_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_1_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_1_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_1_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_1_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_10_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_10_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_10_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_10_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_10_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_10_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_10_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_10_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_11_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_11_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_11_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_11_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_11_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_11_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_11_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_11_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_12_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_12_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_12_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_12_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_12_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_12_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_12_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_12_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_13_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_13_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_13_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_13_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_13_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_13_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_13_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_13_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_14_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_14_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_14_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_14_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_14_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_14_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_14_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_14_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_15_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_15_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_15_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_15_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_15_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_15_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_15_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_15_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_2_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_2_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_2_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_2_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_2_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_2_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_2_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_2_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_3_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_3_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_3_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_3_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_3_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_3_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_3_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_3_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_4_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_4_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_4_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_4_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_4_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_4_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_4_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_4_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_5_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_5_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_5_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_5_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_5_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_5_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_5_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_5_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_6_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_6_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_6_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_6_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_6_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_6_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_6_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_6_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_7_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_7_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_7_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_7_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_7_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_7_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_7_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_7_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_8_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_8_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_8_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_8_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_8_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_8_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_8_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_8_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_9_HIGH_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_9_HIGH_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_9_HIGH_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_9_HIGH_TX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_9_LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LANE_9_LOW_RX_POWER_ALARM

2 PLATFORM

CFP-2-LANE_9_LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LANE_9_LOW_TX_POWER_ALARM

2 PLATFORM

CFP-2-LOW_BIAS_ALARM

2 PLATFORM

CFP-2-LOW_TEMP_ALARM

2 PLATFORM

CFP-2-LOW_VOLTAGE_ALARM

2 PLATFORM

CFP-3-HIGH_BIAS_WARNING

3 PLATFORM

CFP-3-HIGH_TEMP_WARNING

3 PLATFORM

CFP-3-HIGH_VOLTAGE_WARNING

3 PLATFORM

CFP-3-LANE_0_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_0_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_0_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_0_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_0_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_0_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_0_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_0_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_1_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_1_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_1_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_1_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_1_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_1_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_1_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_1_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_10_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3LANE_10_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_10_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3LANE_10_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_10_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_10_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_10_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_10_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_11_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3LANE_11_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_11_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3LANE_11_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_11_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_11_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_11_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_11_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_12_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3LANE_12_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_12_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3LANE_12_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_12_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_12_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_12_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_12_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_13_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3LANE_13_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_13_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3LANE_13_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_13_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_13_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_13_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_13_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_14_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3LANE_14_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_14_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3LANE_14_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_14_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_14_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_14_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_14_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_15_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3LANE_15_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_15_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3LANE_15_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_15_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_15_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_15_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_15_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_2_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_2_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_2_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_2_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_2_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_2_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_2_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_2_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_3_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_3_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_3_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_3_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_3_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_3_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_3_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_3_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_4_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_4_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_4_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_4_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_4_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_4_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_4_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_4_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_5_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_5_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_5_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_5_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_5_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_5_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_5_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_5_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_6_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_6_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_6_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_6_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_6_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_6_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_6_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_6_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_7_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_7_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_7_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_7_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_7_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_7_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_7_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_7_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_8_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_8_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_8_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_8_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_8_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_8_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_8_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_8_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_9_HIGH_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_9_HIGH_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_9_HIGH_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_9_HIGH_TX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_9_LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LANE_9_LOW_RX_POWER_WARNING

3 PLATFORM

CFP-3-LANE_9_LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LANE_9_LOW_TX_POWER_WARNING

3 PLATFORM

CFP-3-LOW_BIAS_WARNING

3 PLATFORM

CFP-3-LOW_TEMP_WARNING

3 PLATFORM

CFP-3-LOW_VOLTAGE_WARNING

3 PLATFORM

CGV6_SERVICES-2ERR_CGV6_SERVICES_INIT

2 PLATFORM

CGV6_SERVICES-3-CGV6_SERVICES

3 PLATFORM

CGV6_SERVICES-3-DEBUG_FAIL

3 PLATFORM

CGV6_SERVICES-3-ERROR

3 PLATFORM

CGV6_SERVICES-3-MSG_ERROR

3 PLATFORM

CGV6_SERVICES-6-INFO

6 PLATFORM

CGV6_SERVICES-7-DEBUG

7 PLATFORM

CGV6_SERVICES-7-GENERIC_ERROR

7 PLATFORM

CGV6_SERVICES-7-GENERIC_INFO

7 PLATFORM

CHP-0-FAULT_RECOVERY_ERR

--

PLATFORM

CHP-3-CRC_ERR

3 PLATFORM

CHP-3-DEVICE_HALT

3 PLATFORM

CHP-3-DMA_ERR

3 PLATFORM

CHP-3-FATAL

3 PLATFORM

CHP-3-FATAL_2

3 PLATFORM

CHP-3-FUSILLI_PARITY_ERR

3 PLATFORM

CHP-3-GEN_INFO

3 PLATFORM

CHP-3-HWINIT_INCOMPLETE

3 PLATFORM

CHP-3-INFO

3 PLATFORM

CHP-3-INTR_ENABLE_FAIL

3 PLATFORM

CHP-3-INTR_STATUS_GET_ERR

3 PLATFORM

CHP-3-MALLOC_FAILED

3 PLATFORM

CHP-3-NOT_AVAILABLE

3 PLATFORM

CHP-3-NOT_OPERATIONAL

3 PLATFORM

CHP-3-NOT_YET_IMPLEMENTED

3 PLATFORM

CHP-3-PCI_ERR

3 PLATFORM

CHP-3-SRAM_PARITY_ERR

3 PLATFORM

CHP-6-UNHANDLED_HALT

6 PLATFORM

CHP-6-UNHANDLED_INTR

6 PLATFORM

CIH-0-ASIC_ERROR_BOARD_RELOAD

--

PLATFORM

CIH-0-ASIC_ERROR_BOARD_RELOAD

--

PLATFORM

CIH-0-ASIC_ERROR_RELOAD_SYS

--

PLATFORM

CIH-0-ASIC_ERROR_RELOAD_SYS

--

PLATFORM

CIH-0-ASIC_ERROR_RELOAD_SYS

--

PLATFORM

CIH-0-ASIC_ERROR_RELOAD_SYS

--

PLATFORM

CIH-0-ASIC_ERROR_RELOAD_SYS

--

PLATFORM

CIH-0-ASIC_ERROR_RELOAD_SYS

--

PLATFORM

CIH-0-ASIC_ERROR_RESET_THRESH_CROSS --

PLATFORM

CIH-0-ASIC_ERROR_RESET_THRESH_CROSS --

PLATFORM

CIH-0-ASIC_ERROR_RESET_THRESH_CROSS --

PLATFORM

CIH-0-ASIC_ERROR_RESET_THRESH_CROSS --

PLATFORM

CIH-0-ASIC_ERROR_SHUTDOWN_BOARD

--

PLATFORM

CIH-0-ASIC_ERROR_SHUTDOWN_BOARD

--

PLATFORM

CIH-0-ASIC_ERROR_SHUTDOWN_BOARD

--

PLATFORM

CIH-0-ASIC_ERROR_SHUTDOWN_BOARD

--

PLATFORM

CIH-0-ASIC_ERROR_SHUTDOWN_BOARD

--

PLATFORM

CIH-0-ASIC_ERROR_SHUTDOWN_BOARD

--

PLATFORM

CIH-1-ASIC_ERROR_PERSIST

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_HARD_RESET

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_HARD_RESET

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_HARD_RESET

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_HARD_RESET

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_HARD_RESET

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_HARD_RESET

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_PON_RESET

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_PON_RESET

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_PON_RESET

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_PON_RESET

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_PON_RESET

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_PON_RESET

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_REPROG_RESOURCE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_REPROG_RESOURCE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_REPROG_RESOURCE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_REPROG_RESOURCE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_REPROG_RESOURCE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_REPROG_RESOURCE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_REPROG_RESOURCE
_THRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_REPROG_RESOURCE
_THRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_REPROG_RESOURCE
_THRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_REPROG_RESOURCE
_THRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_REPROG_RESOURCE
_THRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_REPROG_RESOURCE
_THRESH

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_RETRAIN_LINK

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_RETRAIN_LINK

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_RETRAIN_LINK

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_RETRAIN_LINK

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_RETRAIN_LINK

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_RETRAIN_LINK

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SCRUB_THRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SCRUB_THRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SCRUB_THRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SCRUB_THRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SCRUB_THRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SCRUB_THRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SHUTDOWN_LINK_FA
BRIC

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SHUTDOWN_LINK_FA
BRIC

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SHUTDOWN_LINK_FA
BRIC

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SHUTDOWN_LINK_FA
BRIC

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SHUTDOWN_LINK_FA
BRIC

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SHUTDOWN_LINK_FA
BRIC

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SHUTDOWN_LINK_ILI
TE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SHUTDOWN_LINK_ILI
TE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SHUTDOWN_LINK_ILI
TE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SHUTDOWN_LINK_ILI
TE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SHUTDOWN_LINK_ILI
TE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SHUTDOWN_LINK_ILI
TE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SPECIAL_HANDLE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SPECIAL_HANDLE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SPECIAL_HANDLE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SPECIAL_HANDLE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SPECIAL_HANDLE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SPECIAL_HANDLE

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SPECIAL_HANDLE_T
HRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SPECIAL_HANDLE_T
HRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SPECIAL_HANDLE_T
HRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SPECIAL_HANDLE_T
HRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SPECIAL_HANDLE_T
HRESH

1 PLATFORM

CIH-1ASIC_ERROR_PERSIST_SPECIAL_HANDLE_T
HRESH

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_THRESHOLD

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_THRESHOLD

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_THRESHOLD

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_THRESHOLD

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_THRESHOLD

1 PLATFORM

CIH-1-ASIC_ERROR_PERSIST_THRESHOLD

1 PLATFORM

CIH-1-ASIC_ERROR_RELOAD_BOARD

1 PLATFORM

CIH-1-ASIC_ERROR_RELOAD_BOARD

1 PLATFORM

CIH-1-ASIC_ERROR_RELOAD_BOARD

1 PLATFORM

CIH-1-ASIC_ERROR_RELOAD_BOARD

1 PLATFORM

CIH-1-ASIC_ERROR_RELOAD_BOARD

1 PLATFORM

CIH-1-ASIC_ERROR_RELOAD_BOARD

1 PLATFORM

CIH-1ASIC_ERROR_REQUEST_RELOAD_BOARD

1 PLATFORM

CIH-1ASIC_ERROR_REQUEST_RELOAD_BOARD

1 PLATFORM

CIH-1ASIC_ERROR_REQUEST_RELOAD_BOARD

1 PLATFORM

CIH-1ASIC_ERROR_REQUEST_RELOAD_BOARD

1 PLATFORM

CIH-1ASIC_ERROR_REQUEST_RELOAD_BOARD

1 PLATFORM

CIH-1ASIC_ERROR_REQUEST_RELOAD_BOARD

1 PLATFORM

CIH-1-ASIC_ERROR_SHUTDOWN_LINK_ILITE

1 PLATFORM

CIH-1-ASIC_ERROR_SHUTDOWN_LINK_ILITE

1 PLATFORM

CIH-1-ASIC_ERROR_SHUTDOWN_LINK_ILITE

1 PLATFORM

CIH-1-ASIC_ERROR_SHUTDOWN_LINK_ILITE

1 PLATFORM

CIH-1-ASIC_ERROR_SHUTDOWN_LINK_ILITE

1 PLATFORM

CIH-1-ASIC_ERROR_SHUTDOWN_LINK_ILITE

1 PLATFORM

CIH-2-ASIC_ERROR_HARD_RESET

2 PLATFORM

CIH-2-ASIC_ERROR_HARD_RESET

2 PLATFORM

CIH-2-ASIC_ERROR_HARD_RESET

2 PLATFORM

CIH-2-ASIC_ERROR_HARD_RESET

2 PLATFORM

CIH-2-ASIC_ERROR_HARD_RESET

2 PLATFORM

CIH-2-ASIC_ERROR_HARD_RESET

2 PLATFORM

CIH-2-ASIC_ERROR_PON_RESET

2 PLATFORM

CIH-2-ASIC_ERROR_PON_RESET

2 PLATFORM

CIH-2-ASIC_ERROR_PON_RESET

2 PLATFORM

CIH-2-ASIC_ERROR_PON_RESET

2 PLATFORM

CIH-2-ASIC_ERROR_PON_RESET

2 PLATFORM

CIH-2-ASIC_ERROR_PON_RESET

2 PLATFORM

CIH-3ASIC_ERROR_SHUTDOWN_LINK_FABRIC

3 PLATFORM

CIH-3ASIC_ERROR_SHUTDOWN_LINK_FABRIC

3 PLATFORM

CIH-3ASIC_ERROR_SHUTDOWN_LINK_FABRIC

3 PLATFORM

CIH-3ASIC_ERROR_SHUTDOWN_LINK_FABRIC

3 PLATFORM

CIH-3ASIC_ERROR_SHUTDOWN_LINK_FABRIC

3 PLATFORM

CIH-3ASIC_ERROR_SHUTDOWN_LINK_FABRIC

3 PLATFORM

CIH-3ASIC_ERROR_SPECIAL_HANDLE_THRESH

3 PLATFORM

CIH-3ASIC_ERROR_SPECIAL_HANDLE_THRESH

3 PLATFORM

CIH-3ASIC_ERROR_SPECIAL_HANDLE_THRESH

3 PLATFORM

CIH-3ASIC_ERROR_SPECIAL_HANDLE_THRESH

3 PLATFORM

CIH-3ASIC_ERROR_SPECIAL_HANDLE_THRESH

3 PLATFORM

CIH-3ASIC_ERROR_SPECIAL_HANDLE_THRESH

3 PLATFORM

CIH-3-COMMON_ERROR

3 PLATFORM

CIH-3-COMMON_ERROR

3 PLATFORM

CIH-3-COMMON_ERROR

3 PLATFORM

CIH-3-COMMON_ERROR

3 PLATFORM

CIH-3-COMMON_ERROR

3 PLATFORM

CIH-3-COMMON_ERROR

3 PLATFORM

CIH-3-MISS_MEM_INFO

3 PLATFORM

CIH-3-MISS_MEM_INFO

3 PLATFORM

CIH-3-MISS_MEM_INFO

3 PLATFORM

CIH-3-MISS_MEM_INFO

3 PLATFORM

CIH-3-MISS_MEM_INFO

3 PLATFORM

CIH-3-MISS_MEM_INFO

3 PLATFORM

CIH-3-MULTIPLE_STUCK_BITS

3 PLATFORM

CIH-3-MULTIPLE_STUCK_BITS

3 PLATFORM

CIH-3-MULTIPLE_STUCK_BITS

3 PLATFORM

CIH-3-MULTIPLE_STUCK_BITS

3 PLATFORM

CIH-5-ASIC_ERROR

5 PLATFORM

CIH-5-ASIC_ERROR

5 PLATFORM

CIH-5-ASIC_ERROR

5 PLATFORM

CIH-5-ASIC_ERROR

5 PLATFORM

CIH-5-ASIC_ERROR

5 PLATFORM

CIH-5-ASIC_ERROR

5 PLATFORM

CIH-5-ASIC_ERROR_ASIC_SCAN

5 PLATFORM

CIH-5-ASIC_ERROR_ASIC_SCAN

5 PLATFORM

CIH-5-ASIC_ERROR_ASIC_SCAN

5 PLATFORM

CIH-5-ASIC_ERROR_ASIC_SCAN

5 PLATFORM

CIH-5-ASIC_ERROR_ASIC_SCAN

5 PLATFORM

CIH-5-ASIC_ERROR_ASIC_SCAN

5 PLATFORM

CIH-5-ASIC_ERROR_HARD_RESET_START

5 PLATFORM

CIH-5-ASIC_ERROR_HARD_RESET_START

5 PLATFORM

CIH-5-ASIC_ERROR_HARD_RESET_START

5 PLATFORM

CIH-5-ASIC_ERROR_HARD_RESET_START

5 PLATFORM

CIH-5-ASIC_ERROR_HARD_RESET_START

5 PLATFORM

CIH-5-ASIC_ERROR_HARD_RESET_START

5 PLATFORM

CIH-5-ASIC_ERROR_PON_RESET_START

5 PLATFORM

CIH-5-ASIC_ERROR_PON_RESET_START

5 PLATFORM

CIH-5-ASIC_ERROR_PON_RESET_START

5 PLATFORM

CIH-5-ASIC_ERROR_PON_RESET_START

5 PLATFORM

CIH-5-ASIC_ERROR_PON_RESET_START

5 PLATFORM

CIH-5-ASIC_ERROR_PON_RESET_START

5 PLATFORM

CIH-5ASIC_ERROR_REPROG_RESOURCE_THRESH

5 PLATFORM

CIH-5ASIC_ERROR_REPROG_RESOURCE_THRESH

5 PLATFORM

CIH-5ASIC_ERROR_REPROG_RESOURCE_THRESH

5 PLATFORM

CIH-5ASIC_ERROR_REPROG_RESOURCE_THRESH

5 PLATFORM

CIH-5ASIC_ERROR_REPROG_RESOURCE_THRESH

5 PLATFORM

CIH-5ASIC_ERROR_REPROG_RESOURCE_THRESH

5 PLATFORM

CIH-5ASIC_ERROR_RESET_THRESH_CROSS_NOTI
FICATION

5 PLATFORM

CIH-5ASIC_ERROR_RESET_THRESH_CROSS_NOTI
FICATION

5 PLATFORM

CIH-5ASIC_ERROR_RESET_THRESH_CROSS_NOTI
FICATION

5 PLATFORM

CIH-5ASIC_ERROR_RESET_THRESH_CROSS_NOTI
FICATION

5 PLATFORM

CIH-5-ASIC_ERROR_RETRAIN_LINK

5 PLATFORM

CIH-5-ASIC_ERROR_RETRAIN_LINK

5 PLATFORM

CIH-5-ASIC_ERROR_RETRAIN_LINK

5 PLATFORM

CIH-5-ASIC_ERROR_RETRAIN_LINK

5 PLATFORM

CIH-5-ASIC_ERROR_RETRAIN_LINK

5 PLATFORM

CIH-5-ASIC_ERROR_RETRAIN_LINK

5 PLATFORM

CIH-5-ASIC_ERROR_SCRUB_THRESH

5 PLATFORM

CIH-5-ASIC_ERROR_SCRUB_THRESH

5 PLATFORM

CIH-5-ASIC_ERROR_SCRUB_THRESH

5 PLATFORM

CIH-5-ASIC_ERROR_SCRUB_THRESH

5 PLATFORM

CIH-5-ASIC_ERROR_SCRUB_THRESH

5 PLATFORM

CIH-5-ASIC_ERROR_SCRUB_THRESH

5 PLATFORM

CIH-5-ASIC_ERROR_SPECIAL_HANDLE

5 PLATFORM

CIH-5-ASIC_ERROR_SPECIAL_HANDLE

5 PLATFORM

CIH-5-ASIC_ERROR_SPECIAL_HANDLE

5 PLATFORM

CIH-5-ASIC_ERROR_SPECIAL_HANDLE

5 PLATFORM

CIH-5-ASIC_ERROR_SPECIAL_HANDLE

5 PLATFORM

CIH-5-ASIC_ERROR_SPECIAL_HANDLE

5 PLATFORM

CIH-5-ASIC_ERROR_THRESHOLD

5 PLATFORM

CIH-5-ASIC_ERROR_THRESHOLD

5 PLATFORM

CIH-5-ASIC_ERROR_THRESHOLD

5 PLATFORM

CIH-5-ASIC_ERROR_THRESHOLD

5 PLATFORM

CIH-5-ASIC_ERROR_THRESHOLD

5 PLATFORM

CIH-5-ASIC_ERROR_THRESHOLD

5 PLATFORM

CIH-5-SINGLE_STUCK_BIT

5 PLATFORM

CIH-5-SINGLE_STUCK_BIT

5 PLATFORM

CIH-5-SINGLE_STUCK_BIT

5 PLATFORM

CIH-5-SINGLE_STUCK_BIT

5 PLATFORM

CIH-7-ASIC_ERROR_REPROG_RESOURCE

7 PLATFORM

CIH-7-ASIC_ERROR_REPROG_RESOURCE

7 PLATFORM

CIH-7-ASIC_ERROR_REPROG_RESOURCE

7 PLATFORM

CIH-7-ASIC_ERROR_REPROG_RESOURCE

7 PLATFORM

CIH-7-ASIC_ERROR_REPROG_RESOURCE

7 PLATFORM

CIH-7-ASIC_ERROR_REPROG_RESOURCE

7 PLATFORM

CLKCTRL_T-2-DEV_VERSION_ERROR

2 PLATFORM

CLKCTRL_T-2-EEPROM_OVERCURRENT

2 PLATFORM

CLKCTRL_T-2-PARITY_ERROR

2 PLATFORM

CLKCTRL_T-3-INVALID_64K_INPUT_SYNC_0

3 PLATFORM

CLKCTRL_T-3-INVALID_64K_INPUT_SYNC_1

3 PLATFORM

CLKCTRL_T-3-PLL_T0_STATE_FREERUN

3 PLATFORM

CLKCTRL_T-3-PLL_T0_STATE_HOLDOVER

3 PLATFORM

CLKCTRL_T-3-PLL_T4_STATE_FREERUN

3 PLATFORM

CLKCTRL_T-3-RX_ALARM_AIS_SYNC_0

3 PLATFORM

CLKCTRL_T-3-RX_ALARM_AIS_SYNC_1

3 PLATFORM

CLKCTRL_T-3RX_ALARM_FRAME_ERR_SYNC_0

3 PLATFORM

CLKCTRL_T-3RX_ALARM_FRAME_ERR_SYNC_1

3 PLATFORM

CLKCTRL_T-3RX_ALARM_INVALID_10M_CLOCK_SYNC_2

3 PLATFORM

CLKCTRL_T-3-RX_ALARM_LOF_SYNC_0

3 PLATFORM

CLKCTRL_T-3-RX_ALARM_LOF_SYNC_1

3 PLATFORM

CLKCTRL_T-3-RX_ALARM_LOS_SYNC_0

3 PLATFORM

CLKCTRL_T-3-RX_ALARM_LOS_SYNC_1

3 PLATFORM

CLKCTRL_T-3RX_ALARM_NO_SATELLITE_AVAILABLE_SYN
C_2

3 PLATFORM

CLKCTRL_T-3RX_ALARM_NO_TOD_MSG_SYNC_2

3 PLATFORM

CLKCTRL_T-3-RX_ALARM_RAI_SYNC_0

3 PLATFORM

CLKCTRL_T-3-RX_ALARM_RAI_SYNC_1

3 PLATFORM

CLKCTRL_T-3-TX_ALARM_OC_SYNC_0

3 PLATFORM

CLKCTRL_T-3-TX_ALARM_OC_SYNC_1

3 PLATFORM

CLKCTRL_T-3-TX_ALARM_SC_SYNC_0

3 PLATFORM

CLKCTRL_T-3-TX_ALARM_SC_SYNC_1

3 PLATFORM

CLKCTRL_T-3-TX_ALARM_TAF_SYNC_0

3 PLATFORM

CLKCTRL_T-3-TX_ALARM_TAF_SYNC_1

3 PLATFORM

CLKCTRL_T-3-TX_ALARM_TMF_SYNC_0

3 PLATFORM

CLKCTRL_T-3-TX_ALARM_TMF_SYNC_1

3 PLATFORM

CLKCTRL_T-3-TX_ALARM_TPDV_SYNC_0

3 PLATFORM

CLKCTRL_T-3-TX_ALARM_TPDV_SYNC_1

3 PLATFORM

CLKCTRL-3-ERR_INIT

3 PLATFORM

CLKCTRL-3-ERR_INIT

3 PLATFORM

CLKCTRL-3-ERR_MEM_ALLOC

3 PLATFORM

CLKCTRL-3-INVALID_10M_CLOCK

3 PLATFORM

CLKCTRL-3-INVALID_10M_CLOCK

3 PLATFORM

CLKCTRL-3-INVALID_64K_INPUT

3 PLATFORM

CLKCTRL-3-INVALID_64K_INPUT

3 PLATFORM

CLKCTRL-3-INVALID_64K_INPUT

3 PLATFORM

CLKCTRL-3-NO_SATELLITE_AVAILABLE

3 PLATFORM

CLKCTRL-3-NO_SATELLITE_AVAILABLE

3 PLATFORM

CLKCTRL-3-NO_TOD_MSG

3 PLATFORM

CLKCTRL-3-NO_TOD_MSG

3 PLATFORM

CLKCTRL-3-RX_ALARM_AIS

3 PLATFORM

CLKCTRL-3-RX_ALARM_AIS

3 PLATFORM

CLKCTRL-3-RX_ALARM_AIS

3 PLATFORM

CLKCTRL-3-RX_ALARM_FRAME_ERR

3 PLATFORM

CLKCTRL-3-RX_ALARM_FRAME_ERR

3 PLATFORM

CLKCTRL-3-RX_ALARM_FRAME_ERR

3 PLATFORM

CLKCTRL-3-RX_ALARM_LOF

3 PLATFORM

CLKCTRL-3-RX_ALARM_LOF

3 PLATFORM

CLKCTRL-3-RX_ALARM_LOF

3 PLATFORM

CLKCTRL-3-RX_ALARM_LOS

3 PLATFORM

CLKCTRL-3-RX_ALARM_LOS

3 PLATFORM

CLKCTRL-3-RX_ALARM_LOS

3 PLATFORM

CLKCTRL-3-RX_ALARM_RAI

3 PLATFORM

CLKCTRL-3-RX_ALARM_RAI

3 PLATFORM

CLKCTRL-3-RX_ALARM_RAI

3 PLATFORM

CLKCTRL-3-TX_ALARM_OC

3 PLATFORM

CLKCTRL-3-TX_ALARM_OC

3 PLATFORM

CLKCTRL-3-TX_ALARM_OC

3 PLATFORM

CLKCTRL-3-TX_ALARM_SC

3 PLATFORM

CLKCTRL-3-TX_ALARM_SC

3 PLATFORM

CLKCTRL-3-TX_ALARM_SC

3 PLATFORM

CLKCTRL-3-TX_ALARM_TAF

3 PLATFORM

CLKCTRL-3-TX_ALARM_TAF

3 PLATFORM

CLKCTRL-3-TX_ALARM_TAF

3 PLATFORM

CLKCTRL-3-TX_ALARM_TMF

3 PLATFORM

CLKCTRL-3-TX_ALARM_TMF

3 PLATFORM

CLKCTRL-3-TX_ALARM_TMF

3 PLATFORM

CLKCTRL-3-TX_ALARM_TPDV

3 PLATFORM

CLKCTRL-3-TX_ALARM_TPDV

3 PLATFORM

CLKCTRL-3-TX_ALARM_TPDV

3 PLATFORM

CLKCTRL-5-ERR_CONT

5 PLATFORM

CLKCTRL-5-ERR_CONT

5 PLATFORM

CLKCTRL-5-ERR_CONT

5 PLATFORM

CLKCTRL-5-PLL_T0_STATE_FREERUN

5 PLATFORM

CLKCTRL-5-PLL_T0_STATE_FREERUN

5 PLATFORM

CLKCTRL-5-PLL_T0_STATE_FREERUN

5 PLATFORM

CLKCTRL-5-PLL_T0_STATE_HOLDOVER

5 PLATFORM

CLKCTRL-5-PLL_T0_STATE_HOLDOVER

5 PLATFORM

CLKCTRL-5-PLL_T0_STATE_HOLDOVER

5 PLATFORM

CLKCTRL-5-PLL_T4_STATE_FREERUN

5 PLATFORM

CLKCTRL-5-PLL_T4_STATE_FREERUN

5 PLATFORM

CLKCTRL-5-PLL_T4_STATE_FREERUN

5 PLATFORM

CLKCTRL-7-ERR_EVM_CREATE

7 PLATFORM

CLKCTRL-7-ERR_EVM_NOTIFY

7 PLATFORM

CLKCTRL-7-ERR_EXIT

7 PLATFORM

CLKCTRL-7-ERR_EXIT

7 PLATFORM

CLKCTRL-7-ERR_EXIT

7 PLATFORM

CLKCTRL-7-ERR_LWM_EVENT_BLOCK

7 PLATFORM

CLKCTRL-7-ERR_LWM_REPLY

7 PLATFORM

CLUSTER_CLM-6-UPDN

6 PLATFORM

CLUSTER_UPGRADE-6-INFO

6 PLATFORM

COMMON-0LC_HEADLESS_ACT_RSP_HB_REQ_FAILURE

--

PLATFORM

COMMON-0RSP_HEADLESS_ACT_RSP_HB_REQ_FAILURE --

PLATFORM

CONCERTO-3-ERR_INIT

3 PLATFORM

CONCERTO-3-ERR_MEM_ALLOC

3 PLATFORM

CONCERTO-5-ERR_CONT

5 PLATFORM

CONCERTO-7-ERR_EVM_CREATE

7 PLATFORM

CONCERTO-7-ERR_EVM_NOTIFY

7 PLATFORM

CONCERTO-7-ERR_EXIT

7 PLATFORM

CONCERTO-7-ERR_LWM_EVENT_BLOCK

7 PLATFORM

CONCERTO-7-ERR_LWM_REPLY

7 PLATFORM

CPU_CTRL_CLIENT-3-GEN_ERR

3 PLATFORM

CPU_CTRL_CLIENT-3-GEN_ERR_1

3 PLATFORM

CPU_CTRL_CLIENT-3-GEN_ERR_2

3 PLATFORM

CPU_CTRL_CLIENT-6-GEN_INFO

6 PLATFORM

CPU_CTRL-2-ERR

2 PLATFORM

CPU_CTRL-2-ERR_RC

2 PLATFORM

CPU_CTRL-2-GEN_CRIT

2 PLATFORM

CPU_CTRL-3-ACK_ERROR

3 PLATFORM

CPU_CTRL-3-ACK_ERROR

3 PLATFORM

CPU_CTRL-3-BACKUP_PARTITION

3 PLATFORM

CPU_CTRL-3-ERR_ALLOC

3 PLATFORM

CPU_CTRL-3-ERR_EXIT

3 PLATFORM

CPU_CTRL-3-ERR_INIT

3 PLATFORM

CPU_CTRL-3-ERR_MSG_CLIENT_SEND

3 PLATFORM

CPU_CTRL-3-ERR_MSG_SEND

3 PLATFORM

CPU_CTRL-3-GEN_ERR

3 PLATFORM

CPU_CTRL-3-GEN_ERR_1

3 PLATFORM

CPU_CTRL-3-PROG_ERROR

3 PLATFORM

CPU_CTRL-3-TIMEOUT_ERROR

3 PLATFORM

CPU_CTRL-3-TIMEOUT_ERROR

3 PLATFORM

CPU_CTRL-3-USB_ERROR

3 PLATFORM

CPU_CTRL-6-GEN_INFO

6 PLATFORM

CPU_CTRL-7-GEN_DEBUG

7 PLATFORM

CPUCTRL_SIP700_DLL-0-INIT_ERROR

--

PLATFORM

CPUCTRL_SIP700_DLL-3-CLEANUP_ERROR

3 PLATFORM

CPUCTRL_SIP700_DLL-3-TRACE_ERROR

3 PLATFORM

CPUCTRL_SIP700-0-EVT_INIT_FAILURE

--

PLATFORM

CPUCTRL_SIP700-0-INIT_FAILURE

--

PLATFORM

CPUCTRL_SIP700-0-INTR_INIT_FAILURE

--

PLATFORM

CPUCTRL_SIP700-3-ASICPP_INIT_FAILURE

3 PLATFORM

CPUCTRL_SIP700-3-EDM_INIT_FAILURE

3 PLATFORM

CPUCTRL_SIP700-3-FPD_FAILURE

3 PLATFORM

CPUCTRL_SIP700-3-TRACE_INIT_FAILURE

3 PLATFORM

CPUCTRL-3-ASIC_NOT_FOUND

3 PLATFORM

CPUCTRL-3-ASIC_RESET_FAILURE

3 PLATFORM

CPUCTRL-3CDMA_RAM_CORRECTABLE_ERROR

3 PLATFORM

CPUCTRL-3-CDMA_RAM_PARITY_ERROR

3 PLATFORM

CPUCTRL-3CDMA_RAM_UNCORRECTABLE_ERROR

3 PLATFORM

CPUCTRL-3-DETECTED_TX_PDMA_STALL

3 PLATFORM

CPUCTRL-3-ERR_EVM_CREATE

3 PLATFORM

CPUCTRL-3-ERR_EVM_NOTIFY

3 PLATFORM

CPUCTRL-3-ERR_INIT

3 PLATFORM

CPUCTRL-3-HW_DETECTED_ERROR_ISN

3 PLATFORM

CPUCTRL-3-HW_DETECTED_ERROR_LINK

3 PLATFORM

CPUCTRL-3-HW_DETECTED_ERROR_PCI_PM

3 PLATFORM

CPUCTRL-3-HW_DETECTED_ERROR_PCI_SN

3 PLATFORM

CPUCTRL-3-HW_DETECTED_ERROR_PCIX

3 PLATFORM

CPUCTRL-3-HW_DETECTED_ERROR_PORT

3 PLATFORM

CPUCTRL-3-HW_GASPP_READ_BUS_ERROR

3 PLATFORM

CPUCTRL-3-HW_GASPP_WRITE_ERROR

3 PLATFORM

CPUCTRL-3-IMDR_ABORT

3 PLATFORM

CPUCTRL-3-IMDR_ERR

3 PLATFORM

CPUCTRL-3PCI_RAM_CORRECTABLE_ERROR_MASK

3 PLATFORM

CPUCTRL-3PCI_RAM_CORRECTABLE_ERROR_OTHER

3 PLATFORM

CPUCTRL-3PCI_RAM_UNCORRECTABLE_ERROR

3 PLATFORM

CPUCTRL-3-PDMA_QUEUE_RX_STOP

3 PLATFORM

CPUCTRL-3PDMA_RAM_CORRECTABLE_ERROR

3 PLATFORM

CPUCTRL-3-PDMA_RAM_PARITY_ERROR

3 PLATFORM

CPUCTRL-3PDMA_RAM_UNCORRECTABLE_ERROR

3 PLATFORM

CPUCTRL-3-PERSISTENT_CRC_LINK_FAILURE

3 PLATFORM

CPUCTRL-7-ERR_BAG_REG

7 PLATFORM

CPUCTRL-7-ERR_DLL_INIT

7 PLATFORM

CPUCTRL-7-ERR_LWM_EVENT_BLOCK

7 PLATFORM

CPUCTRL-7-ERR_SYSDB_EDM_REG

7 PLATFORM

CPUCTRLLIB-3-DETECTED_CDMA_PORT0

3 PLATFORM

CPUCTRLLIB-3DETECTED_EGRESSQ_QUEUE0_PDMA

3 PLATFORM

CPUCTRLLIB-3-DETECTED_ERROR_PDMA

3 PLATFORM

CPUCTRLLIB-3DETECTED_RX_DROP_ERROR

3 PLATFORM

CPUCTRLLIB-3DETECTED_TRUNCATED_TX_PKT

3 PLATFORM

CPUCTRLLIB-3HW_DETECTED_ERROR_CDMA

3 PLATFORM

CPUCTRLLIB-3HW_DETECTED_ERROR_RX_PDMA

3 PLATFORM

CPUCTRLLIB-3-UNRECOVERED_PIO_ERROR

3 PLATFORM

CPUCTRLLIB-4-INT_WARNING

4 PLATFORM

CPUCTRLLIB-4-PORT_INIT_FAILURE

4 PLATFORM

CPUCTRLLIB-4-PORT_NOT_PRESENT

4 PLATFORM

CPUCTRLLIB-4PORT_REFRAME_SYNC_FAILURE

4 PLATFORM

CPUCTRLLIB-4-PORT_REINIT_FAILURE

4 PLATFORM

CPUCTRLLIB-6-NO_BUF_TO_REPLACE

6 PLATFORM

CROSSBAR-1HI_FPOE_DB_CORR_ECC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1HI_FPOE_DB_CORR_ECC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1HI_FPOE_DB_UCORR_ECC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1HI_FPOE_DB_UCORR_ECC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1HI_IN_MEM_CORR_ECC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1HI_IN_MEM_CORR_ECC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1HI_IN_MEM_UCORR_ECC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1HI_IN_MEM_UCORR_ECC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1HI_OUT_MEM_CORR_ECC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1HI_OUT_MEM_CORR_ECC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1HI_OUT_MEM_UCORR_ECC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1HI_OUT_MEM_UCORR_ECC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1-IN_BUF_CRC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1-IN_BUF_CRC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1-IN_MEM_ERROR_LNK0

1 PLATFORM

CROSSBAR-1-IN_MEM_ERROR_LNK1

1 PLATFORM

CROSSBAR-1LOW_FPOE_DB_CORR_ECC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1LOW_FPOE_DB_CORR_ECC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1LOW_FPOE_DB_UCORR_ECC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1LOW_FPOE_DB_UCORR_ECC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1LOW_IN_MEM_CORR_ECC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1LOW_IN_MEM_CORR_ECC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1LOW_IN_MEM_UCORR_ECC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1LOW_IN_MEM_UCORR_ECC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1LOW_OUT_MEM_CORR_ECC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1LOW_OUT_MEM_CORR_ECC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1LOW_OUT_MEM_UCORR_ECC_ERROR_LNK0

1 PLATFORM

CROSSBAR-1LOW_OUT_MEM_UCORR_ECC_ERROR_LNK1

1 PLATFORM

CROSSBAR-1-OUT_MEM_ERROR_LNK0

1 PLATFORM

CROSSBAR-1-OUT_MEM_ERROR_LNK1

1 PLATFORM

CROSSBAR-1-SERDES_ERROR_LNK0

1 PLATFORM

CROSSBAR-1-SERDES_ERROR_LNK1

1 PLATFORM

CROSSBAR-1-XBAR_TIMEOUT_ERROR_LNK0

1 PLATFORM

CROSSBAR-1-XBAR_TIMEOUT_ERROR_LNK1

1 PLATFORM

CROSSBAR-2-ACCESS_FAILURE

2 PLATFORM

CROSSBAR-2-BIST_FAILURE

2 PLATFORM

CROSSBAR-2-TEMP_OVER_LIMIT

2 PLATFORM

CROSSBAR-4MULTICAST_THRESHOLD_CROSSED_LNK0

4 PLATFORM

CROSSBAR-4MULTICAST_THRESHOLD_CROSSED_LNK1

4 PLATFORM

DATA_SWITCH-3-LINK_FAIL

3 PLATFORM

DC_SERVICE_SRVR-2-ENS_INIT_FAIL

2 PLATFORM

DC_SERVICE_SRVR-2-INIT_CARD_FAIL

2 PLATFORM

DC_SERVICE_SRVR-2-INIT_SRVR_FAIL

2 PLATFORM

DC_SERVICE_SRVR-3-DEBUG_FAIL

3 PLATFORM

DC_SERVICE_SRVR-3-LTRACE_FAIL

3 PLATFORM

DIAGS-0-LC_NP_LOOPBACK_FAILED

--

PLATFORM

DIAGS-0LC_NP_LOOPBACK_FAILED_RX_PATH

--

PLATFORM

DIAGS-0LC_NP_LOOPBACK_FAILED_TX_PATH

--

PLATFORM

DIAGS-3-EXCESSIVE_ECC_SBE_ERROR

3 PLATFORM

DIAGS-3-FAB_MCAST_SC0_FAILED

3 PLATFORM

DIAGS-3-FAB_MCAST_SC1_FAILED

3 PLATFORM

DIAGS-3-FAB_UNICAST_FAILED

3 PLATFORM

DIAGS-3-FPD_IMG_CORRUPTED

3 PLATFORM

DIAGS-3-INVALID_DEVICE_ID

3 PLATFORM

DIAGS-3-LC_EOBC_FAILED_BOTH_RSP

3 PLATFORM

DIAGS-3-LC_EOBC_FAILED_RSP0

3 PLATFORM

DIAGS-3-LC_EOBC_FAILED_RSP1

3 PLATFORM

DIAGS-3-LC_EOBC_FAILED_STBY_RSP

3 PLATFORM

DIAGS-3-LC_EOBC_NO_RSP_UP

3 PLATFORM

DIAGS-3-LC_EOBC_SEND_FAILED

3 PLATFORM

DIAGS-3-PUNT_FABRIC_DATA_PATH_FAILED

3 PLATFORM

DIAGS-3-SCRATCH_TEST_ERROR

3 PLATFORM

DIAGS-3-SRSP_ACTIVE_EOBC_FAILED

3 PLATFORM

DIAGS-3SRSP_ACTIVE_EOBC_MCAST_FAILED

3 PLATFORM

DIAGS-3-SRSP_STANDBY_EOBC_FAILED

3 PLATFORM

DIAGS-3SRSP_STANDBY_EOBC_MCAST_FAILED

3 PLATFORM

DISCOVERY-0-ERR

--

PLATFORM

DISCOVERY-3-ERR_KD_MMAP

3 PLATFORM

DISCOVERY-3-ERR_KD_MMAP

3 PLATFORM

DISCOVERY-3-ERR_SET_REBOOT_CAUSE

3 PLATFORM

DISCOVERY-3-ERR_SET_REBOOT_CAUSE

3 PLATFORM

DISCOVERY-3-RAM_ECC_2BIT

3 PLATFORM

DISCOVERY-3-RAM_ECC_2BIT

3 PLATFORM

DISCOVERY-4-CPU_LATCH

4 PLATFORM

DISCOVERY-4-CPU_NOLATCH

4 PLATFORM

DISCOVERY-4-DEV_LATCH

4 PLATFORM

DISCOVERY-4-DEV_NOLATCH

4 PLATFORM

DISCOVERY-4-PCI_LATCH

4 PLATFORM

DISCOVERY-4-PCI_NOLATCH

4 PLATFORM

DISCOVERY-4-RAM_ECC_1BIT_THRESH

4 PLATFORM

DISCOVERY-4-RAM_ECC_1BIT_THRESH

4 PLATFORM

DISCOVERY-4-SRAM_PARITY

4 PLATFORM

DISCOVERY-7-ASMP_ERR_REGS

7 PLATFORM

DISCOVERY-7-ASMP_PCI_DETAILS

7 PLATFORM

DISCOVERY-7-CPU_DETAILS

7 PLATFORM

DISCOVERY-7-DEV_DETAILS

7 PLATFORM

DISCOVERY-7-INFO

7 PLATFORM

DISCOVERY-7-INFO

7 PLATFORM

DISCOVERY-7-PCI_DETAILS

7 PLATFORM

DISCOVERY-7-RAM_DETAILS

7 PLATFORM

DISCOVERY-7-RAM_DETAILS

7 PLATFORM

DISCOVERY-7-SRAM_DETAILS

7 PLATFORM

DISK_DRIVER-3FAILED_TO_ALLOCATE_TIMER_ID

3 PLATFORM

DISK_DRIVER-3FAILED_TO_ALLOCATE_TIMER_LEAF

3 PLATFORM

DISK_DRIVER-3-FAILED_TO_CREATE_EVM

3 PLATFORM

DISK_DRIVER-3FAILED_TO_CREATE_THREAD

3 PLATFORM

DISK_DRIVER-3-FAILED_TO_OPEN_FILE

3 PLATFORM

DISK_DRIVER-4-ATA_NESTED_ERROR

4 PLATFORM

DISKCAM-3-ERR_PASS_THROUGH

3 PLATFORM

DMAC-0-DAO_LINK_STATE_CHANGE

--

PLATFORM

DMAC-2-ECC_ERR

2 PLATFORM

DMAC-2-PCI_FATAL_ERR

2 PLATFORM

DMAC-2-PCI_LINK_DOWN

2 PLATFORM

DMAC-2-TEMP_ALARM

2 PLATFORM

DMAC-2-XAUI_FAULT

2 PLATFORM

DMAC-3-CE_SWITCH_LINK_STATE_CHANGE

3 PLATFORM

DMAC-6-PCI_ERR

6 PLATFORM

DMAC-6-UNEXPECTED_PCI_CONFIG

6 PLATFORM

DMAC-7-LINK_STATUS_CHANGE

7 PLATFORM

DMAC-7-RX_MISS

7 PLATFORM

DRP_PAIRING_CLIENT-7-ERR_DLL_INIT

7 PLATFORM

DRP_PAIRING_CLIENT-7-ERR_DLL_INIT

7 PLATFORM

DRP_PAIRING-3-CFGMGR_CONN_ERR

3 PLATFORM

DRP_PAIRING-3-CHKPT_APPL_ERR

3 PLATFORM

DRP_PAIRING-3-ERR_DSC_NODEID

3 PLATFORM

DRP_PAIRING-3-ERR_EVM_CREATE

3 PLATFORM

DRP_PAIRING-3-ERR_GET_MY_NODEID

3 PLATFORM

DRP_PAIRING-3-ERR_SERVER_INIT

3 PLATFORM

DRP_PAIRING-3-ERR_SYSDB_ACCESS

3 PLATFORM

DRP_PAIRING-3-ERR_THREAD_CREATE

3 PLATFORM

DRP_PAIRING-3-NO_PROC_READY

3 PLATFORM

DRP_PAIRING-4-CERR_REG

4 PLATFORM

DRP_PAIRING-6-NON_DRP_NODE

6 PLATFORM

DRP_PAIRING-6-NON_DRP_NODE

6 PLATFORM

DRP_PAIRING-6-NOT_SUPPORTED

6 PLATFORM

DRP_PAIRING-6-NOT_SUPPORTED

6 PLATFORM

DRP_PAIRING-6-PROC_BLOCK

6 PLATFORM

DSC_CTRL-3-FAILURE

3 PLATFORM

DSC_CTRL-3MULTIPLE_PRIMARY_DSC_NODES

3 PLATFORM

DSC_CTRL-3-NO_PRIMARY_DSC_NODE

3 PLATFORM

DSC_CTRL-3-RACK_MISMATCH_FAILURE

3 PLATFORM

DSC_CTRL-6-CONTROL_LINK_FAILURE

6 PLATFORM

DSC_CTRL-6-INFO

6 PLATFORM

DSC_CTRL-6-ISSU_RELOAD

6 PLATFORM

DSC_CTRL-6-RACK_STATE

6 PLATFORM

DSC-1-ERR_LOST_ALL_FABRIC_RACKS

1 PLATFORM

DSC-3-ERR_DSC_INIT

3 PLATFORM

DSC-3-ERR_DSC_INIT

3 PLATFORM

DSC-3-ERR_INPUT_PRIORITY

3 PLATFORM

DSC-3-ERR_INTERNAL_SW

3 PLATFORM

DSC-3-ERR_LTRACE_INIT

3 PLATFORM

DSC-3-ERR_MEM_ALLOC

3 PLATFORM

DSC-3-ERR_MEM_ALLOC

3 PLATFORM

DSC-3-ERR_NULL_SERIAL_ID

3 PLATFORM

DSC-3-ERR_RACK_DOWN

3 PLATFORM

DSC-3-ERR_RMF_NOTIFY

3 PLATFORM

DSC-3-ERR_SYSDB_CONNECT

3 PLATFORM

DSC-3-ERR_TRANSPORT

3 PLATFORM

DSC-3-LOST_RACK

3 PLATFORM

DSC-4-LOST_RACK_ON_SYSTEM_RELOAD

4 PLATFORM

DSC-4-SKIP_RELOAD

4 PLATFORM

DSC-4-SYSTEM_RELOAD_STATUS

4 PLATFORM

DSC-4-WARNING_HB_THRESHOLD

4 PLATFORM

DSC-4-WARNING_RACK_NUM

4 PLATFORM

DSC-5-NOTICE_RACK_NUM

5 PLATFORM

DSC-6-CLEANUP_NODE_PRESENT

6 PLATFORM

DSC-6-INFO_I_AM_DSC

6 PLATFORM

DSC-6-RACK_UP_NOTIFY

6 PLATFORM

DSC-6-WAIT_TIME

6 PLATFORM

DSC-7DEBUG_INSTALL_WILL_REBOOT_NODE

7 PLATFORM

DSC-7-DEBUG_MISSED_HEARTBEAT

7 PLATFORM

DSC-7-ERR_RACK_DELETE

7 PLATFORM

DSC-7-ERR_RACK_OIR

7 PLATFORM

DSC-7-ERR_RACK_OIR_TIMEOUT

7 PLATFORM

DSC-7-ERR_STORE_REBOOT_INFO

7 PLATFORM

DSCMEDIA-2-ERR_WAIT_REDUNDANCY

2 PLATFORM

DSCMEDIA-3-ERR_CCTL

3 PLATFORM

DSCMEDIA-3-ERR_EVM

3 PLATFORM

DSCMEDIA-3-ERR_NODEID

3 PLATFORM

DSCMEDIA-3-ERR_TRANSPORT

3 PLATFORM

DSCMEDIA-3-ERROR

3 PLATFORM

DSCMEDIA-3-ERROR2

3 PLATFORM

DSCMEDIA-3-READ_PERSIST

3 PLATFORM

DSCMEDIA-3-WRITE_PERSIST

3 PLATFORM

DSCMEDIA-4-ERR_THREAD_MUTEX_LOCK

4 PLATFORM

DSCMEDIA-4ERR_THREAD_MUTEX_UNLOCK

4 PLATFORM

DSCMEDIA-4-FETCH

4 PLATFORM

DSCMEDIA-4-LISTEN

4 PLATFORM

DSCMEDIA-4-NO_CSC_SN

4 PLATFORM

DSCMEDIA-4-WARNING

4 PLATFORM

DSCMEDIA-4-WARNING2
DSCMEDIA-6-DSC_ELECTED

4 PLATFORM
6 PLATFORM

EIO-4-ERR_LWM_SEND

4 PLATFORM

EIO-7-ERR_ECM

7 PLATFORM

EIO-7-ERR_EDM_INIT

7 PLATFORM

EIO-7-ERR_LINK_TRAINING

7 PLATFORM

EIO-7-ERR_MEM_ALLOC

7 PLATFORM

EIO-7-ERR_REGISTER_GET

7 PLATFORM

EIO-7-ERR_REGISTER_SET

EMUX-0-SEM_UNCORR_ERR

7 PLATFORM

--

PLATFORM

EMUX-1-LOSS_OF_SYNC_FIA00

1 PLATFORM

EMUX-1-LOSS_OF_SYNC_FIA01

1 PLATFORM

EMUX-1-LOSS_OF_SYNC_FIA10

1 PLATFORM

EMUX-1-LOSS_OF_SYNC_FIA11

1 PLATFORM

EMUX-1-MC_HI_MBE_ERR

1 PLATFORM

EMUX-1-MC_HI_OVR_ERR

1 PLATFORM

EMUX-1-MC_HI_SBE_ERR

1 PLATFORM

EMUX-1-MC_LO_MBE_ERR

1 PLATFORM

EMUX-1-MC_LO_OVR_ERR

1 PLATFORM

EMUX-1-MC_LO_SBE_ERR

1 PLATFORM

EMUX-1-UC_HI_MBE_ERR

1 PLATFORM

EMUX-1-UC_HI_OVR_ERR

1 PLATFORM

EMUX-1-UC_HI_SBE_ERR

1 PLATFORM

EMUX-1-UC_LO_MBE_ERR

1 PLATFORM

EMUX-1-UC_LO_OVR_ERR

1 PLATFORM

EMUX-1-UC_LO_SBE_ERR

1 PLATFORM

EMUX-3-BF_MBE_ERR_FIA00

3 PLATFORM

EMUX-3-BF_MBE_ERR_FIA01

3 PLATFORM

EMUX-3-BF_MBE_ERR_FIA10

3 PLATFORM

EMUX-3-BF_MBE_ERR_FIA11

3 PLATFORM

EMUX-3-BF_OVR_ERR_FIA00

3 PLATFORM

EMUX-3-BF_OVR_ERR_FIA01

3 PLATFORM

EMUX-3-BF_OVR_ERR_FIA10

3 PLATFORM

EMUX-3-BF_OVR_ERR_FIA11

3 PLATFORM

EMUX-3-BF_SBE_ERR_FIA00

3 PLATFORM

EMUX-3-BF_SBE_ERR_FIA01

3 PLATFORM

EMUX-3-BF_SBE_ERR_FIA10

3 PLATFORM

EMUX-3-BF_SBE_ERR_FIA11

3 PLATFORM

EMUX-3-RX_HDR_CSM_ERR_FIA00

3 PLATFORM

EMUX-3-RX_HDR_CSM_ERR_FIA01

3 PLATFORM

EMUX-3-RX_HDR_CSM_ERR_FIA10

3 PLATFORM

EMUX-3-RX_HDR_CSM_ERR_FIA11

3 PLATFORM

EMUX-3-RX_MAX_LEN_ERR_FIA00

3 PLATFORM

EMUX-3-RX_MAX_LEN_ERR_FIA01

3 PLATFORM

EMUX-3-RX_MAX_LEN_ERR_FIA10

3 PLATFORM

EMUX-3-RX_MAX_LEN_ERR_FIA11

3 PLATFORM

EMUX-3-RX_MIN_LEN_ERR_FIA00

3 PLATFORM

EMUX-3-RX_MIN_LEN_ERR_FIA01

3 PLATFORM

EMUX-3-RX_MIN_LEN_ERR_FIA10

3 PLATFORM

EMUX-3-RX_MIN_LEN_ERR_FIA11

3 PLATFORM

EMUX-3-RX_PKT_LEN_ERR_FIA00

3 PLATFORM

EMUX-3-RX_PKT_LEN_ERR_FIA01

3 PLATFORM

EMUX-3-RX_PKT_LEN_ERR_FIA10

3 PLATFORM

EMUX-3-RX_PKT_LEN_ERR_FIA11

3 PLATFORM

EMUX-3-SEM_CORR_ERR

3 PLATFORM

EMUX-3-SEM_CRIT_ERR

3 PLATFORM

EMUX-3-TEMP_ERR

3 PLATFORM

EMUX-3-VCCAUX_ERR

3 PLATFORM

EMUX-3-VCCINT_ERR

3 PLATFORM

ENV_AGT_DLL-3-MSG_IF_OPERATION_FAIL

3 PLATFORM

ENV_AGT_DLL-3-MSG_OPERATION_FAIL

3 PLATFORM

ENVMON_MON-4-TEMPERATURE_READ_FAIL

4 PLATFORM

ENVMON-0-CARD_OVERTEMP_SHUTDOWN

--

PLATFORM

ENVMON-0CHASSIS_OVERTEMP_SHUTDOWN

--

PLATFORM

ENVMON-1-CANTSHUT

1 PLATFORM

ENVMON-1-ENV_POWER_FAILURE

1 PLATFORM

ENVMON-1-ENV_POWER_FAULT

1 PLATFORM

ENVMON-1-FAN_REMOVE

1 PLATFORM

ENVMON-1-PEM_REMOVE

1 PLATFORM

ENVMON-1-SHUTDOWN

1 PLATFORM

ENVMON-1-SPA_CANTSHUT

1 PLATFORM

ENVMON-1-SPA_SHUTDOWN

1 PLATFORM

ENVMON-2ADDITIVE_POWER_OVERBUDGET

2 PLATFORM

ENVMON-2-ALL_FANTRAYS_MISSING

2 PLATFORM

ENVMON-2-ALL_FANTRAYS_MISSING_CLEAR

2 PLATFORM

ENVMON-2-CARD_OVERTEMP

2 PLATFORM

ENVMON-2-CARD_OVERTEMP_CLEAR

2 PLATFORM

ENVMON-2-CARD_STT_HIT

2 PLATFORM

ENVMON-2-CHASSIS_OVERTEMP

2 PLATFORM

ENVMON-2-CHASSIS_OVERTEMP_CLEAR

2 PLATFORM

ENVMON-2-DIE_OVERTEMP_CRITICAL

2 PLATFORM

ENVMON-2-ENV_CONDITION

2 PLATFORM

ENVMON-2-ENV_CONDITION

2 PLATFORM

ENVMON-2-ENV_SLOT_FORCE_CLEAR

2 PLATFORM

ENVMON-2-ENV_SPA_FORCE_CLEAR

2 PLATFORM

ENVMON-2-FAN

2 PLATFORM

ENVMON-2-FAN_CLEAR

2 PLATFORM

ENVMON-2-FAN_FAIL

2 PLATFORM

ENVMON-2-FAN_FAIL

2 PLATFORM

ENVMON-2-FANTRAY_CLEAR

2 PLATFORM

ENVMON-2-FANTRAY_COMM_CLEAR

2 PLATFORM

ENVMON-2-FANTRAY_COMM_FAIL

2 PLATFORM

ENVMON-2-FANTRAY_FAIL

2 PLATFORM

ENVMON-2-MESSAGE_FAIL

2 PLATFORM

ENVMON-2-PORT_OVERTEMP_DISABLE

2 PLATFORM

ENVMON-2-POWER_BUDGET_OK

2 PLATFORM

ENVMON-2-POWERSUPPLY_CURRENT

2 PLATFORM

ENVMON-2-POWERSUPPLY_NONOP

2 PLATFORM

ENVMON-2-POWERSUPPLY_VOLTAGE

2 PLATFORM

ENVMON-2REDUNDANT_POWER_OVERBUDGET

2 PLATFORM

ENVMON-2-SAT_BAT_FAL_A

2 PLATFORM

ENVMON-2-SAT_BAT_FAL_A

2 PLATFORM

ENVMON-2-SAT_BAT_FAL_B

2 PLATFORM

ENVMON-2-SAT_BAT_FAL_B

2 PLATFORM

ENVMON-2-SAT_CHASSIS_TEMP_ALARM

2 PLATFORM

ENVMON-2-SAT_FAN_FAIL

2 PLATFORM

ENVMON-2-SAT_FAN_FAIL

2 PLATFORM

ENVMON-2-SAT_FAN_MFGMEM

2 PLATFORM

ENVMON-2-SAT_FAN_MFGMEM

2 PLATFORM

ENVMON-2-SAT_FAN_MISSING

2 PLATFORM

ENVMON-2-SAT_FAN_MISSING

2 PLATFORM

ENVMON-2-SAT_FAN_RPM_ALARM

2 PLATFORM

ENVMON-2-SAT_PM_FAIL

2 PLATFORM

ENVMON-2-SAT_SENSOR_TEMP_ALARM

2 PLATFORM

ENVMON-2-SPA_OVERTEMP_SHUTDOWN

2 PLATFORM

ENVMON-2-TEMP

2 PLATFORM

ENVMON-2-VOLT_ALARM_SHUTDOWN

2 PLATFORM

ENVMON-2VOLT_ALARM_SHUTDOWN_FAILED

2 PLATFORM

ENVMON-2-VOLTAGE

2 PLATFORM

ENVMON-2-VOLTAGE_SUPPLY_FAILED

2 PLATFORM

ENVMON-3-ASSUME_OLD_E5

3 PLATFORM

ENVMON-3-CARD_UNSUPPORTED

3 PLATFORM

ENVMON-3DIE_OVERTEMP_SHUTDOWN_COUNT

3 PLATFORM

ENVMON-3-E5_NOSUPPORT

3 PLATFORM

ENVMON-3-ERROR_EXIT

3 PLATFORM

ENVMON-3-ERROR_READ_AC

3 PLATFORM

ENVMON-3-FANTRAY_ALARM

3 PLATFORM

ENVMON-3-FANTRAY_ALARM_CLEAR

3 PLATFORM

ENVMON-3-MARGIN_MODE_UNKNOWN

3 PLATFORM

ENVMON-3-NON_COMPLIANT_PS

3 PLATFORM

ENVMON-3-OPERATION_ERROR

3 PLATFORM

ENVMON-3-OPERATION_FAIL

3 PLATFORM

ENVMON-3SLOT_INSERTION_THRESHOLD_B

3 PLATFORM

ENVMON-3-SLOT_INVALID

3 PLATFORM

ENVMON-3-UNEXPECTED_PRP_TYPE

3 PLATFORM

ENVMON-3-UNKNOWN_E5_FW

3 PLATFORM

ENVMON-3-UNKNOWN_E5_HW_TYPE

3 PLATFORM

ENVMON-3-UNKNOWN_PEM

3 PLATFORM

ENVMON-3-UNKNOWN_PRP_TYPE

3 PLATFORM

ENVMON-4-ALARM

4 PLATFORM

ENVMON-4-BLWR_LIFECYCLE_RESET

4 PLATFORM

ENVMON-4-CARD_VOLTAGE_ALARM

4 PLATFORM

ENVMON-4-CARD_VOLTAGE_ALARM_CLEAR

4 PLATFORM

ENVMON-4-CB_OFF_ALARM

4 PLATFORM

ENVMON-4CBC_WDOG_EXCEED_THRESHOLD

4 PLATFORM

ENVMON-4-DIE_OVERTEMP_MAJOR

4 PLATFORM

ENVMON-4-FANTRAY_RPM

4 PLATFORM

ENVMON-4-FANTRAY_RPM_CLEAR

4 PLATFORM

ENVMON-4-FANTRAY_VER_MISMATCH

4 PLATFORM

ENVMON-4FANTRAY_VER_MISMATCH_CLEAR

4 PLATFORM

ENVMON-4-OLD_E5_FW

4 PLATFORM

ENVMON-4-OP_SFP_WARN

4 PLATFORM

ENVMON-4-OPERATION_WARN

4 PLATFORM

ENVMON-4-OVERTEMP

4 PLATFORM

ENVMON-4-PS_NOT_PRESENT_ALARM

4 PLATFORM

ENVMON-4-SAT_FAN_RPM_ALARM

4 PLATFORM

ENVMON-4-SAT_SPEED_DUP_DEGRADE

4 PLATFORM

ENVMON-4-SAT_SPEED_DUP_DEGRADE

4 PLATFORM

ENVMON-4-SAT_SPEED_DUP_UPGRADE

4 PLATFORM

ENVMON-4SLOT_INSERTION_THRESHOLD_A

4 PLATFORM

ENVMON-4-SPA_OVERTEMP_MAJOR

4 PLATFORM

ENVMON-5-ERR_MBUS_EEPROM

5 PLATFORM

ENVMON-5-SPA_OVERTEMP_MINOR

5 PLATFORM

ENVMON-6-ENV_POWER_FAILURE_CLEAR

6 PLATFORM

ENVMON-6-ENV_POWER_FAULT_CLEAR

6 PLATFORM

ENVMON-6-FAN_CLEAR

6 PLATFORM

ENVMON-6-FAN_INSERT

6 PLATFORM

ENVMON-6-LOW_FAN_SPEED_WARNING

6 PLATFORM

ENVMON-6-OPERATION_OVERRIDE

6 PLATFORM

ENVMON-6-OVERTEMP_CLEAR

6 PLATFORM

ENVMON-6-PEM_INSERT

6 PLATFORM

ENVMON-6POWERSUPPLY_CURRENT_CLEAR

6 PLATFORM

ENVMON-6-POWERSUPPLY_NONOP_CLEAR

6 PLATFORM

ENVMON-6-POWERSUPPLY_VOLTAGE_CLEAR

6 PLATFORM

ENVMON-6-PS_SHUTDOWN_ERROR

6 PLATFORM

ENVMON-6-SAT_UNQUAL_PPM

6 PLATFORM

ENVMON-6-SAT_UNQUAL_PPM

6 PLATFORM

ENVMON-6-SEND_PULSE_FAIL

6 PLATFORM

ENVMON-6-TEMP_CLEAR

6 PLATFORM

ENVMON-6-VOLTAGE_CLEAR

6 PLATFORM

ENVMON-7-BAG_DECODE_FAILED

7 PLATFORM

ENVMON-7-CACHE_TOO_SMALL

7 PLATFORM

ENVMON-7-ERR_ASSERT

7 PLATFORM

ENVMON-7-ERR_CHKPT

7 PLATFORM

ENVMON-7-ERR_CHKPT_CREATE

7 PLATFORM

ENVMON-7-ERR_CHKPT_DELETE

7 PLATFORM

ENVMON-7-ERR_CHKPT_ITERATE

7 PLATFORM

ENVMON-7-ERR_CHKPT_RESTORE

7 PLATFORM

ENVMON-7-ERR_CHKPT_SAVE

7 PLATFORM

ENVMON-7-ERR_DEBUG_REG

7 PLATFORM

ENVMON-7-ERR_DSC_CONNECT

7 PLATFORM

ENVMON-7-ERR_DSC_GET

7 PLATFORM

ENVMON-7-ERR_EDM_INIT

7 PLATFORM

ENVMON-7-ERR_EDM_MISSING

7 PLATFORM

ENVMON-7-ERR_EVM_ASYNC_ATTACH

7 PLATFORM

ENVMON-7-ERR_EVM_CREATE
ENVMON-7-ERR_INTERNAL

7 PLATFORM
7 PLATFORM

ENVMON-7-ERR_LWM_RECEIVE

7 PLATFORM

ENVMON-7-ERR_LWM_REPLY

7 PLATFORM

ENVMON-7-ERR_MBUS_READREG

7 PLATFORM

ENVMON-7-ERR_MBUS_RECEIVE

7 PLATFORM

ENVMON-7-ERR_NODEID_CREATE

7 PLATFORM

ENVMON-7-ERR_PTHREAD

7 PLATFORM

ENVMON-7-ERR_SLOT_EXTRACT

7 PLATFORM

ENVMON-7-ERR_SYSDB_BIND

7 PLATFORM

ENVMON-7-ERR_SYSDB_REG_NOTIFY

7 PLATFORM

ENVMON-7-ERR_SYSDB_REG_VERIF

7 PLATFORM

ENVMON-7-ERR_THREAD_CREATE

7 PLATFORM

ENVMON-7-ERR_TRAP_SEND

7 PLATFORM

ENVMON-7-ERROR

7 PLATFORM

ENVMON-7-EVENT_BLOCK_FAILED

7 PLATFORM

ENVMON-7-MBUS_CEC

7 PLATFORM

ENVMON-7-NOT_ON_DSC

7 PLATFORM

ENVMON-7-OP_DBG

7 PLATFORM

ENVMON-7-OPERATION_DEBUG

7 PLATFORM

ENVMON-7-SYSMGR_PROC_READY_FAILED

7 PLATFORM

EOBC-3-PKT_ERRORS_LC0

3 PLATFORM

EOBC-3-PKT_ERRORS_LC1

3 PLATFORM

EOBC-3-PKT_ERRORS_LC10

3 PLATFORM

EOBC-3-PKT_ERRORS_LC11

3 PLATFORM

EOBC-3-PKT_ERRORS_LC12

3 PLATFORM

EOBC-3-PKT_ERRORS_LC13

3 PLATFORM

EOBC-3-PKT_ERRORS_LC14

3 PLATFORM

EOBC-3-PKT_ERRORS_LC15

3 PLATFORM

EOBC-3-PKT_ERRORS_LC16

3 PLATFORM

EOBC-3-PKT_ERRORS_LC17

3 PLATFORM

EOBC-3-PKT_ERRORS_LC18

3 PLATFORM

EOBC-3-PKT_ERRORS_LC19

3 PLATFORM

EOBC-3-PKT_ERRORS_LC2

3 PLATFORM

EOBC-3-PKT_ERRORS_LC3

3 PLATFORM

EOBC-3-PKT_ERRORS_LC4

3 PLATFORM

EOBC-3-PKT_ERRORS_LC5

3 PLATFORM

EOBC-3-PKT_ERRORS_LC6

3 PLATFORM

EOBC-3-PKT_ERRORS_LC7

3 PLATFORM

EOBC-3-PKT_ERRORS_LC8

3 PLATFORM

EOBC-3-PKT_ERRORS_LC9

3 PLATFORM

EOBC-3-PKT_ERRORS_LOCAL_RSP

3 PLATFORM

EOBC-3-PKT_ERRORS_PEER_RSP

3 PLATFORM

EOBC-3-PKT_ERRORS_SFP0

3 PLATFORM

EOBC-3-PKT_ERRORS_SFP1

3 PLATFORM

ETH_SRVR_API-3-ERR_ORPHAN_COUNT

3 PLATFORM

ETH_SRVR_API-5-NOTICE_SKIP_BUFF

5 PLATFORM

ETH_SRVR-3-TX_STALLED

3 PLATFORM

ETH_SRVR-3-TX_STALLED

3 PLATFORM

ETH_SRVR-3-UNKNOWN_FORUS_PAK

3 PLATFORM

ETH_SRVR-3-UNKNOWN_FORUS_PAK

3 PLATFORM

ETH_SRVR-4-INIT_ERR

4 PLATFORM

ETH_SRVR-4-INIT_ERR

4 PLATFORM

ETH_SRVR-4-ISOLATE

4 PLATFORM

ETH_SRVR-4-PCDS_ERR

4 PLATFORM

ETH_SRVR-4-POISON_PILL_FORUS_PAK

4 PLATFORM

ETH_SRVR-4-queue_err

4 PLATFORM

ETH_SRVR-7-ERR_FSM

7 PLATFORM

ETH_SRVR-7-ERR_FSM

7 PLATFORM

ETH_SRVR-7-INCORRECT_PAK

7 PLATFORM

ETHER_CTRL_DLL-3-MSG_OPERATION_FAIL

3 PLATFORM

ETHER_CTRL-3-CARD_EVENT_HDLR

3 PLATFORM

ETHER_CTRL-3-ERROR_EXIT

3 PLATFORM

ETHER_CTRL-3-EVENT_FAIL

3 PLATFORM

ETHER_CTRL-3-IF_CONFIG_OPERATION_FAIL

3 PLATFORM

ETHER_CTRL-3-IF_OPERATION_FAIL

3 PLATFORM

ETHER_CTRL-3-IF_OPERATION_FAIL

3 PLATFORM

ETHER_CTRL-3-INIT_FAIL

3 PLATFORM

ETHER_CTRL-3-MGMT_IF_FAIL

3 PLATFORM

ETHER_CTRL-3-MGMT_IF_FAIL

3 PLATFORM

ETHER_CTRL-3-MUTEX_OPERATION_FAIL

3 PLATFORM

ETHER_CTRL-3-MUTEX_OPERATION_FAIL

3 PLATFORM

ETHER_CTRL-3-OPERATION_FAIL

3 PLATFORM

ETHER_CTRL-3-OPERATION_FAIL

3 PLATFORM

ETHER_CTRL-3-PORT_INDEX_FAIL

3 PLATFORM

ETHER_CTRL-3-PORT_INDEX_FAIL

3 PLATFORM

ETHER_CTRL-3-UNKNOWN_CODE

3 PLATFORM

ETHER_CTRL-3-UNKNOWN_CODE

3 PLATFORM

ETHER_CTRL-4-COUNTER_OVFL

4 PLATFORM

ETHER_CTRL-4-COUNTER_OVFL

4 PLATFORM

ETHER_CTRL-4-XCVR_WARNING

4 PLATFORM

ETHER_CTRL-4-XCVR_WARNING

4 PLATFORM

ETHER_CTRL-6-INFO

6 PLATFORM

ETHER_CTRL-6-PRINT_INFO

6 PLATFORM

ETHERNET_LOOPBACK-3-DEBUG_INIT

3 PLATFORM

ETHERNET_LOOPBACK-3-ERROR_INIT

3 PLATFORM

ETHERNET_LOOPBACK-3-IM_INIT

3 PLATFORM

ETHERNET_LOOPBACK-3-PRM_INIT

3 PLATFORM

ETHERNET_LOOPBACK-3-SHM_INIT

3 PLATFORM

ETHERNET_LOOPBACK-3-TRACE_INIT

3 PLATFORM

ETHERNET_LOOPBACK-3-UIDB_INIT

3 PLATFORM

FAB_XBAR-2-EJECTOR_SWITCH_PRESS

2 PLATFORM

FAB_XBAR-2-ERR_ACCESS_ALARM

2 PLATFORM

FAB-3-no_rackid

3 PLATFORM

FAB-5-ltrace_init_error

5 PLATFORM

FABARBITER-1-BKR_ERROR

1 PLATFORM

FABARBITER-1-BKT_ERROR

1 PLATFORM

FABARBITER-1-CARB_CRM_ERROR

1 PLATFORM

FABARBITER-1-CARB_ENQDEQ_ERROR

1 PLATFORM

FABARBITER-1-CARB_FIL_ERROR

1 PLATFORM

FABARBITER-1-MSG_PAR_CRC

1 PLATFORM

FABARBITER-1-RX_LINK_ERR

1 PLATFORM

FABARBITER-1-SERDES_ERROR

1 PLATFORM

FABARBITER-1-SYNC_ERR

1 PLATFORM

FABARBITER-2-CPIF_SCSM_MBE

2 PLATFORM

FABARBITER-2-CPU_ACCESS_ERROR

2 PLATFORM

FABARBITER-2-CPU_PERR_ERROR

2 PLATFORM

FABARBITER-2-CPU_PROTOCOL_ERROR

2 PLATFORM

FABARBITER-2-QCR_FMT_MBE

2 PLATFORM

FABARBITER-2-QCR_HD_MEM_MBE

2 PLATFORM

FABARBITER-2-QCR_MEM0_MBE

2 PLATFORM

FABARBITER-2-QCR_MEM1_MBE

2 PLATFORM

FABARBITER-2-QCR_MEM2_MBE

2 PLATFORM

FABARBITER-2-QCR_MEM3_MBE

2 PLATFORM

FABARBITER-2-QCR_PGAR_CURR_MEM_MBE

2 PLATFORM

FABARBITER-2-QCR_PGAR_MAX_MEM_MBE

2 PLATFORM

FABARBITER-2-QCR_TL_MEM_MBE

2 PLATFORM

FABARBITER-2-TEMP_FAULT

2 PLATFORM

FABARBITER-2-XIF_CNTR_MEM_MBE

2 PLATFORM

FABARBITER-2-XIF_GTFF0_MEM_MBE

2 PLATFORM

FABARBITER-2-XIF_GTFF1_MEM_MBE

2 PLATFORM

FABARBITER-2-XIF_GTFF2_MEM_MBE

2 PLATFORM

FABARBITER-2-XIF_RQFF_MEM_MBE

2 PLATFORM

FABARBITER-2-XIF_VQI_TBL_MBE

2 PLATFORM

FABIO_HFR-3-ERR_CCI_CREATE_Q

3 PLATFORM

FABIO_HFR-3ERR_IMDR_V1_PREP_CALL_FAILED

3 PLATFORM

FABIO_HFR-3-ERR_IMDR_V1_PREP_EINVAL

3 PLATFORM

FABIO_HFR-3-ERR_INIT

3 PLATFORM

FABIO_HFR-3-ERR_PAK_FSV_REGISTRATION

3 PLATFORM

FABIO_HFR-3ERR_QAD_EGRESS_QUEUE_MISSING

3 PLATFORM

FABIO_HFR-3-ERR_QAD_GET_DEPTH

3 PLATFORM

FABIO_HFR-3-ERR_QAD_NOTIF

3 PLATFORM

FABIO_HFR-3-ERR_QAD_SET_WM

3 PLATFORM

FABIO_HFR-4-ERR_NETIO_CONN

4 PLATFORM

FABIO_HFR-7-ERR_NULL_ARGS

7 PLATFORM

FABIO_HFR-7ERR_SEND_EGRESS_IPSLA_PKT

7 PLATFORM

FABIO_HFR-7-ERR_SEND_EGRESS_PKT

7 PLATFORM

FABIO_HFR-7-ERR_SEND_INGRESS_PKT

7 PLATFORM

FABIO_TOPAZ-3-ERR_CCI_CREATE_Q

3 PLATFORM

FABIO_TOPAZ-3-ERR_INIT

3 PLATFORM

FABIO_TOPAZ-3ERR_PAK_FSV_REGISTRATION

3 PLATFORM

FABIO_TOPAZ-3ERR_QAD_EGRESS_QUEUE_MISSING

3 PLATFORM

FABIO_TOPAZ-3-ERR_QAD_GET_DEPTH

3 PLATFORM

FABIO_TOPAZ-3-ERR_QAD_NOTIF

3 PLATFORM

FABIO_TOPAZ-3-ERR_QAD_SET_WM

3 PLATFORM

FABIO_TOPAZ-4-ERR_NETIO_CONN

4 PLATFORM

FABIO_TOPAZ-7-ERR_NULL_ARGS

7 PLATFORM

FABIO_TOPAZ-7ERR_SEND_EGRESS_IPSLA_PKT

7 PLATFORM

FABIO_TOPAZ-7-ERR_SEND_EGRESS_PKT

7 PLATFORM

FABIO_TOPAZ-7-ERR_SEND_INGRESS_PKT

7 PLATFORM

FABIO-3-ERR_CCI_CREATE_Q

3 PLATFORM

FABIO-3-ERR_IMDR_V1_PREP_CALL_FAILED

3 PLATFORM

FABIO-3-ERR_IMDR_V1_PREP_EINVAL

3 PLATFORM

FABIO-3-ERR_INIT

3 PLATFORM

FABIO-3-ERR_PAK_FSV_REGISTRATION

3 PLATFORM

FABIO-3ERR_QAD_EGRESS_QUEUE_MISSING

3 PLATFORM

FABIO-3-ERR_QAD_GET_DEPTH

3 PLATFORM

FABIO-3-ERR_QAD_NOTIF

3 PLATFORM

FABIO-3-ERR_QAD_SET_WM

3 PLATFORM

FABIO-4-ERR_NETIO_CONN

4 PLATFORM

FABIO-7-ERR_NULL_ARGS

7 PLATFORM

FABIO-7-ERR_SEND_EGRESS_IPSLA_PKT

7 PLATFORM

FABIO-7-ERR_SEND_EGRESS_PKT

7 PLATFORM

FABIO-7-ERR_SEND_INGRESS_PKT

7 PLATFORM

FABMGR-0-ASIC_ERROR

--

PLATFORM

FABMGR-0-SPINE_SHUTDOWN

--

PLATFORM

FABMGR-1-ARB_SERDES_FAIL

1 PLATFORM

FABMGR-1-BAD_XBAR

1 PLATFORM

FABMGR-1-PERSISTENT_SERDES_FAIL

1 PLATFORM

FABMGR-1-SPINE_UNAVAILABLE

1 PLATFORM

FABMGR-2-FABRIC_FATAL_FAULT

2 PLATFORM

FABMGR-2-FABRIC_INTERNAL_ARB_FAULT

2 PLATFORM

FABMGR-2-FABRIC_INTERNAL_FAULT

2 PLATFORM

FABMGR-2-FABRIC_SPINE_FAULT

2 PLATFORM

FABMGR-2-SPINE_DEACTIVATED

2 PLATFORM

FABMGR-3-XBAR_DIS_FR_PEER

3 PLATFORM

FABMGR-5-FABRIC_TRANSIENT_FAULT

5 PLATFORM

FABRIC_CTRL-2-ACTIVE_RP

2 PLATFORM

FABRIC_CTRL-2-CARD_STATE

2 PLATFORM

FABRIC_CTRL-2-CHKPT_INIT_FAILED

2 PLATFORM

FABRIC_CTRL-2CHKPT_REGISTRATION_FAILED

2 PLATFORM

FABRIC_CTRL-2-ERR_MEM_ALLOC

2 PLATFORM

FABRIC_CTRL-2-ERR_MEM_ALLOC

2 PLATFORM

FABRIC_CTRL-2-EVENT_LOOP

2 PLATFORM

FABRIC_CTRL-2-FAIL_MEM_ALLOC

2 PLATFORM

FABRIC_CTRL-2-FAIL_REPORT

2 PLATFORM

FABRIC_CTRL-2-FAILED_SYNCH

2 PLATFORM

FABRIC_CTRL-2-FAILED_TO_RESET_FC

2 PLATFORM

FABRIC_CTRL-2-FAILED_TO_SEND_CONFIG

2 PLATFORM

FABRIC_CTRL-2-FAILED_TO_SEND_SLOT_BW

2 PLATFORM

FABRIC_CTRL-2-FAILED_TO_SYNC_RP

2 PLATFORM

FABRIC_CTRL-2FAILED_TO_SYNC_RP_TO_CSCS

2 PLATFORM

FABRIC_CTRL-2-FAILED_TO_SYNC_TO_SELF

2 PLATFORM

FABRIC_CTRL-2-FIA_INIT_LOS_FAIL

2 PLATFORM

FABRIC_CTRL-2-FIA_MULTI_INIT_LOS_FAIL

2 PLATFORM

FABRIC_CTRL-2-MBUS_ERROR

2 PLATFORM

FABRIC_CTRL-2-NOTIFY_BW_CHG_FAIL

2 PLATFORM

FABRIC_CTRL-2-PROCESS_INIT

2 PLATFORM

FABRIC_CTRL-3CARD_ID_FPGA_VERSION_MISMATCH

3 PLATFORM

FABRIC_CTRL-3-CONNECT_LCS

3 PLATFORM

FABRIC_CTRL-3-DISCONNECT_LCS

3 PLATFORM

FABRIC_CTRL-3-GET_CARD_TYPE

3 PLATFORM

FABRIC_CTRL-3-MBUS

3 PLATFORM

FABRIC_CTRL-3-MIB_INIT_FAIL

3 PLATFORM

FABRIC_CTRL-3-RESTORE_DATA

3 PLATFORM

FABRIC_CTRL-3-THREAD_CREATE

3 PLATFORM

FABRIC_CTRL-3-UNKNOWN_CHASSIS

3 PLATFORM

FABRIC_CTRL-3-UNKNOWN_MSG

3 PLATFORM

FABRIC_CTRL-3-UNSUPPORTED_CHASSIS

3 PLATFORM

FABRIC_CTRL-4-AM_NOT_ROOT_LR

4 PLATFORM

FABRIC_CTRL-4FABRIC_CARDS_UNAVAILABLE

4 PLATFORM

FABRIC_CTRL-4-MCAST_PRI_CFG

4 PLATFORM

FABRIC_CTRL-4-SYSDB_FAIL

4 PLATFORM

FABRIC_CTRL-5FABRIC_CARD_OIR_INSERTED

5 PLATFORM

FABRIC_CTRL-5FABRIC_CARD_OIR_REMOVED

5 PLATFORM

FAN-3-OVERCURRENT

3 PLATFORM

FAULT_MGR_CLIENT-3-MSG_ERROR

3 PLATFORM

FAULT_MGR_EH-3-MSG_ERROR

3 PLATFORM

FAULT_MGR-1-MSG_E7_INFO

1 PLATFORM

FAULT_MGR-1-MSG_INFO

1 PLATFORM

FAULT_MGR-1-TW_INFO

1 PLATFORM

FAULT_MGR-3-INIT_ERROR

3 PLATFORM

FAULT_MGR-3-MSG_E7_ERROR

3 PLATFORM

FAULT_MGR-3-MSG_ERROR

3 PLATFORM

FAULT_MGR-3-STAT

3 PLATFORM

FAULT-2-LC_RESET

2 PLATFORM

FAULT-3-LC_DEVICE

3 PLATFORM

FCA-0-MAC_SEU_UNCORR_ERR

--

PLATFORM

FCA-2-CLK_FAIL

2 PLATFORM

FCA-2-CPT_DEV_VERSION_ERROR

2 PLATFORM

FCA-2-CPT_PAR_ERROR

2 PLATFORM

FCA-2-CPT4_DEV_VERSION_ERROR

2 PLATFORM

FCA-2-CPT4_PAR_ERROR

2 PLATFORM

FCA-2-CRRS_DEV_VERSION_ERROR

2 PLATFORM

FCA-2-CRRS_PAR_ERROR

2 PLATFORM

FCA-2-CRRS4_DEV_VERSION_ERROR

2 PLATFORM

FCA-2-CRRS4_PAR_ERROR

2 PLATFORM

FCA-2-CT2_DEV_VERSION_ERROR

2 PLATFORM

FCA-2-CT2_PAR_ERROR

2 PLATFORM

FCA-2-INVALID_ADDR

2 PLATFORM

FCA-2-LB_DEV_VERSION_ERROR

2 PLATFORM

FCA-2-LBO_PAR_ERROR

2 PLATFORM

FCA-2-LDA_AFP_LNK_FAULT_ERROR

2 PLATFORM

FCA-2-LDA_DEV_VERSION_ERROR

2 PLATFORM

FCA-2-LDA_PAR_ERROR

2 PLATFORM

FCA-2-MAC_SEU_CORR_ERR

2 PLATFORM

FCA-2-MISC_ERROR

2 PLATFORM

FCA-2-SEQ_ERROR

2 PLATFORM

FCA-2-SFP_I2C_PHY_ACK_ERROR

2 PLATFORM

FCA-2-SFP_I2C_PHY_TM_ERROR

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_0

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_1

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_10

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_11

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_12

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_13

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_14

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_15

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_16

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_17

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_18

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_19

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_2

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_20

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_21

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_22

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_23

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_24

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_25

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_26

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_27

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_28

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_29

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_3

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_30

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_31

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_32

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_33

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_34

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_35

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_36

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_37

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_38

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_39

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_4

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_5

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_6

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_7

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_8

2 PLATFORM

FCA-2-SFP_LNK_FAULT_ERROR_9

2 PLATFORM

FCA-2-TMCAT_DEV_VERSION_ERROR

2 PLATFORM

FCA-2-TMCAT_PAR_ERROR

2 PLATFORM

FCA-2-TX_RX_PAR_ERROR

2 PLATFORM

FCA-2-TX_RX_TIMEOUT

2 PLATFORM

FCA-2-VLK_DEV_VERSION_ERROR

2 PLATFORM

FCA-2-VLK_PAR_ERROR

2 PLATFORM

FCA-2-XFP_I2C_ERROR

2 PLATFORM

FCA-2-XFP_LNK_FAULT_ERROR_0

2 PLATFORM

FCA-2-XFP_LNK_FAULT_ERROR_1

2 PLATFORM

FCA-2-XFP_LNK_FAULT_ERROR_2

2 PLATFORM

FCA-2-XFP_LNK_FAULT_ERROR_3

2 PLATFORM

FCA-2-XFP_LNK_FAULT_ERROR_4

2 PLATFORM

FCA-2-XFP_LNK_FAULT_ERROR_5

2 PLATFORM

FCA-2-XFP_LNK_FAULT_ERROR_6

2 PLATFORM

FCA-2-XFP_LNK_FAULT_ERROR_7

2 PLATFORM

FCA-3-SFP_I2C_ACK_ERROR

3 PLATFORM

FCA-3-SFP_I2C_TM_ERROR

3 PLATFORM

FDIAGS-3-BAD_EE_READ

3 PLATFORM

FDIAGS-3-BAD_EE_WRITE

3 PLATFORM

FDIAGS-3-BAD_F_DIAG_KILL

3 PLATFORM

FDIAGS-3-BUFFER_TOO_SMALL

3 PLATFORM

FDIAGS-3-CANNOT_GET_JID

3 PLATFORM

FDIAGS-3-CANT_SEND_MBUS_MSG_F

3 PLATFORM

FDIAGS-3-FAB_MBUS_NOT_READY

3 PLATFORM

FDIAGS-3-FABRIC_NOT_DISCONNECTED

3 PLATFORM

FDIAGS-3-FABRIC_NOT_RESTORED

3 PLATFORM

FDIAGS-3-FAILED_SYSMGR_FORK

3 PLATFORM

FDIAGS-3-FILE_READ_JID_BAD

3 PLATFORM

FDIAGS-3-IDLE_CELL_GEN_ADDR

3 PLATFORM

FDIAGS-3-IF_BAD_HALT_OPEN

3 PLATFORM

FDIAGS-3-IF_BAD_HALT_WRITE

3 PLATFORM

FDIAGS-3-IF_BAD_JID_OPEN

3 PLATFORM

FDIAGS-3-IF_BAD_JID_READ

3 PLATFORM

FDIAGS-3-IF_BAD_JID_WRITE

3 PLATFORM

FDIAGS-3-IF_FAIL_CONN_SYSLDR_F

3 PLATFORM

FDIAGS-3-IF_FAIL_SEND_SYSLDR_F

3 PLATFORM

FDIAGS-3-IF_FAIL_SYSLDR_DISCONNECT_F

3 PLATFORM

FDIAGS-3-IF_FAIL_UUT_LAUNCH

3 PLATFORM

FDIAGS-3-IF_INACTIVITY_TIMEOUT

3 PLATFORM

FDIAGS-3-IF_NON_EXISTANT_JID_OPEN

3 PLATFORM

FDIAGS-3-ILLEGAL_FSM_STATE

3 PLATFORM

FDIAGS-3-INVALID_FABRIC

3 PLATFORM

FDIAGS-3-INVALID_SLOT

3 PLATFORM

FDIAGS-3-MALFORMED_INSTALL_PATH

3 PLATFORM

FDIAGS-3-MS_NODE_ID_CREATE_FAIL_F

3 PLATFORM

FDIAGS-3-MS_PRI_CLK_READ

3 PLATFORM

FDIAGS-3-MS_READ_REG_FAIL

3 PLATFORM

FDIAGS-3-MS_UNDEF_MS_MSG

3 PLATFORM

FDIAGS-3-MS_WRITE_REG_FAIL

3 PLATFORM

FDIAGS-3-MS_XBAR_MAP

3 PLATFORM

FDIAGS-3-NO_PRIMARY_CSC

3 PLATFORM

FDIAGS-3-NO_TIME_OF_DAY

3 PLATFORM

FDIAGS-3-NODE_ID_EXTRACTION_FAILED

3 PLATFORM

FDIAGS-3-NON_UUT_IN_STATE

3 PLATFORM

FDIAGS-3-PROBLEM_WITH_FDIAG_REQUEST

3 PLATFORM

FDIAGS-3-PROG_REG_FAIL

3 PLATFORM

FDIAGS-3-RESTORE_DEFAULT_RAM_AGENT

3 PLATFORM

FDIAGS-3-RP_FILE_PATH

3 PLATFORM

FDIAGS-3-RP_INSTALL_PATH

3 PLATFORM

FDIAGS-3-SPA_ID_FAIL

3 PLATFORM

FDIAGS-3-SPA_UNSUPPORTED_INSTANCE

3 PLATFORM

FDIAGS-3-SPCL_RAM_AGENTDL_FAILED

3 PLATFORM

FDIAGS-3-SYSDB_BIND_FAILURE

3 PLATFORM

FDIAGS-3SYSLDR_RESULT_CODE_OUT_OF_BOUNDS

3 PLATFORM

FDIAGS-3-SYSTEM_ERR_NO_CONTINUE

3 PLATFORM

FDIAGS-3-T_O_D_CONVERT_ERR

3 PLATFORM

FDIAGS-3-UNRECOGNIZED_CARD

3 PLATFORM

FDIAGS-3-UNSUPP_CARD

3 PLATFORM

FDIAGS-3-VARIABLE_GET

3 PLATFORM

FDIAGS-3-VARIABLE_SET

3 PLATFORM

FDIAGS-4-BOOT_ALREADY_SET

4 PLATFORM

FDIAGS-4-ERROR_AFTER_RESULTS_REPORT

4 PLATFORM

FDIAGS-4-SYSDB_ITEM_GET_FAILURE

4 PLATFORM

FDIAGS-4-UNEXP_MSV_SUB_MSG

4 PLATFORM

FDIAGS-4-UNEXP_SUB_MSG

4 PLATFORM

FDIAGS-4-UNSUPPORTED_RP_HW_CONFIG

4 PLATFORM

FDIAGS-4-WRONG_CONFIG_REG_VAL

4 PLATFORM

FDIAGS-5-CLEANED_DANGLING_JID_FILE

5 PLATFORM

FDIAGS-5DIAG_ONLY_SUPPORT_IN_IOX_RUNNING_STA
TE

5 PLATFORM

FDIAGS-5-DL_DONE

5 PLATFORM

FDIAGS-5-DL_START

5 PLATFORM

FDIAGS-5-DONE

5 PLATFORM

FDIAGS-5-HALT_REQUESTED

5 PLATFORM

FDIAGS-5-IF_LONGEST_TIME_MSG

5 PLATFORM

FDIAGS-5-IF_NO_CONSOLE

5 PLATFORM

FDIAGS-5-IF_TERMINATED_F_DIAGS_OK

5 PLATFORM

FDIAGS-5-IF_TOTAL_TEST_TIME

5 PLATFORM

FDIAGS-5-LC_TYPE_DEFAULT_RAM_AGENT

5 PLATFORM

FDIAGS-5LC_TYPE_REQUIRES_SPCL_RAM_AGENT

5 PLATFORM

FDIAGS-5-START

5 PLATFORM

FDIAGS-5-SYSLDR_FINISH_HANDOFF

5 PLATFORM

FDIAGS-6-COMPLETE

6 PLATFORM

FDIAGS-6-OUT

6 PLATFORM

FDIAGS-6-RESULT

6 PLATFORM

FDIAGS-6-UUT_OUT

6 PLATFORM

FDIAGS-6-UUT_OUT_I

6 PLATFORM

FDIAGS-7-FORCE_INTO_FSM

7 PLATFORM

FDIAGS-7-NON_HELLO_MSG

7 PLATFORM

FFQ-0-SW_INIT_ERR

--

PLATFORM

FFQ-3-CORRUPT_PKT

3 PLATFORM

FFQ-3-CORRUPT_PTR

3 PLATFORM

FFQ-3-FATAL

3 PLATFORM

FFQ-3-FATAL_2

3 PLATFORM

FFQ-3-GEN_INFO

3 PLATFORM

FFQ-3-INFO

3 PLATFORM

FFQ-3-MALLOC_FAILED

3 PLATFORM

FFQ-3-MEM_ERR

3 PLATFORM

FFQ-3-NOBUF

3 PLATFORM

FFQ-3-NOT_YET_IMPLEMENTED

3 PLATFORM

FFQ-3-PAK_FREE_ERR

3 PLATFORM

FFQ-3-PAK_INVALID

3 PLATFORM

FFQ-3-RATEI

3 PLATFORM

FFQ-3-RATEW

3 PLATFORM

FFQ-3-TMR

3 PLATFORM

FFQ-3-USAGE

3 PLATFORM

FFQ-4-PAK_INVALID

4 PLATFORM

FIB_DBG-3-ERR_DEBUG_LOG

3 PLATFORM

FIB_DBG-3-ERR_INFO_VERBOSE

3 PLATFORM

FIB_DBG-3-ERR_INFO_VERBOSE

3 PLATFORM

FIB_DBG-3-ERR_INFO_VERBOSE

3 PLATFORM

FIB_DBG-3-ERR_INFO_VERBOSE

3 PLATFORM

FIB_IDB_LIB-3-ERR_STR

3 PLATFORM

FIB_IDB_LIB-3-ERR_STR

3 PLATFORM

FIB_IDB_LIB-3-ERR_STR

3 PLATFORM

FIB_IDB_LIB-3-ERROR

3 PLATFORM

FIB_IDB_LIB-3-ERROR

3 PLATFORM

FIB_IDB_LIB-3-ERROR

3 PLATFORM

FIB_LTRACE-3-ERR_INFO_VERBOSE

3 PLATFORM

FIB_LTRACE-3-ERR_INFO_VERBOSE

3 PLATFORM

FIB_LTRACE-3-ERR_INFO_VERBOSE

3 PLATFORM

FIB_LTRACE-3-ERR_INFO_VERBOSE
FPD_BURNER-3-BAD_ARG

3 PLATFORM
3 PLATFORM

FPD_BURNER-3-FILE_OP_ERR

3 PLATFORM

FPD_BURNER-3-NO_MEM
FPD_BURNER-5-progress

3 PLATFORM
5 PLATFORM

FPD_BURNER-5-version

5 PLATFORM

FPD-3-ERR

3 PLATFORM

FPD-3-INIT_ERR

3 PLATFORM

FPD-4-WARN

4 PLATFORM

FPD-6-INFO

6 PLATFORM

FPD-7-DEBUG

7 PLATFORM

FPGALIBASGARD-3-FPGA_PLL_ERR

3 PLATFORM

FPGALIBRPFPGA-3-FPGA_RP_ERR

3 PLATFORM

FPGAMGR-2-BOARD_RESTART

2 PLATFORM

FPGAMGR-2-BOARD_RESTART

2 PLATFORM

FPGAMGR-3-DEV_LIB_INIT

3 PLATFORM

FPGAMGR-3-INIT_FAIL

3 PLATFORM

FPGAMGR-3-LTRACE_OPEN_FAIL

3 PLATFORM

FPGAMGR-3-SHM_WIN_SETUP

3 PLATFORM

FPGAMGR-7-INIT_COMPLETE

7 PLATFORM

FSYNC-3-CHECKPOINT_ALLOC_FAIL

3 PLATFORM

FSYNC-3-CHECKPOINT_NOT_INITIALIZED

3 PLATFORM

FSYNC-3-CHKPT_ALLOC_FAIL

3 PLATFORM

FSYNC-3-CHKPT_NOT_INITIALIZED

3 PLATFORM

FSYNC-3CLOCK_BATCH_CONFIG_NOT_SUPPORTED_I
N_HARDWARE

3 PLATFORM

FSYNC-3CLOCK_CONFIG_NOT_SUPPORTED_IN_HARD
WARE

3 PLATFORM

FSYNC-3CLOCK_PORT_CONFIG_NOT_SUPPORTED_IN
_HARDWARE

3 PLATFORM

FSYNC-3-CONN_FAIL

3 PLATFORM

FSYNC-3-CONNECTION_FAIL

3 PLATFORM

FSYNC-3-FIXME

3 PLATFORM

FSYNC-3-INIT_FAIL

3 PLATFORM

FSYNC-3-INIT_FAILED

3 PLATFORM

FSYNC-3-NOT_SUPPORTED

3 PLATFORM

FSYNC-3-VER_MISMATCH

3 PLATFORM

FSYNC-4-INIT_FAILED

4 PLATFORM

FSYNC-5CLOCK_INTERFACE_0_OUTPUT_SQUELCHED

5 PLATFORM

FSYNC-5CLOCK_INTERFACE_0_SENDING_AIS

5 PLATFORM

FSYNC-5-CLOCK_INTERFACE_0_TX_DISABLE

5 PLATFORM

FSYNC-5CLOCK_INTERFACE_1_OUTPUT_SQUELCHED

5 PLATFORM

FSYNC-5CLOCK_INTERFACE_1_SENDING_AIS

5 PLATFORM

FSYNC-5-CLOCK_INTERFACE_1_TX_DISABLE

5 PLATFORM

FSYNC-5CLOCK_INTERFACE_PORT_0_OUTPUT_SQUEL
CHED

5 PLATFORM

FSYNC-5CLOCK_INTERFACE_PORT_0_SENDING_AIS

5 PLATFORM

FSYNC-5CLOCK_INTERFACE_PORT_0_TX_DISABLE

5 PLATFORM

FSYNC-5CLOCK_INTERFACE_PORT_1_OUTPUT_SQUEL
CHED

5 PLATFORM

FSYNC-5CLOCK_INTERFACE_PORT_1_SENDING_AIS

5 PLATFORM

FSYNC-5CLOCK_INTERFACE_PORT_1_TX_DISABLE

5 PLATFORM

FSYNC-6-INIT_INFO

6 PLATFORM

FSYNC-6-NOT_SUPPORTED

6 PLATFORM

FSYNC-6-UNKNOWN_BOARD_TYPE

6 PLATFORM

FWD_HAL_BGP-3-NH_SHM_INIT

3 PLATFORM

FWD_HAL_BGP-3-NH_SHM_MALLOC

3 PLATFORM

FWD_HAL_BGP-3-SHM_POOL_CREATE

3 PLATFORM

G_PLIM_QOS-3-ERROR

3 PLATFORM

G_PLIM_QOS-6-INFO

6 PLATFORM

GE_DMAC-3-MLAN_LINK_STATE_CHANGE

3 PLATFORM

GE_DMAC-3-OPERATION_FAIL

3 PLATFORM

GE_DMAC-3-OPERATION_FAIL

3 PLATFORM

GE_DMAC-6-UPDN

6 PLATFORM

GE_DMAC-6-UPDN

6 PLATFORM

GSP_EM-5-DEBUG_INIT_FAIL

5 PLATFORM

GSP_EM-6-FABRIC_MEDIA_DISABLED

6 PLATFORM

GSR_AIPC_LIB-3-CRC_ERR

3 PLATFORM

GSR_FIB_STATS_API-3-ERROR

3 PLATFORM

GSR_IPV4_EA-3-ERROR

3 PLATFORM

GSR_IPv6_EA-3-ERROR

3 PLATFORM

GSR_lc_exmem-0-SHMWIN_FREE

--

PLATFORM

GSR_lc_exmem-0-SHMWIN_MALLOC

--

PLATFORM

GSR_lc_exmem-0-SHMWIN_PLAT

--

PLATFORM

GSR_lc_exmem-1-RES_ERROR

1 PLATFORM

GSR_lc_exmem-3-ERROR

3 PLATFORM

GSR_lc_exmem-3-FATAL

3 PLATFORM

GSR_lc_exmem-3-GET_THREAD_PARAM

3 PLATFORM

GSR_lc_exmem-3-SET_THREAD_PARAM

3 PLATFORM

GSR_lc_exmem-6-INFO_MSG

6 PLATFORM

GSR_LC_PM-2-FAULT_LC

2 PLATFORM

GSR_LC_PM-2-FAULT_LC

2 PLATFORM

GSR_LC_PM-3-CONN_ERR

3 PLATFORM

GSR_LC_PM-3-ENGINE_PORT

3 PLATFORM

GSR_LC_PM-3-FATAL

3 PLATFORM

GSR_LC_PM-3-FATAL_2

3 PLATFORM

GSR_LC_PM-3IMC_CONTROL_SERVER_BIND_FAIL

3 PLATFORM

GSR_LC_PM-3-INIT_ERR

3 PLATFORM

GSR_LIB-3-COMM_MAGIC

3 PLATFORM

GSR_LIB-3-CONN_ERR

3 PLATFORM

GSR_LIB-3-ERROR

3 PLATFORM

GSR_LIB-3-FILE_OPEN

3 PLATFORM

GSR_LIB-3-FILE_READ

3 PLATFORM

GSR_LIB-3-FSTAT

3 PLATFORM

GSR_LIB-3-GET_PARTNER

3 PLATFORM

GSR_LIB-3-LR_ERR

3 PLATFORM

GSR_LIB-3-MEMMAP

3 PLATFORM

GSR_LIB-3-MMAP_INT_REG

3 PLATFORM

GSR_LIB-3-SHM_MEM_INCONSISTENT

3 PLATFORM

GSR_LIB-3-SHM_OPEN

3 PLATFORM

GSR_LIB-3-THREAD_CREATE

3 PLATFORM

GSR_LIB-3-THREAD_DETACH

3 PLATFORM

GSR_LIB-3-UNMOUNT

3 PLATFORM

GSR_MPLS_EA-2-ADD_FEATURE

2 PLATFORM

GSR_MPLS_EA-3-ERROR

3 PLATFORM

GSR_PRP_PM-2-CRIT_DEVICE

2 PLATFORM

GSR_PRP_PM-3-HIGH_DEVICE

3 PLATFORM

GSR_PRP_PM-3-INIT_ERR

3 PLATFORM

GSR_PRP_PM-3-LOW_DEVICE

3 PLATFORM

GT_I2C-3-BACKPLANE

3 PLATFORM

GT_I2C-3-DRV_ERR

3 PLATFORM

GT_I2C-3-LOWER_FANTRAY

3 PLATFORM

GT_I2C-3-ONBOARD

3 PLATFORM

GT_I2C-3REWORK_AND_UPGRADE_REQUIRED

3 PLATFORM

GT_I2C-3-UNRECOVERABLE_BUS_HANG

3 PLATFORM

GT_I2C-3-UPPER_FANTRAY

3 PLATFORM

GT_I2C-7-BUS_HANG

7 PLATFORM

GT_I2C-7-BUS_UNHANG_SUCCESS

7 PLATFORM

HAL_COMM_DBG-3-ERR_INFO_VERBOSE

3 PLATFORM

HBAGENT-2-CAUSE_HBLOSS

2 PLATFORM

HBAGENT-2-FATAL

2 PLATFORM

HBAGENT-2-HANDOFF_FAILED

2 PLATFORM

HBAGENT-3-API_FAILURE

3 PLATFORM

HBAGENT-3-THREAD_CREATE

3 PLATFORM

HBAGENT-4ATTACH_RECONNECT_HANDLER

4 PLATFORM

HBAGENT-4-INIT_LTRACE

4 PLATFORM

HBAGENT-4-SET_HEARTBEAT_PRIORITY

4 PLATFORM

HBAGENT-4-SET_THREAD_PRIORITY

4 PLATFORM

HBAGENT-6-NODE_RELOAD

6 PLATFORM

HBAGENT-7HBLOSS_COLLECTION_IGNORED

7 PLATFORM

HBAGENT-7-RELOAD_NOTIFICATION_TEST

7 PLATFORM

HD-2-DEV_HARDDISK_DEVICE_ERR

2 PLATFORM

HD-3-DEV_HARDDISK_RESTART
HFR_IP_EA-3-CRITICAL
HFR_IP_EA-3-ERROR1
HFR_IP_EA-3-ERROR2
HFR_IP_EA-5-DEBUG
HFR_IPV6_EA-3-CRITICAL
HFR_IPV6_EA-3-ERROR1
HFR_IPV6_EA-3-ERROR2
HFR_IPV6_EA-5-DEBUG

3 PLATFORM
3 PLATFORM
3 PLATFORM
3 PLATFORM
5 PLATFORM
3 PLATFORM
3 PLATFORM
3 PLATFORM
5 PLATFORM

HFR_L2FIB_METRO_SHOW-3INVALID_ARG_TYPE

3 PLATFORM

HFR_L2FIB_METRO_SHOW-7INVALID_OPTION

7 PLATFORM

HFR_LCPM_SHOW-3-ERROR

3 PLATFORM

HFR_LCPM_SHOW-7-USAGE
HFR_MPLS_EA-3-ERR

7 PLATFORM
3 PLATFORM

HFR_MPLS_EA-3-ERRSTR
HFR_MPLS_EA-6-INFO

3 PLATFORM
6 PLATFORM

HFR_PM_CS-6-INFO

6 PLATFORM

HFR_PM_SHOW-3-ERROR

3 PLATFORM

HFR_PM_SHOW-7-USAGE

7 PLATFORM

HFR_PM_TEST-3-ERROR

3 PLATFORM

HFR_PM_TEST-3-ERROR_2

3 PLATFORM

HFR_PM-3-BAD_PMLIB_SERVER_CONTEXT

3 PLATFORM

HFR_PM-3-ERR_FAULT_FROM_DEVICE

3 PLATFORM

HFR_PM-3-ERROR

3 PLATFORM

HFR_PM-3-ERROR_INIT

3 PLATFORM

HFR_PM-3-MALLOC_FAILED

3 PLATFORM

HFR_PM-3-POLICE_GRAN

3 PLATFORM

HFR_PM-3-RELOAD_LC

3 PLATFORM

HFR_PM-4-WARNING

4 PLATFORM

HFR_PM-4-WARNING

4 PLATFORM

HFR_PM-7-ERROR

7 PLATFORM

HFR_PM-7-ERROR_INIT

7 PLATFORM

HFR_SPP-3-ERR_INIT

3 PLATFORM

HFR_SPP-3-ERR_MEM_ALLOC

3 PLATFORM

HFR_SPP-3-ERR_QUEUE_ELEMENT_SIZE

3 PLATFORM

HFR_SPP-3-ERR_THREAD

3 PLATFORM

HFR_TUNNEL_EA-3-ERROR

3 PLATFORM

HFR_TUNNEL_EA-3-ERROR_PARAM

3 PLATFORM

HFR_TUNNEL_EA-3-ERROR2

3 PLATFORM

HFR_TUNNEL_EA-3-ERROR3

3 PLATFORM

HFR_TUNNEL_EA-3-ERROR4

3 PLATFORM

HORSE-2-ERR

2 PLATFORM

HORSE-2-ERR_RC

2 PLATFORM

HPI-3-DETECTED_TX_PDMA_STALL

3 PLATFORM

HPI-3-DETECTED_TX_PDMA_STALL

3 PLATFORM

HPI-4-ACCESS_WIDTH_NOT_MATCH

4 PLATFORM

HPI-6-NO_BUF_TO_REPLACE

6 PLATFORM

HPI-6-NO_BUF_TO_REPLACE

6 PLATFORM

hytop-3-INTERNAL_FAILURE

3 PLATFORM

hytop-6-INFO_MSG

6 PLATFORM

I2C_DRV-3-UNRECOVERABLE_BUS_HANG

3 PLATFORM

I2C_DRV-3-UNRECOVERABLE_BUS_HANG

3 PLATFORM

I2C_DRV-7-BUS_UNHANG_SUCCESS

7 PLATFORM

I2C_DRV-7-BUS_UNHANG_SUCCESS

7 PLATFORM

I2C_DRV-7-SCL_HANG

7 PLATFORM

I2C_DRV-7-SCL_HANG

7 PLATFORM

I2C_DRV-7-SDA_HANG

7 PLATFORM

I2C_DRV-7-SDA_HANG

7 PLATFORM

I2C_MASTERSHIP-0ARBITRATION_LOCK_UNAVAILABLE

--

PLATFORM

I2C-0-ARBITRATION_LOCK_UNAVAILABLE

--

PLATFORM

I2C-2-ASIC_PLL_LOCK_FAILURE

2 PLATFORM

I2C-2-ASICS_NOT_RELEASED_FROM_RESET

2 PLATFORM

I2C-2CRS_X_FABRIC_VOLTAGE_SUPPLY_FAILED

2 PLATFORM

I2C-2-CRS_X_MSC_POWERUP_FAILED

2 PLATFORM

I2C-2-LC_POWER_NOT_READY

2 PLATFORM

I2C-2MSC_140_POWER_DISABLED_STATE_NOT_R
ECOVERED

2 PLATFORM

I2C-2MSC_140_POWER_DISABLED_STATE_POWE
R_DOWN

2 PLATFORM

I2C-2-PLIM_BYPASSED

2 PLATFORM

I2C-2-PLIM_DCEN

2 PLATFORM

I2C-2-PLIM_GENERATION_INCORRECT

2 PLATFORM

I2C-2-PLIM_NOT_PRESENT

2 PLATFORM

I2C-2-PLIM_NOT_READY

2 PLATFORM

I2C-2POGO_TCAMS_NOT_RELEASED_FROM_RESE
T

2 PLATFORM

I2C-2-PROXY_ECM_EXIT

2 PLATFORM

I2C-2-SUPERSTAR_VOLTAGE_SUPPLY_FAILED

2 PLATFORM

I2C-2-VOLT_ALARM_SHUTDOWN

2 PLATFORM

I2C-2-VOLTAGE_NOT_VALIDATED

2 PLATFORM

I2C-2-VOLTAGE_SUPPLY_FAILED

2 PLATFORM

I2C-3-BP_EN_ERROR

3 PLATFORM

I2C-3-EMPTY_BIT_NOT_CLEARED_ERROR

3 PLATFORM

I2C-3-ERR_INIT

3 PLATFORM

I2C-3-LC_BAD_VRM_INFO

3 PLATFORM

I2C-3-LC_POWER_FAIL

3 PLATFORM

I2C-3-PARK_FAIL

3 PLATFORM

I2C-4-CARD_RELOAD

4 PLATFORM

I2C-4-CRS_X_MSC_UNKNOWN_SW_REV

4 PLATFORM

I2C-6-VOLTAGE_VALIDATED
I2C-7-BOARD_POWERUP

6 PLATFORM
7 PLATFORM

I2C-7-BOARD_POWERUP_FAIL

7 PLATFORM

I2C-7-BOARD_POWERUP_NOT_HAPPENED

7 PLATFORM

I2C-7-HANDLE_PARK_MUX

7 PLATFORM

I2C-7-HANDLE_POWER_DOWN

7 PLATFORM

I2C-7-LC_POWERUP_CHECK_FAIL

7 PLATFORM

I2C-7-PLIM_NOT_POWERED_UP

7 PLATFORM

I2C-7-SEND_PULSE_FAIL

7 PLATFORM

I2C-7-SHELFMGR_PULSE_FAILED

7 PLATFORM

I2CCTRL-2-IO_FAIL

2 PLATFORM

I2CCTRL-2-MASTERSHIP_DENIED

2 PLATFORM

I2CCTRL-2-STUCK_LOW

2 PLATFORM

I2CCTRL-2-TRANSACTION_INTERRUPTED

2 PLATFORM

ILITE-3-COMMON_ERROR

3 PLATFORM

IMIO-3-INVALID_SLOT

3 PLATFORM

IMIO-3-OPERATION_FAIL
IMIO-3-OPERATION_NOTIFY

3 PLATFORM
3 PLATFORM

IMUX-0-SEM_UNCORR_ERR

--

PLATFORM

IMUX-1-LOSS_OF_SYNC

1 PLATFORM

IMUX-1-RX_BRST_LEN_ERR

1 PLATFORM

IMUX-1-RX_BRST_MAX_ERR

1 PLATFORM

IMUX-1-RX_EOP_ERR

1 PLATFORM

IMUX-1-RX_ILKN_ERR

1 PLATFORM

IMUX-1-RX_MTA_FRM_LEN_ERR

1 PLATFORM

IMUX-1-RX_MTA_FRM_RPT_ERR

1 PLATFORM

IMUX-1-RX_MTA_FRM_SYN_ERR

1 PLATFORM

IMUX-1-RX_MTA_FRM_TYP_ERR

1 PLATFORM

IMUX-1-RX_OVF_ERR

1 PLATFORM

IMUX-1-RX_SOP_ERR

1 PLATFORM

IMUX-3-CF_MBE_ERR_FIA00

3 PLATFORM

IMUX-3-CF_MBE_ERR_FIA01

3 PLATFORM

IMUX-3-CF_MBE_ERR_FIA10

3 PLATFORM

IMUX-3-CF_MBE_ERR_FIA11

3 PLATFORM

IMUX-3-CF_OVF_ERR_FIA00

3 PLATFORM

IMUX-3-CF_OVF_ERR_FIA01

3 PLATFORM

IMUX-3-CF_OVF_ERR_FIA10

3 PLATFORM

IMUX-3-CF_OVF_ERR_FIA11

3 PLATFORM

IMUX-3-CF_SBE_ERR_FIA00

3 PLATFORM

IMUX-3-CF_SBE_ERR_FIA01

3 PLATFORM

IMUX-3-CF_SBE_ERR_FIA10

3 PLATFORM

IMUX-3-CF_SBE_ERR_FIA11

3 PLATFORM

IMUX-3-SEM_CRIT_ERR

3 PLATFORM

IMUX-3-TEMP_ERR

3 PLATFORM

IMUX-3-TX_BRST_SHRT_ERR_FIA00

3 PLATFORM

IMUX-3-TX_BRST_SHRT_ERR_FIA01

3 PLATFORM

IMUX-3-TX_BRST_SHRT_ERR_FIA10

3 PLATFORM

IMUX-3-TX_BRST_SHRT_ERR_FIA11

3 PLATFORM

IMUX-3-TX_FF_OVF_ERR_FIA00

3 PLATFORM

IMUX-3-TX_FF_OVF_ERR_FIA01

3 PLATFORM

IMUX-3-TX_FF_OVF_ERR_FIA10

3 PLATFORM

IMUX-3-TX_FF_OVF_ERR_FIA11

3 PLATFORM

IMUX-3-TX_OVF_ERR_FIA00

3 PLATFORM

IMUX-3-TX_OVF_ERR_FIA01

3 PLATFORM

IMUX-3-TX_OVF_ERR_FIA10

3 PLATFORM

IMUX-3-TX_OVF_ERR_FIA11

3 PLATFORM

IMUX-3-TX_UNF_ERR_FIA00

3 PLATFORM

IMUX-3-TX_UNF_ERR_FIA01

3 PLATFORM

IMUX-3-TX_UNF_ERR_FIA10

3 PLATFORM

IMUX-3-TX_UNF_ERR_FIA11

3 PLATFORM

IMUX-3-VCCINT_ERR

3 PLATFORM

INTCTRL-2-BLG_RDY_ERROR

2 PLATFORM

INTCTRL-2-BLG_RX_PAR_ERROR

2 PLATFORM

INTCTRL-2-BLG_TX_PAR_ERROR

2 PLATFORM

INTCTRL-2-CLKCTRL_DACK_ERROR

2 PLATFORM

INTCTRL-2-CLKCTRL_RX_PAR_ERROR

2 PLATFORM

INTCTRL-2-CLKCTRL_TX_PAR_ERROR

2 PLATFORM

INTCTRL-2-CPU_PRT_A_ERROR

2 PLATFORM

INTCTRL-2-CPU_PRT_D_ERROR

2 PLATFORM

INTCTRL-2-DEV_VERSION_ERROR

2 PLATFORM

INTCTRL-2-OCT_RDY_ERROR

2 PLATFORM

INTCTRL-2-OCT_RX_PAR_ERROR

2 PLATFORM

INTCTRL-2-OCT_TX_PAR_ERROR

2 PLATFORM

INTCTRL-2-PUNT_RDY_ERROR

2 PLATFORM

INTCTRL-2-PUNT_RX_PAR_ERROR

2 PLATFORM

INTCTRL-2-PUNT_TX_PAR_ERROR

2 PLATFORM

INTCTRL-2-THERM_ALARM_ERROR

2 PLATFORM

INTCTRL-2-THERM_OVERT_ERROR

2 PLATFORM

INTCTRL-3-ERR_INIT

3 PLATFORM

INTCTRL-3-ERR_LTRACE_INIT

3 PLATFORM

INTCTRL-3-ERR_MEM_ALLOC

3 PLATFORM

INTCTRL-5-ERR_CONT

5 PLATFORM

INTCTRL-7-ERR_EVM_CREATE

7 PLATFORM

INTCTRL-7-ERR_EVM_NOTIFY

7 PLATFORM

INTCTRL-7-ERR_EXIT

7 PLATFORM

INTCTRL-7-ERR_LWM_EVENT_BLOCK

7 PLATFORM

INTCTRL-7-ERR_LWM_REPLY

7 PLATFORM

INTEG_SWITCH-2-LINK_STATE_CHANGE

2 PLATFORM

INTEG_SWITCH-5-LINK_SHUT_DOWN

5 PLATFORM

INTF_EA_SHOW-3-ERROR

3 PLATFORM

INTF_EA_SHOW-7-USAGE

7 PLATFORM

INTF_EA-3BAD_INTF_EALIB_SERVER_CONTEXT

3 PLATFORM

INTF_EA-3-ERROR

3 PLATFORM

INTF_EA-3-ERROR_INIT

3 PLATFORM

INTF_EA-3-POLICE_GRAN

3 PLATFORM

INTF_EA-3-RELOAD_LC

3 PLATFORM

INTF_EA-4-WARNING

4 PLATFORM

INV_AGENT-3-ERROR_EXIT

3 PLATFORM

INV_AGENT-3-OPT_FAIL

3 PLATFORM

INV_AGENT-6-IF_OIRIN

6 PLATFORM

INV_AGENT-6-IF_OIROUT

6 PLATFORM

INV_AGENT-7-INFO

7 PLATFORM

INV-3-THREADPOOL_FAIL

3 PLATFORM

INV-6-CARD_OIRIN

6 PLATFORM

INV-6-CF_OIRIN

6 PLATFORM

INV-6-CF_OIROUT

6 PLATFORM

INV-6-IF_OIRIN

6 PLATFORM

INV-6-IF_OIROUT

6 PLATFORM

INV-6-NODE_STATE_CHANGE

6 PLATFORM

INV-6-NODE_STATE_CHANGE

6 PLATFORM

INV-6-OIRIN

6 PLATFORM

INV-6-OIROUT

6 PLATFORM

INV-6-XFP_OIR

6 PLATFORM

INV-7-CARD_FAILURE

7 PLATFORM

INV-7-ERR

7 PLATFORM

INV-7-ERR_DLL

7 PLATFORM

INV-7-ERR_EDM_CREATE

7 PLATFORM

INV-7-ERR_EDM_OPEN

7 PLATFORM

INV-7-ERR_MEM_ALLOC

7 PLATFORM

INV-7-ERR_RACK_CREATE

7 PLATFORM

INV-7-FAIL_DLL

7 PLATFORM

INV-7-FAIL_EDM_CREATE

7 PLATFORM

INV-7-FAIL_EDM_OPEN

7 PLATFORM

INV-7-FAIL_MEM_ALLOC

7 PLATFORM

INV-7-FAIL_RACK_CREATE

7 PLATFORM

INV-7-SYSDB_ERR

7 PLATFORM

INVMGR-3-EEPROM_READ

3 PLATFORM

INVMGR-3-ERR_EEPROM_READ

3 PLATFORM

INVMGR-3-ERR_EEPROM_READ

3 PLATFORM

INVMGR-3-ERR_INIT

3 PLATFORM

INVMGR-3-ERR_INIT

3 PLATFORM

INVMGR-3-ERR_MEM_ALLOC

3 PLATFORM

INVMGR-3-ERR_MEM_ALLOC

3 PLATFORM

INVMGR-3-ERR_NODEID_CREATE

3 PLATFORM

INVMGR-3-ERR_NODEID_CREATE

3 PLATFORM

INVMGR-3-ERR_OBJECT_CREATE

3 PLATFORM

INVMGR-3-ERR_OBJECT_CREATE

3 PLATFORM

INVMGR-3-ERR_SENSOR_CREATE

3 PLATFORM

INVMGR-3-ERR_SENSOR_CREATE

3 PLATFORM

INVMGR-3-ERR_SYSDB_BIND

3 PLATFORM

INVMGR-3-ERR_SYSDB_BIND

3 PLATFORM

INVMGR-3-ERR_SYSDB_REG_NOTIFY

3 PLATFORM

INVMGR-3-ERR_SYSDB_REG_NOTIFY

3 PLATFORM

INVMGR-3-FAILURE

3 PLATFORM

INVMGR-3-INIT

3 PLATFORM

INVMGR-3-MEM_ALLOC

3 PLATFORM

INVMGR-3-NODEID

3 PLATFORM

INVMGR-3-NODEID_CREATE

3 PLATFORM

INVMGR-3-OBJECT_CREATE

3 PLATFORM

INVMGR-3-SENSOR_CREATE

3 PLATFORM

INVMGR-3-SYSDB_BIND

3 PLATFORM

INVMGR-3-SYSDB_REG_NOTIFY

3 PLATFORM

INVMGR-3-SYSDB_SETUP_FAIL

3 PLATFORM

INVMGR-5-OIRIN

5 PLATFORM

INVMGR-5-OIRIN

5 PLATFORM

INVMGR-5-OIRIN

5 PLATFORM

INVMGR-5-OIROUT

5 PLATFORM

INVMGR-5-OIROUT

5 PLATFORM

INVMGR-5-OIROUT
INVMGR-6-INFO

5 PLATFORM
6 PLATFORM

INVMGR-6-NODE_STATE_CHANGE

6 PLATFORM

INVMGR-6-NODE_STATE_CHANGE

6 PLATFORM

INVMGR-6-NODE_STATE_CHANGE

6 PLATFORM

INVMGR-7-ERR

7 PLATFORM

INVMGR-7-ERR_API

7 PLATFORM

INVMGR-7-ERR_API

7 PLATFORM

INVMGR-7-ERR_API

7 PLATFORM

INVMGR-7-ERR_NODEID

7 PLATFORM

INVMGR-7-ERR_NODEID

7 PLATFORM

INVMGR-7-FAIL

7 PLATFORM

INVMGR-7-FAIL

7 PLATFORM

INVMGR-7-FAIL

7 PLATFORM

IPCP_SRVR-3-RT_FAIL

3 PLATFORM

IPCP_SRVR-3-SW_INIT_ERROR

3 PLATFORM

IPCP_SRVR-3-SW_INIT_ERROR

3 PLATFORM

IPCP_SRVR-6IPCP_SERVER_RESTARTED_NODE_REBOOTI
NG

6 PLATFORM

IPCP_SRVR-6IPCP_SERVER_RESTARTED_NODE_REBOOTI
NG

6 PLATFORM

JBI-3-ERROR

3 PLATFORM

JBI-6-INFO

6 PLATFORM

JBI-7-DEBUG

7 PLATFORM

KD-3-FILE_OPEN_FAILURE

3 PLATFORM

KENSHO_GL-3-INIT_ERROR

3 PLATFORM

KENSHO_GL-3-LTRACE_INIT_ERROR

3 PLATFORM

KENSHO_GL-3-PCIE_ATTACH_FAIL

3 PLATFORM

KENSHO_GL-4-WARNING

4 PLATFORM

KENSHO_GL-6-INFO

6 PLATFORM

L2FIB_ALARM-3-MAC_LEARN

3 PLATFORM

L2FIB_ALARM-3-MAX_AC_PER_BRG_PER_NP

3 PLATFORM

L2FIB_ALARM-3MAX_BRGMEM_ENTRY_PER_NP

3 PLATFORM

L2FIB_ALARM-3-STORM_CONTROL

3 PLATFORM

LAMPTEST-6-ABORTED

6 PLATFORM

LAMPTEST-6-COMPLETE

6 PLATFORM

LAMPTEST-6-INITIATED

6 PLATFORM

LAMPTEST-6-REJECTED

6 PLATFORM

LC_CPIDB-2-INIT

2 PLATFORM

LC_CPIDB-2-OPEN

2 PLATFORM

LC_CPIDB-3-ERROR

3 PLATFORM

LC_CPIDB-4-WARN

4 PLATFORM

LC_CPIDB-6-INFO

6 PLATFORM

LC_CPPIF-2-INIT

2 PLATFORM

LC_CPPIF-2-OPEN

2 PLATFORM

LC_CPPIF-3-ERROR

3 PLATFORM

LC_CPPIF-4-WARN

4 PLATFORM

LC_CPPIF-6-INFO

6 PLATFORM

LC_CPUCTRL-0-NO_RSP_ACT_ERROR

--

PLATFORM

LC_CPUCTRL-0-NO_RSP_PRESENT_ERROR

--

PLATFORM

LC_CPUCTRL-2-ACT_ARB_ERROR

2 PLATFORM

LC_CPUCTRL-2-ACT_RSP_ERROR

2 PLATFORM

LC_CPUCTRL-2-BOARD_REV_ERROR

2 PLATFORM

LC_CPUCTRL-2-BOARD_REV_PAR_ERROR

2 PLATFORM

LC_CPUCTRL-2-DEV_VERSION_ERROR

2 PLATFORM

LC_CPUCTRL-2-NO_ARB_ACT_ERROR

2 PLATFORM

LC_CPUCTRL-2-NO_FAB_ACT_ERROR

2 PLATFORM

LC_CPUCTRL-2-RSP_PAR_ERROR

2 PLATFORM

LC_CPUCTRL-2-TX_RX_PAR_ERROR

2 PLATFORM

LC_FPGA_UPGRADE-2BOARD_HW_DBG_MODE

2 PLATFORM

LC_PIDB-2-INIT

2 PLATFORM

LC_PIDB-2-INIT_FAILURE

2 PLATFORM

LC_PIDB-2-OPEN

2 PLATFORM

LC_PIDB-3-ERROR

3 PLATFORM

LC_PIDB-3-FAILURE

3 PLATFORM

LC_PIDB-4-OPEN_FAILURE

4 PLATFORM

LC_PIDB-4-WARN

4 PLATFORM

LC_PIDB-6-INFO

6 PLATFORM

LC_QFPCPUCTRL-1-BOARD_REV_ERROR

1 PLATFORM

LC_QFPCPUCTRL-1BOARD_REV_PAR_ERROR

1 PLATFORM

LC_QFPCPUCTRL-1-CPU_PAR_ERROR

1 PLATFORM

LC_QFPCPUCTRL-1-DEV_ID_ERROR

1 PLATFORM

LC_QFPCPUCTRL-1-DEV_VERSION_ERROR

1 PLATFORM

LC_QFPCPUCTRL-1-ERP_PAR_ERROR_0

1 PLATFORM

LC_QFPCPUCTRL-1-ERP_PAR_ERROR_1

1 PLATFORM

LC_QFPCPUCTRL-1-FATAL_ERR_INTR

1 PLATFORM

LDA-2-MPA_IDENT_SKIPPED

2 PLATFORM

LDA-3-DBCTRL_INIT_FAILED

3 PLATFORM

LDA-3-INIT_FAIL

3 PLATFORM

LDA-3-MPA_INIT_FAIL

3 PLATFORM

LDA-3-MPA_INIT_VIC_START_FAILED

3 PLATFORM

LDA-3-MPA_PHY_INIT_FAILED

3 PLATFORM

LDA-3-MPA_POWER_FAILURE

3 PLATFORM

LDA-3-MPA_SW_ERROR

3 PLATFORM

LDA-3-PHY_INIT_FAIL

3 PLATFORM

LDA-3-SHMEM_INIT_FAIL

3 PLATFORM

LDA-3-SW_INIT_FAIL

3 PLATFORM

LDA-3-TIMING_FAILURE

3 PLATFORM

LDA-4-LTRACE_INIT_ERROR

4 PLATFORM

LDA-4-MAP_EP_SHMEM_FAILED

4 PLATFORM

LDA-4-MPA_IDPROM_READ_WARNING

4 PLATFORM

LDA-4-MPA_IDPROM_SW_WARNING

4 PLATFORM

LDA-4-MPA_NP_CLEANUP_FAILED

4 PLATFORM

LDA-4MPA_OIR_QUICK_BACK_TO_BACK_ERROR

4 PLATFORM

LDA-4-MPA_SHUT_VIC_WARNING

4 PLATFORM

LDA-4-WARNING

4 PLATFORM

LDA-6-INFO

6 PLATFORM

LDA-6-OPCODE_NOT_SUPPORTED

6 PLATFORM

LIB_ISOLATION-3-FAILURE

3 PLATFORM

LIB_ISOLATION-3-FAILURE

3 PLATFORM

LIB_ISOLATION-6-INFO

6 PLATFORM

LIB_ISOLATION-7-SUCCESS

7 PLATFORM

LIB_ISOLATION-7-SUCCESS

7 PLATFORM

libpcmcia_ide-1-CARD_REMOVE

1 PLATFORM

libpcmcia_ide-5-CARD_INSERT

5 PLATFORM

libpcmcia_linux-4-SPAWN_FAILED

4 PLATFORM

libpcmcia_linux-7-CHILD_SPAWN

7 PLATFORM

libpcmcia_linux-7-FD_UNAVAILABLE

7 PLATFORM

libpcmcia_linux-7-FUNCTION_FAILED

7 PLATFORM

libpcmcia_linux-7-MALLOC_FAILED

7 PLATFORM

libpcmcia_linux-7-NO_SPAWN_PARAM

7 PLATFORM

libpcmcia_linux-7-OPEN_FAILED

7 PLATFORM

libpcmcia_linux-7-SLEEPON_LOCK_FAILED

7 PLATFORM

LIC_UDI-3-ACQUIRE_FAILURE

3 PLATFORM

LIC_UDI-3-ACQUIRE_FAILURE

3 PLATFORM

LIC_UDI-6-INFO

6 PLATFORM

LIC_UDI-7-ERR_EVM_CREATE
LIC_UDI-7-ERR_INTERNAL
LIC_UDI-7-ERR_INTERNAL
LIC_UDI-7-ERR_MALLOC

7 PLATFORM
7 PLATFORM
7 PLATFORM
7 PLATFORM

LIC_UDI-7-ERR_SYSDB_REG_NOTIF

7 PLATFORM

MACE_CLIENT-0-ERR_MEMORY_MAP

--

PLATFORM

MANSDORF-3-INIT_FAILURE

3 PLATFORM

MANSDORF-3-NO_INTR_HANDLER

3 PLATFORM

MANSDORF-3-SQUID_DMA_REQ_FAILURE

3 PLATFORM

MANSDORF-6-GENERIC_EVENT

6 PLATFORM

MANSDORF-6-GENERIC_EVENT_FAILURE

6 PLATFORM

MBI_HELLO-2-CAUSE_HBLOSS

2 PLATFORM

MBI_HELLO-2-ETHSERVER_DOWN

2 PLATFORM

MBI_HELLO-2ETHSERVER_REGISTRATION_FAILURE

2 PLATFORM

MBI_HELLO-2-FAILED

2 PLATFORM

MBI_HELLO-2-HBLOSS_COLLECT_LOGS

2 PLATFORM

MBI_HELLO-2-HEADLESS_RSP_DETECTED

2 PLATFORM

MBI_HELLO-2HEADLESS_RSP_TIMER_INIT_FAILED

2 PLATFORM

MBI_HELLO-2-INIT_FAILURE

2 PLATFORM

MBI_HELLO-2-NODE_RELOAD

2 PLATFORM

MBI_HELLO-2-NODE_RELOAD

2 PLATFORM

MBI_HELLO-2-NODE_RELOAD_NOW

2 PLATFORM

MBI_HELLO-3-API_FAILURE

3 PLATFORM

MBI_HELLO-3CANNOT_RUN_HBLOSS_SCRIPT

3 PLATFORM

MBI_HELLO-3-CLOCK_FAIL

3 PLATFORM

MBI_HELLO-3-CORRUPTED_HB_REQ_MSG

3 PLATFORM

MBI_HELLO-3-ETHSERVER_CONNECT

3 PLATFORM

MBI_HELLO-3ETHSERVER_MSG_HANDLING_FAILURE

3 PLATFORM

MBI_HELLO-3-ETHSERVER_WRITE

3 PLATFORM

MBI_HELLO-3-HBLOSS_SCRIPT_ERROR

3 PLATFORM

MBI_HELLO-3-HEADLESS_RSP_TIMER

3 PLATFORM

MBI_HELLO-3-INIT_FAILURE

3 PLATFORM

MBI_HELLO-3-MALLOC_FAIL

3 PLATFORM

MBI_HELLO-3-MSG_SEND_FAIL

3 PLATFORM

MBI_HELLO-3REQUEST_NETMGR_MOUNTPOINT_FAIL

3 PLATFORM

MBI_HELLO-3-SERVER_CONNECT_FAIL

3 PLATFORM

MBI_HELLO-3-SHMEM_ALLOC_FAILURE

3 PLATFORM

MBI_HELLO-3-THREAD_CREATE

3 PLATFORM

MBI_HELLO-3-THREAD_CREATE

3 PLATFORM

MBI_HELLO-3-TIMER_TIMEOUT

3 PLATFORM

MBI_HELLO-4ATTACH_RECONNECT_HANDLER

4 PLATFORM

MBI_HELLO-4ATTACH_RECONNECT_HANDLER

4 PLATFORM

MBI_HELLO-4-CARD_SIZE_HUGE

4 PLATFORM

MBI_HELLO-4-INIT_LTRACE

4 PLATFORM

MBI_HELLO-4-PRIORITY_SET_FAILURE

4 PLATFORM

MBI_HELLO-4-QUEUE_WAIT_FAILURE

4 PLATFORM

MBI_HELLO-4-SET_HEARTBEAT_PRIORITY

4 PLATFORM

MBI_HELLO-4-SET_HEARTBEAT_PRIORITY

4 PLATFORM

MBI_HELLO-4-SET_THREAD_PRIORITY

4 PLATFORM

MBI_HELLO-4-SET_THREAD_PRIORITY

4 PLATFORM

MBI_HELLO-6-IMDR_COMPLETED

6 PLATFORM

MBI_HELLO-6-IMDR_STARTED

6 PLATFORM

MBI_HELLO-6-IMDR_STATE_INFO

6 PLATFORM

MBI_HELLO-6-INIT_LTRACE

6 PLATFORM

MBI_HELLO-6-LTRACE_INIT_FAILURE

6 PLATFORM

MBI_HELLO-6-NODE_PWRCYL

6 PLATFORM

MBI_HELLO-6-NODE_PWRDWN

6 PLATFORM

MBI_HELLO-6-NODE_RELOAD

6 PLATFORM

MBI_HELLO-7-ERR_MSG_SEND

7 PLATFORM

MBI_HELLO-7ERR_NETMGR_MOUNTPOINT_REQUEST

7 PLATFORM

MBI_HELLO-7-ERR_SERVER_CONNECT

7 PLATFORM

MBI_HELLO-7-HBAGENT_EXISTS

7 PLATFORM

MBI_HELLO-7HBLOSS_COLLECT_COMPLETED

7 PLATFORM

MBI_HELLO-7HBLOSS_COLLECTION_IGNORED

7 PLATFORM

MBI_HELLO-7-INFO_CREATE_SUCCESS

7 PLATFORM

MBI_HELLO-7-MEM_ALLOC_FAILURE

7 PLATFORM

MBI_HELLO-7-RELOAD_NOTIFICATION_TEST

7 PLATFORM

MBI_HELLO-7-RELOAD_NOTIFICATION_TEST

7 PLATFORM

MBI_HELLO-7-TIMER_TIMEOUT

7 PLATFORM

MBI_HELLO-7-WARNING

7 PLATFORM

MBI_LIB_ACCESS-3-MSG_SEND_FAIL

3 PLATFORM

MBI_LIB_ACCESS-3-MSG_SEND_FAIL

3 PLATFORM

MBI_LIB_ACCESS-3-SERVER_CONNECT_FAIL

3 PLATFORM

MBI_LIB_ACCESS-3-SERVER_CONNECT_FAIL

3 PLATFORM

MBI_LIB_ACCESS-7-ERR_MSG_SEND

7 PLATFORM

MBI_LIB_ACCESS-7-ERR_SERVER_CONNECT

7 PLATFORM

MBI_LIB-3-MSG_SEND_FAIL

3 PLATFORM

MBI_LIB-3-MSG_SEND_FAIL

3 PLATFORM

MBI_LIB-3-MSG_SEND_FAIL

3 PLATFORM

MBI_LIB-3-SERVER_CONNECT_FAIL

3 PLATFORM

MBI_LIB-3-SERVER_CONNECT_FAIL

3 PLATFORM

MBI_LIB-3-SERVER_CONNECT_FAIL

3 PLATFORM

MBI_LIB-4-CLOCK_FAIL

4 PLATFORM

MBI_LIB-4-CLOCK_FAIL

4 PLATFORM

MBIMGR-3-COPY_MBI_FILE_NAME_FAIL

3 PLATFORM

MBIMGR-3-COPY_MBI_FILE_NAME_FAIL

3 PLATFORM

MBIMGR-3-DEFAULT_MBI_FAIL

3 PLATFORM

MBIMGR-3-DEFAULT_MBI_FAIL

3 PLATFORM

MBIMGR-3-FAILED_TO_CALCULATE_MD5

3 PLATFORM

MBIMGR-3-FAILED_TO_CALCULATE_MD5

3 PLATFORM

MBIMGR-3-FAILED_TO_COMPARE_MD5

3 PLATFORM

MBIMGR-3-FAILED_TO_COMPARE_MD5

3 PLATFORM

MBIMGR-3-IGNORING_MBI

3 PLATFORM

MBIMGR-3-IGNORING_MBI

3 PLATFORM

MBIMGR-3-INVALID_ARG

3 PLATFORM

MBIMGR-3-INVALID_NODE

3 PLATFORM

MBIMGR-3-MALLOC_FAIL

3 PLATFORM

MBIMGR-3-MALLOC_FAIL

3 PLATFORM

MBIMGR-3-NODEID_EXTRACT_FAIL

3 PLATFORM

MBIMGR-3-NODEID_EXTRACT_FAIL

3 PLATFORM

MBIMGR-3-NODEID_FAIL

3 PLATFORM

MBIMGR-3-NODEID_FAIL

3 PLATFORM

MBIMGR-3-NODEID_TO_IP_ADDR_FAIL

3 PLATFORM

MBIMGR-3-NODEID_TO_IP_ADDR_FAIL

3 PLATFORM

MBIMGR-3NODEID_TO_STR_EXTERNAL_FAIL

3 PLATFORM

MBIMGR-3NODEID_TO_STR_EXTERNAL_FAIL

3 PLATFORM

MBIMGR-3-NULL_PTR

3 PLATFORM

MBIMGR-3-NULL_PTR

3 PLATFORM

MBIMGR-3REMOTE_NODEID_MSG_STR_CREATE_FAIL

3 PLATFORM

MBIMGR-3-TFTP_INFO_FAIL

3 PLATFORM

MBIMGR-3-TFTP_INFO_FAIL

3 PLATFORM

MBIMGR-3-UNKNOWN_BOARDTYPE

3 PLATFORM

MBIMGR-3-UNKNOWN_BOARDTYPE

3 PLATFORM

MBIMGR-4REMOTE_NODEID_MSG_STR_CREATE_FAIL

4 PLATFORM

MBIMGR-6-MBIVSN_DIGIT_INFO
MBIMGR-6-MBIVSN_DIGIT_INFO

6 PLATFORM
6 PLATFORM

MBIMGR-6-MBIVSN_STR_INFO
MBIMGR-6-MBIVSN_STR_INFO

6 PLATFORM
6 PLATFORM

MBIMGR-7-IMAGE_VALIDATED

7 PLATFORM

MBIMGR-7-IMAGE_VALIDATED

7 PLATFORM

MBIMGR-7-INVALID_MBIVSN

7 PLATFORM

MBIMGR-7-INVALID_MBIVSN

7 PLATFORM

MBUS-4-SVC_AGENT_ROM_DOWN_REV

4 PLATFORM

MBUS-4-SVC_AGENT_ROM_DOWN_REV

4 PLATFORM

MBUS-4-SVC_AGENT_ROM_DOWN_REV

4 PLATFORM

MBUS-4-SVC_ZERO_LEN_PKT

4 PLATFORM

MBUS-4-SVC_ZERO_LEN_PKT

4 PLATFORM

MBUS-4-SVC_ZERO_LEN_PKT

4 PLATFORM

MBUS-7-API_DEBUG

7 PLATFORM

MBUS-7-API_DOWNLOAD_FAIL_STATUS

7 PLATFORM

MBUS-7-API_FILE_OPERATION_FAILED

7 PLATFORM

MBUS-7-API_INFO

7 PLATFORM

MBUS-7-API_INFO_DUMP

7 PLATFORM

MBUS-7-API_INVALID_SLOT
MBUS-7-API_NULL_PARAMETER

7 PLATFORM
7 PLATFORM

MBUS-7-ATTACH_DEBUG

7 PLATFORM

MBUS-7-ATTACH_ERR
MBUS-7-ATTACH_INFO_DUMP

7 PLATFORM
7 PLATFORM

MBUS-7-CLIENT_FAILURE

7 PLATFORM

MBUS-7-MSG_INFO_DUMP

7 PLATFORM

MBUS-7-MSG_INFO_DUMP

7 PLATFORM

MBUS-7-SVC_AGENT_CHECK_FAILED

7 PLATFORM

MBUS-7-SVC_AGENT_CHECK_FAILED

7 PLATFORM

MBUS-7-SVC_AGENT_CHECK_FAILED

7 PLATFORM

MBUS-7-SVC_DEBUG

7 PLATFORM

MBUS-7-SVC_DEBUG

7 PLATFORM

MBUS-7-SVC_DEBUG

7 PLATFORM

MBUS-7-SVC_EOF_UNEXPECTED

7 PLATFORM

MBUS-7-SVC_EOF_UNEXPECTED

7 PLATFORM

MBUS-7-SVC_EOF_UNEXPECTED

7 PLATFORM

MBUS-7-SVC_FILE_OPERATION_FAILED

7 PLATFORM

MBUS-7-SVC_FILE_OPERATION_FAILED

7 PLATFORM

MBUS-7-SVC_FILE_OPERATION_FAILED

7 PLATFORM

MBUS-7-SVC_INFO_DUMP

7 PLATFORM

MBUS-7-SVC_INFO_DUMP

7 PLATFORM

MBUS-7-SVC_INFO_DUMP

7 PLATFORM

MBUS-7-SVC_INVALID_STREAM

7 PLATFORM

MBUS-7-SVC_INVALID_STREAM

7 PLATFORM

MBUS-7-SVC_INVALID_STREAM

7 PLATFORM

MCE-2-L2CACHE_ERR

2 PLATFORM

MCU-3-NOT_IN_SYNC

3 PLATFORM

MCU-3-OLD_FPGA

3 PLATFORM

MDIO-7-OPERATION_FAIL

7 PLATFORM

MGID_ERROR-3-CHKPT_TRAN

3 PLATFORM

MGID_OOR-3-OOR_STATE_RED

3 PLATFORM

MGID_OOR-4-MGID_COUNT_OOR_ABOVE

4 PLATFORM

MGID_OOR-4-MGID_COUNT_OOR_GREEN

4 PLATFORM

MGID_OOR-4-MGID_COUNT_OOR_RED

4 PLATFORM

MGID_PROTECTED_FABRIC-4MGID_ACL_REMOVED

4 PLATFORM

MGID_PROTECTED_FABRIC-4MGID_MAX_HB_FLOWS

4 PLATFORM

MGID_PROTECTED_FABRIC-4MGID_RESYNC_END

4 PLATFORM

MGID_PROTECTED_FABRIC-4MGID_RESYNC_START

4 PLATFORM

MLAN-3-BUSY_FLAG

3 PLATFORM

MLAN-3-DRIVER_ERROR

3 PLATFORM

MLAN-3-DRIVER_ERROR_MSG

3 PLATFORM

MLAN-3-OPERATION_ERROR

3 PLATFORM

MLAN-3-RESET_FAILED

3 PLATFORM

MLAN-6-DRIVER_INFO

6 PLATFORM

MLAN-6-DRIVER_INFO_MSG

6 PLATFORM

MLAN-6-OPERATION_INFO

6 PLATFORM

MLAN-7-OPERATION_TRACE

7 PLATFORM

MLRMGR-5-GO_MLR_ROOT

5 PLATFORM

MLRMGR-6-RELOAD

6 PLATFORM

MPC8641-3-PCI_ERROR

3 PLATFORM

MPC8641-3-PCI_FATAL

3 PLATFORM

MPC8641-3-PCI_SW_ERR
MSM-3-ERR

3 PLATFORM
3 PLATFORM

NFEA_HW_PROG-5-MAX_LIMIT

5 PLATFORM

NFEA_HW_PROG-6-INFO_MSG

6 PLATFORM

NFEA_HW_PROG-6-INFO_MSG

6 PLATFORM

NFEA_HW_PROG-6-INFO_MSG

6 PLATFORM

NFEA_HW_PROG-7-ERR_MSG

7 PLATFORM

NFEA_HW_PROG-7-ERR_MSG

7 PLATFORM

NFEA_HW_PROG-7-ERR_MSG

7 PLATFORM

NFEA_PAL-1-FLOWEXP_LIMIT

1 PLATFORM

NIRVANA-2-S8_POWER_FAIL

2 PLATFORM

NP-0-HW_DOUBLE_ECC_ERROR

--

PLATFORM

NP-0-INIT_ERR

--

PLATFORM

NP-0-LC_RELOAD

--

PLATFORM

NP-0-NON_RECOVERABLE_SOFT_ERROR

--

PLATFORM

NP-0-NP_INIT_FAILURE

--

PLATFORM

NP-0-NP_OOR_ERROR

--

PLATFORM

NP-0-PEX_PARITY

--

PLATFORM

NP-0-TCAM_EXCESSIVE_PARITY_ERRORS

--

PLATFORM

NP-0-TM_CLUSTER_PARITY

--

PLATFORM

NP-0-TM_CNTL_CLUSTER_PARITY

--

PLATFORM

NP-0-TMA_CLUSTER_PARITY

--

PLATFORM

NP-0-TMB_CLUSTER_PARITY

--

PLATFORM

NP-0-TMC_CLUSTER_PARITY

--

PLATFORM

NP-2-CENTRAL_CLUSTER_PARITY

2 PLATFORM

NP-2-FATAL_INT_CASE

2 PLATFORM

NP-2-HW_SINGLE_ECC_ERROR

2 PLATFORM

NP-2-MATRIX_CLUSTER_PARITY

2 PLATFORM

NP-2MEMORY_RESOURCE_PROFILE_UNKNOWN

2 PLATFORM

NP-2-NP_DIAG

2 PLATFORM

NP-2-PARSE_CLUSTER_PARITY

2 PLATFORM

NP-2-RESOLVE_CLUSTER_PARITY

2 PLATFORM

NP-2-ROLLBACK_FAIL

2 PLATFORM

NP-2-SEARCH_CLUSTER_PARITY

2 PLATFORM

NP-2-TCAM_FATAL_INT_CASE

2 PLATFORM

NP-2-TCAM_WRITE_PARITY_ERROR

2 PLATFORM

NP-3-BIQ_EMPTY

3 PLATFORM

NP-3-DIAG

3 PLATFORM

NP-3-ECC

3 PLATFORM

NP-3-EG_FBU_POOL_EMPTY

3 PLATFORM

NP-3-FBU3_LOW_RESOURCE

3 PLATFORM

NP-3-HOST_SLAVE_QUEUE_FULL

3 PLATFORM

NP-3-HOST_SLAVE_QUEUE_NOT_EMPTY

3 PLATFORM

NP-3-HW_OQ_FULL

3 PLATFORM

NP-3-HW_RX_RFD_EMPTY

3 PLATFORM

NP-3-HW_TFD_FULL

3 PLATFORM

NP-3-HW_TX_RFD_EMPTY

3 PLATFORM

NP-3-IF_OIR_FAILURE

3 PLATFORM

NP-3-ING_FBU_POOL_EMPTY

3 PLATFORM

NP-3-OOR

3 PLATFORM

NP-3-TMA_FULL

3 PLATFORM

NP-3-TMB_FULL

3 PLATFORM

NP-3-UNEXPECTED

3 PLATFORM

NP-4-CONFIG_INIT

4 PLATFORM

NP-4-CONFIG_WARNING

4 PLATFORM

NP-4-FAULT

4 PLATFORM

NP-4-PROFILE_INACTIVE

4 PLATFORM

NP-4-PROFILE_NOT_SUPPORT

4 PLATFORM

NP-5-FAST_RESET

5 PLATFORM

NPU-3-DETECTED_TX_PDMA_STALL

3 PLATFORM

NPU-6-NO_BUF_TO_REPLACE

6 PLATFORM

NPUXBAR_BRIDGE-0-CPP_ASYNC_FIFO_FULL --

PLATFORM

NPUXBAR_BRIDGE-0-CPP_ASYNC_FIFO_MBE --

PLATFORM

NPUXBAR_BRIDGE-0-CPP_LTH_FIFO_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-CPP_LTH_FIFO_MBE

--

PLATFORM

NPUXBAR_BRIDGE-0-CPP_PKT_F0_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-CPP_PKT_F0_MBE

--

PLATFORM

NPUXBAR_BRIDGE-0-CPP_PKT_F1_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-CPP_PKT_F1_MBE

--

PLATFORM

NPUXBAR_BRIDGE-0-CPP_PKT_F2_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-CPP_PKT_F2_MBE

--

PLATFORM

NPUXBAR_BRIDGE-0-CPP_PKT_F3_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-CPP_PKT_F3_MBE

--

PLATFORM

NPUXBAR_BRIDGE-0CPP_TO_DDR_FIFO_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-CPP_TO_DDR_PAR_ERR --

PLATFORM

NPUXBAR_BRIDGE-0CPU_ASYNC_FIFO_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-CPU_ASYNC_FIFO_MBE --

PLATFORM

NPUXBAR_BRIDGE-0-CPU_FIFO_PAR_ERR

--

PLATFORM

NPUXBAR_BRIDGE-0-CPU_LTH_FIFO_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-CPU_LTH_FIFO_MBE

--

PLATFORM

NPUXBAR_BRIDGE-0-CPU_PKT_F0_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-CPU_PKT_F0_MBE

--

PLATFORM

NPUXBAR_BRIDGE-0-CPU_PKT_F1_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-CPU_PKT_F1_MBE

--

PLATFORM

NPUXBAR_BRIDGE-0-CPU_PKT_F2_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-CPU_PKT_F2_MBE

--

PLATFORM

NPUXBAR_BRIDGE-0-CPU_PKT_F3_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-CPU_PKT_F3_MBE

--

PLATFORM

NPUXBAR_BRIDGE-0EBS_CPP_HP_FIFO_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0EBS_CPP_HP_TAIL_DROP

--

PLATFORM

NPUXBAR_BRIDGE-0EBS_CPP_LP_FIFO_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0EBS_CPP_LP_TAIL_DROP

--

PLATFORM

NPUXBAR_BRIDGE-0-EBS_RGMII_FIFO_FULL --

PLATFORM

NPUXBAR_BRIDGE-0-EBS_RGMII_PAR_ERR
NPUXBAR_BRIDGE-0-FATAL_ERROR

---

PLATFORM
PLATFORM

NPUXBAR_BRIDGE-0-NO_ACTIVE_RSP

--

PLATFORM

NPUXBAR_BRIDGE-0-PCIE_CORE_ERROR

--

PLATFORM

NPUXBAR_BRIDGE-0-PCIE_RESP_FIFO_MBE --

PLATFORM

NPUXBAR_BRIDGE-0-PCIE_TX_FIFO_MBE

--

PLATFORM

NPUXBAR_BRIDGE-0-PCIE_TXIF_FIFO_MBE

--

PLATFORM

NPUXBAR_BRIDGE-0-RDDR_FIFO0_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-RDDR_FIFO0_PAR_ERR --

PLATFORM

NPUXBAR_BRIDGE-0-RDDR_FIFO1_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-RDDR_FIFO1_PAR_ERR --

PLATFORM

NPUXBAR_BRIDGE-0RSPI_ALIGN_MISMATCH

--

PLATFORM

NPUXBAR_BRIDGE-0-RSPI_ALIGN_OVFL

--

PLATFORM

NPUXBAR_BRIDGE-0-TDDR_FIFO0_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-TDDR_FIFO0_PAR_ERR --

PLATFORM

NPUXBAR_BRIDGE-0-TDDR_FIFO1_FULL

--

PLATFORM

NPUXBAR_BRIDGE-0-TDDR_FIFO1_PAR_ERR --

PLATFORM

NPUXBAR_BRIDGE-0TSPI_ASYNC_FIFO_OVFL

PLATFORM

--

NPUXBAR_BRIDGE-1-CPP_PKT_DIP4_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-CPP_PKT_PROT_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-CPU_PKT_CRC_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-CPU_PKT_LTH_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-EBS_CPP_DATA_MBE

1 PLATFORM

NPUXBAR_BRIDGE-1EBS_CPP_HP_FIFO_MBE

1 PLATFORM

NPUXBAR_BRIDGE-1-EBS_CPP_LP_FIFO_MBE

1 PLATFORM

NPUXBAR_BRIDGE-1-EBS_CPU_DATA_MBE

1 PLATFORM

NPUXBAR_BRIDGE-1-EBS_CPU_FIFO_MBE

1 PLATFORM

NPUXBAR_BRIDGE-1EBS_CPU_LP_FIFO_FULL

1 PLATFORM

NPUXBAR_BRIDGE-1-EBS_OC_CRC_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-EBS_OC_DELM_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1EBS_OC_HDR_CRC_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-EBS_OC_HDR_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-LBUS_PARITY_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-LBUS_READ_TIMEOUT

1 PLATFORM

NPUXBAR_BRIDGE-1-LBUS_WRITE_TIMEOUT

1 PLATFORM

NPUXBAR_BRIDGE-1PCIE_BAD_WRITE_ADDR
NPUXBAR_BRIDGE-1-RSP0_PAR_ERR

1 PLATFORM
1 PLATFORM

NPUXBAR_BRIDGE-1-RSP1_PAR_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-RSPI_CAL_ECC_MBE
NPUXBAR_BRIDGE-1-RSPI_DIP4_ERR

1 PLATFORM
1 PLATFORM

NPUXBAR_BRIDGE-1-RSPI_OUTOF_FRAME

1 PLATFORM

NPUXBAR_BRIDGE-1-RSPI_PHY_LOSS_SYNC

1 PLATFORM

NPUXBAR_BRIDGE-1RSPI_PROT_BURST_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-RSPI_PROT_GAP_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-RSPI_PROT_SEQ_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1RSPI_RPOT_RSVD_CTR_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-TSP_A_PKT_CRC_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1TSP_A_PKT_FRAME_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-TSP_A_PKT_LTH_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-TSP_B_PKT_CRC_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1TSP_B_PKT_FRAME_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-TSP_B_PKT_LTH_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1TSPI_ASYNC_FIFO_H72_MBE

1 PLATFORM

NPUXBAR_BRIDGE-1TSPI_ASYNC_FIFO_L72_MBE

1 PLATFORM

NPUXBAR_BRIDGE-1-TSPI_BUS_FRAME_ERR

1 PLATFORM

NPUXBAR_BRIDGE-1-TSPI_CAL_ECC_MBE
NPUXBAR_BRIDGE-1-TSPI_DIP2_ERR

1 PLATFORM
1 PLATFORM

NPUXBAR_BRIDGE-1-TSPI_OUTOF_FRAME

1 PLATFORM

NPUXBAR_BRIDGE-2-CPP_ASYNC_FIFO_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-CPP_LTH_FIFO_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-CPP_PKT_F0_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-CPP_PKT_F1_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-CPP_PKT_F2_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-CPP_PKT_F3_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-CPP_PKT_TOO_LONG

2 PLATFORM

NPUXBAR_BRIDGE-2-CPP_PKT_TOO_SHORT

2 PLATFORM

NPUXBAR_BRIDGE-2-CPU_ASYNC_FIFO_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-CPU_LTH_FIFO_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-CPU_PKT_F0_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-CPU_PKT_F1_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-CPU_PKT_F2_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-CPU_PKT_F3_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-CPU_PKT_TOO_LONG

2 PLATFORM

NPUXBAR_BRIDGE-2-CPU_PKT_TOO_SHORT
NPUXBAR_BRIDGE-2-CRIT_ERROR

2 PLATFORM
2 PLATFORM

NPUXBAR_BRIDGE-2-EBS_CPP_DATA_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-EBS_CPP_HP_FIFO_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-EBS_CPP_LP_FIFO_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-EBS_CPU_DATA_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-EBS_CPU_FIFO_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2EBS_CPU_HP_TAIL_DROP

2 PLATFORM

NPUXBAR_BRIDGE-2-EBS_OC_PKT_LTH_ERR

2 PLATFORM

NPUXBAR_BRIDGE-2EBS_OC_PKT_TOO_LONG

2 PLATFORM

NPUXBAR_BRIDGE-2EBS_OC_PKT_TOO_SHORT

2 PLATFORM

NPUXBAR_BRIDGE-2PCIE_BAD_READ_ADDR

2 PLATFORM

NPUXBAR_BRIDGE-2-PCIE_RESP_FIFO_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-PCIE_TX_FIFO_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-PCIE_TXIF_FIFO_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-RSPI_CAL_ECC_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2TSPI_ASYNC_FIFO_H72_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2TSPI_ASYNC_FIFO_L72_SBE

2 PLATFORM

NPUXBAR_BRIDGE-2-TSPI_CAL_ECC_SBE

2 PLATFORM

NPUXBAR_BRIDGE-3EBS_CPU_LP_TAIL_DROP
NPUXBAR_BRIDGE-3-ERROR

3 PLATFORM
3 PLATFORM

NPUXBAR_BRIDGE-3-RSPI_PROT_CTR_ERR

3 PLATFORM

NPUXBAR_BRIDGE-3RSPI_PROT_EOP_ABORT

3 PLATFORM

NPUXBAR_BRIDGE-3TSP_A_PKT_DECODE_DIS

3 PLATFORM

NPUXBAR_BRIDGE-3-TSP_A_PWM_ERR

3 PLATFORM

NPUXBAR_BRIDGE-3TSP_B_PKT_DECODE_DIS

3 PLATFORM

NPUXBAR_BRIDGE-3-TSP_B_PWM_ERR

3 PLATFORM

NPUXBAR_BRIDGE-3-TSP_GST_TIMEOUT

3 PLATFORM

NPUXBAR_BRIDGE-3-TSP_GST_TIMER_JUMP

3 PLATFORM

NPUXBAR_BRIDGE-3-TSP_TDDR_TIMEOUT

3 PLATFORM

NPUXBAR_BRIDGE-3TSP_TDDR_TIMER_JUMP

3 PLATFORM

NVEDGE_DATA-1-SHM_CORRUPT

1 PLATFORM

NVEDGE_DATA-3-ERROR_DISABLE

3 PLATFORM

NVEDGE_DATA-3-IRL_MAXSLOT_LIMIT

3 PLATFORM

NVEDGE_DATA-6-IRL_1SLOT

6 PLATFORM

NVEDGE_DATA-6-IRL_MAXSLOT

6 PLATFORM

NVEDGE_DATA-6-ONE_IRL

6 PLATFORM

OBFL_PD-3-ERROR

3 PLATFORM

OBFL_PD-3-FORMAT_DEVICE

3 PLATFORM

OBFL_PD-6-INFO

6 PLATFORM

OBFL-3-ERR_CREATE

3 PLATFORM

obfl-7-ERR_EVM_CREATE
obfl-7-ERR_INTERNAL
obfl-7-ERR_MALLOC

7 PLATFORM
7 PLATFORM
7 PLATFORM

obfl-7-ERR_SYSDB_REG_NOTIF

7 PLATFORM

obfl-7-ERR_THREAD_CREATE

7 PLATFORM

obfl-7-ERROR
obfl-7-TRACE_INTERNAL

7 PLATFORM
7 PLATFORM

OIRD-5-OIRIN

5 PLATFORM

OIRD-5-OIROUT

5 PLATFORM

OIRD-7-ASYNC_ATTACH_FAIL

7 PLATFORM

OIRD-7-ASYNC_MSG_ERROR

7 PLATFORM

OIRD-7-CHKPT_FAIL

7 PLATFORM

OIRD-7-EVM_CREATE_FAIL

7 PLATFORM

OIRD-7-MMAP_FAIL

7 PLATFORM

OIRD-7-MSG_ATTACH_FAIL

7 PLATFORM

OIRD-7-MSG_CHAN_CONN_FAIL

7 PLATFORM

OIRD-7-MSG_ERROR

7 PLATFORM

OIRD-7-THREAD_CREATE_FAIL

7 PLATFORM

OIRD-7-TIMER_CREATE_FAIL

7 PLATFORM

OIRD-7-TIMER_INIT_FAIL

7 PLATFORM

OIRD-7-UNEXPECTED

7 PLATFORM

P40X0_DPAA-3-ERROR

3 PLATFORM

P40X0_DPAA-3-ERROR_INIT

3 PLATFORM

P40X0_DPAA-4-WARNING

4 PLATFORM

PANINI_FWDLIB-7-ERR_INIT

7 PLATFORM

PANINI_SPP-3-ERR_INIT

3 PLATFORM

PANINI_SPP-3-ERR_MEM_ALLOC

3 PLATFORM

PANINI_SPP-3-ERR_THREAD

3 PLATFORM

PANINI_SPP-5-PAK_EVT

5 PLATFORM

PBR_EA_OOR-4-NP_FLOWS_OOR_GREEN

4 PLATFORM

PBR_EA_OOR-4-NP_FLOWS_OOR_RED

4 PLATFORM

PBR_EA_VERIFY-6-POLICY_ERROR

6 PLATFORM

PCIE_CLIENT-3-TRACE_BUFFER_INIT_ERROR

3 PLATFORM

PCIE_HAL-3-DOUBLE_FAULT

3 PLATFORM

PCIE_SWITCH-3-ERROR

3 PLATFORM

PCIE_SWITCH-3-ERROR

3 PLATFORM

PCIE-2-BUS_CRITICAL

2 PLATFORM

PCIE-2-BUS_CRITICAL

2 PLATFORM

PCIE-2BUS_CRITICAL_THRESHOLD_EXCEEDED

2 PLATFORM

PCIE-2BUS_CRITICAL_THRESHOLD_EXCEEDED

2 PLATFORM

PCIE-2-DEVICE_FAULT

2 PLATFORM

PCIE-2-GEN_CRIT

2 PLATFORM

PCIE-2-INIT_ERROR

2 PLATFORM

PCIE-2-PCI_BUS_CRITICAL

2 PLATFORM

PCIE-2-PCI_BUS_CRITICAL

2 PLATFORM

PCIE-2PCI_BUS_CRITICAL_THRESHOLD_EXCEEDED

2 PLATFORM

PCIE-2PCI_BUS_CRITICAL_THRESHOLD_EXCEEDED

2 PLATFORM

PCIE-2-PCIE_FC_ENUM_ERR

2 PLATFORM

PCIE-2-ROOT_DEVICE_BUS_CRITICAL

2 PLATFORM

PCIE-2ROOT_DEVICE_BUS_CRITICAL_THRESHOLD_
EXCEEDED

2 PLATFORM

PCIE-3-BUS_ERROR

3 PLATFORM

PCIE-3-BUS_ERROR

3 PLATFORM

PCIE-3BUS_ERROR_THRESHOLD_EXCEEDED

3 PLATFORM

PCIE-3BUS_ERROR_THRESHOLD_EXCEEDED

3 PLATFORM

PCIE-3-BUS_UNKNOWN_ERROR

3 PLATFORM

PCIE-3-BUS_UNKNOWN_ERROR

3 PLATFORM

PCIE-3-DEVICE_ERROR

3 PLATFORM

PCIE-3-ERROR

3 PLATFORM

PCIE-3-ERROR

3 PLATFORM

PCIE-3-GEN_ERR

3 PLATFORM

PCIE-3-LINK_RESET_ERROR

3 PLATFORM

PCIE-3-PCI_BUS_ERROR

3 PLATFORM

PCIE-3-PCI_BUS_ERROR

3 PLATFORM

PCIE-3PCI_BUS_ERROR_THRESHOLD_EXCEEDED

3 PLATFORM

PCIE-3PCI_BUS_ERROR_THRESHOLD_EXCEEDED

3 PLATFORM

PCIE-3-ROOT_DEVICE_BUS_ERROR

3 PLATFORM

PCIE-3ROOT_DEVICE_BUS_ERROR_THRESHOLD_E
XCEEDED

3 PLATFORM

PCIE-4-BUS_WARNING

4 PLATFORM

PCIE-4-BUS_WARNING

4 PLATFORM

PCIE-4BUS_WARNING_THRESHOLD_EXCEEDED

4 PLATFORM

PCIE-4BUS_WARNING_THRESHOLD_EXCEEDED

4 PLATFORM

PCIE-4-PCI_BUS_WARNING

4 PLATFORM

PCIE-4-PCI_BUS_WARNING

4 PLATFORM

PCIE-4PCI_BUS_WARNING_THRESHOLD_EXCEEDE
D

4 PLATFORM

PCIE-4PCI_BUS_WARNING_THRESHOLD_EXCEEDE
D

4 PLATFORM

PCIE-4-ROOT_DEVICE_BUS_WARNING

4 PLATFORM

PCIE-4ROOT_DEVICE_BUS_WARNING_THRESHOLD
_EXCEEDED

4 PLATFORM

PCIE-6-BUS_INFO

6 PLATFORM

PCIE-6-BUS_INFO

6 PLATFORM

PCIE-6-BUS_INFO_THRESHOLD_EXCEEDED

6 PLATFORM

PCIE-6-BUS_INFO_THRESHOLD_EXCEEDED

6 PLATFORM

PCIE-6-LINK_RESET

6 PLATFORM

PCIE-6-PCI_BUS_INFO

6 PLATFORM

PCIE-6-PCI_BUS_INFO

6 PLATFORM

PCIE-6PCI_BUS_INFO_THRESHOLD_EXCEEDED

6 PLATFORM

PCIE-6PCI_BUS_INFO_THRESHOLD_EXCEEDED

6 PLATFORM

PCIE-6-ROOT_DEVICE_BUS_INFO

6 PLATFORM

PCIE-6ROOT_DEVICE_BUS_INFO_THRESHOLD_EXC
EEDED

6 PLATFORM

PCIE-7-DEVICE_INFO

7 PLATFORM

PCIE-7-GEN_DEBUG

7 PLATFORM

PCIE-7-INIT_INFO

7 PLATFORM

PCIER-2-PCIE_1_ROOT_ERROR

2 PLATFORM

PCIER-2-PCIE_2_ROOT_ERROR

2 PLATFORM

PCIER-2-PCIE_FC_ENUM_ERR

2 PLATFORM

PCIMGR-2-SW_FATAL_ERROR

2 PLATFORM

PCIMGR-3-MUTEX_LOCK_ERROR

3 PLATFORM

PCIMGR-3-MUTEX_LOCK_ERROR

3 PLATFORM

PCIMGR-3-MUTEX_UNLOCK_ERROR

3 PLATFORM

PCIMGR-3-MUTEX_UNLOCK_ERROR

3 PLATFORM

PCIMGR-3-REG_PM_ERROR

3 PLATFORM

PCIMGR-3-REG_PM_ERROR

3 PLATFORM

PCIMGR-7-DEBUG_INFO

7 PLATFORM

PCIMGR-7-DEBUG_INFO_STAT

7 PLATFORM

PCIMGR-7-DEBUG_STAT

7 PLATFORM

PCIMGR-7-DEBUG_STAT_HEX

7 PLATFORM

PCIMGR-7-INFO

7 PLATFORM

PCIMGR-7-STAT

7 PLATFORM

PCIMGR-7-STAT_INFO

7 PLATFORM

PCIMGR-7-STAT_INFO_HEX

7 PLATFORM

PCIMGR-7-STAT_INFO_VOID

7 PLATFORM

PCIMGR-7-VERBOSE

7 PLATFORM

PCIMGR-7-VERBOSE_GENERAL

7 PLATFORM

PCIMGR-7-VERBOSE_INFO

7 PLATFORM

PCIMGR-7-VERBOSE_INFO_STAT

7 PLATFORM

PCIMGR-7-VERBOSE_INT_HEX

7 PLATFORM

PCIMGR-7-VERBOSE_STAT

7 PLATFORM

PCIMGR-7-VERBOSE_STR

7 PLATFORM

PCIMGR-7-VERBOSE_STR_HEX

7 PLATFORM

PCIMGR-7-VERBOSE_STR_STR

7 PLATFORM

PCMCIA-2-HBA_FAIL

2 PLATFORM

PCMCIA-3-PCI_DEV_ATTACH_FAIL

3 PLATFORM

PCMCIA-3-PCI_SVR_ATTACH_FAIL

3 PLATFORM

PCMCIA-7-MEM_MAP_FAIL

7 PLATFORM

PCMCIA-7-REG_PM_FAIL

7 PLATFORM

PCMCIAD-3-CARDMGR_START_FAILED

3 PLATFORM

PCMCIAD-3-START_FAILED

3 PLATFORM

PCMCIAD-4-SIGNAL_OP_FAILED

4 PLATFORM

PCMCIAD-7-KILL_FAILED

7 PLATFORM

PCMCIAD-7-MSGSEND_FAILED

7 PLATFORM

PCMCIAD-7-RESTART

7 PLATFORM

PCMCIAD-7-UNLINK_FAILED

7 PLATFORM

PCTL-3-GSP_MSG_FAILED

3 PLATFORM

PCTL-3-gsp_msg_failed

3 PLATFORM

PDMA_SPP-3-ERR_INIT

3 PLATFORM

PDMA_SPP-3-ERR_MEM_ALLOC

3 PLATFORM

PDMA_SPP-3-ERR_PKT_OVERSIZED

3 PLATFORM

PDMA_SPP-3-ERR_THREAD

3 PLATFORM

PDMA_SPP-3-PKT_DROPPED

3 PLATFORM

PDMA_SPP-3-THREAD_EVENT_BLOCK_FAIL

3 PLATFORM

PEX-2-CONFIG_FAIL

2 PLATFORM

PEX-2-ENTER_EVENT_LOOP_FAIL

2 PLATFORM

PEX-2-INIT_ERROR

2 PLATFORM

PEX-2-VER_TRANSLATE_FAIL

2 PLATFORM

PEX-3-ERROR

3 PLATFORM

PEX-3-LINK_ERROR

3 PLATFORM

PEX8111-2-DEVICE_INTERNAL_ERROR

2 PLATFORM

PEX8111-2-TRANSACTION_TIMEOUT

2 PLATFORM

PEX8111-2-UNSUPPORTED_REQUEST

2 PLATFORM

PEX8111-3-EXIT_INIT

3 PLATFORM

PEX8111-3-INTR_MASKED

3 PLATFORM

PEX8111-3-WARN_INIT

3 PLATFORM

PEX8508-2-BIST_FAIL

2 PLATFORM

PEX8508-2-HW_STRAP_ERROR

2 PLATFORM

PEX8508-2-LINK_TRAIN_FAIL

2 PLATFORM

PEX8508-2-UNCORR_ECC_ERROR

2 PLATFORM

PEX8508-3-CORR_ECC_ERROR

3 PLATFORM

PEX8508-3-EXIT_INIT

3 PLATFORM

PEX8508-3-INTR_MASKED

3 PLATFORM

PEX8508-3-WARN_INIT

3 PLATFORM

PEXMGR-1-EXIT_INIT

1 PLATFORM

PEXMGR-2-BIST_FAIL

2 PLATFORM

PEXMGR-2-HW_STRAP_ERROR

2 PLATFORM

PEXMGR-2-LINK_TRAIN_FAIL

2 PLATFORM

PEXMGR-2-UNCORR_ECC_ERROR

2 PLATFORM

PEXMGR-2-WARN_INIT

2 PLATFORM

PEXMGR-3-CORR_ECC_ERROR

3 PLATFORM

PEXMGR-3-INTR_MASKED

3 PLATFORM

PEXRC-1-EXIT_INIT

1 PLATFORM

PEXRC-2-WARN_INIT

2 PLATFORM

PFM-0-CARD_RESET_ABORTED

--

PLATFORM

PFM-0-CARD_RESET_REQ

--

PLATFORM

PFM-0GRACEFUL_CARD_RESET_TIMED_OUT

--

PLATFORM

PFM-2-LIB_LC_RESET

2 PLATFORM

PFM-3-APPL_COND_RESYNC_MISMATCH

3 PLATFORM

PFM-3-APPL_DEV_RESYNC_MISMATCH

3 PLATFORM

PFM-3-APPL_RESYNC_MISMATCH

3 PLATFORM

PFM-3-CARD_RESET_NOT_ALLOWED

3 PLATFORM

PFM-3-CHIP_RESET_NOT_ALLOWED

3 PLATFORM

PFM-3-CHIP_RESET_NOT_SUPPORTED

3 PLATFORM

PFM-3-DB_INT_ERR

3 PLATFORM

PFM-3-INV_FAULT_SEVERITY

3 PLATFORM

PFM-3-LIB_INT_ERR

3 PLATFORM

PFM-3-LIB_NOMEM_ERR

3 PLATFORM

PFM-3-LIB_SENT_FAIL

3 PLATFORM

PFM-3-NFM_INT_ERR

3 PLATFORM

PFM-3-NODE_INT_ERR

3 PLATFORM

PFM-3-NODE_INT_SLOW_REP_ERR

3 PLATFORM

PFM-3-SYSDB_INIT_FAILED

3 PLATFORM

PFM-3-UNK_RECOVERY_ACTION

3 PLATFORM

PFM-6-FAULT_SUPPRESSED_EVT_INFO

6 PLATFORM

PFM-6-NODE_INFO

6 PLATFORM

PLAT_BMADJ-3-ERR_INFO

3 PLATFORM

PLAT_BMADJ-3-ERR_INFO_RT

3 PLATFORM

PLAT_BMADJ-3-ERR_STR

3 PLATFORM

PLAT_BMADJ-3-ERR_STR_RT

3 PLATFORM

PLAT_BMADJ-3-ERROR

3 PLATFORM

PLAT_BMADJ-3-ERROR_RT

3 PLATFORM

PLAT_BMADJ-6-INFO

6 PLATFORM

PLAT_BMADJ-6-INFO_STR

6 PLATFORM

PLAT_DISC-3DU_CREATE_HW_INFO_TYPE_NODE_FAIL

3 PLATFORM

PLAT_DISC-3DU_SYSDB_HW_TREE_BIND_FAIL

3 PLATFORM

PLAT_DISC-3DU_SYSDB_HW_TREE_UNBIND_FAIL

3 PLATFORM

PLAT_DISC-3-PACKET_REGION_DEFINE_FAIL

3 PLATFORM

PLAT_DISC-3-PACKET_SEND_INIT_INFO_FAIL

3 PLATFORM

PLAT_DISC-3PARTICLE_BIG_POOL_DEFINE_FAIL

3 PLATFORM

PLAT_DISC-3PARTICLE_GIANT_POOL_DEFINE_FAIL

3 PLATFORM

PLAT_DISC-3PARTICLE_HUGE_POOL_DEFINE_FAIL

3 PLATFORM

PLAT_DISC-3PARTICLE_LARGE_POOL_DEFINE_FAIL

3 PLATFORM

PLAT_DISC-3PARTICLE_MEDIUM_POOL_DEFINE_FAIL

3 PLATFORM

PLAT_DISC-3PARTICLE_QNET_POOL_DEFINE_FAIL

3 PLATFORM

PLAT_DISC-3PARTICLE_SMALL_POOL_DEFINE_FAIL

3 PLATFORM

PLAT_DISC-3PARTICLE_TINY_POOL_DEFINE_FAIL

3 PLATFORM

PLAT_DISC-3PLATFORM_GET_HW_BOARD_TYPE_FAIL

3 PLATFORM

PLAT_DISC-3PLATFORM_GET_RESERVED_PHYSMEM_FAIL

3 PLATFORM

PLAT_DISC-3-SHOW_VER_INFO_INIT

3 PLATFORM

PLAT_DISC-6-PAK_MEM_INFO

6 PLATFORM

PLAT_FIB_EA-3-ERR_INFO

3 PLATFORM

PLAT_FIB_EA-3-ERR_STR

3 PLATFORM

PLAT_FIB_EA-3-ERROR

3 PLATFORM

PLAT_FIB_EA-3-INIT_FAILURE

3 PLATFORM

PLAT_FIB_EA-3-INVALID_OBJECT

3 PLATFORM

PLAT_FIB_EA-3-MEMORY_FAILURE

3 PLATFORM

PLAT_FIB_EA-3-PROGRAM_FAILURE

3 PLATFORM

PLAT_FIB_EA-6-INFO

6 PLATFORM

PLAT_FIB_EA-6-PRINT_INFO

6 PLATFORM

PLAT_FIB_ECD-3-ERR_INFO

3 PLATFORM

PLAT_FIB_ECD-3-ERR_STR

3 PLATFORM

PLAT_FIB_ECD-3-ERROR

3 PLATFORM

PLAT_FIB_ECD-6-INFO

6 PLATFORM

PLAT_FIB_ECD-6-INFO_STR

6 PLATFORM

PLAT_FIB_GTRIE-3-ERR_INFO

3 PLATFORM

PLAT_FIB_GTRIE-3-ERR_INFO

3 PLATFORM

PLAT_FIB_GTRIE-3-ERR_INFO_RT

3 PLATFORM

PLAT_FIB_GTRIE-3-ERR_STR

3 PLATFORM

PLAT_FIB_GTRIE-3-ERR_STR

3 PLATFORM

PLAT_FIB_GTRIE-3-ERR_STR_RT

3 PLATFORM

PLAT_FIB_GTRIE-3-ERROR

3 PLATFORM

PLAT_FIB_GTRIE-3-ERROR

3 PLATFORM

PLAT_FIB_GTRIE-3-ERROR_RT

3 PLATFORM

PLAT_FIB_GTRIE-6-FRR_INFO

6 PLATFORM

PLAT_FIB_GTRIE-6-INFO

6 PLATFORM

PLAT_FIB_GTRIE-6-INFO

6 PLATFORM

PLAT_FIB_HAL-3-ERR_DETAIL

3 PLATFORM

PLAT_FIB_HAL-3-ERR_INFO

3 PLATFORM

PLAT_FIB_HAL-3-ERR_INFO

3 PLATFORM

PLAT_FIB_HAL-3-ERR_INFO_HEX

3 PLATFORM

PLAT_FIB_HAL-3-ERR_INFO_NOT_SUP

3 PLATFORM

PLAT_FIB_HAL-3-ERR_INFO_RT

3 PLATFORM

PLAT_FIB_HAL-3-ERR_INFO_RT

3 PLATFORM

PLAT_FIB_HAL-3-ERR_STR

3 PLATFORM

PLAT_FIB_HAL-3-ERR_STR

3 PLATFORM

PLAT_FIB_HAL-3-ERR_STR_RT

3 PLATFORM

PLAT_FIB_HAL-3-ERR_STR_RT

3 PLATFORM

PLAT_FIB_HAL-3-ERROR

3 PLATFORM

PLAT_FIB_HAL-3-ERROR

3 PLATFORM

PLAT_FIB_HAL-3-ERROR_RT

3 PLATFORM

PLAT_FIB_HAL-3-ERROR_RT

3 PLATFORM

PLAT_FIB_HAL-6-INFO

6 PLATFORM

PLAT_FIB_HAL-6-INFO
PLAT_FIB_MPLS-2-CRITICAL

6 PLATFORM
2 PLATFORM

PLAT_FIB_MPLS-2-CRITICAL_INFO

2 PLATFORM

PLAT_FIB_MPLS-3-ACCESS_FAILURE

3 PLATFORM

PLAT_FIB_MPLS-3-ACCESS_FAILURE_STR

3 PLATFORM

PLAT_FIB_MPLS-3-ACTION_FAILURE

3 PLATFORM

PLAT_FIB_MPLS-3-ACTION_FAILURE_DETAIL

3 PLATFORM

PLAT_FIB_MPLS-3-ACTION_FAILURE_STR

3 PLATFORM

PLAT_FIB_MPLS-3-ERR_DETAIL

3 PLATFORM

PLAT_FIB_MPLS-3-ERR_DETAIL

3 PLATFORM

PLAT_FIB_MPLS-3-ERR_INFO

3 PLATFORM

PLAT_FIB_MPLS-3-ERR_INFO
PLAT_FIB_MPLS-3-ERR_INFO

3 PLATFORM
3 PLATFORM

PLAT_FIB_MPLS-3-ERR_INFO

3 PLATFORM

PLAT_FIB_MPLS-3-ERR_INFO_HEX

3 PLATFORM

PLAT_FIB_MPLS-3-ERR_INFO_HEX

3 PLATFORM

PLAT_FIB_MPLS-3-ERR_INFO_STR

3 PLATFORM

PLAT_FIB_MPLS-3-ERR_INIT

3 PLATFORM

PLAT_FIB_MPLS-3-ERR_INIT_STR

3 PLATFORM

PLAT_FIB_MPLS-3-ERR_MEM

3 PLATFORM

PLAT_FIB_MPLS-3-ERR_MEM_STR

3 PLATFORM

PLAT_FIB_MPLS-3-ERR_STR
PLAT_FIB_MPLS-3-ERR_STR

3 PLATFORM
3 PLATFORM

PLAT_FIB_MPLS-3-ERR_STR

3 PLATFORM

PLAT_FIB_MPLS-3-ERROR
PLAT_FIB_MPLS-3-ERROR

3 PLATFORM
3 PLATFORM

PLAT_FIB_MPLS-3-ERROR

3 PLATFORM

PLAT_FIB_MPLS-3-ERROR

3 PLATFORM

PLAT_FIB_MPLS-3-INIT_FAILURE

3 PLATFORM

PLAT_FIB_MPLS-3-INIT_FAILURE_STR

3 PLATFORM

PLAT_FIB_MPLS-3-INVALID_ACTION

3 PLATFORM

PLAT_FIB_MPLS-3-INVALID_OBJECT

3 PLATFORM

PLAT_FIB_MPLS-3-INVALID_OBJECT_STR

3 PLATFORM

PLAT_FIB_MPLS-3-INVALID_RANGE

3 PLATFORM

PLAT_FIB_MPLS-3-SHMEM
PLAT_FIB_MPLS-4-WARNING
PLAT_FIB_MPLS-4-WARNING_INFO
PLAT_FIB_MPLS-6-INFO

3 PLATFORM
4 PLATFORM
4 PLATFORM
6 PLATFORM

PLAT_FIB_RP-3-ERR_INFO

3 PLATFORM

PLAT_FIB_RP-3-ERR_INFO

3 PLATFORM

PLAT_FIB_RP-3-ERR_INFO_VERBOSE

3 PLATFORM

PLAT_FIB_RP-3-ERR_INFO_VERBOSE
PLAT_FIB_RP-3-ERROR
PLAT_FIB_RP-3-ERROR

3 PLATFORM
3 PLATFORM
3 PLATFORM

PLAT_FIB-1-HFR_FIB_OOR_LIMIT_EXCEEDED

1 PLATFORM

PLAT_FIB-2HFR_FIB_OOR_ROUTES_BLOCKED

2 PLATFORM

PLAT_FIB-2HFR_FIB_OOR_ROUTES_UNBLOCKED

2 PLATFORM

PLAT_FIB-3-CONNECT_FAILURE

3 PLATFORM

PLAT_FIB-3-CONNECTION_FAIL

3 PLATFORM

PLAT_FIB-3-ERR_INFO

3 PLATFORM

PLAT_FIB-3-ERR_INFO

3 PLATFORM

PLAT_FIB-3-ERR_INFO

3 PLATFORM

PLAT_FIB-3-ERR_INFO

3 PLATFORM

PLAT_FIB-3-ERR_INFO

3 PLATFORM

PLAT_FIB-3-ERR_INFO_INIT

3 PLATFORM

PLAT_FIB-3-ERR_INFO_NOT_SUPP

3 PLATFORM

PLAT_FIB-3-ERR_INFO_OPER

3 PLATFORM

PLAT_FIB-3-ERR_INFO_PRM

3 PLATFORM

PLAT_FIB-3-ERR_INFO_RT

3 PLATFORM

PLAT_FIB-3-ERR_INFO_RT

3 PLATFORM

PLAT_FIB-3-ERR_INFO_RT

3 PLATFORM

PLAT_FIB-3-ERR_INFO_RT

3 PLATFORM

PLAT_FIB-3-ERR_INFO_SHOW

3 PLATFORM

PLAT_FIB-3-ERR_STR

3 PLATFORM

PLAT_FIB-3-ERR_STR

3 PLATFORM

PLAT_FIB-3-ERR_STR

3 PLATFORM

PLAT_FIB-3-ERR_STR

3 PLATFORM

PLAT_FIB-3-ERR_STR

3 PLATFORM

PLAT_FIB-3-ERR_STR_INIT

3 PLATFORM

PLAT_FIB-3-ERR_STR_NEGO_FAIL

3 PLATFORM

PLAT_FIB-3-ERR_STR_RT

3 PLATFORM

PLAT_FIB-3-ERR_STR_RT

3 PLATFORM

PLAT_FIB-3-ERR_STR_RT

3 PLATFORM

PLAT_FIB-3-ERR_STR_RT

3 PLATFORM

PLAT_FIB-3-ERR_STR_RT_ACC

3 PLATFORM

PLAT_FIB-3-ERR_STR_RT_PRM

3 PLATFORM

PLAT_FIB-3-ERROR

3 PLATFORM

PLAT_FIB-3-ERROR

3 PLATFORM

PLAT_FIB-3-ERROR

3 PLATFORM

PLAT_FIB-3-ERROR

3 PLATFORM

PLAT_FIB-3-ERROR

3 PLATFORM

PLAT_FIB-3-ERROR

3 PLATFORM

PLAT_FIB-3-ERROR_HW_LIMIT_RT

3 PLATFORM

PLAT_FIB-3-ERROR_INFO

3 PLATFORM

PLAT_FIB-3-ERROR_INIT

3 PLATFORM

PLAT_FIB-3-ERROR_NOT_SUPP

3 PLATFORM

PLAT_FIB-3-ERROR_OPER

3 PLATFORM

PLAT_FIB-3-ERROR_RT

3 PLATFORM

PLAT_FIB-3-ERROR_RT

3 PLATFORM

PLAT_FIB-3-ERROR_RT

3 PLATFORM

PLAT_FIB-3-ERROR_RT

3 PLATFORM

PLAT_FIB-3-ERROR_RT_SHOW

3 PLATFORM

PLAT_FIB-3-ERROR_SHOW

3 PLATFORM

PLAT_FIB-3-INFO_RT

3 PLATFORM

PLAT_FIB-3-INIT_FAIL

3 PLATFORM

PLAT_FIB-3-INVALID_SIZE

3 PLATFORM

PLAT_FIB-3-MEMORY_FAILURE

3 PLATFORM

PLAT_FIB-3-MESSAGE_FAIL

3 PLATFORM

PLAT_FIB-3-OPERATION_FAIL

3 PLATFORM

PLAT_FIB-3-OPERATION_FAILURE

3 PLATFORM

PLAT_FIB-3-RT_FAIL

3 PLATFORM

PLAT_FIB-3-STR_NEGO_FAIL

3 PLATFORM

PLAT_FIB-3-STR_RT

3 PLATFORM

PLAT_FIB-3-SYSDB_DATALIST_FAIL

3 PLATFORM

PLAT_FIB-3-SYSDB_INIT_FAIL

3 PLATFORM

PLAT_FIB-3-WARNING

3 PLATFORM

PLAT_FIB-3-WARNING_INFO

3 PLATFORM

PLAT_FIB-3-WARNING_INFO_RT

3 PLATFORM

PLAT_FIB-3-WARNING_RT

3 PLATFORM

PLAT_FIB-3-WARNING_STR

3 PLATFORM

PLAT_FIB-3-WARNING_STR_RT

3 PLATFORM

PLAT_FIB-4-GRE_UNSUPPORTED

4 PLATFORM

PLAT_FIB-4-GRE_UNSUPPORTED

4 PLATFORM

PLAT_FIB-4-LFA_FRR_BKUP_INCOMPLETE

4 PLATFORM

PLAT_FIB-4-LFA_FRR_INVALID_BKUP

4 PLATFORM

PLAT_FIB-4-LFA_FRR_INVALID_CARD_TYPE

4 PLATFORM

PLAT_FIB-4-WARNING_RT

4 PLATFORM

PLAT_FIB-6-COMM_INFO

6 PLATFORM

PLAT_FIB-6-FRR_INFO

6 PLATFORM

PLAT_FIB-6-FRR_INFO

6 PLATFORM

PLAT_FIB-6-FRR_INFO

6 PLATFORM

PLAT_FIB-6-FRR_INFO

6 PLATFORM

PLAT_FIB-6-FRR_INFO

6 PLATFORM

PLAT_FIB-6-FRR_INFO

6 PLATFORM

PLAT_FIB-6-INFO

6 PLATFORM

PLAT_FIB-6-INFO

6 PLATFORM

PLAT_FIB-6-INFO

6 PLATFORM

PLAT_FIB-6-INFO

6 PLATFORM

PLAT_FIB-6-INFO

6 PLATFORM

PLAT_FIB-6-INFO

6 PLATFORM

PLAT_FIB-6-INFO

6 PLATFORM

PLAT_FIB-6-INFO

6 PLATFORM

PLAT_FIB-6-INFO_GL

6 PLATFORM

PLAT_FIB-6-INFO_SHOW

6 PLATFORM

PLAT_FIB-6-PRINT_INFO

6 PLATFORM

PLAT_FIB-6-VERSION_INFO

6 PLATFORM

PLAT_ICPE_EA_DEBUG-6-REGISTER_FAILED

6 PLATFORM

PLAT_ICPE_EA_DEBUG-6-REGISTER_FAILED

6 PLATFORM

PLAT_ICPE_EA_LTRACE-6ERR_INFO_VERBOSE

6 PLATFORM

PLAT_ICPE_EA_LTRACE-6ERR_INFO_VERBOSE

6 PLATFORM

PLAT_ICPE_EA-3-ICL_PROVISIONING_ERROR

3 PLATFORM

PLAT_ICPE_EA-3-ICL_PROVISIONING_ERROR

3 PLATFORM

PLAT_ICPE_EA-6-CERR_INFO

6 PLATFORM

PLAT_ICPE_EA-6-CERR_INFO

6 PLATFORM

PLAT_ICPE_EA-6-HW_INIT_INFO

6 PLATFORM

PLAT_ICPE_EA-6-HW_INIT_INFO

6 PLATFORM

PLAT_ICPE_EA-6ICL_ACCESS_PORT_SCALE_LIMIT

6 PLATFORM

PLAT_ICPE_EA-6LC_ACCESS_PORT_SCALE_LIMIT

6 PLATFORM

PLAT_ICPE_EA-6-LC_SAT_SCALE_LIMIT

6 PLATFORM

PLAT_ICPE_EA-6NP_ACCESS_PORT_SCALE_LIMIT

6 PLATFORM

PLAT_ICPE_EA-6-NP_SAT_SCALE_LIMIT

6 PLATFORM

PLAT_L2FIB_ATOM-6-DEBUG_INFO

6 PLATFORM

PLAT_L2FIB_ATOM-6-INIT_INFO

6 PLATFORM

PLAT_L2FIB_ATOM-6-LTRACE_INFO

6 PLATFORM

PLAT_L2FIB_ATOM-7-DEBUG_ERROR

7 PLATFORM

PLAT_L2FIB_ATOM-7-INIT_ERROR

7 PLATFORM

PLAT_L2FIB_ATOM-7-LTRACE_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7-BRIDGE_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7-DEBUG_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7ENQUEUE_MAC_COUNT_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7-HW_INIT_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7-INIT_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7INVALID_MAC_CHUNK_TYPE_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7INVALID_NEXT_MAC_OFFSET_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7INVALID_SET_MAC_OFFSET_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7-LTRACE_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7MAC_CHUNK_DB_OUTOFSYNC_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7MAC_COUNT_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7-PFI_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7REDUNDANT_MAC_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7SETTING_NONFREE_MAC_OFFSET_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7TCAM_CHUNK_MAX_MAC_LIMIT_ERROR

7 PLATFORM

PLAT_L2FIB_BRIDGING-7-TCAM_ERROR

7 PLATFORM

PLAT_L2FIB_COMMON-7-HW_INIT_ERROR

7 PLATFORM

PLAT_L2FIB_COMMON-7-TIMER_ERROR

7 PLATFORM

PLAT_L2FIB_DEBUG-6-REGISTER_FAILED

6 PLATFORM

PLAT_L2FIB_DEBUG-7-REGISTER_FAILED

7 PLATFORM

PLAT_L2FIB_L2TP-6-DEBUG_INFO

6 PLATFORM

PLAT_L2FIB_L2TP-6-INIT_INFO

6 PLATFORM

PLAT_L2FIB_L2TP-6-LTRACE_INFO

6 PLATFORM

PLAT_L2FIB_L2TP-7-DEBUG_ERROR

7 PLATFORM

PLAT_L2FIB_L2TP-7-INIT_ERROR

7 PLATFORM

PLAT_L2FIB_L2TP-7-LTRACE_ERROR

7 PLATFORM

PLAT_L2FIB_LOCSW-6-DEBUG_INFO

6 PLATFORM

PLAT_L2FIB_LOCSW-6-INIT_INFO

6 PLATFORM

PLAT_L2FIB_LOCSW-6-LTRACE_INFO

6 PLATFORM

PLAT_L2FIB_LOCSW-6-PFI_INFO

6 PLATFORM

PLAT_L2FIB_LOCSW-7-DEBUG_ERROR

7 PLATFORM

PLAT_L2FIB_LOCSW-7-INIT_ERROR

7 PLATFORM

PLAT_L2FIB_LOCSW-7-LTRACE_ERROR

7 PLATFORM

PLAT_L2FIB_LOCSW-7-PFI_ERROR

7 PLATFORM

PLAT_L2FIB_LTRACE-6-ERR_INFO_VERBOSE

6 PLATFORM

PLAT_L2FIB_LTRACE-7-ERR_INFO_VERBOSE

7 PLATFORM

PLAT_L2FIB_MAC_CACHE-6RESYNC_COMPLETE

6 PLATFORM

PLAT_L2FIB_MAC_CACHE-6RESYNC_COMPLETE

6 PLATFORM

PLAT_L2FIB_METRO-3-NULL_CONTEXT

3 PLATFORM

PLAT_L2FIB_METRO-3-QINQ_INIT_ERR

3 PLATFORM

PLAT_L2FIB_METRO-3QINQ_TCAM_WRITE_ERR

3 PLATFORM

PLAT_L2FIB_METRO-4-HW_INIT

4 PLATFORM

PLAT_L2FIB_POGO-3-NULL_CONTEXT

3 PLATFORM

PLAT_L2FIB_POGO-4-HW_INIT

4 PLATFORM

PLAT_L2FIB_RP_DEBUG-6-REGISTER_FAILED

6 PLATFORM

PLAT_L2FIB_RP_LTRACE-6ERR_INFO_VERBOSE

6 PLATFORM

PLAT_L2FIB_RP-3-BTREE_RESET_ERROR

3 PLATFORM

PLAT_L2FIB_RP-3-CERR_ERROR

3 PLATFORM

PLAT_L2FIB_RP-3-DEBUG_ERROR

3 PLATFORM

PLAT_L2FIB_RP-3-INIT_ERROR

3 PLATFORM

PLAT_L2FIB_RP-3-LTRACE_ERROR

3 PLATFORM

PLAT_L2FIB_RP-3-XID_COUNT_ERROR

3 PLATFORM

PLAT_L2FIB_RP-4-DEBUG_INIT

4 PLATFORM

PLAT_L2FIB_RP-4-HW_MAC_INCONSIST_CFG

4 PLATFORM

PLAT_L2FIB_RP-4-LTRACE_INIT

4 PLATFORM

PLAT_L2FIB_RP-6-EVENT_TIMEOUT

6 PLATFORM

PLAT_L2FIB_SNOOP-7-INIT_ERROR

7 PLATFORM

PLAT_L2FIB_VPLS-3PRM_ASYNC_REQ_FAILURE

3 PLATFORM

PLAT_L2FIB_VPLS-6-DEBUG_INFO

6 PLATFORM

PLAT_L2FIB_VPLS-6-IMC_INFO

6 PLATFORM

PLAT_L2FIB_VPLS-6-INIT_INFO

6 PLATFORM

PLAT_L2FIB_VPLS-6-LTRACE_INFO

6 PLATFORM

PLAT_L2FIB-3-ADDIF_ERR

3 PLATFORM

PLAT_L2FIB-3-ENTRY_EXISTS_ERR

3 PLATFORM

PLAT_L2FIB-3-ENTRY_NOT_EXIST_ERR

3 PLATFORM

PLAT_L2FIB-3-HW_RES_OVERFLOW

3 PLATFORM

PLAT_L2FIB-3-INIT_FAIL

3 PLATFORM

PLAT_L2FIB-3-NP_FAILURE

3 PLATFORM

PLAT_L2FIB-6-CERR_INFO

6 PLATFORM

PLAT_L2FIB-6-DEBUG_INFO

6 PLATFORM

PLAT_L2FIB-6-ENTRY_EXISTS_INFO

6 PLATFORM

PLAT_L2FIB-6-ENTRY_NOT_EXIST_INFO

6 PLATFORM

PLAT_L2FIB-6-HW_INIT_INFO

6 PLATFORM

PLAT_L2FIB-6-HW_INIT_INFO

6 PLATFORM

PLAT_L2FIB-6-INIT_INFO

6 PLATFORM

PLAT_L2FIB-6-LTRACE_INFO

6 PLATFORM

PLAT_L2FIB-7-CERR_ERROR

7 PLATFORM

PLAT_L2FIB-7-DEBUG_ERROR

7 PLATFORM

PLAT_L2FIB-7-HW_INIT_ERROR

7 PLATFORM

PLAT_L2FIB-7-LTRACE_ERROR

7 PLATFORM

PLAT_L2FIB-7-NHOP_ERROR

7 PLATFORM

PLAT_L2FIB-7-PFI_ERROR

7 PLATFORM

PLAT_L2VPN_DEBUG-7-REGISTER_FAILED

7 PLATFORM

PLAT_L2VPN_FGID-3-ALLOC_ERROR

3 PLATFORM

PLAT_L2VPN_FGID-3-INIT_ERROR

3 PLATFORM

PLAT_L2VPN_FGID-3-MEM_ERROR

3 PLATFORM

PLAT_L2VPN_FGID-3-REMARK_ERROR

3 PLATFORM

PLAT_L2VPN_FGID-3-TIMER_ERROR

3 PLATFORM

PLAT_L2VPN_FGID-4-DEBUG_INIT

4 PLATFORM

PLAT_L2VPN_FGID-4-LTRACE_INIT

4 PLATFORM

PLAT_L2VPN_FGID-6-INIT_INFO

6 PLATFORM

PLAT_L2VPN_FGID-6-LTRACE_INFO

6 PLATFORM

PLAT_L2VPN_FGID-6-TIMER_INFO

6 PLATFORM

PLAT_L2VPN_LTRACE-7-ERR_INFO_VERBOSE

7 PLATFORM

PLAT_L2VPN-3-RSI_ERROR

3 PLATFORM

PLAT_MCAST-3-ERR_INFO

3 PLATFORM

PLAT_MCAST-3-ERR_INFO_RT

3 PLATFORM

PLAT_MCAST-3-ERR_STR

3 PLATFORM

PLAT_MCAST-3-ERR_STR_RT

3 PLATFORM

PLAT_MCAST-3-ERROR

3 PLATFORM

PLAT_MCAST-3-ERROR_RT

3 PLATFORM

PLAT_MCAST-6-INFO

6 PLATFORM

PLAT_MCAST-6-OLE_INFO

6 PLATFORM

PLAT_NVSAT_EA_DEBUG-6REGISTER_FAILED

6 PLATFORM

PLAT_NVSAT_EA_LTRACE-6ERR_INFO_VERBOSE

6 PLATFORM

PLAT_NVSAT_EA-3ICL_PROVISIONING_ERROR

3 PLATFORM

PLAT_NVSAT_EA-6-CERR_INFO

6 PLATFORM

PLAT_NVSAT_EA-6-HW_INIT_INFO

6 PLATFORM

PLAT_THOR_L2FIB_ATOM-3DEBUG_WARNING

3 PLATFORM

PLAT_THOR_L2FIB_ATOM-3-INIT_WARNING

3 PLATFORM

PLAT_THOR_L2FIB_ATOM-3LTRACE_WARNING

3 PLATFORM

PLAT_THOR_L2FIB_DEBUG-3REGISTER_FAILED

3 PLATFORM

PLAT_THOR_L2FIB_LOCSW-7DEBUG_WARNING

7 PLATFORM

PLAT_THOR_L2FIB_LOCSW-7-INIT_WARNING

7 PLATFORM

PLAT_THOR_L2FIB_LOCSW-7LTRACE_WARNING

7 PLATFORM

PLAT_THOR_L2FIB_LOCSW-7-PFI_WARNING

7 PLATFORM

PLAT_THOR_L2FIB_LTRACE-3WARNING_INFO_VERBOSE

3 PLATFORM

PLAT_THOR_L2FIB_MLD-3-INIT_ERROR

3 PLATFORM

PLAT_THOR_L2FIB_VPLS-3-CERR_WARNING

3 PLATFORM

PLAT_THOR_L2FIB_VPLS-3DEBUG_WARNING

3 PLATFORM

PLAT_THOR_L2FIB_VPLS-3-INIT_WARNING

3 PLATFORM

PLAT_THOR_L2FIB_VPLS-3LTRACE_WARNING

3 PLATFORM

PLAT_THOR_L2FIB-3-CERR_WARNING

3 PLATFORM

PLAT_THOR_L2FIB-3-DEBUG_WARNING

3 PLATFORM

PLAT_THOR_L2FIB-3-HW_INIT_WARNING

3 PLATFORM

PLAT_THOR_L2FIB-3-LTRACE_WARNING

3 PLATFORM

PLAT_UDI_MGR-3-ERROR_EXIT
PLAT_V6FIB_RP-3-ERR_INFO
PLAT_V6FIB_RP-3-ERR_INFO

3 PLATFORM
3 PLATFORM
3 PLATFORM

PLAT_V6FIB_RP-3-ERR_INFO_VERBOSE

3 PLATFORM

PLAT_V6FIB_RP-3-ERR_INFO_VERBOSE_INIT
PLAT_V6FIB_RP-3-ERROR
PLAT_V6FIB_RP-3-ERROR

3 PLATFORM
3 PLATFORM
3 PLATFORM

PLATFORM_A9K_LC_SVI-2LOCAL_INTERFACE_FAILURE

2 PLATFORM

PLATFORM_A9K_LC_SVI-2VQI_ERROR_FAILED

2 PLATFORM

PLATFORM_A9K_LC_SVI-3UIDB_ERROR_FAILED

3 PLATFORM

PLATFORM_ASR9K_LIB-3FAILURE_TO_BIND_TO_SYSDB

3 PLATFORM

PLATFORM_ASR9K_LIB-3FAILURE_TO_CACHE_FILE

3 PLATFORM

PLATFORM_ASR9K_LIB-3FAILURE_TO_RETRIEVE

3 PLATFORM

PLATFORM_ASR9K_LIB-7-AM_I_SC_ERROR

7 PLATFORM

PLATFORM_ASR9K_NSR_PACKET-2CANT_READ_MAGIC

2 PLATFORM

PLATFORM_ASR9K_NSR_PACKET-2CANT_TRIM_CLSTR_NPH

2 PLATFORM

PLATFORM_ASR9K_NSR_PACKET-2ERR_TRIMMING_HDR_FROM_PACKET

2 PLATFORM

PLATFORM_ASR9K_NSR_PACKET-2NULL_HDR_AFTER_UNSCRAMBLE

2 PLATFORM

PLATFORM_ASR9K_NSR_PACKET-2SPP_ADD_L2_HDR_FAILED

2 PLATFORM

PLATFORM_ASR9K_NSR_PACKET-3ERROR_TRACE_INIT_FAILED

3 PLATFORM

PLATFORM_ASR9K_NSR_PACKET-3EVENT_TRACE_INIT_FAILED

3 PLATFORM

PLATFORM_ASR9K_SCH_LIB-2CONNECT_NODE_FAILED

2 PLATFORM

PLATFORM_ASR9K_SCH_LIB-2GET_NODEID_FAILED

2 PLATFORM

PLATFORM_ASR9K_SCH_LIB-3EVM_CREATE_FAIL

3 PLATFORM

PLATFORM_ASR9K_SCH_LIB-3EVM_MSG_ATTACH_FAIL

3 PLATFORM

PLATFORM_DRV-2ERR_PHY_RESERVE_START

2 PLATFORM

PLATFORM_DRV-3-ERR__MIB_SYS_OBJ

3 PLATFORM

PLATFORM_DRV-3-ERR__SHMEM_CREATE

3 PLATFORM

PLATFORM_DRV-3-ERR__VERSION_INFO

3 PLATFORM

PLATFORM_DRV-3-ERR_FUNC

3 PLATFORM

PLATFORM_DRV-3-ERR_PHY_MEM

3 PLATFORM

PLATFORM_DRV-6-MEM_SIZE

6 PLATFORM

PLATFORM_HFR_LIB-7ERR_GET_BOARD_TYPE

7 PLATFORM

PLATFORM_HFR_LIB-7ERR_GET_CARD_TYPE

7 PLATFORM

PLDMGR-0-NIRVANA_FATAL_EVENT

--

PLATFORM

PLDMGR-0-ZENJF_FATAL_EVENT

--

PLATFORM

PLDMGR-2-BOARD_RESTART

2 PLATFORM

PLDMGR-2-BOARD_RESTART

2 PLATFORM

PLDMGR-2-BOARD_RESTART

2 PLATFORM

PLDMGR-2-BOARD_RESTART

2 PLATFORM

PLDMGR-2-CLIENT_ERROR

2 PLATFORM

PLDMGR-2-FPD_EN_ERR

2 PLATFORM

PLDMGR-2-INTR_HDLR

2 PLATFORM

PLDMGR-2-LTRACE_BUF_INIT

2 PLATFORM

PLDMGR-2-LTRACE_DECODE_INIT

2 PLATFORM

PLDMGR-2-LTRACE_DECODE_INIT

2 PLATFORM

PLDMGR-3-DEV_LIB_INIT

3 PLATFORM

PLDMGR-3-LTRACE_OPEN_FAIL

3 PLATFORM

PLDMGR-3-NO_CONSOLE_TUNNELING

3 PLATFORM

PLDMGR-3-SHM_WIN_SETUP

3 PLATFORM

PLDMGR-4-CLIENT_WARNING

4 PLATFORM

PLDMGR-4-DEBUG_WARNING

4 PLATFORM

PLDMGR-4-EXT_USB_FAULT

4 PLATFORM

PLDMGR-6-LTRACE_BUF_INIT

6 PLATFORM

PLDMGR-6-LTRACE_DECODE_INIT

6 PLATFORM

PLDMGR-6-MCU_DOWN_REV

6 PLATFORM

PLIM_16P_OC48-3-DEVICE_INTR_CLEAR

3 PLATFORM

PLIM_16P_OC48-3-DEVICE_INTR_DISABLE

3 PLATFORM

PLIM_16P_OC48-3-DRV_INIT_ERR

3 PLATFORM

PLIM_16P_OC48-3-GENERIC_ERROR

3 PLATFORM

PLIM_16P_OC48-3-GET_NODEID_ERR

3 PLATFORM

PLIM_16P_OC48-6-GENERIC_INFO

6 PLATFORM

PLIM_16P_OC48-6-OIM_OIR

6 PLATFORM

PLIM_IPC-3-API_ERROR

3 PLATFORM

PLIM_IPC-3-ERROR

3 PLATFORM

PLIM_IPC-3-INIT_ERROR

3 PLATFORM

PLIM_IPC-6-INFO

6 PLATFORM

PLIM_SERVICES-3-BABMI_RESET_FAIL

3 PLATFORM

PLIM_SERVICES-3-BPARAMS_ERROR

3 PLATFORM

PLIM_SERVICES-3BPARAMS_UPDATE_FAILURE

3 PLATFORM

PLIM_SERVICES-3-EDM_INIT_FAILURE

3 PLATFORM

PLIM_SERVICES-3-ERR_EDM_INIT

3 PLATFORM

PLIM_SERVICES-3-ERR_EVM_EVENT_BLOCK

3 PLATFORM

PLIM_SERVICES-3-ERR_MEM_ALLOC

3 PLATFORM

PLIM_SERVICES-3-ERR_PLIM_SERVICES_INIT

3 PLATFORM

PLIM_SERVICES-3-ERR_UBOOT_UPGRADE

3 PLATFORM

PLIM_SERVICES-3-EVM_EVENT_BLOCK_FAIL

3 PLATFORM

PLIM_SERVICES-3-FLASH_ERROR

3 PLATFORM

PLIM_SERVICES-3-HEARTBEAT_ERROR

3 PLATFORM

PLIM_SERVICES-3-HEARTBEAT_FAILURE

3 PLATFORM

PLIM_SERVICES-3-IMG_DLOAD_ERROR

3 PLATFORM

PLIM_SERVICES-3-IMG_DLOAD_FAILED

3 PLATFORM

PLIM_SERVICES-3-IMG_LAUNCH_ERROR

3 PLATFORM

PLIM_SERVICES-3-IMG_LAUNCH_FAILED

3 PLATFORM

PLIM_SERVICES-3MANS_FPGA_ACCESS_FAIL

3 PLATFORM

PLIM_SERVICES-3-MANS_INIT_FAILURE

3 PLATFORM

PLIM_SERVICES-3MANS_OCTEON_MEM_RW_FAIL

3 PLATFORM

PLIM_SERVICES-3-MEM_ALLOC_FAILURE

3 PLATFORM

PLIM_SERVICES-3MISSING_OR_WRONG_ROLE_CONFIG

3 PLATFORM

PLIM_SERVICES-3-PLIM_SERVICES_INIT_FAIL

3 PLATFORM

PLIM_SERVICES-3PLIM_STATE_CONS_INIT_FAILURE

3 PLATFORM

PLIM_SERVICES-3-SVI_WRONG_CONFIG

3 PLATFORM

PLIM_SERVICES-3-TEJAS_FPGA_ERROR

3 PLATFORM

PLIM_SERVICES-3-TEJAS_GASPP_ERROR

3 PLATFORM

PLIM_SERVICES-3-TEJAS_INIT_ERROR

3 PLATFORM

PLIM_SERVICES-3-UART_ACCESS_FAILURE

3 PLATFORM

PLIM_SERVICES-3-UART_ERROR

3 PLATFORM

PLIM_SERVICES-3-UBOOT_UPGRADE_FAIL

3 PLATFORM

PLIM_SERVICES-6-COLD_RESTART

6 PLATFORM

PLIM_SERVICES-6PORT_USAGE_BELOW_THRESH

6 PLATFORM

PLIM_SERVICES-6PORT_USAGE_THRESH_EXCEEDED

6 PLATFORM

PLIM_SERVICES-6SESSION_USAGE_BELOW_THRESH

6 PLATFORM

PLIM_SERVICES-6SESSION_USAGE_THRESH_EXCEEDED

6 PLATFORM

PLIM_SERVICES-7-GENERIC_ERROR

7 PLATFORM

PLIM_SERVICES-7-GENERIC_INFO

7 PLATFORM

PLIM_SERVICES-7-GENERIC_TILE_ERROR

7 PLATFORM

PLIM_SERVICES-7-GENERIC_TILE_INFO

7 PLATFORM

PLIM_SERVICES-7-HA_ERROR

7 PLATFORM

PLIM_SERVICES-7-TEJAS_GASPP_INFO

7 PLATFORM

PLIM_UPGRADE_FPD-7-SW_ERR

7 PLATFORM

PLU-4-TBM_HW_INIT_FAILED

4 PLATFORM

PLU-4-TBM_INCONS_CORRECTED

4 PLATFORM

PLU-4-TBM_INCONSISTENT

4 PLATFORM

PLU-6-BKT_COMPACTED

6 PLATFORM

PLU-6-BKT_FORCE_COMPACTED

6 PLATFORM

PLUTLU-3-PTMM_INIT_FAILED

3 PLATFORM

PLUTLU-3-PTMM_INIT_PROC_FAILED

3 PLATFORM

PLUTLU-3-SERVER_INIT_FAILED

3 PLATFORM

PLUTLU-4-ERR_RESTART_FAILED

4 PLATFORM

PLUTLU-4-LTRACE_INIT_FAILED

4 PLATFORM

PLUTLU-4-REPL_MODE_FAILED

4 PLATFORM

PM_OS-2-SHM_OPEN

2 PLATFORM

PM_OS-2-SHM_PLATFORM_INFO

2 PLATFORM

PM_OS-2-SHM_READY_WORD

2 PLATFORM

PM_OS-2-UIDB_SHM_OPEN

2 PLATFORM

PM_OS-3-ALLOC_DEFAULT_TBL

3 PLATFORM

PM_OS-3-ALLOC_LBL_TBL

3 PLATFORM

PM_OS-3DC_SERVICES_LIB_IFH_TO_PIC_ELEMENT_FA
IL

3 PLATFORM

PM_OS-3-IFH_2_ENGINE_PORT_FAIL

3 PLATFORM

PM_OS-3-PIC_ARRAY

3 PLATFORM

PORT_CFG-3-INIT

3 PLATFORM

POWERMGR-1-POWER_MODE_WARN

1 PLATFORM

POWERMGR-2-AC_DC_FAILURE

2 PLATFORM

POWERMGR-2-CANNOT_TALK

2 PLATFORM

POWERMGR-2-INITFAIL

2 PLATFORM

POWERMGR-2-INITMEMFAIL

2 PLATFORM

POWERMGR-2-LOW_POWER

2 PLATFORM

POWERMGR-2-NO_PATH

2 PLATFORM

POWERMGR-2-OVERBUDGET

2 PLATFORM

POWERMGR-2-POWER_INSUFFICIENT

2 PLATFORM

POWERMGR-3-BAD_DATA

3 PLATFORM

POWERMGR-3-CANNOT_RESERVE

3 PLATFORM

POWERMGR-3DISCOVERY_THREAD_CREATE_FAILED

3 PLATFORM

POWERMGR-3-ERROR

3 PLATFORM

POWERMGR-3-IMPRECISE

3 PLATFORM

POWERMGR-3-INIT_SEM_ERR

3 PLATFORM

POWERMGR-3-INTERIM

3 PLATFORM

POWERMGR-3-INVALID_COMBINATION

3 PLATFORM

POWERMGR-3-NODEID_CREATE_ERROR

3 PLATFORM

POWERMGR-3-NOTFOUND

3 PLATFORM

POWERMGR-3-ROM_ERROR_STATUS

3 PLATFORM

POWERMGR-3-SEM_SEND_ERR

3 PLATFORM

POWERMGR-3-STILL_POWERED

3 PLATFORM

POWERMGR-3-SYSDB_BIND_ERROR

3 PLATFORM

POWERMGR-3-SYSDB_SET_ERROR

3 PLATFORM

POWERMGR-3-TIMEOUT

3 PLATFORM

POWERMGR-3-UNKNOWN_PEM

3 PLATFORM

POWERMGR-3-UNKNOWN_PEMS

3 PLATFORM

POWERMGR-3-UNKNOWN_SHELF

3 PLATFORM

POWERMGR-3-WAIT_SEM_ERR

3 PLATFORM

POWERMGR-4-ENQUEUE

4 PLATFORM

POWERMGR-4-ENQUEUE_ZONE

4 PLATFORM

POWERMGR-4-INVALID_COND

4 PLATFORM

POWERMGR-4-INVALID_SCALE

4 PLATFORM

POWERMGR-4-PEM_DOWN

4 PLATFORM

POWERMGR-4-PRIO_SLOT_EMPTY

4 PLATFORM

POWERMGR-4-TEST_CHASSIS

4 PLATFORM

POWERMGR-4-UNPOWERED

4 PLATFORM

POWERMGR-5-EVENT_ERROR

5 PLATFORM

POWERMGR-5-INVALID_EVENT

5 PLATFORM

POWERMGR-5-MIXED_PEMS

5 PLATFORM

POWERMGR-5-PEM_UP

5 PLATFORM

POWERMGR-5-REMOVED

5 PLATFORM

POWERMGR-5-UNKNOWN_TYPE

5 PLATFORM

POWERMGR-6-BUDGET_OK

6 PLATFORM

POWERMGR-6-CARD_OVERRIDE

6 PLATFORM

POWERMGR-6-DEBUG

6 PLATFORM

POWERMGR-6-INFO

6 PLATFORM

POWERMGR-6-INSERTED

6 PLATFORM

POWERMGR-6-PEM_OVERRIDE

6 PLATFORM

POWERMGR-6-ZONE_OVERRIDE

6 PLATFORM

preroute-3-INTERNAL_ERR

3 PLATFORM

preroute-3-INTERNAL_FAILURE

3 PLATFORM

preroute-6-INFO_MSG

6 PLATFORM

preroute-6-INFO_MSG

6 PLATFORM

PROCMGR_DLL-2-CRIT_FSB_ERROR

2 PLATFORM

PROCMGR_DLL-2-CRIT_INT_MCH_ERROR

2 PLATFORM

PROCMGR_DLL-3-HANDLE_ERR

3 PLATFORM

PROCMGR_DLL-3-LTRACE_INIT_ERROR

3 PLATFORM

PROCMGR_DLL-3-UNCORR_DDR_ERROR

3 PLATFORM

PROCMGR_DLL-3-UNCORR_FSB_ERROR

3 PLATFORM

PROCMGR_DLL-3UNCORR_INT_MCH_ERROR

3 PLATFORM

PROCMGR_DLL-6-PERFMON_ENABLED

6 PLATFORM

PROCMGR_DLL-6-PERFMON_NOTSUPP

6 PLATFORM

PROCMGR-3-CERR_REG_ERROR

3 PLATFORM

PROCMGR-3-EVM_CREATE_ERROR

3 PLATFORM

PROCMGR-3-INIT_ERROR

3 PLATFORM

PROCMGR-3-LIB_REG_ERROR

3 PLATFORM

PROCMGR-3-LTRACE_INIT_ERROR

3 PLATFORM

PROCMGR-3-MEM_ALLOC_ERROR

3 PLATFORM

PROCMGR-6-ERROR_LOG_SUCCESS

6 PLATFORM

PROCMGR-7-PM_REPORT_ERROR

7 PLATFORM

PROCMGR-7-SYSDB_EDM_REG_ERROR

7 PLATFORM

PROCMGR-7-THRESH_RESET_ERROR

7 PLATFORM

PRP_HW-1-NVRAM_LOW_BATTERY_ERROR

1 PLATFORM

PRP_HW-1-OIR_IN

1 PLATFORM

PRP_HW-1-OIR_OUT

1 PLATFORM

PRP_HW-3-INIT_ERROR

3 PLATFORM

PRP3_FABIO-3-ERR_INIT

3 PLATFORM

PRP3_SLR_FABIO-3-ERR_INIT

3 PLATFORM

PSARB-1-WRONG_SLOT

1 PLATFORM

PSARB-2-MSG_HEARTBEAT_LOST

2 PLATFORM

PSARB-3-INIT_FAIL

3 PLATFORM

PSARB-3-LR_INFO_FAILURE

3 PLATFORM

PSARB-3-STANDBY_READY_QUERY_FAILURE

3 PLATFORM

PSARB-3-TWO_PRIMARY_DETECTED

3 PLATFORM

PSARB-4-CONFLICT_WITH_DSC

4 PLATFORM

PSARB-4-PARTNER_NOT_IN_LR

4 PLATFORM

PSARB-4-SPURIOUS_COUNTDOWN

4 PLATFORM

PSARB-5-IOS_RP_DETECTED

5 PLATFORM

PSARB-6-DEBUG_REMINDER

6 PLATFORM

PSARB-6-FORCE_DOWN

6 PLATFORM

PSARB-6-GO_ACTIVE

6 PLATFORM

PSARB-6-GO_STANDBY

6 PLATFORM

PSARB-6-IGNORE_TO

6 PLATFORM

PSARB-6-IGNORING_ACTIVE_TIMEOUT

6 PLATFORM

PSARB-6-IGNORING_CARD_TIMEOUT

6 PLATFORM

PSARB-6-MBUS_RX_FAILURE

6 PLATFORM

PSARB-6-NOISY

6 PLATFORM

PSARB-6-NORMAL_TO

6 PLATFORM

PSARB-6-PARTNER_TAKEOVER

6 PLATFORM

PSARB-6-QUIET

6 PLATFORM

PSARB-6-RESUME

6 PLATFORM

PSARB-6-RMF_NOT_REGISTERED

6 PLATFORM

PSARB-6-ROLE_LOCKED

6 PLATFORM

PSARB-6-RX_FROM_PARTNER_FAILURE

6 PLATFORM

PSARB-6-SELF_SEND_FAILURE

6 PLATFORM

PSARB-6-STANDBY_NOT_READY

6 PLATFORM

PSARB-6-SUSPEND

6 PLATFORM

PSARB-6-TAKE_OVER

6 PLATFORM

PSARBLC-3-INIT_FAIL

3 PLATFORM

PSARBLC-3-LR_NAME

3 PLATFORM

PSARBLC-3-SELF_RESET_DLRSC_DOWN

3 PLATFORM

PSARBLC-6-TIMER_FAIL

6 PLATFORM

PTP-6-SERVO_EVENTS

6 PLATFORM

PUNT_INFRA-3-INIT

3 PLATFORM

PUNT_SWITCH-2-REG_ACCESS_FAIL

2 PLATFORM

PUNT_SWITCH-3-LINK_FAIL_0

3 PLATFORM

PUNT_SWITCH-3-LINK_FAIL_1

3 PLATFORM

PUNT_SWITCH-3-LINK_FAIL_2

3 PLATFORM

PUNT_SWITCH-3-LINK_FAIL_24

3 PLATFORM

PUNT_SWITCH-3-LINK_FAIL_25

3 PLATFORM

PUNT_SWITCH-3-LINK_FAIL_3

3 PLATFORM

PUNT_SWITCH-3-LINK_FAIL_4

3 PLATFORM

PUNT_SWITCH-3-LINK_FAIL_5

3 PLATFORM

PUNT_SWITCH-3-LINK_FAIL_6

3 PLATFORM

PUNT_SWITCH-3-LINK_FAIL_7

3 PLATFORM

PUNT_SWITCH-3-LINK_FAIL_8

3 PLATFORM

PUNT_SWITCH-3-LINK_FAIL_9

3 PLATFORM

PUNT-2-CPU_RGMII_RX_LINK_FAIL_0

2 PLATFORM

PUNT-2-CPU_RGMII_RX_LINK_FAIL_1

2 PLATFORM

PUNT-2-DDR_IF_FAIL

2 PLATFORM

PUNT-2-ILK_IF_FAIL

2 PLATFORM

PUNT-2-REG_ACCESS_FAIL

2 PLATFORM

PUNT-2-XAUI_IF_FAIL

2 PLATFORM

PUNT-3-EBS_FAIL

3 PLATFORM

PUNT-3-IBS_FAIL

3 PLATFORM

PUNT-3-ILI_FAIL

3 PLATFORM

PUNT-3-PLL_NOT_LOCKED

3 PLATFORM

PUNT-3-XAUI_FAIL

3 PLATFORM

PWHE_EA_PD-7-ERR_NOTSUP

7 PLATFORM

PWR_MGMT-1-IDPROM_INVALID

1 PLATFORM

PWR_MGMT-1-ZERO_CAPACITY

1 PLATFORM

PWR_MGMT-2-MODULE_FAILURE

2 PLATFORM

PWR_MGMT-2-MODULE_WARNING

2 PLATFORM

PWR_MGMT-3-FIRMWARE_UPGRADE_ERROR

3 PLATFORM

PWR_MGMT-3-IO_COMM_FAILURE

3 PLATFORM

PWR_MGMT-4-OIR

4 PLATFORM

PWR_SUPPLY-3-FAULT

3 PLATFORM

PWRMON-1-IDPROM_INVALID

1 PLATFORM

PWRMON-1-ZERO_CAPACITY

1 PLATFORM

PWRMON-2-MODULE_FAIL_REASON

2 PLATFORM

PWRMON-2-MODULE_FAILURE

2 PLATFORM

PWRMON-2-MODULE_WARNING

2 PLATFORM

PWRMON-2-MODULE_WARNING_REASON

2 PLATFORM

PWRMON-3-IO_COMM_FAILURE

3 PLATFORM

PWRMON-4-OIR

4 PLATFORM

QFPCPUBridgeFPGA-0-CPP0_FATAL_ERROR

--

PLATFORM

QFPCPUBridgeFPGA-0-CPP1_FATAL_ERROR

--

PLATFORM

QFPCPUBridgeFPGA-0-FATAL_ERROR

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_ECSR_0

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_ECSR_1

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_HT0_CHAIN

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_HT0_CRC

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_HT0_EOC

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_HT0_ERR_CMD

--

PLATFORM

QFPCPUBridgeFPGA-0INT_HT0_INVALID_CMD

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_HT0_OFLOW

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_HT0_PROTO

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_HT1_CHAIN

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_HT1_CRC

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_HT1_EOC

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_HT1_ERR_CMD

--

PLATFORM

QFPCPUBridgeFPGA-0INT_HT1_INVALID_CMD

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_HT1_OFLOW

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_HT1_PROTO

--

PLATFORM

QFPCPUBridgeFPGA-0INT_LOCAL_REG_READ

--

PLATFORM

QFPCPUBridgeFPGA-0INT_LOCAL_REG_WRITE

--

PLATFORM

QFPCPUBridgeFPGA-0-INT_MBE

--

PLATFORM

QFPCPUBridgeFPGA-3-INT_HT0_DROP_INT

3 PLATFORM

QFPCPUBridgeFPGA-3-INT_HT1_DROP_INT

3 PLATFORM

QFPCPUBridgeFPGA-3INT_PCI_CORE_OVRUN

3 PLATFORM

QFPCPUBridgeFPGA-3-INT_SBE

3 PLATFORM

QFPCPUBridgeFPGA-3-NON_FATAL_ERROR

3 PLATFORM

QOSHAL-4-QOS_CONFIG_WARNING

4 PLATFORM

QOSHAL-4-QOS_CONFIG_WARNING

4 PLATFORM

QOSHAL-6-FLOW_QOS_CONFIG

6 PLATFORM

QOSHAL-6-QOS_MODE_CHANGE

6 PLATFORM

QOSHAL-6-QOS_MODE_CHANGE

6 PLATFORM

QOSHAL-6-QOS_MODE_UNSUPPORTED

6 PLATFORM

QSFP_PLUS-2DEV_QSFP_COMPLIANCE_ERROR

2 PLATFORM

QSFP_PLUS-2DEV_QSFP_OPTICS_PORT_UNSUP

2 PLATFORM

QSFP_PLUS-2DEV_QSFP_PID_NOT_SUPPORTED

2 PLATFORM

QSFP_PLUS-2DEV_QSFP_SUPPORTED_ERROR

2 PLATFORM

QSFP_PLUS-2-HIGH_BIAS_ALARM

2 PLATFORM

QSFP_PLUS-2-HIGH_TEMP_ALARM

2 PLATFORM

QSFP_PLUS-2-HIGH_VOLTAGE_ALARM

2 PLATFORM

QSFP_PLUS-2-LANE_0_HIGH_BIAS_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_0_HIGH_RX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2-LANE_0_HIGH_TEMP_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_0_HIGH_TX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2-LANE_0_LOW_BIAS_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_0_LOW_RX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_0_LOW_TX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2-LANE_1_HIGH_BIAS_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_1_HIGH_RX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2-LANE_1_HIGH_TEMP_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_1_HIGH_TX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2-LANE_1_LOW_BIAS_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_1_LOW_RX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_1_LOW_TX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2-LANE_2_HIGH_BIAS_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_2_HIGH_RX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2-LANE_2_HIGH_TEMP_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_2_HIGH_TX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2-LANE_2_LOW_BIAS_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_2_LOW_RX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_2_LOW_TX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2-LANE_3_HIGH_BIAS_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_3_HIGH_RX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2-LANE_3_HIGH_TEMP_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_3_HIGH_TX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2-LANE_3_LOW_BIAS_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_3_LOW_RX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2LANE_3_LOW_TX_POWER_ALARM

2 PLATFORM

QSFP_PLUS-2-LOW_BIAS_ALARM

2 PLATFORM

QSFP_PLUS-2-LOW_VOLTAGE_ALARM

2 PLATFORM

QSFP_PLUS-3-HIGH_BIAS_WARNING

3 PLATFORM

QSFP_PLUS-3-HIGH_TEMP_WARNING

3 PLATFORM

QSFP_PLUS-3-HIGH_VOLTAGE_WARNING

3 PLATFORM

QSFP_PLUS-3-LANE_0_HIGH_BIAS_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_0_HIGH_RX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_0_HIGH_TEMP_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_0_HIGH_TX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3-LANE_0_LOW_BIAS_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_0_LOW_RX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3-LANE_0_LOW_TEMP_ALARM

3 PLATFORM

QSFP_PLUS-3LANE_0_LOW_TEMP_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_0_LOW_TX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3-LANE_1_HIGH_BIAS_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_1_HIGH_RX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_1_HIGH_TEMP_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_1_HIGH_TX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3-LANE_1_LOW_BIAS_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_1_LOW_RX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3-LANE_1_LOW_TEMP_ALARM

3 PLATFORM

QSFP_PLUS-3LANE_1_LOW_TEMP_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_1_LOW_TX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3-LANE_2_HIGH_BIAS_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_2_HIGH_RX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_2_HIGH_TEMP_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_2_HIGH_TX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3-LANE_2_LOW_BIAS_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_2_LOW_RX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3-LANE_2_LOW_TEMP_ALARM

3 PLATFORM

QSFP_PLUS-3LANE_2_LOW_TEMP_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_2_LOW_TX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3-LANE_3_HIGH_BIAS_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_3_HIGH_RX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_3_HIGH_TEMP_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_3_HIGH_TX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3-LANE_3_LOW_BIAS_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_3_LOW_RX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3-LANE_3_LOW_TEMP_ALARM

3 PLATFORM

QSFP_PLUS-3LANE_3_LOW_TEMP_WARNING

3 PLATFORM

QSFP_PLUS-3LANE_3_LOW_TX_POWER_WARNING

3 PLATFORM

QSFP_PLUS-3-LOW_BIAS_WARNING

3 PLATFORM

QSFP_PLUS-3-LOW_TEMP_ALARM

3 PLATFORM

QSFP_PLUS-3-LOW_TEMP_WARNING

3 PLATFORM

QSFP_PLUS-3-LOW_VOLTAGE_WARNING

3 PLATFORM

RCCLIB-3-ERR_HW_BIST

3 PLATFORM

RCCLIB-3-ERR_HW_BIST

3 PLATFORM

RCCLIB-3-ERR_HW_BIST_TIMEDOUT

3 PLATFORM

RCCLIB-3-ERR_HW_BIST_TIMEDOUT

3 PLATFORM

RCCLIB-3-ERR_HW_INIT

3 PLATFORM

RCCLIB-3-ERR_HW_INIT

3 PLATFORM

RCCLIB-3-ERR_SW_INIT

3 PLATFORM

RCCLIB-3-ERR_SW_INIT

3 PLATFORM

RDM_LIB-6-RWLOCK_TIMEOUT

6 PLATFORM

REDDRV-0ARBITRATION_LOCK_UNAVAILABLE

--

PLATFORM

REDDRV-2-CHECK_COUNTDOWN_EXIT

2 PLATFORM

REDDRV-2-FABRIC_PING_NOT_OK

2 PLATFORM

REDDRV-2-HBLOSS_COLLECT_LOGS

2 PLATFORM

REDDRV-2-IN_INSTALL_RESET

2 PLATFORM

REDDRV-2MSG_LOCAL_NODE_DEAD_RELOAD_MYSELF

2 PLATFORM

REDDRV-2-MSG_LOCAL_NODE_NOT_UP

2 PLATFORM

REDDRV-2-MSG_PRIMARY_GLARE

2 PLATFORM

REDDRV-2-ROLE_MISMATCH

2 PLATFORM

REDDRV-3-CANNOT_RUN_HBLOSS_SCRIPT

3 PLATFORM

REDDRV-3-ERR_INTERNAL_SW

3 PLATFORM

REDDRV-3-ERR_PEER_NOT_ISOLATED

3 PLATFORM

REDDRV-3-ERR_SET_REBOOT_CAUSE

3 PLATFORM

REDDRV-3-FAIL_EXIT

3 PLATFORM

REDDRV-3-FAILURE

3 PLATFORM

REDDRV-3-HBLOSS_SCRIPT_ERROR

3 PLATFORM

REDDRV-3-QSM_NOTIFICATION_FAILED

3 PLATFORM

REDDRV-3-ROLE_LOCKED

3 PLATFORM

REDDRV-3-SWITCHOVER_SUPPORT_FAIL

3 PLATFORM

REDDRV-3-UNEXPECTED

3 PLATFORM

REDDRV-4-CRITERIA_CONFLICT

4 PLATFORM

REDDRV-4-CRITERIA_CONFLICT

4 PLATFORM

REDDRV-4-FILE_OPEN

4 PLATFORM

REDDRV-4-FILE_OPEN

4 PLATFORM

REDDRV-4-HARDWARE_ERROR

4 PLATFORM

REDDRV-4-HARDWARE_READ_FAILURE

4 PLATFORM

REDDRV-4-WD_EXPIRED

4 PLATFORM

REDDRV-4-WD_EXPIRED

4 PLATFORM

REDDRV-5-GO_ACTIVE

5 PLATFORM

REDDRV-5-GO_BID

5 PLATFORM

REDDRV-5-GO_STANDBY

5 PLATFORM

REDDRV-5MSG_DLRSC_CPU_FAILOVER_NORMAL

5 PLATFORM

REDDRV-5MSG_NDLRSC_CPU_FAILOVER_DELAYED

5 PLATFORM

REDDRV-5MSG_PARTNER_NODE_DEAD_START_FAILOV
ER

5 PLATFORM

REDDRV-6-CHECK_FABRIC_CONN

6 PLATFORM

REDDRV-6-DELIVER_POISON_PILL

6 PLATFORM

REDDRV-6-ECM_FAILURE

6 PLATFORM

REDDRV-6-ETH_SERVER_CONNECT_STATUS

6 PLATFORM

REDDRV-6-FABRIC_PING_SUCCESS

6 PLATFORM

REDDRV-6-HBLOSS_COLLECT_COMPLETED

6 PLATFORM

REDDRV-6-LOST_CONNECTIVITY

6 PLATFORM

REDDRV-6-RESET_SELF

6 PLATFORM

REDDRV-6-RESET_STANDBY

6 PLATFORM

REDDRV-6-RESET_STANDBY

6 PLATFORM

REDDRV-6-ROLE_CHANGE

6 PLATFORM

REDDRV-7-ASYNC_SEND

7 PLATFORM

REDDRV-7-ASYNC_SEND

7 PLATFORM

REDDRV-7-ERROR

7 PLATFORM

REDDRV-7-KDUMPER_MESSAGE

7 PLATFORM

REDDRV-7-KDUMPER_MESSAGE

7 PLATFORM

REDDRV-7-MESSAGE_RETRY_ERROR

7 PLATFORM

REDDRV-7-MESSAGE_RETRY_FAILURE

7 PLATFORM

REDDRV-7-MISS_ACK_COUNT

7 PLATFORM

REDDRV-7-MISS_ACK_COUNT

7 PLATFORM

REDDRV-7-MSG_ERROR

7 PLATFORM

REDDRV-7-MSG_INVALID_MSGLEN

7 PLATFORM

REDDRV-7-NODE_ERROR

7 PLATFORM

REDDRV-7-NODE_NO_RESET

7 PLATFORM

REDDRV-7-NODE_RESET

7 PLATFORM

REDDRV-7-NODE_RESET_FAILED

7 PLATFORM

REDDRV-7-OPERATION_FAIL

7 PLATFORM

REDDRV-7-PEER_NO_RESET

7 PLATFORM

REDDRV-7-RMF_REREGISTER

7 PLATFORM

REDDRV-7-ROLE_CHANGE

7 PLATFORM

REDDRV-7-SHMEM

7 PLATFORM

REDDRV-7-SHMEM

7 PLATFORM

REDDRV-7-SW_ROLE_ERROR

7 PLATFORM

REDDRV-7-SW_ROLE_FAILURE

7 PLATFORM

REDDRV-7-UNEXPECTED

7 PLATFORM

REDDRV-7-UNEXPECTED_MSG

7 PLATFORM

REEP-3ERROR_OPENING_ETHERNET_CONNECTION

3 PLATFORM

REEP-3-GET_BOARD_TYPE_FAILED

3 PLATFORM

REEP-3-I2C_BKPLANE_READ_FAILED

3 PLATFORM

REEP-3-I2C_SERVER_CONNECT_FAILED

3 PLATFORM

REEP-7-ERROR_ASYNC_FREE_BUFF

7 PLATFORM

REEP-7-ERROR_ASYNC_GET_BUFF

7 PLATFORM

REEP-7-ERROR_ASYNC_GET_CLIENT_START

7 PLATFORM

REEP-7-ERROR_ASYNC_GET_SRC_MAC

7 PLATFORM

REEP-7-REPLY_SEND_FAILED

7 PLATFORM

REM_PROXY-3-ERR

3 PLATFORM

REM_PROXY-3-ERR_MEM_ALLOC

3 PLATFORM

ROM_UPGRADE_LIB-7-ERROR

7 PLATFORM

ROMMON_BURNER-2-ROM_BURN_FAILED

2 PLATFORM

ROMMON_BURNER-2-ROMA_BOOT
ROMMON_BURNER-3-BAD_ARG

2 PLATFORM
3 PLATFORM

ROMMON_BURNER-3-FILE_OP_ERR

3 PLATFORM

ROMMON_BURNER-3-NO_MEM

3 PLATFORM

ROMMON_BURNER-3-ROMA_ABORT
ROMMON_BURNER-5-progress

3 PLATFORM
5 PLATFORM

ROMMON_BURNER-5-version

5 PLATFORM

RSP_CPUCTRL-1-FC_I2C_ERROR_OR_TO

1 PLATFORM

RSP_CPUCTRL-1-I2C_ERROR

1 PLATFORM

RSP_CPUCTRL-1-I2C_ERROR_2

1 PLATFORM

RSP_CPUCTRL-1-I2C_TIMEOUT

1 PLATFORM

RSP_CPUCTRL-1-I2C_TIMEOUT_2

1 PLATFORM

RSP_CPUCTRL-1-PCIE_RESP_FIFO_SBE

1 PLATFORM

RSP_CPUCTRL-1-PCIE_TX_FIFO_SBE

1 PLATFORM

RSP_CPUCTRL-1-PCIE_TXIF_FIFO_SBE

1 PLATFORM

RSP_CPUCTRL-2-BOARD_REV_ERROR

2 PLATFORM

RSP_CPUCTRL-2-BOARD_REV_PAR_ERROR

2 PLATFORM

RSP_CPUCTRL-2-DAO_PROGRAM_ERR

2 PLATFORM

RSP_CPUCTRL-2-DEV_VERSION_ERROR

2 PLATFORM

RSP_CPUCTRL-2-DTI_PROGRAM_ERR

2 PLATFORM

RSP_CPUCTRL-2-FPD_FPGA_LOAD_ERR

2 PLATFORM

RSP_CPUCTRL-2-PCB_VERSION_ERROR

2 PLATFORM

RSP_CPUCTRL-2-PEER_PAR_ERROR

2 PLATFORM

RSP_CPUCTRL-2-SLOTID_PAR_ERROR

2 PLATFORM

RSP_CPUCTRL-3-ARB_ECTW_RD_PERR

3 PLATFORM

RSP_CPUCTRL-3ARB_ECTW_RDATA_ACKERR

3 PLATFORM

RSP_CPUCTRL-3-ARB_ECTW_RDATA_TO

3 PLATFORM

RSP_CPUCTRL-3-BOARD_SEATING_ERROR

3 PLATFORM

RSP_CPUCTRL-3PCIE_CORE_ERROR_OVERRUN

3 PLATFORM

RSP_CPUCTRL-3PCIE_CORE_ERROR_OVERRUN_2

3 PLATFORM

RSP_CPUCTRL-3-PCIE_FATAL

3 PLATFORM

RSP_CPUCTRL-3-PCIE_RESP_FIFO_MBE

3 PLATFORM

RSP_CPUCTRL-3-PCIE_TX_FIFO_MBE

3 PLATFORM

RSP_CPUCTRL-3-PCIE_TXIF_FIFO_MBE

3 PLATFORM

RSP_CPUCTRL-3-SAC0_ECTW_RD_PERR

3 PLATFORM

RSP_CPUCTRL-3SAC0_ECTW_RDATA_ACKERR

3 PLATFORM

RSP_CPUCTRL-3-SAC0_ECTW_RDATA_TO

3 PLATFORM

RSP_CPUCTRL-3-SCI_CRAM_SBE_ERR

3 PLATFORM

RSP_CPUCTRL-3-SFP_ACK_ERR

3 PLATFORM

RSP_CPUCTRL-3-SFP_TIMEOUT

3 PLATFORM

RSP_CPUCTRL-3-SKT_ECTW_RD_PERR

3 PLATFORM

RSP_CPUCTRL-3-SKT_ECTW_RDATA_ACKERR

3 PLATFORM

RSP_CPUCTRL-3-SKT_ECTW_RDATA_TO

3 PLATFORM

RUNA-2-ERR

2 PLATFORM

RUNA-2-ERR_RC

2 PLATFORM

RWMGR-0-INIT_RETRY_SUCCEEDED

--

PLATFORM

RWMGR-2-INIT_FAILURE

2 PLATFORM

RWMGR-2-MALLOC_FAILURE

2 PLATFORM

RWMGR-4-INIT_ERROR

4 PLATFORM

RWMGR-4-TRACE

4 PLATFORM

RWMGR-7-INTERNAL

7 PLATFORM

SATORI-3-GET_BOARD_TYPE_FAIL

3 PLATFORM

SATORI-3-INIT_ERROR

3 PLATFORM

SATORI-3-LTRACE_INIT_ERROR

3 PLATFORM

SATORI-3-PCIE_ATTACH_FAIL

3 PLATFORM

SATORI-4-WARNING

4 PLATFORM

SATORI-6-INFO

6 PLATFORM

SATORI-6-SETTIME_INFO

6 PLATFORM

SCC-2-BAD_ID_HW

2 PLATFORM

SCC-2-FAILED_ID_HW

2 PLATFORM

SCC-2-PROTO_HW

2 PLATFORM

SCENET-3-IO_PRIV

3 PLATFORM

SCF-7-INIT_LTRACE

7 PLATFORM

SE_P2MP_SRVR-2-ERR_EVM_EVENT_BLOCK

2 PLATFORM

SE_P2MP_SRVR-2-FAIL_EVM_EVENT_BLOCK

2 PLATFORM

SE_P2MP_SRVR-2-INIT_APP_FAIL

2 PLATFORM

SE_P2MP_SRVR-2-INIT_ATTACH_FAIL

2 PLATFORM

SE_P2MP_SRVR-2-INIT_EVM_FAIL

2 PLATFORM

SE_P2MP_SRVR-2-INIT_FAIL

2 PLATFORM

SE_P2MP_SRVR-2-RECV_ERROR

2 PLATFORM

SE_P2MP_SRVR-3-DEBUG_ERROR

3 PLATFORM

SE_P2MP_SRVR-3-DEBUG_INIT_FAIL

3 PLATFORM

SE_P2MP_SRVR-3-DEBUG_SHUT_FAIL

3 PLATFORM

SE_P2MP_SRVR-3-DLL_ERROR

3 PLATFORM

SE_P2MP_SRVR-3-DLL_FAIL

3 PLATFORM

SE_P2MP_SRVR-3-EVM_EVENT_BLOCK_FAIL

3 PLATFORM

SE_P2MP_SRVR-3-INIT_CRITICAL_ERROR

3 PLATFORM

SE_P2MP_SRVR-3-INIT_FAILURE

3 PLATFORM

SE_P2MP_SRVR-3-LTRACE_ERROR

3 PLATFORM

SE_P2MP_SRVR-3-LTRACE_FAIL

3 PLATFORM

SECGN-3-PD_FAIL

3 PLATFORM

SERDES-2-TX_ERR

2 PLATFORM

SERDES-3-RX_ERR

3 PLATFORM

SERVICE_AGENT-3-EVM_EVENT_BLOCK_FAIL

3 PLATFORM

SERVICE_AGENT-3-INIT_FAILURE

3 PLATFORM

SERVICE_SE-3-ATTACH_FAIL

3 PLATFORM

SERVICE_SE-3-MALLOC_FAIL

3 PLATFORM

SERVICE_SE-6-GENERIC_EVENT

6 PLATFORM

SFP-2-DEV_SFP_COMPLIANCE_ERROR

2 PLATFORM

SFP-2-DEV_SFP_OPTICS_PORT_UNSUP

2 PLATFORM

SFP-2-DEV_SFP_SUPPORTED_ERROR

2 PLATFORM

SFP-2-HIGH_LASER_BIAS_ALARM

2 PLATFORM

SFP-2-HIGH_RX_POWER_ALARM

2 PLATFORM

SFP-2-HIGH_TEMP_ALARM

2 PLATFORM

SFP-2-HIGH_TX_POWER_ALARM

2 PLATFORM

SFP-2-HIGH_VOLTAGE_ALARM

2 PLATFORM

SFP-2-LOW_LASER_BIAS_ALARM

2 PLATFORM

SFP-2-LOW_RX_POWER_ALARM

2 PLATFORM

SFP-2-LOW_TX_POWER_ALARM

2 PLATFORM

SFP-2-LOW_VOLTAGE_ALARM

2 PLATFORM

SFP-3-DEV_SFP_PID_NOT_SUPPORTED

3 PLATFORM

SFP-3-HIGH_LASER_BIAS_WARNING

3 PLATFORM

SFP-3-HIGH_RX_POWER_WARNING

3 PLATFORM

SFP-3-HIGH_TEMP_WARNING

3 PLATFORM

SFP-3-HIGH_TX_POWER_WARNING

3 PLATFORM

SFP-3-HIGH_VOLTAGE_WARNING

3 PLATFORM

SFP-3-LOW_LASER_BIAS_WARNING

3 PLATFORM

SFP-3-LOW_RX_POWER_WARNING

3 PLATFORM

SFP-3-LOW_TEMP_ALARM

3 PLATFORM

SFP-3-LOW_TEMP_WARNING

3 PLATFORM

SFP-3-LOW_TX_POWER_WARNING

3 PLATFORM

SFP-3-LOW_VOLTAGE_WARNING

3 PLATFORM

SHELFMGR_API-3TLV_MSG_DECODE_ERROR

3 PLATFORM

SHELFMGR_API-3-TLVLIB_INIT_FAIL

3 PLATFORM

SHELFMGR_HAL-1MEMORY_MODULE_ALERT

1 PLATFORM

SHELFMGR_HAL-1PWR_DRIVER_NOT_READY

1 PLATFORM

SHELFMGR_HAL-2-CONFIG_NOT_READY

2 PLATFORM

SHELFMGR_HAL-2CPI_NO_PEER_VALIDATION

2 PLATFORM

SHELFMGR_HAL-2-CPI_NOT_READY

2 PLATFORM

SHELFMGR_HAL-2-CPI_SELF_FAIL

2 PLATFORM

SHELFMGR_HAL-2-CPU_FAILURE_ALERT

2 PLATFORM

SHELFMGR_HAL-3-CAN_CARD_INVALID

3 PLATFORM

SHELFMGR_HAL-3-CAN_INIT_FAILED

3 PLATFORM

SHELFMGR_HAL-3CARD_PRESENCE_DRIVER_INIT_FAILED

3 PLATFORM

SHELFMGR_HAL-3-CBC_OFFLINE

3 PLATFORM

SHELFMGR_HAL-3-NO_POWER_AVAILABLE

3 PLATFORM

SHELFMGR_HAL-3-NO_POWER_FTV2

3 PLATFORM

SHELFMGR_HAL-3POWER_FEED_REDUNDANCY

3 PLATFORM

SHELFMGR_HAL-3-POWER_REQ_INVALID

3 PLATFORM

SHELFMGR_HAL-3POWER_REQ_NOT_DEFINED

3 PLATFORM

SHELFMGR_HAL-3POWER_SUPPLY_REDUNDANCY

3 PLATFORM

SHELFMGR_HAL-6-BOOT_REQ_RECEIVED

6 PLATFORM

SHELFMGR_HAL-6-CARD_POWERCYCLE

6 PLATFORM

SHELFMGR_HAL-6-CARD_POWERDOWN

6 PLATFORM

SHELFMGR_HAL-6-CARD_POWERUP

6 PLATFORM

SHELFMGR_HAL-6-CARD_SHUTDOWN

6 PLATFORM

SHELFMGR_HAL-6-COLD_BOOT

6 PLATFORM

SHELFMGR_HAL-6-CPI_PEER_FAIL

6 PLATFORM

SHELFMGR_HAL-6-HEARTBEAT_ALERT

6 PLATFORM

SHELFMGR_HAL-6-HEARTBEAT_FAIL

6 PLATFORM

SHELFMGR_HAL-6-POWER_REJECTED

6 PLATFORM

SHELFMGR_HAL-7-BOOT_REQ_FAILED

7 PLATFORM

SHELFMGR_HAL-7-CAN_INFO

7 PLATFORM

SHELFMGR_HAL-7-CPI_GET_FAIL

7 PLATFORM

SHELFMGR-0-CD_IN_RESET_STATE

--

PLATFORM

SHELFMGR-0-CHASSIS_SHUTDOWN

--

PLATFORM

SHELFMGR-0-CHASSIS_SHUTDOWN

--

PLATFORM

SHELFMGR-0-MAX_BOOTREQ_BRINGDOWN --

PLATFORM

SHELFMGR-0-MAX_RESET_BRINGDOWN

SHELFMGR-1-ALL_FANTRAYS_OFF

--

PLATFORM

1 PLATFORM

SHELFMGR-1-ALL_FANTRAYS_REMOVED

1 PLATFORM

SHELFMGR-1-BOTH_FC_REMOVED

1 PLATFORM

SHELFMGR-1CLEAR_ALL_FANTRAYS_REMOVED

1 PLATFORM

SHELFMGR-1-INRESET_ALARM

1 PLATFORM

SHELFMGR-1-NO_POWER_AVAIL

1 PLATFORM

SHELFMGR-1PARTIAL_CHASSIS_SHUTDOWN_POWERUP

1 PLATFORM

SHELFMGR-1SET_ALL_FANTRAYS_REMOVED

1 PLATFORM

SHELFMGR-2-NODE_REBOOT_RECEIVED

2 PLATFORM

SHELFMGR-3-BOARD_NOT_SUPPORTED

3 PLATFORM

SHELFMGR-3-BOARD_NOT_SUPPORTED

3 PLATFORM

SHELFMGR-3BOARD_NOT_SUPPORTED_ONSLOT

3 PLATFORM

SHELFMGR-3CHECKPT_MEM_RESTORE_FAILED

3 PLATFORM

SHELFMGR-3-CHKPT_MEM_OUT_OF_RANGE

3 PLATFORM

SHELFMGR-3-CHKPT_MEM_RESTORE_ERR

3 PLATFORM

SHELFMGR-3-DRP_NOT_BOOTED_UP

3 PLATFORM

SHELFMGR-3-EMPTY_SERIAL_FAIL_BOOT

3 PLATFORM

SHELFMGR-3-EMPTY_SERIAL_FAIL_BOOT

3 PLATFORM

SHELFMGR-3-FAILED_LOAD

3 PLATFORM

SHELFMGR-3-FAILED_LOAD

3 PLATFORM

SHELFMGR-3-FAILEDPOWERUP

3 PLATFORM

SHELFMGR-3-FSMTIMEOUT_RESET

3 PLATFORM

SHELFMGR-3-FSMTIMEOUT_RSP_ISOLATION

3 PLATFORM

SHELFMGR-3-FSMTIMEOUTA_RESET

3 PLATFORM

SHELFMGR-3-FSMTIMEOUTB_RESET

3 PLATFORM

SHELFMGR-3-FSMTIMEOUTD_RESET

3 PLATFORM

SHELFMGR-3-FSMTIMEOUTMDR_RESET

3 PLATFORM

SHELFMGR-3INCOMPATIBLE_FC_FOR_CHASSIS

3 PLATFORM

SHELFMGR-3INCOMPATIBLE_LC_FOR_CHASSIS

3 PLATFORM

SHELFMGR-3INCOMPATIBLE_RP_FOR_CHASSIS

3 PLATFORM

SHELFMGR-3-INRESET_BRINGDOWN

3 PLATFORM

SHELFMGR-3-INRESET_INV_CARD_TYPE

3 PLATFORM

SHELFMGR-3-INV_NODEID_EVT_IGNORE

3 PLATFORM

SHELFMGR-3INV_NODEID_IN_CHKPT_MEMORY

3 PLATFORM

SHELFMGR-3-INVALID_SLOTID_IN_BOOTREQ

3 PLATFORM

SHELFMGR-3-LOCAL_RESET_TIMEDOUT

3 PLATFORM

SHELFMGR-3-MIXED_MEMORY_ALARM

3 PLATFORM

SHELFMGR-3-MIXED_MEMORY_FORCED

3 PLATFORM

SHELFMGR-3-MIXED_MEMORY_POWERED

3 PLATFORM

SHELFMGR-3-MIXED_MEMORY_SHUT

3 PLATFORM

SHELFMGR-3-MIXED_RP_FOR_CHASSIS

3 PLATFORM

SHELFMGR-3-MSG_SEND_FAILED

3 PLATFORM

SHELFMGR-3-NODE_DB_CREATE_ERR

3 PLATFORM

SHELFMGR-3-NODE_KDUMP

3 PLATFORM

SHELFMGR-3NODE_KERNEL_DUMP_TIMEOUT

3 PLATFORM

SHELFMGR-3-NODE_RESET_ALARM

3 PLATFORM

SHELFMGR-3-NODE_RESET_ALARM

3 PLATFORM

SHELFMGR-3-NODE_RESET_BRINGDOWN

3 PLATFORM

SHELFMGR-3-NODE_RESET_BRINGDOWN

3 PLATFORM

SHELFMGR-3-PARTIAL_INSERTED_CARD

3 PLATFORM

SHELFMGR-3-POWERDOWN_RESET

3 PLATFORM

SHELFMGR-3-POWERRELOAD_RESET

3 PLATFORM

SHELFMGR-3-RACK_NOT_BOOTED_UP

3 PLATFORM

SHELFMGR-3-RESET_ON_I2C_ALARM

3 PLATFORM

SHELFMGR-3-RP_SHUTDOWN

3 PLATFORM

SHELFMGR-3-RP_SHUTDOWN

3 PLATFORM

SHELFMGR-3-RSP_ISOLATION_MSG_INVALID

3 PLATFORM

SHELFMGR-3-RSP_MIXED_MEMORY

3 PLATFORM

SHELFMGR-3-RSP_MIXED_VER

3 PLATFORM

SHELFMGR-3-SHUTDOWN

3 PLATFORM

SHELFMGR-3-SHUTDOWN

3 PLATFORM

SHELFMGR-3SHUTDOWN_ON_BOARD_FAULT

3 PLATFORM

SHELFMGR-3SHUTDOWN_ON_ENVMON_ALARM

3 PLATFORM

SHELFMGR-3-SHUTDOWN_ON_I2C_ALARM

3 PLATFORM

SHELFMGR-3SHUTDOWN_ON_MULTIPLE_UNGRACEFUL_R
ELOAD

3 PLATFORM

SHELFMGR-3-SHUTDOWN_RESET

3 PLATFORM

SHELFMGR-3-SHUTDOWN_RESET

3 PLATFORM

SHELFMGR-3-STATE_MSG_DELAY

3 PLATFORM

SHELFMGR-3-TIMER_QUEUE_FULL

3 PLATFORM

SHELFMGR-3-UNEXP_EVENT

3 PLATFORM

SHELFMGR-3-UNEXPECTED_EVENT

3 PLATFORM

SHELFMGR-3-UNEXPECTED_EXIT

3 PLATFORM

SHELFMGR-3-UNKNOWN_BOARD

3 PLATFORM

SHELFMGR-3-UNKNOWN_BOARD

3 PLATFORM

SHELFMGR-3-UNKNOWN_SLOT

3 PLATFORM

SHELFMGR-4CMDLINE_BOOT_OVERRIDE_ENABLED

4 PLATFORM

SHELFMGR-4-COLLECTING_DEBUGS

4 PLATFORM

SHELFMGR-4-EEPROM_READ_FAIL

4 PLATFORM

SHELFMGR-4EMPTY_SERIAL_BOOT_OVERRIDE

4 PLATFORM

SHELFMGR-4-FC40G_NOT_POWERED_ON

4 PLATFORM

SHELFMGR-4-IDPROM_READ_FAIL

4 PLATFORM

SHELFMGR-4-INVALID_PLIM

4 PLATFORM

SHELFMGR-4-L3LC_NOT_POWERED_ON

4 PLATFORM

SHELFMGR-4-NO_HB_RECEIVED

4 PLATFORM

SHELFMGR-4NON_SERVICES_PLIM_MISPLACED

4 PLATFORM

SHELFMGR-4-SCRIPT_FAIL

4 PLATFORM

SHELFMGR-4-SERVICES_PLIM_MISPLACED

4 PLATFORM

SHELFMGR-4-WARM_RLD_FAILED

4 PLATFORM

SHELFMGR-4-WARM_RLD_FAILED

4 PLATFORM

SHELFMGR-6-ABORT

6 PLATFORM

SHELFMGR-6BOOT_OVERRIDE_CMD_DEPRECATED

6 PLATFORM

SHELFMGR-6-BOOTREQ_MAX

6 PLATFORM

SHELFMGR-6-BRINGDOWN_REQUEST

6 PLATFORM

SHELFMGR-6-BRINGDOWN_REQUEST_LIB

6 PLATFORM

SHELFMGR-6-ETH_SERVER_CONNECTED

6 PLATFORM

SHELFMGR-6-ETH_SERVER_DISCONNECTED

6 PLATFORM

SHELFMGR-6-FABRIC_CARD_RESET

6 PLATFORM

SHELFMGR-6FABRIC_CARD_RESET_REJECTED

6 PLATFORM

SHELFMGR-6-HB_RECEIVED_AGAIN

6 PLATFORM

SHELFMGR-6-NO_PLIM

6 PLATFORM

SHELFMGR-6-NO_PLIM

6 PLATFORM

SHELFMGR-6-NODE_CPU_RESET

6 PLATFORM

SHELFMGR-6-NODE_DISCOVERY

6 PLATFORM

SHELFMGR-6-NODE_IMDR_COMPLETED

6 PLATFORM

SHELFMGR-6-NODE_KERNEL_DUMP_EVENT

6 PLATFORM

SHELFMGR-6-NODE_NORESET

6 PLATFORM

SHELFMGR-6-NODE_NORESET

6 PLATFORM

SHELFMGR-6-NODE_RESET
SHELFMGR-6-NODE_STATE_CHANGE

6 PLATFORM
6 PLATFORM

SHELFMGR-6-NOREASON_RESET

6 PLATFORM

SHELFMGR-6-NOREASON_RESET

6 PLATFORM

SHELFMGR-6-POWERDOWN_RESET

6 PLATFORM

SHELFMGR-6-POWERRELOAD_RESET

6 PLATFORM

SHELFMGR-6-RSP_ISOLATED

6 PLATFORM

SHELFMGR-6-SYSTEM_COLD_START

6 PLATFORM

SHELFMGR-6-USER_RESET

6 PLATFORM

SHELFMGR-6-USER_RESET

6 PLATFORM

SHELFMGR-6-USER_RESET_REJECTED

6 PLATFORM

SHELFMGR-6-WARM_RLD_JUMP

6 PLATFORM

SHELFMGR-7-WARM_RLD_FO

7 PLATFORM

SHELFMGR-7-WARM_RLD_OK

7 PLATFORM

SHELFMGR-7-WARM_RLD_OK

7 PLATFORM

SHELFMGRV2-0-CHASSIS_SHUTDOWN

--

PLATFORM

SHELFMGRV2-1-ALL_FANTRAYS_OFF

1 PLATFORM

SHELFMGRV2-1-ALL_FANTRAYS_REMOVED

1 PLATFORM

SHELFMGRV2-1-BOTH_FC_REMOVED

1 PLATFORM

SHELFMGRV2-1-FC_OIR_ALERT

1 PLATFORM

SHELFMGRV2-2-INDUCED_ENS_NOTIF

2 PLATFORM

SHELFMGRV2-2-INDUCED_GSP_DOWN

2 PLATFORM

SHELFMGRV2-2-INDUCED_GSP_UP

2 PLATFORM

SHELFMGRV2-2-INDUCED_QNET_DOWN

2 PLATFORM

SHELFMGRV2-2INDUCED_SHELFMGR_NOTIF

2 PLATFORM

SHELFMGRV2-2-INFRA_FAILURE

2 PLATFORM

SHELFMGRV2-2INSUFFICIENT_RACK_POWER

2 PLATFORM

SHELFMGRV2-2INSUFFICIENT_ZONE_POWER

2 PLATFORM

SHELFMGRV2-2-NODE_REBOOT_RECEIVED

2 PLATFORM

SHELFMGRV2-2-RESET_ON_I2C_ALARM

2 PLATFORM

SHELFMGRV2-2SHUTDOWN_ON_I2C_ALARM

2 PLATFORM

SHELFMGRV2-2STDBY_RP_REBOOT_RECEIVED

2 PLATFORM

SHELFMGRV2-2-ZONE_POWER_LOST

2 PLATFORM

SHELFMGRV2-3ALARM_DISPLAY_THREAD_FAIL

3 PLATFORM

SHELFMGRV2-3-ALARM_INIT_FAIL

3 PLATFORM

SHELFMGRV2-3-ALARM_ON_ISOLATED_RP

3 PLATFORM

SHELFMGRV2-3-BOARD_INCOMP

3 PLATFORM

SHELFMGRV2-3BREQ_RCVD_AFTER_POWEROFF

3 PLATFORM

SHELFMGRV2-3-CARD_POWERUP_FAIL

3 PLATFORM

SHELFMGRV2-3-CARD_RELOAD_FAIL

3 PLATFORM

SHELFMGRV2-3-CARD_SHUTDOWN_FAIL

3 PLATFORM

SHELFMGRV2-3CCB_NODEID_CREATION_FAILURE

3 PLATFORM

SHELFMGRV2-3CCB_NODENAME_CREATION_FAILURE

3 PLATFORM

SHELFMGRV2-3-CHKPT_ERROR

3 PLATFORM

SHELFMGRV2-3CHKPT_INVALID_TABLE_NAME

3 PLATFORM

SHELFMGRV2-3CHKPT_RECORD_BAD_LENGTH

3 PLATFORM

SHELFMGRV2-3-CRITICAL_ALARM_RESET

3 PLATFORM

SHELFMGRV2-3-DCDC_SEND_FAILURE

3 PLATFORM

SHELFMGRV2-3-ENS_NOTIF_FAILURE

3 PLATFORM

SHELFMGRV2-3-ERROR

3 PLATFORM

SHELFMGRV2-3-EXEC_SCRIPT_FAILED

3 PLATFORM

SHELFMGRV2-3FAILED_TO_ALLOCATE_RACK

3 PLATFORM

SHELFMGRV2-3-FAILED_TO_GET_SYSCLK

3 PLATFORM

SHELFMGRV2-3-FAILURE

3 PLATFORM

SHELFMGRV2-3-FAILURE2

3 PLATFORM

SHELFMGRV2-3FORCED_POWEROFF_FAILED

3 PLATFORM

SHELFMGRV2-3FSM_LEAF_TIMER_CREATE_FAILURE

3 PLATFORM

SHELFMGRV2-3FSM_ROOT_TIMER_CREATE_FAILURE

3 PLATFORM

SHELFMGRV2-3-GET_HW_BOARDTYPE_FAIL

3 PLATFORM

SHELFMGRV2-3-GET_NODE_NAME_FAILURE

3 PLATFORM

SHELFMGRV2-3-HB_DECODE_ERROR

3 PLATFORM

SHELFMGRV2-3-INCOMP_CARDS_IN_SDR

3 PLATFORM

SHELFMGRV2-3-INVAL_NODEID_POWER

3 PLATFORM

SHELFMGRV2-3-INVALID_POST_RUN_REQ

3 PLATFORM

SHELFMGRV2-3INVALID_SLOTID_IN_BOOTREQ

3 PLATFORM

SHELFMGRV2-3-KILL_SCRIPT_FAILED

3 PLATFORM

SHELFMGRV2-3-MBI_VALIDATION_FAILURE

3 PLATFORM

SHELFMGRV2-3NODE_BREQ_TIMEOUT_RESET

3 PLATFORM

SHELFMGRV2-3-NODE_HBLOSS_RESET

3 PLATFORM

SHELFMGRV2-3NODE_IMDR_PROC_START_TIMEOUT_RESET

3 PLATFORM

SHELFMGRV2-3-NODE_KDUMP

3 PLATFORM

SHELFMGRV2-3NODE_KDUMP_TIMEOUT_RESET

3 PLATFORM

SHELFMGRV2-3NODE_MBI_HB_TIMEOUT_RESET

3 PLATFORM

SHELFMGRV2-3-NODE_POWEROFF_FAILED

3 PLATFORM

SHELFMGRV2-3NODE_REBOOT_TIMEOUT_RESET

3 PLATFORM

SHELFMGRV2-3-NODE_RESET_ALARM

3 PLATFORM

SHELFMGRV2-3NODE_SHUTDOWN_ON_MULTIPLE_RELOAD

3 PLATFORM

SHELFMGRV2-3-NODE_SPECIFIC_FAILURE

3 PLATFORM

SHELFMGRV2-3NODE_XR_HB_TIMEOUT_RESET

3 PLATFORM

SHELFMGRV2-3-NULL_NCB_OFF_OF_FSMCB

3 PLATFORM

SHELFMGRV2-3-PULSE_FAILURE

3 PLATFORM

SHELFMGRV2-3-QNET_NOTIF_FAILURE

3 PLATFORM

SHELFMGRV2-3-RACK_NOT_BOOTED_UP

3 PLATFORM

SHELFMGRV2-3-REQUEST_REJECTED

3 PLATFORM

SHELFMGRV2-3-RP_SHUTDOWN

3 PLATFORM

SHELFMGRV2-3-SCRIPT_ERROR

3 PLATFORM

SHELFMGRV2-3-SCRIPT_KILLED

3 PLATFORM

SHELFMGRV2-3SHUTDOWN_ON_MULTIPLE_UNGRACEFUL_R
ELOAD

3 PLATFORM

SHELFMGRV2-3-SLOT_SPECIFIC_FAILURE

3 PLATFORM

SHELFMGRV2-3-SYSDB_CFG_BIND_FAIL

3 PLATFORM

SHELFMGRV2-3SYSDB_CFG_BIND_OR_UNBIND_FAIL

3 PLATFORM

SHELFMGRV2-3SYSDB_CFG_REGISTER_NOTIF_FAIL

3 PLATFORM

SHELFMGRV2-3-SYSDB_CFG_UNBIND_FAIL

3 PLATFORM

SHELFMGRV2-3-UNEXPECTED_HB

3 PLATFORM

SHELFMGRV2-3-UNEXPECTED_SCRIPT_EXIT

3 PLATFORM

SHELFMGRV2-3-UNKNOWN_BOARD

3 PLATFORM

SHELFMGRV2-3-UNKNOWN_BOOT_PROTOID

3 PLATFORM

SHELFMGRV2-3UNKNOWN_BOOT_REQ_MSG_VER

3 PLATFORM

SHELFMGRV2-3-UNKNOWN_RP_BOARD

3 PLATFORM

SHELFMGRV2-3-UNSUPPORTED_BOARD

3 PLATFORM

SHELFMGRV2-4-ALARM_EVENT_FAIL

4 PLATFORM

SHELFMGRV2-4AVOID_THERMALLY_SENSITIVE_PLIM_IN_UPP
ER_SLOT

4 PLATFORM

SHELFMGRV2-4BRINGDOWN_REQUEST_RCVD

4 PLATFORM

SHELFMGRV2-4CARD_POST_IMAGE_NOT_AVAILABLE

4 PLATFORM

SHELFMGRV2-4CARD_POST_NOT_AVAILABLE

4 PLATFORM

SHELFMGRV2-4-CARD_POST_NOT_TRIGGER

4 PLATFORM

SHELFMGRV2-4-CARD_POST_TRIGGER

4 PLATFORM

SHELFMGRV2-4-CARD_UNPOWERED

4 PLATFORM

SHELFMGRV2-4COLLECTING_DEBUGS_PRIOR_RESET

4 PLATFORM

SHELFMGRV2-4COMBINATION_OF_PLIM_NOT_SUPPORTED

4 PLATFORM

SHELFMGRV2-4-FORCED_POWEROFF

4 PLATFORM

SHELFMGRV2-4HIGH_POWERED_PLIM_NOT_POWERED_ON_
IN_LOWER_BAY

4 PLATFORM

SHELFMGRV2-4HIGH_POWERED_PLIM_NOT_POWERED_ON_
IN_UPPER_BAY

4 PLATFORM

SHELFMGRV2-4IGNORE_REMOTE_RESET_EVENT

4 PLATFORM

SHELFMGRV2-4-INVALID_PARAMETER

4 PLATFORM

SHELFMGRV2-4-LTRACE_INIT_FAIL

4 PLATFORM

SHELFMGRV2-4-NO_PLIM

4 PLATFORM

SHELFMGRV2-4NODE_ISOLATION_ABORTED

4 PLATFORM

SHELFMGRV2-4NON_HIGH_POWERED_PLIM_NOT_POWERE
D_ON_IN_UPPER_BAY

4 PLATFORM

SHELFMGRV2-4NON_SERVICES_PLIM_MISPLACED

4 PLATFORM

SHELFMGRV2-4POWER_MODULE_REDUNDANCY_LOST

4 PLATFORM

SHELFMGRV2-4-POWER_ZONE_DOWN

4 PLATFORM

SHELFMGRV2-4RACK_DOWN_NOTIF_SEND_FAILURE

4 PLATFORM

SHELFMGRV2-4-RELOAD_DENIED

4 PLATFORM

SHELFMGRV2-4SAVED_PARTIAL_RESET_DEBUGS

4 PLATFORM

SHELFMGRV2-4-SAVED_RESET_DEBUGS

4 PLATFORM

SHELFMGRV2-4-SERVICES_PLIM_MISPLACED

4 PLATFORM

SHELFMGRV2-4-SHUTDOWN_REQUEST

4 PLATFORM

SHELFMGRV2-4-STATS_INIT_FAIL

4 PLATFORM

SHELFMGRV2-4-SYSDB_ITEM

4 PLATFORM

SHELFMGRV2-4-UNKNOWN_CFG_TYPE

4 PLATFORM

SHELFMGRV2-5-FDIAG_HBLOSS

5 PLATFORM

SHELFMGRV2-5RELOAD_EVENT_CANCELLED

5 PLATFORM

SHELFMGRV2-5-RELOAD_EVENT_DELAYED

5 PLATFORM

SHELFMGRV2-6-ADMIN_POWEROFF

6 PLATFORM

SHELFMGRV2-6BOOT_REQUEST_TIMER_EXPIRED

6 PLATFORM

SHELFMGRV2-6-CARD_POWER_UNKNOWN

6 PLATFORM

SHELFMGRV2-6-DSC_CHANGE_EVENT
SHELFMGRV2-6-INFO_LOG

6 PLATFORM
6 PLATFORM

SHELFMGRV2-6-NMON_CFG_APPLIED

6 PLATFORM

SHELFMGRV2-6-NMON_CFG_REMOVED

6 PLATFORM

SHELFMGRV2-6-NODE_NORESET

6 PLATFORM

SHELFMGRV2-6-NODE_NOSHUTDOWN

6 PLATFORM

SHELFMGRV2-6POWER_MODULE_REDUNDANCY_RESTORE
D

6 PLATFORM

SHELFMGRV2-6-SUFFICIENT_RACK_POWER

6 PLATFORM

SHELFMGRV2-6-SUFFICIENT_ZONE_POWER

6 PLATFORM

SHELFMGRV2-6-TIMER_EXPIRED

6 PLATFORM

SHELFMGRV2-6-USER_RESET

6 PLATFORM

SHELFMGRV2-6-ZONE_POWER_RESTORED

6 PLATFORM

SHOW_VERSION_CMD-7-IFMGR_BIND

7 PLATFORM

SHOW_VERSION_CMD-7-SYSDB_BIND

7 PLATFORM

SIM_INFRA-3-APIV_BIND_FAILED

3 PLATFORM

SIM_INFRA-3-APIV_INIT_FAILED

3 PLATFORM

SIM_INFRA-3-APIV_LISTENTH_START_FAILED

3 PLATFORM

SIM_INFRA-3-APIV_MSG_ENCODE_ERROR

3 PLATFORM

SIM_INFRA-3-APIV_MSG_SEND_ERROR

3 PLATFORM

SIM_INFRA-3-APIV_NEG_INCOMP

3 PLATFORM

SIM_INFRA-3-APIV_NEG_TIMEOUT

3 PLATFORM

SIM_INFRA-3-APIV_REGIST_FAILED

3 PLATFORM

SIM_INFRA-3-APIV_TRANS_CREATE_FAILED

3 PLATFORM

SIM_INFRA-3-DEBUG_FAIL

3 PLATFORM

SIM_INFRA-3-ENS_ERROR

3 PLATFORM

SIM_INFRA-3-EVENT_FAIL

3 PLATFORM

SIM_INFRA-3-SAM_CFG_ERROR

3 PLATFORM

SIM_INFRA-3-SAM_CMD_ERROR

3 PLATFORM

SIM_INFRA-3-SAM_INV_ERROR

3 PLATFORM

SIM_INFRA-3-SE_PLATFORM_INFO_ERROR

3 PLATFORM

SIM_INFRA-3-SEND_PLATFORM_INFO_FAILED

3 PLATFORM

SIM_INFRA-3-SIM_INV_ERROR

3 PLATFORM

SIM_INFRA-3-SW_ERROR

3 PLATFORM

SIM_INFRA-3-SYSDB_API_ERROR

3 PLATFORM

SIM_INFRA-3-SYSDB_ERROR

3 PLATFORM

SIM_INFRA-6-INSTALL_ROLE

6 PLATFORM

SIM_INFRA-6-PRINT_INFO

6 PLATFORM

SIM_IPC-3-BIND_FAIL

3 PLATFORM

SIM_IPC-3-DEBUG_FAIL

3 PLATFORM

SIM_IPC-3-NODE_FAIL

3 PLATFORM

SIM_IPC-3-OPERATION_FAILURE

3 PLATFORM

SIM_IPC-3-SW_ERROR

3 PLATFORM

SIM_IPC-3-SYSDB_LIST_FAIL

3 PLATFORM

SIM_IPC-3-UNKNOWN_OPTION

3 PLATFORM

SIM_IPC-6-SW_INFO

6 PLATFORM

SIM_SE-3-APIV_FAILURE

3 PLATFORM

SIM_SE-3-BIOS_INIT_FAILURE

3 PLATFORM

SIM_SE-3-BOOT_RECOVERY_ERROR

3 PLATFORM

SIM_SE-3-CPU_THERMAL_SHUT

3 PLATFORM

SIM_SE-3-DISK_FSCK_FAILURE

3 PLATFORM

SIM_SE-3-DISK_FSCK_TIMEOUT

3 PLATFORM

SIM_SE-3-HA_DP_FAILED

3 PLATFORM

SIM_SE-3-HA_ERR

3 PLATFORM

SIM_SE-3-HA_PP_FAILED

3 PLATFORM

SIM_SE-3-HB_FAILED

3 PLATFORM

SIM_SE-3-HB_FAILURE_STATS

3 PLATFORM

SIM_SE-3-HB_SEND_FAILED

3 PLATFORM

SIM_SE-3-HB_SW_ERROR

3 PLATFORM

SIM_SE-3-KDUMP_DONE

3 PLATFORM

SIM_SE-3-KERNEL_CRASHED

3 PLATFORM

SIM_SE-3-KEXE_INIT_TIMEOUT

3 PLATFORM

SIM_SE-3-LATEST_BIOS_BOOT_TIMEOUT

3 PLATFORM

SIM_SE-3-LINUX_INIT_FAILURE

3 PLATFORM

SIM_SE-3-MAINT_IMG_LOAD_FAILURE

3 PLATFORM

SIM_SE-3-MAINT_IMG_NOT_FOUND

3 PLATFORM

SIM_SE-3-SW_ERROR

3 PLATFORM

SIM_SE-3-SYS_INIT_FAILURE

3 PLATFORM

SIM_SE-3-SYSDB_API_ERROR

3 PLATFORM

SIM_SE-4-HA_WARN

4 PLATFORM

SIM_SE-4-MAINT_IMG_BOOT_REQ

4 PLATFORM

SIM_SE-4-ROLE_MISMATCH

4 PLATFORM

SIM_SE-5-HA_INFO

5 PLATFORM

SIM_SE-5-SW_INFO

5 PLATFORM

SIM_SE-6-STATE_CHANGE

6 PLATFORM

SL-7-INIT_FAIL

7 PLATFORM

SL-7-INIT_LTRACE

7 PLATFORM

SLICE_MGR_PROXY-3CAPI_CONNECTION_ERROR

3 PLATFORM

SLICE_MGR_PROXY-3CFGMGR_PARTITION_REG_ERROR

3 PLATFORM

SLICE_MGR_PROXY-3-INIT_ERROR

3 PLATFORM

SLICE_MGR_PROXY-3-SHMWIN_ERROR

3 PLATFORM

SLICE_MGR_PROXY-3-SYSDB_BIND_ERROR

3 PLATFORM

SLICE_MGR_PROXY-3SYSDB_REG_NOTIFY_ERROR

3 PLATFORM

SLICE_MGR_PROXY-3SYSDB_REG_VERIFY_ERROR

3 PLATFORM

SLICE_MGR_PROXY-3-SYSDB_TUPLE_ERROR

3 PLATFORM

SMITH-3-CONN_FAIL

3 PLATFORM

SMITH-3-EVENT_FAIL

3 PLATFORM

SMITH-3-MEMORY_FAIL

3 PLATFORM

SMITH-3-MEMORY_FAIL

3 PLATFORM

SMITH-3-PROGRAMMING_FAILURE

3 PLATFORM

SMITH-3-RT_FAIL

3 PLATFORM

SMITH-3-RT_FAIL_RC

3 PLATFORM

SMITH-3-RT_FAIL_RC

3 PLATFORM

SMITH-3-SYSMGR_FAIL

3 PLATFORM

SMITH-3-WESSEN_FAIL

3 PLATFORM

SMITH-6-PRINT_INFO

6 PLATFORM

SOCKET_SPP-3-ERR_INIT

3 PLATFORM

SOCKET_SPP-3-ERR_MEM_ALLOC

3 PLATFORM

SOCKET_SPP-3-ERR_THREAD

3 PLATFORM

SPA_JBI-3-ERROR

3 PLATFORM

SPA_JBI-3-FAILURE

3 PLATFORM

SPA_JBI-6-INFO

6 PLATFORM

SPA_JBI-6-INFO

6 PLATFORM

SPA_JBI-7-DEBUG

7 PLATFORM

SPA_JBI-7-DEBUG

7 PLATFORM

SPAN_EA-3-ERROR_DETAIL

3 PLATFORM

SPAN_EA-3-ERROR_INTERNAL

3 PLATFORM

SPAN_EA-3-MEM_ERROR

3 PLATFORM

SPAN_EA-3-MEM_ERROR

3 PLATFORM

SPAN_EA-6-INFO

6 PLATFORM

SPAN_EA-7-TLU_WRITE

7 PLATFORM

SPAQFPBridgeCtrl-0-FATAL_ERROR

--

PLATFORM

SPAQFPBridgeCtrl-0-OUT_OF_SYNC

--

PLATFORM

SPAQFPBridgeCtrl-1-ERP_ERROR

1 PLATFORM

SPAQFPBridgeCtrl-1-MBIT_ECC_ERROR

1 PLATFORM

SPAQFPBridgeCtrl-1-PARITY_ERROR

1 PLATFORM

SPAQFPBridgeCtrl-1-RX_ESPI4_ERROR

1 PLATFORM

SPAQFPBridgeCtrl-1-TX_ESPI4_ERROR

1 PLATFORM

SPAQFPBridgeCtrl-3-SBIT_ECC_ERROR

3 PLATFORM

SPAQFPBridgeCtrl-3-SPA_FATAL_ISR

3 PLATFORM

SPAQFPBridgeCtrl-3SPABUS1_PARITY_ERROR

3 PLATFORM

SPAQFPBridgeCtrl-3SPABUS3_PARITY_ERROR

3 PLATFORM

SPAQFPBridgeCtrl-3-SPI_BUS1_ERROR

3 PLATFORM

SPAQFPBridgeCtrl-3-SPI_BUS3_ERROR

3 PLATFORM

SPB_I2C-3-UNRECOVERABLE_BUS_HANG

3 PLATFORM

SPB_I2C-7-BUS_HANG

7 PLATFORM

SPB_I2C-7-BUS_UNHANG_SUCCESS

7 PLATFORM

SPC_I2C-3-UNRECOVERABLE_BUS_HANG

3 PLATFORM

SPC_I2C-7-BUS_HANG

7 PLATFORM

SPC_I2C-7-BUS_UNHANG_SUCCESS

7 PLATFORM

SPENET-2-MDI_READ_FAILURE

2 PLATFORM

SPENET-2-MDI_READ_FAILURE

2 PLATFORM

SPENET-3-INVAL_MEDIA_RATE

3 PLATFORM

SPENET-3-INVAL_MEDIA_RATE

3 PLATFORM

SPENET-3-IO_PRIV

3 PLATFORM

SPENET-3-IO_PRIV

3 PLATFORM

SPENET-7-ERR_DEBUG

7 PLATFORM

SPENET-7-ERR_DEBUG

7 PLATFORM

SPENET-7-ERR_DEBUG

7 PLATFORM

SPIO_PD-3-EA_DEBUG_INIT

3 PLATFORM

SPIO_PD-3-EA_LTRACE_INIT

3 PLATFORM

SPIO_PD-3-INVALID_PID

3 PLATFORM

SPIO_PD-3-LTRACE_INIT

3 PLATFORM

SPIO_PD-3-NULL_EVM

3 PLATFORM

SPIO_PD-3-NULL_INIT_DATA

3 PLATFORM

SPIO_PD-3-NULL_RXNFN_FUNC

3 PLATFORM

SPIO_PD-3-PLIM_ASIC_THREAD

3 PLATFORM

SPIO_PD-4-CONFIG_CFM

4 PLATFORM

SPIO-3BUNDLE_OFFLOAD_NOT_SUPPORTED

3 PLATFORM

SPIO-3CLUSTER_OFFLOAD_NOT_SUPPORTED

3 PLATFORM

SPMCE-0-ECC_REBOOT

--

PLATFORM

SPMCE-3-ERR_KD_MMAP

3 PLATFORM

SPMCE-3-ERR_SET_REBOOT_CAUSE

3 PLATFORM

SPMCE-6-HOURLY_COUNTS

6 PLATFORM

SPP_PDMA-3-ERR_INIT

3 PLATFORM

SPP_PDMA-3-ERR_MEM_ALLOC

3 PLATFORM

SPP_PDMA-3-ERR_THREAD
SQUID_LOADER-5-progress

3 PLATFORM
5 PLATFORM

SSE_FIB_NPU-3-INT_ERR

3 PLATFORM

SSE_FIB_NPU-3-PD_INFRA_ERR

3 PLATFORM

SSE_FIB-3-ATTR_ERR

3 PLATFORM

SSE_FIB-3-INIT_ERR

3 PLATFORM

SSE_FIB-3-INT_ERR

3 PLATFORM

SSE_FIB-3-PD_INFRA_ERR
SSE_IPV4_EA-3-CRITICAL
SSE_IPV4_EA-3-ERROR1
SSE_IPV4_EA-3-ERROR2
SSE_IPV4_EA-3-ERROR3
SSE_IPV4_EA-5-DEBUG
SSE_IPV6_EA-3-CRITICAL
SSE_IPV6_EA-3-ERROR1
SSE_IPV6_EA-3-ERROR2
SSE_IPV6_EA-3-ERROR3
SSE_IPV6_EA-5-DEBUG
SSE_MPLS_EA-3-ERR

3 PLATFORM
3 PLATFORM
3 PLATFORM
3 PLATFORM
3 PLATFORM
5 PLATFORM
3 PLATFORM
3 PLATFORM
3 PLATFORM
3 PLATFORM
5 PLATFORM
3 PLATFORM

SSE_MPLS_EA-3-ERRSTR
SSE_MPLS_EA-6-INFO

3 PLATFORM
6 PLATFORM

SSE_PLU-1-PLU_RESMON_OOR_GREEN

1 PLATFORM

SSE_PLU-1-PLU_RESMON_OOR_ORANGE

1 PLATFORM

SSE_PLU-1-PLU_RESMON_OOR_RED

1 PLATFORM

SSE_PLU-1-PLU_RESMON_OOR_YELLOW

1 PLATFORM

SSE_SERDES-3-ERR_SW_INIT

3 PLATFORM

STATE_OUT_OF_SYNC-6MONITORING_INTERVAL_OVERRIDEN

6 PLATFORM

STATE_OUT_OF_SYNC-6UNSUPPORTED_METRIC_ON_BUNDLE_MEMB
ER

6 PLATFORM

STATS_INFRA-3-ERR_ARG_1

3 PLATFORM

STATS_INFRA-3-ERR_ARG_2

3 PLATFORM

STATS_INFRA-3-ERR_EVENT_MGR

3 PLATFORM

STATS_INFRA-3-ERR_INFRA_MAP

3 PLATFORM

STATS_INFRA-3-ERR_MUTEX_REVIVE

3 PLATFORM

STATS_INFRA-3-ERR_PID

3 PLATFORM

STATS_INFRA-3-ERR_STR

3 PLATFORM

STATS_INFRA-3-ERR_STR_1

3 PLATFORM

STATS_INFRA-3-ERR_STR_1

3 PLATFORM

STATS_INFRA-3-ERR_STR_2

3 PLATFORM

STATS_INFRA-6-ERR_STR

6 PLATFORM

STATS_INFRA-6-ERR_STR_RETURN

6 PLATFORM

STATS_INFRA-6-ERR_TIMER_INIT

6 PLATFORM

STP_SHIM-6-LINK_STATE_CHANGE

6 PLATFORM

STP_SHIM-7-DRV_ERR

7 PLATFORM

SYSLDR_LC-2-NODE_RELOAD

2 PLATFORM

SYSLDR_LC-2-NODE_RELOAD_NOW

2 PLATFORM

SYSLDR_LC-3-CHANNEL_CREATE_FAILURE

3 PLATFORM

SYSLDR_LC-3-CLIENT_CONNECT_FAILURE

3 PLATFORM

SYSLDR_LC-3-EVENT_CREATE_FAILURE

3 PLATFORM

SYSLDR_LC-3-EVENT_FETCH_FAILURE

3 PLATFORM

SYSLDR_LC-3-REGISTRATION_FAILURE

3 PLATFORM

SYSLDR_LC-3-THREAD_CREATE_FAILURE

3 PLATFORM

SYSLDR_LC-6-LTRACE_INIT_ERR

6 PLATFORM

SYSLDR_LC-7-ERR_MSG_SEND

7 PLATFORM

SYSLDR_LC-7-ERR_SERVER_CONNECT

7 PLATFORM

SYSLDR_LC-7-TIMER_TIMEOUT

7 PLATFORM

SYSLDR_LC-7-TIMER_TIMEOUT_MDR

7 PLATFORM

SYSLDR_LC-7-WARNING

7 PLATFORM

SYSLDR_RP-1-NODE_RELOAD_NOW

1 PLATFORM

SYSLDR_RP-2-NODE_RELOAD

2 PLATFORM

SYSLDR_RP-3-ERROR

3 PLATFORM

SYSLDR_RP-4-LTRACE_INIT_ERR

4 PLATFORM

SYSLDR_RP-6-INVALID_MEM_SIZE

6 PLATFORM

SYSLDR_RP-7-ERR_MSG_SEND

7 PLATFORM

SYSLDR_RP-7-ERR_SERVER_CONNECT

7 PLATFORM

SYSLDR_RP-7-TIMER_TIMEOUT

7 PLATFORM

SYSLDR_RP-7-WARNING

7 PLATFORM

SYSLDR-1-MODE_CHANGE

1 PLATFORM

SYSLDR-1-PING_FAILURE

1 PLATFORM

SYSLDR-1-PING_FAILURE_BOOT

1 PLATFORM

SYSLDR-1-SELF_PING_DISABLED

1 PLATFORM

SYSLDR-1-SELF_PING_FAILURE

1 PLATFORM

SYSLDR-1-SELF_PING_FAILURE_BOOT

1 PLATFORM

SYSLDR-2-CRITICAL

2 PLATFORM

SYSLDR-2-FABRIC_DOWN

2 PLATFORM

SYSLDR-2-MBI_FABRIC_DOWN

2 PLATFORM

SYSLDR-2-MBI_NOLOAD

2 PLATFORM

SYSLDR-2-RELOAD_REQ

2 PLATFORM

SYSLDR-3ACTIVE_DSC_NODE_DETERMINATION_FAILE
D

3 PLATFORM

SYSLDR-3-BANDWIDTH_SHUTDOWN

3 PLATFORM

SYSLDR-3-CARD_KDUMPER

3 PLATFORM

SYSLDR-3-DEBUG_INIT_FAILED

3 PLATFORM

SYSLDR-3-ECM_THREAD_CREATE_ERR

3 PLATFORM

SYSLDR-3-ENVMON_SHUTDOWN

3 PLATFORM

SYSLDR-3-ERROR

3 PLATFORM

SYSLDR-3-ERROR2

3 PLATFORM

SYSLDR-3-EVENT_CONNECTION_FAILURE

3 PLATFORM

SYSLDR-3-EVENT_MSG_ATTACH_FAILED

3 PLATFORM

SYSLDR-3-EVM_CREATE_ERROR

3 PLATFORM

SYSLDR-3-EXITING_EVENT_DISPATCH

3 PLATFORM

SYSLDR-3FABRIC_CONTROL_REGISTRATION_FAILURE

3 PLATFORM

SYSLDR-3-FABRIC_DOWN_WARN

3 PLATFORM

SYSLDR-3-FALSE_OIR

3 PLATFORM

SYSLDR-3-FIELD_DIAG_ERROR

3 PLATFORM

SYSLDR-3FIELD_DIAG_THREAD_CREATE_ERR

3 PLATFORM

SYSLDR-3-FPING_THREAD_CREATE_FAILED

3 PLATFORM

SYSLDR-3-FSM_INFO_THREAD_CREATE_ERR

3 PLATFORM

SYSLDR-3-FW_NOTFOUND

3 PLATFORM

SYSLDR-3-GSP_INIT_NOTIFICATION_FAILED

3 PLATFORM

SYSLDR-3-HARD_FAILURE

3 PLATFORM

SYSLDR-3-ISSU_PHASE_DETECTION_FAILED

3 PLATFORM

SYSLDR-3-LICENSE_SHUTDOWN

3 PLATFORM

SYSLDR-3-LOW_LC_MEM

3 PLATFORM

SYSLDR-3LWM_CHANNEL_PATH_CREATE_FAILED

3 PLATFORM

SYSLDR-3-MALFUNCTION_SHUTDOWN

3 PLATFORM

SYSLDR-3-MANY_RESTARTS

3 PLATFORM

SYSLDR-3-MBUS_PING_WARN

3 PLATFORM

SYSLDR-3-MBUS_SHUT_FAILED

3 PLATFORM

SYSLDR-3-MODE_ERROR

3 PLATFORM

SYSLDR-3-NODE_CTRL_FAILED

3 PLATFORM

SYSLDR-3-NODE_ISO_FAILED

3 PLATFORM

SYSLDR-3-NOT_RESPONDING

3 PLATFORM

SYSLDR-3-PCODE_ALLOCATION_FAILED

3 PLATFORM

SYSLDR-3-PFI_THREAD_EXIT

3 PLATFORM

SYSLDR-3-PLUGIN_THREAD_CREATE_FAILED

3 PLATFORM

SYSLDR-3POWER_MGR_MAIN_THREAD_CREATE_FAILE
D

3 PLATFORM

SYSLDR-3-RP_MAX_RELOADS

3 PLATFORM

SYSLDR-3-SHUTDOWN

3 PLATFORM

SYSLDR-3-SLOT_RETRIEVAL_FAILED

3 PLATFORM

SYSLDR-3-SPA_POLL_THREAD_CREATE_ERR

3 PLATFORM

SYSLDR-3-SYSTEM_DB_SETUP_ERROR

3 PLATFORM

SYSLDR-3-TIMER_CREATE_FAILED

3 PLATFORM

SYSLDR-3-TIMER_INIT_ERR

3 PLATFORM

SYSLDR-3-TOO_LARGE

3 PLATFORM

SYSLDR-3-UNKNOWN_MOD

3 PLATFORM

SYSLDR-3-UNPOWER

3 PLATFORM

SYSLDR-3-VOL_SHUTDOWN

3 PLATFORM

SYSLDR-4-AM_I_ON_DSC_CHECK_FAILED

4 PLATFORM

SYSLDR-4-CLIENT_SIZE_MISMATCH

4 PLATFORM

SYSLDR-4-DOWN_REV

4 PLATFORM

SYSLDR-4-ENS_INIT_ERROR

4 PLATFORM

SYSLDR-4-ERR

4 PLATFORM

SYSLDR-4-MBUS_CONNECTION_FAILURE

4 PLATFORM

SYSLDR-4-MBUS_FW

4 PLATFORM

SYSLDR-4-MBUS_IN_ROM

4 PLATFORM

SYSLDR-4-NO_AUTO_RESET

4 PLATFORM

SYSLDR-4-NO_RELOAD_SIM_OIR

4 PLATFORM

SYSLDR-4-PAK_CLIENT_CLEANUP_FAILED

4 PLATFORM

SYSLDR-4-PAKMAN_INIT_FAILED

4 PLATFORM

SYSLDR-4-SPA_WARNING

4 PLATFORM

SYSLDR-4-UNSUPPORTED

4 PLATFORM

SYSLDR-4-WARM_RLD_FAILED

4 PLATFORM

SYSLDR-4-WARM_RLD_NOT_INITIATED

4 PLATFORM

SYSLDR-4-WARN

4 PLATFORM

SYSLDR-4-WARN_LC_MEM
SYSLDR-4-WARN2

4 PLATFORM
4 PLATFORM

SYSLDR-5-BANDWIDTH

5 PLATFORM

SYSLDR-5-BANDWIDTH_RESTART

5 PLATFORM

SYSLDR-5-DRP_DISABLED

5 PLATFORM

SYSLDR-5EVENT_CONNECTION_OPEN_FAILURE

5 PLATFORM

SYSLDR-5-JOIN

5 PLATFORM

SYSLDR-5-LC_ENABLED

5 PLATFORM

SYSLDR-5-MBUS_EEPROM

5 PLATFORM

SYSLDR-5-MON_DRP

5 PLATFORM

SYSLDR-5-MON_RP

5 PLATFORM

SYSLDR-5-OIRIN

5 PLATFORM

SYSLDR-5-OIROUT

5 PLATFORM

SYSLDR-5-RESTART

5 PLATFORM

SYSLDR-5-RESTART_REQ

5 PLATFORM

SYSLDR-5-RP_DISABLED

5 PLATFORM

SYSLDR-5-RP_ENABLED

5 PLATFORM

SYSLDR-6-AUX_CARDS_INFO

6 PLATFORM

SYSLDR-6-CANJAMRST

6 PLATFORM

SYSLDR-6-CARD_REBOOT

6 PLATFORM

SYSLDR-6-FPING_DIAG_COLLECT

6 PLATFORM

SYSLDR-6-FPING_DIAG_COLLECT_RELOAD

6 PLATFORM

SYSLDR-6-INCOMPATIBLE_ROMMON

6 PLATFORM

SYSLDR-6-LTRACE_INIT_ERR

6 PLATFORM

SYSLDR-6-ROMMON_UPGRADE_COMPLETE

6 PLATFORM

SYSLDR-6ROMMON_UPGRADE_IN_PROGRESS

6 PLATFORM

SYSLDR-6-WARM_RLD_REJECTED

6 PLATFORM

SYSLDR-7-CHECKPOINT_INIT_FAILED
SYSLDR-7-DEBUG

7 PLATFORM
7 PLATFORM

SYSLDR-7-DEBUG_INIT_EVENT_FAILED

7 PLATFORM

SYSLDR-7-DEBUG_REGISTER_FAILED

7 PLATFORM

SYSLDR-7-ERR_MEM_ALLOC

7 PLATFORM

SYSLDR-7-ERR_SYSDB_CONNECTION

7 PLATFORM

SYSLDR-7-ERR_SYSDB_DELETE

7 PLATFORM

SYSLDR-7-ERR_SYSDB_GET

7 PLATFORM

SYSLDR-7-ERR_SYSDB_NOTIFY

7 PLATFORM

SYSLDR-7-ERR_SYSDB_SET

7 PLATFORM

SYSLDR-7-EVENT_INIT_FAILED

7 PLATFORM

SYSLDR-7-FATAL

7 PLATFORM

SYSLDR-7-INFO

7 PLATFORM

SYSLDR-7-INTERNAL_ERROR

7 PLATFORM

SYSLDR-7-MUTEX_LOCK_FAILED

7 PLATFORM

SYSLDR-7-MUTEX_UNLOCK_FAILED

7 PLATFORM

SYSLDR-7-WARM_RLD_OK

7 PLATFORM

SYSLDR-7-WARNING

7 PLATFORM

SYSLDR-7-WRONG_EVENT_CONTEXT

7 PLATFORM

TEJAS_DRV-2-CRITICAL_ERROR

2 PLATFORM

TEJAS_DRV-3-GENERIC_ERROR

3 PLATFORM

TEJAS_DRV-6-GENERIC_INFO

6 PLATFORM

TEMPERATURE_ALARM-2DIE_OVERTEMP_CRITICAL

2 PLATFORM

TEMPERATURE_ALARM-3DIE_OVERTEMP_MAJOR

3 PLATFORM

TEMPERATURE_ALARM-3DIE_OVERTEMP_SHUTDOWN_COUNT

3 PLATFORM

TFQ-0-SW_INIT_ERR

--

PLATFORM

TFQ-3-BAD_ALIGN

3 PLATFORM

TFQ-3-BUFHDR_INVALID

3 PLATFORM

TFQ-3-DESCQ_FULL

3 PLATFORM

TFQ-3-ERR_MEM_ALLOC

3 PLATFORM

TFQ-3-FATAL

3 PLATFORM

TFQ-3-FATAL_2

3 PLATFORM

TFQ-3-GEN_INFO

3 PLATFORM

TFQ-3-INFO

3 PLATFORM

TFQ-3-MALLOC_DESC_FAILED

3 PLATFORM

TFQ-3-MALLOC_FAILED

3 PLATFORM

TFQ-3-MEM_ERR

3 PLATFORM

TFQ-3-MSGTOOBIG

3 PLATFORM

TFQ-3-MSGTOOBIG

3 PLATFORM

TFQ-3-NODEID_INVALID

3 PLATFORM

TFQ-3-NOT_YET_IMPLEMENTED

3 PLATFORM

TFQ-3-PAK_DUPLICATE_ERR

3 PLATFORM

TFQ-3-PAK_FREE_ERR

3 PLATFORM

TFQ-3-PAK_INVALID

3 PLATFORM

TFQ-3-PAK_INVALID

3 PLATFORM

TFQ-3-PAK_LEGACY

3 PLATFORM

TFQ-3-QUEUE_BLOCKED

3 PLATFORM

TFQ-3-USAGE

3 PLATFORM

TFQ-4-NODEID_INVALID

4 PLATFORM

TFQ-5-UNEXPECTED_PKT

5 PLATFORM

TGN-3-ERROR_EXIT

3 PLATFORM

TGN-6-OPERATION_INFO

6 PLATFORM

TGN-7-OPERATION_DEBUG

7 PLATFORM

TGN-7-OPERATION_FAIL

7 PLATFORM

TIMESYNC_CLIENT-4-ERR_CONNECT_ARB

4 PLATFORM

TIMESYNC_CLIENT-4-ERR_GET_ARB_STATE

4 PLATFORM

TIMESYNC_CLIENT-4-ERR_GET_TIME

4 PLATFORM

TIMESYNC_CLIENT-4-ERR_INIT_DSC

4 PLATFORM

TIMESYNC_CLIENT-4-ERR_READ_MBUS

4 PLATFORM

TIMESYNC_CLIENT-4-ERR_SET_TIME

4 PLATFORM

TIMESYNC_CLIENT-4-ERR_WRITE_MBUS

4 PLATFORM

TIMESYNC_CLIENT-6-TIME_SET

6 PLATFORM

TIMESYNC-4-ERR_CONNECT_ARB

4 PLATFORM

TIMESYNC-4-ERR_GET_ARB_STATE

4 PLATFORM

TIMESYNC-4-ERR_GET_TIME

4 PLATFORM

TIMESYNC-4-ERR_WRITE_MBUS

4 PLATFORM

TIMESYNC-5-ERR_GET_LR_INFO

5 PLATFORM

TIPCP-3-SW_FAILURE

3 PLATFORM

TLU-4-ADDR_VALIDATE_FAILED

4 PLATFORM

TOPMGR-2-INIT_FAILURE

2 PLATFORM

TOPMGR-2-MALLOC_FAILURE

2 PLATFORM

TOPMGR-3-CHILD_NOTFOUND

3 PLATFORM

TSEC_SPP-3-RX_PKT_DROP

3 PLATFORM

TSEC-2-DRIVER_ERROR

2 PLATFORM

TSEC-3-OPERATION_ERROR

3 PLATFORM

TSEC-4-DRIVER_ERROR_BUFALIGN

4 PLATFORM

TSEC-6-DRIVER_INFO

6 PLATFORM

TSEC-6-DRIVER_INFO_1REG

6 PLATFORM

TSEC-6-DRIVER_INFO_2REG

6 PLATFORM

TSEC-6-OPERATION_INFO

6 PLATFORM

TUNL_GRE_EA_PD-4UNSUPPORTED_CONFIG

4 PLATFORM

TUNNEL_GRE_EA-3-ERROR

3 PLATFORM

TURBO-1-HIGH_PRI_INTR

1 PLATFORM

TURBO-1-NO_STBY_SMDC

1 PLATFORM

TURBO-2-BFM_CHN_FAIL

2 PLATFORM

TURBO-2-BFM_MALLOC_FAIL

2 PLATFORM

TURBO-2-DUMP_ABORT

2 PLATFORM

TURBO-2-DUMP_MMAP_FAIL

2 PLATFORM

TURBO-2-FM_SHUTDOWN

2 PLATFORM

TURBO-2-INIT_SWITCHOVER

2 PLATFORM

TURBO-2-LINUX_MMAP_FAIL

2 PLATFORM

TURBO-2-OCT_INTR

2 PLATFORM

TURBO-2-OCT_MMAP_FAIL

2 PLATFORM

TURBO-2-PCI_MMAP_FAIL

2 PLATFORM

TURBO-2-RECV_INTR

2 PLATFORM

TURBO-2-RECV_NOTIFY

2 PLATFORM

TURBO-2-RELOAD_DC

2 PLATFORM

TURBO-2-SLR_RELOAD

2 PLATFORM

TURBO-2-SPP_MALLOC_FAIL

2 PLATFORM

TURBO-2-SYSDB_SHUTDOWN

2 PLATFORM

TURBO-3-INIT_FAIL

3 PLATFORM

UDLD-4-DISABLE_PORT

4 PLATFORM

UDLD-4-MUTEX_LOCK_FAIL

4 PLATFORM

UDLD-4-MUTEX_UNLOCK_FAIL

4 PLATFORM

UPGRADE_FPD-2-FATAL

2 PLATFORM

UPGRADE_FPD-3-ASYNC_ATTACH

3 PLATFORM

UPGRADE_FPD-3-CHAN_CREATE

3 PLATFORM

UPGRADE_FPD-3-EVT_BLOCK

3 PLATFORM

UPGRADE_FPD-3FW_MGR_OPERATION_ERROR

3 PLATFORM

UPGRADE_FPD-3-GENERIC_FPD_ERROR

3 PLATFORM

UPGRADE_FPD-3-MSG_REPLY

3 PLATFORM

UPGRADE_FPD-3-OPERATION_FAILED

3 PLATFORM

UPGRADE_FPD-3-SYNC_ATTACH

3 PLATFORM

UPGRADE_FPD-4-DOWN_REV

4 PLATFORM

UPGRADE_FPD-4-MIN_REV

4 PLATFORM

UPGRADE_FPD-4-ROMMONA_DOWN_REV

4 PLATFORM

UPGRADE_FPD-4-UP_REV

4 PLATFORM

UPGRADE_FPD-4-WARNING

4 PLATFORM

UPGRADE_FPD-6FW_MGR_OPERATION_INFO

6 PLATFORM

UPGRADE_FPD-6-PASSED

6 PLATFORM

UPGRADE_FPD-6-START

6 PLATFORM

UPGRADE_FPD-6-STATUS

6 PLATFORM

UPGRADE_FPD-6-STATUS_LOC

6 PLATFORM

UPGRADE_FPD-6STATUS_UPG_LOC_ALL_OPT

6 PLATFORM

UPGRADE-3-FL_SIZE

3 PLATFORM

UPGRADE-3-FLASH_DEVICE

3 PLATFORM

UPGRADE-3-IMAGE_UNAVAIL

3 PLATFORM

UPGRADE-3-INVALID_IMAGETYPE

3 PLATFORM

UPGRADE-3-INVALID_MSGTYPE

3 PLATFORM

UPGRADE-3-NEW_ROM_SIZE

3 PLATFORM

UPGRADE-3-NEW_ROM_SIZE

3 PLATFORM

UPGRADE-3-NO_DAUGHTER_CARD

3 PLATFORM

UPGRADE-3-RP_WARNING

3 PLATFORM

UPGRADE-3-SETUP_FAILURE

3 PLATFORM

UPGRADE-3-VERSION_MISSING

3 PLATFORM

UPGRADE-6-STATUS_COMPLETE

6 PLATFORM

UPGRADE-6-STATUS_COMPLETE

6 PLATFORM

UPGRADE-7-ERASE_SECTORS

7 PLATFORM

UPGRADE-7-ERASE_SECTORS

7 PLATFORM

UPGRADE-7-ERR_BUF_READ

7 PLATFORM

UPGRADE-7-ERR_BUF_READ

7 PLATFORM

UPGRADE-7-ERR_CHAN_CREATE

7 PLATFORM

UPGRADE-7-ERR_DEBUG_INIT

7 PLATFORM

UPGRADE-7-ERR_DEBUG_REG

7 PLATFORM

UPGRADE-7-ERR_EVENT_MGR

7 PLATFORM

UPGRADE-7-ERR_FILE_OPEN

7 PLATFORM

UPGRADE-7-ERR_FILE_OPEN

7 PLATFORM

UPGRADE-7-ERR_LWM_REPLY

7 PLATFORM

UPGRADE-7-ERR_MEM_ALLOC

7 PLATFORM

UPGRADE-7-ERR_MEM_ALLOC

7 PLATFORM

UPGRADE-7-FLASH_DEVICE

7 PLATFORM

UPGRADE-7-GET_SLOT

7 PLATFORM

UPGRADE-7-MMAP

7 PLATFORM

UPGRADE-7-MMAP

7 PLATFORM

UPGRADE-7-MUNMAP

7 PLATFORM

UPGRADE-7-MUNMAP

7 PLATFORM

UPGRADE-7-PROGRAM_FLASH

7 PLATFORM

UPGRADE-7-PROGRAM_FLASH

7 PLATFORM

UPGRADE-7-PROGRAM_FLASH_HEADER

7 PLATFORM

UPGRADE-7-STAT

7 PLATFORM

UPGRADE-7-STAT

7 PLATFORM

UPGRADE-7-STATUS_SEND

7 PLATFORM

UPGRADE-7-VERIFY_FLASH

7 PLATFORM

UPGRADE-7-VERIFY_FLASH

7 PLATFORM

UPGRADE-7-VERIFY_FLASH_HEADER

7 PLATFORM

USB-2-DEV_CTRL_TIMEOUT

2 PLATFORM

USB-2-DEV_EUSB0_NOT_AVAILABLE

2 PLATFORM

USB-2-DEV_EUSB0_NOT_RESPONDING

2 PLATFORM

USB-2-DEV_EUSB0_TIMEOUT

2 PLATFORM

USB-2-DEV_EUSB1_NOT_AVAILABLE

2 PLATFORM

USB-2-DEV_EUSB1_NOT_RESPONDING

2 PLATFORM

USB-2-DEV_EUSB1_TIMEOUT

2 PLATFORM

USB-2-DEV_HUB_TIMEOUT

2 PLATFORM

USB-2-DEVICE_TIMEOUT

2 PLATFORM

USB-3-DEV_COMPACTFLASH_TIMEOUT

3 PLATFORM

VCDMA-7-ERR_BAG_REG

7 PLATFORM

VCDMA-7-ERR_DLL_INIT

7 PLATFORM

VCDMA-7-ERR_EVM_CREATE

7 PLATFORM

VCDMA-7-ERR_EVM_NOTIFY

7 PLATFORM

VCDMA-7-ERR_SYSDB_EDM_REG

7 PLATFORM

VIC-3-LOOPBACK_CONFIG

3 PLATFORM

VIC-3-MAC_NOT_CONFIGURED

3 PLATFORM

VIC-3-MIB_STATS

3 PLATFORM

VIC-3-MPA_MAC_NOT_CONFIGURED

3 PLATFORM

VIC-3-OPTICS_PIE_DEACTIVATED

3 PLATFORM

VIC-3-OTN_LICENSE

3 PLATFORM

VIC-3-PFM_FAILED

3 PLATFORM

VIC-3-PFM_IF_FAILED

3 PLATFORM

VIC-3-UDLR_UNSUPPORTED

3 PLATFORM

VIC-4-XCVR_WARNING

4 PLATFORM

VIC-6-INFO

6 PLATFORM

VKG_AMCC2035-3-ERROR_EXIT

3 PLATFORM

VKG_AMCC2035-3-IF_OPERATION_FAIL

3 PLATFORM

VKG_AMCC2035-3-OPERATION_FAIL

3 PLATFORM

VKG_AMCC2035-7-INFO

7 PLATFORM

VKG_BCM8705-3-ERROR_EXIT

3 PLATFORM

VKG_BCM8705-3-IF_OPERATION_FAIL

3 PLATFORM

VKG_BCM8705-3-OPERATION_FAIL

3 PLATFORM

VKG_BCM8705-7-INFO

7 PLATFORM

VKG_CPP_LCPM_SHOW-3SYSDB_IM_FAILURE

3 PLATFORM

VKG_CPP_LCPM_SHOW-7-USAGE

7 PLATFORM

VKG_CPP_PM_SHM-3-FAILURE

3 PLATFORM

VKG_CPP_PM_TEST-3-ERROR

3 PLATFORM

VKG_CPP_PM_TEST-3-ERROR_2

3 PLATFORM

VKG_CPP_PM-3-INIT_FAILURE

3 PLATFORM

VKG_CPP_PM-3-NOMEM_MSGREPLY_FAILURE

3 PLATFORM

VKG_CPP_PM-4-WARNING

4 PLATFORM

VKG_CPP_PM-5-INFO

5 PLATFORM

VKG_INTF_INJ_CAP_DLL-3-LTRACE_INIT

3 PLATFORM

VKG_IP_EA-3-ERR_INFO

3 PLATFORM

VKG_IP_EA-3-ERR_INFO_STR

3 PLATFORM

VKG_IP_EA-3-ERR_INIT

3 PLATFORM

VKG_IP_EA-3-ERR_INIT_STR

3 PLATFORM

VKG_IP_EA-3-ERR_MEM

3 PLATFORM

VKG_IP_EA-3-ERR_MEM_STR

3 PLATFORM

VKG_IP_EA-3-ERROR1

3 PLATFORM

VKG_IP_EA-3-ERROR2

3 PLATFORM

VKG_IPV4_EA-3-FAILURE1

3 PLATFORM

VKG_IPV4_EA-3-FAILURE2

3 PLATFORM

VKG_IPV4_EA-3-FAILURE3

3 PLATFORM

VKG_IPV4_EA-5-DEBUG

5 PLATFORM

VKG_IPV6_EA-3-ERR_INFO

3 PLATFORM

VKG_IPV6_EA-3-ERR_INFO_STR

3 PLATFORM

VKG_IPV6_EA-3-ERR_INIT

3 PLATFORM

VKG_IPV6_EA-3-ERR_INIT_STR

3 PLATFORM

VKG_IPV6_EA-3-ERR_MEM

3 PLATFORM

VKG_IPV6_EA-3-ERR_MEM_STR

3 PLATFORM

VKG_IPV6_EA-3-ERROR1

3 PLATFORM

VKG_IPV6_EA-3-ERROR2

3 PLATFORM

VKG_IPV6_EA-3-FAILURE1

3 PLATFORM

VKG_IPV6_EA-3-FAILURE2

3 PLATFORM

VKG_IPV6_EA-5-DEBUG

5 PLATFORM

VKG_LCPM_SHOW-3-ERROR

3 PLATFORM

VKG_LCPM_SHOW-7-USAGE

7 PLATFORM

VKG_MPLS_EA-3-ERR

3 PLATFORM

VKG_MPLS_EA-3-ERR_INFO

3 PLATFORM

VKG_MPLS_EA-3-ERR_INFO_STR

3 PLATFORM

VKG_MPLS_EA-3-ERR_INFO_TWO_STR

3 PLATFORM

VKG_MPLS_EA-3-ERR_INIT

3 PLATFORM

VKG_MPLS_EA-3-ERR_INIT_STR

3 PLATFORM

VKG_MPLS_EA-3-ERR_MEM

3 PLATFORM

VKG_MPLS_EA-3-ERR_MEM_STR

3 PLATFORM

VKG_PM_TEST-3-ERROR

3 PLATFORM

VKG_PM_TEST-3-ERROR

3 PLATFORM

VKG_PM_TEST-3-ERROR_2

3 PLATFORM

VKG_PM_TEST-3-ERROR_2

3 PLATFORM

VKG_PM-3-ERROR

3 PLATFORM

VKG_PM-3-ERROR

3 PLATFORM

VKG_PM-3-ERROR_INIT

3 PLATFORM

VKG_PM-3-ERROR_INIT

3 PLATFORM

VKG_PM-3-INDEX_FAIL

3 PLATFORM

VKG_PM-3-INDEX_MISMATCH

3 PLATFORM

VKG_PM-3-INTERFACE_ERR

3 PLATFORM

VKG_PM-3-INTERFACE_FAIL

3 PLATFORM

VKG_PM-3-MEMORY_FAILURE

3 PLATFORM

VKG_PM-3-SIZE_ERR

3 PLATFORM

VKG_PM-4-WARNING

4 PLATFORM

VKG_PM-6-DEBUG_INFO

6 PLATFORM

VKG_PM-6-EA_INFO

6 PLATFORM

VKG_PM-6-IFH_INFO

6 PLATFORM

VKG_PM-6-IFH_READ_INFO

6 PLATFORM

VKG_PM-6-INDEX_INFO

6 PLATFORM

VKG_PM-6-INFO

6 PLATFORM

VKG_PM-6-INTERFACE_EA_INFO

6 PLATFORM

VKG_PM-6-L2TRANSPORT_INFO

6 PLATFORM

VKG_PM-6-MALLOC_INFO

6 PLATFORM

VKG_PM-6-MEMORY_INFO

6 PLATFORM

VKG_PM-6-PACKET_INFO

6 PLATFORM

VKG_PM-6-PRINT_INFO

6 PLATFORM

VKG_PM-6-TEST_INFO

6 PLATFORM

VKG_PMLIB_CLIENT-3-ERROR

3 PLATFORM

VKG_PMLIB_CLIENT-4-WARNING

4 PLATFORM

VKG_PMLIB_IM-3-ERROR

3 PLATFORM

VKG_PMLIB_IM-4-WARNING

4 PLATFORM

VKG_PMLIB-2-ERROR_INIT

2 PLATFORM

VKG_PMLIB-3-ERROR

3 PLATFORM

VKG_PMLIB-3-ERROR

3 PLATFORM

VKG_PMLIB-4-WARNING

4 PLATFORM

VKG_SERDES-3-MUTEX_OPERATION_FAIL

3 PLATFORM

VKG_SERDES-3-OPERATION_FAIL

3 PLATFORM

VKG_SERDES-6-INFO

6 PLATFORM

VKG_SIS-3-ERROR

3 PLATFORM

VKG_SIS-3-ERROR_INIT

3 PLATFORM

VKG_SIS-3-ERROR_NO_TB

3 PLATFORM

VKG_SIS-4-WARNING

4 PLATFORM

VKG_SIS-6-GENERIC_EVENT

6 PLATFORM

WD_PLATFORM-2-FAILED_TO_TICK

2 PLATFORM

WD_PLATFORM-2-INTERNAL_ERROR

2 PLATFORM

WD_PLATFORM-3-INVALID_TICK_CALL

3 PLATFORM

WD_PLATFORM-3SRP_STATE_CHANGE_REG_FAILED

3 PLATFORM

WD_PLATFORM-4-INVALID_TICKER

4 PLATFORM

WD_PLATFORM-4-WATCHDOG_STATE

4 PLATFORM

WD_PLATFORM-6-SRP_READY_STATE

6 PLATFORM

WDMBI-3-ERR_SET_REBOOT_CAUSE

3 PLATFORM

WDMBI-3-ERR_SET_REBOOT_CAUSE

3 PLATFORM

WDMBI-3-ERR_SET_REBOOT_CAUSE

3 PLATFORM

XBAR_CLIENT-3-ERR_SPINEID_STR

3 PLATFORM

XBAR_CLIENT-3-GEN_ERR

3 PLATFORM

XBAR_CLIENT-3-GEN_ERR_1

3 PLATFORM

XBAR_CLIENT-3-GEN_ERR_2

3 PLATFORM

XBAR_CLIENT-3-GEN_ERR_3

3 PLATFORM

XBAR_ERR-3-ERR_CARDTYPE

3 PLATFORM

XBAR_ERR-3-ERR_STR

3 PLATFORM

XBAR_ERR-3-ERR_STR_1

3 PLATFORM

XBAR-3-ERR_INIT

3 PLATFORM

XBAR-3-ERR_INIT

3 PLATFORM

XBAR-3-ERR_MEM_ALLOC

3 PLATFORM

XBAR-5-ERR_CONT

5 PLATFORM

XBAR-7-ERR_EVM_CREATE

7 PLATFORM

XBAR-7-ERR_EVM_NOTIFY

7 PLATFORM

XBAR-7-ERR_EXIT

7 PLATFORM

XBAR-7-ERR_EXIT

7 PLATFORM

XBAR-7-ERR_LWM_EVENT_BLOCK

7 PLATFORM

XBAR-7-ERR_LWM_REPLY

7 PLATFORM

XCVR-3-DEBUG_INIT_FAILED

3 PLATFORM

XCVR-3-DEBUG_REGISTER_FAILED

3 PLATFORM

XCVR-3-ERROR

3 PLATFORM

XCVR-3-FAILURE

3 PLATFORM

XCVR-6-ENABLE

6 PLATFORM

XCVR-6-INFO

6 PLATFORM

XCVR-6-REMOVAL

6 PLATFORM

XFP-2-DEV_XFP_COMPLIANCE_ERROR

2 PLATFORM

XFP-2-DEV_XFP_OPTICS_PORT_UNSUP

2 PLATFORM

XFP-2-DEV_XFP_PID_NOT_SUPPORTED

2 PLATFORM

XFP-2-DEV_XFP_SUPPORTED_ERROR

2 PLATFORM

XFP-2-HIGH_LASER_BIAS_ALARM

2 PLATFORM

XFP-2-HIGH_RX_POWER_ALARM

2 PLATFORM

XFP-2-HIGH_TEMP_ALARM

2 PLATFORM

XFP-2-HIGH_TX_POWER_ALARM

2 PLATFORM

XFP-2-LOW_LASER_BIAS_ALARM

2 PLATFORM

XFP-2-LOW_RX_POWER_ALARM

2 PLATFORM

XFP-2-LOW_TX_POWER_ALARM

2 PLATFORM

XFP-3-HIGH_LASER_BIAS_WARNING

3 PLATFORM

XFP-3-HIGH_RX_POWER_WARNING

3 PLATFORM

XFP-3-HIGH_TEMP_WARNING

3 PLATFORM

XFP-3-HIGH_TX_POWER_WARNING

3 PLATFORM

XFP-3-LOW_LASER_BIAS_WARNING

3 PLATFORM

XFP-3-LOW_RX_POWER_WARNING

3 PLATFORM

XFP-3-LOW_TEMP_ALARM

3 PLATFORM

XFP-3-LOW_TEMP_WARNING

3 PLATFORM

XFP-3-LOW_TX_POWER_WARNING

3 PLATFORM

ZENJF-4-BACKUP_NIRVANA_PROM

4 PLATFORM

ZENJF-4-BACKUP_ROMMON

4 PLATFORM

ZENJF-4-BACKUP_ZENJF_PROM

4 PLATFORM

ZENJF-4-DBG_JUMPER_WARNING

4 PLATFORM

ZENJF-4-FMEA_FLAG_WARNING

4 PLATFORM

Zl30160_ERROR-3-ERR_FTRUNCATE

3 PLATFORM

Zl30160_ERROR-3-ERR_MMAP

3 PLATFORM

Zl30160_ERROR-3-ERR_SHM

3 PLATFORM

ZL-3-ERR_MEM_ALLOC

3 PLATFORM

ZL-7-ERR_INIT

7 PLATFORM

ZPLL_API-3-ERR_MEM_ALLOC

3 PLATFORM

ZPLL_API-7-ERR_INIT

7 PLATFORM

PLMGR_OBJ_LIB-3-MUTEX

3 PLMGR_OBJ_LIB

PLMGR_OBJ_LIB-3-NAME_DLLINIT

3 PLMGR_OBJ_LIB

PLMGR_OBJ_LIB-4-DEBUG

4 PLMGR_OBJ_LIB

PLMGR_OBJ_LIB-6-RETRY_INPLACE

6 PLMGR_OBJ_LIB

PLMGR_BAG_OPS-3-NOMEM

3 PLMGR_UIBAG_OPS

PLMGR_BAG_OPS-4-DEBUG

4 PLMGR_UIBAG_OPS

AFMON_EA_TEST-3-ERROR

3 QOS

AFMON_MA-3-CAPS_REMOVE

3 QOS

AFMON_MA-7-INIT

7 QOS

AFMON_MA-7-INVALID_CAPS_STATUS

7 QOS

EFCM-3-ERROR

3 QOS

EFCM-6-INFO

6 QOS

EFCM-7-DEBUG

7 QOS

QOS_EA_BW_CHG-6-BWCHG_LOG

6 QOS

QOS_EA_CLEAR_CTR-6-FAILED

6 QOS

QOS_EA_IIR_ADD-3-FAILED

3 QOS

QOS_EA_INIT-3-ERROR

3 QOS

QOS_EA_INIT-3-FAILED

3 QOS

QOS_EA_INPLACE_ONGOING-3-ERROR

3 QOS

QOS_EA_INPLACE-3-ERROR

3 QOS

QOS_EA_MODIFY-3-FAILED

3 QOS

QOS_EA_TEST-3-ERROR

3 QOS

QOS_EA_VERIFY-6-ERROR

6 QOS

QOS_EA_VERIFY-6-FAILED

6 QOS

QOS_EA-3-ERROR

3 QOS

QOS_EA-3-INIT_ERROR

3 QOS

QOS_EA-3-INIT_ERROR
QOS_EA-6-INFO

3 QOS
6 QOS

QOS_FIFO-7-DEBUG_INIT_ERROR

7 QOS

QOS_LIB_PLMGR_SUPP-3-LTRACEOPEN

3 QOS

QOS_MA-3-CAPS_INFO_ADD

3 QOS

QOS_MA-3-CAPS_REMOVE

3 QOS

QOS_MA-3-DPC_REM

3 QOS

QOS_MA-3-IFH_BW_UPDATE_RATE

3 QOS

QOS_MA-3-INVALID_BW_ENTRY

3 QOS

QOS_MA-3-OP_FAIL

3 QOS

QOS_MA-5-L2_OVHD_MOD

5 QOS

QOS_MA-6-CLEAR_ALL_STATS

6 QOS

QOS_MA-7-FABQOS_SEND_FAILED

7 QOS

QOS_MA-7-INIT

7 QOS

QOS_MA-7-INVALID_CAPS_STATUS

7 QOS

QOS_MA-7-INVALID_ERROR_ARRAY_STATUS

7 QOS

QOS_TXM-3-ENS_INIT

3 QOS

QOS_TXM-7-DEBUG_NETIO_INIT

7 QOS

QOS_TXM-7-NETIO_UNINIT

7 QOS

QOS-2-MALLOC_FAIL

2 QOS

QOS-3-CLEAR_REDQ_ENTRY_FAIL

3 QOS

QOS-3-CONNECT_FAIL

3 QOS

QOS-3-CONNECT_FAIL

3 QOS

QOS-3-DEBUG_FAIL

3 QOS

QOS-3-EA_ICL_CREATE_FAILURE

3 QOS

QOS-3-EA_IIR_ATTACH_FAILURE

3 QOS

QOS-3-EA_IM_CAPS_RESYNC_FAILURE

3 QOS

QOS-3-EA_IMDR_PREPARE_FAILURE

3 QOS

QOS-3-EA_MIPC_NTFN_ACK_FAILURE

3 QOS

QOS-3EA_ROLLBACK_FAILURE_DURING_MODIFY

3 QOS

QOS-3-EA_SCOL_INIT_FAILURE

3 QOS

QOS-3-EA_SHM_INIT_FAILURE

3 QOS

QOS-3-ERR_EVM_CREATE

3 QOS

QOS-3-EVM_CREATE_FAIL

3 QOS

QOS-3-INTF_CREATE_FAIL

3 QOS

QOS-3-INTF_DELETE_FAIL

3 QOS

QOS-3-INTF_MODIFY_FAIL

3 QOS

QOS-3-PROGRAM_REDQ_ENTRY_FAIL

3 QOS

QOS-3-REDQ_UPDATE_HW_FAIL

3 QOS

QOS-3-UNKNWN_INTF_DEFAULT_QUEUE

3 QOS

QOS-3-UPDATE_INTF_BW_FAILURE

3 QOS

QOS-3-WAIT_ERR

3 QOS

QOS-4-ERR_EVM_EVENT_BLOCK

4 QOS

QOS-6-EA_DEBUG_INIT_FAIL

6 QOS

QOS-6-EA_LTRACE_INIT_FAIL

6 QOS

QOS-6-EA_MIPC_NTFN_HNDLR_FAILURE

6 QOS

QOS-6-NETIO_SET_PAK_SHAPEQ_FAIL

6 QOS

QOS-6-NO_SPACE_ERROR

6 QOS

QOS-6-QFIFO_DEBUG_NETIO_INIT_FAIL

6 QOS

QOSEA-3-BM_ADD_REMOVE_ERROR

3 QOS

QOSEA-3-BWCHG_ERROR

3 QOS

QOSEA-3-DB_INSERT_FAILED

3 QOS

QOSEA-3-ERROR

3 QOS

QOSEA-3-EXIT_ERROR

3 QOS

QOSEA-3-HIER_POLICY_NOT_SUPPORTED

3 QOS

QOSEA-3-IMATTR_ERROR

3 QOS

QOSEA-3-INCONSISTENT_CFG_STATE

3 QOS

QOSEA-3IPV4_ACL_REG_CHECK_USAGE_FAILED

3 QOS

QOSEA-3IPV4_ACL_REG_RES_CHECK_FAILED

3 QOS

QOSEA-3IPV6_ACL_REG_CHECK_USAGE_FAILED

3 QOS

QOSEA-3IPV6_ACL_REG_RES_CHECK_FAILED

3 QOS

QOSEA-3-MSG_CHAN

3 QOS

QOSEA-3-MSG_HANDLER_ERR

3 QOS

QOSEA-3-POLICY_ERROR

3 QOS

QOSEA-3-ROLLBACK_ERROR

3 QOS

QOSEA-3-UNHANDLED_MSG

3 QOS

QOSEA-3-UNKNOWN_MSG

3 QOS

QOSEA-4-WARN

4 QOS

QOSEA-5-NOTICE

5 QOS

QOSEA-5-POLICE_PARAM_ADJUST

5 QOS

QOSEA-6-BWCHG_LOG

6 QOS

QOSEA-6-HIER_POLICY_DISASSOC_FAILED

6 QOS

QOSEA-6-INFO

6 QOS

QOSEA-6-MSG_ASYNC

6 QOS

QOSEA-6-POLICY_INFO

6 QOS

QOSEA-6-SKIP_SUBIFS

6 QOS

QOSEA-6-SKIP_VLANS

6 QOS

QOSEA-7-DEBUG

7 QOS

QOSLIB-3-DLOPEN

3 QOS

QOSLIB-4-DLCLOSE

4 QOS

QOSLIBTIF-6-ALE_ATTRIB_VAL

6 QOS

QOSRM_DLL-3-ERROR

3 QOS

QOSRM_DLL-3-MSG_CHAN

3 QOS

QOSRM_DLL-3-MSG_HANDLER_ERR

3 QOS

QOSRM_DLL-3-UNHANDLED_MSG

3 QOS

QOSRM_DLL-3-UNKNOWN_MSG

3 QOS

QOSRM_DLL-3-UNKNOWN_QTYPE

3 QOS

QOSRM_DLL-4-WARN

4 QOS

QOSRM_DLL-6-INFO

6 QOS

QOSRM_DLL-6-MSG_ASYNC

6 QOS

QOSRM_DLL-7-DEBUG

7 QOS

QOSRM-3-ERROR

3 QOS

QOSRM-3-MSG_CHAN

3 QOS

QOSRM-3-MSG_HANDLER_ERR

3 QOS

QOSRM-3-UNHANDLED_MSG

3 QOS

QOSRM-3-UNKNOWN_MSG

3 QOS

QOSRM-3-UNKNOWN_QTYPE

3 QOS

QOSRM-4-WARN

4 QOS

QOSRM-6-INFO

6 QOS

QOSRM-6-MSG_ASYNC

6 QOS

QOSRM-7-DEBUG

7 QOS

QPREP_QOSEA-3-QUEUE_CNT_NULL

3 QOS

QPREP_QOSEA-6-DISP_INTF_TABLE

6 QOS

QPREP_QOSEA-6-DISP_MGID_LIST

6 QOS

QPREP_QOSEA-6-DISP_TEST_IFH_LIST

6 QOS

QPREP_QOSEA-6FAILED_ALLOC_LMGID_LIST

6 QOS

QPREP_QOSEA-6-FAILED_FIND_DSCP

6 QOS

QPREP_QOSEA-6-FAILED_FREE

6 QOS

QPREP_QOSEA-6-FAILED_MEM_ALLOC_IDB

6 QOS

QPREP_QOSEA-6FAILED_MEM_ALLOC_TESTCASE

6 QOS

QPREP_QOSEA-6-FAILED_MIDB_MEM_ALLOC

6 QOS

QPREP_QOSEA-6FAILED_QPREP_DEBUG_INIT

6 QOS

QPREP_QOSEA-6-FAILED_SHRINK

6 QOS

QPREP_QOSEA-6-INTF_EXISTS

6 QOS

QPREP_QOSEA-6-INVALID_MSG_TYPE

6 QOS

QPREP_QOSEA-6-LMGID_DOESNT_EXIST

6 QOS

QPREP_QOSEA-6-LMGID_LIST_AFTER_FREE

6 QOS

QPREP_QOSEA-6-LMGID_LIST_FUNC

6 QOS

QPREP_QOSEA-6LMGID_LIST_FUNC_UNDER_TEST

6 QOS

QPREP_QOSEA-6-MCAST_QUEUE_INFO

6 QOS

QPREP_QOSEA-6-MIDB_LIST

6 QOS

QPREP_QOSEA-6-NO_SUCH_ACTION

6 QOS

QPREP_QOSEA-6-NOT_E3_CARD

6 QOS

QPREP_QOSEA-6-POLICY_EVENT_INFO

6 QOS

QPREP_QOSEA-6-SHOW_IFQ_LIST

6 QOS

QPREP_QOSEA-6-SHOW_MCAST_IF_TABLE

6 QOS

SSE_QOSEA-2-SHMWIN_CRITICAL_ERROR

2 QOS

SSE_QOSEA-3-BANDWIDTH_RANGE

3 QOS

SSE_QOSEA-3-BANDWIDTH_RATIO

3 QOS

SSE_QOSEA-3BANDWIDTH_REMAINING_RATIO

3 QOS

SSE_QOSEA-3-DATABASE_CORRUPTED

3 QOS

SSE_QOSEA-3-DATABASE_RESET_FAILURE

3 QOS

SSE_QOSEA-3-FAILURE_DURING_MODIFY

3 QOS

SSE_QOSEA-3-IM_CAPS_RESYNC_FAILURE

3 QOS

SSE_QOSEA-3-INIT_ERROR

3 QOS

SSE_QOSEA-3ROLLBACK_FAILURE_DURING_MODIFY

3 QOS

SSE_QOSEA-3-SHMWIN_ERROR

3 QOS

SSE_QOSEA-6-DEBUG_INIT_FAIL

6 QOS

SSE_QOSEA-6-LTRACE_INIT_FAIL

6 QOS

VIDMON_MGR-7MAX_CLONE_PROFILE_EXCEEDED

7 QOS

AIB_CLIENT-3-EXTRA_UNLOCK

3 ROUTING

AIB-1-EVENTBLOCK

1 ROUTING

AIB-4-CLDATA_ZERO_REFCOUNT

4 ROUTING

AIB-4-DLLINFO_DB_INIT_FAIL

4 ROUTING

AIB-4-DLLINFO_ZERO_REFCOUNT

4 ROUTING

AIB-4-IDB_NOT_FOUND

4 ROUTING

AIB-4-INDEX_REG_FAIL

4 ROUTING

AIB-4-INDEX_VERSION_FAIL

4 ROUTING

AIB-4-LEN_MISMATCH_CLDATA

4 ROUTING

AIB-4-LTRACE_ERROR

4 ROUTING

AIB-4-RADIXINIT_FAIL

4 ROUTING

AIB-4-SHM_FAIL

4 ROUTING

AIB-4-SYSTEM_FAIL

4 ROUTING

AMT-3-ERR_MALLOC

3 ROUTING

AMT-3-EVM

3 ROUTING

AMT-3-NET_ERR

3 ROUTING

AMT-3-SYSDB_BSCAN_ERR

3 ROUTING

AMT-3-SYSDB_INIT

3 ROUTING

AMT-3-SYSDB_REG_ERR

3 ROUTING

AUTORP_CRP-3EVENT_CONN_MGR_FAILURE

3 ROUTING

AUTORP_CRP-3-GEN_FAILURE

3 ROUTING

AUTORP_CRP-3-IM_RELATED_FAILURE

3 ROUTING

AUTORP_CRP-3-INIT_FAILED

3 ROUTING

AUTORP_CRP-3-IPARM_RELATED_FAILURE

3 ROUTING

AUTORP_CRP-3-TIMER_FAILURE

3 ROUTING

AUTORP_MAP-3-DEBUG_FAILURE

3 ROUTING

AUTORP_MAP-3EVENT_CONN_MGR_FAILURE

3 ROUTING

AUTORP_MAP-3EVENT_MGR_CREATE_FAILED

3 ROUTING

AUTORP_MAP-3-IM_RELATED_FAILURE

3 ROUTING

AUTORP_MAP-3-INIT_FAILED

3 ROUTING

AUTORP_MAP-3-INIT_FAILED_MA

3 ROUTING

AUTORP_MAP-3-IPARM_RELATED_FAILURE

3 ROUTING

AUTORP_MAP-3-OOR_LIMIT

3 ROUTING

AUTORP_MAP-3-SOCKET_FAILURE

3 ROUTING

AUTORP_MAP-3-TIMER_FAILURE

3 ROUTING

AUTORP_MAP-4-OOR_OK

4 ROUTING

AUTORP_MAP-4-OOR_THRESHOLD

4 ROUTING

BGP_VRF-2-MEM_ALLOC

2 ROUTING

BGP_VRF-3-DUPLICATE_ID

3 ROUTING

BGP_VRF-3-INIT

3 ROUTING

BGP_VRF-3-MAX_IMPORT_RTS

3 ROUTING

BGP_VRF-3-NOTIFY

3 ROUTING

BGP_VRF-3-RD_APPLY

3 ROUTING

BGP_VRF-3-RD_PUBLISH

3 ROUTING

BGP-2-ADDROUTE

2 ROUTING

BGP-2-ERR_EVM_EVENT_BLOCK

2 ROUTING

BGP-2-ERR_MEM_ALLOC

2 ROUTING

BGP-2-ERR_THREAD_DEADLOCK

2 ROUTING

BGP-2-FATAL_WRAPPER

2 ROUTING

BGP-3-AF_LIB_FILE_ERROR

3 ROUTING

BGP-3-AF_LIB_FILE_WRONG_INFO

3 ROUTING

BGP-3-ASYNC_IPC

3 ROUTING

BGP-3-ATTRKEY_BAD

3 ROUTING

BGP-3-BAD_REFCNT

3 ROUTING

BGP-3-BPM_AS_INIT

3 ROUTING

BGP-3-BPM_INIT

3 ROUTING

BGP-3-BPM_PROCESS_START

3 ROUTING

BGP-3-BPM_PROCESS_STOP

3 ROUTING

BGP-3-BPM_SWITCH_MODE

3 ROUTING

BGP-3-BRIB_INIT

3 ROUTING

BGP-3-BUF_TOO_SHORT

3 ROUTING

BGP-3-COMM_DECODE_RDINFO

3 ROUTING

BGP-3-CONFIG_DEL

3 ROUTING

BGP-3-CONFIG_FALLOVER

3 ROUTING

BGP-3-CONFIG_SET

3 ROUTING

BGP-3-DEBUG_CONFIG

3 ROUTING

BGP-3-DELPATH

3 ROUTING

BGP-3-DLL_ERROR

3 ROUTING

BGP-3-EDM_INIT_FAILED

3 ROUTING

BGP-3-ERR_ALM_API

3 ROUTING

BGP-3-ERR_ALM_ONE_LABEL

3 ROUTING

BGP-3-ERR_FILE_ATTACH

3 ROUTING

BGP-3-ERR_GENERAL

3 ROUTING

BGP-3-ERR_PATH_ELEM

3 ROUTING

BGP-3-EXTCOMM

3 ROUTING

BGP-3-EXTCOMM_ADD

3 ROUTING

BGP-3-GWARRAY_INIT

3 ROUTING

BGP-3-GWCTX_CREATE

3 ROUTING

BGP-3-HA_INIT

3 ROUTING

BGP-3-IM_DMZLINK_BW

3 ROUTING

BGP-3-IMPORT_INIT

3 ROUTING

BGP-3-INIT_GET_VALUE

3 ROUTING

BGP-3-INITSYNC_PFX_MISMATCH

3 ROUTING

BGP-3-INSUFMEM

3 ROUTING

BGP-3-INTERNAL_ERROR

3 ROUTING

BGP-3-INVAL_REDUNDANCY_ROLE

3 ROUTING

BGP-3-IO_INIT

3 ROUTING

BGP-3-IO_INITSYNC_SESSION_FAILED

3 ROUTING

BGP-3-LABEL_INIT

3 ROUTING

BGP-3-LOCK_RECURSIVE

3 ROUTING

BGP-3-MALFORM_UPDATE

3 ROUTING

BGP-3-MAX_IMPORT

3 ROUTING

BGP-3-MAX_VALUE_EXCEEDED

3 ROUTING

BGP-3-MIB_INIT

3 ROUTING

BGP-3-NBR_NSR_DISABLED

3 ROUTING

BGP-3-NEGCOUNTER

3 ROUTING

BGP-3-NH_LOCK_RECURSIVE

3 ROUTING

BGP-3-NH_UNLOCK_ERR

3 ROUTING

BGP-3-NOMEM_RESET

3 ROUTING

BGP-3-NOMSGCHUNK

3 ROUTING

BGP-3-NPL_SEND_ERR

3 ROUTING

BGP-3-NPL_TIMEOUT

3 ROUTING

BGP-3-ORA_INSTBUILD

3 ROUTING

BGP-3-ORA_ORABUILD

3 ROUTING

BGP-3-ORA_RUN

3 ROUTING

BGP-3-OVERCOUNTER

3 ROUTING

BGP-3-RD_CREATE

3 ROUTING

BGP-3-RD_LOCK_RECURSIVE

3 ROUTING

BGP-3-RD_UNLOCK_ERR

3 ROUTING

BGP-3-REDIST_FAIL

3 ROUTING

BGP-3-RIB_CONN_FAIL

3 ROUTING

BGP-3-RIB_FAIL

3 ROUTING

BGP-3-RIB_INIT

3 ROUTING

BGP-3-RIB_INIT_FAIL

3 ROUTING

BGP-3-RIB_RETRY_FAIL

3 ROUTING

BGP-3-RIB_TABLE_FAIL

3 ROUTING

BGP-3-RPC_SET_ERROR

3 ROUTING

BGP-3-SCAN_INIT

3 ROUTING

BGP-3-SPKR_INIT

3 ROUTING

BGP-3-TABLE_CREATE

3 ROUTING

BGP-3-TBLATTR_VERSION

3 ROUTING

BGP-3-TIMER_PARENT_CHANGE

3 ROUTING

BGP-3-UNDERCOUNTER

3 ROUTING

BGP-3-UNKNOWN_MEMSTATE

3 ROUTING

BGP-3-UNLOCK_ERR

3 ROUTING

BGP-3-UPD_BUFFER_SMALL

3 ROUTING

BGP-3-VRF_CREATE

3 ROUTING

BGP-3-VRF_DELETE

3 ROUTING

BGP-4-ASPATH_TOO_LONG

4 ROUTING

BGP-4-ATTRKEY_INCONSISTENT

4 ROUTING

BGP-4-BFD_INVALID_NBR

4 ROUTING

BGP-4-BPM_NEG_NBR

4 ROUTING

BGP-4-CAP_4BYTEAS

4 ROUTING

BGP-4-CLIENT_ID_OVERWRITE

4 ROUTING

BGP-4-DESTROY_CHUNK

4 ROUTING

BGP-4-ENCODE_NET_OVERRUN

4 ROUTING

BGP-4-ERR_MALFORMED_ORF

4 ROUTING

BGP-4-FEEDBACK_OUT_OF_ORDER

4 ROUTING

BGP-4-FEEDBACK_OUTSIDE_RANGE

4 ROUTING

BGP-4-INCONSISTENT

4 ROUTING

BGP-4-INCONSISTENT_ASPATHMERGE

4 ROUTING

BGP-4-INITSYNC_FAILED

4 ROUTING

BGP-4-L2VPN_DEL_ADD

4 ROUTING

BGP-4-L2VPN_RD_LOCAL_AND_REMOTE

4 ROUTING

BGP-4-L2VPN_READD

4 ROUTING

BGP-4-L2VPN_SIGNAL_MISMATCH

4 ROUTING

BGP-4-L2VPN_SIGNAL_OVERLAP

4 ROUTING

BGP-4-L2VPN_SIGNALLING_MISMATCH

4 ROUTING

BGP-4-LABEL_COLLISION

4 ROUTING

BGP-4-LABEL_INCONSISTENCY

4 ROUTING

BGP-4-LOCK_ORDER

4 ROUTING

BGP-4-LOCK_RELEASE

4 ROUTING

BGP-4-MASKLEN_TOO_LONG

4 ROUTING

BGP-4-MAXPFXEXCEED

4 ROUTING

BGP-4-MISSING_SUBGRP

4 ROUTING

BGP-4-NBR_DOUBLE_ADD_SCOPED_ILIST

4 ROUTING

BGP-4-NSR_UNRECOGNIZED_PATH_INFO

4 ROUTING

BGP-4-OVERSIZED_UPDATE

4 ROUTING

BGP-4-PATH_ELEM_LIMIT

4 ROUTING

BGP-4-POLICY_COMMUNITY_OVERFLOW

4 ROUTING

BGP-4-POLICY_EBGP

4 ROUTING

BGP-4-POLICY_IBGP

4 ROUTING

BGP-4-POLICY_NHOP_WRONGAFI

4 ROUTING

BGP-4-POTENTIAL_DEADLOCK

4 ROUTING

BGP-4-RIB_REG_FAIL

4 ROUTING

BGP-4-SAME_RD_SET

4 ROUTING

BGP-4-SLOW_FEEDBACK

4 ROUTING

BGP-4-SPKR_RUNNING

4 ROUTING

BGP-4-TABLE_DELINK

4 ROUTING

BGP-4-UNKNOWN_ACL

4 ROUTING

BGP-4-UPD_MSG_ALLOC_FAIL

4 ROUTING

BGP-4-WRITE_SOCKET

4 ROUTING

BGP-5-ADJCHANGE

5 ROUTING

BGP-5-ADJCHANGE_DETAIL

5 ROUTING

BGP-5-ALREADY_DONE

5 ROUTING

BGP-5-ASYNC_IPC_STATUS

5 ROUTING

BGP-5-BPM_ROUTER_ID

5 ROUTING

BGP-5-IO_INITSYNC_FAILED

5 ROUTING

BGP-5-LOWMEM_RESET

5 ROUTING

BGP-5-LOWMEM_SHUTDOWN

5 ROUTING

BGP-5-MAXPFX

5 ROUTING

BGP-5-NBR_NSR_DISABLED_STANDBY

5 ROUTING

BGP-5-NSR_STATE_CHANGE

5 ROUTING

BGP-5-POLICY_RESET

5 ROUTING

BGP-5-RCVD_NOTIF_BADHOLDTIME

5 ROUTING

BGP-5-ROUTER_ID_CONFLICT

5 ROUTING

BGP-5-ROUTER_ID_CONFLICT2

5 ROUTING

BGP-5-RPKI_ADJCHANGE

5 ROUTING

BGP-5-SENT_NOTIF_BADHOLDTIME

5 ROUTING

BGP-5TBLATTR_UNLOCK_MISMATCH_TBLCTX

5 ROUTING

BGP-5-TUN_NULL_IFHANDLE

5 ROUTING

BGP-5-TUN_NULL_IFHANDLE2

5 ROUTING

BGP-5-UPDATE_FILTERED

5 ROUTING

BGP-6-NBR_NOPOLICY

6 ROUTING

BGP-6-NSR_RESTART

6 ROUTING

BGP-6-TRIGGER_SO

6 ROUTING

BGP-6-UPD_FILTER_MSG_BUFFERS_RESIZE

6 ROUTING

BGP-6-UPD_GEN_RECOVERY

6 ROUTING

BGP-6-UPD_GEN_THROTTLE

6 ROUTING

BGP-6-UPD_LIMIT_ACCOUNTING

6 ROUTING

BGP-6-WARNING_WRAPPER

6 ROUTING

BGP-7-BPM_CHKPT

7 ROUTING

BGP-7-RIB_TABLE_INFO
BGP-7-TREE_OP_ERR

7 ROUTING
7 ROUTING

C12000_IPV4_MRIB-3-INIT_ERROR
C12K_MCAST_GTRIE-3-ERROR
C12K_MCAST_GTRIE-3-INIT_ERR
C12K_MCAST_GTRIE-7-DEV_MSG

3 ROUTING
3 ROUTING
3 ROUTING
7 ROUTING

C12K_MCAST_MDT_EA-3-CONN_ERR

3 ROUTING

C12K_MCAST_MDT_EA-3-THREAD_ERR

3 ROUTING

C12K_MCAST_MDT_EA-7-CHINOOK_DEV

7 ROUTING

C12K_MCAST-2-FRAG_DROP

2 ROUTING

C12K_MCAST-3-CLEANUP_WARN

3 ROUTING

C12K_MCAST-3-IMC_ERR

3 ROUTING

C12K_MCAST-3-INIT_ERR

3 ROUTING

C12K_MCAST-3-INIT_WARN

3 ROUTING

C12K_MCAST-4-ANOMALY

4 ROUTING

CLNS-2-LC_INPUT

2 ROUTING

CLNS-3-ASYNC_ATTACH

3 ROUTING

CLNS-3-BUNDLE_FSV_REGISTER_FAIL

3 ROUTING

CLNS-3-CONFIG_INIT

3 ROUTING

CLNS-3-CONN_OPEN

3 ROUTING

CLNS-3-DEBUG_RETRIES_EXCEEDED

3 ROUTING

CLNS-3-DROP_PKT

3 ROUTING

CLNS-3-EDM_CLIENT

3 ROUTING

CLNS-3-EDM_ENCODE_FAILED

3 ROUTING

CLNS-3-EDM_INIT

3 ROUTING

CLNS-3-ERROR_INIT

3 ROUTING

CLNS-3-ETHERENCAP

3 ROUTING

CLNS-3-EVENT_CONN_CREATE_FAIL

3 ROUTING

CLNS-3-EVENT_CONN_NOTIFY_FAIL

3 ROUTING

CLNS-3-EVM_INIT

3 ROUTING

CLNS-3-GET_TRAFFIC

3 ROUTING

CLNS-3-HSSD_REGISTER_FAIL

3 ROUTING

CLNS-3-INTERFACE

3 ROUTING

CLNS-3-INTERFACE_DATA

3 ROUTING

CLNS-3-LPTS_ADD_BINDING

3 ROUTING

CLNS-3-LPTS_DELETE_BINDING

3 ROUTING

CLNS-3-LPTS_SETOPT

3 ROUTING

CLNS-3-MEDIA_REGISTER

3 ROUTING

CLNS-3-NETIO_ENCAP_CALLBACK

3 ROUTING

CLNS-3-NETIO_SET_MAPPING

3 ROUTING

CLNS-3-PAK

3 ROUTING

CLNS-3-SOCK_INIT

3 ROUTING

CLNS-3-SOCK_SET_NAME

3 ROUTING

CLNS-3-SOCKET_PARSE_PATH

3 ROUTING

CLNS-3-SOCKET_RESMGR_ATTACH

3 ROUTING

CLNS-3-STATSD_INIT

3 ROUTING

CLNS-3-STATSD_REGISTER

3 ROUTING

CLNS-3-THREAD_CREATE

3 ROUTING

CLNS-3-TIMESTAMP

3 ROUTING

CLNS-4-BASE_CAPS_LU_FAIL

4 ROUTING

CLNS-4-CONN_SETRETRY

4 ROUTING

CLNS-4-DEBUG_REGISTER_FAIL

4 ROUTING

CLNS-4-IDB_LOOKUP_DROP_PKT

4 ROUTING

CLNS-4-IM_SIGEVENT_FAIL

4 ROUTING

CLNS-4-NETIO_OUTPUT_FAIL

4 ROUTING

CLNS-4-PAK_FROM_ISIS_FAIL

4 ROUTING

CLNS-4-PAK_FROM_NETIO_FAIL

4 ROUTING

CLNS-4-SEND_HELLO_PDU_TO_ISIS_FAIL

4 ROUTING

CLNS-4-SEND_PDU_TO_ISIS_FAIL

4 ROUTING

CLNS-4-TRACE_INIT_FAIL

4 ROUTING

CLNS-4-UNKNOWN_MEDIA

4 ROUTING

CLNS-7-CAPS_ADD_FAIL

7 ROUTING

CLNS-7-CONN_PAK_AREA_FAIL

7 ROUTING

CLNS-7-DEBUG_THREAD_CREATE

7 ROUTING

CLNS-7-L2_HASH

7 ROUTING

DAD-3-EVM_ASYNC_ATTACH_FAIL

3 ROUTING

DAD-3-SETUP

3 ROUTING

DAD-3-SYSDB_BIND_FAIL

3 ROUTING

DAD-3-SYSDB_DELETE_FAIL

3 ROUTING

DAD-3-SYSDB_SET_FAIL

3 ROUTING

DAD-3-SYSMGR_PROC_AVAILABLE_FAIL

3 ROUTING

DAD-3-SYSMGR_PROC_CLEANUP_FAIL

3 ROUTING

DAD-3-SYSMGR_PROC_READY_FAIL

3 ROUTING

EC_TRACE-3-GEN_ERR

3 ROUTING

EIGRP_POLICY-3-ORA_INSTBUILD

3 ROUTING

EIGRP_POLICY-3-ORA_ORABUILD

3 ROUTING

EIGRP_POLICY-3-ORA_RUN

3 ROUTING

EIGRP-2-ERR_MEM_ALLOC

2 ROUTING

EIGRP-3-ANCHORCOUNT

3 ROUTING

EIGRP-3-BADCOUNT

3 ROUTING

EIGRP-3-ERR_EVM_CRE_FAIL

3 ROUTING

EIGRP-3-ERR_NO_ENCODER_DECODER

3 ROUTING

EIGRP-3-ERR_PROC_READY

3 ROUTING

EIGRP-3-ERR_SYSDB_APPLY_BATCH

3 ROUTING

EIGRP-3-ERR_SYSDB_CONNECT

3 ROUTING

EIGRP-3-ERR_SYSDB_REG_VERIFY

3 ROUTING

EIGRP-3-ERR_VRFN_FNS_INIT

3 ROUTING

EIGRP-3-EVENT_ERR

3 ROUTING

EIGRP-3-INTERNAL

3 ROUTING

EIGRP-3-MULTIFLOW

3 ROUTING

EIGRP-3-NO_REDISTMETRIC

3 ROUTING

EIGRP-3-NOBUFFER

3 ROUTING

EIGRP-3-PAK_WRITE

3 ROUTING

EIGRP-3-PEERSEXIST

3 ROUTING

EIGRP-3-PFXLIMIT

3 ROUTING

EIGRP-3-RDBLEFT

3 ROUTING

EIGRP-3-REFCOUNT

3 ROUTING

EIGRP-3-SIA

3 ROUTING

EIGRP-3-UNKTIMER

3 ROUTING

EIGRP-4-CERR_REG_FAIL

4 ROUTING

EIGRP-4-DBG_REGISTER_FAILED

4 ROUTING

EIGRP-4-ERR_SOCKET

4 ROUTING

EIGRP-4-ERR_SYSDB_DISCONNECT

4 ROUTING

EIGRP-4-ISSU_SUPPORT

4 ROUTING

EIGRP-4-PFXLIMITTHR

4 ROUTING

EIGRP-4-WARNING

4 ROUTING

EIGRP-5-NBRCHANGE

5 ROUTING

EIGRP-6-EVENT

6 ROUTING

EIGRP-6-INSTANCE_ASN_VIRTUAL_NAME

6 ROUTING

EIGRP-6-PAK_SEND

6 ROUTING

ENXR_MRIB-3-IFH_FAIL

3 ROUTING

ENXR_MRIB-3-INIT_FAIL

3 ROUTING

EVENT-3-ERR_MEM_ALLOC

3 ROUTING

FIB_ForUs-3-LIB_DEBUG_INIT

3 ROUTING

FIB-1-FIBALLOC

1 ROUTING

FIB-1-FIBTBLINIT

1 ROUTING

FIB-2-BGP_ATTR_INSERT_DROP

2 ROUTING

FIB-2-IFH_RECYCLE_CLEANUP_EXT_FAIL

2 ROUTING

FIB-2-INIT

2 ROUTING

FIB-2-INVALID_MSG

2 ROUTING

FIB-2-NOMEM_ROUTEDROP_ADDMODIFY

2 ROUTING

FIB-2-NOMEM_ROUTEDROP_DEL

2 ROUTING

FIB-2-NOMEMINFO_ROUTEDROP

2 ROUTING

FIB-2-NOMEMINFO_SHMERR

2 ROUTING

FIB-2-OOR

2 ROUTING

FIB-2-OOR_TBL

2 ROUTING

FIB-2-PROTO_INIT

2 ROUTING

FIB-2-ROUTEDROP_UPD

2 ROUTING

FIB-2-STATE

2 ROUTING

FIB-2-THREAD_INIT

2 ROUTING

FIB-3-ADD

3 ROUTING

FIB-3-ADJ_INIT

3 ROUTING

FIB-3-ASSERT

3 ROUTING

FIB-3-ASSERT_RL

3 ROUTING

FIB-3-ATTRIBUTE

3 ROUTING

FIB-3-BCDL

3 ROUTING

FIB-3-BCDL

3 ROUTING

FIB-3-CFGREG

3 ROUTING

FIB-3-CLIENT

3 ROUTING

FIB-3-CLIENT_ERROR

3 ROUTING

FIB-3-DEFAULT_ROUTE_CREATE_FAIL

3 ROUTING

FIB-3-DELETE

3 ROUTING

FIB-3-DUMMY_ZERO_ERR

3 ROUTING

FIB-3-DUMMY_ZERO_REMOVE

3 ROUTING

FIB-3-FIBGTRIEINIT

3 ROUTING

FIB-3-GEN_ERR

3 ROUTING

FIB-3-GTRIE

3 ROUTING

FIB-3-GTRIE_DEL

3 ROUTING

FIB-3-IDB

3 ROUTING

FIB-3-INIT_GR_EXIT_TOUT

3 ROUTING

FIB-3-INTERNAL_ERR

3 ROUTING

FIB-3-INVALID_BGP_PATH_FLAGS

3 ROUTING

FIB-3-LEAF_DEPEND_CLEANUP_ERR

3 ROUTING

FIB-3-LISP_EID_TBL

3 ROUTING

FIB-3-LISP_IID_MAPPING

3 ROUTING

FIB-3-LISP_RLOC_TBL

3 ROUTING

FIB-3-MALLOC_FAILED

3 ROUTING

FIB-3-NOMEM

3 ROUTING

FIB-3-NOTABLE

3 ROUTING

FIB-3-PD_FAIL

3 ROUTING

FIB-3-PFI_FIB_IFTYPE_MISMATCH

3 ROUTING

FIB-3-PFI_IFINFO

3 ROUTING

FIB-3-PLATF_UPD_FAIL

3 ROUTING

FIB-3-RCC

3 ROUTING

FIB-3-RCC_NO_TABLE

3 ROUTING

FIB-3-RCC_TABLE

3 ROUTING

FIB-3-RECURSIVE_LOOP

3 ROUTING

FIB-3-RETRY

3 ROUTING

FIB-3-ROUTE_GEN

3 ROUTING

FIB-3-RPCINIT

3 ROUTING

FIB-3-SERVER

3 ROUTING

FIB-3-SERVER_CERR

3 ROUTING

FIB-3-SHM

3 ROUTING

FIB-3-SHMEM

3 ROUTING

FIB-3-TABLE

3 ROUTING

FIB-3-THREAD

3 ROUTING

FIB-3-TIMER

3 ROUTING

FIB-4-FIBIDB

4 ROUTING

FIB-4-FIBIDB_LOOKUP_FAIL

4 ROUTING

FIB-4-HA

4 ROUTING

FIB-4-IDB_PLATF_UPDATE_TOO_LONG

4 ROUTING

FIB-4-IM_CONN

4 ROUTING

FIB-4-IM_CONN

4 ROUTING

FIB-4-INIT

4 ROUTING

FIB-4-LCL_ATTRIB_ENTER_OOR

4 ROUTING

FIB-4-LTRACE_ERR

4 ROUTING

FIB-4-PFI_IFH_CONN

4 ROUTING

FIB-4-PFI_IFH_LOOKUP

4 ROUTING

FIB-4-PL_FRR_LOOKUP_CREATE_FAILED

4 ROUTING

FIB-4-PULSE_HNDLR

4 ROUTING

FIB-4-RADIXINIT

4 ROUTING

FIB-4-RSRC_LOW

4 ROUTING

FIB-4-WARNING

4 ROUTING

FIB-5-ROUTE_UPDATE_DROP

5 ROUTING

FIB-6-DEBUG_REG

6 ROUTING

FIB-6-DEPEND_UNBIND_FAILURE

6 ROUTING

FIB-6-HARD_RESET

6 ROUTING

FIB-6-LCL_ATTRIB_EXIT_OOR

6 ROUTING

FIB-6-RSRC_OK

6 ROUTING

FIB-6-SHMRESET_NON_RELOAD_SMU

6 ROUTING

FWD_HA-4-PROCESS_RESTART

4 ROUTING

HFR_IPV4_MRIB-3-CHKPT_ERR

3 ROUTING

HFR_IPV4_MRIB-3-FGID_ADD_ERR

3 ROUTING

HFR_IPV4_MRIB-3-FGID_ERR

3 ROUTING

HFR_IPV4_MRIB-3-FGID_REMOVE_ERR

3 ROUTING

HFR_IPV4_MRIB-3-FILE_OPEN_ERR

3 ROUTING

HFR_IPV4_MRIB-3-IFH_ERR

3 ROUTING

HFR_IPV4_MRIB-3-IM_NAME_ERR

3 ROUTING

HFR_IPV4_MRIB-3-INIT_ERR

3 ROUTING

HFR_IPV4_MRIB-3-INTERNAL_ERR

3 ROUTING

HFR_IPV4_MRIB-3-INVALID_FGID_ERR

3 ROUTING

HFR_IPV4_MRIB-3-MEM_ERR

3 ROUTING

HFR_IPV4_MRIB-3-PERF_ERR

3 ROUTING

IGMP_MTRACE-3-EVENT_ERROR

3 ROUTING

IGMP_MTRACE-3-INIT_ERROR

3 ROUTING

IGMP_MTRACE-3-MEMORY_ERROR

3 ROUTING

IGMP_MTRACE-3-MSG_ERROR

3 ROUTING

IGMP_MTRACE-3-SOCKET_ERROR

3 ROUTING

IGPTE_LIB-3-ERR_BAG_REGISTER

3 ROUTING

IGPTE_LIB-3-ERR_DBG_REGISTER

3 ROUTING

IGPTE_LIB-3-ERR_LTRACE_INIT

3 ROUTING

IGPTE_LIB-3-ERR_SYSDB_BIND

3 ROUTING

IGPTE_LIB-3-ERR_SYSDB_REG_NOTIFY

3 ROUTING

IGPTE_LIB-3-ERR_SYSDB_UNREG_NOTIFY

3 ROUTING

IGPTE_LIB-4-CLIENT_ERR_MEM_ALLOC

4 ROUTING

IGPTE_LIB-4-DATA_QUEUE_FULL

4 ROUTING

IGPTE_LIB-4-ERR_MEM_ALLOC

4 ROUTING

IGPTE_LIB-4-INVALID_TLV

4 ROUTING

IGPTE_LIB-4-SERVER_ERR_CLINFO_HOLD

4 ROUTING

IGPTE_LIB-4-SERVER_ERR_CLINFO_UNHOLD

4 ROUTING

IP_STATIC_BFD_SESSMGR-4UNSUPPORTED_INTERFACE

4 ROUTING

IP_STATIC-3-IDB_DELETE

3 ROUTING

IP_STATIC-3-INTERNAL

3 ROUTING

IP_STATIC-3-ITAL_EVENT

3 ROUTING

IP_STATIC-3-ITAL_INTERFACE_CREATE

3 ROUTING

IP_STATIC-3-ITAL_TDB_REGISTER_FAILED

3 ROUTING

IP_STATIC-3-NHDB_DELETE

3 ROUTING

IP_STATIC-3-OTDB_DELETE

3 ROUTING

IP_STATIC-3-PATH_BP_DELETE

3 ROUTING

IP_STATIC-3-RIB_BATCH

3 ROUTING

IP_STATIC-3-RIB_CLEAR_PREFIX

3 ROUTING

IP_STATIC-3-RIB_CLEAR_TABLE

3 ROUTING

IP_STATIC-3-RIB_CLEAR_UNKNOWN_PREFIX

3 ROUTING

IP_STATIC-3-RIB_CLEAR_UNKNOWN_TABLE

3 ROUTING

IP_STATIC-3-RIB_ECMP

3 ROUTING

IP_STATIC-3-RIB_FETCH

3 ROUTING

IP_STATIC-3-RIB_FULL

3 ROUTING

IP_STATIC-3-RIB_INTERFACE

3 ROUTING

IP_STATIC-3-RIB_NEXTHOP

3 ROUTING

IP_STATIC-3-RIB_NEXTHOP_REGISTER

3 ROUTING

IP_STATIC-3-RIB_NEXTHOP_UNREGISTER

3 ROUTING

IP_STATIC-3-RIB_OBJECT

3 ROUTING

IP_STATIC-3-RIB_TOO_MANY_PATHS

3 ROUTING

IP_STATIC-3-SHUTDOWN

3 ROUTING

IP_STATIC-3-TDB_DELETE

3 ROUTING

IP_STATIC-3-TDB_REGISTER_FAILED

3 ROUTING

IP_STATIC-3-UPDATE_COMPLETE

3 ROUTING

IP_STATIC-4CONFIG_NEXTHOP_ETHER_INTERFACE

4 ROUTING

IP_STATIC-6-CONFIG_MAXIMUM_CHANGE

6 ROUTING

IP_STATIC-6-NHDB_LOCAL

6 ROUTING

IP_STATIC-6-NHDB_OUT_OF_SUBNET

6 ROUTING

IP_STATIC-6-NHDB_WITHIN_SUBNET

6 ROUTING

IP_STATIC-7-ITAL_INTERFACE_EVENT

7 ROUTING

IPMC_GTRIE_DEBUG-3-ERR

3 ROUTING

IPMC_GTRIE_DEBUG-3-INIT_ERR

3 ROUTING

IPMC_GTRIE_DEBUG-6-TERM_ERR

6 ROUTING

IPMC_GTRIE_DEFAULT-2-FATAL

2 ROUTING

IPMC_GTRIE_DEFAULT-3-INIT_ERR

3 ROUTING

IPMC_GTRIE_DEFAULT-4-INIT_WARN

4 ROUTING

IPMC_GTRIE_DEFAULT-4-WARN

4 ROUTING

IPV4_ADJ-3-ADD_DB_MALLOC_FAIL

3 ROUTING

IPV4_ADJ-3-ENT_UPDATE

3 ROUTING

IPV4_ADJ-3-L2_LOADHASH_FAIL

3 ROUTING

IPV4_ADJ-3-NO_FIBIDB

3 ROUTING

IPV4_ADJ-4-ADD_DB

4 ROUTING

IPV4_ADJ-4-LARGE_MAC

4 ROUTING

IPV4_ADJ-6-DEBUG_REG

6 ROUTING

IPV4_ADJ-7-INV_MSG_CODE

7 ROUTING

IPV4_IGMP-3ACCOUNTING_RECORD_DROPPED

3 ROUTING

IPV4_IGMP-3-CHUNK_FAIL

3 ROUTING

IPV4_IGMP-3-CONTEXT_REG_ERR

3 ROUTING

IPV4_IGMP-3-EDM_INIT

3 ROUTING

IPV4_IGMP-3-GROUP_ADD_ERR

3 ROUTING

IPV4_IGMP-3-GROUP_ERR

3 ROUTING

IPV4_IGMP-3-GROUP_FIND_ERR

3 ROUTING

IPV4_IGMP-3-IDB_ADD_ERR

3 ROUTING

IPV4_IGMP-3-IDB_FREE_ERR

3 ROUTING

IPV4_IGMP-3-IDB_HANDLE_MISMATCH_ERR

3 ROUTING

IPV4_IGMP-3-IDB_INIT_ERR

3 ROUTING

IPV4_IGMP-3-IDB_PRESENT_ERR

3 ROUTING

IPV4_IGMP-3-IDB_STATE_MONITOR_ERR

3 ROUTING

IPV4_IGMP-3-IDB_VERIFY_ERR

3 ROUTING

IPV4_IGMP-3-IDB_VERIFY1_ERR

3 ROUTING

IPV4_IGMP-3-IM_BATCH_STATE_ERR

3 ROUTING

IPV4_IGMP-3-IM_BULK_ERR

3 ROUTING

IPV4_IGMP-3-JOIN_IN_SSM_RANGE

3 ROUTING

IPV4_IGMP-3-LTRACE_ERR

3 ROUTING

IPV4_IGMP-3-MRIB_CONN_ERR

3 ROUTING

IPV4_IGMP-3-NET_ERR

3 ROUTING

IPV4_IGMP-3-SOCK_ERR

3 ROUTING

IPV4_IGMP-3-SYSDB_BIND_ERR

3 ROUTING

IPV4_IGMP-3-SYSDB_BSCAN_ERR

3 ROUTING

IPV4_IGMP-3-SYSDB_INIT

3 ROUTING

IPV4_IGMP-3-SYSDB_REG_ERR

3 ROUTING

IPV4_IGMP-3-WDSYSMON_EVENT_ERROR

3 ROUTING

IPV4_IGMP-3WDSYSMON_REGISTER_ERROR

3 ROUTING

IPV4_IGMP-4-OOM_STATE_THROTTLE

4 ROUTING

IPV4_IGMP-4-OOM_STATE_UNTHROTTLE

4 ROUTING

IPV4_IGMP-4-OOR_WARN

4 ROUTING

IPV4_IGMP-6-ACCESS_GROUP_INFO

6 ROUTING

IPV4_IGMP-6-IPARMS_UPDATE_ERR

6 ROUTING

IPV4_MCAST_CHKPT-3-ERR

3 ROUTING

IPV4_MCAST_NETIO_DEBUG-3-INIT_ERR

3 ROUTING

IPV4_MCAST_NETIO_DEBUG-6-TERM_ERR

6 ROUTING

IPV4_MFWD_HFR-3-BAG_REGISTRY

3 ROUTING

IPV4_MFWD_HFR-3-CFG_NOTIF_SETUP

3 ROUTING

IPV4_MFWD_HFR-3-EDM_ACT_SETUP

3 ROUTING

IPV4_MFWD_HFR-3-EDM_OPER_SETUP

3 ROUTING

IPV4_MFWD_HFR-3-EDM_REGISTER

3 ROUTING

IPV4_MFWD_HFR-3-SYSDB_BIND

3 ROUTING

IPV4_MFWD_HFR-5-ERR_SYSDB_INIT

5 ROUTING

IPV4_MFWD_HFR-5-SYSDB_INIT

5 ROUTING

IPV4_MFWD_HFR-7-ERR_BAG_REGISTRY

7 ROUTING

IPV4_MFWD_HFR-7-ERR_EDM_REGISTER

7 ROUTING

IPV4_MFWD_HFR-7-ERR_GEN

7 ROUTING

IPV4_MFWD_VKG-3-INACTIVE_FLOW

3 ROUTING

IPV4_MFWD_VKG-5-ERR_SYSDB_INIT

5 ROUTING

IPV4_MFWD_VKG-5-ERR_SYSDB_INIT

5 ROUTING

IPV4_MFWD_VKG-7-ERR_BAG_REGISTRY

7 ROUTING

IPV4_MFWD_VKG-7-ERR_BAG_REGISTRY

7 ROUTING

IPV4_MFWD_VKG-7-ERR_EDM_REGISTER

7 ROUTING

IPV4_MFWD_VKG-7-ERR_EDM_REGISTER

7 ROUTING

IPV4_MFWD_VKG-7-ERR_GEN

7 ROUTING

IPV4_MFWD_VKG-7-ERR_GEN

7 ROUTING

IPV4_MFWD-3-ADJ_CREATE

3 ROUTING

IPV4_MFWD-3-BOUNDARY_FAIL

3 ROUTING

IPV4_MFWD-3-ERR

3 ROUTING

IPV4_MFWD-3-ERR_AIB_FINT

3 ROUTING

IPV4_MFWD-3-ERR_AIB_MAP

3 ROUTING

IPV4_MFWD-3-ERR_AIB_ZERO_ALL

3 ROUTING

IPV4_MFWD-3-ERR_DEBUG_INIT_EVENT

3 ROUTING

IPV4_MFWD-3-ERR_DEBUG_REG

3 ROUTING

IPV4_MFWD-3-ERR_EVM_ASYNC_ATTACH

3 ROUTING

IPV4_MFWD-3-ERR_EVM_CONN_CREATE

3 ROUTING

IPV4_MFWD-3-ERR_EVM_CONN_NOTIFY

3 ROUTING

IPV4_MFWD-3-ERR_EVM_CONN_OPEN

3 ROUTING

IPV4_MFWD-3-ERR_EVM_CONN_SETRETRY

3 ROUTING

IPV4_MFWD-3-ERR_EVM_CREATE

3 ROUTING

IPV4_MFWD-3-ERR_EVM_INIT_EVENT

3 ROUTING

IPV4_MFWD-3-ERR_EVM_TIMER_ATTACH

3 ROUTING

IPV4_MFWD-3-ERR_EVM_TIMER_LEAF_NEW

3 ROUTING

IPV4_MFWD-3-ERR_IDB_INIT

3 ROUTING

IPV4_MFWD-3-ERR_IFH

3 ROUTING

IPV4_MFWD-3-ERR_IFH_BIND

3 ROUTING

IPV4_MFWD-3-ERR_IFH_INIT

3 ROUTING

IPV4_MFWD-3-ERR_IFH_UNBIND

3 ROUTING

IPV4_MFWD-3-ERR_IM_CNTL_SVR_BIND

3 ROUTING

IPV4_MFWD-3ERR_IMC_CAPS_DATAPATH_CONTROL

3 ROUTING

IPV4_MFWD-3-ERR_MEM_ALLOC

3 ROUTING

IPV4_MFWD-3-ERR_MEM_ALLOC_ARM_IDB

3 ROUTING

IPV4_MFWD-3-ERR_MLIB_INIT

3 ROUTING

IPV4_MFWD-3-ERR_MRIB_INIT

3 ROUTING

IPV4_MFWD-3-ERR_NSF_INIT

3 ROUTING

IPV4_MFWD-3-ERR_PAK_CLIENT_CONN

3 ROUTING

IPV4_MFWD-3-ERR_SHMWIN

3 ROUTING

IPV4_MFWD-3-ERR_SYSDB_BAG_DECODE

3 ROUTING

IPV4_MFWD-3ERR_SYSDB_BAG_FREE_INDIRECTIONS

3 ROUTING

IPV4_MFWD-3-ERR_SYSDB_BAG_REG

3 ROUTING

IPV4_MFWD-3-ERR_SYSDB_BSCAN

3 ROUTING

IPV4_MFWD-3-ERR_SYSDB_DATALIST_FREE

3 ROUTING

IPV4_MFWD-3-ERR_SYSDB_DATALIST_NEXT

3 ROUTING

IPV4_MFWD-3-ERR_SYSDB_EDM_FNS_INIT

3 ROUTING

IPV4_MFWD-3-ERR_SYSDB_EDM_REG

3 ROUTING

IPV4_MFWD-3-ERR_SYSDB_REG_NOTIFY

3 ROUTING

IPV4_MFWD-3-ERR_SYSDB_REG_VERIFY

3 ROUTING

IPV4_MFWD-3-EXIT

3 ROUTING

IPV4_MFWD-3-GEN_ERR

3 ROUTING

IPV4_MFWD-3-GROUP_ERR

3 ROUTING

IPV4_MFWD-3-HA

3 ROUTING

IPV4_MFWD-3-IARM_ERR

3 ROUTING

IPV4_MFWD-3-IDB_FAIL

3 ROUTING

IPV4_MFWD-3-IM_LOOKUP_FAILED

3 ROUTING

IPV4_MFWD-3-INSTALL

3 ROUTING

IPV4_MFWD-3-LRD_ERR

3 ROUTING

IPV4_MFWD-3-MAX_CONN_RETRY

3 ROUTING

IPV4_MFWD-3-MAX_DISABLE_RETRY

3 ROUTING

IPV4_MFWD-3-MAX_ENABLE_RETRY

3 ROUTING

IPV4_MFWD-3-TABLE_OPERATION_FAIL

3 ROUTING

IPV4_MFWD-3TABLE_OPERATION_FAIL_GLACIAL

3 ROUTING

IPV4_MFWD-3TRANSACTION_PENDING_FLAG

3 ROUTING

IPV4_MFWD-3-TTL_CFG_FAIL

3 ROUTING

IPV4_MFWD-4-ADJ_CREATE_RETRY

4 ROUTING

IPV4_MFWD-4-CLEAN_ALL_FAIL

4 ROUTING

IPV4_MFWD-4-ERR_AIB_UPDATE

4 ROUTING

IPV4_MFWD-4-ERR_LTRACE_INIT

4 ROUTING

IPV4_MFWD-4-ERR_MRIB_INIT_RETRY

4 ROUTING

IPV4_MFWD-4ERR_MRIB_SEND_RESPONSE_RETRY

4 ROUTING

IPV4_MFWD-4-ERR_RETRY_INIT

4 ROUTING

IPV4_MFWD-4-ERR_RETRY_TRANS_INIT

4 ROUTING

IPV4_MFWD-4-ERR_RETRY_TRANS_REG

4 ROUTING

IPV4_MFWD-4ERR_RETRY_TRANS_SPEC_INIT

4 ROUTING

IPV4_MFWD-4-FROM_MRIB_UPDATE

4 ROUTING

IPV4_MFWD-4FROM_MRIB_UPDATE_GLACIAL

4 ROUTING

IPV4_MFWD-4-SVD_ERR

4 ROUTING

IPV4_MFWD-4-TERMINATE

4 ROUTING

IPV4_MFWD-4-TO_MRIB_MDT_UPDATE

4 ROUTING

IPV4_MFWD-4-TO_MRIB_MOFRR_UPDATE

4 ROUTING

IPV4_MFWD-4-TO_MRIB_UPDATE

4 ROUTING

IPV4_MFWD-5-CLEAN_ALL

5 ROUTING

IPV4_MFWD-5-ERR_SHMWIN_MUTEX

5 ROUTING

IPV4_MFWD-5-IP_ADDR_RETRY

5 ROUTING

IPV4_MFWD-5-MCAST_DISABLED

5 ROUTING

IPV4_MFWD-5-MFIB_RESET

5 ROUTING

IPV4_MFWD-5-MRIB_UPDATE_RETRY

5 ROUTING

IPV4_MFWD-5-PER_PREFIX

5 ROUTING

IPV4_MFWD-5-PER_PREFIX_GLACIAL

5 ROUTING

IPV4_MFWD-5-ROUTE_UPDATE_FAIL

5 ROUTING

IPV4_MFWD-5-TABLE_PER_PREFIX

5 ROUTING

IPV4_MFWD-5-TABLE_PER_PREFIX_GLACIAL

5 ROUTING

IPV4_MFWD-5-TABLE_ROUTE_RATE

5 ROUTING

IPV4_MFWD-5-TABLE_ROUTE_RATE_GLACIAL

5 ROUTING

IPV4_MFWD-5-UPGRADE_AFFECT_TRAFFIC

5 ROUTING

IPV4_MLIB_DEBUG-3-ERR

3 ROUTING

IPV4_MLIB_DEBUG-3-INIT_ERR

3 ROUTING

IPV4_MLIB_DEBUG-6-TERM_ERR

6 ROUTING

IPV4_MLIB-1-OOR_ROUTES_YELLOW

1 ROUTING

IPV4_MLIB-2-OOR_ROUTES_GREEN

2 ROUTING

IPV4_MLIB-2-OOR_ROUTES_RED

2 ROUTING

IPV4_MLIB-3-DATAPATH_CONTROL

3 ROUTING

IPV4_MLIB-3-DELETE_FAIL

3 ROUTING

IPV4_MLIB-3-EVENT_CONN_MGR

3 ROUTING

IPV4_MLIB-3-EVENT_MGR

3 ROUTING

IPV4_MLIB-3-SHMWIN_ERR

3 ROUTING

IPV4_MLIB-3-STATE_ERR

3 ROUTING

IPV4_MLIB-5-PER_PREFIX

5 ROUTING

IPV4_MLIB-5-PER_PREFIX_GLACIAL

5 ROUTING

IPV4_MLIB-5-SVD

5 ROUTING

IPV4_MLIB-5-TABLE_PER_PREFIX

5 ROUTING

IPV4_PIM-3-ACL_GETLIST_ERR

3 ROUTING

IPV4_PIM-3-ACL_REG_ERR

3 ROUTING

IPV4_PIM-3-ACTIVE_GRANGE_ERR

3 ROUTING

IPV4_PIM-3-AIPC_ERROR

3 ROUTING

IPV4_PIM-3-BGP_ENS_ERROR

3 ROUTING

IPV4_PIM-3-CONTEXT_CREATE

3 ROUTING

IPV4_PIM-3-CONTEXT_INIT

3 ROUTING

IPV4_PIM-3-CONTEXT_REGISTRATION

3 ROUTING

IPV4_PIM-3-ERR_CHKPT_REGISTER

3 ROUTING

IPV4_PIM-3-ERR_CHUNK_CREATE

3 ROUTING

IPV4_PIM-3-ERR_DEBUG_REGISTER

3 ROUTING

IPV4_PIM-3-ERR_EVM_ASYNC_ATTACH

3 ROUTING

IPV4_PIM-3-ERR_EVM_ASYNC_SEND

3 ROUTING

IPV4_PIM-3-ERR_EVM_CONN_CREATE

3 ROUTING

IPV4_PIM-3ERR_EVM_CONN_EVM_HANDLER

3 ROUTING

IPV4_PIM-3-ERR_EVM_CONN_NOTIFY

3 ROUTING

IPV4_PIM-3-ERR_EVM_CONN_OPEN

3 ROUTING

IPV4_PIM-3-ERR_EVM_CONN_SETRETRY

3 ROUTING

IPV4_PIM-3-ERR_EVM_EVENT_INIT

3 ROUTING

IPV4_PIM-3-ERR_EVM_MESSAGE_ATTACH

3 ROUTING

IPV4_PIM-3-ERR_IM_BATCH_STATE

3 ROUTING

IPV4_PIM-3-ERR_IM_BULK

3 ROUTING

IPV4_PIM-3-ERR_IM_CAPS_ADD

3 ROUTING

IPV4_PIM-3ERR_IM_CAPS_DATAPATH_CONTROL

3 ROUTING

IPV4_PIM-3-ERR_IM_INTERFACE_CREATE

3 ROUTING

IPV4_PIM-3-ERR_IM_INTERFACE_DELETE

3 ROUTING

IPV4_PIM-3-ERR_INIT

3 ROUTING

IPV4_PIM-3-ERR_LIST

3 ROUTING

IPV4_PIM-3-ERR_LTRACE_INIT

3 ROUTING

IPV4_PIM-3-ERR_MAX_PATH

3 ROUTING

IPV4_PIM-3-ERR_MEM_ALLOC

3 ROUTING

IPV4_PIM-3-ERR_MGD_TIMER_GET_ROOT

3 ROUTING

IPV4_PIM-3-ERR_MGD_TIMER_NEW

3 ROUTING

IPV4_PIM-3-ERR_MRIB_BIND

3 ROUTING

IPV4_PIM-3-ERR_MRIB_CONN

3 ROUTING

IPV4_PIM-3-ERR_MRIB_UNBIND

3 ROUTING

IPV4_PIM-3-ERR_NSF_INIT

3 ROUTING

IPV4_PIM-3-ERR_PAK_CLIENT_CONN

3 ROUTING

IPV4_PIM-3-ERR_SYSDB_BAG_DECODE

3 ROUTING

IPV4_PIM-3ERR_SYSDB_BAG_FREE_INDIRECTIONS

3 ROUTING

IPV4_PIM-3-ERR_SYSDB_DATALIST_FREE

3 ROUTING

IPV4_PIM-3-ERR_SYSDB_DATALIST_NEXT

3 ROUTING

IPV4_PIM-3-ERR_SYSMGR_READY

3 ROUTING

IPV4_PIM-3-ERR_SYSMGR_REGISTER

3 ROUTING

IPV4_PIM-3-ERR_WDSYSMON_EVENT

3 ROUTING

IPV4_PIM-3-ERR_WDSYSMON_REGISTER

3 ROUTING

IPV4_PIM-3-GEN_ERR

3 ROUTING

IPV4_PIM-3-IDB_HANDLE_MISMATCH_ERR

3 ROUTING

IPV4_PIM-3-IDB_INIT

3 ROUTING

IPV4_PIM-3-IDB_VRF_BIND

3 ROUTING

IPV4_PIM-3-INTF_FWD_REF_ERR

3 ROUTING

IPV4_PIM-3-INVALID_MHOST_DEFAULT

3 ROUTING

IPV4_PIM-3-MDR_INIT

3 ROUTING

IPV4_PIM-3-MULTICAST_IGP_MTR

3 ROUTING

IPV4_PIM-3-MULTICAST_INTACT

3 ROUTING

IPV4_PIM-3-NET_ERR

3 ROUTING

IPV4_PIM-3-OOR_COUNTER_ERR

3 ROUTING

IPV4_PIM-3-OOR_GLOBAL_BSR_CRP_LIMIT

3 ROUTING

IPV4_PIM-3OOR_GLOBAL_BSR_GRANGE_LIMIT

3 ROUTING

IPV4_PIM-3-OOR_GROUP_RANGE_LIMIT

3 ROUTING

IPV4_PIM-3-OOR_VRF_BSR_CRP_LIMIT

3 ROUTING

IPV4_PIM-3-OOR_VRF_BSR_GRANGE_LIMIT

3 ROUTING

IPV4_PIM-3-PROTOCOL_ERR

3 ROUTING

IPV4_PIM-3-RP_INIT

3 ROUTING

IPV4_PIM-3-SRC_UPDATE_ERR

3 ROUTING

IPV4_PIM-3v6_DATA_MDT_INVALID_GRANGE

3 ROUTING

IPV4_PIM-3-v6_DATA_MDT_INVALID_VRF

3 ROUTING

IPV4_PIM-3-v6_DATA_MDT_NO_CORE

3 ROUTING

IPV4_PIM-3-v6_DATA_MDT_NO_MEM

3 ROUTING

IPV4_PIM-4-CFG_WARNING

4 ROUTING

IPV4_PIM-4-ITAL_CREATE_WARN

4 ROUTING

IPV4_PIM-4-MIB_GROUP_TREE_ERR

4 ROUTING

IPV4_PIM-4-MYADDR_DB_ERR

4 ROUTING

IPV4_PIM-4-OOM_STATE_THROTTLE

4 ROUTING

IPV4_PIM-4-OOM_STATE_UNTHROTTLE

4 ROUTING

IPV4_PIM-4OOR_GLOBAL_BSR_CRP_THRESHOLD_WARN

4 ROUTING

IPV4_PIM-4OOR_GLOBAL_BSR_GRANGE_THRESHOLD_
WARN

4 ROUTING

IPV4_PIM-4-OOR_GROUP_RANGE_OK

4 ROUTING

IPV4_PIM-4OOR_GROUP_RANGE_THRESHOLD

4 ROUTING

IPV4_PIM-4-OOR_REGISTER_OK

4 ROUTING

IPV4_PIM-4OOR_REGISTER_THRESHOLD_WARN

4 ROUTING

IPV4_PIM-4-OOR_REGISTER_WARN

4 ROUTING

IPV4_PIM-4-OOR_ROUTES_OK

4 ROUTING

IPV4_PIM-4OOR_ROUTES_THRESHOLD_WARN

4 ROUTING

IPV4_PIM-4-OOR_ROUTES_WARN

4 ROUTING

IPV4_PIM-4OOR_VRF_BSR_CRP_THRESHOLD_WARN

4 ROUTING

IPV4_PIM-4OOR_VRF_BSR_GRANGE_THRESHOLD_WAR
N

4 ROUTING

IPV4_PIM-4-RANGE_INIT

4 ROUTING

IPV4_PIM-4-RPF_REDIRECT_DROP

4 ROUTING

IPV4_PIM-4-RPF_REDIRECT_HAS_BW

4 ROUTING

IPV4_PIM-4-RPF_REDIRECT_NO_BW

4 ROUTING

IPV4_PIM-4-RPF_REDIRECT_NSF_DUP

4 ROUTING

IPV4_PIM-4-RPF_REDIRECT_PREEMPTED

4 ROUTING

IPV4_PIM-4-RPF_REDIRECT_SN_NO_BW

4 ROUTING

IPV4_PIM-4-RPF_REDIRECT_SN_THRESHOLD

4 ROUTING

IPV4_PIM-4-RPF_REDIRECT_THRESHOLD

4 ROUTING

IPV4_PIM-4-RPF_REDIRECT_UP_REJECTED

4 ROUTING

IPV4_PIM-4-TE_MDT_MISMATCH_WARN

4 ROUTING

IPV4_PIM-5-INTCHG

5 ROUTING

IPV4_PIM-5-INVALID_JP

5 ROUTING

IPV4_PIM-5-INVALID_REGISTER

5 ROUTING

IPV4_PIM-5-NBRCHG

5 ROUTING

IPV4_PIM-5-RP_MAPPING_CHG

5 ROUTING

IPV4MC_STATIC-7-ERR_CERR_V

7 ROUTING

IPV4MC_STATIC-7-ERR_DEBUG_INIT

7 ROUTING

IPV4MC_STATIC-7-ERR_EVENT_INIT

7 ROUTING

IPV4MC_STATIC-7-ERR_EVM_CREATE

7 ROUTING

IPV4MC_STATIC-7-ERR_IDB_INIT

7 ROUTING

IPV4MC_STATIC-7-ERR_INTF

7 ROUTING

IPV4MC_STATIC-7-ERR_MRIB

7 ROUTING

IPV4MC_STATIC-7-ERR_ROUTE

7 ROUTING

IPV4MC_STATIC-7-ERR_TIMER_ASYNC_CODE

7 ROUTING

IPV4MC_STATIC-7-ERR_TIMER_CREATE_LEAF

7 ROUTING

IPV4MC_STATIC-7-ERR_TIMER_INIT

7 ROUTING

IPV4MC_STATIC-7-ERR_TOPOLOGY_INIT

7 ROUTING

IPV6_FIB-2-RIBREJECT

2 ROUTING

IPV6_FIB-7-PFIFAIL

7 ROUTING

ISIS_IP_ORA-3-INSTBUILD

3 ROUTING

ISIS-2-DUPSYSTEM

2 ROUTING

ISIS-3-BFD_SESSION_CREATE_FAIL

3 ROUTING

ISIS-3-DBG_INIT_FAILED

3 ROUTING

ISIS-3-ERR_ATOMIC_RING_OP

3 ROUTING

ISIS-3-ERR_BAD_SOCKET_ADDR_LENGTH

3 ROUTING

ISIS-3-ERR_BAG_ENCODE

3 ROUTING

ISIS-3-ERR_BAG_REGISTER

3 ROUTING

ISIS-3-ERR_CLOCKTIME

3 ROUTING

ISIS-3-ERR_CONFIG_TO_TE

3 ROUTING

ISIS-3-ERR_DLIST_ADD

3 ROUTING

ISIS-3-ERR_DLIST_CREATE

3 ROUTING

ISIS-3-ERR_DLIST_SET_MORE_FLAG

3 ROUTING

ISIS-3-ERR_EDM_FNS_INIT

3 ROUTING

ISIS-3-ERR_EDM_REGISTER

3 ROUTING

ISIS-3-ERR_GET_JOB_ID

3 ROUTING

ISIS-3-ERR_GET_NODE_STATE

3 ROUTING

ISIS-3-ERR_GET_TUPLE

3 ROUTING

ISIS-3-ERR_IFINDEX

3 ROUTING

ISIS-3-ERR_LIST_ADD

3 ROUTING

ISIS-3-ERR_LIST_CREATE

3 ROUTING

ISIS-3-ERR_LOCKING_FAIL

3 ROUTING

ISIS-3-ERR_LTRACE_BUFFER

3 ROUTING

ISIS-3-ERR_MEMPOOL_CREATE

3 ROUTING

ISIS-3-ERR_NODE_STATE_CHANGE

3 ROUTING

ISIS-3-ERR_PAK_CLIENT_ACCESS

3 ROUTING

ISIS-3-ERR_PAK_CLIENT_CONN

3 ROUTING

ISIS-3-ERR_PAK_CLIENT_GET_BUFFER

3 ROUTING

ISIS-3-ERR_PROC_AVAILABLE

3 ROUTING

ISIS-3-ERR_PROC_READY

3 ROUTING

ISIS-3-ERR_RECV_BAD_TE_MSG

3 ROUTING

ISIS-3-ERR_RECV_PAK

3 ROUTING

ISIS-3-ERR_RIB_BATCH_BUFFER

3 ROUTING

ISIS-3-ERR_RIB_PATH

3 ROUTING

ISIS-3-ERR_SEND_PAK

3 ROUTING

ISIS-3-ERR_SYSDB_ACCESS

3 ROUTING

ISIS-3-ERR_SYSDB_APPLY_BATCH

3 ROUTING

ISIS-3-ERR_SYSDB_CONNECT

3 ROUTING

ISIS-3-ERR_SYSDB_DATALIST

3 ROUTING

ISIS-3-ERR_SYSDB_REG_NOTIFY

3 ROUTING

ISIS-3-ERR_SYSDB_REG_VERIFY

3 ROUTING

ISIS-3-ERR_SYSDB_STRING_CODING

3 ROUTING

ISIS-3-ERR_TAG_NAME

3 ROUTING

ISIS-3-ERR_THREAD_CREATE

3 ROUTING

ISIS-3-ERR_THREAD_KEY_CREATE

3 ROUTING

ISIS-3-ERR_THREAD_ONCE

3 ROUTING

ISIS-3-ERR_THREAD_SET_SPECIFIC

3 ROUTING

ISIS-3-ERR_VRFN_FNS_INIT

3 ROUTING

ISIS-3-EVENT_CONN_CREATE_FAIL

3 ROUTING

ISIS-3-EVQ_DEQUEUE_FAIL

3 ROUTING

ISIS-3-EVQ_ENQUEUE_FAIL

3 ROUTING

ISIS-3-EVQ_SIZE_FAIL

3 ROUTING

ISIS-3-IM_CB_REG_FAIL

3 ROUTING

ISIS-3-IM_CONN_TO_COID_FAIL

3 ROUTING

ISIS-3-INTF_SET_ADD_FAIL

3 ROUTING

ISIS-3-IPV6_LAS

3 ROUTING

ISIS-3-LKGP_ADD

3 ROUTING

ISIS-3-LKGP_VERIFY

3 ROUTING

ISIS-3-PDU_INSUFFICIENT_SPACE

3 ROUTING

ISIS-3-RSI_C_API_FAIL

3 ROUTING

ISIS-3-RSI_C_LIB_INIT

3 ROUTING

ISIS-3-SNMP_IDX_REL

3 ROUTING

ISIS-3-TIMESTAMP

3 ROUTING

ISIS-3-TRIGGER

3 ROUTING

ISIS-4-AREALOST

4 ROUTING

ISIS-4-BFD_BIND_FAIL

4 ROUTING

ISIS-4-BFD_CREATE_FAIL

4 ROUTING

ISIS-4-BFD_DELETE_FAIL

4 ROUTING

ISIS-4-BFD_DELETE_UNCONFIG_FAIL

4 ROUTING

ISIS-4-BFD_SESSION_NOT_FOUND

4 ROUTING

ISIS-4-CERR_REG_FAIL

4 ROUTING

ISIS-4-DBG_REGISTER_FAILED

4 ROUTING

ISIS-4-DUPLICATE_MT_CAPABILITY

4 ROUTING

ISIS-4-ERR_ACL

4 ROUTING

ISIS-4-ERR_ADVMASK

4 ROUTING

ISIS-4-ERR_BAD_CIRC_TYPE

4 ROUTING

ISIS-4-ERR_BAD_CIRC_TYPE

4 ROUTING

ISIS-4-ERR_BAD_HDR_LENGTH

4 ROUTING

ISIS-4-ERR_BAD_HDR_LENGTH

4 ROUTING

ISIS-4-ERR_BAD_ID_LENGTH

4 ROUTING

ISIS-4-ERR_BAD_ID_LENGTH

4 ROUTING

ISIS-4-ERR_BAD_MAX_AREA_ADDR

4 ROUTING

ISIS-4-ERR_BAD_MAX_AREA_ADDR

4 ROUTING

ISIS-4-ERR_BAD_PAK_LENGTH

4 ROUTING

ISIS-4-ERR_BAD_PDU_FORMAT

4 ROUTING

ISIS-4-ERR_BAD_PDU_FORMAT

4 ROUTING

ISIS-4-ERR_BAD_PDU_LENGTH

4 ROUTING

ISIS-4-ERR_BAD_PDU_LENGTH

4 ROUTING

ISIS-4-ERR_BAD_PDU_VERSION

4 ROUTING

ISIS-4-ERR_BAD_PDU_VERSION

4 ROUTING

ISIS-4-ERR_BAD_VERSION

4 ROUTING

ISIS-4-ERR_BAD_VERSION

4 ROUTING

ISIS-4-ERR_BGP_CONVERGE

4 ROUTING

ISIS-4-ERR_BGP_UNREG_NOTIFY

4 ROUTING

ISIS-4-ERR_EVM_ATT_FAIL

4 ROUTING

ISIS-4-ERR_EVM_CBACK_ATT_FAIL

4 ROUTING

ISIS-4-ERR_EVM_CRE_FAIL

4 ROUTING

ISIS-4-ERR_EVM_SEND_FAIL

4 ROUTING

ISIS-4-ERR_GET_RESPAWN_COUNT

4 ROUTING

ISIS-4-ERR_LSP_DB_CORRUPT

4 ROUTING

ISIS-4-ERR_LSP_DB_CORRUPT

4 ROUTING

ISIS-4-ERR_LSP_INPUT_Q_OVERFLOW

4 ROUTING

ISIS-4-ERR_MEMPOOL_NOMEM

4 ROUTING

ISIS-4-ERR_MIN_PDU_LENGTH

4 ROUTING

ISIS-4-ERR_MIN_PDU_LENGTH

4 ROUTING

ISIS-4-ERR_MIN_PKT_LENGTH

4 ROUTING

ISIS-4-ERR_MIN_PKT_LENGTH

4 ROUTING

ISIS-4-ERR_MSG_CHAN_GLOBAL

4 ROUTING

ISIS-4-ERR_MSG_GET_SCOID

4 ROUTING

ISIS-4-ERR_MSG_REPLY

4 ROUTING

ISIS-4-ERR_PCL

4 ROUTING

ISIS-4-ERR_REG_SHUTDOWN_NOTIFY

4 ROUTING

ISIS-4-ERR_RIB

4 ROUTING

ISIS-4-ERR_RIB_BATCH_SEND

4 ROUTING

ISIS-4-ERR_RIB_CONN_SETRETRY

4 ROUTING

ISIS-4-ERR_RIB_LIB

4 ROUTING

ISIS-4-ERR_RIB_NOTIFICATION

4 ROUTING

ISIS-4-ERR_RIB_PATH_NOMEM

4 ROUTING

ISIS-4-ERR_SHOW_PROTO_REG

4 ROUTING

ISIS-4-ERR_SYSDB_DISCONNECT

4 ROUTING

ISIS-4-ERR_SYSDB_UNREG_NOTIFY

4 ROUTING

ISIS-4-ERR_THREAD_DESTROY

4 ROUTING

ISIS-4-ERR_THREAD_SET_NAME

4 ROUTING

ISIS-4-ERR_WDSYSMON_MEM_STATE

4 ROUTING

ISIS-4-EVENT_BOOL_FAIL

4 ROUTING

ISIS-4-EVENT_CONN_ERROR_FAIL

4 ROUTING

ISIS-4-EVENT_CONN_EVM_HANDLER_FAIL

4 ROUTING

ISIS-4-EVENT_CONN_GET_FD_FAIL

4 ROUTING

ISIS-4-EVENT_CONN_NOTIFY_FAIL

4 ROUTING

ISIS-4-EVENT_CONN_OPEN_FAIL

4 ROUTING

ISIS-4-EVQ_CRE_FAIL

4 ROUTING

ISIS-4-EXTRA_AREA_ADDRESSES

4 ROUTING

ISIS-4-IDB_CHKPT_CLEANUP

4 ROUTING

ISIS-4-IIH_TOO_MANY_IF_ADDRESSES

4 ROUTING

ISIS-4-IM_ATTR_INIT

4 ROUTING

ISIS-4-IM_CAPS_UNKNOWN

4 ROUTING

ISIS-4-IM_CB_NAME_TRUNC

4 ROUTING

ISIS-4-INTF_ADDR_CHG_REG

4 ROUTING

ISIS-4-INTF_ATTR_FAIL

4 ROUTING

ISIS-4-INTF_CKTNUM_ALLOC_FAIL

4 ROUTING

ISIS-4-INTF_CLNS_CLIENT_INIT

4 ROUTING

ISIS-4-INTF_CLNS_LPTS_UPDATE

4 ROUTING

ISIS-4-INTF_CLNS_MAC_ADDR_NOTIFY

4 ROUTING

ISIS-4-INTF_CONFIG_ERROR

4 ROUTING

ISIS-4-INTF_FIND_FAIL

4 ROUTING

ISIS-4-INTF_FWS_INIT

4 ROUTING

ISIS-4-INTF_IM_REG_FAIL

4 ROUTING

ISIS-4-INTF_INACTIVE_AF

4 ROUTING

ISIS-4-INTF_IP_ARM_BATCH_UPDATE_FAIL

4 ROUTING

ISIS-4-INTF_LAS_FAIL

4 ROUTING

ISIS-4-INTF_MAC_SIZE_ERR

4 ROUTING

ISIS-4-INTF_MCAST_JOIN_FAIL

4 ROUTING

ISIS-4-INTF_MCAST_SIZE_ERR

4 ROUTING

ISIS-4-INTF_MTU_REDUCED

4 ROUTING

ISIS-4-INTF_MTU_TOO_SMALL

4 ROUTING

ISIS-4-INTF_NAME_FAIL

4 ROUTING

ISIS-4-INTF_NSF_MEDIA_MISMATCH

4 ROUTING

ISIS-4-INTF_PROTECT_INFRA_UPDATE

4 ROUTING

ISIS-4-INTF_RSI_SRLG_UPDATE

4 ROUTING

ISIS-4-INTF_STORE_FAIL

4 ROUTING

ISIS-4-INTF_UNKNOWN_MEDIA

4 ROUTING

ISIS-4-INVALID_LSP_LIFETIME

4 ROUTING

ISIS-4-INVALID_LSP_LIFETIME

4 ROUTING

ISIS-4-IP_ARM_ADDR_INFO_FAIL

4 ROUTING

ISIS-4-ITEMSIZE

4 ROUTING

ISIS-4-ITEMSIZE

4 ROUTING

ISIS-4-KEY_DEACTIVATE_FAIL

4 ROUTING

ISIS-4-LINK_TO_SELF

4 ROUTING

ISIS-4-LSPCKSUM

4 ROUTING

ISIS-4-LSPCKSUM

4 ROUTING

ISIS-4-LSPFULL

4 ROUTING

ISIS-4-LSPFULL

4 ROUTING

ISIS-4-LSPTOOBIG

4 ROUTING

ISIS-4-LSPTOOBIG

4 ROUTING

ISIS-4-MARTIAN

4 ROUTING

ISIS-4-MAX_REDIST_PREFIXES

4 ROUTING

ISIS-4-MEM_ALLOC_FAIL

4 ROUTING

ISIS-4-MEM_ALLOC_FAIL

4 ROUTING

ISIS-4-MGD_TIMER_FAIL

4 ROUTING

ISIS-4-NSF_CHKPT_ACCESS_FAIL

4 ROUTING

ISIS-4-NSF_CHKPT_INIT

4 ROUTING

ISIS-4-NSF_CHKPT_TABLE_FAIL

4 ROUTING

ISIS-4-NSF_CREATE_FAIL

4 ROUTING

ISIS-4-NSF_TE_TUNNEL_RESTORE_FAIL

4 ROUTING

ISIS-4-OSI_SOKT_FAIL

4 ROUTING

ISIS-4-P2P_CONFIG_MISMATCH

4 ROUTING

ISIS-4-REDIST_FAIL

4 ROUTING

ISIS-4-RSI_C_REGISTRATION_FAIL

4 ROUTING

ISIS-4-SAMESYSID_DIFFHOST

4 ROUTING

ISIS-4-SEQNUM_WRAP

4 ROUTING

ISIS-4-SEQNUM_WRAP

4 ROUTING

ISIS-4-SETSOCKOPT_FAIL

4 ROUTING

ISIS-4-SHOW_NOMEM

4 ROUTING

ISIS-4-SHUTDOWN

4 ROUTING

ISIS-4-SNPTOOBIG

4 ROUTING

ISIS-4-SNPTOOBIG

4 ROUTING

ISIS-4-THREAD_SPURIOUS_PULSE

4 ROUTING

ISIS-4-TIMESTAMP_FAIL

4 ROUTING

ISIS-4-UNKNOWN_ADDRESS_FAMILY

4 ROUTING

ISIS-4-WD_METRIC_NOT_CONF

4 ROUTING

ISIS-4-ZERO_COST_LINK

4 ROUTING

ISIS-4-ZEROHOLDTIME

4 ROUTING

ISIS-4-ZEROHOLDTIME

4 ROUTING

ISIS-5-ADJCHANGE

5 ROUTING

ISIS-5-AUTH_COMPUTE_FAILED

5 ROUTING

ISIS-5-AUTH_FAILURE_DROP

5 ROUTING

ISIS-5-AUTH_VERIFY_FAILED

5 ROUTING

ISIS-6-ADJNSF

6 ROUTING

ISIS-6-ATOMIC_RING_FULL

6 ROUTING

ISIS-6-DBG_UNKNOWN_TRACEPOINT_NAME

6 ROUTING

ISIS-6-ERR_DUPID

6 ROUTING

ISIS-6-ERR_DUPID

6 ROUTING

ISIS-6-EVENT_CONN_DESTROY_FAIL

6 ROUTING

ISIS-6-EVENT_ERR

6 ROUTING

ISIS-6-EVQ_DESTROY_FAIL

6 ROUTING

ISIS-6-FAIL_ADJADD

6 ROUTING

ISIS-6-FAIL_ADJADD

6 ROUTING

ISIS-6-IIH_IF_ADDRESS

6 ROUTING

ISIS-6-INFO_STARTUP_ABORTED

6 ROUTING

ISIS-6-INFO_STARTUP_FINISH

6 ROUTING

ISIS-6-INFO_STARTUP_FORCED_COLD

6 ROUTING

ISIS-6-INFO_STARTUP_START

6 ROUTING

ISIS-6-INTF_MAC_ADDR_CHG_INVALID

6 ROUTING

ISIS-6-NO_INPUTBUF

6 ROUTING

ISIS-6-NO_INPUTBUF

6 ROUTING

ISIS-7-ERR_CREATEMQ

7 ROUTING

ISIS-7-ERR_MSG

7 ROUTING

ISIS-7-ERR_MSGLEN

7 ROUTING

ISIS-7-ERR_RCV_PAKTYPE

7 ROUTING

ISIS-7-ERR_RCV_PAKTYPE

7 ROUTING

ISIS-7-ERR_RECV_TE_MSG

7 ROUTING

ISIS-7-ERR_RECV_TE_MSG_VERSION

7 ROUTING

ISIS-7-ERR_SEND_TE_MSG

7 ROUTING

ISIS-7-STALE_PNODE_PURGE

7 ROUTING

ISIS-7-STALE_PNODE_PURGE

7 ROUTING

LDP-3-CONFIG_SCAN_FAILED

3 ROUTING

LDP-3-INTERNAL_INCONSISTENCY

3 ROUTING

LDP-3-LDP_CTX_INIT_FAILED

3 ROUTING

LDP-3-LIB_DB_ENTRY_ADD_FAILED

3 ROUTING

LDP-3LIB_INVALID_TYPE_FOR_LONGEST_MATCH_A
CL

3 ROUTING

LDP-3-LPTS_UDP_POLICY_FAILED

3 ROUTING

LDP-3-LSD_CONN_FAILED

3 ROUTING

LDP-3-LSD_INTF_OP_FAILED

3 ROUTING

LDP-3-NSR_ACK_CHK_FAILED

3 ROUTING

LDP-3-NSR_SYNC_IPC_XPORT_FAILURE

3 ROUTING

LDP-3-NSR_SYNC_PEER_NO_SOCK

3 ROUTING

LDP-3-NSR_SYNC_PEER_OP_FAILED

3 ROUTING

LDP-3-PROC_EXIT

3 ROUTING

LDP-3-PROC_SHUTDOWN_OOM

3 ROUTING

LDP-3ROUTE_UPDATE_UNSUPP_PROTECTION

3 ROUTING

LDP-3-RX_BAD_PREFIX_LEN

3 ROUTING

LDP-3-RX_PKT_BAD_PDU_LEN

3 ROUTING

LDP-3-RX_PKT_TLV_CHK_FAILED

3 ROUTING

LDP-3-RX_RIB_REDUND_PROTO_NOTIF

3 ROUTING

LDP-3-TCB_FREE_OPEN_SOCK

3 ROUTING

LDP-4-CAP_CHANGE_DYNAMIC

4 ROUTING

LDP-4-DISCOVERY_SLIP

4 ROUTING

LDP-4-LIB_REV_NUM_WRAP

4 ROUTING

LDP-4-LIB_RX_INVALID_FEC_TYPE

4 ROUTING

LDP-4-MAX_DISC_NBRS

4 ROUTING

LDP-4-MAX_NEIGHBORS

4 ROUTING

LDP-4-NSR_GLOBAL_SYNC_LOST

4 ROUTING

LDP-4-NSR_TCP_MSG_INVAL_TX_CTX

4 ROUTING

LDP-4-NSR_TCP_MSG_TX_NOT_ALLOWED

4 ROUTING

LDP-4-PEER_DUP_ADDRS

4 ROUTING

LDP-4-RX_BAD_ADDR_TYPE

4 ROUTING

LDP-4-RX_BAD_PDU_HEADER

4 ROUTING

LDP-4-RX_PEER_DUP_ADDR

4 ROUTING

LDP-4-RX_PKT_MALFORMED

4 ROUTING

LDP-4-RX_UNEXPECTED_MSG_TYPE

4 ROUTING

LDP-4-RX_UNSUPP_SESSION_PARAM

4 ROUTING

LDP-4-SESSION_UNEXPECTED_FSM_EVENT

4 ROUTING

LDP-4-TX_KEEPALIVE_SLIP

4 ROUTING

LDP-4-UNSOL_OPEN_PEER_FAILED

4 ROUTING

LDP-5-GR_LCL_RESTART_COMPLETE

5 ROUTING

LDP-5-GR_NBR_ABORT

5 ROUTING

LDP-5-GR_NBR_CHANGE

5 ROUTING

LDP-5-GR_NBR_ID_CHANGE

5 ROUTING

LDP-5-HELLO_ADJ_CHANGE

5 ROUTING

LDP-5-LDP_IGP_SYNC_CHKPT_LIMIT

5 ROUTING

LDP-5-MSG_TX_SKIPPED_NO_PEER

5 ROUTING

LDP-5-NBR_CHANGE

5 ROUTING

LDP-5-NSR_PEER_SYNC_LOST

5 ROUTING

LDP-5-NSR_SYNC_DONE

5 ROUTING

LDP-5-NSR_SYNC_PEER_DONE

5 ROUTING

LDP-5-NSR_SYNC_START

5 ROUTING

LDP-5-SESSION_PROTECTION

5 ROUTING

LDP-6-CAP_CHANGE

6 ROUTING

LMRIB_API-3-GEN_FAIL

3 ROUTING

LMRIB_API-3-GENINITFAIL

3 ROUTING

LMRIB_API-3-LWM_FAIL

3 ROUTING

LMRIB_API-3-RPC_FAIL

3 ROUTING

LSLIB-3-ERR

3 ROUTING

LSPV-4-show_timeout

4 ROUTING

LSPV-7-MSG_EVENT

7 ROUTING

LSPV-7-MSG_GENERAL

7 ROUTING

LSPV-7-MSG_INIT_MUTEX

7 ROUTING

LSPV-7-MSG_INIT_RC

7 ROUTING

LSPV-7-MSG_TIMER

7 ROUTING

MFWD_MA-3-CFG_ERR

3 ROUTING

MFWD_MA-3-ERR_DEBUG_INIT_EVENT

3 ROUTING

MFWD_MA-3-ERR_DEBUG_REG

3 ROUTING

MFWD_MA-3-ERR_EVM_ASYNC_ATTACH

3 ROUTING

MFWD_MA-3-ERR_EVM_CONN_CREATE

3 ROUTING

MFWD_MA-3-ERR_EVM_CONN_NOTIFY

3 ROUTING

MFWD_MA-3-ERR_EVM_CONN_OPEN

3 ROUTING

MFWD_MA-3-ERR_EVM_CREATE

3 ROUTING

MFWD_MA-3ERR_IMC_CONTROL_SERVER_BIND

3 ROUTING

MFWD_MA-3-ERR_LTRACE_INIT

3 ROUTING

MFWD_MA-3-ERR_MEM_ALLOC

3 ROUTING

MFWD_MA-3-ERR_MEM_FAIL

3 ROUTING

MFWD_MA-3-ERR_MEM_FAIL_1

3 ROUTING

MFWD_MA-3-ERR_SYSDB_BAG_DECODE

3 ROUTING

MFWD_MA-3ERR_SYSDB_BAG_FREE_INDIRECTIONS

3 ROUTING

MFWD_MA-3-ERR_SYSDB_BAG_REG

3 ROUTING

MFWD_MA-3-ERR_SYSDB_BIND

3 ROUTING

MFWD_MA-3-ERR_SYSDB_DATALIST_FREE

3 ROUTING

MFWD_MA-3-ERR_SYSDB_DATALIST_NEXT

3 ROUTING

MFWD_MA-3-ERR_SYSDB_EDM_FNS_INIT

3 ROUTING

MFWD_MA-3-ERR_SYSDB_EDM_REG

3 ROUTING

MFWD_MA-3-ERR_SYSDB_REG_VERIFY

3 ROUTING

MFWD_MA-3-ERR_SYSDB_VRFN_FNS_INIT

3 ROUTING

MFWD_MA-3-GEN_ERR

3 ROUTING

MFWD_MA-3-GENINITFAIL

3 ROUTING

MFWD_MA-3-IDB_ERR

3 ROUTING

MFWD_MA-3IM_UPDATE_IDB_HANDLE_MISMATCH

3 ROUTING

MFWD_MA-3-MISC_ERR

3 ROUTING

MLDP_POLICY-3-ORA_ERR
MLDP-5-BRANCH_ADD
MLDP-5-BRANCH_DELETE
MLDP-5-BRANCH_MODIFY

3 ROUTING
5 ROUTING
5 ROUTING
5 ROUTING

MLDP-5-DISABLED

5 ROUTING

MLDP-5-ENABLED

5 ROUTING

MLDP-7-INIT_FAIL

7 ROUTING

MOFRR_FLOW-3-DETECT_ACTIVE_BACKUP

3 ROUTING

MOFRR_FLOW-3-DETECT_ACTIVE_PRIM

3 ROUTING

MOFRR_FLOW-3-DETECT_LOSS_BACKUP

3 ROUTING

MOFRR_FLOW-3-DETECT_LOSS_PRIM

3 ROUTING

MOFRR_FLOW-3-WD_OOR_GREEN

3 ROUTING

MOFRR_FLOW-3-WD_OOR_RED

3 ROUTING

MPLS_ALM-7-ERR_GENERAL

7 ROUTING

MPLS_FWD-2-NO_MEM

2 ROUTING

MPLS_FWD-3-BAG_REG_ERR

3 ROUTING

MPLS_FWD-3-ERR_GENERAL

3 ROUTING

MPLS_FWD-3-EVENT_ERR

3 ROUTING

MPLS_FWD-3-SYSDB_BIND_ERR

3 ROUTING

MPLS_FWD-3-SYSDB_ERR

3 ROUTING

MPLS_HW-2-ERROR

2 ROUTING

MPLS_HW-2-ERROR_TLU_ALLOC

2 ROUTING

MPLS_HW-2-ERROR_TLU_WRITE

2 ROUTING

MPLS_HW-2-ERROR_WITH_LABEL

2 ROUTING

MPLS_HW-6-INFO

6 ROUTING

MPLS_HW-6-INFO_WITH_LABEL

6 ROUTING

MPLS_IMC_CLIENT-3-ERR_IMC

3 ROUTING

MPLS_IO-3-ERR_MEM_ALLOC

3 ROUTING

MPLS_IO-6-ERR_GENERAL

6 ROUTING

MPLS_IO-7-ERR_IM

7 ROUTING

MPLS_IO-7-ERR_PAK

7 ROUTING

MPLS_IO-7-ERR_TIMER

7 ROUTING

MPLS_IO-7-ERR_WAVL

7 ROUTING

MPLS_LCAC-4-SHOW_WARNING

4 ROUTING

MPLS_LCAC-7-ERR_INTERNAL

7 ROUTING

MPLS_LSD_CLIENT-4ERR_CLIENT_API_CALL_NOTCONN

4 ROUTING

MPLS_LSD-2-ERR_MEM_ALLOC

2 ROUTING

MPLS_LSD-3-BCDL_INIT_FAILED

3 ROUTING

MPLS_LSD-3-ERR_INVALID_THREAD

3 ROUTING

MPLS_LSD-3-MULTI_IP_FPI_RW

3 ROUTING

MPLS_LSD-7-ERR_CHKPT

7 ROUTING

MPLS_LSD-7-ERR_CLIENT_FAULT

7 ROUTING

MPLS_LSD-7-ERR_GENERAL

7 ROUTING

MPLS_LSD-7-ERR_INIT

7 ROUTING

MPLS_LSD-7-ERR_RCC_INIT

7 ROUTING

MPLS_NETIO-5-CLEAR_MAPPING_FAILED

5 ROUTING

MPLS_NETIO-5-SET_MAPPING_FAILED

5 ROUTING

MPLS_NETIO-7-BAD_ARP_DROP

7 ROUTING

MPLS_NETIO-7-ERR_GENERAL

7 ROUTING

MPLS_PCE-5-PEER_STATE_CHANGE
MPLS_STATIC-4-ERR_MEM_ALLOC

5 ROUTING
4 ROUTING

MPLS_STATIC-6-ERR_CONN

6 ROUTING

MPLS_STATIC-7-ERR_INIT

7 ROUTING

MPLS_STATIC-7ERR_STATIC_LABEL_DISCREPANCY

7 ROUTING

MPLS_TE_SLSP-4-SHOW_WARNING

4 ROUTING

MPLS_TE-3-CALLBACK_WRONG_THREAD

3 ROUTING

MPLS_TE-3-CALLBACK_WRONG_THREAD

3 ROUTING

MPLS_TE-3-CHKPT_XFORM_INVALID_DIR

3 ROUTING

MPLS_TE-3-CONSISTENCY_CHECK

3 ROUTING

MPLS_TE-3ERR_AUTO_TUN_BKP_ID_LIMIT_EXCEEDED

3 ROUTING

MPLS_TE-3ERR_AUTO_TUN_BKP_TUN_DEST_LIMIT_EXC
EEDED

3 ROUTING

MPLS_TE-3ERR_AUTO_TUN_BKP_TUN_LIMIT_EXCEEDED

3 ROUTING

MPLS_TE-3ERR_AUTO_TUN_LIMIT_EXCEEDED

3 ROUTING

MPLS_TE-3ERR_AUTO_TUN_MESH_ID_LIMIT_EXCEEDED

3 ROUTING

MPLS_TE-3ERR_AUTO_TUN_MESH_TUN_DEST_LIMIT_EX
CEEDED

3 ROUTING

MPLS_TE-3ERR_AUTO_TUN_MESH_TUN_LIMIT_EXCEED
ED

3 ROUTING

MPLS_TE-3ERR_AUTO_TUN_P2MP_DEST_LIMIT_EXCEED
ED

3 ROUTING

MPLS_TE-3ERR_AUTO_TUN_P2MP_ID_LIMIT_EXCEEDED

3 ROUTING

MPLS_TE-3ERR_AUTO_TUN_P2MP_LIMIT_EXCEEDED

3 ROUTING

MPLS_TE-3ERR_AUTOROUTE_DESTINATIONS_PATH_EX
CEEDED

3 ROUTING

MPLS_TE-3-ERR_IM

3 ROUTING

MPLS_TE-3-ERR_IM

3 ROUTING

MPLS_TE-3-ERR_INTERNAL_CHECK

3 ROUTING

MPLS_TE-3-ERR_INTERNAL_CHECK

3 ROUTING

MPLS_TE-3-ERR_INTERNAL_CHECK_RC

3 ROUTING

MPLS_TE-3-ERR_INTERNAL_CHECK_RC

3 ROUTING

MPLS_TE-3-ERR_LMRIB_LABEL_RW

3 ROUTING

MPLS_TE-3-ERR_LMRIB_LABEL_RW

3 ROUTING

MPLS_TE-3-ERR_LMRIB_TUNNEL_RW

3 ROUTING

MPLS_TE-3-ERR_LMRIB_TUNNEL_RW

3 ROUTING

MPLS_TE-3-ERR_MEM_ALLOC

3 ROUTING

MPLS_TE-3-ERR_MEM_ALLOC

3 ROUTING

MPLS_TE-3-ERR_SYSDB_BAG_DECODE

3 ROUTING

MPLS_TE-3-ERR_SYSDB_DELETE

3 ROUTING

MPLS_TE-3-ERR_SYSDB_GET

3 ROUTING

MPLS_TE-3-ERR_TRACE_INIT

3 ROUTING

MPLS_TE-3-ERR_TRACE_INIT

3 ROUTING

MPLS_TE-3-NONRESPONSIVE_CLIENT

3 ROUTING

MPLS_TE-4-GMPLS_NNI_DEPRECATED

4 ROUTING

MPLS_TE-4-SHOW_WARNING

4 ROUTING

MPLS_TE-4-SHOW_WARNING

4 ROUTING

MPLS_TE-4-SHUTDOWN

4 ROUTING

MPLS_TE-4-SHUTDOWN

4 ROUTING

MPLS_TE-4-WARN

4 ROUTING

MPLS_TE-4-WARN

4 ROUTING

MPLS_TE-4-WARNING_FSM_EVENT_DROP

4 ROUTING

MPLS_TE-4-WARNING_FSM_EVENT_DROP

4 ROUTING

MPLS_TE-5-FRR

5 ROUTING

MPLS_TE-5-FRR

5 ROUTING

MPLS_TE-5-LSP_BW_CHANGE

5 ROUTING

MPLS_TE-5-LSP_INSUFFICIENT_BW

5 ROUTING

MPLS_TE-5-LSP_PCALC_FAIL

5 ROUTING

MPLS_TE-5-LSP_PREEMPT

5 ROUTING

MPLS_TE-5-LSP_RECORDROUTE

5 ROUTING

MPLS_TE-5-LSP_REOPT

5 ROUTING

MPLS_TE-5-LSP_REOPT

5 ROUTING

MPLS_TE-5-LSP_REROUTE

5 ROUTING

MPLS_TE-5-LSP_REROUTE

5 ROUTING

MPLS_TE-5-LSP_REROUTE_PENDING

5 ROUTING

MPLS_TE-5-LSP_REROUTE_PENDING

5 ROUTING

MPLS_TE-5-LSP_REROUTE_PENDING_CLEAR

5 ROUTING

MPLS_TE-5-LSP_REROUTE_PENDING_CLEAR

5 ROUTING

MPLS_TE-5-LSP_SOFT_PREEMPT

5 ROUTING

MPLS_TE-5-LSP_SOFT_PREEMPT_TIMEOUT

5 ROUTING

MPLS_TE-5-LSP_SOFT_PREEMPTED

5 ROUTING

MPLS_TE-5-LSP_SWITCH

5 ROUTING

MPLS_TE-5-LSP_SWITCH

5 ROUTING

MPLS_TE-5-LSP_UPDOWN

5 ROUTING

MPLS_TE-5-LSP_UPDOWN

5 ROUTING

MPLS_TE-5-S2L_BFD_DOWN

5 ROUTING

MPLS_TE-5-S2L_BFD_TIMEOUT

5 ROUTING

MPLS_TE-5-S2L_BFD_UP

5 ROUTING

MPLS_TE-5-S2L_INSUFFICIENT_BW

5 ROUTING

MPLS_TE-5-S2L_PCALC_FAIL

5 ROUTING

MPLS_TE-5-S2L_PREEMPT

5 ROUTING

MPLS_TE-5-S2L_REROUTE

5 ROUTING

MPLS_TE-5-S2L_REROUTE

5 ROUTING

MPLS_TE-5-S2L_UPDOWN

5 ROUTING

MPLS_TE-5-S2L_UPDOWN

5 ROUTING

MPLS_TE-7-ERR_INTERNAL

7 ROUTING

MPLS_TE-7-ERR_INTERNAL

7 ROUTING

MPLS_TP_ALARM-4-LOCKOUT

4 ROUTING

MPLS_TP_ALARM-4-PROT_SWITCH

4 ROUTING

MPLS_TP_ALARM-4-TUNNEL_STATE

4 ROUTING

MRIB_API-3-ASYNC_ERR

3 ROUTING

MRIB_API-3-CORRPT

3 ROUTING

MRIB_API-3-GEN_ERR

3 ROUTING

MRIB_API-3-GENINITFAIL

3 ROUTING

MRIB_API-3-LWM_ERR

3 ROUTING

MRIB_API-3-RPC_FAIL

3 ROUTING

MRIB_API-7-ASYNC_WAR

7 ROUTING

MRIB-2-NOMEMORY

2 ROUTING

MRIB-2-NORESOURCE

2 ROUTING

MRIB-2-RC_INIT_ERR

2 ROUTING

MRIB-3-EDM_INIT

3 ROUTING

MRIB-3-EXTRANET_ERR

3 ROUTING

MRIB-3-GEN_ERR

3 ROUTING

MRIB-3-GENCOMMERR

3 ROUTING

MRIB-3-GENINITFAIL

3 ROUTING

MRIB-3-IFCACHE_ERR

3 ROUTING

MRIB-3-INT_ERR

3 ROUTING

MRIB-3-INTERNALERR

3 ROUTING

MRIB-3-LRD_ERR

3 ROUTING

MRIB-3-LWM_2_ERR

3 ROUTING

MRIB-3-LWM_ERR

3 ROUTING

MRIB-3-MOD_INTF_LIST

3 ROUTING

MRIB-3-NSF_ERR

3 ROUTING

MRIB-3-NSFSTATE

3 ROUTING

MRIB-3-PLATFORM_API_ERR

3 ROUTING

MRIB-3-RC_ERR

3 ROUTING

MRIB-3-REDUCEDFUNCT

3 ROUTING

MRIB-3-TLC_ERR

3 ROUTING

MRIB-3-TREE_OPER

3 ROUTING

MRIB-4-ADD_DEL_SAME_BATCH_ERR

4 ROUTING

MRIB-4-CLIENT_WRITE

4 ROUTING

MRIB-4-DEBUGERR

4 ROUTING

MRIB-4-EXTRANET_WARN

4 ROUTING

MRIB-4-FILTRVIOLERR

4 ROUTING

MRIB-4-GEN_WARN

4 ROUTING

MRIB-4-INCORRECTPARS

4 ROUTING

MRIB-4-NOMEMORYW

4 ROUTING

MRIB-4-STALE_HANDLE_ERR

4 ROUTING

MRIB-5-BCDL_ERR

5 ROUTING

MSDP-3-BAD_STATE

3 ROUTING

MSDP-3-CACHE_FAIL

3 ROUTING

MSDP-3-CONNECTION_FAIL

3 ROUTING

MSDP-3-EDM_FAIL

3 ROUTING

MSDP-3-EVENT_FAILED

3 ROUTING

MSDP-3-INIT_FAILED

3 ROUTING

MSDP-3-INIT_FAILED2

3 ROUTING

MSDP-3-INTERNAL_STATE_FAIL

3 ROUTING

MSDP-3-IO_FAILED

3 ROUTING

MSDP-3-ITAL_REG_FAIL

3 ROUTING

MSDP-3-LTRACE_INIT

3 ROUTING

MSDP-3-MRIB_FAIL

3 ROUTING

MSDP-3-OUT_OF_MEMORY

3 ROUTING

MSDP-3-OUT_OF_RESOURCE

3 ROUTING

MSDP-3-SYSDB_FAIL

3 ROUTING

MSDP-3-WDSYSMON_EVENT_FAIL

3 ROUTING

MSDP-3-WDSYSMON_REGISTER_FAILURE

3 ROUTING

MSDP-4-CONFIG_FAILED

4 ROUTING

MSDP-4-OOM_STATE_THROTTLE

4 ROUTING

MSDP-4-OOM_STATE_UNTHROTTLE

4 ROUTING

MSDP-4-PEER_FAIL

4 ROUTING

MSDP-4-RIB_FAIL

4 ROUTING

MSDP-5-INIT_PEER_UP_DOWN

5 ROUTING

MULTIVER-3-DLL_OPEN_FAIL

3 ROUTING

MULTIVER-4-DLL_SIGNATURE_MISMATCH

4 ROUTING

ORA_SHARED-4-ERR_DLL_REG

4 ROUTING

ORA-2-MEM_ALLOC_FAIL

2 ROUTING

ORA-3-DUPLICATE_DOCKENTRY

3 ROUTING

ORA-3-INIT

3 ROUTING

ORA-3-MISSING_BASE_TYPE

3 ROUTING

ORA-3-MISSING_FUNCTION

3 ROUTING

ORA-3-MISSING_OPERATOR

3 ROUTING

ORA-3-THREADING_FAIL

3 ROUTING

ORA-4-DLL_REG_FAIL

4 ROUTING

ORA-4-MERGE_FAILED

4 ROUTING

ORA-4-MISSING_DOCK_INFO

4 ROUTING

ORA-7-DBGINIT

7 ROUTING

ORA-7-DBGSHUTDOWN

7 ROUTING

OSPF_EDM-3-DATALIST_ADD_FAILED

3 ROUTING

OSPF_EDM-3-DATALIST_CREATE_FAILED

3 ROUTING

OSPF_EDM-3-DATALIST_SET_MORE_FLAG

3 ROUTING

OSPF_EDM-3-ENCODE_FAILED

3 ROUTING

OSPF_EDM-3-LIST_ADD_FAILED

3 ROUTING

OSPF_EDM-3-LIST_CREATE_FAILED

3 ROUTING

OSPF_EDM-3-SYSDB_BIND_FAILED

3 ROUTING

OSPF_POLICY-3-ORA_INSTBUILD

3 ROUTING

OSPF_POLICY-3-ORA_RUN

3 ROUTING

OSPF_RIB-3-ERR_PATH_ADD

3 ROUTING

OSPF_RIB-3-ERR_PATH_DELETE

3 ROUTING

OSPF_RIB-3-ERR_PROTO_MODIFY

3 ROUTING

OSPF_RIB-3-ERR_ROUTE_HDR

3 ROUTING

OSPF_RIB-3-ERR_UPDATE_DONE

3 ROUTING

OSPF_RIB-4-BATCH_LOG_PATH

4 ROUTING

OSPF_RIB-5-BATCH_ERROR

5 ROUTING

OSPF_RIB-5-BATCH_ERROR_CODE

5 ROUTING

OSPF_RIB-6-INFO_RT_HDR_NOTUSED

6 ROUTING

OSPF_UV-3-CERR_REG_FAIL

3 ROUTING

OSPF_UV-3-ERR_DBG_REGISTER_FAILED

3 ROUTING

OSPF_UV-3-ERR_MEM_ALLOC_FAIL

3 ROUTING

OSPF_UV-3-ERR_PROC_READY

3 ROUTING

OSPF_UV-3-ERR_SYSDB_CONNECT

3 ROUTING

OSPF_UV-3-ERR_SYSDB_DISCONNECT

3 ROUTING

OSPF_UV-3-ERR_SYSDB_REG_VERIFY

3 ROUTING

OSPF_UV-3-ERR_VRFN_FNS_INIT

3 ROUTING

OSPF_UV-3-EVENT_ERR

3 ROUTING

OSPF_UV-3-EVM_CRE_FAIL

3 ROUTING

OSPF_UV-3-INTF_FWS_INIT

3 ROUTING

OSPF_UV-6-PROCESS_NAME

6 ROUTING

OSPF-2-ERR_MEM_ALLOC

2 ROUTING

OSPF-3-ALLOC_ERR

3 ROUTING

OSPF-3-AREANULL

3 ROUTING

OSPF-3-BADMSG

3 ROUTING

OSPF-3-BADSHARE

3 ROUTING

OSPF-3-BADTIMER

3 ROUTING

OSPF-3-DBGINIT

3 ROUTING

OSPF-3-DUP_RTRID

3 ROUTING

OSPF-3-ERR_RESOURCE_ALLOC

3 ROUTING

OSPF-3-EVM

3 ROUTING

OSPF-3-EVM_CODE

3 ROUTING

OSPF-3-EVM_RL

3 ROUTING

OSPF-3-EXTERNALERR

3 ROUTING

OSPF-3-EXTERNALERR_RC

3 ROUTING

OSPF-3-FRIS

3 ROUTING

OSPF-3-IDBERR

3 ROUTING

OSPF-3-IFCHECK

3 ROUTING

OSPF-3-IFINIT

3 ROUTING

OSPF-3-IFMGR

3 ROUTING

OSPF-3-IGPTE

3 ROUTING

OSPF-3-INIT_ERR

3 ROUTING

OSPF-3-INIT_ERR_STR

3 ROUTING

OSPF-3-INTERNALERR

3 ROUTING

OSPF-3-INTERNALERR_RC

3 ROUTING

OSPF-3-IPARM

3 ROUTING

OSPF-3-LWM

3 ROUTING

OSPF-3-MCAST

3 ROUTING

OSPF-3-MEDIAERR

3 ROUTING

OSPF-3-MUTEX

3 ROUTING

OSPF-3-NOBACKBONE

3 ROUTING

OSPF-3-NOIPADDR

3 ROUTING

OSPF-3-NOSELF

3 ROUTING

OSPF-3-NOTNBRTYPE

3 ROUTING

OSPF-3-NSR_SYNC_ERR

3 ROUTING

OSPF-3-PATH_ID_OOR

3 ROUTING

OSPF-3-PKTDROP

3 ROUTING

OSPF-3-RDB_NO_LSA

3 ROUTING

OSPF-3-RECONF_VL

3 ROUTING

OSPF-3-RIB

3 ROUTING

OSPF-3-RIB_MSG

3 ROUTING

OSPF-3-RPC

3 ROUTING

OSPF-3-RSI

3 ROUTING

OSPF-3-SOCKET

3 ROUTING

OSPF-3-SYSDB

3 ROUTING

OSPF-3-THREAD_CREATE

3 ROUTING

OSPF-3-UNKNOWNSTATE

3 ROUTING

OSPF-4-BADLENGTH

4 ROUTING

OSPF-4-BADLSATYPE

4 ROUTING

OSPF-4-CONFLICTING_LSAID

4 ROUTING

OSPF-4-DEPRECATED_RTRID

4 ROUTING

OSPF-4-DOMAIN_TAG_NEEDED

4 ROUTING

OSPF-4-ERR_MSG_GET_SCOID

4 ROUTING

OSPF-4-ERR_MSG_REPLY

4 ROUTING

OSPF-4-ERRRCV

4 ROUTING

OSPF-4-IFINDEX_GET

4 ROUTING

OSPF-4-KEYCFG

4 ROUTING

OSPF-4-MAX_INTF_APPLY

4 ROUTING

OSPF-4-MAX_LSA

4 ROUTING

OSPF-4-MAX_LSA_THR

4 ROUTING

OSPF-4-MUTEX_ERR

4 ROUTING

OSPF-4-NBREXIST

4 ROUTING

OSPF-4-NETWORK_TYPE_MISMATCH

4 ROUTING

OSPF-4-NONEIGHBOR

4 ROUTING

OSPF-4-NORTRID

4 ROUTING

OSPF-4-OLD_CMD

4 ROUTING

OSPF-4-PAKMAN_EVENT

4 ROUTING

OSPF-4-POLICYCONFIG

4 ROUTING

OSPF-4-RAW_OUTPUT_ERR

4 ROUTING

OSPF-4-REDIST_FAILED

4 ROUTING

OSPF-4-REDIST_MAX_PFX

4 ROUTING

OSPF-4-REDIST_THR_PFX

4 ROUTING

OSPF-4-STUB_ASBR

4 ROUTING

OSPF-4-USING_OLD_RTRID

4 ROUTING

OSPF-4-VIRTUAL_IN_NON_BACKBONE

4 ROUTING

OSPF-5-ADJCHG

5 ROUTING

OSPF-5-COST_FALLBACK

5 ROUTING

OSPF-5-HA_NOTICE
OSPF-5-HA_NOTICE_START

5 ROUTING
5 ROUTING

OSPF-6-BADCHKSUM

6 ROUTING

OSPF-6-DBEXIST

6 ROUTING

OSPF-6-GRACEFUL_SHUTDOWN

6 ROUTING

OSPF-6-HA_INFO

6 ROUTING

OSPF-6-LSAREFRESH

6 ROUTING

OSPF-6-MAXMETRIC_RUNNING

6 ROUTING

OSPF-6-MEM_NOTIF

6 ROUTING

OSPF-6-MGDTIMER

6 ROUTING

OSPF-6-NEWLIMIT

6 ROUTING

OSPF-6-NOTREDIST3

6 ROUTING

OSPF-6-REFBW_CHG

6 ROUTING

OSPF-6-USING_MSGDGST

6 ROUTING

OSPF-7-DB_EX_DQUEUE

7 ROUTING

OSPF-7-DB_READY_Q

7 ROUTING

OSPF-7-DLINK

7 ROUTING

OSPF-7-DQUEUE

7 ROUTING

OSPF-7-ERR_TUNNEL_INT

7 ROUTING

OSPF-7-INIT_FAIL

7 ROUTING

OSPF-7-TRACEBACK

7 ROUTING

OSPF-7-VRF_DELETE

7 ROUTING

OSPFv3_EDM-3-DATALIST_ADD_FAILED

3 ROUTING

OSPFv3_EDM-3-DATALIST_CREATE_FAILED

3 ROUTING

OSPFv3_EDM-3-DATALIST_SET_MORE_FLAG

3 ROUTING

OSPFv3_EDM-3-EDMINIT

3 ROUTING

OSPFv3_EDM-3-ENCODE_FAILED

3 ROUTING

OSPFv3_EDM-3EVENT_REGISTRATION_FAILED

3 ROUTING

OSPFv3_EDM-3-LIST_ADD_FAILED

3 ROUTING

OSPFv3_EDM-3-LIST_CREATE_FAILED

3 ROUTING

OSPFv3_EDM-3-NO_DATA

3 ROUTING

OSPFv3_EDM-3-PROTO_REG_FAILED

3 ROUTING

OSPFv3_EDM-3-REGISTER_FAILED

3 ROUTING

OSPFv3_EDM-3-SYSDB_BIND_FAILED

3 ROUTING

OSPFv3_EDM-3-SYSDB_COID_FAILED

3 ROUTING

OSPFv3_EDM-6-BAGREG_FAILED

6 ROUTING

OSPFV3_POLICY-3-ORA_INSTBUILD

3 ROUTING

OSPFV3_POLICY-3-ORA_RUN

3 ROUTING

OSPFv3_RIB-2-NO_MEMORY

2 ROUTING

OSPFv3_RIB-3-BIND

3 ROUTING

OSPFv3_RIB-3-DEFAULT_REG

3 ROUTING

OSPFv3_RIB-3-DISCONNECT

3 ROUTING

OSPFv3_RIB-3-ERR_BATCH_COMPLETE

3 ROUTING

OSPFv3_RIB-3-ERR_PATH_ADD

3 ROUTING

OSPFv3_RIB-3-ERR_PATH_DELETE

3 ROUTING

OSPFv3_RIB-3-ERR_ROUTE_HDR

3 ROUTING

OSPFv3_RIB-3-ERR_UPDATE_COMPLETE

3 ROUTING

OSPFv3_RIB-3-FINDPDB

3 ROUTING

OSPFv3_RIB-3-PURGE

3 ROUTING

OSPFv3_RIB-3-REDIST_REG

3 ROUTING

OSPFv3_RIB-3-REGISTER

3 ROUTING

OSPFv3_UV-3-CERR_REG_FAIL

3 ROUTING

OSPFv3_UV-3-ERR_DBG_REGISTER_FAILED

3 ROUTING

OSPFv3_UV-3-ERR_MEM_ALLOC_FAIL

3 ROUTING

OSPFv3_UV-3-ERR_PROC_READY

3 ROUTING

OSPFv3_UV-3-ERR_SYSDB_CONNECT

3 ROUTING

OSPFv3_UV-3-ERR_SYSDB_DISCONNECT

3 ROUTING

OSPFv3_UV-3-ERR_SYSDB_REG_VERIFY

3 ROUTING

OSPFv3_UV-3-ERR_VRFN_FNS_INIT

3 ROUTING

OSPFv3_UV-3-EVENT_ERR

3 ROUTING

OSPFv3_UV-3-EVM_CRE_FAIL

3 ROUTING

OSPFv3_UV-3-INTF_FWS_INIT

3 ROUTING

OSPFv3_UV-6-PROCESS_NAME

6 ROUTING

OSPFv3-2-NOMEMORY

2 ROUTING

OSPFv3-3-ACL_GET

3 ROUTING

OSPFv3-3-ACL_REG

3 ROUTING

OSPFv3-3-ALLOCFAIL

3 ROUTING

OSPFv3-3-APIERR

3 ROUTING

OSPFv3-3-BADMSG

3 ROUTING

OSPFv3-3-BADTIMER

3 ROUTING

OSPFv3-3-CERR_REGISTER

3 ROUTING

OSPFv3-3-CONN_FAIL

3 ROUTING

OSPFv3-3-DBGINIT

3 ROUTING

OSPFv3-3-DBGREG

3 ROUTING

OSPFv3-3-DELVLINK

3 ROUTING

OSPFv3-3-DLINK

3 ROUTING

OSPFv3-3-DUP_RTRID

3 ROUTING

OSPFv3-3-DUP_RTRID_AREA

3 ROUTING

OSPFv3-3-DUP_RTRID_AS

3 ROUTING

OSPFv3-3-EVENTBLOCK

3 ROUTING

OSPFv3-3-EVM

3 ROUTING

OSPFv3-3-EVM_FD

3 ROUTING

OSPFv3-3-EVM_RETRY

3 ROUTING

OSPFv3-3-EXTERNALERR

3 ROUTING

OSPFv3-3-EXTERNALERR_RC

3 ROUTING

OSPFv3-3-FRIS_INSERT

3 ROUTING

OSPFv3-3-HELLOINIT

3 ROUTING

OSPFv3-3-IFINDEX_GET

3 ROUTING

OSPFv3-3-IFINIT

3 ROUTING

OSPFv3-3-IFMGR

3 ROUTING

OSPFv3-3-IFMGR_IF

3 ROUTING

OSPFv3-3-INIT

3 ROUTING

OSPFv3-3-INIT_ERR

3 ROUTING

OSPFv3-3-INSTALL_REG

3 ROUTING

OSPFv3-3-INSTALL_UNREG

3 ROUTING

OSPFv3-3-INTERNALERR

3 ROUTING

OSPFv3-3-INTERNALERR_RC

3 ROUTING

OSPFv3-3-IPARM

3 ROUTING

OSPFv3-3-IPARM_IF

3 ROUTING

OSPFv3-3-IPSEC_CLOSE

3 ROUTING

OSPFv3-3-IPSEC_DEBUG_INIT

3 ROUTING

OSPFv3-3-IPSEC_INIT

3 ROUTING

OSPFv3-3-IPSEC_OPEN

3 ROUTING

OSPFv3-3-LWM

3 ROUTING

OSPFv3-3-MCAST

3 ROUTING

OSPFv3-3-MEM_ALLOC_FAIL

3 ROUTING

OSPFv3-3-MUTEX_INIT

3 ROUTING

OSPFv3-3-NO_VL_ENDPOINT

3 ROUTING

OSPFv3-3-NOBACKBONE

3 ROUTING

OSPFv3-3-NOSELF

3 ROUTING

OSPFv3-3-NOTNBRTYPE

3 ROUTING

OSPFv3-3-NSR_SYNC_ERR

3 ROUTING

OSPFv3-3-PKTDROP

3 ROUTING

OSPFv3-3-PKTDROP_STR

3 ROUTING

OSPFv3-3-PROCINIT

3 ROUTING

OSPFv3-3-RIB

3 ROUTING

OSPFv3-3-RIB_ERR_PROTO_MODIFY

3 ROUTING

OSPFv3-3-RSI

3 ROUTING

OSPFv3-3-RTRINIT

3 ROUTING

OSPFv3-3-SOCKET

3 ROUTING

OSPFv3-3-SYSDB

3 ROUTING

OSPFv3-3-SYSMGR

3 ROUTING

OSPFv3-3-THREAD_CREATE

3 ROUTING

OSPFv3-3-UCAST

3 ROUTING

OSPFv3-3-UNKNOWNSTATE

3 ROUTING

OSPFv3-3-UNSUPPORTED_IFTYPE

3 ROUTING

OSPFv3-4-BADAREA

4 ROUTING

OSPFv3-4-BADLENGTH

4 ROUTING

OSPFv3-4-BADLSA

4 ROUTING

OSPFv3-4-BADVERS

4 ROUTING

OSPFv3-4-DEPRECATED_RTRID

4 ROUTING

OSPFv3-4-ERRRCV

4 ROUTING

OSPFv3-4-LSDB_ERROR

4 ROUTING

OSPFv3-4-LTRACE_INIT

4 ROUTING

OSPFv3-4-NETWORK_MISMATCH

4 ROUTING

OSPFv3-4-NETWORK_TYPE_MISMATCH

4 ROUTING

OSPFv3-4-NONEIGHBOR

4 ROUTING

OSPFv3-4-NORTRID

4 ROUTING

OSPFv3-4-PKTDROP_WARN

4 ROUTING

OSPFv3-4-POLICYCONFIG

4 ROUTING

OSPFv3-4-REDIST_MAX_PFX

4 ROUTING

OSPFv3-4-REDIST_THR_PFX

4 ROUTING

OSPFv3-4-SOCKET_WARN

4 ROUTING

OSPFv3-4-STUB_ASBR

4 ROUTING

OSPFv3-4-USING_OLD_RTRID

4 ROUTING

OSPFv3-4-VIRTUAL_IN_NON_BACKBONE

4 ROUTING

OSPFv3-5-ADJCHG

5 ROUTING

OSPFv3-5-HA_NOTICE
OSPFv3-5-HA_NOTICE_START

5 ROUTING
5 ROUTING

OSPFv3-6-AREA_DELETE

6 ROUTING

OSPFv3-6-AREACREATE

6 ROUTING

OSPFv3-6-BADCHKSUM

6 ROUTING

OSPFv3-6-GRACEFUL_SHUTDOWN

6 ROUTING

OSPFv3-6-HA_INFO

6 ROUTING

OSPFv3-6-MGDTIMER

6 ROUTING

OSPFv3-6-RECONF_VL

6 ROUTING

OSPFv3-6-REFBW_CHG

6 ROUTING

PANINI_IPV4_MRIB-3-CHKPT_ERR

3 ROUTING

PANINI_IPV4_MRIB-3-EXIT_ERR

3 ROUTING

PANINI_IPV4_MRIB-3-FGID_ADD_ERR

3 ROUTING

PANINI_IPV4_MRIB-3-FGID_ERR

3 ROUTING

PANINI_IPV4_MRIB-3-FGID_REMOVE_ERR

3 ROUTING

PANINI_IPV4_MRIB-3-FILE_OPEN_ERR

3 ROUTING

PANINI_IPV4_MRIB-3-IFH_ERR

3 ROUTING

PANINI_IPV4_MRIB-3-IM_NAME_ERR

3 ROUTING

PANINI_IPV4_MRIB-3-INIT_ERR

3 ROUTING

PANINI_IPV4_MRIB-3-INTERNAL_ERR

3 ROUTING

PANINI_IPV4_MRIB-3-INVALID_FGID_ERR

3 ROUTING

PANINI_IPV4_MRIB-3-MEM_ERR

3 ROUTING

PANINI_IPV4_MRIB-3-PERF_ERR

3 ROUTING

PANINI_IPV4_MRIB-4FROM_FGID_UPDATE_GLACIAL

4 ROUTING

PIM_MA-3-CONN_ERR

3 ROUTING

PIM_MA-3-ERR

3 ROUTING

PIM_NETIO-3-DEBUG_ERR

3 ROUTING

PIM_POLICY-3-ORA_INSTBUILD

3 ROUTING

PIM_POLICY-3-ORA_ORABUILD

3 ROUTING

PIM_POLICY-3-ORA_RUN

3 ROUTING

POLICY_REPOSITORY_DYNREG-3AP_ADD_FAIL

3 ROUTING

POLICY_REPOSITORY_DYNREG-3AP_CREATE_FAIL

3 ROUTING

POLICY_REPOSITORY_DYNREG-3AP_DATA_EXTRACT_FAIL

3 ROUTING

POLICY_REPOSITORY_DYNREG-3AP_DELETE_FAIL

3 ROUTING

POLICY_REPOSITORY_DYNREG-3AP_DOCK_FAIL

3 ROUTING

POLICY_REPOSITORY_DYNREG-3AP_FIND_FAIL

3 ROUTING

POLICY_REPOSITORY_DYNREG-3AP_REGISTER_FAIL

3 ROUTING

POLICY_REPOSITORY_DYNREG-3AP_UNDOCK_FAIL

3 ROUTING

POLICY_REPOSITORY_DYNREG-3AP_UNREGISTER_FAIL

3 ROUTING

POLICY_REPOSITORY_DYNREG-3INSTALL_AP_FAIL

3 ROUTING

POLICY_REPOSITORY_DYNREG-3MODIFY_AP_FAIL

3 ROUTING

POLICY_REPOSITORY_DYNREG-3UNLOAD_AP_FAIL

3 ROUTING

POLICY_REPOSITORY_DYNREG-4AP_DATA_CONFLICT

4 ROUTING

POLICY_REPOSITORY_EDM-3SYSDB_BAG_ENCODE_FAIL

3 ROUTING

POLICY_REPOSITORY_EDM-3SYSDB_BIND_FAIL

3 ROUTING

POLICY_REPOSITORY_EDM-3SYSDB_EDM_DATA_GENERATE_FAIL

3 ROUTING

POLICY_REPOSITORY_EDM-3SYSDB_EDM_LIST_ADD_FAIL

3 ROUTING

POLICY_REPOSITORY_EDM-3SYSDB_EDM_LIST_CREATE_FAIL

3 ROUTING

POLICY_REPOSITORY_EDM-3SYSDB_EDM_REG_FAIL

3 ROUTING

POLICY_REPOSITORY_EDM-3SYSDB_UNBIND_FAIL

3 ROUTING

POLICY_REPOSITORY_EDM-6SYSDB_BAG_REG_FAIL

6 ROUTING

POLICY_REPOSITORY-3-MEM_ALLOC_FAIL

3 ROUTING

POLICY_REPOSITORY-3-ORA_DOCK_FAIL

3 ROUTING

POLICY_REPOSITORY-3POLICY_REPOSITORY_INCONSISTENT

3 ROUTING

POLICY_REPOSITORY-3SYSDB_BAG_DECODE_FAIL

3 ROUTING

POLICY_REPOSITORY-3SYSDB_CONNECT_FAIL

3 ROUTING

POLICY_REPOSITORY-3-SYSDB_GET_FAIL

3 ROUTING

POLICY_REPOSITORY-3SYSDB_REG_NOTIFY_FAIL

3 ROUTING

POLICY_REPOSITORY-3SYSDB_REG_VERIFY_FAIL

3 ROUTING

POLICY_REPOSITORY-4-PARSER_DLL

4 ROUTING

POLICY_REPOSITORY-4POLICY_CLEANUP_FAIL

4 ROUTING

POLICY_REPOSITORY-4-RPL_EDIT

4 ROUTING

POLICY_REPOSITORY-4-SYSDB_DELETE_FAIL

4 ROUTING

POLICY_REPOSITORY-4SYSMGR_GET_NODE_STATE

4 ROUTING

POLICY_REPOSITORY-7-ARG_MISMATCH

7 ROUTING

POLICY_REPOSITORY-7ATTACHPOINT_ADD_FAIL

7 ROUTING

POLICY_REPOSITORY-7ATTACHPOINT_MISMATCH

7 ROUTING

POLICY_REPOSITORY-7-OBJECT_INIT_FAIL

7 ROUTING

POLICY_REPOSITORY-7OBJECT_REBUILD_FAIL

7 ROUTING

POLICY_REPOSITORY-7POLICY_ITEM_UNSUPPORTED

7 ROUTING

POLICY_REPOSITORY-7-POLICY_TOO_BIG

7 ROUTING

POLICY_REPOSITORY-7SETS_REBUILD_INCONSISTENCY

7 ROUTING

POLICY_REPOSITORY-7-VERIFY_APPLY_FAIL

7 ROUTING

RASF-2-NO_CMP_RETRIEVER

2 ROUTING

RASF-2-NO_COMPARE

2 ROUTING

RASF-2-NO_RETRIEVER

2 ROUTING

RASF-2-NO_SETTER

2 ROUTING

RASF-4-DLL_REG_FAIL

4 ROUTING

RASF-4-NO_BASE_COMPARE

4 ROUTING

RASF-7-DBGINIT

7 ROUTING

RASF-7-DBGSHUTDOWN

7 ROUTING

RCMD_LIB_XFORM-3-VERSION_MISMATCH

3 ROUTING

RCMD_LIB-3-INIT_FAIL

3 ROUTING

RCMD_LIB-3-PREFIX_LIST_CFG_FAIL

3 ROUTING

RCMD_LIB-4-PFX_MON_LIMIT_REACHED

4 ROUTING

RCMD_LIB-5-FRR_BELOW_THRESHOLD

5 ROUTING

RCMD_LIB-5LABEL_COVERAGE_BELOW_THRESHOLD

5 ROUTING

RCMD_LIB-5-THRESHOLD_EXCEEDED

5 ROUTING

RCMD-3-ARCHIVE_FAIL

3 ROUTING

RCMD-3-ASSERT_INFO

3 ROUTING

RCMD-3-DUP_INST_ID

3 ROUTING

RCMD-3-INIT_FAIL

3 ROUTING

RCMD-3-MEM_ALERT

3 ROUTING

RCMD-3-STR_SIZE

3 ROUTING

RCMD-4-INV_DIAG_CONFIG

4 ROUTING

RCMD-6-INV_SIZE_CONFIG

6 ROUTING

RCMD-6-NTP_DRIFT

6 ROUTING

RCMD-6-PROCESS_THROTTLED

6 ROUTING

RCMD-6-SERVER_INIT

6 ROUTING

RETRY-4-DEBUG_INIT

4 ROUTING

RIB_LIB-3-ERR_LOCK_FATAL

3 ROUTING

RIB_LIB-3-FETCH_UPDATE

3 ROUTING

RIB_LIB-4ERR_POSSIBLE_CONNECTION_LEAK

4 ROUTING

RIB_LIB-4-UNBIND

4 ROUTING

RIB_QUERY_ORA-3-CERRNO_REG

3 ROUTING

RIB_QUERY_ORA-3-INSTBUILD

3 ROUTING

RIB_QUERY_ORA-3-ORABUILD

3 ROUTING

RIB_QUERY_ORA-3-RUN

3 ROUTING

RIB-2-CHILD_PARENT_MISMATCH

2 ROUTING

RIB-2-PARENT_REREGISTER

2 ROUTING

RIB-2-PARENT_UNREGISTER

2 ROUTING

RIB-3-BATCH_PROTO_REG_FAILURE

3 ROUTING

RIB-3-CONVERGE_VERSION_MISMATCH

3 ROUTING

RIB-3-ECMP_ERR_ADD

3 ROUTING

RIB-3-ERR_ADD

3 ROUTING

RIB-3-ERR_CHILD_REDIST_REQUESTS

3 ROUTING

RIB-3-ERR_DELETE

3 ROUTING

RIB-3-ERR_LOCK_FATAL

3 ROUTING

RIB-3-ERR_LOOKUP

3 ROUTING

RIB-3-ERR_MEM_ALLOC

3 ROUTING

RIB-3-ERR_MEM_NHPATH

3 ROUTING

RIB-3-ERR_MUTEX_FATAL

3 ROUTING

RIB-3-ERR_NH_ATTRIBUTE

3 ROUTING

RIB-3-ERR_NH_PACK

3 ROUTING

RIB-3-ERR_NH_PATH

3 ROUTING

RIB-3-ERR_REDIST_INFO_CLEAR

3 ROUTING

RIB-3-ERR_RIBIO

3 ROUTING

RIB-3-ERR_RSI

3 ROUTING

RIB-3-ERR_TABLE_OPERATION

3 ROUTING

RIB-3-ERR_THREAD_POOL

3 ROUTING

RIB-3-EVENT_BOOLEAN_SET
RIB-3-GENERIC_ERROR

3 ROUTING
3 ROUTING

RIB-3-GO_ACTIVE

3 ROUTING

RIB-3-GO_STANDBY

3 ROUTING

RIB-3-IMPROPER_PREFIX_MASK_LEN

3 ROUTING

RIB-3-INTERFACE_DB

3 ROUTING

RIB-3-INVALID_BATCH_OPERATION

3 ROUTING

RIB-3-INVALID_BCDL_REGISTRATION

3 ROUTING

RIB-3-INVALID_TABLE_ACCESS

3 ROUTING

RIB-3-LABEL_ERR_ADD

3 ROUTING

RIB-3-LTRACE_INIT

3 ROUTING

RIB-3-LWM_REPLY

3 ROUTING

RIB-3-MAIN_INIT

3 ROUTING

RIB-3-MGMNT_INIT

3 ROUTING

RIB-3-NEXTHOPS_TRAVERSE

3 ROUTING

RIB-3-NH_CLIENT

3 ROUTING

RIB-3-NH_DB_ADD

3 ROUTING

RIB-3-NH_INSERT_HEAP

3 ROUTING

RIB-3-NSF_WARN

3 ROUTING

RIB-3-PREFIXES_FULL

3 ROUTING

RIB-3-PURGE_TIMER_ALLOC

3 ROUTING

RIB-3-QSM_ADD_SERVICE

3 ROUTING

RIB-3-RUMP_NOTIFY

3 ROUTING

RIB-3-SHUTDOWN
RIB-3-TIME_ERR

3 ROUTING
3 ROUTING

RIB-3-UPDATE_TIMEOUT

3 ROUTING

RIB-4-INVALID_SYSDB_ERROR

4 ROUTING

RIB-4-OPAQUE_FLAG_MISMATCH

4 ROUTING

RIB-4-PREFIXES_BELOW_THRESHOLD

4 ROUTING

RIB-4PREFIXES_REACHED_LOW_THRESHOLD

4 ROUTING

RIB-4-RECURSION_DEPTH_CHANGED

4 ROUTING

RIB-4-SELECT_IGNORED

4 ROUTING

RIB-4-SYSMGR_NODE_STATE

4 ROUTING

RIB-4-UNSUPPORTED_OOM_STATE

4 ROUTING

RIB-4-WARN_UNEXPECTED_EXT_COMM

4 ROUTING

RIB-5-TABLE_NH_DAMPED

5 ROUTING

RIB-6-INFO_LOCKING_CONTEXT_DISPLAY

6 ROUTING

RIB-7-INFO_LOCKING_OPERATION_DISPLAY

7 ROUTING

RIB-7-SERVER_ROUTING_DEPTH

7 ROUTING

RIB-7-SYSDB_FD_CLOSED

7 ROUTING

RIP_POLICY-3-ORA_INSTBUILD

3 ROUTING

RIP_POLICY-3-ORA_ORABUILD

3 ROUTING

RIP_POLICY-3-ORA_RUN

3 ROUTING

RIP-2-ERR_MEM_ALLOC

2 ROUTING

RIP-3-ERR_AUTH

3 ROUTING

RIP-3-ERR_CFG

3 ROUTING

RIP-3-ERR_CLEAR

3 ROUTING

RIP-3-ERR_EVENT

3 ROUTING

RIP-3-ERR_IF

3 ROUTING

RIP-3-ERR_INIT

3 ROUTING

RIP-3-ERR_ITAL

3 ROUTING

RIP-3-ERR_OOM

3 ROUTING

RIP-3-ERR_PAK_AUTH

3 ROUTING

RIP-3-ERR_PAK_RECV

3 ROUTING

RIP-3-ERR_POLICY

3 ROUTING

RIP-3-ERR_RDB

3 ROUTING

RIP-3-ERR_REDIST

3 ROUTING

RIP-3-ERR_RIB

3 ROUTING

RIP-3-ERR_THREAD_MUTEX_LOCK

3 ROUTING

RIP-3-ERR_THREAD_MUTEX_UNLOCK

3 ROUTING

RIP-3-ERR_TOPO

3 ROUTING

RIP-6-INFO_OOM

6 ROUTING

RPL_COORD-3-EVM_CREATE_FAIL

3 ROUTING

RPL_COORD-3-EVM_EVENT_BLOCK_FAIL

3 ROUTING

RPL_COORD-3-EVM_PROC_AVAILABLE_FAIL

3 ROUTING

RPL_COORD-3-EVM_PROC_READY_FAIL

3 ROUTING

RPL_COORD-3-GROUP_CREATE_FAIL

3 ROUTING

RPL_COORD-3-LWM_CHANNEL_FAIL

3 ROUTING

RPL_COORD-3-SW_CHANGE

3 ROUTING

RPL_COORD-4-BAD_GROUP_MSG

4 ROUTING

RPL_COORD-4-DEFAULT_ACTION_FAIL

4 ROUTING

RPL_COORD-4-DLL_CHECK_FAIL

4 ROUTING

RPL_COORD-4-DLL_LIST_FAIL

4 ROUTING

RPL_COORD-4-DLL_MANAGER_SETUP_FAIL

4 ROUTING

RPL_COORD-4-FIND_FILE_FAIL

4 ROUTING

RPL_COORD-4GROUP_COMPONENT_IGNORE

4 ROUTING

RPL_COORD-4-GROUP_MSG_LONG

4 ROUTING

RPL_COORD-4-GROUP_MSG_SHORT

4 ROUTING

RPL_COORD-4-INSTALL_READY_FAIL

4 ROUTING

RPL_COORD-4-MEM_ALLOC_FAIL

4 ROUTING

RPL_COORD-4-REBOOT_FAIL

4 ROUTING

RPL_COORD-7-DBGINIT

7 ROUTING

RPL_COORD-7GROUP_RESPONSE_UNEXPECTED

7 ROUTING

RPL_COORD-7-NO_NULL_TERM

7 ROUTING

RRR_PCALC-3-ERR_MEM_ALLOC

3 ROUTING

RRR_PCALC-3-ERR_MEM_ALLOC

3 ROUTING

RSVP-3CHKPT_XFORM_BUFFER_TOO_SMALL

3 ROUTING

RSVP-3-CHKPT_XFORM_INVALID_DIR

3 ROUTING

RSVP-3CHKPT_XFORM_UNSUPPORTED_TYPE

3 ROUTING

RSVP-3-CLIENT_QUEUE_OVERFLOW

3 ROUTING

RSVP-3-RSVP_LSP_RESOURCE_EXHAUSTED

3 ROUTING

RSVP-3-RSVP_TRACE_INIT_FAILED

3 ROUTING

RSVP-4-LATENCY_ABOVE_THRESHOLD

4 ROUTING

RSVP-4-SHUTDOWN

4 ROUTING

RSVP-5BAD_RSVP_MSG_RCVD_AUTH_DIGEST

5 ROUTING

RSVP-5-BAD_RSVP_MSG_RCVD_AUTH_DUP

5 ROUTING

RSVP-5-BAD_RSVP_MSG_RCVD_AUTH_KEY

5 ROUTING

RSVP-5-BAD_RSVP_MSG_RCVD_AUTH_SEQ

5 ROUTING

RSVP-5BAD_RSVP_MSG_RCVD_AUTH_TYPE_MISMAT
CH

5 ROUTING

RSVP-5-RSVP_AUTH_NO_KEYS

5 ROUTING

RSVP-6-LATENCY_BELOW_THRESHOLD

6 ROUTING

RSVP-6-RSVP_HELLO_STATE_DOWN

6 ROUTING

RSVP-6-RSVP_HELLO_STATE_UP

6 ROUTING

RUMP-2-ERR_MEM_ALLOC

2 ROUTING

RUMP-3-ERR_INIT

3 ROUTING

RUMP-3-ERR_SYSDB

3 ROUTING

RUMP-3-INTERNALERR

3 ROUTING

RUMP-3-RIB_FAIL

3 ROUTING

RUMP-6-GRACEFUL_RESTART

6 ROUTING

SAP_LISTEN-3-BAG_RELATED_FAILURE

3 ROUTING

SAP_LISTEN-3-EVENT_CONN_MGR_FAILURE

3 ROUTING

SAP_LISTEN-3-EVENT_MGR_CREATE_FAILED

3 ROUTING

SAP_LISTEN-3-GEN_FAIL

3 ROUTING

SAP_LISTEN-3-SOCKET_FAIL

3 ROUTING

SAP_LISTEN-3SYSDB_REGISTRATION_FAILED

3 ROUTING

TOPO-3-CTRACE_SERVER_INIT_FAILURE

3 ROUTING

TOPO-3-ERR_INET_NTOP

3 ROUTING

TOPO-3-ERR_INIT_MODULE

3 ROUTING

TOPO-3-ERR_MISSING_SERIAL_NUMBER
TOPO-3-ERR_PM_INIT

3 ROUTING
3 ROUTING

TOPO-3-MEMORY_ERROR

3 ROUTING

TOPO-5-OIR_ACTION

5 ROUTING

TOPO-5-PROCESS_UPDATE

5 ROUTING

TOPO-6-BAD_SVC_INFO

6 ROUTING

TOPO-6-ERR_ADD_SDR_TO_CARD

6 ROUTING

TOPO-6-ERR_CHUNK_CREATE

6 ROUTING

TOPO-6-ERR_RACK_LEAD_PUBLISH

6 ROUTING

TOPO-6-ERR_THREAD_START

6 ROUTING

TOPO-6-ERROR_THREAD_CREATE

6 ROUTING

TOPO-6-LEAD

6 ROUTING

TXLIB-3-ERR

3 ROUTING

UCP_LCTRL_LIB-3-ERR_LIB

3 ROUTING

UCP_LCTRL-7-ERR_INIT_SERVER

7 ROUTING

UCP_OLM-7-ACTIVE_IPCC_AVAIL

7 ROUTING

UCP_OLM-7-ERR_INTERNAL

7 ROUTING

UCP_OLM-7-LMP_ROUTER_ID_CHANGE

7 ROUTING

UCP_OLM-7-LMP_ROUTER_ID_ZERO

7 ROUTING

UCP_OLM-7MPLS_TE_LMP_ROUTER_ID_ZERO

7 ROUTING

UCP_OLM-7-NO_ACTIVE_IPCC

7 ROUTING

UCP_OLM-7-ROUTER_ID_ZERO

7 ROUTING

UCP_OUNI-4-OUNI_DEPRECATED

4 ROUTING

UCP_OUNI-6-CONNECTION_DESTROYED

6 ROUTING

UCP_OUNI-6-CONNECTION_ESTABLISHED

6 ROUTING

UCP_OUNI-7-ERR_INTERNAL

7 ROUTING

VKG_CPP_MCAST_GTRIE-3-INIT_FAILURE

3 ROUTING

VKG_CPP_MCAST_GTRIE-3LEAF_LOOKUP_FAILURE

3 ROUTING

VKG_CPP_MCAST_GTRIE-4-INIT_WARN

4 ROUTING

VKG_IPV4_MRIB-3-INIT_ERROR

3 ROUTING

VKG_MCAST_EDM-5-SYSDB_INIT_FAILURE

5 ROUTING

VKG_MCAST_EDM-7BAG_REGISTRY_FAILURE

7 ROUTING

VKG_MCAST_EDM-7EDM_REGISTER_FAILURE

7 ROUTING

VKG_MCAST_EDM-7-GEN_FAILURE

7 ROUTING

AAA_BASE-3-ERROR

3 SECURITY

AAA_BASE-4-WARNING

4 SECURITY

AAA_BASE-7-DEBUG

7 SECURITY

aaa_task-3-DEBUG_ERROR

3 SECURITY

aaa_task-3-DLLMAIN_ERROR

3 SECURITY

aaa_task-3INVALID_AAA_TASK_DEBUG_FLAG

3 SECURITY

aaa_task-7-GENERIC_ERROR

7 SECURITY

AAA-3-DEBUG_ERROR

3 SECURITY

AAA-3-DEBUG_ERROR

3 SECURITY

AAA-3-DES_INIT_FAIL

3 SECURITY

AAA-3-DLL_INIT_ERROR

3 SECURITY

AAA-3-DLLMAIN_ERROR

3 SECURITY

AAA-3-ERR_SERVER_GROUP

3 SECURITY

AAA-3-ERROR_NO_MEM

3 SECURITY

AAA-3-INVALID_DEBUG_FLAG

3 SECURITY

AAA-3-LIB_UTIL_ERROR_NO_MEM

3 SECURITY

AAA-3-SYSDB_BIND_ERROR

3 SECURITY

AAA-4WHITESPACE_TRUNCATED_IN_SERVER_KEY

4 SECURITY

AAA-7-ERR_ECM

7 SECURITY

AAA-7-ERR_SYSDB

7 SECURITY

ACCTD-3-AMBIGUOUS_PASSWD

3 SECURITY

ACCTD-3-BAG_ENCODE_ERR

3 SECURITY

ACCTD-3-BAGS_UNREG_ERR

3 SECURITY

ACCTD-3-DB_CLEAR_FAILED

3 SECURITY

ACCTD-3-DEBUG_ERROR

3 SECURITY

ACCTD-3-EDM_INIT_ERR

3 SECURITY

ACCTD-3-ERR_INVALID_GROUP

3 SECURITY

ACCTD-3-ERR_THREAD_FN

3 SECURITY

ACCTD-3-ERR_UNSUPPORTED_GROUP

3 SECURITY

ACCTD-3-INSUFFICIENT_BUFFER_SIZE

3 SECURITY

ACCTD-3-LIST_UNDEFINED

3 SECURITY

ACCTD-3-LWA_ADD_DIR_FAIL

3 SECURITY

ACCTD-3-LWA_ADD_FAIL

3 SECURITY

ACCTD-3-LWA_REM_FAIL

3 SECURITY

ACCTD-3-MEMORY

3 SECURITY

ACCTD-3-MSG_ERROR

3 SECURITY

ACCTD-3-MSG_SIZE_ERR

3 SECURITY

ACCTD-3-PLANE_MISMATCH

3 SECURITY

ACCTD-3-RED_STATE_ERROR

3 SECURITY

ACCTD-3-ROOT_USERDB_INIT_FAIL

3 SECURITY

ACCTD-3-ROOT_USERDB_LOCK_ERR

3 SECURITY

ACCTD-3-SETPRIO_FAILED

3 SECURITY

ACCTD-3-SHMWIN_INIT_FAILURE

3 SECURITY

ACCTD-3-SHUTDOWN_ERROR

3 SECURITY

ACCTD-3-SIGEVENT_SEND_FAIL

3 SECURITY

ACCTD-3-STARTUP_ERROR

3 SECURITY

ACCTD-3-STBY_INIT_ERR

3 SECURITY

ACCTD-4-ACCT_FAILURE

4 SECURITY

ACCTD-4-ACCT_TIMEOUT_FAILURE

4 SECURITY

ACCTD-4-CERR_REGISTER

4 SECURITY

ACCTD-4-CHKPT_REGISTER_FAILURE

4 SECURITY

ACCTD-4-CHKPT_RESTORE_FAILURE

4 SECURITY

ACCTD-4-CHKPT_SAVE_FAILURE

4 SECURITY

ACCTD-4-PASSWD_ALREADY_EXISTS

4 SECURITY

ACCTD-4-SECRET_ALREADY_EXISTS

4 SECURITY

ACCTD-7-ERR_SYSDB_FD

7 SECURITY

ACCTD-7-ERR_TTYMGMT_FD

7 SECURITY

ACCTD-7-GENERIC_ERROR
ACE_GRP-3-ERROR

ACE_LC-0-ACE_SYSLOG_EMERG

7 SECURITY
3 SECURITY

--

SECURITY

ACE_LC-1-ACE_SYSLOG_ALERT

1 SECURITY

ACE_LC-2-ACE_SYSLOG_CRIT

2 SECURITY

ACE_LC-3-ACE_SYSLOG_ERR

3 SECURITY

ACE_LC-3-ERR

3 SECURITY

ACE_LC-4-ACE_SYSLOG_WARNING

4 SECURITY

ACE_LC-4-WARNING
ACE_LC-5-ACE_SYSLOG_NOTICE
ACE_LC-6-ACE_SYSLOG_INFO
ACE_LC-6-INFO

4 SECURITY
5 SECURITY
6 SECURITY
6 SECURITY

ACE_QAD-3-ERR

3 SECURITY

ACE_TSB_LC-3-ERR

3 SECURITY

ACE_TSB_LC-6-INFO

6 SECURITY

ACE_TSB_LC-6-WARNING
ACE_TSB_LC-7-DEBUG

6 SECURITY
7 SECURITY

CEPKI-6-ERR

6 SECURITY

CEPKI-6-ERR_2

6 SECURITY

CEPKI-6-INFO

6 SECURITY

CEPKI-6-WARNING

6 SECURITY

COND_DEB_RP-3-INSUFMEM

3 SECURITY

COND_DEB_RP-3-NOCONDDBG

3 SECURITY

COND_DEB_RP-3-NOIPCONDDBG

3 SECURITY

COND_DEB_RP-6-ILLIPVAL

6 SECURITY

IKE_CLIENT-3-MQ_SEND_FAIL

3 SECURITY

IKE_CLIENT-4-WARNING

4 SECURITY

IKE-2-ERR_NO_MEMORY

2 SECURITY

IKE-3-ACCT_MSG_TX_FAILURE

3 SECURITY

IKE-3-ADD_KEY_FAIL

3 SECURITY

IKE-3-AUTHENTICATION_FAILED

3 SECURITY

IKE-3-BAD_CERT_USE

3 SECURITY

IKE-3-BAD_DOI_NOTIFY

3 SECURITY

IKE-3-BADMAGIC

3 SECURITY

IKE-3-CRYPTO_FAILURE

3 SECURITY

IKE-3-ERR_2_PARAM

3 SECURITY

IKE-3-ERR_EMPTY_SESSION

3 SECURITY

IKE-3-ERROR

3 SECURITY

IKE-3-FAILED_TO_CREATE_SKEYID

3 SECURITY

IKE-3-GROUP_AUTHOR_FAILED

3 SECURITY

IKE-3GROUP_CONFIG_UPLOAD_LOCAL_AAA_FAIL
ED

3 SECURITY

IKE-3-IKEINIT

3 SECURITY

IKE-3-INTF_PARAMS_FAILURE

3 SECURITY

IKE-3-INVALID_CERT

3 SECURITY

IKE-3IP_AP_NOTIFY_INUSE_ADDRESS_FAILED

3 SECURITY

IKE-3-IP_POOL_FREE_FAILURE

3 SECURITY

IKE-3-KEY_NOT_FOUND_IN_PROFILE

3 SECURITY

IKE-3-LOCAL_ADDRESS_FAILURE

3 SECURITY

IKE-3-MALFORMED_MESSAGE

3 SECURITY

IKE-3-MQ_FAIL

3 SECURITY

IKE-3-MQ_SEND_FAIL

3 SECURITY

IKE-3-NO_POLICY_FOUND

3 SECURITY

IKE-3-PACKET_PROCESS_FAILURE

3 SECURITY

IKE-3-PHASE2_PROPOSAL_NOT_CHOSEN

3 SECURITY

IKE-3-POLICY_MISMATCH

3 SECURITY

IKE-3-PRESHARED_KEY_NOT_FOUND

3 SECURITY

IKE-3-PROFILE_NOT_FOUND

3 SECURITY

IKE-3-QUICK_MODE_TIMER_EXPIRED

3 SECURITY

IKE-3-RADIUS_USER_AUTHEN_FAIL

3 SECURITY

IKE-3-RETRANSMISSION_LIMIT

3 SECURITY

IKE-3-RSA_PUBLIC_KEY_NOT_FOUND

3 SECURITY

IKE-3-SA_NOT_AUTH

3 SECURITY

IKE-3-SA_NOT_OFFERED

3 SECURITY

IKE-3-USER_AUTHEN_REJECTED

3 SECURITY

IKE-4-BAD_DOI_SA

4 SECURITY

IKE-4-CERT_DOESNT_MATCH_ID

4 SECURITY

IKE-4-CERT_ISNT_TRUSTED_ROOT

4 SECURITY

IKE-4-INCOMING_PKT_TOO_BIG

4 SECURITY

IKE-4-IPV4_ROUTES_TOO_MANY

4 SECURITY

IKE-4-MESSAGE_NOT_PROCESSED

4 SECURITY

IKE-4-NO_SA

4 SECURITY

IKE-4-OUTGOING_PKT_TOO_BIG

4 SECURITY

IKE-4-PACKET_NOT_ENCRYPTED

4 SECURITY

IKE-4-PACKET_OVERFLOW

4 SECURITY

IKE-4-UNKNOWN_EXCHANGE_TYPE

4 SECURITY

IKE-4-UNRELIABLE_INFO_MSG

4 SECURITY

IKE-4-WARNING

4 SECURITY

IKE-4-WARNING2

4 SECURITY

IKE-6-CAC_DROPS

6 SECURITY

IKE-6-CRYPTO_TUNNEL_STATUS

6 SECURITY

IKE-6-DEFAULT_POLICY_ACCEPTED

6 SECURITY

IKE-6-IPSEC_REJECTED

6 SECURITY

IKE-6-MODE_FAILURE

6 SECURITY

IKEv2-3-ERROR

3 SECURITY

IKEv2-4-WARNING

4 SECURITY

IKEv2-4-WARNING2

4 SECURITY

IMP-3-CONFIG_ERR

3 SECURITY

IMP-3-FATAL_ERR

3 SECURITY

IMP-3-MQ_FAIL

3 SECURITY

IMP-3-SVI_TUNNEL_TYPE_ERR

3 SECURITY

IMP-4-MSG_WARN

4 SECURITY

IMP-6-PROC_READY

6 SECURITY

IPP-3-ERR_GENERAL

3 SECURITY

IPP-3-ERR_MALLOC

3 SECURITY

IPP-6-INFO_GENERAL

6 SECURITY

IPSEC-3-ERR

3 SECURITY

IPSEC-4-WARNING

4 SECURITY

IPSEC-6-INFO

6 SECURITY

KEYCHAIN-3-FATAL_ERR

3 SECURITY

KEYCHAIN-4-MSG_WARN

4 SECURITY

LOCALD-3-AMBIGUOUS_PASSWD

3 SECURITY

LOCALD-3-BAG_ENCODE_ERR

3 SECURITY

LOCALD-3-BAGS_UNREG_ERR

3 SECURITY

LOCALD-3-DB_CLEAR_FAILED

3 SECURITY

LOCALD-3-DEBUG_ERROR

3 SECURITY

LOCALD-3-EDM_INIT_ERR

3 SECURITY

LOCALD-3-ERR_FILE_OPEN

3 SECURITY

LOCALD-3-ERR_FILE_WRITE

3 SECURITY

LOCALD-3-ERR_INVALID_GROUP

3 SECURITY

LOCALD-3-ERR_THREAD_FN

3 SECURITY

LOCALD-3-ERR_UNSUPPORTED_GROUP

3 SECURITY

LOCALD-3-GENERIC_ERROR

3 SECURITY

LOCALD-3-INSUFFICIENT_BUFFER_SIZE

3 SECURITY

LOCALD-3-LIST_UNDEFINED

3 SECURITY

LOCALD-3-LWA_ADD_DIR_FAIL

3 SECURITY

LOCALD-3-LWA_ADD_FAIL

3 SECURITY

LOCALD-3-LWA_REM_FAIL

3 SECURITY

LOCALD-3-MEMORY

3 SECURITY

LOCALD-3-MSG_ERROR

3 SECURITY

LOCALD-3-MSG_SIZE_ERR

3 SECURITY

LOCALD-3-PLANE_MISMATCH

3 SECURITY

LOCALD-3-RED_STATE_ERROR

3 SECURITY

LOCALD-3-ROOT_USERDB_INIT_FAIL

3 SECURITY

LOCALD-3-ROOT_USERDB_LOCK_ERR

3 SECURITY

LOCALD-3-SETPRIO_FAILED

3 SECURITY

LOCALD-3-SHMWIN_INIT_FAILURE

3 SECURITY

LOCALD-3-SHUTDOWN_ERROR

3 SECURITY

LOCALD-3-SIGEVENT_SEND_FAIL

3 SECURITY

LOCALD-3-STARTUP_ERROR

3 SECURITY

LOCALD-3-STBY_INIT_ERR

3 SECURITY

LOCALD-4-ACCT_FAILURE

4 SECURITY

LOCALD-4-ACCT_TIMEOUT_FAILURE

4 SECURITY

LOCALD-4-CERR_REGISTER

4 SECURITY

LOCALD-4-CHKPT_REGISTER_FAILURE

4 SECURITY

LOCALD-4-CHKPT_RESTORE_FAILURE

4 SECURITY

LOCALD-4-CHKPT_SAVE_FAILURE

4 SECURITY

LOCALD-4-PASSWD_ALREADY_EXISTS

4 SECURITY

LOCALD-4-SECRET_ALREADY_EXISTS

4 SECURITY

LOCALD-7-ERR_SYSDB_FD

7 SECURITY

LOCALD-7-ERR_TTYMGMT_FD

7 SECURITY

login-3-DEBUG_ERROR

3 SECURITY

login-3-DLLMAIN_ERROR

3 SECURITY

login-3-INVALID_LOGIN_DEBUG_FLAG

3 SECURITY

login-3-NO_MEMORY

3 SECURITY

login-4-AUTHEN_FAILED

4 SECURITY

login-6-AUTHEN_SUCCESS

6 SECURITY

MPP-3-FATAL_ERR

3 SECURITY

MPP-4-MSG_WARN

4 SECURITY

MPP-6-MSG_INFO

6 SECURITY

PKI-6-ERR_1_PARAM

6 SECURITY

PKI-6-ERR_2_PARAM

6 SECURITY

PKI-6-LOG_INFO

6 SECURITY

RADIUSD-3-ACCT_NOTIFY_FAIL

3 SECURITY

RADIUSD-3-ACCT_NOTIFY_FAIL

3 SECURITY

RADIUSD-3-ADD_SYS_IP_ADDR_ATTR_ERR

3 SECURITY

RADIUSD-3-ADD_SYS_IP_ADDR_ATTR_ERR

3 SECURITY

RADIUSD-3-ADD_VSA_FAIL

3 SECURITY

RADIUSD-3-ADD_VSA_FAIL

3 SECURITY

RADIUSD-3-BAD_AVPAIR

3 SECURITY

RADIUSD-3-BAD_AVPAIR

3 SECURITY

RADIUSD-3-BAD_MSG_TYPE

3 SECURITY

RADIUSD-3-BAD_MSG_TYPE

3 SECURITY

RADIUSD-3-BAD_VSA_FORMAT_BIT

3 SECURITY

RADIUSD-3-BAD_VSA_FORMAT_BIT

3 SECURITY

RADIUSD-3-BAD_VSA_LENGTH

3 SECURITY

RADIUSD-3-BAD_VSA_LENGTH

3 SECURITY

RADIUSD-3-BAD_VSA_TYPE

3 SECURITY

RADIUSD-3-BAD_VSA_TYPE

3 SECURITY

RADIUSD-3-BAD_VSA_VENDOR

3 SECURITY

RADIUSD-3-BAD_VSA_VENDOR

3 SECURITY

RADIUSD-3-BAG_ENCODE_ERR

3 SECURITY

RADIUSD-3-BAG_ENCODE_ERR

3 SECURITY

RADIUSD-3-BAGS_UNREG_ERR

3 SECURITY

RADIUSD-3-BAGS_UNREG_ERR

3 SECURITY

RADIUSD-3-CONFIG_ERR

3 SECURITY

RADIUSD-3-CONFIG_ERR

3 SECURITY

RADIUSD-3-DEBUG_ERROR

3 SECURITY

RADIUSD-3-DEBUG_ERROR

3 SECURITY

RADIUSD-3-EDM_INIT_ERR

3 SECURITY

RADIUSD-3-EDM_INIT_ERR

3 SECURITY

RADIUSD-3-ERR_CREATE_SERVER_ENTRY

3 SECURITY

RADIUSD-3-ERR_CREATE_SERVER_ENTRY

3 SECURITY

RADIUSD-3-ERR_CREATESG

3 SECURITY

RADIUSD-3-ERR_CREATESG

3 SECURITY

RADIUSD-3-ERR_SET_SERVER_ENTRY

3 SECURITY

RADIUSD-3-ERR_SET_SERVER_ENTRY

3 SECURITY

RADIUSD-3-ERR_SYSDBBIND

3 SECURITY

RADIUSD-3-ERR_SYSDBBIND

3 SECURITY

RADIUSD-3-ERR_TTY_IFH_PRESENT

3 SECURITY

RADIUSD-3-ERR_TTY_IFH_PRESENT

3 SECURITY

RADIUSD-3EVENT_ASYNC_ATTACH_FAIL_ERR

3 SECURITY

RADIUSD-3EVENT_ASYNC_ATTACH_FAIL_ERR

3 SECURITY

RADIUSD-3-IP_ADDR_TOO_LONG_ERR

3 SECURITY

RADIUSD-3-IP_ADDR_TOO_LONG_ERR

3 SECURITY

RADIUSD-3-LOCKING

3 SECURITY

RADIUSD-3-LOCKING

3 SECURITY

RADIUSD-3-MEMORY

3 SECURITY

RADIUSD-3-MEMORY

3 SECURITY

RADIUSD-3-MSG_ERROR

3 SECURITY

RADIUSD-3-MSG_ERROR

3 SECURITY

RADIUSD-3-MSG_SIZE_ERR

3 SECURITY

RADIUSD-3-MSG_SIZE_ERR

3 SECURITY

RADIUSD-3-NOT_VSA

3 SECURITY

RADIUSD-3-NOT_VSA

3 SECURITY

RADIUSD-3-PARAMETER

3 SECURITY

RADIUSD-3-PARAMETER

3 SECURITY

RADIUSD-3-RIB_BIND_ERR

3 SECURITY

RADIUSD-3-RIB_BIND_ERR

3 SECURITY

RADIUSD-3-RIB_LOCAL_ADDRESS_ERR

3 SECURITY

RADIUSD-3-RIB_LOCAL_ADDRESS_ERR

3 SECURITY

RADIUSD-3-SERVER_MUTEX_INIT_FAILED

3 SECURITY

RADIUSD-3-SERVER_MUTEX_INIT_FAILED

3 SECURITY

RADIUSD-3-SETPRIO_FAILED

3 SECURITY

RADIUSD-3-SETPRIO_FAILED

3 SECURITY

RADIUSD-3-SHUTDOWN_ERROR

3 SECURITY

RADIUSD-3-SHUTDOWN_ERROR

3 SECURITY

RADIUSD-3-STARTUP_ERROR

3 SECURITY

RADIUSD-3-STARTUP_ERROR

3 SECURITY

RADIUSD-3-VSA_FORMAT_ERR1

3 SECURITY

RADIUSD-3-VSA_FORMAT_ERR1

3 SECURITY

RADIUSD-3-VSA_FORMAT_ERR2

3 SECURITY

RADIUSD-3-VSA_FORMAT_ERR2

3 SECURITY

RADIUSD-3-VSA_FORMAT_ERR3

3 SECURITY

RADIUSD-3-VSA_FORMAT_ERR3

3 SECURITY

RADIUSD-3-VSA_FORMAT_ERR4

3 SECURITY

RADIUSD-3-VSA_FORMAT_ERR4

3 SECURITY

RADIUSD-3-VSA_FORMAT_ERR5

3 SECURITY

RADIUSD-3-VSA_FORMAT_ERR5

3 SECURITY

RADIUSD-3-VSA_NOTFOUND

3 SECURITY

RADIUSD-3-VSA_NOTFOUND

3 SECURITY

RADIUSD-3-VSA_TABLE_ERROR

3 SECURITY

RADIUSD-3-VSA_TABLE_ERROR

3 SECURITY

RADIUSD-3ZERO_TIMER_REPEATEDLY_EXPIRING_ERRO
R

3 SECURITY

RADIUSD-3ZERO_TIMER_REPEATEDLY_EXPIRING_ERRO
R

3 SECURITY

RADIUSD-4-CERR_REGISTER

4 SECURITY

RADIUSD-4-CERR_REGISTER

4 SECURITY

RADIUSD-4-IFHANDLE_NULL

4 SECURITY

RADIUSD-4-IFHANDLE_NULL

4 SECURITY

RADIUSD-4-IP_ADDRESS_NOT_FOUND

4 SECURITY

RADIUSD-4-IP_ADDRESS_NOT_FOUND

4 SECURITY

RADIUSD-4-NO_IP_ADDRESS

4 SECURITY

RADIUSD-4-NO_IP_ADDRESS

4 SECURITY

RADIUSD-4-NOSUCH_INTF

4 SECURITY

RADIUSD-4-NOSUCH_INTF

4 SECURITY

RADIUSD-4-RADIUS_NOSERV

4 SECURITY

RADIUSD-4-RADIUS_NOSERV

4 SECURITY

RADIUSD-4-SRCINTF_NOTUP

4 SECURITY

RADIUSD-4-SRCINTF_NOTUP

4 SECURITY

RADIUSD-6-BAD_ATTR_LENGTH

6 SECURITY

RADIUSD-6-BAD_ATTR_LENGTH

6 SECURITY

RADIUSD-6-BAD_ATTR_TYPE

6 SECURITY

RADIUSD-6-BAD_ATTR_TYPE

6 SECURITY

RADIUSD-6-ERR_ACCT_ID

6 SECURITY

RADIUSD-6-ERR_ACCT_ID

6 SECURITY

RADIUSD-6-ERR_BAD_REPLY_ATTR

6 SECURITY

RADIUSD-6-ERR_BAD_REPLY_ATTR

6 SECURITY

RADIUSD-6-ERR_BAD_SESSID_ATTR

6 SECURITY

RADIUSD-6-ERR_BAD_SESSID_ATTR

6 SECURITY

RADIUSD-6-ERR_LEAFTIMER

6 SECURITY

RADIUSD-6-ERR_LEAFTIMER

6 SECURITY

RADIUSD-6-ERR_SOCKET_BIND_FAIL

6 SECURITY

RADIUSD-6-ERR_SOCKET_BIND_FAIL

6 SECURITY

RADIUSD-6-ERR_SOCKETFAIL

6 SECURITY

RADIUSD-6-ERR_SOCKETFAIL

6 SECURITY

RADIUSD-6-EVENT_CONN_DESTROY_FAILED

6 SECURITY

RADIUSD-6-EVENT_CONN_DESTROY_FAILED

6 SECURITY

RADIUSD-6-EVENT_CONN_INIT_FAILED

6 SECURITY

RADIUSD-6-EVENT_CONN_INIT_FAILED

6 SECURITY

RADIUSD-6-GOT_CISCO_VSA

6 SECURITY

RADIUSD-6-GOT_CISCO_VSA

6 SECURITY

RADIUSD-6-INTRFC_STATE_QUERY_FAILED

6 SECURITY

RADIUSD-6-INTRFC_STATE_QUERY_FAILED

6 SECURITY

RADIUSD-6-INVALID_AUTHOR_TYPE

6 SECURITY

RADIUSD-6-INVALID_AUTHOR_TYPE

6 SECURITY

RADIUSD-6-INVALID_VSA

6 SECURITY

RADIUSD-6-INVALID_VSA

6 SECURITY

RADIUSD-6-LEN_TOO_LONG

6 SECURITY

RADIUSD-6-LEN_TOO_LONG

6 SECURITY

RADIUSD-6-SNPRINTF_FAIL

6 SECURITY

RADIUSD-6-SNPRINTF_FAIL

6 SECURITY

RADIUSD-6-UNSUPPORTED_VENDOR

6 SECURITY

RADIUSD-6-UNSUPPORTED_VENDOR

6 SECURITY

RADIUSD-7-GENERIC_ERROR

7 SECURITY

RADIUSD-7-GENERIC_ERROR

7 SECURITY

SAM-3-ERR_COPY_CRL

3 SECURITY

SAM-3-ERR_DEL_CA_CERT

3 SECURITY

SAM-3-ERR_FILE_MD5

3 SECURITY

SAM-3-ERR_INVALID_DEVICE

3 SECURITY

SAM-3-ERR_NO_DIGESTINDEX_VALUE

3 SECURITY

SAM-3-ERR_NO_MEMORY

3 SECURITY

SAM-3-ERR_OPEN_FILE

3 SECURITY

SAM-3-ERR_REG_MSGNO

3 SECURITY

SAM-3-ERR_RESTORE_LOG_ENCODE

3 SECURITY

SAM-3-ERR_SYSDB_GET

3 SECURITY

SAM-3-ERR_SYSDB_SET

3 SECURITY

SAM-3-ERR_WR_FILE

3 SECURITY

SAM-3-WARN_NVRAM

3 SECURITY

SAM-3-WARN_SPM

3 SECURITY

SAM-4-CAUGHT_SIGNAL

4 SECURITY

SAM-4-NO_BACKUP_LOG

4 SECURITY

SAM-4-SYSDB_INTEGRITY

4 SECURITY

SAM-4-WARN_CA_CERT_EXPIRED

4 SECURITY

SAM-4-WARN_CSS_CERT_EXPIRED

4 SECURITY

SAM-6-ERR_1_PARAM

6 SECURITY

SAM-6-ERR_2_PARAM

6 SECURITY

SAM-6-WARN_CHANGE_NOT_PERSISTENT

6 SECURITY

SAM-6-WARN_DIGEST_FILE_MISSING

6 SECURITY

SAM-6-WARN_DIGEST_FILE_REINIT

6 SECURITY

SAM-6-WARN_INIT_LOG_BACKUP_FILE

6 SECURITY

SAM-6-WARN_MEM_DIGEST

6 SECURITY

SAM-6-WARNING

6 SECURITY

SAM-6-WARNING_INSECURE_FLASH_FILE

6 SECURITY

SAM-6-WARNING_UNMATCH_DIGEST

6 SECURITY

SANOS-0-FW_ADMIN_EMERG

--

SECURITY

SANOS-0-FW_APP_EMERG

--

SECURITY

SANOS-0-FW_KERNEL_EMERG

--

SECURITY

SANOS-1-FW_ADMIN_ALERT

1 SECURITY

SANOS-1-FW_APP_ALERT

1 SECURITY

SANOS-1-FW_KERNEL_ALERT

1 SECURITY

SANOS-2-FW_ADMIN_CRIT

2 SECURITY

SANOS-2-FW_APP_CRIT

2 SECURITY

SANOS-2-FW_KERNEL_CRIT

2 SECURITY

SANOS-3-BOOT_LOAD_ERR

3 SECURITY

SANOS-3-CLOCK_UPDATE_FAIL

3 SECURITY

SANOS-3-EVENT

3 SECURITY

SANOS-3-FW_ADMIN_ERR

3 SECURITY

SANOS-3-FW_APP_ERR

3 SECURITY

SANOS-3-FW_KERNEL_ERR

3 SECURITY

SANOS-3-INIT

3 SECURITY

SANOS-4-ATTACH_INIT

4 SECURITY

SANOS-4-BOOT_IMAGE_ERR

4 SECURITY

SANOS-4-CONNECT

4 SECURITY

SANOS-4-FW_ADMIN_WARNING

4 SECURITY

SANOS-4-FW_APP_WARNING

4 SECURITY

SANOS-4-FW_KERNEL_WARNING

4 SECURITY

SANOS-4-IPCP

4 SECURITY

SANOS-4-IPCP_INVALID_ATTACH_MSG

4 SECURITY

SANOS-4-IPCP_INVALID_SYSLOG_MSG

4 SECURITY

SANOS-5-FW_ADMIN_NOTICE

5 SECURITY

SANOS-5-FW_APP_NOTICE

5 SECURITY

SANOS-5-FW_KERNEL_NOTICE

5 SECURITY

SANOS-6-BOOT_IMAGE_STATUS
SANOS-6-BOOT_LOAD_STATUS

6 SECURITY
6 SECURITY

SANOS-6-FW_ADMIN_INFO

6 SECURITY

SANOS-6-FW_APP_INFO

6 SECURITY

SANOS-6-FW_KERNEL_INFO

6 SECURITY

SANOS-7-FW_ADMIN_DEBUG

7 SECURITY

SANOS-7-FW_APP_DEBUG

7 SECURITY

SANOS-7-FW_KERNEL_DEBUG

7 SECURITY

sIMP-3-FATAL_ERR

3 SECURITY

sIMP-4-ITI_WARN

4 SECURITY

sIMP-4-MSG_WARN

4 SECURITY

SPM-3-ERR_CHAN_CONNECT

3 SECURITY

SPM-3-ERR_ENTRY_FIND

3 SECURITY

SPM-3-ERR_INVALID_EVENT

3 SECURITY

SPM-3-ERR_MALLOC

3 SECURITY

SPM-3-ERR_MSG_GEN

3 SECURITY

SPM-3-ERR_OPEN_SECURE

3 SECURITY

SPM-3-ERR_PTHREAD_CREATE

3 SECURITY

SPM-3-ERR_PTHREAD_INIT

3 SECURITY

SPM-3-ERR_PTHREAD_SET

3 SECURITY

SPM-3-ERR_PULSE_CODE

3 SECURITY

SPM-3-ERR_REG_HANDLER

3 SECURITY

SPM-3-ERR_REG_MSG

3 SECURITY

SPM-3-ERR_REPLY_FAIL

3 SECURITY

SPM-3-ERR_TOKEN_MISMATCH

3 SECURITY

SSHD-3-ERR_DETAILS

3 SECURITY

SSHD-3-ERR_ERRNO

3 SECURITY

SSHD-3-ERR_GENERAL

3 SECURITY

SSHD-3-ERR_MALLOC

3 SECURITY

SSHD-3-ERR_SYSDB_BIND

3 SECURITY

SSHD-3-ERR_SYSDB_DATALIST

3 SECURITY

SSHD-3-ERR_SYSDB_DELETE

3 SECURITY

SSHD-3-ERR_SYSDB_PACK

3 SECURITY

SSHD-3-ERR_SYSDB_SET

3 SECURITY

SSHD-4-INFO_FAILURE

4 SECURITY

SSHD-4-WARNING_LOGIN

4 SECURITY

SSHD-6-INFO_GENERAL

6 SECURITY

SSHD-6-INFO_SUCCESS

6 SECURITY

SSHD-6-INFO_SUCCESS_COMMAND

6 SECURITY

TACACSD-3-BAG_ENCODE_ERR

3 SECURITY

TACACSD-3-BAGS_UNREG_ERR

3 SECURITY

TACACSD-3-DEBUG_ERROR

3 SECURITY

TACACSD-3-EDM_INIT_ERR

3 SECURITY

TACACSD-3-ERR_ATTACH_SOCK

3 SECURITY

TACACSD-3-ERR_CONFIG_GLOBAL

3 SECURITY

TACACSD-3-ERR_CONFIG_SERVER

3 SECURITY

TACACSD-3-ERR_CREATE_SERVER_ENTRY

3 SECURITY

TACACSD-3-ERR_CREATE_SGSERVER

3 SECURITY

TACACSD-3-ERR_CREATESG

3 SECURITY

TACACSD-3-ERR_DELETE_SGSERVER

3 SECURITY

TACACSD-3-ERR_DELETESG

3 SECURITY

TACACSD-3-ERR_SYSDBBIND

3 SECURITY

TACACSD-3-MEMORY

3 SECURITY

TACACSD-3-MSG_ERROR

3 SECURITY

TACACSD-3-MSG_SIZE_ERR

3 SECURITY

TACACSD-3-PARAMETER

3 SECURITY

TACACSD-3PROBE_THREAD_CREATE_FAILED

3 SECURITY

TACACSD-3-SETPRIO_FAILED

3 SECURITY

TACACSD-3-SHUTDOWN_ERROR

3 SECURITY

TACACSD-3-STARTUP_ERROR

3 SECURITY

TACACSD-4-CERR_REGISTER

4 SECURITY

TACACSD-4-IFHANDLE_NULL

4 SECURITY

TACACSD-4-NO_IP_ADDRESS

4 SECURITY

TACACSD-4-NOSUCH_INTF

4 SECURITY

TACACSD-4-SRCINTF_NOTUP

4 SECURITY

TACACSD-4-TACACS_NOSERV

4 SECURITY

TACACSD-4-WRONG_KEY

4 SECURITY

TACACSD-6-NO_CMD

6 SECURITY

TACACSD-6-NULL_REQ

6 SECURITY

TACACSD-6-SERVER_DOWN

6 SECURITY

TACACSD-6-SERVER_UP

6 SECURITY

TACACSD-6-TIMEOUT_IGNORED

6 SECURITY

TACACSD-7-GENERIC_ERROR

7 SECURITY

VFW-3-FAA_FA_CB

3 SECURITY

VFW-3-FMI_NETIO_DROPPED_PACKETS

3 SECURITY

VFW-3-FWC_AVL_DELETE_FAILED

3 SECURITY

VFW-3-FWC_DB_CREATE_FAIL

3 SECURITY

VFW-3-FWC_FWS_CFG_UPDATE_FAIL

3 SECURITY

VFW-3-FWC_FWS_FW_NOTFOUND

3 SECURITY

VFW-3-FWC_INIT

3 SECURITY

VFW-3-FWC_INTF_FW_NOTFOUND

3 SECURITY

VFW-3-FWC_SPU_CLEAR_FAIL

3 SECURITY

VFW-3-FWC_SSC_UPDATE_FAIL

3 SECURITY

VFW-3-FWC_WAVL_DELETE_FAILED

3 SECURITY

VFW-3-FWM_INIT

3 SECURITY

VFW-4-EXITING

4 SECURITY

VFW-4-FWC_CONFIG_ERR

4 SECURITY

VFW-4-FWC_EVENT_CONN_ERROR_FAIL

4 SECURITY

VFW-4-FWC_FMI_IFH_MISMATCH

4 SECURITY

VFW-4-FWC_FMI_INFO_UPDATE

4 SECURITY

VFW-4-FWC_FW_APP_BAD_VERSION

4 SECURITY

VFW-4-FWC_FW_APP_RECV_FAILED

4 SECURITY

VFW-4-FWC_INTF_DB_INFO_ALREADY_SET

4 SECURITY

VFW-4-FWC_INTF_IFH_MISMATCH

4 SECURITY

VFW-4-FWC_REMOVE_ATTACHMENT

4 SECURITY

VFW-4-LOST_EVENT

4 SECURITY

VFW-6-FMI_CONFLICTING_CONFIG

6 SECURITY

CGN-3-APP_INTF

3 SERVICES

CGN-3-APP_INTF

3 SERVICES

CGN-3-APP_INTF_INCON

3 SERVICES

CGN-3-APP_INTF_INCON

3 SERVICES

CGN-3-APP_INTF_INST

3 SERVICES

CGN-3-APP_INTF_INST

3 SERVICES

CGN-3-CORE_FAIL

3 SERVICES

CGN-3-CORE_FAIL
CGN-3-EA_FAIL
CGN-3-EA_FAIL

3 SERVICES
3 SERVICES
3 SERVICES

CGN-3-INITFAIL

3 SERVICES

CGN-3-INITFAIL

3 SERVICES

CGN-3-INVALID_IP

3 SERVICES

CGN-3-INVALID_IP

3 SERVICES

CGN-3-LWM_FAIL

3 SERVICES

CGN-3-LWM_FAIL
CGN-3-MSGQ_FAIL
CGN-3-MSGQ_FAIL

3 SERVICES
3 SERVICES
3 SERVICES

CGN-3-RODDICK_UPD_FAIL

3 SERVICES

CGN-3-RODDICK_UPD_FAIL

3 SERVICES

CGN-3-SD_FAIL

3 SERVICES

CGN-3-SD_FAIL

3 SERVICES

CGN-3-STATPORT_MAP

3 SERVICES

CGN-3-STATPORT_MAP

3 SERVICES

CGN-3-VRF_DB_UPD_FAIL

3 SERVICES

CGN-3-VRF_DB_UPD_FAIL

3 SERVICES

CGN-4-ERR_MEM

4 SERVICES

CGN-4-ERR_MEM

4 SERVICES

CGN-7-CHKPT_INIT

7 SERVICES

CGN-7-CHKPT_INIT

7 SERVICES

CGN-7-CHKPT_NULL_PTR

7 SERVICES

CGN-7-CHKPT_NULL_PTR

7 SERVICES

CGN-7-CHKPT_TBL_ADD

7 SERVICES

CGN-7-CHKPT_TBL_ADD

7 SERVICES

CGN-7-CHKPT_TBL_INIT

7 SERVICES

CGN-7-CHKPT_TBL_INIT

7 SERVICES

CGN-7-CHKPT_TBL_RECOVER

7 SERVICES

CGN-7-CHKPT_TBL_RECOVER

7 SERVICES

CGN-7-CHKPT_TBL_REMOVE

7 SERVICES

CGN-7-CHKPT_TBL_REMOVE

7 SERVICES

CGN-7-CHKPT_TBL_RESET

7 SERVICES

CGN-7-CHKPT_TBL_RESET

7 SERVICES

CGN-7-ERR_SYSDB

7 SERVICES

CGN-7-ERR_SYSDB

7 SERVICES

IFLX_LIB_EA-3-ADJACENCY

3 SERVICES

IFLX_LIB_EA-3-INITFAIL

3 SERVICES

IFLX_LIB_EA-3-SSC_SEND

3 SERVICES

IFLX_LIB_EA-3-SSC_SEND_BATCH_END

3 SERVICES

IFLX_LIB_EA-3-SSC_SEND_SRV

3 SERVICES

IFLX_LIB_EA-3-UNABLE_TO_RESYNC

3 SERVICES

IFLX_LIB_MGR-3-INTF_CREATE_FAIL

3 SERVICES

IFLX_LIB_MGR-3-INTF_DB_DEL_ERR

3 SERVICES

IFLX_LIB_MGR-3-INTF_DPC_REMOVE_ERR

3 SERVICES

IFLX_LIB_MGR-3-PTFM_BW_ERR

3 SERVICES

IFLX_LIB_MGR-3-PTFM_CARD_TYPE_ERR

3 SERVICES

IFLX_LIB_MGR-3-PTFM_MAX_INTF_ERR

3 SERVICES

IFLX_LIB_MGR-3-PTFM_NODEID_ERR

3 SERVICES

IFLX_LIB_MGR-4-UNABLE_TO_RESYNC

4 SERVICES

IFLX_LIB_MGR-6NOT_ENOUGH_MAC_ADDRESSES

6 SERVICES

IFLX_LIB_MGR-6NOT_ENOUGH_MAC_ADDRESSES_RESYNC

6 SERVICES

IPSEC_SVI_EA-3-INITFAIL

3 SERVICES

IPSEC_SVI_EA-3-INTERNAL

3 SERVICES

IPSEC_SVI_EA-3-INTERNAL_ERR

3 SERVICES

IPSEC_SVI_EA-3-LINK_FAIL

3 SERVICES

IPSEC_SVI_EA-3-NOT_FOUND

3 SERVICES

IPSEC_SVI_EA-3-SSC_SEND

3 SERVICES

IPSEC_SVI_EA-3-SSC_SEND_SRV

3 SERVICES

IPSEC_SVI_EA-3-STATE_CHANGE

3 SERVICES

IPSEC_SVI_NETIO-3-INIT_DEBUG

3 SERVICES

IPSEC_SVI_NETIO-3-INIT_TRACE

3 SERVICES

OT-3-ERROR

3 SERVICES

OT-3-ERROR

3 SERVICES

OT-3-ERROR

3 SERVICES

OT-4-WARNING

4 SERVICES

OT-4-WARNING

4 SERVICES

OT-4-WARNING

4 SERVICES

OT-6-TRACK_INFO

6 SERVICES

OT-6-TRACK_INFO

6 SERVICES

OT-6-TRACK_INFO

6 SERVICES

OT-7-SYSDB_FAIL

7 SERVICES

PERF_TRAFFIC_ALERT_CLONE-1QUEUE_FULL

1 SERVICES

PERF_TRAFFIC_ALERT_NETFLOW-1-NOT_UP

1 SERVICES

PERF_TRAFFIC_ALERT-0-ALM_EMERG

--

SERVICES

PERF_TRAFFIC_ALERT-0-GRP_ALM_EMERG

--

SERVICES

PERF_TRAFFIC_ALERT-1-ALM_ALERT

1 SERVICES

PERF_TRAFFIC_ALERT-1-GRP_ALM_ALERT

1 SERVICES

PERF_TRAFFIC_ALERT-2-ALM_CRIT

2 SERVICES

PERF_TRAFFIC_ALERT-2-GRP_ALM_CRIT

2 SERVICES

PERF_TRAFFIC_ALERT-3-ALM_ERR

3 SERVICES

PERF_TRAFFIC_ALERT-3-GRP_ALM_ERR

3 SERVICES

rspp_drop-3-DEBUG

3 SERVICES

rspp_drop-3-DIVERT

3 SERVICES

rspp_drop-3-INIT

3 SERVICES

rspp_drop-3-UNDIVERT

3 SERVICES

RSPP_MA-2-IMP_FAILED

2 SERVICES

RSPP_MA-3-EVENT

3 SERVICES

RSPP_MA-3-IMP_ERROR

3 SERVICES

RSPP_MA-3-INIT

3 SERVICES

RSPP_MA-3-INIT_NON_FATAL

3 SERVICES

RSPP_MA-3-LCFG_DELETE

3 SERVICES

RSPP_MA-3-LCFG_UPDATE

3 SERVICES

RSPP_MA-3-NO_VFW

3 SERVICES

RSPP_MA-3-PUBLISH_DELETE

3 SERVICES

RSPP_MA-3-PUBLISH_UPDATE

3 SERVICES

RSPP_MA-3-RCFG

3 SERVICES

RSPP_MA-3-RCFG_REFRESH

3 SERVICES

RSPP_MA-4-DUP_CREATE

4 SERVICES

RSPP_MA-4-DUP_CREATE_ERR

4 SERVICES

RSPP_MA-4-DUP_REMOVE

4 SERVICES

RSPP_MA-4-DUP_REMOVE_ERR

4 SERVICES

RSPP_MA-4-FA_BATCH_ERR

4 SERVICES

RSPP_MA-4-RCFG_BATCH

4 SERVICES

RSPP_MA-4-RED_STATE_ERR

4 SERVICES

RSPP_MA-4-RED_STATE_UNK

4 SERVICES

RSPP_MA-4-RESYNC_FAILED

4 SERVICES

RSPP_MA-4-SD_BATCH_ERR

4 SERVICES

RSPP_MA-4-SD_ERR

4 SERVICES

RSPP_MA-6-IMP_ERROR_CLEARED

6 SERVICES

RSPP_MA-6-PROBLEM_EXITING

6 SERVICES

RSPP_REPO-3-DUAL_ERR

3 SERVICES

RSPP_REPO-3-INIT

3 SERVICES

RSPP_REPO-3-INIT_MSG

3 SERVICES

RSPP_REPO-3-TWEAK_ERR

3 SERVICES

RSPP_REPO-3-UPDATE_MSG

3 SERVICES

RSPP_REX-3-EDM

3 SERVICES

RSPP_REX-3-IMP_CONNECT

3 SERVICES

RSPP_REX-3-INIT

3 SERVICES

RSPP_REX-3-MEM

3 SERVICES

RSPP_REX-3-MSG_REPLY

3 SERVICES

RSPP_REX-3-SYSDB

3 SERVICES

RSPP_REX-6-CORE

6 SERVICES

RSPP_RIO_EA-3-DEBUG

3 SERVICES

RSPP_RIO_EA-3-DM_REMOVE

3 SERVICES

RSPP_RIO_EA-3-EDM

3 SERVICES

RSPP_RIO_EA-3-EVENT_BLOCK

3 SERVICES

RSPP_RIO_EA-3-EVM_CREATE_FAILED

3 SERVICES

RSPP_RIO_EA-3-FM_INIT_REPLAY

3 SERVICES

RSPP_RIO_EA-3-IMP_INIT_ERR

3 SERVICES

RSPP_RIO_EA-3-INIT_FAILED

3 SERVICES

RSPP_RIO_EA-3-MEM

3 SERVICES

RSPP_RIO_EA-3-TRACE

3 SERVICES

RSPP_RIO_EA-3-UTIL_ASSERT

3 SERVICES

RSPP_RIO_EA-6-CORE

6 SERVICES

rspp_rio_netio-3-CAPS_BUILDER_FAILED

3 SERVICES

rspp_rio_netio-3-CAPS_CONTROL_FAILED

3 SERVICES

rspp_rio_netio-3-CAPS_UNBUILDER_FAILED

3 SERVICES

rspp_rio_netio-3-INIT_DEBUG

3 SERVICES

rspp_rio_netio-3-INIT_TRACE

3 SERVICES

rspp_rio_netio-3-SUBBLOCK_REG_FAILED

3 SERVICES

rspp_rio_netio-3-TERM_FAILED

3 SERVICES

RSPP_ROXI-3-IMP_CONNECT

3 SERVICES

RSPP_ROXI-3-INIT

3 SERVICES

RSPP_ROXI-3-MEM

3 SERVICES

RSPP_ROXI-3-REPLICATE

3 SERVICES

SBC_MPF-6-INFO

6 SERVICES

SBC_PROC-6-INFO

6 SERVICES

SBC_RSRCMON-1-ALERT

1 SERVICES

SBC_RSRCMON-4-WARNING

4 SERVICES

SBC_RSRCMON-6-INFO

6 SERVICES

SBC_RSRCMON-7-DEBUG

7 SERVICES

SBC-1-L1

1 SERVICES

SBC-2-L2

2 SERVICES

SBC-3-L3

3 SERVICES

SBC-6-L6

6 SERVICES

SBCSVI_BILLING-3-CONFERR

3 SERVICES

SBCSVI_BILLING-3-PATHERR

3 SERVICES

SBCSVI_BILLING-4-PATHWARN

4 SERVICES

SBCSVI_BILLING-5-PATHSTATUS

5 SERVICES

SBCSVI_EA-3-INITFAIL

3 SERVICES

SBCSVI_EA-3-INTERNAL

3 SERVICES

SBCSVI_EA-3-INTERNAL_ERR

3 SERVICES

SBCSVI_EA-3-LINK_FAIL

3 SERVICES

SBCSVI_EA-3-NOT_FOUND

3 SERVICES

SBCSVI_EA-3-SSC_SEND

3 SERVICES

SBCSVI_EA-3-SSC_SEND_SRV

3 SERVICES

SBCSVI_EA-3-STATE_CHANGE

3 SERVICES

SBCSVI_NETIO-3-INIT_DEBUG

3 SERVICES

SBCSVI_NETIO-3-INIT_TRACE

3 SERVICES

SD_COMMON-3-SEND_FAILED

3 SERVICES

SD-3-ASSERT

3 SERVICES

SD-3-INIT_FAILED

3 SERVICES

SD-3-LOOP_FAILED

3 SERVICES

SD-3-NOMEM

3 SERVICES

SD-3-SYSMGR_FAIL

3 SERVICES

SD-4-INVALID_FIND_SERVICE

4 SERVICES

SD-4-WRONG_SSC

4 SERVICES

SD-6-RESTART_SELF

6 SERVICES

SE_INFRA_MGR-3-BIND_FAIL

3 SERVICES

SE_INFRA_MGR-3-EVENT_FAIL

3 SERVICES

SE_INFRA_MGR-3-INVALID

3 SERVICES

SE_INFRA_MGR-3-SYSDB_FAIL

3 SERVICES

SE_INFRA_SECONTROLLER-3-DEBUG_FAIL

3 SERVICES

SE_INFRA_SECONTROLLER-6-INFO

6 SERVICES

SESVI_EA-3-INITFAIL

3 SERVICES

SESVI_EA-3-INTERNAL

3 SERVICES

SESVI_EA-3-INTERNAL_ERR

3 SERVICES

SESVI_EA-3-LINK_FAIL

3 SERVICES

SESVI_EA-3-NOT_FOUND

3 SERVICES

SESVI_EA-3-OPERATION_FAIL

3 SERVICES

SESVI_EA-3-SSC_SEND

3 SERVICES

SESVI_EA-3-SSC_SEND_SRV

3 SERVICES

SESVI_EA-3-STATE_CHANGE

3 SERVICES

SESVI_EA-6-INFO

6 SERVICES

SESVI_NETIO-3-INIT_DEBUG

3 SERVICES

SESVI_NETIO-3-INIT_TRACE

3 SERVICES

SI-3-ERR_MEM

3 SERVICES

SI-3-ERR_SYSDB

3 SERVICES

SI-3-INITFAIL

3 SERVICES

SI-3-INTERNAL

3 SERVICES

SI-3-SD_FAIL

3 SERVICES

SRD_AGENT-6-NODE_REBOOTING

6 SERVICES

SRD_LIB-4-NOTIFICATION_FAILED

4 SERVICES

SRD-3-ASSERT

3 SERVICES

SRD-3-INIT_FAILED

3 SERVICES

SRD-3-LOOP_FAILED

3 SERVICES

SRD-3-NOMEM

3 SERVICES

SRD-4-CARD_NOT_PRESENT

4 SERVICES

SRD-4-ERROR_PROCESSING_LRD_EVENT

4 SERVICES

SRD-4-ERROR_STARTING_AGENT

4 SERVICES

SRD-4-MISSING_TIMER_CONTEXT

4 SERVICES

SVII_EA_GSR-3-INTF_EXIST

3 SERVICES

SVII_EA_GSR-3-INTF_EXIST

3 SERVICES

SVII_EA_GSR-3-NOMEM

3 SERVICES

SVII_EA_GSR-3-NOMEM

3 SERVICES

SVII_EA_STATS-3-CHKPT_GET_FAILURE

3 SERVICES

SVII_EA-3-EVENT

3 SERVICES

SVII_EA-3-FORWARDER_CONNECTION

3 SERVICES

SVII_EA-3-INIT

3 SERVICES

SVII_EA-3-SEND_FAILED

3 SERVICES

SVII_EA-3-SYSMGR

3 SERVICES

SVII_EA-3-UNABLE_TO_RECONNECT

3 SERVICES

SVII_LRD_SPA-3-STATE_UPDATE

3 SERVICES

SVII_MGR-3-ACTIVATE

3 SERVICES

SVII_MGR-3-EVENT

3 SERVICES

SVII_MGR-3-EVM_CREATE

3 SERVICES

SVII_MGR-3-EXITING

3 SERVICES

SVII_MGR-3-INIT

3 SERVICES

SVII_MGR-3-SEND_FAILED

3 SERVICES

SVII_MGR-3-SYSMGR

3 SERVICES

SVII_MGR-3-UNABLE_TO_RECONNECT

3 SERVICES

SVII_MGR-3-UNABLE_TO_RESYNC

3 SERVICES

VASI_EA-3-ADJACENCY

3 SERVICES

VASI_EA-3-INITFAIL

3 SERVICES

VASI_EA-3-LINK_FAIL

3 SERVICES

VASI_EA-3-NOT_FOUND

3 SERVICES

VASI_EA-3-SSC_SEND

3 SERVICES

VASI_EA-3-SSC_SEND_SRV

3 SERVICES

VASI_EA-3-STATE_CHANGE

3 SERVICES

VASI_MA-3-INIT

3 SERVICES

VASI_MA-3-INTF_CREATE_FAIL

3 SERVICES

VASI_MA-3-INTF_CREATE_FAIL_CLEANUP

3 SERVICES

VASI_NETIO-3-DROPPED_PACKETS

3 SERVICES

VASI_NETIO-3-INIT_DEBUG

3 SERVICES

VASI_NETIO-3-INIT_TRACE

3 SERVICES

AFMONMIB-3-ERR_MEM_ALLOC

3 SNMP

AFMONMIB-3-ERR_MUTEX

3 SNMP

ATM_MIB-3-INIT_ERR

3 SNMP

ATMSNMP-3-IFMGR
ATMSNMP-3-info

3 SNMP
3 SNMP

ATMSNMP-3-SYSDB

3 SNMP

BULKFILEMIB-3-MEM_ALLOC

3 SNMP

BULKFILEMIB-3-THREAD_CREATE

3 SNMP

CBQOSMIB-3-MEM_ALLOC

3 SNMP

CBQOSMIB-3-MUTEX

3 SNMP

CBQOSMIB-4-ERR_BLOCK

4 SNMP

CISCOBGPPAMIB-3-ERR_MEM_ALLOC

3 SNMP

CISCOPROCESSMIB-3-ERR_MEM_ALLOC

3 SNMP

CISCOSYSTEMMIB-3-CLOCK

3 SNMP

CISCOSYSTEMMIB-3-SPAWN

3 SNMP

CISCOSYSTEMMIB-3-SYSDB_ACCESS

3 SNMP

CISCOSYSTEMMIB-3-TARGET_CFG_PROBLEM

3 SNMP

CISCOSYSTEMMIB-3-TIMER

3 SNMP

CISCOSYSTEMMIB-7-CREATE_EVM

7 SNMP

COPYMIB-3-ENTRYNONE

3 SNMP

COPYMIB-3-ERR_MEM_ALLOC

3 SNMP

CSCMIB-7-CSC_ASSERT

7 SNMP

CSCMIB-7-CSC_BAG

7 SNMP

CSCMIB-7-CSC_OCTETSTRING

7 SNMP

CSCMIB-7-CSC_SNMP

7 SNMP

CSCMIB-7-INVALID_ARG

7 SNMP

CSCMIB-7-NOMEM

7 SNMP

CSCMIB-7-SYSDB_ACCESS

7 SNMP

CSCMIB-7-SYSDB_BIND

7 SNMP

ENTITYMIB-3-INIT_ERROR

3 SNMP

FTPCLIENTMIB-3-NOMEM

3 SNMP

FTPCLIENTMIB-3-NOTHREADCREATE

3 SNMP

HSRPMIB-3-ERR_CONN

3 SNMP

HSRPMIB-4-WARN_DEBUG

4 SNMP

HSRPMIB-4-WARN_NOTIFY

4 SNMP

HSRPMIB-4-WARN_OID

4 SNMP

IFINDEX_PROVIDER-3-DUPLICATE_INDEX

3 SNMP

IFINDEX_PROVIDER-3INTERFACE_INDEX_PERSISTENCE_PARTIAL_
RESTORE

3 SNMP

IFINDEX_PROVIDER-3INTERFACE_PERSISTENCE_FILE_READ_ONLY

3 SNMP

IFINDEX_PROVIDER-3-INTERNAL

3 SNMP

IFINDEX_PROVIDER-7-LTRACE_INIT_ERROR

7 SNMP

IFMIB_IFSPECIFIC_CLIENT-3-ERR_INV_MSG

3 SNMP

IFMIB_IFSPECIFIC_CLIENT-3-ERR_OPER_INTF

3 SNMP

IFMIB_IFSPECIFIC_CLIENT-3ERR_OPER_TABLE

3 SNMP

IFMIB_IFSPECIFIC_CLIENT-6ERR_DBG_FAILED

6 SNMP

IFMIB_IFSPECIFIC_SERVER-6ERR_DBG_FAILED

6 SNMP

IFMIB-3-GEN_ERROR

3 SNMP

IFMIB-3-MEM_ALLOC

3 SNMP

IFMIB-3-REGEXP_COMP

3 SNMP

IFMIB-3-SYSDB

3 SNMP

IFMIB-4-SYSDB_APPLY

4 SNMP

IPMIB-3-BAG_FAILED

3 SNMP

IPMIB-3-SYSDB_ACCESS

3 SNMP

LIBSNMP-3-NOMEM_FOR_INIT

3 SNMP

MACSTATMIB-4-MIB_INIT

4 SNMP

MIB-3-BADTRANSPORT

3 SNMP

MIB-3-NOINIT

3 SNMP

NLMMIB-3-ERR_MEM_ALLOC

3 SNMP

PINGMIB-3-EVENT_BLOCK

3 SNMP

PINGMIB-3-NOMEM

3 SNMP

PINGMIB-3-NOTHREADCREATE

3 SNMP

PINGMIB-7-DEBUG_REGISTER

7 SNMP

QOSMIB-3-ERR_MEM_ALLOC

3 SNMP

QOSMIB-3-ERR_NO_ENT

3 SNMP

RFMIB-3-VERIFICATION_FAILED

3 SNMP

SESSION_MON-3-EDM_INIT_ERR

3 SNMP

SESSION_MON-3-GEN_ERROR

3 SNMP

SESSION_MON-3-MEMORY

3 SNMP

SESSION_MON-4-CERR_CODE

4 SNMP

SESSION_MON-4-DEBUG_ERROR

4 SNMP

SESSION_MON-4-GEN_WARNING

4 SNMP

SHOWCMD-3-CLI_ERROR

3 SNMP

SHOWCMD-3-STD_MSG

3 SNMP

SHOWCMD-3-VALIDATE_LENGTH

3 SNMP

SHOWCMD-3-VALIDATE_MSG

3 SNMP

SHOWCMD-7-SVR_MSG

7 SNMP

SNLIB-3-INTERNAL_ERROR

3 SNMP

SNMP_IPC-4-INTERNAL

4 SNMP

SNMP_IPC-4-MEM_ALLOC

4 SNMP

SNMP_TEST-3-INTERNAL_ERROR

3 SNMP

SNMP-3-CONFIGFAIL

3 SNMP

SNMP-3-DATASIZE

3 SNMP

SNMP-3-DLL_LOAD

3 SNMP

SNMP-3-DLL_UNKNOWN

3 SNMP

SNMP-3-EVM_EVENT_BLOCK

3 SNMP

SNMP-3-INIT

3 SNMP

SNMP-3-INTERNAL

3 SNMP

SNMP-3-INTERNAL_TUPLE_ERROR

3 SNMP

SNMP-3-MEM_ALLOC

3 SNMP

SNMP-3-MIBCFGERR

3 SNMP

SNMP-3-NOTIFOID_FAILED

3 SNMP

SNMP-3-OID_SUBTREE_MISSING

3 SNMP

SNMP-3-SUBAGT

3 SNMP

SNMP-3-SYSDB_BIND

3 SNMP

SNMP-3-SYSDB_LIST

3 SNMP

SNMP-3-TARGETNONE

3 SNMP

SNMP-3-TRANSPORTIO

3 SNMP

SNMP-3-TRAPSEND

3 SNMP

SNMP-3-TUPLEVALUE

3 SNMP

SNMP-4-BULKSTATOID_NOT_FOUND

4 SNMP

SNMP-4-DEBUGDUP

4 SNMP

SNMP-4-DEBUGFAIL

4 SNMP

SNMP-4-INCOMING_QUEUE_FULL

4 SNMP

SNMP-4-INTERNAL_TRAP_QFULL

4 SNMP

SNMP-4-MIBCFGFAIL

4 SNMP

SNMP-4-MIBINSTALL

4 SNMP

SNMP-4-NOTIFYTWICE

4 SNMP

SNMP-4-RESPONSE

4 SNMP

SNMP-4-TARGETINUSE

4 SNMP

SNMP-4-TIMER

4 SNMP

SNMP-4-TRAPEMPTY

4 SNMP

SNMP-4-USER_NOT_AVAILABLE

4 SNMP

SNMP-4-VIEWFAIL

4 SNMP

SNMP-4-VIEWOID_NOT_FOUND

4 SNMP

SNMP-4-WARN_BAG_REG

4 SNMP

SNMP-4-WARN_MEM_ALLOC

4 SNMP

SNMP-4-WARN_SYSDB_BAG_ENCODE

4 SNMP

SNMP-4-WARN_SYSDB_EDM_REG

4 SNMP

SNMP-4-WARN_SYSDB_NOTIFY

4 SNMP

SNMP-7-PERSISTENCE_FILE_MISSING

7 SNMP

SONETMIB-3-BAG

3 SNMP

SONETMIB-3-BAG

3 SNMP

SONETMIB-3-NOMEM_ERROR

3 SNMP

SONETMIB-3-NOMEM_ERROR

3 SNMP

SONETMIB-3-SYSDB_ACCESS

3 SNMP

SONETMIB-3-SYSDB_ACCESS

3 SNMP

SONETMIBAPI-2-THREAD_CREATE

2 SNMP

SONETMIBAPI-3-BAG

3 SNMP

SONETMIBAPI-3-EVM_CREATE_ERR

3 SNMP

SONETMIBAPI-3-NOMEM_ERROR

3 SNMP

SONETMIBAPI-3-SYSDB_ACCESS

3 SNMP

SONETMIBCORE-2-THREAD_CREATE

2 SNMP

SONETMIBCORE-3-BAG

3 SNMP

SONETMIBCORE-3-EVM_CREATE_ERR

3 SNMP

SONETMIBCORE-3-NOMEM_ERROR

3 SNMP

SONETMIBCORE-3-SYSDB_ACCESS

3 SNMP

SONETMIBCORE-7-DEBUG

7 SNMP

SONETMIBCORE-7-DEBUG2

7 SNMP

SONETMIBCORE-7-ERROR

7 SNMP

SONETMIBCORE-7-STATUS

7 SNMP

SYSLOGMIB-3-NOMEM

3 SNMP

SYSLOGMIB-3-PARSEERROR

3 SNMP

SYSLOGMIB-3-SYSDBERROR

3 SNMP

SYSLOGMIB-3-TARGET_CFG_PROBLEM

3 SNMP

UDPSNMP-3-INIT

3 SNMP

UDPSNMP-3-MEM_ALLOC

3 SNMP

UDPSNMP-3-SYSDB_ACCESS

3 SNMP

UDPSNMP-3-SYSDB_BIND

3 SNMP

UDPSNMP-3-SYSDB_REG

3 SNMP

UDPSNMP-3-SYSTEM

3 SNMP

UDPSNMP-4-AGENTIO_WARN

4 SNMP

UDPSNMP-4-NOVRF

4 SNMP

UDPSNMP-4-SYSMGR_INFORM

4 SNMP

UDPSNMP-7-INTERNAL_ERROR

7 SNMP

UTIL-3-NOINIT

3 SNMP

VLANIFMIB-4-BAG

4 SNMP

VLANIFMIB-4-GEN

4 SNMP

VLANIFMIB-4-MEMORY

4 SNMP

VLANIFMIB-4-MIBLIB

4 SNMP

VLANIFMIB-4-SYSDB_ACCESS

4 SNMP

ACCT_EA-3-INIT

3 SUBSCRIBER

ACCT_MA-3-ACCT_NOT_CONFIGURED

3 SUBSCRIBER

ACCT_MA-3-BAD_MATCH_TYPE

3 SUBSCRIBER

ACCT_MA-3-CFG_UNDEFINED

3 SUBSCRIBER

ACCT_MA-3-INIT

3 SUBSCRIBER

ACCT_MA-3-MERGE

3 SUBSCRIBER

ACCT_MA-3-PLCYMAP_UNDEFINED

3 SUBSCRIBER

ACCT_MA-3-PREPAID_REQUEST

3 SUBSCRIBER

DATABASE-0-INIT_FAILURE

--

SUBSCRIBER

DATABASE-0-INIT_RETRY_SUCCEEDED

--

SUBSCRIBER

DATABASE-4-INIT_ERROR

4 SUBSCRIBER

DATABASE-4-TRACE

4 SUBSCRIBER

DATABASE-7-INTERNAL

7 SUBSCRIBER

IPSUB_EA-3-ERR_EVENT_BLOCK

3 SUBSCRIBER

IPSUB_EA-3-INIT

3 SUBSCRIBER

IPSUB_MA-3-INIT_FAIL

3 SUBSCRIBER

ISLM-4-CONFIGURED_SESSIONS_LIMIT

4 SUBSCRIBER

ISLM-4-ENTITLED_SESSIONS_EXCEEDED

4 SUBSCRIBER

ISLM-4-ENTITLED_SESSIONS_LIMIT

4 SUBSCRIBER

ISLM-4-SESSION_THRESHOLD_EXCEEDED

4 SUBSCRIBER

PPPOE_EA-4-ERR_EVC_ERROR

4 SUBSCRIBER

PPPOE_EA-4-ERR_EVM_EVENT_BLOCK

4 SUBSCRIBER

PPPOE_EA-4-ERR_INIT

4 SUBSCRIBER

PPPOE_EA-4-ERR_MEM_ALLOC

4 SUBSCRIBER

PPPOE_EA-4-ERR_RWMGR

4 SUBSCRIBER

PPPOE_EA-6-ERR_IMP_MULTIPLE_NTFCNS

6 SUBSCRIBER

PPPOE_GBL_CFG-4-ERR_DBG_TRACE

4 SUBSCRIBER

PPPOE_GBL_CFG-4-ERR_EVM_CREATE

4 SUBSCRIBER

PPPOE_MA-4-ERR_AAA_ATTR

4 SUBSCRIBER

PPPOE_MA-4-ERR_AAA_CONN_DOWN

4 SUBSCRIBER

PPPOE_MA-4-ERR_AAA_SESSION

4 SUBSCRIBER

PPPOE_MA-4-ERR_AAA_STALE_SESSION

4 SUBSCRIBER

PPPOE_MA-4-ERR_BBA_CONFIG

4 SUBSCRIBER

PPPOE_MA-4-ERR_BEFORE_TRACE

4 SUBSCRIBER

PPPOE_MA-4-ERR_CDM

4 SUBSCRIBER

PPPOE_MA-4-ERR_CHKPT

4 SUBSCRIBER

PPPOE_MA-4-ERR_CHKPT_CORRUPT

4 SUBSCRIBER

PPPOE_MA-4-ERR_CHKPT_DUPLICATE

4 SUBSCRIBER

PPPOE_MA-4-ERR_DEBUG

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVC_CLOSE

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVC_CREATE

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVC_ERROR

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVC_GET_FD

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVC_NOTIFY

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVC_OPEN

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVM_ATTACH

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVM_CREATE

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVM_EVENT_BLOCK

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVM_SEND

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVQ_CREATE

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVQ_DEQUEUE

4 SUBSCRIBER

PPPOE_MA-4-ERR_EVQ_ENQUEUE

4 SUBSCRIBER

PPPOE_MA-4-ERR_IMC

4 SUBSCRIBER

PPPOE_MA-4-ERR_INSERT_GLOBAL

4 SUBSCRIBER

PPPOE_MA-4-ERR_INVALID_CB

4 SUBSCRIBER

PPPOE_MA-4-ERR_INVALID_MTU

4 SUBSCRIBER

PPPOE_MA-4-ERR_MEM_ALLOC

4 SUBSCRIBER

PPPOE_MA-4-ERR_MGD_TIMER

4 SUBSCRIBER

PPPOE_MA-4ERR_PACKET_WITH_INVALID_SESSION_ID_R
ECEIVED

4 SUBSCRIBER

PPPOE_MA-4ERR_PLATFORM_IFNAME_PARSE

4 SUBSCRIBER

PPPOE_MA-4ERR_RADIUS_OVERRIDE_CONFIG_UNEXPEC
TEDLY_UPDATED

4 SUBSCRIBER

PPPOE_MA-4ERR_RADIUS_OVERRIDE_PORT_LIMIT_REAC
HED

4 SUBSCRIBER

PPPOE_MA-4-ERR_REGCOMP

4 SUBSCRIBER

PPPOE_MA-4-ERR_SUBDB

4 SUBSCRIBER

PPPOE_MA-4-ERR_SYSDB

4 SUBSCRIBER

PPPOE_MA-4-ERR_SYSMGR

4 SUBSCRIBER

PPPOE_MA-4-ERR_TEST_ONLY

4 SUBSCRIBER

PPPOE_MA-4-ERR_TIMER_WHEEL

4 SUBSCRIBER

PPPOE_MA-4-ERR_TUPLE

4 SUBSCRIBER

PPPOE_MA-4-ERR_UNEXPECTED_CB

4 SUBSCRIBER

PPPOE_MA-4-ERR_UNEXPECTED_CLEANUP

4 SUBSCRIBER

PPPOE_MA-4WARN_ACCESS_INTERFACE_SESSION_LIMIT_
REACHED

4 SUBSCRIBER

PPPOE_MA-4WARN_ACCESS_INTERFACE_SESSION_THRE
SHOLD_EXCEEDED

4 SUBSCRIBER

PPPOE_MA-4WARN_CARD_SESSION_LIMIT_REACHED

4 SUBSCRIBER

PPPOE_MA-4WARN_CARD_SESSION_THRESHOLD_EXCEE
DED

4 SUBSCRIBER

PPPOE_MA-4WARN_CIDRID_SESSION_LIMIT_REACHED

4 SUBSCRIBER

PPPOE_MA-4WARN_CIDRID_SESSION_THRESHOLD_EXCE
EDED

4 SUBSCRIBER

PPPOE_MA-4WARN_CIRCUIT_ID_SESSION_LIMIT_REACHE
D

4 SUBSCRIBER

PPPOE_MA-4WARN_CIRCUIT_ID_SESSION_THRESHOLD_E
XCEEDED

4 SUBSCRIBER

PPPOE_MA-4WARN_INNER_VLAN_SESSION_LIMIT_REACH
ED

4 SUBSCRIBER

PPPOE_MA-4WARN_INNER_VLAN_SESSION_THRESHOLD_
EXCEEDED

4 SUBSCRIBER

PPPOE_MA-4WARN_MAC_IF_SESSION_LIMIT_REACHED

4 SUBSCRIBER

PPPOE_MA-4WARN_MAC_IF_SESSION_THRESHOLD_EXCE
EDED

4 SUBSCRIBER

PPPOE_MA-4WARN_MAC_IWF_IF_SESSION_LIMIT_REACH
ED

4 SUBSCRIBER

PPPOE_MA-4WARN_MAC_IWF_IF_SESSION_THRESHOLD_
EXCEEDED

4 SUBSCRIBER

PPPOE_MA-4WARN_MAC_IWF_SESSION_LIMIT_REACHED

4 SUBSCRIBER

PPPOE_MA-4WARN_MAC_IWF_SESSION_THRESHOLD_EX
CEEDED

4 SUBSCRIBER

PPPOE_MA-4WARN_MAC_SESSION_LIMIT_REACHED

4 SUBSCRIBER

PPPOE_MA-4WARN_MAC_SESSION_THRESHOLD_EXCEED
ED

4 SUBSCRIBER

PPPOE_MA-4WARN_OUTER_VLAN_SESSION_LIMIT_REAC
HED

4 SUBSCRIBER

PPPOE_MA-4WARN_OUTER_VLAN_SESSION_THRESHOLD
_EXCEEDED

4 SUBSCRIBER

PPPOE_MA-4WARN_REMOTE_ID_SESSION_LIMIT_REACHE
D

4 SUBSCRIBER

PPPOE_MA-4WARN_REMOTE_ID_SESSION_THRESHOLD_
EXCEEDED

4 SUBSCRIBER

PPPOE_MA-4WARN_VLAN_SESSION_LIMIT_REACHED

4 SUBSCRIBER

PPPOE_MA-4WARN_VLAN_SESSION_THRESHOLD_EXCEE
DED

4 SUBSCRIBER

PPPOE_MA-6-ERR_EVC_DESTROY

6 SUBSCRIBER

PPPOE_MA-6-ERR_EVQ_DESTROY

6 SUBSCRIBER

PPPOE_MA-6INFO_ACCESS_INTERFACE_SESSION_LIMIT_
NOT_REACHED

6 SUBSCRIBER

PPPOE_MA-6INFO_ACCESS_INTERFACE_SESSION_THRES
HOLD_NOT_EXCEEDED

6 SUBSCRIBER

PPPOE_MA-6INFO_CARD_SESSION_LIMIT_NOT_REACHED

6 SUBSCRIBER

PPPOE_MA-6INFO_CARD_SESSION_THRESHOLD_NOT_EX
CEEDED

6 SUBSCRIBER

PPPOE_MA-6INFO_CIDRID_SESSION_LIMIT_NOT_REACHE
D

6 SUBSCRIBER

PPPOE_MA-6INFO_CIDRID_SESSION_THRESHOLD_NOT_E
XCEEDED

6 SUBSCRIBER

PPPOE_MA-6INFO_CIRCUIT_ID_SESSION_LIMIT_NOT_REA
CHED

6 SUBSCRIBER

PPPOE_MA-6INFO_CIRCUIT_ID_SESSION_THRESHOLD_N
OT_EXCEEDED

6 SUBSCRIBER

PPPOE_MA-6INFO_INNER_VLAN_SESSION_LIMIT_NOT_RE
ACHED

6 SUBSCRIBER

PPPOE_MA-6INFO_INNER_VLAN_SESSION_THRESHOLD_
NOT_EXCEEDED

6 SUBSCRIBER

PPPOE_MA-6INFO_MAC_IF_SESSION_LIMIT_NOT_REACHE
D

6 SUBSCRIBER

PPPOE_MA-6INFO_MAC_IF_SESSION_THRESHOLD_NOT_E
XCEEDED

6 SUBSCRIBER

PPPOE_MA-6INFO_MAC_IWF_IF_SESSION_LIMIT_NOT_REA
CHED

6 SUBSCRIBER

PPPOE_MA-6INFO_MAC_IWF_IF_SESSION_THRESHOLD_N
OT_EXCEEDED

6 SUBSCRIBER

PPPOE_MA-6INFO_MAC_IWF_SESSION_LIMIT_NOT_REAC
HED

6 SUBSCRIBER

PPPOE_MA-6INFO_MAC_IWF_SESSION_THRESHOLD_NOT
_EXCEEDED

6 SUBSCRIBER

PPPOE_MA-6INFO_MAC_SESSION_LIMIT_NOT_REACHED

6 SUBSCRIBER

PPPOE_MA-6INFO_MAC_SESSION_THRESHOLD_NOT_EXC
EEDED

6 SUBSCRIBER

PPPOE_MA-6INFO_OUTER_VLAN_SESSION_LIMIT_NOT_RE
ACHED

6 SUBSCRIBER

PPPOE_MA-6INFO_OUTER_VLAN_SESSION_THRESHOLD_
NOT_EXCEEDED

6 SUBSCRIBER

PPPOE_MA-6INFO_REMOTE_ID_SESSION_LIMIT_NOT_REA
CHED

6 SUBSCRIBER

PPPOE_MA-6INFO_REMOTE_ID_SESSION_THRESHOLD_N
OT_EXCEEDED

6 SUBSCRIBER

PPPOE_MA-6INFO_VLAN_SESSION_LIMIT_NOT_REACHED

6 SUBSCRIBER

PPPOE_MA-6INFO_VLAN_SESSION_THRESHOLD_NOT_EX
CEEDED

6 SUBSCRIBER

SUB_UTIL-2-INIT_FAILURE

2 SUBSCRIBER

SUB_UTIL-2-INIT_FAILURE

2 SUBSCRIBER

SUB_UTIL-3-THROTTLE_INTERNAL

3 SUBSCRIBER

SUB_UTIL-4-TRACE_INIT

4 SUBSCRIBER

SUB_UTIL-4-TRACE_INIT

4 SUBSCRIBER

SUB_UTIL-4-TRACE_SHUTDOWN

4 SUBSCRIBER

SUB_UTIL-4-TRACE_SHUTDOWN

4 SUBSCRIBER

SUB_UTIL-5-SESSION_THROTTLE

5 SUBSCRIBER

TMPL-5-UNSUPPORTED

5 SUBSCRIBER

TMPL-7-INTERNAL

7 SUBSCRIBER

VPDN-3-CALL_DLL_ENABLE

3 SUBSCRIBER

VPDN-3-CALL_DLL_INIT

3 SUBSCRIBER

VPDN-3-CALL_IPC_NOTIFY

3 SUBSCRIBER

VPDN-3-CALL_IPC_SEND

3 SUBSCRIBER

VPDN-3-CALL_SADB_UPDATE

3 SUBSCRIBER

VPDN-3-MGR_ACTIVE

3 SUBSCRIBER

VPDN-3-MGR_EVM

3 SUBSCRIBER

VPDN-3-MGR_INIT

3 SUBSCRIBER

VPDN-3-MGR_SHUTDOWN

3 SUBSCRIBER

VPDN-4-CALL_ALLOC

4 SUBSCRIBER

VPDN-4-CALL_DLL_DISABLE

4 SUBSCRIBER

VPDN-4-CALL_DLL_UNINIT

4 SUBSCRIBER

VPDN-4-CALL_IPC_DISCONNECT

4 SUBSCRIBER

VPDN-4-CALL_TLV

4 SUBSCRIBER

VPDN-4-DATAPLANE_ADD

4 SUBSCRIBER

VPDN-4-DATAPLANE_BATCH

4 SUBSCRIBER

VPDN-4-DATAPLANE_DELETE

4 SUBSCRIBER

VPDN-4-FSM_APPDATA

4 SUBSCRIBER

VPDN-4-FSM_CONNECT

4 SUBSCRIBER

VPDN-4-FSM_NVPAIR

4 SUBSCRIBER

VPDN-4-FSM_NVPAIR_ATTR

4 SUBSCRIBER

VPDN-4-FSM_SOCKOPTS

4 SUBSCRIBER

VPDN-4-MGR_ALLOC

4 SUBSCRIBER

VPDN-4-MGR_CHUNK_ALLOC

4 SUBSCRIBER

VPDN-4-MGR_L2TP_SESSION_ID_SPACE

4 SUBSCRIBER

VPDN-6-AUTHEN

6 SUBSCRIBER

VPDN-6-AUTHOR

6 SUBSCRIBER

VPDN-6-DEADCACHE

6 SUBSCRIBER

VPDN-6-SESSION

6 SUBSCRIBER

VPDN-6-TUNNEL

6 SUBSCRIBER

VPDN-6-UNKNOWN

6 SUBSCRIBER

VPDN-6-USER

6 SUBSCRIBER

BACKEND-7-INTERNAL

7 SYSDB

BACKEND-7-INTERNAL_PATH

7 SYSDB

BACKEND-7-INVALIDARG

7 SYSDB

BACKEND-7-INVALIDARG_PATH

7 SYSDB

BACKEND-7-IPADDR_AS_UINT

7 SYSDB

BACKEND-7-MISMATCH

7 SYSDB

BACKUPDB-7-INTERNAL

7 SYSDB

BAG-7-INTERNAL

7 SYSDB

IXDB-3-GC_ERROR

3 SYSDB

IXDB-4-RECOVERY

4 SYSDB

LIBSYSDB-4-CFG_SIZE_CRIT

4 SYSDB

LIBSYSDB-4-CFG_SIZE_CRIT_NB

4 SYSDB

LIBSYSDB-6-CFG_SIZE_HIGH

6 SYSDB

LIBSYSDB-6-CFG_SIZE_HIGH_NB

6 SYSDB

LIBSYSDB-7-APPLY

7 SYSDB

LIBSYSDB-7-APPLY_NB

7 SYSDB

LIBSYSDB-7-CERRNO_REG

7 SYSDB

LIBSYSDB-7-CERRNO_REG_NB

7 SYSDB

LIBSYSDB-7-CFG_SIZE_LOW

7 SYSDB

LIBSYSDB-7-CFG_SIZE_LOW_NB

7 SYSDB

LIBSYSDB-7-EDM_BIND

7 SYSDB

LIBSYSDB-7-EDM_BIND_NB

7 SYSDB

LIBSYSDB-7-INTERNAL

7 SYSDB

LIBSYSDB-7-INTERNAL_NB

7 SYSDB

LIBSYSDB-7-LOCKING

7 SYSDB

LIBSYSDB-7-LOCKING_NB

7 SYSDB

LIBSYSDB-7-LOCKING_RETRY

7 SYSDB

LIBSYSDB-7-MULT_DEFAULTIFIERS

7 SYSDB

LIBSYSDB-7-MULT_DEFAULTIFIERS_NB

7 SYSDB

LIBSYSDB-7-PICKUP_FAILED

7 SYSDB

LIBSYSDB-7-PICKUP_FAILED_NB

7 SYSDB

LIBSYSDB-7-RECONNECTION

7 SYSDB

LIBSYSDB-7-RECONNECTION_NB

7 SYSDB

LIBSYSDB-7-REFERRAL_COUNT

7 SYSDB

LIBSYSDB-7-REFERRAL_COUNT_NB

7 SYSDB

LIBSYSDB-7-RESTORE

7 SYSDB

LIBSYSDB-7-RESTORE_NB

7 SYSDB

LIBSYSDB-7-UNEXPECTED_SEND_ERROR

7 SYSDB

LIBSYSDB-7UNEXPECTED_SEND_ERROR_NB

7 SYSDB

SMC-7-DEPRECATED_PATH

7 SYSDB

SMC-7-ERROR_RINFO

7 SYSDB

SMC-7-INTERNAL

7 SYSDB

SMC-7-INTERNAL_STATE

7 SYSDB

SMC-7-INVALID_PATH

7 SYSDB

SMC-7-MISSING_NODE_NFN

7 SYSDB

SMC-7-MULTI_NODE_TRANS

7 SYSDB

SMC-7-PARSE_FAILED

7 SYSDB

SMC-7-PROTOCOL

7 SYSDB

SMC-7-RESTARTING

7 SYSDB

SMC-7-TIMEOUT

7 SYSDB

SMC-7-TIMEOUT_RINFO

7 SYSDB

SMC-7-TRANS

7 SYSDB

SMC-7-UNEXPECTED_MSG_TYPE

7 SYSDB

SMC-7UNEXPECTED_MULTIPLE_RESPONSES

7 SYSDB

SMC-7-UNEXPECTED_VALUE

7 SYSDB

SMC-7-WRONG_PLANE

7 SYSDB

SMS-3-ASYNC_MSG_TAG_INVALID

3 SYSDB

SMS-3-GSP_EVQ_HANDLE_ERROR

3 SYSDB

SMS-3-MSG_SEND_ZERO_BYTES

3 SYSDB

SMS-6-EDM_RESPONSE_TOO_BIG

6 SYSDB

SMS-7-INTERNAL

7 SYSDB

SMS-7-LOCKING

7 SYSDB

SMS-7-MISSING_NODE_NFN

7 SYSDB

SMS-7-PROTOCOL

7 SYSDB

SMS-7-REG_CONTEXT_EXISTS

7 SYSDB

SMS-7-REG_SEC_CONTEXT_EXISTS

7 SYSDB

SMS-7-REG_SEC_DEL_FAIL

7 SYSDB

SMS-7-REQUEST_REG_SEND_ERR

7 SYSDB

SMS-7-RESTARTING

7 SYSDB

SMS-7-SEND_RESPONSE

7 SYSDB

SMS-7-UNEXPECTED_MSG_TYPE

7 SYSDB

SMS-7-UNEXPECTED_VALUE

7 SYSDB

SYSDB-3-MEMORY

3 SYSDB

SYSDB-3-SC_BIND

3 SYSDB

SYSDB-3-SC_DATATYPERET

3 SYSDB

SYSDB-3-SC_EXTFMTSTR

3 SYSDB

SYSDB-3-SC_FILEREAD

3 SYSDB

SYSDB-3-SC_INTERR

3 SYSDB

SYSDB-3-SC_NOFILE

3 SYSDB

SYSDB-3-SC_PKDREAD

3 SYSDB

SYSDB-3-SC_PKDTUPLECRE

3 SYSDB

SYSDB-3-SC_PKDTUPLEFILE

3 SYSDB

SYSDB-3-SC_READERINIT

3 SYSDB

SYSDB-3-SC_UNPACKTUP

3 SYSDB

SYSDB-3-THREAD_EXIT

3 SYSDB

SYSDB-4-REPLICATOR_OOS

4 SYSDB

SYSDB-4-SC_ABORTBULK

4 SYSDB

SYSDB-4-SC_ABORTTRANS

4 SYSDB

SYSDB-4-SC_BAD_INTEGER

4 SYSDB

SYSDB-4-SC_BADFORMAT

4 SYSDB

SYSDB-4-SC_BIND_NOTFOUND

4 SYSDB

SYSDB-4-SC_BULK_NUM_OPS

4 SYSDB

SYSDB-4-SC_CFGMGR_ADD_DELETES

4 SYSDB

SYSDB-4-SC_CFGMGR_ADDDIFFS

4 SYSDB

SYSDB-4-SC_CFGMGR_DELETE

4 SYSDB

SYSDB-4-SC_CFGMGR_MERGE

4 SYSDB

SYSDB-4-SC_CFGMGR_REMOVE_DELETES

4 SYSDB

SYSDB-4-SC_COMMITTRANS

4 SYSDB

SYSDB-4-SC_COPY

4 SYSDB

SYSDB-4-SC_CREATE

4 SYSDB

SYSDB-4-SC_DATAFIND

4 SYSDB

SYSDB-4-SC_DATALIST

4 SYSDB

SYSDB-4-SC_DATATYPE

4 SYSDB

SYSDB-4-SC_DELETE

4 SYSDB

SYSDB-4-SC_EDM_NOT

4 SYSDB

SYSDB-4-SC_ENDBULK

4 SYSDB

SYSDB-4-SC_ERRORSLIST

4 SYSDB

SYSDB-4-SC_EVENT

4 SYSDB

SYSDB-4-SC_EVENTFIND

4 SYSDB

SYSDB-4-SC_EXCESS

4 SYSDB

SYSDB-4-SC_FILERESTORE

4 SYSDB

SYSDB-4-SC_FILESAVE

4 SYSDB

SYSDB-4-SC_FIND

4 SYSDB

SYSDB-4-SC_GENERIC

4 SYSDB

SYSDB-4-SC_GET

4 SYSDB

SYSDB-4-SC_GET_INH

4 SYSDB

SYSDB-4-SC_GET_ITEMS

4 SYSDB

SYSDB-4-SC_ITERATE

4 SYSDB

SYSDB-4-SC_LIST

4 SYSDB

SYSDB-4-SC_MISMATCH

4 SYSDB

SYSDB-4-SC_MISSEVENT

4 SYSDB

SYSDB-4-SC_MISSFILENAME

4 SYSDB

SYSDB-4-SC_MISSNAME

4 SYSDB

SYSDB-4-SC_MISSTYPE

4 SYSDB

SYSDB-4-SC_MISSVALUE

4 SYSDB

SYSDB-4-SC_PATHCREATE

4 SYSDB

SYSDB-4-SC_PKDFMTSTR

4 SYSDB

SYSDB-4-SC_RDLOCK

4 SYSDB

SYSDB-4-SC_REBIND

4 SYSDB

SYSDB-4-SC_REMOVE_BULK_OP

4 SYSDB

SYSDB-4-SC_SET

4 SYSDB

SYSDB-4-SC_STARTBULK

4 SYSDB

SYSDB-4-SC_STARTTRANS

4 SYSDB

SYSDB-4-SC_UNKCMD

4 SYSDB

SYSDB-4-SC_UNLOCK

4 SYSDB

SYSDB-4-SC_VERIFY

4 SYSDB

SYSDB-4-SC_VRFNRES

4 SYSDB

SYSDB-4-SC_VRFNSUSP

4 SYSDB

SYSDB-4-SC_WRLOCK

4 SYSDB

SYSDB-4-TIMEOUT_NFN

4 SYSDB

SYSDB-6-TIMEOUT_EDM

6 SYSDB

SYSDB-7-CFG_WRITE

7 SYSDB

SYSDB-7-CLIENT_STATS

7 SYSDB

SYSDB-7-CLIENT_STATS_MISMATCH

7 SYSDB

SYSDB-7-INFO

7 SYSDB

SYSDB-7-INTERNAL

7 SYSDB

SYSDB-7-INVALID_PATHNAME

7 SYSDB

SYSDB-7-LOCKING

7 SYSDB

SYSDB-7-LTRACE_INIT

7 SYSDB

SYSDB-7-REPLICATOR_NO_CB

7 SYSDB

SYSDB-7-REPLY

7 SYSDB

SYSDB-7-RPL_INIT

7 SYSDB

SYSDB-7-SEND

7 SYSDB

SYSDB-7-SHUTDOWN

7 SYSDB

SYSDB-7-STARTUP

7 SYSDB

SYSDB-7-USAGE

7 SYSDB

SYSDBHELPER-7-INTERNAL

7 SYSDB

SYSDBHELPER-7-LOCKING

7 SYSDB

SYSDBUTILS-7-INTERNAL

7 SYSDB

SYSDBUTILS-7-INTERNAL_NODEID_STR

7 SYSDB

SYSDBUTILS-7-LOCKING

7 SYSDB

Message Text

Explanation

The ACL MIB library failed to initialize due

to the following error: [chars]

The ACL MIB library initialization has failed.

The ACL Statistics MIB functionality will be
unavailable

The ACL MIB library failed to initialize due

to the following error: [chars]

The ACL MIB library initialization has failed.

The ACL Statistics MIB functionality will be
still be available, but some of its
functionality not be completely available.
You may not be able to turn on debugs, get
ltrace, ship logs, or some other minor
functionality.

[chars]

This is simply a debug message. If any

severe errors occur the process will exit
and will be restarted by the sysmgr.

Process '[chars]' is not authorized to use

the ACL compression library

A process that is not authorized to use the

ACL compression library is trying to load
and use it.

The ACL compression library initialization

The ACL compression library fails to
has failed. The ACL compression
initialize due to the following error: [chars] functionality will be unavailable

A packet matching the log criteria for the

given access list was detected. It has both
outer and inner vlan. These messages are
issued whenever access lists are
configured with the 'log' option. Any access
access-list [chars] ([dec]) [chars] [hex]
list entry that has had hits are logged via
Outer vlan [dec] dei [dec] \ cos [dec] inner this message. These messages are issued
vlan [dec] dei [dec] cos [dec] [chars] ->
either at 5 minute intervals, or whenever
[chars], \ [dec] packet[chars]
the log buffer overflows.

Unable to allocate memory for [chars]

Memory allocation failed, probably due to

memory depletion. An entry could not be
added to the cache, the associated
command will be blocked by the parser.

Unable to lock cache mutex. Error: [chars]

A mutex is used to protect the ACL and

Prefix List caches. An attempt to lock a
mutex failed with the error reported.

System cannot raise rlimit for ACL library,

'[chars]'

The ACL library has requested the

operating system to grant additional heap
memory. The request has failed and the
error indicating the reason has been given

Access lists with object groups are not

supported by this application

An access list that contains object-groups

in one of its entries was specified. At this
time ACLs with object-groups are supported
only for packet filtering. I.e., attached to an
interface.

access-list [chars] ([dec]) [chars] [dec]

[chars] [chars]-> [chars] ([dec]/[dec]),
[dec] packet[chars]

A packet matching the log criteria for the

given access list was detected. These
messages are issued whenever access lists
are configured with the 'log' option and
matches with the IP protocol type ICMP.
This message is seen for the first match
and for each match after the hit count is
greater than 0x7FFFFFFF(2147483647).

access-list [chars] ([dec]) [chars] [chars]

[chars] [chars]-> [chars] ([dec]/[dec]),
[dec] packet[chars]

A packet matching the log criteria for the

given access list was detected. These
messages are issued whenever access lists
are configured with the 'log' option and
matches with the IP protocol type ICMP.
This message is seen for the first match
and for each match after the hit count is
greater than 0x7FFFFFFF(2147483647).

access-list [chars] ([dec]) [chars] [dec]

[chars] [chars]-> [chars], [dec]
packet[chars]

A packet matching the log criteria for the

given access list was detected. These
messages are issued whenever access lists
are configured with the 'log' option and
matches with the IP protocol type other
than TCP, UDP, SCTP, IGMP, ICMP and
'standard ACL'. This message is seen for
the first match and for each match after
the hit count is greater than
0x7FFFFFFF(2147483647).

access-list [chars] ([dec]) [chars] [dec]

[chars] [chars]-> [chars], [dec]
packet[chars]

A packet matching the log criteria for the

given access list was detected. These
messages are issued whenever access lists
are configured with the 'log' option and
matches with the IP protocol type other
than TCP, UDP, SCTP, IGMP, ICMP and
'standard ACL'. This message is seen for
the first match and for each match after
the hit count is greater than
0x7FFFFFFF(2147483647).

access-list [chars] ([dec]) [chars] [dec]

[chars]([dec]) [chars]-> [chars]([dec]),
[dec] packet[chars]

A packet matching the log criteria for the

given access list was detected. These
messages are issued whenever access lists
are configured with the 'log' option and
matches with the IP protocol type TCP (or)
UDP (or) SCTP. This message is seen for the
first match and for each match after the hit
count is greater than
0x7FFFFFFF(2147483647).

access-list [chars] ([dec]) [chars] [chars]

[chars]([dec]) [chars]-> [chars]([dec]),
[dec] packet[chars]

A packet matching the log criteria for the

given access list was detected. These
messages are issued whenever access lists
are configured with the 'log' option and
matches with the IP protocol type TCP (or)
UDP (or) SCTP. This message is seen for the
first match and for each match after the hit
count is greater than
0x7FFFFFFF(2147483647).

access-list [chars] ([dec]) [chars] [dec]

[chars] [chars]-> [chars], [dec]
packet[chars]

A packet matching the log criteria for the

given access list was detected. These
messages are issued whenever access lists
are configured with the 'log' option and
matches with the IP protocol type IGMP.
This message is seen for the first match
and for each match after the hit count is
greater than 0x7FFFFFFF(2147483647).

access-list [chars] ([dec]) [chars] [chars]

[chars] [chars]-> [chars], [dec]
packet[chars]

A packet matching the log criteria for the

given access list was detected. These
messages are issued whenever access lists
are configured with the 'log' option and
matches with the IP protocol type IGMP.
This message is seen for the first match
and for each match after the hit count is
greater than 0x7FFFFFFF(2147483647).

access-list [chars] ([dec]) [chars] [chars]

[dec] packet[chars]

A packet matching the log criteria for the

given access list was detected. These
messages are issued whenever access lists
are configured with the 'log' option and
matches with the access-list that is used by
routing protocols. This message is seen for
the first match and for each match after
the hit count is greater than
0x7FFFFFFF(2147483647).

access-list [chars] ([dec]) [chars] [chars]

[dec] packet[chars]

A packet matching the log criteria for the

given access list was detected. These
messages are issued whenever access lists
are configured with the 'log' option and
matches with the access-list that is used by
routing protocols. This message is seen for
the first match and for each match after
the hit count is greater than
0x7FFFFFFF(2147483647).

IPv4 ACL Manager initialisation failed in

function [chars]: [chars]

The ACL manager process encountered the

specified error while initializing the
specified facility. If this error occurs, the
sysmgr process will restart the ACL
manager process. This failure will occur
only on RP.

failed to [chars] ACL mutex, error [[dec]]:

[chars]

The mutex used to protect access to the

ACL data structure could not be locked or
unlocked. The error message will include
details of the particular failure. Possible
causes of failure are the mutex is
corrupted, has not been initialised or is
being accessed recursively (this is not
allwowed). Because the mutex could not be
used the process may restart to recover
from the failure.

failed to [chars] ACL mutex, error [[dec]]:

[chars]

The mutex used to protect access to the

ACL data structure could not be locked or
unlocked. The error message will include
details of the particular failure. Because
the mutex could not be used the process
was restarted to recover from the failure.

Failed to initialize [chars], because of

[chars]

Initialization failed. Both the initialization

type and the error code are displayed. The
sysmgr process will restart the IPv6
daemon if this condition happens.

failed to open dll: [chars]

This message is seen when the process

fails to open the DLL 'libipv6_acl_tree.dll'.
This failure may occur on RP and LC. It may
fail to open the DLL due to any one of the
following reasons: 1. passing the bad mode
like no share mode(RTLD_NOSHARE) 2. list
of DLL objects is empty or the list itself
doesn't exits. 3. if no symbol in executable.
4. if the memory allocation fails at any
stage 5. if the dll is not unique with respect
to the other DLL's loaded and placed in the
list.

failed to open dll: [chars]

This message is seen when the process

fails to open the DLL 'libipv6_acl_tree.dll'.
This failure may occur on RP and LC. It may
fail to open the DLL due to any one of the
following reasons: 1. passing the bad mode
like no share mode(RTLD_NOSHARE) 2. list
of DLL objects is empty or the list itself
doesn't exits. 3. if no symbol in executable.
4. if the memory allocation fails at any
stage 5. if the dll is not unique with respect
to the other DLL's loaded and placed in the
list.

dlsym lookup for ipv6_acl_api_functions

failed for dll: [chars]

This message indicates that a process

could not find the specified DLL name. The
name of this DLL is included in the
message. Functionalites of the process that
failed to load this DLL will be impacted.

dlsym lookup for ipv6_acl_api_functions

failed for dll: [chars]

This message indicates that a process

could not find the specified DLL name. The
name of this DLL is included in the
message. Functionalites of the process that
failed to load this DLL will be impacted.

insufficient memory for dll: [chars]

There is insufficient memory available to

load the specified dll. This could be
because of the shortage of system memory
given the complexity of the configuration.

insufficient memory for dll: [chars]

There is insufficient memory available to

load the specified dll. This could be
because of the shortage of system memory
given the complexity of the configuration.

failed to [chars] ACL mutex, error [[dec]]:

[chars]

The mutex used to protect access to the

ACL data structure could not be locked or
unlocked. The error message will include
details of the particular failure. Possible
causes of this failure are the mutex is
corrupted, has not been initialised or is
being accessed recursively (this is not
allwowed). Because the mutex could not be
used, the process may restart to recover
from the failure.

failed to [chars] ACL mutex, error [[dec]]:

[chars]

The mutex used to protect access to the

ACL data structure could not be locked or
unlocked. The error message will include
details of the particular failure. Possible
causes of this failure are the mutex is
corrupted, has not been initialised or is
being accessed recursively (this is not
allwowed). Because the mutex could not be
used, the process may restart to recover
from the failure.

ltrace_init failed for '[chars]': [chars]

Initialization of the ltrace debug capability

failed with the reason displayed in the error
message. This failure does not impact the
functionality of ipv6 access-lists. However,
debugging of any issues will be impaired.

System cannot raise rlimit for ACL library,

'[chars]'

The ACL library has requested the

operating system to grant additional heap
memory. The request has failed and the
error indicating the reason has been given

Access lists with object groups is not

supported by this application

An access list that contains object-groups

in one of its entries was specified. At this
time ACLs with object-groups are supported
only for packet filtering. I.e., attached to an
interface.

access-list [chars] ([dec]) [chars] [chars]

[chars] [chars]-> [chars] ([dec]/[dec]),
[dec] packet[chars]

A packet matching the log criteria for the

given access list was detected.

access-list [chars] ([dec]) [chars] [dec]

[chars] [chars]-> [chars] ([dec]/[dec]),
[dec] packet[chars]

Packet matching the log criteria for the

given access list was detected.

access-list [chars] ([dec]) [chars] [dec]

[chars] [chars]-> [chars], [dec]
packet[chars]

Packet matching the log criteria for the

given access list was detected. These
messages are issued when the IP protocol
type is other than TCP, UDP and SCTP. This
message is seen for the first match and for
each match after the hit count is greater
than 0x7FFFFFFF(2147483647).

access-list [chars] ([dec]) [chars] [dec]

[chars] [chars]-> [chars], [dec]
packet[chars]

These messages are issued whenever

access lists are configured with the 'log'
option and matches with the IP protocol
type other than TCP, UDP, SCTP. This
message is seen for the first match and for
each match after the hit count is greater
than 0x7FFFFFFF(2147483647).

access-list [chars] ([dec]) [chars] [chars]

[chars]([dec]) [chars]-> [chars]([dec]),
[dec] packet[chars]

These messages are issued whenever

access lists are configured with the 'log'
option and matches with the IP protocol
type TCP (or) UDP (or) SCTP. This message
is seen for the first match and for each
match after the hit count is greater than
0x7FFFFFFF(2147483647).

access-list [chars] ([dec]) [chars] [dec]

[chars]([dec]) [chars]-> [chars]([dec]),
[dec] packet[chars]

Packet matching the log criteria for the

given access list was detected. These
messages are issued when the IP protocol
type is TCP or UDP or SCTP. This message is
seen for the first match and for each match
after the hit count is greater than
0x7FFFFFFF(2147483647).

accesss-list [chars] ([dec]) [chars] [dec]

[chars] [chars]-> [chars], [dec]
packet[chars]

A packet matching the log criteria for the

given access list was etected.

accesss-list [chars] ([dec]) [chars] [chars]

[chars] [chars]-> [chars], [dec]
packet[chars]

A packet matching the log criteria for the

given access list was etected.

access-list [chars] ([dec]) [chars] [chars]

[dec] packet[chars]

A packet matching the log criteria for the

given access list was detected.

access-list [chars] ([dec]) [chars] [chars]

[dec] packet[chars]

A packet matching the log criteria for the

given access list was detected.

[chars]: LI Netio thread init failed for proto

[dec], during [chars]: ([dec])[chars]

The LI Netio thread encountered the

specified error during thread creation or
during initialization of the specified facility.
System will retry to start the process to
recover.

ltrace_init failed for '[chars]': [chars]

Initialization failed. Both the initialization

type and the error code are displayed. The
sysmgr process will restart the ipv4_aclmgr
if this condition happens.

Failed to cleanup '[chars]', [hex]:[chars].

When 'object group' shutsdown, the OBJ

Manager (obj_mgr) process shutsdown and
cleans up. Something has failed in this
proceedure.

Failed to initialize '[chars]', [hex]:[chars].

When 'object group' configuration is first

added, the OBJ Manager (obj_mgr) process
starts and initializes. Something has failed
in this proceedure and may prevent OBJ
Manager from functioning.

Error encountered while processing policy- An unexpected error occurred while parsing
map/class-map command: [chars]. Error:
the policy manager configuration
'[chars]'
command.

Failed to allocate %zd bytes.

The node which logged this message is

running low on memory and the requested
operation could not be completed.

Failed to [chars] debug [chars]:'[chars]'

The policy manager ui library debug(s)

could not be initialized. The is a non-fatal
error and should not affect the normal
functioning of the system. The only effect
of this error will be that the policy manager
ui library debugs may not show up .

[chars] [dec]

The policymgr ui library received invalid

data from the user interface. Ideally this
should never happen and would be caused
only by a bug in the code.

Failed to [chars] ltrace [chars]:'[chars]'

The policymgr ui library ltrace

infrastructure encountered an error during
initialization or displaying ltrace messages,
as indicated in the syslog. This should not
affect the normal functioning of the
system.

Get application name failed for app :

[unsigned int]

An internal error encountered during

policymgr initialization, configuration of
one or more types of policy-maps/classmaps may not work.

Error encountered in [chars] during

policymgr activation after failover: [chars]

An error was encountered in policymgr

during policymgr activation after failover.
Policymgr configurations may not work
properly. Subsequent
updates/modifications to policy-map/classmap configurations may not function
properly, including activating servicepolicies on interfaces.

Policy manager initialization failed in

[chars]: [chars]

The policy manager process encountered

the specified error while initializing the
specified facility. If this error occurs, the
sysmgr process will restart the policy
manager process.

[chars] is not detected.

A line card could not be located in a slot

where a diagnostic action was requested.

[chars]: process_enqueue() failed.

An internal software error occurred while

processing the diagnostic message
alongwith the opcode to the dignostic
process of the specified card or
location/sub-location.

[chars]

An error occurred, likely due to an invalid

argument was entered.

[chars]: [chars] detected a Major Error.

Please use 'show diagnostic result location A major error was detected if all the
<node>' to see test results.
diagnostic test fail for the specified card.

A minor error was detected if the

[chars]: [chars] detected a Minor Error.
diagnostic test fails for the specified card
Please use 'show diagnostic result location such as if a single device associated with
<node>' to see test results.
the particular diagnostic test has failed.

[chars]

An internal software error occurred.

[chars]: [chars]{ID=[dec]} has failed. Error A diagnostic test has found an error on the
code = [hex] ([chars])
line card.

[chars]

An internal software error occurred.

[chars]: The users are not allow to disable

monitoring for Test #[dec]

The specified health monitoring test must

be run and cannot be disabled.

[chars]: Diagnostic is currently running

A diagnostic test is currently being run on

the specified card and additional tests
cannot be run until the previously
requested tests have been completed.

[chars]: The users are not allow to change

monitoring interval of Test #[dec]

The specified health monitoring test

interval is not user-configurable and
therefore cannot be changed.

Invalid device number : [chars]

A diagnostic request is being made on a

device that does not exist.

[chars]: The [chars][ID=[dec]] monitoring

interval must be at least [dec] millisec

The specified test monitoring interval is too

small.

Invalid port number : [chars]

A diagnostic request is being made on a

port that does not exist.

Invalid test IDs : [chars]

A test ID for diagnostics that does not exist

was requested.

The specified test is no longer a health

[chars]: The monitoring test:[dec] is disable monitoring test because health monitoring
since default interval is Zero
has been disabled.

[chars]: Monitoring interval is 0. Cannot

enable monitoring for Test #[dec]

Health Monitoring cannot be enabled for

the specified test because the interval for
the test has been set to 0.

[chars]: The test:[dec] cannot be used as

health monitoring test

The specified test number cannot be used

as a health monitoring test.

The diagnostic test is not supported on

[chars]: [chars]{ID=[dec]} is not supported current chassis configuration.

[chars]: Diagnostics is bypassed

This is an informational message stating

that diagnostics testing was not performed
on the card because diagnostic testing was
disabled in the user configuration.

[chars]: Passed [chars]

The diagnostic tests did not detect any

error on the card.

[chars]: Diagnostic is stopped.

Diagnostic test has stopped.

[chars]

GOLD-XR general information.

[chars]: Diagnostic is not running

An attempt to stop a diagnostic test that

was not running was made.

[chars]: No test to run

The diagnostic test cannot find tests to run.

[chars]: Running Complete Diagnostics...

Complete Diagnostic is running on the card

[chars]: Running Minimum Diagnostics...

Minimum Diagnostic is running on the card

[chars]: Scheduled Online Diagnostic is

completed

The scheduled Diagnostic test is complete.

[chars]: Performing Scheduled Online

Diagnostic...

The scheduled diagnostic test is running.

[chars]: Scheduled Online Diagnostic is

stopped

The scheduled Diagnostic test has been

stopped.

[chars]: Schedule Diagnostic for [[chars]

[chars] [dec]:[dec].] is removed

The scheduled online diagnostic tests are

no longer configured. This message usually
appears after a scheduled test is removed
by the user or a card is removed from the
chassis.

[chars]: test not allowed for ondemand

[chars]{ID=[dec]} ...

Diagnostic test executed is not an

ondemand test.

[chars]: [chars]{ID=[dec]} has completed

successfully

Diagnostic testing was completed and no

errors were found on the line card.

[chars]: Running [chars]{ID=[dec]} ...

Diagnostic testing is running a test on the

card

[chars]: [chars]{ID=[dec]} is skipped

The specified diagnostic test cannot be run.

[chars]: [chars] cannot be executed from

active node.

The specified test cannot be run from

active node.

[chars]: [chars] cannot be executed from

standby node.

The specified test cannot be run from

standby node.

Unable to determine receipt checksum

Error=[hex] Reason [chars]

Diagnostics detected a software error

computing the checksum of a recieved
packet. This is not a service impacting
error.

Diagnostics software has received a packet

from a client, but the client is not
connected to the server. Another
component may have restarted causing the
No server connection for this client. (Client connection to be broken. This is not a
Id=[dec] - [chars])
service impacting error.

The diagnostics software detected an

invalid or null pointer was passed to the
named function. This is a serious error and
could indicate memory coruption or a bug
Invalid or no connection context passed to in the software. This is not a service
function [chars]
impacting error.

[chars] ([hex] - [chars])

An error occurred during initialization.

[chars] (Client Id [dec] - [chars])

An error occurred during initialization of

diagnostic's server queue.

Unknown message was passed to a

function (msg type = [dec]) [chars]

The diagnostics software received a

message with an unknown message type
and was not able to process it. This is a
serious error and indicates message or
memory corruption or a bug in the
software. This is not a service impacting
error.

Unable to [chars] a shared memory buffer

[chars] queue element (Error=[dec] [chars])

Diagnostics was unable to attach or detach

the payload stored in shared memory
to/from a packet in the queue. This is a
serious error and should not occur. It may
indicate there is a bug in the software. This
is not a service impacting error.

Unable to read incoming packet

(Error=[dec] - [chars])

A packet processing error occurred. The

diagnostics software attempted to retrieve
a packet and an error occurred while doing
so. This is not a service impacting error.

Unable to [chars] item (Error=[dec] [chars])

An software error occurred while

performing the stated action (queue
operation) on a packet or message. This is
a serious error and could indicate memory
corruption or a bug in the software. This is
not a service impacting error.

Invalid state ([dec]) [chars]

An internal state of the diagnostics process

was set to an invalid state or value. The
process did not know how to handle this
state. This is a serious error and may
indicate a bug in the software. This is not a
service impacting error.

[chars] ([hex] - [chars])

An internal software error occurred.

[chars] ([hex] - [chars])

An internal software error occurred.

[chars] ([hex] - [chars])

Software detected an unexpected error or

condition, which is not fatal to the features
performance, but which may have affected
a test result or similar.

[chars] ([hex] - [chars])

Software detected an unexpected error or

condition, which is not fatal to the features
performance, but which may have affected
a test result or similar.

Plane [dec] is detected to be at fault.

Unable to notify fabric process to shut
down the plane.

The diagnostic test has detected an error

on a fabric plane but failed to notify the
fabric management process to take the
plane out of service.

Node [unsigned int]: Detected [dec] CE

[chars] switch failure. Will attempt to
reload node after [dec] consecutive such
failures

The diagnostic control ethernet switch loop

back ping test for inter and intra rack has
detected an error and if the test fails for
three consecutive iterations resulting RP
reset by diagnostic software on failure.

[chars]%s

The fabric diagnostic test has detected an

error as part of the FIM. Fabric multicast
and unicast tests aimed at identifying the
faulty plane(s).

[chars]

The diagnostic test for fabric SRCC has

detected an error. SRCC allows for the test
cells to specify an exact route through the
fabric based on IngressQ physical link
number and each of the S1, S2 and S3
ASICs physical link numbers. The test is
capable of potentially isolating a problem
to a single link and/or ASIC.

[chars]

The diagnostic test for combined fabric

unicast and mulitcast ping has detected an
error condition and if the reload/shutdown
is configured for the test diagnostic
software will take corresonding action such
as reload/shutdown on single node
consecutive failure.

[chars]

The diagnostic test for basic file system

devices such as disk0, disk1, harddisk
respectively has detected an error
condition, if the devices are not present or
having some access issues.

[UUT [chars]: [chars]]

The diagnostic software has detected an

error while running Field/Offline Diagnostic
(IFD) on the target node/card under test.

[chars]

The diagnostic test for LC scrach register

has detected an error and if
reload/shutdown thresholds are set
corresponding action will be taken by the
diagnostic software on failure.

[chars]

Informational diagnostics message.

Node [unsigned int]: Test could not send

packet - rslt:UNKNOWN/rc:SKIPPED

Unable to send switch loopback tests

packets, resetting fail count because some
amount of time we allow for the packet to
be sent by eth_server and This is done to
double check that there is no software
issue when switch loopback test fails and
crosses threshold.

CCSQ: device halted, sub-block: [chars],

halted entity: [chars]

CCSQ, ASIC got halted. The halted block

and its parent block are provided

EIO link training threshold exceeded, link:

[dec]

Repeated attempts to train the EIO links to

the neighboring Asic have failed. No further
attempts to retrain the link will be made.

Taking the node down, Reason: [chars]

CCSQ DLL encountered an fatal error

mentioned above. The driver triggers MSC
node-down to recover from the error.

Block: [chars], Generic Error [chars] at

Memory Address [hex].

CCSQ encountered a device error that has

exceeded its threshold value. Driver takes
appropriate action to log and fix the error
which may include a device reset.

Multiple Bit Error in Block: [chars] Error:

[chars].

CCSQ encountered a multiple bit error in

the mentioned block. This error is an
uncorrectable error. Driver takes
appropriate action to log and fix the error
which may include a device reset.

[chars]

The CCSQ driver failed to initialize the

device resulting in the restart of the CCSQ
driver process.

Error Allocating memory for <[chars]>

The CCSQ dll Memory Allocation Error

message.

Resetting CCSQ ASIC Device

CCSQ, cpuctrl net interface encountered a

CRC/Sync Error. This will result in the PIO or
CDMA failure.

CRC Error: Block:[chars] Error:[chars]

Count: [dec]

CCSQ block received a packet with a CRC

error. It is primarily caused by either the
link errors between the devices or packet
corruption in the upstream asic. This error
may cause performance degradation.

CpuCtrl Interface RxFIFO Error: [chars]

CCSQ, cpuctrl net interface Rx FIFO last

sync.

Interrupt enable at addr: [hex] mask: [hex]

failed.
Hardware state is not correct.

Block: [chars], entity: [chars] had parity

error(s), addr: [dec], parity: [dec]

In the specified block a parity error

encountered at mentioned addr offset. If
the error exceeds its threshold, the driver
trigger a corrective action which may
include device reset or MSC reload.

Single Bit Error in Block: [chars] Error:

[chars].

CCSQ encountered a single bit error in the

mentioned block. Persistent errors are
corrected by the software. Non-persistent
errors are automatically corrected by the
next write operation.

Register get failed for address [hex],

Reason: [chars]

An attempt to read a Hardware register

failed. This could result in inconsistent
behavior of the device.

CCSQ Lib: LWM Message send failed msg:

[dec], retried: [dec] time(s), errno: [chars]

Unable to send a LWM message to the

CCSQ server.

CCSQ manager encountered a fatal error

and is not able recover from the error. A
Initialization Error: [chars] Reason: [chars]. reason text will be supplied call support
Exiting.
with this text.

Error Allocating <[dec]> bytes of memory

CCSQ encountered a fatal memory

allocation error

Bag register failed for rules. Reason:

[chars]

EDM Bags are used to share information

between components using sysdb. This
Error indicates that bag registration failed.

Client [chars] failed. Reason: [chars]

CCSQ Manager client

Registration/Unregistration error

Dll Initialization for [chars] failed. Reason:

[chars]

CCSQ driver tried to register for a dll but it

encountered an error. The driver might lose
some of its functionality.

Event Manager create failed for [chars].

Reason: [chars]

CCSQ Event Manager create error

Event Manager notify failed for [chars].

Reason: [chars]

CCSQ Event Manager notify error

LWM Event Manager event block failed.

Reason: [chars]

CCSQ Event Manager event block error

An error occurred during LWM message

reply. Reason: [chars]

CCSQ LWM reply error

Sysdb Register EDM failed. Reason: [chars] CCSQ Sysdb Register EDM error

GSP Fabric: Unable to initialize debug

logging. Error: [chars].

Debug initialization failure for GSP fabric.

Failed to initialize the shared memory for

[chars]: shmwin_init() failed shmwinid [dec] NH.

hal_shm_alloc: shmwin_malloc() failed

shmwinid [dec]

Failed to allocate the shared memory for

NH.

[chars]: shmwin_pool_create_v2() failed,

return: cerr: [dec]

Failed to create the memory pool for

shared memory.

Fabric proxy failed to connect to [chars]

with error: [hex] ([chars]).

The fabric proxy failed to connect to the

required services. The driver will be nonoperational due to this error.

Fabric proxy failed to create the event

manager and hence exiting

The fabric proxy failed to create an event

manager during the initialization. The
driver will be non-operational due to this
error.

Fabric proxy failed to create sysdb thread

due to [chars] with error: [hex] ([chars]).

The fabric proxy failed to create the sysdb

thread during the initialization. The driver
will be non-operational due to this error.

The fabric proxy failed to create the sysdb

thread with error: [hex] ([chars]).

The fabric proxy failed to create the

needed threads during the initialization.
The driver will be non-operational due to
this error.

The fabric proxy failed to initialize due

[chars] with error: [hex] ([chars]).

The fabric proxy failed to create an event

manager during the initialization. The
driver will be non-operational due to this
error.

Fabric proxy failed ltrace initialization with

error: [hex] ([chars]).

The fabric proxy could not open/initialize

the ltrace buffer. The proxy and the system
should stll function as normal, with the
exception that ltrace will not be available.

Fabric server encountered an error while

initializing the CPU control ASIC to either
receive packets from the fabricq ASIC or
transmit packets from the ingressq ASIC.
Failed to initialize the the CPU control ASIC This is crucial for the process and is
interface to [chars]: [chars]. Exiting...
automatically restarted on this failure.

Failed to register event handler, Reason:

[chars]([dec]). Exiting...

Fabric server encountered an error while

trying to register event handler for the
posix message queue. This facility is
deemed crucial and the process
automatically restarts on this failure.

Fabric server encountered an error while

trying to register event handler for
disconnection or connection error event.
This facility is deemed crucial and the
Failed to register handler for disconnection process automatically restarts on this
with EVM, Reason: [chars]([dec]). Exiting... failure.

Failed to open connection with EVM,

Reason: [chars]([dec]). Exiting...

Fabric server encountered an error while

trying to open connection with event
manager. This facility is deemed crucial
and the process automatically restarts on
this failure.

Failed to create the event manager.

Reason: [chars]. Exiting...

Fabric server encountered an error while

attempting to create an event manager.
This failures affects the ability of the
process to service various messages /
pulses from other threads / processes. This
facility is deemed crucial and the process
automatically restarts on this failure. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover.

[chars](id [unsigned int], event [unsigned

int]). Invalid req_state [unsigned int]!
Exiting...

Fabric server encountered an

unexpected/invalid state while trying to
process an event for a client request. This
facility is deemed crucial and the process
automatically restarts on this failure.

Heartbeat connection broken to node

[unsigned int]

Fabric server heartbeat monitoring

mechanism detected interruption in the
periodic 'Hello' messages.

Heartbeat State Machine was found to be

in invalid state [unsigned int] while
processing event [unsigned int].

Fabric server heartbeat monitoring

mechanism detected a problem in the
internal state machine.

[chars] during the initialization. Reason:

[chars]. Exiting...

Fabric server encountered the specified

error during the initialization sequence.
This facility is deemed crucial and hence
the process is automatically restarted on
this failure. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover.

[chars]() rrw lock: 0x[pointer]

Fabric server failed to aquire rrw lock to the

request record area in shared memory.

[chars]() rrw lock: 0x[pointer]

Fabric server failed to release rrw lock to

the request record area in shared memory.
This is a fatal error, the process will
automatically restart.

Failed to set the thread attribute: [chars].

Exiting...

Fabric server encountered an error while

setting the thread attribute during the
process initialization sequence. This is
crucial for the process and is automatically
restarted on this failure.

Fabric server encountered an error while

creating a mutex for use by a client with
the specified ID. This is crucial for the
Failed to initialize a mutex for client with ID process and is automatically restarted on
[dec]: [chars]. Exiting...
this failure.

Shared memory region [chars] [chars]

changed: old [unsigned int], new [unsigned Fabric server encountered a change in the
int]. Reinitializing...
shared memory region parameter.

Fabric server encountered an error while

initializing the CPU control ASIC to either
receive packets from the fabricq ASIC or
transmit packets from the ingressq ASIC.
Failed to initialize the the CPU control ASIC This is crucial for the process and is
interface to [chars]: [chars]. Exiting...
automatically restarted on this failure.

Failed to register event handler, Reason:

[chars]([dec]). Exiting...

Fabric server encountered an error while

trying to register event handler for the
posix message queue. This facility is
deemed crucial and the process
automatically restarts on this failure.

Fabric server encountered an error while

trying to register event handler for
disconnection or connection error event.
This facility is deemed crucial and the
Failed to register handler for disconnection process automatically restarts on this
with EVM, Reason: [chars]([dec]). Exiting... failure.

Failed to open connection with EVM,

Reason: [chars]([dec]). Exiting...

Fabric server encountered an error while

trying to open connection with event
manager. This facility is deemed crucial
and the process automatically restarts on
this failure.

Failed to create the event manager.

Reason: [chars]. Exiting...

Fabric server encountered an error while

attempting to create an event manager.
This failures affects the ability of the
process to service various messages /
pulses from other threads / processes. This
facility is deemed crucial and the process
automatically restarts on this failure. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover.

[chars](id [unsigned int], event [unsigned

int]). Invalid req_state [unsigned int]!
Exiting...

Fabric server encountered an

unexpected/invalid state while trying to
process an event for a client request. This
facility is deemed crucial and the process
automatically restarts on this failure.

Heartbeat connection broken to node

[unsigned int]

Fabric server heartbeat monitoring

mechanism detected interruption in the
periodic 'Hello' messages.

Heartbeat State Machine was found to be

in invalid state [unsigned int] while
processing event [unsigned int].

Fabric server heartbeat monitoring

mechanism detected a problem in the
internal state machine.

[chars] during the initialization. Reason:

[chars]. Exiting...

Fabric server encountered the specified

error during the initialization sequence.
This facility is deemed crucial and hence
the process is automatically restarted on
this failure. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover.

[chars]() rrw lock: 0x[pointer]

Fabric server failed to aquire rrw lock to the

request record area in shared memory.

[chars]() rrw lock: 0x[pointer]

Fabric server failed to release rrw lock to

the request record area in shared memory.
This is a fatal error, the process will
automatically restart.

Failed to set the thread attribute: [chars].

Exiting...

Fabric server encountered an error while

setting the thread attribute during the
process initialization sequence. This is
crucial for the process and is automatically
restarted on this failure.

Fabric server encountered an error while

creating a mutex for use by a client with
the specified ID. This is crucial for the
Failed to initialize a mutex for client with ID process and is automatically restarted on
[dec]: [chars]. Exiting...
this failure.

Shared memory region [chars] [chars]

changed: old [unsigned int], new [unsigned Fabric server encountered a change in the
int]. Reinitializing...
shared memory region parameter.

Failed to initialize [chars] trace buffer, error

[hex] ([chars])
ltrace initialization failed.

Fabric server encountered an error while

initializing the CPU control ASIC to either
receive packets from the fabricq ASIC or
transmit packets from the ingressq ASIC.
Failed to initialize the the CPU control ASIC This is crucial for the process and is
interface to [chars]: [chars]. Exiting...
automatically restarted on this failure.

Failed to register event handler, Reason:

[chars]([dec]). Exiting...

Fabric server encountered an error while

trying to register event handler for the
posix message queue. This facility is
deemed crucial and the process
automatically restarts on this failure.

Fabric server encountered an error while

trying to register event handler for
disconnection or connection error event.
This facility is deemed crucial and the
Failed to register handler for disconnection process automatically restarts on this
with EVM, Reason: [chars]([dec]). Exiting... failure.

Failed to open connection with EVM,

Reason: [chars]([dec]). Exiting...

Fabric server encountered an error while

trying to open connection with event
manager. This facility is deemed crucial
and the process automatically restarts on
this failure.

Failed to create the event manager.

Reason: [chars]. Exiting...

Fabric server encountered an error while

attempting to create an event manager.
This failures affects the ability of the
process to service various messages /
pulses from other threads / processes. This
facility is deemed crucial and the process
automatically restarts on this failure. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover.

[chars](id [unsigned int], event [unsigned

int]). Invalid req_state [unsigned int]!
Exiting...

Fabric server encountered an

unexpected/invalid state while trying to
process an event for a client request. This
facility is deemed crucial and the process
automatically restarts on this failure.

Heartbeat connection broken to node

[unsigned int]

Fabric server heartbeat monitoring

mechanism detected interruption in the
periodic 'Hello' messages.

Heartbeat State Machine was found to be

in invalid state [unsigned int] while
processing event [unsigned int].

Fabric server heartbeat monitoring

mechanism detected a problem in the
internal state machine.

[chars] during the initialization. Reason:

[chars]. Exiting...

Fabric server encountered the specified

error during the initialization sequence.
This facility is deemed crucial and hence
the process is automatically restarted on
this failure. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover.

[chars]() rrw lock: 0x[pointer]

Fabric server failed to aquire rrw lock to the

request record area in shared memory.

[chars]() rrw lock: 0x[pointer]

Fabric server failed to release rrw lock to

the request record area in shared memory.
This is a fatal error, the process will
automatically restart.

Failed to set the thread attribute: [chars].

Exiting...

Fabric server encountered an error while

setting the thread attribute during the
process initialization sequence. This is
crucial for the process and is automatically
restarted on this failure.

Fabric server encountered an error while

creating a mutex for use by a client with
the specified ID. This is crucial for the
Failed to initialize a mutex for client with ID process and is automatically restarted on
[dec]: [chars]. Exiting...
this failure.

Shared memory region [chars] [chars]

changed: old [unsigned int], new [unsigned Fabric server encountered a change in the
int]. Reinitializing...
shared memory region parameter.

ToFab component of the fabric driver has

failed. The root fault was: [chars]

When a hardware fault occurs and the

device driver cannot correct it, the Platform
Manager is required to reset the ASICs. This
error indicates that the Platform Manager
failed to reset the ASICs and the hardware
on the PRP may not be in an operational
state. This condition affects the
functionality of the entire router. %s is the
Interrupt Source.

PRP fabric queue process failed to initialize.

The fabric driver process handles fabric
connectivity. It initializes the packet FPGA
and coordinates with that fabric DLLs that
allow applications to send and recieve
packets via the fabric. An unrecoverable
failure of the process may prevent this
route processor from communicating with
other cards in the chassis. %s - indicates
Process initialization failed: [chars] Reason: the reason for the failure. %s - is the error
[chars]
reason.

Packet carving failed to initialize: [chars]

Reason: [chars]

Initial carving of a packet particle pool

failed. Platform specific memory region,
packet header and particle pool
configuration information are required by
the generic packet manager process
(PAKMAN) to operate. A failure in packet
carving initialization may prevent this route
processor from communicating with other
cards in the chassis. %s - indicates the
reason for the failure. %s - is the error
reason.

FABQ: fatal error encountered,

reason=[chars]

Fabric Queue Driver encountered a fatal

error and is not able recover from the error.
A reason text will be supplied. Call support
with this text.

Process initialization failed: ([chars]%s)

PRP fabric queue process failed to initialize.

The fabric queue process handles fabric
connectivity. It initializes and starts up the
threads in ToFab and FrFab components. An
unrecoverable failure of the process may
prevent this route processor from
communicating with other cards in the
chassis. %s - indicates the reason for the
failure. %s - is the error reason.

Packet carving failed to initialize: ([chars]

%s)

Initial carving of a packet particle pool

failed. Platform specific memory region,
packet header and particle pool
configuration information are required by
the generic packet manager process
(PAKMAN) to operate. A failure in packet
carving initialization may prevent this route
processor from communicating with other
cards in the chassis. %s - indicates the
reason for the failure. %s - is the error
reason.

PKT_INIT: [chars] failed, rc=[dec], reason:

[chars]

Packet carving function has failed.

PKT_INIT: particle_multi_pool_define failed

([chars]), rc=[dec], reason:[chars]

Initial carving of a packet particle pool has

failed.

Fabric messaging infrastructure failed:

[chars] Reason: [chars]

PRP fabric messaging infrastructure failed.

The fabric driver process handles fabric
connectivity. It initializes the packet FPGA
and coordinates with that fabric DLLs that
allow applications to send and recieve
packets via the fabric. An unrecoverable
failure of the process may prevent this
route processor from communicating with
other cards in the chassis. %s - indicates
the reason for the failure. %s - is the error
reason.

Client ID([dec]) Port([dec]) From Fabric

Packet from slot [dec] has invalid Stream
ID([dec])

The packet received from the fabric begins

with a header with Stream ID not
initialized. The issue can happen due to
hardware issue or the sender of the packet
encoded invalid information in the packet
header. %d - Client ID. Every process that
uses the fabric API has an unique Client ID.
%d - Port number (0 to 15) %d - Sender's
slot number (0 to 15) %d - Stream ID
encoded in the packet's header

Client ID([dec]) Port([dec]) From Fabric

Packet from slot [dec] has invalid Start
Offset([dec])

The packet received from the fabric begins

with a header with Start Offset less than
the required. This suggests the packet is
corrupted. The issue can happen due to
hardware issue or the sender of the packet
encoded invalid information in the packet
header. %d - Client ID. Every process that
uses the fabric API has an unique Client ID.
%d - Port number (0 to 15) %d - Sender's
slot number (0 to 15) %d - Start Offset
encoded in the packet's header

The Hummer detects a parity error on a

packet received from the fabric. This is
likely due to a hardware issue, or software
misconfigured the hardware. %d - Client ID.
Client ID([dec]) Port([dec]) Fabric FPGA
Every process that uses the fabric API has
detects Parity error from a packet received an unique Client ID. %d - Port number (0 to
from the Fabric
15)

An error is detected when the software is

trying to service an interrupt from the
Hummer FPGA. Hummer is the fabric
packet processing FPGA on the route
processor. There are 16 bidirectional ports
for 16 different traffic streams. A Hummer
port needs to be enabled in the hardware
level in order to function. A failure in
servicing the Hummer interrupt may
prevent this route processor from
communicating with other cards in the
chassis. %d - indicates the port number (0
to 15) %d - interrupt number that identifies
the interrupt type %s - a decription of the
Hummer Port([dec]) Interrupt- type([dec]) - interrupt event failure %s - is the error
[chars]: Reason: [chars]
reason

Fabric FPGA Error Interrupt: [chars]

An error is detected when the software is

trying to service an interrupt from the
Hummer fabric FPGA. Hummer is the fabric
packet processing FPGA on the route
processor. There are 16 bidirectional ports
for 16 different traffic streams. A Hummer
port needs to be enabled in the hardware
level in order to function. An error status
interrupt may indicate a hardware
condition that may prevent this route
processor from communicating with other
cards in the chassis.

Cannot disable Hummer port([dec]):

Reason: [chars]

Failed to disable Hummer port. Hummer is

the fabric packet processing FPGA on the
route processor. There are 16 bidirectional
ports for 16 different traffic streams. A
Hummer port needs to be enabled in the
hardware level in order to function. A
failure in disabling the Hummer port may
prevent this route processor from
communicating with other cards in the
chassis. It points to a HW issue or a serious
software defects. %d - indicates the port
number (0 to 15) %s - is the error reason.

Cannot enable Hummer port([dec]):

Reason: [chars]

Failed to enable Hummer port. Hummer is

the fabric packet processing FPGA on the
route processor. There are 16 bidirectional
ports for 16 different traffic streams. A
Hummer port needs to be enabled in the
hardware level in order to function. A
failure in enabling the Hummer port may
prevent this route processor from
communicating with other cards in the
chassis. %d - indicates the port number (0
to 15) %s - is the error reason.

The packet processing code formats

packets from the fabric and passes them to
the clients. When the client finished with
the packet, the packet processing code
cannot reuse the packet buffer because
none is found associated with the packet.
The issue can happen due to a software
issue with the client. %d - Client ID. Every
Client ID([dec]) Port([dec]) Packet passed process that uses the fabric API has an
to client cannot be reused since there is No unique Client ID. %d - Port number (0 to
Buffer
15)

Shared Memory failed during [chars]:

[chars]

An internal software error occurred that

prevented the fabric interface from working
properly with shared memory.

RP To Fabric Credit Count([dec]) for

destination slot [dec] is greater than the
limit. Port([dec])

PRP3 fabric hardware requires software to

track To Fabric hardware resources for each
chassis slot. During the update of this
shared per slot information, software
detected the resources for this slot
exceeded that actual maximum available.
This is likely the side affect of a packet
resource management event in the fabric
driver DLL. %d To Fabric count that exceeds
maximum %d The slot associated with the
error %d The fabric application port that
detected the error (but not necessarily the
port that caused the error.

RP To Fabric Queue slot:[dec] is Blocked,

report fault to Sysldr

The PRP3 to fabric queue of the particular

priority and slot is blocked. This means
packets that go that slot of that priority will
fail. In addition, at least one of the
multicast queues (high or low priority) is
blocked as well. This likely means the
particular slot is failing to accept packets
and will cause backpressure on the PRP to
fabric queue. Because of hardware design,
if a multicast packet includes the one faulty
slot then it will be stuck in the tofab
multicast queue, and subsequent multicast
packets will be stuck even if they do not
include the faulty slot in their slotmask.
Having the unicast queue blocked is
somewhat allowable, but having the
multicast queue blocked is not acceptable.
This error message is raised when both
unicast and multicast are blocked. In order
to alleviate this problem, the fault is sent to
sysldr, for sylsdr to decide to reload the
slot. It is very likely that the problem slot
was not accepting packets. slot:%d - is the
slot that is back pressuring to the PRP

RP To Fabric Tx Done Ring. Port:[dec], Tx

Index: [dec]: [chars]

While servicing To Fabric packets which the

PRP3 Fabric FPGA indicates have been
transmitted, software detects differences
between hardware packet list and software
cache of what was to be transmitted. Port:
%d the PRP3 hardware fabric port that
reported the issue Index:%d the index of
the Tx Done Ring when error reported %s a
decription of the To Fabric event failure

FABQ_SHOW: fatal error encountered:

[chars]

Error while executing a show command

PKT_INIT: pak mem size:[hex], pak mem

start: [hex], pak scaling:[dec]

Information on packet memory carving

Packet initialization: pak mem size:[hex],

pak mem start: [hex], pak scaling:[dec]

Information on packet memory carving.

Packet initialization: pak mem size:[hex],

pak mem start: [hex], pak scaling:[dec]

Information on packet memory carving.

The Tx POD detects a fault on a channel.

Tx POD detects a fault on Board([chars]) Tx The channel might not be functioning
Pod([dec]) Channel([dec]): [chars]%s/[dec]/ properly, and can cause cell drops, or
[dec]
corruption in the downstream.

Cannot initialize asic error lib [chars].

rc([hex]) [chars]

The sfe-drvr process cannot initialize the

infrastructure allow error capturing function
for the PODs on the fabric card.

The sfe-drvr process cannot initialize the

Cannot initialize CLI access to POD
infrastructure allow read/write access to
registers. Pod type ([dec]) rc([hex]) [chars] the POD registers on the fabric card.

[chars] rc [hex] [chars]

The 140G fabric POD DLL encountered the

annunciated internal SW error. It likely
affects the operation of the fabric POD and
the fabric subsystem on the multi-chassis.

[chars] POD detects HIGH 2.5Vcc.

Board([chars]) [chars] Pod([dec]) [chars]

The POD detects a high in 2.5Vcc voltage.

The POD might not be functioning properly,
and can cause cell drops or corruption in
the rx or tx link associated with the POD.

[chars] POD detects HIGH 3.3Vcc.

Board([chars]) [chars] Pod([dec]) [chars]

The POD detects a high in 3.3Vcc voltage.

The POD might not be functioning properly,
and can cause cell drops or corruption in
the rx or tx link associated with the POD.

[chars] POD detects HIGH temperature.

Board([chars]) [chars] Pod([dec]) [chars]

The POD detects a high temperature. The

POD might not be functioning properly, and
can cause cell drops or corruption in the rx
or tx link associated with the POD.

[chars] POD detects LOW 2.5Vcc.

Board([chars]) [chars] Pod([dec]) [chars]

The POD detects a low in 2.5Vcc voltage.

The POD might not be functioning properly,
and can cause cell drops or corruption in
the rx or tx link associated with the POD.

[chars] POD detects LOW 3.3Vcc.

Board([chars]) [chars] Pod([dec]) [chars]

The POD detects a low in 3.3Vcc voltage.

The POD might not be functioning properly,
and can cause cell drops or corruption in
the rx or tx link associated with the POD.

[chars] POD detects LOW temperature.

Board([chars]) [chars] Pod([dec]) [chars]

The POD detects a low temperature. The

POD might not be functioning properly, and
can cause cell drops or corruption in the rx
or tx link associated with the POD.

Rx POD detects HIGH power on

Board([chars]) Rx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]
[chars]

The POD detects a high power on a

channel. The channel might not be
functioning properly, and can cause cell
drops, or corruption from received cells.

Rx POD detects LOW power on

Board([chars]) Rx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]
[chars]

The POD detects a low power on a channel.

This is a precursor to Rx LOS errors in the
channel. The link is now marginal, and the
superstar Rx link may be seeing
correctable errors. Although the link is still
working, it is marginal and can become
inoperational in due course. This is also
likely due to contaminates in the optical
cable and/or connector. Please check if the
optical cable and/or connector are secured,
and clean the components as necessary.

Rx POD detects loss of signal on

Board([chars]) Rx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]

The Rx POD detects a loss of signal on a

channel. This can be due to: [1] The link is
configured by software to be receiving cells
with an invalid transmit end [2] The link is
not physically connect to the Tx side. For
[1], it is a software bug where a Rx link
should only be configured if it has a valid
transmit end. For [2], if the Rx channel
suddenly sees this without any physical
change of the optical cable or shut down of
the other end, then it is likely the POD
channel has become defective. If the
optical cable connecting the POD is cut,
then the Rx POD will see loss of signal.

Spurious interrupt (with zero value in

interrupt status) on Board([chars]) [chars]
Pod([dec]) interrupt line.

An interrupt is generated but the interrupt

status register indicates no pending
interrupts. This may be due to a hardware
error where the interrupt line is stuck in its
active state i.e. active low.

Tx POD detects HIGH bias current on

Board([chars]) Tx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]
[chars]

The Tx POD detects a high bias current on

a channel. The channel might not be
functioning properly, and can cause cell
drops, or corruption in the downstream.

Tx POD detects HIGH power on

Board([chars]) Tx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]
[chars]

The POD detects a high power on a

channel. The channel might not be
functioning properly, and can cause cell
drops, or corruption in the downstream.

Tx POD detects LOW bias current on

Board([chars]) Tx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]
[chars]

The Tx POD detects a low bias current on a

channel. The channel might not be
functioning properly, and can cause cell
drops, or corruption in the downstream.

Tx POD detects LOW power on

Board([chars]) Tx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]
[chars]

The POD detects a low power on a channel.

The channel may not be functioning
properly, and can cause cell drops, or
corruption in the downstream. This is a
precursor to the Tx LOS.

Tx POD detects loss of signal on

Board([chars]) Tx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]

The Tx POD detects a loss of signal on a

channel. This can be due to: [1] A valid
superstar Tx link is not powered on by
software [2] An invalid superstar Tx link
has the corresponding Tx POD channel
configured [3] A valid superstar Tx link has
malfunction or the Tx channel has
malfunction to not receive signals from the
superstar Tx link.

The Rx POD detects an unknown error on a

channel. The channel might not be
functioning properly, and can cause cell
Rx POD detects an unknown error
drops, or corruption from received cells.
type([dec]) on Board([chars]) Rx Pod([dec]) There can also be a software bug such that
Channel([dec]): [chars]%s/[dec]/[dec]
the error is not handled

The Rx POD detects an unknown error on a

pod. The pod might not be functioning
properly, and can cause cell drops, or
corruption from received cells. There can
Rx POD detects an unknown error
also be a software bug such that the error
type([dec]) on Board([chars]) Rx Pod([dec]) is not handled

The Tx POD detects an unknown error on a

channel. The channel might not be
functioning properly, and can cause cell
Tx POD detects an unknown error
drops, or corruption from received cells.
type([dec]) on Board([chars]) Tx Pod([dec]) There can also be a software bug such that
Channel([dec]): [chars]%s/[dec]/[dec]
the error is not handled

The Tx POD detects an unknown error on a

pod. The pod might not be functioning
properly, and can cause cell drops, or
corruption from received cells. There can
Tx POD detects an unknown error
also be a software bug such that the error
type([dec]) on Board([chars]) Tx Pod([dec]) is not handled

Rx POD detects LOP signal on Board

([chars]) Pod RX([dec]) for all
channel,Check Pod RX([dec]) health to
confirm.

The Rx POD detects LOP signal on all

channels. Please check sh controllers fabric
pod health <> <> <> to confirm the
same.

Rx POD detects LOS signal on Board

([chars]) Pod RX([dec]) for all
channel,Check Pod RX([dec]) health to
confirm.

The Rx POD detects a LOS signal on all

channels. Please check sh controllers fabric
pod health <> <> <> to confirm the
same.

The Tx POD detects a fault on a channel.

Tx POD detects a fault on Board([chars]) Tx The channel might not be functioning
Pod([dec]) Channel([dec]): [chars]%s/[dec]/ properly, and can cause cell drops, or
[dec]
corruption in the downstream.

Cannot initialize asic error lib [chars].

rc([hex]) [chars]

The sfe-drvr process cannot initialize the

infrastructure allow error capturing function
for the PODs on the fabric card.

The sfe-drvr process cannot initialize the

Cannot initialize CLI access to Topaz [chars] infrastructure allow read/write access to
POD registers. rc([hex]) [chars]
the POD registers on the fabric card.

[chars] rc [hex] [chars]

The 400G fabric POD DLL encountered the

annunciated internal SW error. It likely
affects the operation of the fabric POD and
the fabric subsystem on the multi-chassis.

[chars] POD detects HIGH 2.5Vcc.

Board([chars]) [chars] Pod([dec]) [chars]

The POD detects a high in 2.5Vcc voltage.

The POD might not be functioning properly,
and can cause cell drops or corruption in
the rx or tx link associated with the POD.

[chars] POD detects HIGH 3.3Vcc.

Board([chars]) [chars] Pod([dec]) [chars]

The POD detects a high in 3.3Vcc voltage.

The POD might not be functioning properly,
and can cause cell drops or corruption in
the rx or tx link associated with the POD.

[chars] POD detects HIGH temperature.

Board([chars]) [chars] Pod([dec]) [chars]

The POD detects a high temperature. The

POD might not be functioning properly, and
can cause cell drops or corruption in the rx
or tx link associated with the POD.

[chars] POD detects LOW 2.5Vcc.

Board([chars]) [chars] Pod([dec]) [chars]

The POD detects a low in 2.5Vcc voltage.

The POD might not be functioning properly,
and can cause cell drops or corruption in
the rx or tx link associated with the POD.

[chars] POD detects LOW 3.3Vcc.

Board([chars]) [chars] Pod([dec]) [chars]

The POD detects a low in 3.3Vcc voltage.

The POD might not be functioning properly,
and can cause cell drops or corruption in
the rx or tx link associated with the POD.

[chars] POD detects LOW temperature.

Board([chars]) [chars] Pod([dec]) [chars]

The POD detects a low temperature. The

POD might not be functioning properly, and
can cause cell drops or corruption in the rx
or tx link associated with the POD.

Rx POD detects HIGH power on

Board([chars]) Rx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]
[chars]

The POD detects a high power on a

channel. The channel might not be
functioning properly, and can cause cell
drops, or corruption from received cells.

Rx POD detects LOW power on

Board([chars]) Rx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]
[chars]

The POD detects a low power on a channel.

This is a precursor to Rx LOS errors in the
channel. The link is now marginal, and the
superstar Rx link may be seeing
correctable errors. Although the link is still
working, it is marginal and can become
inoperational in due course. This is also
likely due to contaminates in the optical
cable and/or connector. Please check if the
optical cable and/or connector are secured,
and clean the components as necessary.

Rx POD detects loss of signal on

Board([chars]) Rx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]

The Rx POD detects a loss of signal on a

channel. This can be due to: [1] The link is
configured by software to be receiving cells
with an invalid transmit end [2] The link is
not physically connect to the Tx side. For
[1], it is a software bug where a Rx link
should only be configured if it has a valid
transmit end. For [2], if the Rx channel
suddenly sees this without any physical
change of the optical cable or shut down of
the other end, then it is likely the POD
channel has become defective. If the
optical cable connecting the POD is cut,
then the Rx POD will see loss of signal.

Spurious interrupt (with zero value in

interrupt status) on Board([chars]) [chars]
Pod([dec]) interrupt line.

An interrupt is generated but the interrupt

status register indicates no pending
interrupts. This may be due to a hardware
error where the interrupt line is stuck in its
active state i.e. active low.

Tx POD detects HIGH bias current on

Board([chars]) Tx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]
[chars]

The Tx POD detects a high bias current on

a channel. The channel might not be
functioning properly, and can cause cell
drops, or corruption in the downstream.

Tx POD detects HIGH power on

Board([chars]) Tx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]
[chars]

The POD detects a high power on a

channel. The channel might not be
functioning properly, and can cause cell
drops, or corruption in the downstream.

Tx POD detects LOW bias current on

Board([chars]) Tx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]
[chars]

The Tx POD detects a low bias current on a

channel. The channel might not be
functioning properly, and can cause cell
drops, or corruption in the downstream.

Tx POD detects LOW power on

Board([chars]) Tx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]
[chars]

The POD detects a low power on a channel.

The channel may not be functioning
properly, and can cause cell drops, or
corruption in the downstream. This is a
precursor to the Tx LOS.

Tx POD detects loss of signal on

Board([chars]) Tx Pod([dec])
Channel([dec]): [chars]%s/[dec]/[dec]

The Tx POD detects a loss of signal on a

channel. This can be due to: [1] A valid
superstar Tx link is not powered on by
software [2] An invalid superstar Tx link
has the corresponding Tx POD channel
configured [3] A valid superstar Tx link has
malfunction or the Tx channel has
malfunction to not receive signals from the
superstar Tx link.

The Rx POD detects an unknown error on a

channel. The channel might not be
functioning properly, and can cause cell
Rx POD detects an unknown error
drops, or corruption from received cells.
type([dec]) on Board([chars]) Rx Pod([dec]) There can also be a software bug such that
Channel([dec]): [chars]%s/[dec]/[dec]
the error is not handled

The Rx POD detects an unknown error on a

pod. The pod might not be functioning
properly, and can cause cell drops, or
corruption from received cells. There can
Rx POD detects an unknown error
also be a software bug such that the error
type([dec]) on Board([chars]) Rx Pod([dec]) is not handled

The Tx POD detects an unknown error on a

channel. The channel might not be
functioning properly, and can cause cell
Tx POD detects an unknown error
drops, or corruption from received cells.
type([dec]) on Board([chars]) Tx Pod([dec]) There can also be a software bug such that
Channel([dec]): [chars]%s/[dec]/[dec]
the error is not handled

The Tx POD detects an unknown error on a

pod. The pod might not be functioning
properly, and can cause cell drops, or
corruption from received cells. There can
Tx POD detects an unknown error
also be a software bug such that the error
type([dec]) on Board([chars]) Tx Pod([dec]) is not handled

Fabric driver encountered the annunciated

error during the driver initialization. The
System Manager process (sysmgr) will
automatically respawn the (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
Initialization of fabric driver failed: [chars] ; node reloads, the shelf manager will
exiting...
permanently shutdown the node.

SFE driver failed to create event manager

for [chars].

The SFE common infra driver was unable to

create an event manager for processing
messages and hence failed to initialize.
The System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

[chars]; [chars]

The SFE common infra driver driver

encountered a SW error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

SFE common infra driver was unable to

allocate [dec] bytes

The SFE common infra driver was unable to

allocate memory. The System Manager
process (sysmgr) will automatically
respawn this process, up to a fixed number
of times the error is encountered, to
recover. If the problem continues, sysmgr
will trigger node reload. After a certain
number of node reloads, the shelf manager
will permanently shutdown the node.

The SFE common infra driver could not

open the ltrace buffer. The SFE common
infra driver and the system should function
SFE common infra driver failed to initialize as normal, with the exception that ltrace
the ltrace file [chars]; rc = [chars]
will not be available for sfe_drvr process.

SFE common infra driver failed to initialize The SFE common infra driver could not
shm [chars]; rc = [chars]
initialize shelfmgr.

Fabric ASIC access timed out (reported by

lite process)

This indicates that the fabric ASIC failed to

acknowledge an access request from the
CPU. This can happen if the host CPU tries
to access an address that is out of range
for the ASIC. Also, accessing a register from
a block that is still in the logic reset state
could stall this access and subsequent
accesses to the ASIC.

Initialization of fabric driver lite failed:

[chars] ; exiting...

Fabric driver encountered the annunciated

error during the driver initialization. The
System Manager process (sysmgr) will
automatically respawn the (sfe_drvr_lite)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

The Fabric driver was unable to create an

event manager for processing messages
and hence failed to initialize. The System
Manager process (sysmgr) will
automatically respawn this (sfe_drvr_lite)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
Failed to create event manager for '[chars]' permanently shutdown the node.
Shared Memory Error: [chars]

Attempt to init/open the shared memory

fails

The Fabric driver was unable to change the

interrupt thread to an IO thread. Because of
this failure, the interupt thread will not be
able to receive the interupt thread events.
The System Manager process (sysmgr) will
automatically respawn this (sfe_drvr_lite)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
FABRIC driver lite failed to change interupt node reloads, the shelf manager will
thread to an IO thread: [chars]
permanently shutdown the node.

Fabric driver lite failed to initialize the

ltrace - rc = [chars]

The Fabric driver could not open/initialize

the ltrace buffer. The Fabric driver and the
system should stll function as normal, with
the exception that ltrace will not be
available for sfe_drvr process.

Fabric ASICs initialized (reported by lite

process)

This indicates Fabric ASICs are initialized

and is expected during normal operation.

Initialization of shared memory failed:

[chars]

Fabric driver encountered the annunciated

error during the shared memory
initialization. The fabric driver cannot
complete the initialization of the fabric
ASICs.

[chars]. Register: [hex] Current Status:

[hex]. Expected Status: [hex].

Fabric board is not operational due to the

indicated fault. This information is
extracted from the fabric PLD registers.

[chars]. Register: [hex] Current Status:

[hex]. Expected Status: [hex].

Fabric board is not operational due to the

indicated fault. This information is
extracted from the fabric PLD registers.

[chars]

Fabric board is not operational due to the a

power fault.

[chars]

Fabric board is not operational due to the a

power fault.

Fabric CPLD detects power fault: [chars]

Fabric CPLD detects the specified power

fault. If the failure is for the LTC2978
device, then this error is due to the failure
of the cctl library function call.

Fabric FPGA detects power fault: [chars]

Fabric FPGA detects the specified power

fault. If the failure is for the LTC2978
device, then this error is due to the failure
of the cctl library function call.

The specified device could not be halted

using the CPLD register. Use the fabric
ASICs internal register to halt the device.
Failed to halt [chars] using CPLD halt assert This message is meant to catch specific
signal. Halting ASIC via its internal register. hardware failure.

The specified device could not be halted

using the FPGA register. Use the fabric
ASICs internal register to halt the device.
Failed to halt [chars] using FPGS halt assert This message is meant to catch specific
signal. Halting ASIC via its internal register. hardware failure.

[chars].

The fabric driver verifies the hardware

interfaces between the various
components on the fabric board. This is
done on cold start (POST) and periodically
there after. This message is annunciated
when any of the tests fail.

[chars].

The fabric driver verifies the hardware

interfaces between the various
components on the fabric board. This is
done on cold start (POST) and periodically
there after. This message is annunciated
when any of the tests fail.

[chars].

The fabric driver verifies the hardware

interfaces between the various
components on the fabric board. This is
done on cold start (POST) and periodically
there after. This message is annunciated
when any of the tests fail.

[chars].

The board initialization failed the specified

operation while configuring the device. The
driver will exit and attempt to come up
again. On multiple such failures, the board
will be shutdown permanently by the shelf
manager.

[chars].

The board initialization failed the specified

operation while configuring the device. The
driver will exit and attempt to come up
again. On multiple such failures, the board
will be shutdown permanently by the shelf
manager.

Fabric FPGA detects the specified local bus

Fabric FPGA detects localbus fault: [chars]. fault.

Fabric CPLD detects the specified local bus

Fabric CPLD detects localbus fault: [chars]. fault.

Reload fabric card as [chars] was reset for

maximum allowed times ([dec])

A fabric ASIC may be reset a maximum of 5

times and thereafter the fabric driver
requests for the card to be reloaded. On
the fifth reset, the card is reloaded.

Reload fabric card as [chars] was reset for

maximum allowed times ([dec])

A fabric ASIC may be reset a maximum of 5

times and thereafter the fabric driver
requests for the card to be reloaded. On
the fifth reset, the card is reloaded.

Sapir_[dec] - Speed mismatch while

configuring link [dec]. (Expected = [dec],
Actual = [dec])

Unexpected macro type value read from

ASIC. There could be a h/w or FPGA issue.

Sapir_[dec] - Speed mismatch while

configuring link [dec]. (Expected = [dec],
Actual = [dec])

Unexpected macro type value read from

ASIC. There could be a h/w or FPGA issue.

Fabric driver detected hardware errors and

requested sysmgr to place the card in
maintenance mode. But sysmgr failed to do
so. The card and its fabric ASICs should
Failed to put card in maintenance mode by have been isolated from the system before
sysmgr. error code([hex]) - [chars]
attempting going to maintenance mode.

Failed to shutdown by shelfmgr. error

code([hex]) - [chars]

Fabric driver detected hardware errors and

requested shelfmgr to shut down the node.
But shelfmgr failed to do so. The card and
its fabric ASICs should have been isolated
from the system before the shutdown
attempt.

FABRIC driver: SYSDB unable to bind to

[chars]. Error: [chars]

In Fabric Driver, unable to bind sysdb item.

It could be an Infra-sysdb issue OR fabric
sysdb tuple name issue.

FABRIC driver: SYSDB unable to bind to

[chars]. Error: [chars]

In Fabric Driver, unable to bind sysdb item.

It could be an Infra-sysdb issue OR fabric
sysdb tuple name issue.

FABRIC driver: SYSDB unable to register

notification of pod-err/suppress. Error:
[chars]

In Fabric Driver, unable to register

notification of pod-err/suppress. It could be
an Infra-sysdb issue OR fabric sysdb tuple
name issue.

FABRIC driver: SYSDB unable to register

notification of pod-err/suppress. Error:
[chars]

In Fabric Driver, unable to register

notification of pod-err/suppress. It could be
an Infra-sysdb issue OR fabric sysdb tuple
name issue.

BM Dead Node Failure Occured for

Aggregation Node ([chars]) : ([chars]).

All the receive links for a particular stage

have gone down triggering the ASIC to go
into BM Dead Node. Software will auto
recover. Dead node is expected to be seen
during plane shut as well as SM OIR where
it will result in all receive links of a
particular stage to go down.

BM Dead Node Failure Occured for

Aggregation Node ([chars]) : ([chars]).

All the receive links for a particular stage

have gone down triggering the ASIC to go
into BM Dead Node. Software will auto
recover. Dead node is expected to be seen
during plane shut as well as SM OIR where
it will result in all receive links of a
particular stage to go down.

BM Dead Node Recovery Failure Occured,

Dead Node Status ([chars]) : ([hex]).

We were unable to recovery from dead

node state. We attempted 3 times, but
dead node clearning recovery is failing.

BM Dead Node Recovery Failure Occured,

Dead Node Status ([chars]) : ([hex]).

We were unable to recovery from dead

node state. We attempted 3 times, but
dead node clearning recovery is failing.

Fabric driver failed to initialize the CPLD

interrupts with CCI: err code([hex])

Fabric driver cannot initialize the CPLD

interrupts with CCI infrastructure. The node
may not be able to handle CPLD interrupts.

Fabric driver failed to initialize the FPGA

interrupts with CCI: err code([hex])

Fabric driver cannot initialize the FPGA

interrupts with CCI infrastructure. The node
may not be able to handle FPGA interrupts.

Fabric driver cannot initialize the CPU

Controller Interface library infrastructure
Fabric driver failed to initialize the CPU
for CPLD initialization and handling. Fabric
Controller Interface library: err code([hex]) ASICs access is also compromised.

Fabric driver cannot initialize the CPU

Controller Interface library infrastructure
Fabric driver failed to initialize the CPU
for FPGA initialization and handling. Fabric
Controller Interface library: err code([hex]) ASICs access is also compromised.

Fabric: CDR event message attach failed.

Error: [chars]

Fabric:CDR event message attach failed.

Fabric:CDR Hardware Init failed. Error:

[chars]

Failed to initilise fabric CDR hardware.

[chars] Maxim CDR initialisation failed on

instance [dec]

Driver failed to initialize one of the maxim

CDR hardware modules instance.This
happens when the write to a CDR register
fails.

[chars]

Fabric:CDR driver LWM message reply

failed.

[chars]

Fabric:CDR driver failed to register for

notification from shelf-manager. Please
check with shelf-mgr team.

[chars]

Fabric:CDR shared memory error.

Fabric driver cannot initialize the Common

Interrupt library infrastructure for interrupt
Fabric driver failed to initialize the Common and error handling and logging. The node
Interrupt Handling library: err code([hex]) might not be able to handle interrupts.

Fabric driver cannot initialize the Common

Interrupt library infrastructure for interrupt
Fabric driver failed to initialize the Common and error handling and logging. The node
Interrupt Handling library: err code([hex]) might not be able to handle interrupts.

Fabric driver failed to initialize the Debug

TCAM library: err code([hex])

Fabric driver cannot initialize the Debug

TCAM library. The node may be not be able
to use the debug TCAM to debug cell flows
through the fabric ASICs.

Fabric driver failed to initialize the Debug

TCAM library: err code([hex])

Fabric driver cannot initialize the Debug

TCAM library. The node may be not be able
to use the debug TCAM to debug cell flows
through the fabric ASICs.

[chars]: [chars].

Fabric driver cannot proceed due to the

indicated error.

[chars]: [chars].

Fabric driver cannot proceed due to the

indicated error.

FGID SRAM BIST failed to complete for

[chars]. Result of SRAM BIST: [hex]

This message is seen when the FGID SRAM

BIST operation fails to complete after a \
request is issued to start it for the
identified ASIC. The result of the BIST \
operation for that ASIC is also captured in
the message. This condition implies \ that
the ASIC is either not powered up or it is
not properly reset at initialization.

FGID SRAM BIST failed for [chars]. Pass

status: [hex] Expected Pass status: [hex]

This message is seen when the FGID SRAM

BIST is completed without the necessary
pass \ bits being set for the identified ASIC.
Observed pass bits status and the
expected \ status for the ASIC are also
captured in the message. The pass status
is a 3 bit status \ i.e. one per SRAM.
Number of SRAMs depend on the fabric
stage and the fabric board as \ specified
below: \ S2 Card: 3 SRAMs i.e. SRAM A,
SRAM B & SRAM C. \ S2 ASIC on S123 Cards
(all LCC flavors): 1 SRAM i.e. SRAM A. \ S3
ASIC on S123 & S13 Cards (all LCC flavors):
2 SRAMs i.e. SRAM A & SRAM B. \ Pass
status bit positions: \ SRAM A: bit 2 \ SRAM
B: bit 1 \ SRAM C: bit 0.

Identified Fabric ASIC experienced a severe

ASIC [chars] in error & halted. Hard reset to error and is halted. Hard reset & rerecover.
initialize the ASIC to recover.

Identified Fabric ASIC experienced a severe

ASIC [chars] in error & halted. Hard reset to error and is halted. Hard reset & rerecover.
initialize the ASIC to recover.

ASIC [chars] in error & halted. Power-On

reset to recover.

Identified Fabric ASIC experienced a severe

error and is halted. Power on reset & reinitialize the ASIC to recover.

ASIC [chars] in error & halted. Power-On

reset to recover.

Identified Fabric ASIC experienced a severe

error and is halted. Power on reset & reinitialize the ASIC to recover.

SPB is not designed for supporting SPBmotherboard JTAG operation necessary for
asic scan functionality. SPB board with this
Combined SPB-motherboard for JTAG not
support will have a 73 level base number
supported. Ensure 73 level base number is of 12773. This value is programmed in the
12773
SPB EEPROM at locations 42 to 44.

SPB is not designed for supporting SPBmotherboard JTAG operation necessary for
asic scan functionality. SPB board with this
Combined SPB-motherboard for JTAG not
support will have a 73 level base number
supported. Ensure 73 level base number is of 12773. This value is programmed in the
12773
SPB EEPROM at locations 42 to 44.

[[chars]]: [chars][LEAF ID: [hex]]; TYPE:

[chars] [[chars]]; SYSTEM EFFECT:[chars];
ACTION TAKEN:[chars].

This message is logged whenever an ASIC

detects an error. This message includes:\
ASIC identifier, interrupt name & its ID, \
Interrupt type, effect of the error on the
system & the software action taken.

[[chars]]: [chars][LEAF ID: [hex]]; TYPE:

[chars] [[chars]]; SYSTEM EFFECT:[chars];
ACTION TAKEN:[chars].

This message is logged whenever an ASIC

detects an error. This message includes:\
ASIC identifier, interrupt name & its ID, \
Interrupt type, effect of the error on the
system & the software action taken.

[chars]. Current Status: [hex]. Expected

Status: [hex].

Power controllers on the fabric card are

raising the alerts indicating that either the
voltages or temperature on the card is at
its tolerance limits.

[chars]. Current Status: [hex]. Expected

Status: [hex].

Power controllers on the fabric card are

raising the alerts indicating that either the
voltages or temperature on the card is at
its tolerance limits.

Fabric Board PLD Version ([dec]) not

supported. Upgrade to latest.

This indicates that the fabric board is

running with PLD version that is not
supported. Version lower than (0x1c) is not
supported. Please upgrade to the latest
PLD Version.

Failed to send a message due to invalid link

Unable to dispatch messages due to invalid check. Possible corruption in dispatch
link check ([dec])
pulse.

Fabric driver encountered the annunciated

error during the driver initialization. The
System Manager process (sysmgr) will
automatically respawn the (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
Initialization of fabric driver failed: [chars] ; node reloads, the shelf manager will
exiting...
permanently shutdown the node.

Fabric driver encountered the annunciated

error during the driver initialization. The
System Manager process (sysmgr) will
automatically respawn the (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
Initialization of fabric driver failed: [chars] ; node reloads, the shelf manager will
exiting...
permanently shutdown the node.

Fabric driver encountered the annunciated

error during the driver initialization. The
System Manager process (sysmgr) will
automatically respawn the (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
Initialization of fabric driver failed: [chars] ; node reloads, the shelf manager will
exiting...
permanently shutdown the node.

The Fabric driver was unable to create an

event manager for processing messages
and hence failed to initialize. The System
Manager process (sysmgr) will
automatically respawn this (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
Failed to create event manager for '[chars]' permanently shutdown the node.

The Fabric driver was unable to create an

event manager for processing messages
and hence failed to initialize. The System
Manager process (sysmgr) will
automatically respawn this (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
Failed to create event manager for '[chars]' permanently shutdown the node.

The Fabric driver was unable to create an

event manager for processing messages
and hence failed to initialize. The System
Manager process (sysmgr) will
automatically respawn this (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
Failed to create event manager for '[chars]' permanently shutdown the node.

Fabric Board Going down. FGID access

being aborted.

One or more ASICs for the stage on the

fabric card are being reset. Hence this
multicast FGID access operation for the
specified stage is aborted. This may be
seen on any SM node going down, during
asic reset cleanup process.

Request [dec] to refresh FGID entry [hex].

An FGID entry is disabled following a parity

error. A request to refresh the entry is
issued.

Failed to refresh FGID entry. Reload the

fabric card.

An FGID entry is disabled following a parity

error. Request to refresh the entry wasn't
entertained. This will reload the fabric card
to recover.

One or more ASICs for the stage on the

fabric card are in being reset. Hence this
Device(s) being reset. [chars] FGID write to multicast FGID write operation for the
offset [hex] aborted.
specified stage is aborted.

Access to invalid device id ([dec]).

This indicates that an attempt to access

internal information was made to an invalid
device id.

Access to invalid device id ([dec]).

This indicates that an attempt to access

internal information was made to an invalid
device id.

Sapir_[dec] - Unexpected macro type

([dec]) for DORM[dec] Quad[dec] (addr =
[hex], value = [hex])

Unexpected macro type value read from

ASIC. There could be a h/w or FPGA issue.

Fabric driver failed to initialize ASIC error

infrastructure: err code([hex])

Fabric driver cannot initialize the ASIC error

infrastructure for recording ASIC errors and
interrupts. The node is compromised in
handling those errors.

Fabric driver failed to initialize ASIC error

infrastructure: err code([hex])

Fabric driver cannot initialize the ASIC error

infrastructure for recording ASIC errors and
interrupts. The node is compromised in
handling those errors.

Maximum attempts to receive topology

information exceeded. Restarting
sfe_drvr ...

This indicates that the maximum tries for

the driver to receive the necessary
topology information to initialize the asic
has exceeded. The driver will not
continually re-request topology
information.

Maximum attempts to receive topology

information exceeded. Restarting
sfe_drvr ...

This indicates that the maximum tries for

the driver to receive the necessary
topology information to initialize the asic
has exceeded. The driver will not
continually re-request topology
information.

Maximum attempts to receive topology

information exceeded. Restarting
sfe_drvr ...

This indicates that the maximum tries for

the driver to receive the necessary
topology information to initialize the asic
has exceeded. The driver will not
continually re-request topology
information.

Error Allocating <[dec]> bytes of memory

Failed to allocate memory from Heap. This

can happen during periods of intense
memory resource usage or due to a
memory leak - though these are extremely
rare occurances. This message implies
some message(s) between FSDB and SFE
driver was not processed and so they might
be out of sync.

Error Allocating <[dec]> bytes of memory

Failed to allocate memory from Heap. This

can happen during periods of intense
memory resource usage or due to a
memory leak - though these are extremely
rare occurances. This message implies
some message(s) between FSDB and SFE
driver was not processed and so they might
be out of sync.

Error Allocating <[dec]> bytes of memory

Failed to allocate memory from Heap. This

can happen during periods of intense
memory resource usage or due to a
memory leak - though these are extremely
rare occurances. This message implies
some message(s) between FSDB and SFE
driver was not processed and so they might
be out of sync.

Failed to initialize POD for node: [hex],

error : [chars]; exiting...

Fabric Driver failed to initialize one of the

POD hardware modules. The System
Manager process (sysmgr) will
automatically respawn the (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

Failed to initialize PODs - error([hex]) :

[chars]; exiting...

Fabric Driver failed to initialize one of the

POD hardware modules. The System
Manager process (sysmgr) will
automatically respawn the (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

Failed to initialize PODs - error([hex]) :

[chars]; exiting...

Fabric Driver failed to initialize one of the

POD hardware modules. The System
Manager process (sysmgr) will
automatically respawn the (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

Re-initialization of fabric driver following

post pfd failed. Error: [chars]

Fabric driver re-initialization of all ASICs

and recover failed. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Re-initialization of fabric driver following

post pfd failed. Error : [chars]

Fabric driver re-initialization of all ASICs

and recover failed. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Failed to reload. [chars]

Fabric driver encountered an error when

trying to reload. The card cannot be
reloaded at the time of the message. Fabric
driver may retry again when resources and
conditions are met. The card and its fabric
ASICs should have been isolated from the
system.

Persistent errors seen on ASIC [chars].

Shutdown the fabric card.

The ASIC on the fabric board is faulty and

being taken out of operation.

Persistent errors seen on ASIC [chars].

Shutdown the fabric card.

The ASIC on the fabric board is faulty and

being taken out of operation.

SFE driver requesting PFM to reload card

Fabric driver encountered a system error

which shelfmgr cannot reload the node.
The fabric driver self-reloads instead. The
card and its fabric ASICs should have been
isolated from the system before the selfreload.

Failed to reload by shelf-mgr <[hex]

[[chars]]>. Self-reloading...

Fabric driver encountered a system error

which shelf-mgr cannot reload the node.
The fabric driver self-reloads instead. The
card and its fabric ASICs should have been
isolated from the system before the selfreload.

Failed to reload by shelf-mgr <[hex]

[[chars]]>. Self-reloading...

Fabric driver encountered a system error

which shelf-mgr cannot reload the node.
The fabric driver self-reloads instead. The
card and its fabric ASICs should have been
isolated from the system before the selfreload.

Spurious interrupt (with zero value in

interrupt status) on [chars] interrupt line.

An interrupt is generated but the interrupt

status register indicates no pending
interrupts. This may be due to a hardware
error where the interrupt line is stuck in its
active state i.e. active low.

Spurious interrupt (with zero value in

interrupt status) on [chars] interrupt line.

An interrupt is generated but the interrupt

status register indicates no pending
interrupts. This may be due to a hardware
error where the interrupt line is stuck in its
active state i.e. active low.

Spurious interrupt (with zero value in

interrupt status) on interrupt line.

An interrupt is generated but the interrupt

status register indicates no pending
interrupts. This may be due to a hardware
error where the interrupt line is stuck in its
active state i.e. active low.

Barriers stuck for type [dec] at phase [dec] Barrier flow of certain type is stuck at
[curr: [hex] prev: [hex]] on [chars].
identified phase on the specified ASIC.

FABRIC driver failed to change interupt

thread to an IO thread: [chars]

The Fabric driver was unable to change the

interrupt thread to an IO thread. Because of
this failure, the interupt thread will not be
able to receive the interupt thread events.
The System Manager process (sysmgr) will
automatically respawn this (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

FABRIC driver failed to change interupt

thread to an IO thread: [chars]

The Fabric driver was unable to change the

interrupt thread to an IO thread. Because of
this failure, the interupt thread will not be
able to receive the interupt thread events.
The System Manager process (sysmgr) will
automatically respawn this (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

FABRIC driver failed to change interupt

thread to an IO thread: [chars]

The Fabric driver was unable to change the

interrupt thread to an IO thread. Because of
this failure, the interupt thread will not be
able to receive the interupt thread events.
The System Manager process (sysmgr) will
automatically respawn this (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

Leaf Timer Failed to start. Timer Type:

[dec].

Fabric driver could not start timer.

Driver timed out waiting for topology

information. Attempt re-request for
topology.

This indicates that the driver has not

received the necessary topology
information to initialize the asic. The driver
will continually re-request topology. This
message can also be seen in a multichassis
system when a fabric card is pulled out or
powered down and the other end is still up
and running or if the plane config for this
card is missing.

Driver timed out waiting for topology

information. Attempt re-request for
topology.

This indicates that the driver has not

received the necessary topology
information to initialize the asic. The driver
will continually re-request topology. This
message can also be seen in a multichassis
system when a fabric card is pulled out or
powered down and the other end is still up
and running or if the plane config for this
card is missing.

Driver timed out waiting for topology

information. Attempt re-request for
topology.

This indicates that the driver has not

received the necessary topology
information to initialize the asic. The driver
will continually re-request topology. This
message can also be seen in a multichassis
system when a fabric card is pulled out or
powered down and the other end is still up
and running or if the plane config for this
card is missing.

[chars] ; Node Key = [hex]

The Fabric driver encountered the

annunciated error. For Error Node Keys 0x1050016; 0x1050018; 0x105001A : This
indicates a hardware problem in Fabric
ASIC. Sysmgr will reload the node up to a
fixed number of times the error is
encountered, to recover. After a certain
number of node reloads, the shelf manager
will permanently shutdown the node.

[chars] ; Node Key = [hex]

The Fabric driver encountered the

annunciated error. For Error Node Keys 0x1050016; 0x1050018; 0x105001A : This
indicates a hardware problem in Fabric
ASIC. Sysmgr will reload the node up to a
fixed number of times the error is
encountered, to recover. After a certain
number of node reloads, the shelf manager
will permanently shutdown the node.

[chars] ; Node Key = [hex]

The Fabric driver encountered the

annunciated error. For Error Node Keys 0x1050016; 0x1050018; 0x105001A : This
indicates a hardware problem in Fabric
ASIC. If the displayed error is one of the
following 'Correctable Single-Bit Error in
Cell Reference FIFO' 'Correctable Single-Bit
Error in Reference Count Table' 'Correctable
Single-Bit Error in Cell Store SRAM' The
data will be corrected. The number of
correctable single-bit errors occur on
reading these memory is aggregated,
When the aggregate count exceeds
threshold (2 in 2 days), This ios msg is
reported. The shelf-mgr reloads the fabric
card.

[chars]

The fabric driver encountered the

annunciated error. Sysmgr will reload the
node up to a fixed number of times the
error is encountered, to recover. After a
certain number of node reloads, the shelf
manager will permanently shutdown the
node.

[chars]

The fabric driver encountered the

annunciated error. Sysmgr will reload the
node up to a fixed number of times the
error is encountered, to recover. After a
certain number of node reloads, the shelf
manager will permanently shutdown the
node.

[chars]

The fabric driver encountered the

annunciated error. Sysmgr will reload the
node up to a fixed number of times the
error is encountered, to recover. After a
certain number of node reloads, the shelf
manager will permanently shutdown the
node.

[chars]

The fabric driver encountered the

annunciated error. Sysmgr will reload the
node up to a fixed number of times the
error is encountered, to recover. After a
certain number of node reloads, the shelf
manager will permanently shutdown the
node.

Fabric driver cannot initialize the FIT library.

Fabric driver failed to initialize with FIT: err User will not be able to induce errors via
code([hex])
FIT tool.

Fabric driver cannot initialize the FIT library.

Fabric driver failed to initialize with FIT: err User will not be able to induce errors via
code([hex])
FIT tool.

Fabric driver (sapire) seen error during

Fabric:sapire access filter list doesn't
GASPP init access. This issue is related to
match. sapir_ext_reg_info_table[[dec]] has GASPP infra / Debugging infra. It wont
[chars]. Expected [chars]
affect normal working of the device.

The Fabric driver encountered an error

beyond the threshold times on the
annunciated Fabric Switching Element link
Link [chars] Shutdown permanently due to and the link is shutdown permenently by
[chars] .
the driver .

The Fabric driver encountered an error

beyond the threshold times on the
annunciated Fabric Switching Element link
Link [chars] Shutdown permanently due to and the link is shutdown permenently by
[chars] .
the driver .
sfe[[dec]]: Failed to Drain Queue
Associated To Destination ([dec]) from
[chars] for LM[dec]=[[hex]].

Unable to drain all the cells from a given

queue. This may cause barrier timeouts
once the queue is re-enabled. Hard
resetting Asic'

sfe[[dec]]: Failed to Drain Queue

Associated To Destination ([dec]) from
[chars] for LM[dec]=[[hex]].

Unable to drain all the cells from a given

queue. This may cause barrier timeouts
once the queue is re-enabled. Hard
resetting Asic'

Fabric driver failed to initialize with RCC

HW init library in RLDRAM init sequence
[dec]: err code([hex])

Fabric driver cannot initialize with the RCC

HW init library. Possible fabric multicast
feature may not function correctly.

Fabric driver failed to initialize with RCC

HW init library in RLDRAM init sequence
[dec]: err code([hex])

Fabric driver cannot initialize with the RCC

HW init library. Possible fabric multicast
feature may not function correctly.

Fabric driver failed to initialize the RCC

memory controller library: err code([hex])

Fabric driver cannot initialize the RCC

memory controller library. The node may
be not be able to initialized properly.

Fabric driver failed to initialize the RCC

memory controller library: err code([hex])

Fabric driver cannot initialize the RCC

memory controller library. The node may
be not be able to initialized properly.

[chars]

Fabric driver (sapire) seen error during

trace file init. This could be due to ltrace
infra issue.

[chars]

This is an indication that alerts are being

received from LTC2978 at a rate exceeding
15 per second causing the dampening to
be triggered. Interrupt is disabled for
30seconds after which it will be re-enabled.

[chars]

This is an indication that alerts are being

received from LTC2978 at a rate exceeding
15 per second causing the dampening to
be triggered. Interrupt is disabled for
30seconds after which it will be re-enabled.

Fabric driver failed to initialize the ltrace rc = [chars]

The Fabric driver could not open/initialize

the ltrace buffer. The Fabric driver and the
system should stll function as normal, with
the exception that ltrace will not be
available for sfe_drvr process.

Fabric driver failed to initialize the ltrace rc = [chars]

The Fabric driver could not open/initialize

the ltrace buffer. The Fabric driver and the
system should stll function as normal, with
the exception that ltrace will not be
available for sfe_drvr process.

Fabric driver failed to initialize the ltrace rc = [chars]

The Fabric driver could not open/initialize

the ltrace buffer. The Fabric driver and the
system should stll function as normal, with
the exception that ltrace will not be
available for sfe_drvr process.

Fabric: GASPP driver init failure. Error:

[chars]

Failed to initilise fabric CDR Driver for

gaspp infra. It won't affect normal working
of CRD driver.

RCC BIST of init sequence [dec] on device

[dec] running for [dec] seconds; ([hex])

Fabric drivers health is contingent of the

RCC library's initialization. Driver will poll to
verify the status of the RCC hw init.

RCC BIST of init sequence [dec] on device

[dec] running for [dec] seconds; ([hex])

Fabric drivers health is contingent of the

RCC library's initialization. Driver will poll to
verify the status of the RCC hw init.

[chars].

The fabric driver verifies the hardware

interfaces between the various
components on the fabric board. This is
done on cold start (POST) and periodically
there after. This message is annunciated
when any of the tests fail. Failure of test
doesn't indicate the card is unusable. It
may be a message suggesting an upgrade
for the board.

[chars].

The fabric driver verifies the hardware

interfaces between the various
components on the fabric board. This is
done on cold start (POST) and periodically
there after. This message is annunciated
when any of the tests fail. Failure of test
doesn't indicate the card is unusable. It
may be a message suggesting an upgrade
for the board.

FPD load operation is completed & fabric

ASICs will be reset & recovered.

This message posts a notice to indicate

that the FPD load operation is completed
and a reset of the card is required to come
up with the new PLD image.

FPD load operation is completed & fabric

ASICs will be reset & recovered.

This message posts a notice to indicate

that the FPD load operation is completed
and a reset of the card is required to come
up with the new PLD image.

Fabric ASICs being halted for FPD

operation.

Field upgrade of the fabric PLD while the

fabric card is in the chassis. Due to a bug in
the superstar ASIC, field upgrade of the
PLD cannot be done while the card is in
service and fabric plane is UP. It is required
to halt the ASICs on the board and isolate
the plane while the PLD image is being
loaded via the JTAG interface. This message
posts a notice to indicate that the devices
will be halted.

Fabric ASICs being halted for FPD

operation.

Field upgrade of the fabric PLD while the

fabric card is in the chassis. Due to a bug in
the Sapir ASIC, field upgrade of the PLD
cannot be done while the card is in service
and fabric plane is UP. It is required to halt
the ASICs on the board and isolate the
plane while the PLD image is being loaded
via the JTAG interface. This message posts
a notice to indicate that the devices will be
halted.

Aborted FGID mcast write to [hex] as

[chars] in PON reset state.

Aborted an FGID write update because the

ASIC is in the reset state. This can happen
when an FGID update request is in flight
when the ASIC goes through a PON reset
operation as a part of an error recovery.
During PON reset operation, the FGID
memory refresh logic is not operational and
hence the write operation is not carried
through. After a PON reset recovery, the
connection with the FGID server is
reestablished and a full FGID download is
done again. Note, that this is expected only
for PON reset recovery and not hard reset.

Aborted FGID mcast write to [hex] as

[chars] in PON reset state.

Aborted an FGID write update because the

ASIC is in the reset state. This can happen
when an FGID update request is in flight
when the ASIC goes through a PON reset
operation as a part of an error recovery.
During PON reset operation, the FGID
memory refresh logic is not operational and
hence the write operation is not carried
through. After a PON reset recovery, the
connection with the FGID server is
reestablished and a full FGID download is
done again. Note, that this is expected only
for PON reset recovery and not hard reset.

Freeze state of ASIC [chars] before asic

scan.

Freeze state of the ASIC before initiating

ASIC scan.

Freeze state of ASIC [chars] before asic

scan.

Freeze state of the ASIC before initiating

ASIC scan.

[chars] halted using CPLD halt assert

signal.

The specified device is halted using the

CPLD register.

[chars] halted using FPGA halt assert

signal.

The specified device is halted using the

FPGA register.

Notify FSDB that [chars] is OPER_UP.

Notify FSDB that the specified ASIC is

operationally UP. This indicates that the
fabric ASIC is initialized and FGID download
is completed. This is expected during
normal operation. On a driver restart, this
message will be annunciated when the
FGID download done message is received.

Fabric ASICs initialized

This indicates Fabric ASICs are initialized

and is expected during normal operation.

Notify FSDB that [chars] is OPER_UP.

Notify FSDB that the specified ASIC is

operationally UP. This indicates that the
fabric ASIC is initialized and FGID download
is completed. This is expected during
normal operation. On a driver restart, this
message will be annunciated when the
FGID download done message is received.

Power-On reset ASIC [chars] to recover

after asic scan.

Recover identified ASIC with a power on

reset following ASIC scan.

Power-On reset ASIC [chars] to recover

after asic scan.

Recover identified ASIC with a power on

reset following ASIC scan.

ASIC: [chars] - read register access [hex]

failed

This indicates a failed access to the ASIC.

ASIC: [chars] - read register access [hex]

failed

This indicates a failed access to the ASIC.

This message is seen when fabric ASIC

require to be reset during a driver restart. \
The output contains the a bit mask
depiction of all ASICs on the fabric board. \
'Ready' and 'Reset' masks identifies the
ASICs that are in ready or reset state. \
'Halt', 'Not ready' and 'Init fail' provide
ASIC bit mask: Ready:[hex] Reset:[hex]
additional information if the 'Reset' mask \
Halted:[hex] Not Ready:[hex] Init Fail: [hex] is non-zero.

This message is seen when fabric ASIC

require to be reset during a driver restart. \
The output contains the a bit mask
depiction of all ASICs on the fabric board. \
'Ready' and 'Reset' masks identifies the
ASICs that are in ready or reset state. \
'Halt', 'Not ready' and 'Init fail' provide
ASIC bit mask: Ready:[hex] Reset:[hex]
additional information if the 'Reset' mask \
Halted:[hex] Not Ready:[hex] Init Fail: [hex] is non-zero.

ASIC bit mask: Ready: [hex] Reset: [hex]

Pending interrupt: [hex] Ready bits: [hex].

This message is seen when fabric ASIC

require to be reset during a driver restart. \
The output contains the a bit mask
depiction of all ASICs on the fabric board. \
'Ready' and 'Reset' masks identifies the
ASICs that are in ready or reset state. \ If
an ASIC is in reset state, pending interrupt
captures additional information.

ASIC: [chars] - write value [hex] register

access [hex] failed

This indicates a failed access to the ASIC.

ASIC: [chars] - write value [hex] register

access [hex] failed

This indicates a failed access to the ASIC.

Await FGID download completion to notify

FSDB of ASIC initialization.

This indicates Fabric ASICs are initialized

pending the FGID download done
notification from FGID server. FSDB will be
notified about the ASIC initialization
complete state only after the ASICs are
initialized and the FGID download is
completed.

Await FGID download completion to notify

FSDB of ASIC initialization.

This indicates Fabric ASICs are initialized

pending the FGID download done
notification from FGID server. FSDB will be
notified about the ASIC initialization
complete state only after the ASICs are
initialized and the FGID download is
completed.

Barrier flow started on all ASICs

Barriers started flowing on all the

nodes/types.

Traceback on an address [hex] ([chars])

detected earlier to cause bus stall
interrupt.

Certain address accesses were causing bus

stall interrupts on the Sapir ASIC. Such
addresses are cached by the driver.
Subsequently, when these addresses are
accessed by the driver, this message is
logged to provide a traceback information
to help with debugging.

Traceback on an address [hex] detected

earlier to cause bus stall interrupt.

Certain address accesses were causing bus

stall interrupts on the superstar ASIC. Such
addresses are cached by the driver.
Subsequently, when these addresses are
accessed by the driver, this message is
logged to provide a traceback information
to help with debugging.

Reloading the card to recover after asic

scan.

Recover the card with reload following ASIC

scan.

Reloading the card to recover after asic

scan.
SEA ASIC driver loaded

Recover the card with reload following ASIC

scan.
Fabric driver loaded for the SEA asics.

Sometimes, when the register access of

the superstar ASIC fails, read of any of its
registers returns 0xdeaddead. Now if this
happens when CIH is processing an
interrupt, CIH would accidentally determine
the source of the interrupt as Rx Snoop
SRAM SBE interrupt. In reality, this
interrupt is not even enabled by the driver.
The Rx snoop SRAM SBE interrupt is
obtained if we traverse the interrupt tree of
the superstar ASIC as given below: - Bit 0
of the top level CPU hierarchy interrupt is
Rx block. - Bit 0 of the Rx block hierarchy is
Rx block leaf interrupts. - Bit 0 of the Rx
Access to [chars] timed out. Device will be block leaf interrupts in Rx Snoop SRAM
PON reset to recover.
SBE.

Sometimes, when the register access of

the Sapir ASIC fails, read of any of its
registers returns 0xdeaddead. Now if this
happens when CIH is processing an
interrupt, CIH would accidentally determine
the source of the interrupt as Rx Snoop
SRAM SBE interrupt. In reality, this
interrupt is not even enabled by the driver.
The Rx snoop SRAM SBE interrupt is
obtained if we traverse the interrupt tree of
the Sapir ASIC as given below: - Bit 0 of the
top level CPU hierarchy interrupt is Rx
block. - Bit 0 of the Rx block hierarchy is Rx
Access to [chars] timed out. Device will be block leaf interrupts. - Bit 0 of the Rx block
PON reset to recover.
leaf interrupts in Rx Snoop SRAM SBE.

FIT forcing hard reset of device id: [dec]

This indicates that the FIT tool has

forced/induced a hard reset.

FIT forcing hard reset of device id: [dec]

This indicates that the FIT tool has

forced/induced a hard reset.

FIT forcing power on reset of device id:

[dec]

This indicates that the FIT tool has

forced/induced a power on reset.

FIT forcing power on reset of device id:

[dec]

This indicates that the FIT tool has

forced/induced a power on reset.

[chars].

This message is seen when any of the

previously reported health monitoring error
condition is cleared.

Plane config is missing or inconsistent.

Missing admin plane configuration for this

module.

Plane config is missing or inconsistent.

Missing admin plane configuration for this

module.

Plane config is missing or inconsistent. Asic

status(oper_up/avl_map) = [hex]/[hex]. Cfg
availability (topo/oob/bpe)= [hex]/[hex]/
Missing admin plane configuration for this
[hex]. cfg_retrvd=[hex]
module.
In interrupt detecting OIR of the fabric card
was received. Driver will exit. If the
message is seen at steady state with no
OIR action then support should be
requested. In case the card was physically
OIR interrupt detected[Debug info1 =
OIRed this message may be seen and is not
[hex],Debug info2 = [hex]]. sfe_drvr exited an issue.

A node reload request to envmon is

pending. If the node is not reloaded by
A request to bring down this node is
envmon platform fault manager will be
pending. Node will reload in less than [dec] requested to bring the node down in in the
seconds
time specified

[chars]: Error in Back pressure

configuration, BP Groups : [dec], [dec],
[dec]

The Fabric driver encountered an error in

back pressure configuration. This indicates
BP configuration received from the fabric
control software is incorrect. If this
condition prevails, it could impact data
traffic when fabric gets congested.

[chars]: Error in Back pressure

configuration, BP Groups : [dec], [dec],
[dec]

The Fabric driver encountered an error in

back pressure configuration. This indicates
BP configuration received from the fabric
control software is incorrect. If this
condition prevails, it could impact data
traffic when fabric gets congested.

[chars]: Error in Back pressure

configuration, BP Groups : [dec], [dec],
[dec]

The Fabric driver encountered an error in

back pressure configuration. This indicates
BP configuration received from the fabric
control software is incorrect. If this
condition prevails, it could impact data
traffic when fabric gets congested.

Fabric driver failed to register with the

debug; rc = [chars]

The Fabric driver was unable to register

with the debug. The System Manager
process (sysmgr) will automatically
respawn this (sfe_drvr) process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Fabric driver failed to register with the

debug; rc = [chars]

The Fabric driver was unable to register

with the debug. The System Manager
process (sysmgr) will automatically
respawn this (sfe_drvr) process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Fabric driver failed to register with the

debug; rc = [chars]

The Fabric driver was unable to register

with the debug. The System Manager
process (sysmgr) will automatically
respawn this (sfe_drvr) process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

[chars]

The Fabric driver encountered the

annunciated internal SW error. The System
Manager process (sysmgr) will
automatically respawn this (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

[chars]

The Fabric driver encountered the

annunciated internal SW error. The System
Manager process (sysmgr) will
automatically respawn this (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

[chars]

The Fabric driver encountered the

annunciated internal SW error. The System
Manager process (sysmgr) will
automatically respawn this (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

Topology mismatch for [chars]

The upstream information received from

idle cells on this link does not match with
FSDB information.

The upstream information received from

idle cells on this link does not match with
FSDB information. The topology mismatch
information is a bitmap of links seeing
errors. Links 0-31 is in word 0, links 32-63
A config error has occurred that may cause in word 1, links 64-95 in word 2 and links
cell drop on [chars]. [chars]
96-127 in word 3.

[chars]

The fabric driver encountered the

annunciated error. If the displayed error is
one of the following 'Multicast High Priority
Acknowledge Barrier Timeout' 'Multicast
Low Priority Acknowledge Barrier Timeout'
'Unicast High Priority Acknowledge Barrier
Timeout' 'Unicast Low Priority Acknowledge
Barrier Timeout 'Multicast High Priority
Request Barrier Timeout' 'Multicast Low
Priority Request Barrier Timeout' 'Unicast
High Priority Request Barrier Timeout'
'Unicasts Low Priority Request Barrier
Timeout' The Fabric driver and the System
should still continue to function as
normal.The affected link will be identified
and taken offline momentarily. These errors
are expected during OIR operations. If the
error happens during steady state,
investigation should be done for other
unexpected oir events. If there is no other
unexpected oir or anything, and the issue
happened 2 in 2 days, then some effort
should be done to identify the source link.

[chars]

The fabric driver encountered the

annunciated error. The Fabric driver and
the System should still continue to function
as normal.

[chars]

The fabric driver encountered the

annunciated error. The Fabric driver and
the System should still continue to function
as normal.

Fabric Link: [chars] - Shutdown: [chars]

The Fabric driver encountered an error on

the annunciated Fabric Switching Element
link and the link is brought down.

Fabric Link: [chars] - Shutdown: [chars]

The Fabric driver encountered an error on

the annunciated Fabric Switching Element
link and the link is brought down.

Fabric Link: [chars] - Shutdown: [chars]

The Fabric driver encountered an error on

the annunciated Fabric Switching Element
link and the link is brought down.

[chars]

MINIQ Version 2 chassis type do not

support sea/superstar based fabric cards.
MINIQ Version 1 chassis type do not
support superstar based fabric cards. This
is because of unsupported backplane in
these chassis.

Voltage validation failed, card will be

shutdown.

Fabric card is not powered up yet. Shut it

down.

Failed to shutdown by shelf-mgr. error

code([hex])

Fabric driver encountered a system error in

bringing down the node through shelfmgr.
The card and its fabric ASICs should have
been isolated from the system before the
shutdown attempt.

EES announcement failed, error: [chars]

EES domain enabling failed. This will

prevent ucd/mcd messages to be
exchanged between the applications and
driver.

Invalid parameter passed to DLL API.

An invalid parameter is passed to the DLL

API. Check the implementation in the
process calling this API.

[chars]

API is not supported for specified reason.

Check the implementation in the process
calling this API.

Fabric driver encountered the annunciated

error during the driver initialization. The
System Manager process (sysmgr) will
automatically respawn the (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
Initialization of fabric driver failed: [chars] ; node reloads, the shelf manager will
exiting...
permanently shutdown the node.

EES registration failed, rc = [chars]

EES domain enabling failed. This will

prevent ucd/mcd messages to be
exchanged between the applications and
driver.

[chars] failed for [dec], error: [chars]

The driver failed to enable/disable interprocess communication with fgid_server.

This will prevent ucd/mcd messages to be
exchanged between fgid_server and driver.

The Fabric driver was unable to create an

event manager for processing messages
and hence failed to initialize. The System
Manager process (sysmgr) will
automatically respawn this (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
Failed to create event manager for '[chars]' permanently shutdown the node.

This is an error message and is seen in the

abnormal condition when the fgid
consumer thread fails to start successfully.
Fgid consumer thread will successfully start
if all the asics are operationally up. If the
asics do not report oper-up within the
timeout period fgid_consumer thread
cannot be started. As a consequence SFE
Driver is restarted. avl_map is a bitmap
representing all the asics that are required
to be operationally up to successfully start
the fgid consumer thread. The oper_up
bitmap indicates the asics that are
Process sfe_drvr will be restarted. Asic
currently operationally up. The
status(oper_up/avl_map) = [hex]/[hex]. Cfg topo/oob/bpe information indicates which
availability (topo/oob/bpe)= [hex]/[hex]/
of the asics have received the specific
[hex].
(topo/oob/bpe) configuration.

Initial FGID Download failed (after total

delay of [dec] secs)

The message is seen when initial FGID

download from the FGID server to SFE
driver does not get completed even after
multiple attempts to reset the EES
connection. This means the communication
between SFE driver and FGID driver is
broken and indicates a EES transport issue.

Error Allocating <[dec]> bytes of memory

Failed to allocate memory from Heap. This

can happen during periods of intense
memory resource usage or due to a
memory leak - though these are extremely
rare occurances. This message implies
some message(s) between FSDB and SFE
driver was not processed and so they might
be out of sync.

[chars] signal received when driver is not

ready. [chars]

A signal was received when the driver is

not yet ready. For SIGBUS card will reload.
For others the signal will be raised to the
OS

Failed to create Event Connection

Manager : [chars]

The Fabric driver was unable to create an

event connection manager for EDM. Fabric
driver and the System should continue to
function as normal, with the exception that
the 'show' commands for Fabric driver will
not be available.

Failed to register with ECM to receive

notifications : [chars]

The Fabric driver was unable register with

ECM to receive notifications when the
connection to Sysdb goes down/up/closed.
Fabric driver and the System should
continue to function as normal, with the
exception that the 'show' commands for
Fabric driver will not be available.

Initial FGID Download did not complete

within timeout period ([dec] secs).
Retrying..

The message is seen when initial FGID

download from the FGID server to SFE
driver does not get completed. Generally
this indicates a transient EES transport
issue. The SFE driver will try to recover
from this error by resetting the EES
connection to FGID server.

Fabric driver failed to initialize the ltrace rc = [chars]

The Fabric driver could not open/initialize

the ltrace buffer. The Fabric driver and the
system should still function as normal, with
the exception that ltrace will not be
available for sfe_drvr process.

This message is seen when fabric ASICS

Asics being reset, Respawn Count = [dec] are being reset. The status reported here
Checkpoint status = [dec] Interrupt Status provide information about the reason for
= [hex] ASICs are ready = [dec]
the reset.
[chars]

This is to give infomation regarding fabric

module type.

Discovered [chars] fabric

This is to give infomation regarding fabric

card type.

Cannot find board revision

The message is seen when we fail to read

the EEPROM for board revison. Check
platform libraries & i2c bus connectivity.

FDI request to reset all the ASICs on the

fabric board.

Process a request received from FSDB to

reset all the ASICs on the fabric card.

[chars]

The Fabric driver was unable to register

Fabric driver bags. The Fabric driver and
the System should continue to function as
normal, with the exception that the 'show'
commands for Fabric driver will not be
available.

Fabric driver failed to initialize the debug;

rc = [chars]

The Fabric driver was unable to initialize

debug. The System Manager process
(sysmgr) will automatically respawn this
(sfe_drvr) process, up to a fixed number of
times the error is encountered, to recover.
If the problem continues, sysmgr will
trigger node reload. After a certain number
of node reloads, the shelf manager will
permanently shutdown the node.

Fabric driver failed to register with the

debug; error: [chars]

The Fabric driver was unable to register

with the debug. The System Manager
process (sysmgr) will automatically
respawn this (sfe_drvr) process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

[chars]

The Fabric driver encountered the

annunciated internal SW error. The System
Manager process (sysmgr) will
automatically respawn this (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

[chars]

PCDS support will not be available due to

the specified reason.

[chars]

The Fabric driver was unable to become an

external data manager (EDM) despite
having a connection to SysDB. The
operation will be retried. The Fabric driver
and the System should continue to function
as normal, with the exception that the
'show' commands for Fabric driver will not
be available.

Fabricq received an invalid FBP config.

[chars]

The Fabricq received an invalid Fabric Back

Pressure configuration from fsdb.

Fabricq manager encountered a fatal error

and is not able recover from the error. A
Initialization Error: [chars] Reason: [chars]. reason text will be supplied call support
Exiting.
with this text.

Error Allocating <[dec]> bytes of memory

Fabricq encountered a memory allocation

error. Memory allocation failures will
happen if the the router runs out of
memory or memory leak in this process or
other processes.

Fabricq aborted the iMDR upgrade.

Error=[dec], Reason: [chars]

The FabricQ process aborted the iMDR

upgrade most likely due to a prior process
crash.

Checkpoint Initialization failed. Reason:

[chars]

Fabricq Checkpoint Init error

Unexpected event received during ISSU

Upgrade [chars]

The Fabricq Mgr received an event from the

iMDR Mgr that it did not register for.

Initialization Warning: [chars] Reason:

[chars].

Fabricq manager encountered an error but

was able recover or continue execution.
This message is just for informational.

Bag register failed for rules. Reason:

[chars]

EDM Bags are used to share information

between components using sysdb. This
Error indicates that bag registration failed.

Client [chars] failed. Reason: [chars]

Fabricq Manager client

Registration/Unregistration error

Dll Initialization for [chars] failed. Reason:

[chars]

Fabricq driver tried to register for a dll but

it encountered an error. The driver might
lose some of its functionality.

Event Manager create failed for [chars].

Reason: [chars]

Fabricq Event Manager create error

Event Manager notify failed for [chars].

Reason: [chars]

Fabricq Event Manager notify error

LWM Event Manager event block failed.

Reason: [chars]

Fabricq Event Manager event block error

An error occurred during LWM message

reply. Reason: [chars]

Fabricq LWM reply error

Sysdb Register EDM failed. Reason: [chars] Fabricq Sysdb Register EDM error

[chars]

Fabricq server iMDR debug/info messages.

These are Unit-Test log messages and
presently they are commented. So, only
Dev team can enabled this message and
use it. Hence more info on this log is
unncessary.

Fabricq [dec]: [chars]

Fabricq encountered an ASIC error which

software cannot resolve

If the Asic is in Halt state, the software will

reset the power to recover. Otherwise, the
Fabricq Asic [dec] encountered a hardware fabricq has encountered an ASIC error
error. details: [chars]
which software cannot resolve.

Fabric Asic [dec] encountered generic

error(s). Details: [chars]

Fabricq encountered an unexpected error in

asic. Software will take appropriate action
to log and fix the error.

Fabric Asic [dec] encountered generic

error(s). Details: [chars]

Fabricq encountered an unexpected error in

asic. Software will take appropriate action
to log and fix the error. The ASIC may reset
if the number of errors exceeds the
threshold limit and the driver is able to
recover from this error.

Fabricq [dec]: [chars] : [chars]

Fabricq encountered an internal hardware

dll api error. These type of errors are
usually generated from CAI APIs. Below
gives an example of where these type of
error could be coming from: 1) iLite link
errors 2) cci device discovery errors 3)
gaspp driver init 4) cdma api errors 5)
udma api errors 6) bist api errors

Fabricq [dec]: [chars] : [chars]

Fabricq encountered an internal hardware

dll api error. These type of errors are
usually generated from CAI APIs. Below
gives an example of where these type of
error could be coming from: 1) iLite link
errors 2) cci device discovery errors 3)
gaspp driver init 4) cdma api errors 5)
udma api errors 6) bist api errors

Fabricq [dec]: [chars] : [chars]

Fabricq encountered an internal software

dll api error Following are some of the
reasons for this internal error: 1) mutext
init 2) thread creatation 3) cai API failure

Fabricq [dec]: [chars] : [chars]

Fabricq encountered an internal software

dll api error Following are some of the
reasons for this internal error: 1) mutext
init 2) thread creatation 3) cai API failure

Fabric link [dec] on ASIC [dec] is brought

down due to too many [chars] errors

A fabric link was brought down due to too

many errors.

Fabric link [dec] on ASIC [dec] is brought

down due to too many [chars] errors

A fabric link was brought down due to too

many errors.

Fabricq [dec]: [chars]

Fabricq ASIC encountered a read or write

access error or its Host Processor Interface
block has gone down and come back up.
The access error is classified into two
classes - software or hardware. Hardware
access error refers to an error at the PCI
link used to connect the ASIC to the host
processor. Software access error refers to
the error, caused by a un-discovered
software bug, which makes software to
perform un-supported access to an ASIC
location, like writing to a read-only
location.

Fabricq [dec]: [chars]

Fabricq ASIC encountered a read or write

access error or its Host Processor Interface
block has gone down and come back up.
The access error is classified into two
classes - software or hardware. Hardware
access error refers to an error at the PCI
link used to connect the ASIC to the host
processor. Software access error refers to
the error, caused by a un-discovered
software bug, which makes software to
perform un-supported access to an ASIC
location, like writing to a read-only
location.

[chars], Error: [chars]

i2c read failure. Its not under fabric control.

Please check I2C trace/logs/component.

Assert error in Fabricq ASIC [dec]. FCRAM

Channel [dec].

Fabricq ASIC encountered a FCRAM

Channel error

fabricq asic [dec]: encountered [chars]

during init: [chars]

Fabricq Asic driver encountered a fatal

error and is not able recover from the error.
A reason text will be supplied call support
with this text.

fabricq asic [dec]: encountered [chars]

during init. err: [chars]

Fabricq Asic driver encountered an error

and is not able to recover from the error.

Fabricq ASIC encountered error during

[chars] BIST

Built-In Self-Test failed for Fabricq ASIC.

Fabric(inbar-crab) debugging initialization

Fabric(inbar-crab) debug initialization failed failure. This indicates PI debug infra failure.
for event [chars]. Reason: [chars]
May not be related to PD.

Fabric(crab) debug initialization for event:

[chars] failed. Reason: [chars]

Fabric - Crab debugging initialization

failure. Its debug infra init failure. May not
be related to PD.

Fabric(inbar-crab) debug registration

failure. Reason: [chars]

Crab debugging registration failure. This

indicates PI debug infra failure. May not be
related to PD.

Fabric(crab) debug registation failed,

reason: [chars]

Crab debugging registration failure. Its

debug infra init failure. May not be related
to PD.

[chars]

A hardware error occurred while a DMA

transfer initiated by the FQM process was
taking place. This means certain data
requested by the FQM process will not be
available.

[chars]

A hardware error occurred while a DMA

transfer initiated by the FQM process was
taking place. This means certain data
requested by the FQM process will not be
available.

Fabricq manager encountered an error and

is not able recover from the error. A reason
Initialization Error: [chars] Reason: [chars]. text will be supplied call support with this
Exiting.
text.

[chars]

Fabricq asic dll encountered an internal

software API error where a NULL input
parameter is used.

[chars]

Fabricq asic dll encountered an internal

software API error where a NULL input
parameter is used.

The Fabricq ASIC is configured to expect

fabric backpressure informtion for a
particular set of groups on a small set of
links. This error indicates that incoming
Fabricq ASIC received incorrect FBP bitmap. backpressure information doesn't match
[chars]
the expected config.

The Fabricq ASIC is configured to expect

fabric backpressure informtion for a
particular set of groups on a small set of
links. This error indicates that incoming
Fabricq ASIC received incorrect FBP bitmap. backpressure information doesn't match
[chars]
the expected config.

The Fabricq ASIC is configured to expect

fabric backpressure informtion for a
particular set of groups on a small set of
links. This error indicates that incoming
Fabricq ASIC received incorrect FBP bitmap. backpressure information doesn't match
[chars]
the expected config.

Major error in PCL of fabricq asic [dec]:

[chars] data.

Sponge encountered a PCL cell count

mistmatch error. The cell count from the
cell header mismatches with the cells that
arrived for the same packet.

Major internal error in PCL of fabricq asic

[dec]: [chars].

Sponge encountered a PCL internal error.

The asic will be reset to recover from this
error.

Minor error in PCL of fabricq asic [dec].

[chars]

Sponge encountered a PCL Packet error.

This error could be due to unicast lost
packet.

Major error in PCL of fabricq asic [dec]:

[chars]

Sponge encountered a PCL extra cell error,

and received more cells for a packet than
were expected.

Reseting Fabricq ASIC Device [dec].

Reason: [chars]

The fabricq ASIC is reset due to the reason

displayed in the message. Most often the
situation recovers after ASIC reset. If the
resets persists, contact technical support
with the following information.

Fabricq Asic [dec] detected multibit

error(s). Details: [chars]

Fabricq Asic encountered a memory

uncorrectable error The multi-bit errors can
happen in one of many blocks of the
fabricq ASIC. One of them is the Fabric
Interface (FI). If these error messages are
generated for short intervals for FI links
when a fabric card is disabled / reloaded /
OIR'ed, then they are harmless.

Fabricq Asic [dec] detected parity error(s).

Details: [chars]

Fabricq Asic encountered a parity error

Fabricq ASIC [dec] encountered a CpuCtrl

[chars] error

Fabricq ASIC encountered a CpuCtrl

CRC/Sync error

Link Alarm on Fabricq ASIC [dec] link [dec] Fabricq ASIC encountered a link alarm

Fabric link [dec] on ASIC [dec] may be

brought down due to too many errors

A fabric link was brought down due to too

many UCE or parity errors.

Fabric topology inconsistency detected for

ASIC [unsigned int] link [unsigned int]
An inconsistency between the expected
(observed topology information: [hex],
and observed topologies of the fabric was
expected: [hex])
detected.

[chars]

Fabricq driver monitors the ASIC every 5

seconds to look for any problems. If an
error is reported momentarily, it could be a
false positive seen during a transient state,
or during oversubscription. In case, the
error is seen repeatedly, please contact
TAC support.

Major error in Fabricq ASIC [dec]. MI [chars] Fabricq ASIC encountered a MI

Wedged
Unicast/Multicast Wedge error

Major error in PCL of Fabricq asic [dec]:

[chars] . [hex] spo_pcl_mem_ppbr [hex]
[hex]%08x[hex]%08x[hex]%08x[hex]

Fabricq encountered a PCL Packet

Sequence Wrap error

An error occured while the Fabricq driver

was trying to create queues for an
Error during Resource Programming [chars] interface. This may leave one or more
[unsigned int] Reason: [chars]
interfaces out of operation.
Major error in Fabricq ASIC [dec]. MI [chars] Fabricq ASIC encountered a MI
Backpressure decode error
Unicast/Multicast BP Decode error

Minor error in Fabricq ASIC [dec]. [chars]

End of Packet error

Fabricq ASIC encountered a

Unicast/Multicast Unexpected/Missing End
Of Packet error

Fabric Asic [dec] encountered generic

error(s). Details: [chars]

Fabricq encountered an interrupt that has

exceeded its threshold value. Software
takes appropriate action to log and fix the
error.

Fabricq Asic [dec] encountered [chars] Out Fabricq encountered an out of resources
Of Resources error.
error.

Fabricq ASIC [dec] : [chars]

The annunciated error occurred relating to

asic deferral.

Fabricq Asic [dec] detected single bit

error(s). Details: [chars]

Fabricq Asic encountered a memory

correctable error

Minor error: Cluster: [dec] in Fabricq ASIC

[dec] has SPI FBP [chars] error

The Fabricq asic encounted a fabric

backpressure error. These sort of errors are
to be expected during bootup or during OIR
events, and are harmless for the vast
majority of the time. The only time they
would signify a serious error is if they recur
for long periods.

Minor error in PCL of Fabricq asic [dec].

Urgent Context ([chars])

Fabricq encountered a PCL Urgent Context

error

An error occurred while a DMA transfer

initiated by the FQM process was taking
Error during DMA transfer: Source Addr
place. This means certain data requested
[hex], Dest Addr [pointer]. Reason: [chars] by the FQM process will not be available.

EES Announcement Failed, ERR : [chars]

This process encountered an internal

software error. [chars] provide detailed
information about this error Process will
restart to recover from this error.

An unexpected error occurred while

Unable to send message to the peer, ERR : sending an message. Process will restart to
[chars]
recover from this error.

Structure with Missing or Corrupted TLV.

Previous TLV: [chars]. Current: [chars]

FSDB/Driver encountered a FDI message

containing structure(s) which do not have a
TLV header, or the message is too short to
contain the structure(s) specified in the TLV
header. This means that the TLV encoding
code is missing and needs to be added to
the appropriate structure. After an
occurence of such error, it is likely that
FSDB and Driver have gone out of sync.

Structure received with Invalid TLV.

Previous TLV: [chars]. Current: [chars]

FSDB/Driver received a FDI message

containing structure(s) with invalid TLV
type. This means that the TLV encoding
code is missing some structure entry. After
an occurence of such error, it is likely that
FSDB and Driver have gone out of sync.

Double free of FGID [dec]

A software error occurred, when the PA

attempted to double free the FGID

Number of unknown errors from FGID-DB

([dec]) has exceeded maximum

A software error occurred, when the PA(Port

Arbitrator) attempted to allocate FGID's
from the FGID aggregator.

Attempt to free unallocated FGID [dec]

A software error occurred, when the PA

attempted to free unknown FGID

Unknown error from FGID-DB, [chars] FGID A software error occurred, when the PA(Port
[dec] [nodes:[dec]](location[0]:
Arbitrator) attempted to Allocate, free or
[dec],location[1]:[dec]) error_string: [chars] join FGID from the FGID Aggregator.

fgid_aggregator unable to initialize dbg ;

err = [chars]

The FGID Aggregator was unable to

initialize debug. The System Manager
process (sysmgr) will automatically
respawn this process, up to a fixed number
of times the error is encountered, to
recover. If the problem continues, sysmgr
will trigger node reload. After a certain
number of node reloads, the shelf manager
will permanently shutdown the node.

FGID Aggregator failed to create [chars]

evm ; err = [chars]

The FGID aggregator was unable to create

an event manager for processing messages
and hence failed to initialize. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

The FGID Aggregator was unable to attach

the indicated event handler to the event
manager. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
FGID Aggregator failed to attach [chars] to node reloads, the shelf manager will
evm ; err = [chars]
permanently shutdown the node.

FGID aggregator encountered following

GSP error : [chars]: err = [chars]

The FGID Aggregator was unable to

create/join GSP group. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

The FGID Aggregator encountered the

annunciated SW error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
FGID aggregator encountered following SW shelf manager will permanently shutdown
error : [chars];err = [chars]
the node.

FGID Aggregator unable to allocate [dec]

bytes

The FGID Aggregator was unable to

allocate memory. The System Manager
process (sysmgr) will automatically
respawn this process, up to a fixed number
of times the error is encountered, to
recover. If the problem continues, sysmgr
will trigger node reload. After a certain
number of node reloads, the shelf manager
will permanently shutdown the node.

FGID aggregator encountered following

sysmgr error : [chars]; err = [chars]

The FGID Aggregator encountered the

annunciated sysmgr error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

FGID Aggregator failed to initialize the

ltrace file [chars] : err = [chars]

The FGID Aggregator Could not open the

annunciated ltrace buffer. The FGID
component and the system should still
function as normal, with the exception that
ltrace will not be available for
fgid_aggregator process.

The FGID allocator was unable to create an

event manager for processing messages
and hence failed to initialize. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
FGID Allocator failed to create [chars] evm; shelf manager will permanently shutdown
err = [chars]
the node.

FGID allocator encountered following GSP

error : [chars]: err = [chars]

The FGID Allocator encountered the

annunciated GSP error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

FGID allocator encountered following SW

error : [chars] ; err = [chars]

The FGID Allocator encountered the

annunciated internal SW error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

The FGID Allocator was unable to allocate

memory. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
FGID Allocator failed to allocate [dec] bytes permanently shutdown the node.

FGID allocator encountered following

sysmgr error : [chars]; err = [chars]

The FGID Allocator encountered the

annunciated sysmgr error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

The FGID allocator was unable to register

FGID bags. The FGID component and the
System should continue to function as
normal, with the exception that the 'show'
FGID allocator failed to register FGID bags; commands for FGID allocator will not be
err = [chars]
available.

FGID Allocator failed to initialize the

checkpoint library ; err = [chars]

The FGID Allocator was unable to initialize

the checkpoint library. The fgid_allocator
process may need restarting, if the errors
persist.

FGID Allocator failed to start to iterate

Checkpoint table [chars]; err = [chars]

The FGID Allocator was unable to start to

iterate checkpoint table. The fgid_allocator
process may need restarting, if the errors
persist.

FGID Allocator failed to register the

Checkpoint table [chars] ; err = [chars]

The FGID Allocator was unable to register

the checkpoint table. The fgid_allocator
process may need restarting, if the errors
persist.

The FGID Allocator failed to initialize

debug. The FGID component and the
System should still continue to function as
normal, with the exception that the debugs
FGID Allocator failed to initialize debug ; err will not be available for fgid_allocator
= [chars]
process.

FGID Allocator failed to initialize the ltrace

file [chars]; err = [chars]

The FGID Allocator could not open the

annunciated ltrace buffer. The FGID
component and the system should function
as normal, with the exception that ltrace
will not be available for fgid_aggregator
process.

The FGID-DB allocator unable to bind to

FGID Allocator failed to bind to Sysdb name sysdb name space. The fgid_allocator may
space [chars]; err = [chars]
need restarting if the errors persist.

FGID allocator failed to perform EDM

registration; err = [chars]

The FGID allocator was unable to become

an external data manager (EDM) despite
having a connection to SysDB. The
operation will be retried. The FGID
component and the System should
continue to function as normal, with the
exception that the 'show' commands for
FGID allocator will not be available.

[chars] ; rc = [chars]

The BCDL Consumer process has

encountered the annunciated BCDL error.
The System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

FGID BCDL Consumer failed to get

hardware board type: rc = [chars]

The FGID BCDL Consumer was unable to

get the board type.

The FGID BCDL Consumer Failed to

initialize debug; rc = [chars]

The FGID BCDL Consumer was unable to

initialize debug. The System Manager
process (sysmgr) will automatically
respawn this process, up to a fixed number
of times the error is encountered, to
recover. If the problem continues, sysmgr
will trigger node reload. After a certain
number of node reloads, the shelf manager
will permanently shutdown the node.

[chars] : [chars]

The FGID BCDL consumer encountered the

annunciated Event Manager Error. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

The FGID BCDL Consumer was unable to

register with the FDI client. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
Unable to perform FDI client registration; rc shelf manager will permanently shutdown
= [chars]
the node.

The FGID BCDL Consumer encountered an

error while notifying the SFE driver about
FGID download completion. This indicates a
FGID BCDL Consumer failed to notify SFE
problem with communication between
driver about FGID download complete; rc = SFE_DRVR and FGID BCDL consumer.
[chars]
Restart SFE driver manually.

FGID BCDL Consumer failed to set FGID

[chars] bitmap; rc = [chars]

The FGID BCDL Consumer encountered an

error while setting S2 or S3 bitmap. This
indicates a problem with the
communication between the SFE driver and
the FGID BCDL consumer. The FGID BCDL
consumer and/or SEA driver may need
restarting if the errors persist.

The FGID BCDL Consumer encountered an

error while retrieving the rack value from
nodeid. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
FGID BCDL Consumer failed to get the rack node reloads, the shelf manager will
value; rc = [chars]
permanently shutdown the node.

The FGID BCDL Consumer could not open

the annunciated ltrace buffer. The FGID
component and the system should function
as normal, with the exception that ltrace
FGID BCDL Consumer failed to initialize the will not be available for FGID BCDL
ltrace file [chars] : rc = [chars]
Consumer process.

FGID library failed to initialize the debug ;

err = [chars].

The FGID library failed to initialize debug.

The FGID component and the system
should still function as normal, with the
exception that the debugs will not be
available for FGID library.

FGID library failed to initialize the ltrace ;

err = [chars].

The FGID library failed to initialize ltrace.

The FGID component and the system
should still function as normal, with the
exception that the ltrace will not be
available for FGID library.

Rack num could not be determined, err =

[chars]

Rack num could not be determined

because platform_get_my_nodeid failed.

FGID server encountered following BCDL

error : [chars]; err = [chars]

The FGID Server encountered the

annunciated BCDL error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

The FGID Server encountered DSC error.

The System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
Failed to register for DSC notification; err = shelf manager will permanently shutdown
[chars]
the node.
FGID server encountered some issue with
EES. This can happen if FGID server fails to
FGID encountered following error with EES : register with EES or EES initialization or
[chars], err = [chars]
EES announcement fails.
FGID encountered an error with EES req_id This can happen when EES request id's are
= [dec], ddt_list_count = [dec],
wrapped or some other issue with request
ddt_uc_msgs_count = [dec]
id's.

FGID Server failed to create [chars] evm;

err: [chars]

The FGID Server was unable to create an

event manager for processing messages
and hence failed to initialize. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

FGID Server failed to attach [chars] evm;

err: [chars]

The FGID Server was unable to attach the

indicated event handler to the event
manager. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

FGID encountered following GSP error :

[chars]; err = [chars]

The FGID-DB server encountered the

annunciated GSP error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

FGID encountered following SW error :

[chars]; err = [chars]

The FGID Server encountered the

annunciated SW error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Invalid FGID ([dec]) at [chars]

Trying to add an out of range FGID to an

array.

Invalid card type = [hex] for node = [hex]

Fabric cards bitmap capacity cannot be

determined because
platform_node_get_card_type returned an
unrecognized card type.

The FGID Server was unable to allocate

memory. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
FGID Server unable to allocate [dec] bytes permanently shutdown the node.

FGID Server : Requested Server Id [chars]

is not an allowed server_id

Incorrect command line parameters were

passed to the FGID Server, and so it failed
to start.

FGID server encountered following SW

error : [chars]; err = [chars]

The FGID Server encountered the

annunciated SW error.

The FGID Server Could not open the

annunciated ltrace buffer. The FGID
component and the system should function
as normal, with the exception that ltrace
FGID Server failed to initiaize the ltrace file will not be available for fgid_server
[chars]; rc = [chars]
process.

FGID encountered following sysmgr error :

[chars] ; err = [chars]
The FGID-DB server failed in sysmgr API

Event Connection Manager (ECM) Error:

[chars] : [chars]

The FIA driver client library encountered

the annunciated error condition. There are
3 types of this failure. - ECM create failure:
In this case the FIA driver client library will
not be able to connect to the FIA driver. Register notification handler failure: In this
case the FIA driver client library will not
receive notification of ECM events. - Failure
to open a connection:

[chars] - [chars]

FIA driver encountered an Error in

operation.

[chars] - [chars] [dec]

FIA driver encountered an Error in

operation.

[chars] - [chars] [chars] [dec]

FIA driver encountered an Error in

operation.

[chars] - [chars] [chars]

FIA driver encountered an Error in

operation.

[chars] - [chars] [hex] [hex]

FIA driver operation information.

Initialization of the Amba failed due to:

[chars] with error [hex]([chars])

The amba initialization failed due to the

above mentioned error.

CIH callback registration failed due to:

[chars] with error [hex]([chars])

Registeration of the fia driver with the CIH

library to process fia ASIC interrupts failed.

FIA driver client registration to FSDB failed FIA driver client registration has failed due
with error [hex]([chars]).
to abov error condition.

FIA driver failed to open event connection

manager with error: [hex] ([chars]).

FIA driver failed to open the event

connection manager during the driver
initialization. The driver will be nonoperational due to this error.

FIA driver failed to create event manager

[chars] with error: [hex] ([chars]).

FIA driver failed to create an event

manager during the driver initialization.
The driver will be non-operational due to
this error.

FIA driver failed message queue creation

due to error: [hex] ([chars]).

FIA driver failed to create a message queue

used for inter-thread communication during
the driver initialization.

FIA driver failed to connect for [chars]

service with error: [hex] ([chars]).

FIA driver failed to connect to the identified

service during the driver initialization. The
driver will be non-operational due to this
error.

FIA driver failed [chars] thread creation due FIA driver failed to create the identified
to error: [hex] ([chars]).
thread during driver initialization.

Vendor SDK initialization failed with error:

[hex] ([chars]).

The vendor SDK sofftware database

initialization call by the FIA driver failed
with the indicated error code.

The FIA driver process is exiting with error: FIA driver process is exiting due to the
[hex]
mentioned error condition.

FIA_driver response to FSDB encode failed Fia_driver response is not encoded becuase
because of bufsize is small\n
of bufsize is too small.

Unable to connect to service fsdb due to:

[chars], with error [hex]([chars]).

The FSDB was not able to connect with the

above error condition.

The PCI attach has failed due to: [chars]

with error : [hex]([chars])

The PCI attach has failed due to the above

mentioned reason.

Unable to connect to service due to:

[chars], with error [hex]([chars]).

FIA driver was not able to connect to the

service with the above error condition.

Initialization of the traffic manager failed

due to:[chars] with error [hex]([chars])

The amba traffic manager initialization

failed due to the above mentioned error.

FIA driver failed ltrace initialization with

error: [hex] ([chars]).

The FIA driver could not open/initialize the

ltrace buffer. The FIA driver and the system
should stll function as normal, with the
exception that ltrace will not be available
for fia_drvr process.

Fabric Interface Asic encountered an

internal fatal fault. Card reload is the only
way to recover from this error. The format
Fabric interface asic ASIC[dec] encountered string would display which of the internal
fatal fault [hex] - [chars]
fatal error resulted in this alarm.

Arbitration Serdes Link 0 Failure on FIA

[dec]

Arbitration serdes link 0 failure on FIA

Arbitration Serdes Link 0 Failure on FIA 1

Arbitration serdes link 0 failure on FIA 1.

Arbitration Serdes Link 1 Failure on FIA

[dec]

Arbitration serdes link 1 failure on FIA

Arbitration Serdes Link 1 Failure on FIA 1

Arbitration serdes link 1 failure on FIA 1.

Crossbar fabric interface ASIC-0 init error

Crossbar fabric interface ASIC-0 failed

during init.

Crossbar fabric interface ASIC-1 init error

Crossbar fabric interface ASIC-1 failed

during init.

Data NB Serdes Link 0 Failure on FIA [dec]

Data north bound serdes link 0 failure on

FIA

Data NB Serdes Link 1 Failure on FIA [dec]

Data north bound serdes link 1 failure on

FIA

Data NB Serdes Link 2 Failure on FIA [dec]

Data north bound serdes link 2 failure on

FIA

Data NB Serdes Link 3 Failure on FIA [dec]

Data north bound serdes link 3 failure on

FIA

Data SB Serdes Link 0 Failure on FIA [dec]

Data south bound serdes link 0 failure on

FIA

Data SB Serdes Link 1 Failure on FIA [dec]

Data south bound serdes link 1 failure on

FIA

Data Serdes Link 0 Failure on FIA [dec]

Data serdes link 0 failure on FIA

Data Serdes Link 0 Failure on FIA 1

Data serdes link 0 failure on FIA 1.

Data Serdes Link 1 Failure on FIA [dec]

Data serdes link 1 failure on FIA

Data Serdes Link 1 Failure on FIA 1

Data serdes link 1 failure on FIA 1.

Data Serdes Link 2 Failure on FIA [dec]

Data serdes link 2 failure on FIA

Data Serdes Link 2 Failure on FIA 1

Data serdes link 2 failure on FIA 1.

Data Serdes Link 3 Failure on FIA [dec]

Data serdes link 3 failure on FIA

Data Serdes Link 3 Failure on FIA 1

Data serdes link 3 failure on FIA 1.

Pkt Integrity Error at DDR interface from

Punt/Bridge-0 FPGA on FIA [dec]

Packet Integrity Error at DDR interface from

Punt/Bridge-0 FPGA on FIA

Pkt Integrity Error at DDR interface from

Punt/Bridge-0 FPGA on FIA 1

Packet Integrity Error at DDR interface from

Punt/Bridge-0 FPGA on FIA 0.

Pkt Integrity Error at DDR interface from

Punt/Bridge-1 FPGA on FIA [dec]

Packet Integrity Error at DDR interface from

Punt/Bridge-1 FPGA on FIA

Pkt Integrity Error at DDR interface from

Punt/Bridge-1 FPGA on FIA 1

Packet Integrity Error at DDR interface from

Punt/Bridge-1 FPGA on FIA 1.

Pkt Integrity Error at link interface# 0 from Packet Integrity Error at link interface from
NP/MUX on FIA [dec]
NP/MUX on FIA

Pkt Integrity Error at link interface# 1 from Packet Integrity Error at link nterface from
NP/MUX on FIA [dec]
NP/MUX on FIA

SKT_AB_INTR_FIFO_ORUN on FIA [dec]

SKT_AB_INTR_FIFO_ORUN interrupt on FIA

SKT_AB_INTR_FIFO_URUN on FIA [dec]

SKT_AB_INTR_FIFO_URUN interrupt on FIA

SKT_AB_INTR_IFIFO_ORUN0 on FIA [dec]

SKT_AB_INTR_IFIFO_ORUN0 interrupt on FIA

SKT_AB_INTR_IFIFO_ORUN1 on FIA [dec]

SKT_AB_INTR_IFIFO_ORUN1 interrupt on FIA

SKT_BA_INTR_PA_STALLED on FIA [dec]

SKT_BA_INTR_PA_STALLED interrupt on FIA

SKT_BA_INTR_QUEUE_LEN_URUN on FIA
[dec]

SKT_BA_INTR_QUEUE_LEN_URUN interrupt
on FIA

SKT_CR_INTR_CR_AB_FC on FIA [dec]

SKT_CR_INTR_CR_AB_FC interrupt on FIA

SKT_DM_INTR_FIFO_URUN on FIA [dec]

SKT_DM_INTR_FIFO_URUN interrupt on FIA

SKT_DM_INTR_VM_IFIFO_ORUN interrupt on
SKT_DM_INTR_VM_IFIFO_ORUN on FIA [dec] FIA

SKT_ED_SCH_INTR_MC_BUFFER_HANG on
FIA [dec]

SKT_ED_SCH_INTR_MC_BUFFER_HANG
interrupt on FIA

SKT_ED_SCH_INTR_MC_QTYPE_HANG on FIA SKT_ED_SCH_INTR_MC_QTYPE_HANG

[dec]
interrupt on FIA

SKT_ED_SCH_INTR_UC_QTYPE_HANG on FIA SKT_ED_SCH_INTR_UC_QTYPE_HANG

[dec]
interrupt on FIA

SKT_ET0_INTR_CRC16_CHK_ERR on FIA
[dec]

SKT_ET0_INTR_CRC16_CHK_ERR interrupt
on FIA

SKT_ET0_INTR_CRC32_CHK_ERR on FIA
[dec]

SKT_ET0_INTR_CRC32_CHK_ERR interrupt
on FIA

SKT_ET0_INTR_HDR_CSUM_ERR on FIA
[dec]

SKT_ET0_INTR_HDR_CSUM_ERR interrupt on
FIA

SKT_ET0_INTR_MISSING_EOP on FIA [dec]

SKT_ET0_INTR_MISSING_EOP interrupt on
FIA

SKT_ET0_INTR_MISSING_SOP on FIA [dec]

SKT_ET0_INTR_MISSING_SOP interrupt on
FIA

SKT_ET0_INTR_SOP_ERR on FIA [dec]

SKT_ET0_INTR_SOP_ERR interrupt on FIA

SKT_ET1_INTR_CRC16_CHK_ERR on FIA
[dec]

SKT_ET1_INTR_CRC16_CHK_ERR interrupt
on FIA

SKT_ET1_INTR_CRC32_CHK_ERR on FIA
[dec]

SKT_ET1_INTR_CRC32_CHK_ERR interrupt
on FIA

SKT_ET1_INTR_HDR_CSUM_ERR on FIA
[dec]

SKT_ET1_INTR_HDR_CSUM_ERR interrupt on
FIA

SKT_ET1_INTR_MISSING_EOP on FIA [dec]

SKT_ET1_INTR_MISSING_EOP interrupt on
FIA

SKT_ET1_INTR_MISSING_SOP on FIA [dec]

SKT_ET1_INTR_MISSING_SOP interrupt on
FIA

SKT_ET1_INTR_SOP_ERR on FIA [dec]

SKT_ET1_INTR_SOP_ERR interrupt on FIA

SKT_FI_INTR_RCTL0_HI_EOP_ERR on FIA
[dec]

SKT_FI_INTR_RCTL0_HI_EOP_ERR interrupt
on FIA

SKT_FI_INTR_RCTL0_HI_OVERRUN on FIA
[dec]

SKT_FI_INTR_RCTL0_HI_OVERRUN interrupt
on FIA

SKT_FI_INTR_RCTL0_LO_EOP_ERR on FIA
[dec]

SKT_FI_INTR_RCTL0_LO_EOP_ERR interrupt
on FIA

SKT_FI_INTR_RCTL0_LO_OVERRUN on FIA
[dec]

SKT_FI_INTR_RCTL0_LO_OVERRUN interrupt
on FIA

SKT_FI_INTR_RCTL1_HI_EOP_ERR on FIA
[dec]

SKT_FI_INTR_RCTL1_HI_EOP_ERR interrupt
on FIA

SKT_FI_INTR_RCTL1_HI_OVERRUN on FIA
[dec]

SKT_FI_INTR_RCTL1_HI_OVERRUN interrupt
on FIA

SKT_FI_INTR_RCTL1_LO_EOP_ERR on FIA
[dec]

SKT_FI_INTR_RCTL1_LO_EOP_ERR interrupt
on FIA

SKT_FI_INTR_RCTL1_LO_OVERRUN on FIA
[dec]

SKT_FI_INTR_RCTL1_LO_OVERRUN interrupt
on FIA

SKT_IR0_INTR_ACCPT_TBL_DROP_ERR on
FIA [dec]

SKT_IR0_INTR_ACCPT_TBL_DROP_ERR
interrupt on FIA

SKT_IR0_INTR_DC3_MAX_DROP_ERR on FIA SKT_IR0_INTR_DC3_MAX_DROP_ERR

[dec]
interrupt on FIA

SKT_IR0_INTR_DC3_MIN_DROP_ERR on FIA
[dec]

SKT_IR0_INTR_DC3_MIN_DROP_ERR
interrupt on FIA

SKT_IR0_INTR_FC_BUF_OVFLOW on FIA
[dec]

SKT_IR0_INTR_FC_BUF_OVFLOW interrupt
on FIA

SKT_IR0_INTR_FIFO_ORUN on FIA [dec]

SKT_IR0_INTR_FIFO_ORUN interrupt on FIA

SKT_IR0_INTR_FIFO_URUN on FIA [dec]

SKT_IR0_INTR_FIFO_URUN interrupt on FIA

SKT_IR0_INTR_PKT_EOP_ERR on FIA [dec]

SKT_IR0_INTR_PKT_EOP_ERR interrupt on
FIA

SKT_IR0_INTR_SHORTKT_DROP_ERR on FIA
[dec]

SKT_IR0_INTR_SHORTKT_DROP_ERR
interrupt on FIA

SKT_IR1_INTR_ACCPT_TBL_DROP_ERR on
FIA [dec]

SKT_IR1_INTR_ACCPT_TBL_DROP_ERR
interrupt on FIA

SKT_IR1_INTR_DC3_MAX_DROP_ERR on FIA SKT_IR1_INTR_DC3_MAX_DROP_ERR

[dec]
interrupt on FIA

SKT_IR1_INTR_DC3_MIN_DROP_ERR on FIA
[dec]

SKT_IR1_INTR_DC3_MIN_DROP_ERR
interrupt on FIA

SKT_IR1_INTR_FC_BUF_OVFLOW on FIA
[dec]

SKT_IR1_INTR_FC_BUF_OVFLOW interrupt
on FIA

SKT_IR1_INTR_FIFO_ORUN on FIA [dec]

SKT_IR1_INTR_FIFO_ORUN interrupt on FIA

SKT_IR1_INTR_FIFO_URUN on FIA [dec]

SKT_IR1_INTR_FIFO_URUN interrupt on FIA

SKT_IR1_INTR_PKT_EOP_ERR on FIA [dec]

SKT_IR1_INTR_PKT_EOP_ERR interrupt on
FIA

SKT_IR1_INTR_SHORTKT_DROP_ERR on FIA
[dec]

SKT_IR1_INTR_SHORTKT_DROP_ERR
interrupt on FIA

SKT_NI_INTR_BA_STALLED on FIA [dec]

SKT_NI_INTR_BA_STALLED interrupt on FIA

SKT_NI_INTR_CRC_ERR0 on FIA [dec]

SKT_NI_INTR_CRC_ERR0 interrupt on FIA

SKT_NI_INTR_CRC_ERR1 on FIA [dec]

SKT_NI_INTR_CRC_ERR1 interrupt on FIA

SKT_NI_INTR_CRC_ERR2 on FIA [dec]

SKT_NI_INTR_CRC_ERR2 interrupt on FIA

SKT_NI_INTR_CRC_ERR3 on FIA [dec]

SKT_NI_INTR_CRC_ERR3 interrupt on FIA

SKT_NI_INTR_CRC_ERR4 on FIA [dec]

SKT_NI_INTR_CRC_ERR4 interrupt on FIA

SKT_NI_INTR_PW_STALLED on FIA [dec]

SKT_NI_INTR_PW_STALLED interrupt on FIA

SKT_PA_INTR_MAX_SZ_ERR on FIA [dec]

SKT_PA_INTR_MAX_SZ_ERR interrupt on FIA

SKT_PA_INTR_UCFF_UDR_ERR on FIA [dec]

SKT_PA_INTR_UCFF_UDR_ERR interrupt on
FIA

SKT_PR_INTR_PR_BA_PROTOCOL_ERR on
FIA [dec]

SKT_PR_INTR_PR_BA_PROTOCOL_ERR
interrupt on FIA

SKT_PW_INTR_HDR_PRS_CHDR_VQI_VLD_ER SKT_PW_INTR_HDR_PRS_CHDR_VQI_VLD_ER
R on FIA [dec]
R interrupt on FIA

SKT_PW_INTR_HDR_PRS_EOP_SOP_ERR on
FIA [dec]

SKT_PW_INTR_HDR_PRS_EOP_SOP_ERR
interrupt on FIA

SKT_PW_INTR_HDR_PRS_HDR_TYPE_ERR on SKT_PW_INTR_HDR_PRS_HDR_TYPE_ERR
FIA [dec]
interrupt on FIA

SKT_PW_INTR_HDR_PRS_SOP_EOP_ERR on
FIA [dec]

SKT_PW_INTR_HDR_PRS_SOP_EOP_ERR
interrupt on FIA

SKT_PW_INTR_HDR_PRS_SOP_SEEN_SOP_ER SKT_PW_INTR_HDR_PRS_SOP_SEEN_SOP_ER
R on FIA [dec]
R interrupt on FIA

SKT_PW_INTR_LEN_DROP_CNT_ERR on FIA
[dec]

SKT_PW_INTR_LEN_DROP_CNT_ERR
interrupt on FIA

SKT_PW_INTR_SRC_PT_MISMATCH_ERR on
FIA [dec]

SKT_PW_INTR_SRC_PT_MISMATCH_ERR
interrupt on FIA

SKT_RA_INTR_VQI_DEQ_QERR on FIA [dec]

SKT_RA_INTR_VQI_DEQ_QERR interrupt on
FIA

SKT_RA_INTR_VQI_ENQ_QERR on FIA [dec]

SKT_RA_INTR_VQI_ENQ_QERR interrupt on
FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_0 on FIA [dec]
Y_ERROR_0 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_1 on FIA [dec]
Y_ERROR_1 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_10 on FIA [dec]
Y_ERROR_10 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_11 on FIA [dec]
Y_ERROR_11 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_12 on FIA [dec]
Y_ERROR_12 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_13 on FIA [dec]
Y_ERROR_13 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_14 on FIA [dec]
Y_ERROR_14 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_15 on FIA [dec]
Y_ERROR_15 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_2 on FIA [dec]
Y_ERROR_2 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_3 on FIA [dec]
Y_ERROR_3 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_4 on FIA [dec]
Y_ERROR_4 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_5 on FIA [dec]
Y_ERROR_5 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_6 on FIA [dec]
Y_ERROR_6 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_7 on FIA [dec]
Y_ERROR_7 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_8 on FIA [dec]
Y_ERROR_8 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_DISPARIT SKT_SMC0_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_9 on FIA [dec]
Y_ERROR_9 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_0 on FIA [dec]
BAND_ERROR_0 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_1 on FIA [dec]
BAND_ERROR_1 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_10 on FIA [dec]
BAND_ERROR_10 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_11 on FIA [dec]
BAND_ERROR_11 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_12 on FIA [dec]
BAND_ERROR_12 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_13 on FIA [dec]
BAND_ERROR_13 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_14 on FIA [dec]
BAND_ERROR_14 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_15 on FIA [dec]
BAND_ERROR_15 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_2 on FIA [dec]
BAND_ERROR_2 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_3 on FIA [dec]
BAND_ERROR_3 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_4 on FIA [dec]
BAND_ERROR_4 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_5 on FIA [dec]
BAND_ERROR_5 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_6 on FIA [dec]
BAND_ERROR_6 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_7 on FIA [dec]
BAND_ERROR_7 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_8 on FIA [dec]
BAND_ERROR_8 interrupt on FIA

SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC0_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_9 on FIA [dec]
BAND_ERROR_9 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_0 on FIA [dec]
ATE_0 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_1 on FIA [dec]
ATE_1 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_10 on FIA [dec]
ATE_10 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_11 on FIA [dec]
ATE_11 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_12 on FIA [dec]
ATE_12 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_13 on FIA [dec]
ATE_13 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_14 on FIA [dec]
ATE_14 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_15 on FIA [dec]
ATE_15 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_2 on FIA [dec]
ATE_2 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_3 on FIA [dec]
ATE_3 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_4 on FIA [dec]
ATE_4 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_5 on FIA [dec]
ATE_5 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_6 on FIA [dec]
ATE_6 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_7 on FIA [dec]
ATE_7 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_8 on FIA [dec]
ATE_8 interrupt on FIA

SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC0_INTR_ALIGN_ERROR_LANE_INDIC
ATE_9 on FIA [dec]
ATE_9 interrupt on FIA

SKT_SMC0_INTR_CRC_TRANS_ERR on FIA
[dec]

SKT_SMC0_INTR_CRC_TRANS_ERR interrupt
on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_0 on FIA [dec]
TE_0 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_1 on FIA [dec]
TE_1 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_10 on FIA [dec]
TE_10 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_11 on FIA [dec]
TE_11 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_12 on FIA [dec]
TE_12 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_13 on FIA [dec]
TE_13 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_14 on FIA [dec]
TE_14 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_15 on FIA [dec]
TE_15 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_2 on FIA [dec]
TE_2 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_3 on FIA [dec]
TE_3 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_4 on FIA [dec]
TE_4 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_5 on FIA [dec]
TE_5 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_6 on FIA [dec]
TE_6 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_7 on FIA [dec]
TE_7 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_8 on FIA [dec]
TE_8 interrupt on FIA

SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA SKT_SMC0_INTR_DISP_ERROR_LANE_INDICA
TE_9 on FIA [dec]
TE_9 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_0 on FIA [dec]
TE_0 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_1 on FIA [dec]
TE_1 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_10 on FIA [dec]
TE_10 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_11 on FIA [dec]
TE_11 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_12 on FIA [dec]
TE_12 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_13 on FIA [dec]
TE_13 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_14 on FIA [dec]
TE_14 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_15 on FIA [dec]
TE_15 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_2 on FIA [dec]
TE_2 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_3 on FIA [dec]
TE_3 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_4 on FIA [dec]
TE_4 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_5 on FIA [dec]
TE_5 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_6 on FIA [dec]
TE_6 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_7 on FIA [dec]
TE_7 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_8 on FIA [dec]
TE_8 interrupt on FIA

SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA SKT_SMC0_INTR_OOB_ERROR_LANE_INDICA
TE_9 on FIA [dec]
TE_9 interrupt on FIA

SKT_SMC0_INTR_RX_DESKEW_ERR on FIA
[dec]

SKT_SMC0_INTR_RX_DESKEW_ERR interrupt
on FIA

SKT_SMC0_INTR_TSF_SOT_MISS_ERROR on SKT_SMC0_INTR_TSF_SOT_MISS_ERROR
FIA [dec]
interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_0 on FIA [dec]
Y_ERROR_0 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_1 on FIA [dec]
Y_ERROR_1 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_10 on FIA [dec]
Y_ERROR_10 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_11 on FIA [dec]
Y_ERROR_11 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_12 on FIA [dec]
Y_ERROR_12 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_13 on FIA [dec]
Y_ERROR_13 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_14 on FIA [dec]
Y_ERROR_14 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_15 on FIA [dec]
Y_ERROR_15 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_2 on FIA [dec]
Y_ERROR_2 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_3 on FIA [dec]
Y_ERROR_3 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_4 on FIA [dec]
Y_ERROR_4 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_5 on FIA [dec]
Y_ERROR_5 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_6 on FIA [dec]
Y_ERROR_6 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_7 on FIA [dec]
Y_ERROR_7 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_8 on FIA [dec]
Y_ERROR_8 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_DISPARIT SKT_SMC1_INTR_8B10B_DECODE_DISPARIT
Y_ERROR_9 on FIA [dec]
Y_ERROR_9 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_0 on FIA [dec]
BAND_ERROR_0 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_1 on FIA [dec]
BAND_ERROR_1 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_10 on FIA [dec]
BAND_ERROR_10 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_11 on FIA [dec]
BAND_ERROR_11 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_12 on FIA [dec]
BAND_ERROR_12 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_13 on FIA [dec]
BAND_ERROR_13 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_14 on FIA [dec]
BAND_ERROR_14 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_15 on FIA [dec]
BAND_ERROR_15 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_2 on FIA [dec]
BAND_ERROR_2 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_3 on FIA [dec]
BAND_ERROR_3 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_4 on FIA [dec]
BAND_ERROR_4 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_5 on FIA [dec]
BAND_ERROR_5 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_6 on FIA [dec]
BAND_ERROR_6 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_7 on FIA [dec]
BAND_ERROR_7 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_8 on FIA [dec]
BAND_ERROR_8 interrupt on FIA

SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_ SKT_SMC1_INTR_8B10B_DECODE_OUT_OF_
BAND_ERROR_9 on FIA [dec]
BAND_ERROR_9 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_0 on FIA [dec]
ATE_0 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_1 on FIA [dec]
ATE_1 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_10 on FIA [dec]
ATE_10 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_11 on FIA [dec]
ATE_11 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_12 on FIA [dec]
ATE_12 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_13 on FIA [dec]
ATE_13 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_14 on FIA [dec]
ATE_14 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_15 on FIA [dec]
ATE_15 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_2 on FIA [dec]
ATE_2 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_3 on FIA [dec]
ATE_3 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_4 on FIA [dec]
ATE_4 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_5 on FIA [dec]
ATE_5 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_6 on FIA [dec]
ATE_6 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_7 on FIA [dec]
ATE_7 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_8 on FIA [dec]
ATE_8 interrupt on FIA

SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC SKT_SMC1_INTR_ALIGN_ERROR_LANE_INDIC
ATE_9 on FIA [dec]
ATE_9 interrupt on FIA

SKT_SMC1_INTR_CRC_TRANS_ERR on FIA
[dec]

SKT_SMC1_INTR_CRC_TRANS_ERR interrupt
on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_0 on FIA [dec]
TE_0 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_1 on FIA [dec]
TE_1 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_10 on FIA [dec]
TE_10 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_11 on FIA [dec]
TE_11 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_12 on FIA [dec]
TE_12 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_13 on FIA [dec]
TE_13 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_14 on FIA [dec]
TE_14 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_15 on FIA [dec]
TE_15 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_2 on FIA [dec]
TE_2 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_3 on FIA [dec]
TE_3 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_4 on FIA [dec]
TE_4 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_5 on FIA [dec]
TE_5 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_6 on FIA [dec]
TE_6 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_7 on FIA [dec]
TE_7 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_8 on FIA [dec]
TE_8 interrupt on FIA

SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA SKT_SMC1_INTR_DISP_ERROR_LANE_INDICA
TE_9 on FIA [dec]
TE_9 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_0 on FIA [dec]
TE_0 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_1 on FIA [dec]
TE_1 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_10 on FIA [dec]
TE_10 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_11 on FIA [dec]
TE_11 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_12 on FIA [dec]
TE_12 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_13 on FIA [dec]
TE_13 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_14 on FIA [dec]
TE_14 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_15 on FIA [dec]
TE_15 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_2 on FIA [dec]
TE_2 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_3 on FIA [dec]
TE_3 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_4 on FIA [dec]
TE_4 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_5 on FIA [dec]
TE_5 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_6 on FIA [dec]
TE_6 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_7 on FIA [dec]
TE_7 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_8 on FIA [dec]
TE_8 interrupt on FIA

SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA SKT_SMC1_INTR_OOB_ERROR_LANE_INDICA
TE_9 on FIA [dec]
TE_9 interrupt on FIA

SKT_SMC1_INTR_RX_DESKEW_ERR on FIA
[dec]

SKT_SMC1_INTR_RX_DESKEW_ERR interrupt
on FIA

SKT_SMC1_INTR_TSF_SOT_MISS_ERROR on SKT_SMC1_INTR_TSF_SOT_MISS_ERROR
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_ALIGN_FAIL on FIA [dec]

SKT_SP0_INTR_ALIGN_FAIL interrupt on FIA

SKT_SP0_INTR_BAD_ALIGN on FIA [dec]

SKT_SP0_INTR_BAD_ALIGN interrupt on FIA

SKT_SP0_INTR_BAD_CODE on FIA [dec]

SKT_SP0_INTR_BAD_CODE interrupt on FIA

SKT_SP0_INTR_CW_CRC_ERR on FIA [dec]

SKT_SP0_INTR_CW_CRC_ERR interrupt on
FIA

SKT_SP0_INTR_LANE_CRC_ERR interrupt on
SKT_SP0_INTR_LANE_CRC_ERR on FIA [dec] FIA

SKT_SP0_INTR_SLICE_ERR_0 on FIA [dec]

SKT_SP0_INTR_SLICE_ERR_0 interrupt on
FIA

SKT_SP0_INTR_SLICE_ERR_1 on FIA [dec]

SKT_SP0_INTR_SLICE_ERR_1 interrupt on
FIA

SKT_SP0_INTR_SLICE_ERR_2 on FIA [dec]

SKT_SP0_INTR_SLICE_ERR_2 interrupt on
FIA

SKT_SP0_INTR_SLICE_ERR_3 on FIA [dec]

SKT_SP0_INTR_SLICE_ERR_3 interrupt on
FIA

SKT_SP0_INTR_SLICE_ERR_4 on FIA [dec]

SKT_SP0_INTR_SLICE_ERR_4 interrupt on
FIA

SKT_SP0_INTR_SLICE_ERR_5 on FIA [dec]

SKT_SP0_INTR_SLICE_ERR_5 interrupt on
FIA

SKT_SP0_INTR_SLICE_ERR_6 on FIA [dec]

SKT_SP0_INTR_SLICE_ERR_6 interrupt on
FIA

SKT_SP0_INTR_SLICE_ERR_7 on FIA [dec]

SKT_SP0_INTR_SLICE_ERR_7 interrupt on
FIA

SKT_SP0_INTR_SLICE0_CODE_ERR on FIA
[dec]

SKT_SP0_INTR_SLICE0_CODE_ERR interrupt
on FIA

SKT_SP0_INTR_SLICE0_CODE_ERR_HIGH on SKT_SP0_INTR_SLICE0_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE0_LANE_CRC_ERR on
FIA [dec]

SKT_SP0_INTR_SLICE0_LANE_CRC_ERR
interrupt on FIA

SKT_SP0_INTR_SLICE0_WORD_OUTSYNC on SKT_SP0_INTR_SLICE0_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE1_CODE_ERR on FIA
[dec]

SKT_SP0_INTR_SLICE1_CODE_ERR interrupt
on FIA

SKT_SP0_INTR_SLICE1_CODE_ERR_HIGH on SKT_SP0_INTR_SLICE1_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE1_LANE_CRC_ERR on
FIA [dec]

SKT_SP0_INTR_SLICE1_LANE_CRC_ERR
interrupt on FIA

SKT_SP0_INTR_SLICE1_WORD_OUTSYNC on SKT_SP0_INTR_SLICE1_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE2_CODE_ERR on FIA
[dec]

SKT_SP0_INTR_SLICE2_CODE_ERR interrupt
on FIA

SKT_SP0_INTR_SLICE2_CODE_ERR_HIGH on SKT_SP0_INTR_SLICE2_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE2_LANE_CRC_ERR on
FIA [dec]

SKT_SP0_INTR_SLICE2_LANE_CRC_ERR
interrupt on FIA

SKT_SP0_INTR_SLICE2_WORD_OUTSYNC on SKT_SP0_INTR_SLICE2_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE3_CODE_ERR on FIA
[dec]

SKT_SP0_INTR_SLICE3_CODE_ERR interrupt
on FIA

SKT_SP0_INTR_SLICE3_CODE_ERR_HIGH on SKT_SP0_INTR_SLICE3_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE3_LANE_CRC_ERR on
FIA [dec]

SKT_SP0_INTR_SLICE3_LANE_CRC_ERR
interrupt on FIA

SKT_SP0_INTR_SLICE3_WORD_OUTSYNC on SKT_SP0_INTR_SLICE3_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE4_CODE_ERR on FIA
[dec]

SKT_SP0_INTR_SLICE4_CODE_ERR interrupt
on FIA

SKT_SP0_INTR_SLICE4_CODE_ERR_HIGH on SKT_SP0_INTR_SLICE4_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE4_LANE_CRC_ERR on
FIA [dec]

SKT_SP0_INTR_SLICE4_LANE_CRC_ERR
interrupt on FIA

SKT_SP0_INTR_SLICE4_WORD_OUTSYNC on SKT_SP0_INTR_SLICE4_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE5_CODE_ERR on FIA
[dec]

SKT_SP0_INTR_SLICE5_CODE_ERR interrupt
on FIA

SKT_SP0_INTR_SLICE5_CODE_ERR_HIGH on SKT_SP0_INTR_SLICE5_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE5_LANE_CRC_ERR on
FIA [dec]

SKT_SP0_INTR_SLICE5_LANE_CRC_ERR
interrupt on FIA

SKT_SP0_INTR_SLICE5_WORD_OUTSYNC on SKT_SP0_INTR_SLICE5_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE6_CODE_ERR on FIA
[dec]

SKT_SP0_INTR_SLICE6_CODE_ERR interrupt
on FIA

SKT_SP0_INTR_SLICE6_CODE_ERR_HIGH on SKT_SP0_INTR_SLICE6_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE6_LANE_CRC_ERR on
FIA [dec]

SKT_SP0_INTR_SLICE6_LANE_CRC_ERR
interrupt on FIA

SKT_SP0_INTR_SLICE6_WORD_OUTSYNC on SKT_SP0_INTR_SLICE6_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE7_CODE_ERR on FIA
[dec]

SKT_SP0_INTR_SLICE7_CODE_ERR interrupt
on FIA

SKT_SP0_INTR_SLICE7_CODE_ERR_HIGH on SKT_SP0_INTR_SLICE7_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP0_INTR_SLICE7_LANE_CRC_ERR on
FIA [dec]

SKT_SP0_INTR_SLICE7_LANE_CRC_ERR
interrupt on FIA

SKT_SP0_INTR_SLICE7_WORD_OUTSYNC on SKT_SP0_INTR_SLICE7_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_ALIGN_FAIL on FIA [dec]

SKT_SP1_INTR_ALIGN_FAIL interrupt on FIA

SKT_SP1_INTR_BAD_ALIGN on FIA [dec]

SKT_SP1_INTR_BAD_ALIGN interrupt on FIA

SKT_SP1_INTR_BAD_CODE on FIA [dec]

SKT_SP1_INTR_BAD_CODE interrupt on FIA

SKT_SP1_INTR_CW_CRC_ERR on FIA [dec]

SKT_SP1_INTR_CW_CRC_ERR interrupt on
FIA

SKT_SP1_INTR_LANE_CRC_ERR interrupt on
SKT_SP1_INTR_LANE_CRC_ERR on FIA [dec] FIA

SKT_SP1_INTR_SLICE_ERR_0 on FIA [dec]

SKT_SP1_INTR_SLICE_ERR_0 interrupt on
FIA

SKT_SP1_INTR_SLICE_ERR_1 on FIA [dec]

SKT_SP1_INTR_SLICE_ERR_1 interrupt on
FIA

SKT_SP1_INTR_SLICE_ERR_2 on FIA [dec]

SKT_SP1_INTR_SLICE_ERR_2 interrupt on
FIA

SKT_SP1_INTR_SLICE_ERR_3 on FIA [dec]

SKT_SP1_INTR_SLICE_ERR_3 interrupt on
FIA

SKT_SP1_INTR_SLICE_ERR_4 on FIA [dec]

SKT_SP1_INTR_SLICE_ERR_4 interrupt on
FIA

SKT_SP1_INTR_SLICE_ERR_5 on FIA [dec]

SKT_SP1_INTR_SLICE_ERR_5 interrupt on
FIA

SKT_SP1_INTR_SLICE_ERR_6 on FIA [dec]

SKT_SP1_INTR_SLICE_ERR_6 interrupt on
FIA

SKT_SP1_INTR_SLICE_ERR_7 on FIA [dec]

SKT_SP1_INTR_SLICE_ERR_7 interrupt on
FIA

SKT_SP1_INTR_SLICE0_CODE_ERR on FIA
[dec]

SKT_SP1_INTR_SLICE0_CODE_ERR interrupt
on FIA

SKT_SP1_INTR_SLICE0_CODE_ERR_HIGH on SKT_SP1_INTR_SLICE0_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE0_LANE_CRC_ERR on
FIA [dec]

SKT_SP1_INTR_SLICE0_LANE_CRC_ERR
interrupt on FIA

SKT_SP1_INTR_SLICE0_WORD_OUTSYNC on SKT_SP1_INTR_SLICE0_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE1_CODE_ERR on FIA
[dec]

SKT_SP1_INTR_SLICE1_CODE_ERR interrupt
on FIA

SKT_SP1_INTR_SLICE1_CODE_ERR_HIGH on SKT_SP1_INTR_SLICE1_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE1_LANE_CRC_ERR on
FIA [dec]

SKT_SP1_INTR_SLICE1_LANE_CRC_ERR
interrupt on FIA

SKT_SP1_INTR_SLICE1_WORD_OUTSYNC on SKT_SP1_INTR_SLICE1_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE2_CODE_ERR on FIA
[dec]

SKT_SP1_INTR_SLICE2_CODE_ERR interrupt
on FIA

SKT_SP1_INTR_SLICE2_CODE_ERR_HIGH on SKT_SP1_INTR_SLICE2_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE2_LANE_CRC_ERR on
FIA [dec]

SKT_SP1_INTR_SLICE2_LANE_CRC_ERR
interrupt on FIA

SKT_SP1_INTR_SLICE2_WORD_OUTSYNC on SKT_SP1_INTR_SLICE2_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE3_CODE_ERR on FIA
[dec]

SKT_SP1_INTR_SLICE3_CODE_ERR interrupt
on FIA

SKT_SP1_INTR_SLICE3_CODE_ERR_HIGH on SKT_SP1_INTR_SLICE3_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE3_LANE_CRC_ERR on
FIA [dec]

SKT_SP1_INTR_SLICE3_LANE_CRC_ERR
interrupt on FIA

SKT_SP1_INTR_SLICE3_WORD_OUTSYNC on SKT_SP1_INTR_SLICE3_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE4_CODE_ERR on FIA
[dec]

SKT_SP1_INTR_SLICE4_CODE_ERR interrupt
on FIA

SKT_SP1_INTR_SLICE4_CODE_ERR_HIGH on SKT_SP1_INTR_SLICE4_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE4_LANE_CRC_ERR on
FIA [dec]

SKT_SP1_INTR_SLICE4_LANE_CRC_ERR
interrupt on FIA

SKT_SP1_INTR_SLICE4_WORD_OUTSYNC on SKT_SP1_INTR_SLICE4_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE5_CODE_ERR on FIA
[dec]

SKT_SP1_INTR_SLICE5_CODE_ERR interrupt
on FIA

SKT_SP1_INTR_SLICE5_CODE_ERR_HIGH on SKT_SP1_INTR_SLICE5_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE5_LANE_CRC_ERR on
FIA [dec]

SKT_SP1_INTR_SLICE5_LANE_CRC_ERR
interrupt on FIA

SKT_SP1_INTR_SLICE5_WORD_OUTSYNC on SKT_SP1_INTR_SLICE5_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE6_CODE_ERR on FIA
[dec]

SKT_SP1_INTR_SLICE6_CODE_ERR interrupt
on FIA

SKT_SP1_INTR_SLICE6_CODE_ERR_HIGH on SKT_SP1_INTR_SLICE6_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE6_LANE_CRC_ERR on
FIA [dec]

SKT_SP1_INTR_SLICE6_LANE_CRC_ERR
interrupt on FIA

SKT_SP1_INTR_SLICE6_WORD_OUTSYNC on SKT_SP1_INTR_SLICE6_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE7_CODE_ERR on FIA
[dec]

SKT_SP1_INTR_SLICE7_CODE_ERR interrupt
on FIA

SKT_SP1_INTR_SLICE7_CODE_ERR_HIGH on SKT_SP1_INTR_SLICE7_CODE_ERR_HIGH
FIA [dec]
interrupt on FIA

SKT_SP1_INTR_SLICE7_LANE_CRC_ERR on
FIA [dec]

SKT_SP1_INTR_SLICE7_LANE_CRC_ERR
interrupt on FIA

SKT_SP1_INTR_SLICE7_WORD_OUTSYNC on SKT_SP1_INTR_SLICE7_WORD_OUTSYNC
FIA [dec]
interrupt on FIA

SKT_SSP_INTR_SFIFO_FULL_IF0 interrupt on
SKT_SSP_INTR_SFIFO_FULL_IF0 on FIA [dec] FIA

SKT_SSP_INTR_SFIFO_FULL_IF1 interrupt on
SKT_SSP_INTR_SFIFO_FULL_IF1 on FIA [dec] FIA

SKT_SSP_INTR_SP0_RX_EOP_ERR_P on FIA
[dec]

SKT_SSP_INTR_SP0_RX_EOP_ERR_P
interrupt on FIA

SKT_SSP_INTR_SP0_RX_NEOP_ERR_P on FIA SKT_SSP_INTR_SP0_RX_NEOP_ERR_P

[dec]
interrupt on FIA

SKT_SSP_INTR_SP1_RX_EOP_ERR_P on FIA
[dec]

SKT_SSP_INTR_SP1_RX_EOP_ERR_P
interrupt on FIA

SKT_SSP_INTR_SP1_RX_NEOP_ERR_P on FIA SKT_SSP_INTR_SP1_RX_NEOP_ERR_P

[dec]
interrupt on FIA

SKT_TF_INTR_FIFO_0HI_EXT_ERR on FIA
[dec]

SKT_TF_INTR_FIFO_0HI_EXT_ERR interrupt
on FIA

SKT_TF_INTR_FIFO_0HI_OVFL on FIA [dec]

SKT_TF_INTR_FIFO_0HI_OVFL interrupt on
FIA

SKT_TF_INTR_FIFO_0LO_OVFL on FIA [dec]

SKT_TF_INTR_FIFO_0LO_OVFL interrupt on
FIA

SKT_TF_INTR_FIFO_1HI_EXT_ERR on FIA
[dec]

SKT_TF_INTR_FIFO_1HI_EXT_ERR interrupt
on FIA

SKT_TF_INTR_FIFO_1HI_OVFL on FIA [dec]

SKT_TF_INTR_FIFO_1HI_OVFL interrupt on
FIA

SKT_TF_INTR_FIFO_1LO_OVFL on FIA [dec]

SKT_TF_INTR_FIFO_1LO_OVFL interrupt on
FIA

SKT_VM_INTR_AB_REQ_TOUT_ERR on FIA
[dec]

SKT_VM_INTR_AB_REQ_TOUT_ERR interrupt
on FIA

SKT_VM_INTR_DM_REQ_TOUT_ERR on FIA
[dec]

SKT_VM_INTR_DM_REQ_TOUT_ERR interrupt
on FIA

SKT_VM_INTR_DM_UNEXP_GNT_ERR on FIA SKT_VM_INTR_DM_UNEXP_GNT_ERR

[dec]
interrupt on FIA

SKT_VM_INTR_PA_SOF_EOF_ERR on FIA
[dec]

SKT_VM_INTR_PA_SOF_EOF_ERR interrupt
on FIA

Fabric interface ASIC-[dec] has sustained

CRC errors

Fabric interface ASIC is reporting a

sustained rate of CRC errors.

Crossbar fabric interface ASIC-0

temperature is too high

Crossbar fabric interface ASIC-0 is reporting

a very high temperature.

Crossbar fabric interface ASIC-1

temperature is too high

Crossbar fabric interface ASIC-1 is reporting

a very high temperature.

Driver failed to lock mutex to access qlink

register. rc([hex]) [chars]

The FIA driver cannot access the qlink

register due to mutex lock failure, because
of which it cannot configure the qlink ASIC
on ASIC/channel errors or enabling the
channels.

Driver failed to unlock mutex to after

accessing qlink. rc([hex]) [chars]

The FIA driver cannot unlock the mutex

after accessing the link, because of which it
cannot configure the qlink ASIC on
ASIC/channel errors or enabling the
channels if the mutex is not working.

[chars] [chars] ([hex])

This error usually indicates an internal

hardware problem on the card. The internal
parity error affects the communication bus
between adjacent ASICs on the hardware
datapath. The From Fabric or To Fabric
direction, the detailed error string and the
slot number are provided as part of the
message.

[chars] [chars] ([hex])

This error usually indicates an internal

hardware problem on the card. The internal
parity error affects the communication bus
between adjacent ASICs on the hardware
datapath. The From Fabric or To Fabric
direction, the detailed error string and the
slot number are provided as part of the
message.

Initialization Error: FIA-driver failed to

create Bridge interface. Exiting

FIA driver could not create Bridge instance.

Initialization Error: Bridge-driver failed to

create Event Manager. Exiting

Fabric Bridge driver Event Manager create

error

Initialization Error: Bridge-driver failed to

initialize [chars]. Reason: [chars]. Exiting

Fabric Bridge driver subsystem initialization

error

Initialization Error: Bridge-driver failed to

invoke OS [chars] service. Exiting

Fabric Bridge driver Event Manager create

error

Initialization Error: FIA-driver client failed to

create Event Manager. Exiting.
FIA-driver Event Manager create error

Initialization Error: FIA-driver client failed to

initialize [chars]. . Exiting
Fabric driver subsystem initialization error

Failed to create Event Connection

Manager[[chars]]: [chars], exiting....

The FIA driver encountered an event

connection manager error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger MSC reload.
After a certain number of MSC reloads, the
shelf manager will permanently shutdown
the MSC.

Failed to register [chars] connection

notification handler with the Event
Connection Manager. Err : [chars],
exiting....

The FIA driver encountered an event

connection manager error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger MSC reload.
After a certain number of MSC reloads, the
shelf manager will permanently shutdown
the MSC.

EIO link training failure threshold reached.

Link will not be re-trained. ASIC instance:
[dec], EIO link ID: [dec]

Repeated attempts to train the EIO links

between the FIA and Ingressq/Fabric ASIC
has failed. No further attempts to retrain
the link will be made. This is indicative of a
hardware failure on the serial link between
the ASICs or an inter-process
communication error between the driver
processes.

Initialization Error: FIA-driver failed to

initialize client library on [chars]. Reason:
[chars]. Exiting

FIA driver ENS client library initialization

error

Initialization Error: FIA-driver failed to send

message to [chars]. Reason: [chars].
FIA driver ENS message communication
Exiting
error

Initialization Error: FIA-driver failed to

create Event Manager. Exiting.

FIA-driver Event Manager create error

The FIA driver was unable to initialize an

event manager for processing messages
and hence failed to initialize. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger MSC reload.
After a certain number of MSC reloads, the
Failed to initialize the event manager. Err : shelf manager will permanently shutdown
[chars], exiting...
the MSC.

[chars]: Error creating Main event mgr:

[[hex]] [chars]\n

Fia event manager initialization failed

FIA driver init failed ; rc = [dec]\n

Fia Driver initialization failed

Initialization Error: FIA-driver failed to

initialize [chars]. Reason: [chars]. Exiting

Fabric driver subsystem initialization error

Initialization Error [[chars]]: [chars],

exiting....

The FIA driver failed to initialize the device

resulting in the restart of the FIA driver
process. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger MSC
reload. After a certain number of MSC
reloads, the shelf manager will
permanently shutdown the MSC.

Initialization Error: FIA-driver failed to

initialize XAUI interface with NP.[dec].
Exiting.

FIA driver encountered a fatal error during

interface intialization and is not able
recover from the error after retries. A
reason text will be supplied. Call support
with this text.

qlink driver process unable to create ltrace

Fabric: qlink failed to create [chars] ltrace. init files. It may be due to platform-infra
Error: [chars]
failure. Not a PD problem.

Initialization Error: FIA-driver could not map FIA driver encountered a fatal memory
device memory
allocation error

Memory allocation failed for internal data

structures

Memory was not available for an internal

data structure. The requested operation
could not be accomplished because of a
low memory condition. The LC will not boot
up successfully and will not be able to
participate in data forwarding.

Memory allocation failed for internal data

structures

Memory was not available for an internal

data structure. The requested operation
could not be accomplished because of a
low memory condition. The LC will not boot
up successfully and will not be able to
participate in data forwarding.

Failed to map ASIC instance [dec] into

memory (PROT flags: [dec], MAP flags:
[dec]): [chars], exiting...

The FIA driver was unable to map the

hardware of the specified ASIC instance
into its memory space and therefore failed
to initialize. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger MSC
reload. After a certain number of MSC
reloads, the shelf manager will
permanently shutdown the MSC.

Failed to lock TX slice PLL after [unsigned

int] retries (ASIC instance: [dec], slice ID:
[unsigned int]).

While initializing the transmit slices of the

FIA, the driver failed to lock the PLL. This is
caused due to a clock synchronization
problem between the MSC and the fabric
board. This would result in loss of
connectivity and bandwidth to affected
fabric board.

Initialization Error: [chars] failed to register

with [chars]. Exiting
Fabric driver subsystem initialization error

Initialization Error: FIA-driver exhausted

maximum restart attempts to initialize.
Exiting.

FIA driver encountered a persistance fatal

error during intialization and subsequent
restarts. A reason text will be supplied. Call
support with this text.

Failed to [chars] due to [chars], [chars]

The FIA driver failed to retrive card

state/type from shelfmgr. If the failure is
due to a non EBUSY/EAGAIN error this will
result in restart of the FIA driver process.
The System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger MSC reload.
After a certain number of MSC reloads, the
shelf manager will permanently shutdown
the MSC.

[chars]: [chars] [hex]

This error usually indicates an internal

hardware problem on the card. The internal
parity error affects the communication bus
between adjacent ASICs on the hardware
datapath. In this case parity error was
detected in the FFIA internal reassembly
memory. This error will trigger a recovery
operation. The LC may not be able to
forward data packets and traffic loss may
be observed due to this error.

[chars]: [chars] [hex]

This error usually indicates an internal

hardware problem on the card. The internal
parity error affects the communication bus
between adjacent ASICs on the hardware
datapath. In this case the backpressure
signals between FFIA and Tx PSE is having
signal integrity issue. This error will trigger
a recovery operation. The LC may not be
able to forward data packets and traffic
loss may be observed due to this error.

Failed to configure [chars] config value :

[hex] in hardware, fc_mask = [hex], staus
= [hex]

The low level FIA driver was unable to

complete its write operation. Possible
cause is harware failure. Error recovery will
be triggered for this error. The direction
value of fia_config passed and status
returned of the failure are indicated in th
emessage.

Too many CRC errors on fabric serial line

(from fabric plane [dec])

This error indicates a problem in the

interface between the card reporting error
and the switch fabric card in the indicated
fabric plane. Data corruption is imminent.
Central Fabric control will take appropriate
action to correct the situation.

Too many CRC errors on fabric serial line

(from fabric plane [dec])

This error indicates a problem in the

interface between the card reporting error
and the switch fabric card in the indicated
fabric plane. Data corruption is imminent.

FIA device access (read) failed for [chars]

The low level fabric interface ASIC driver

was unable to complete its hardware
access operation. Hardware configuration
may not have been successfully
completed. This may result in traffic loss.
The output of the show command may not
be valid. The direction of the error is
indicated in the message.

An unexpected error has occurred. This

error typically means that a unicast or a
multicast packet was received by the fabric
interface ASIC to be forwarded across the
switching fabric without any destination
slot set in the header of the data packet.
The direction of the error and the slot are
[chars] Empty destination software request indicated by the parameter in the
error [hex]
message.

[chars] [chars] ([hex])

This error indicates a (possibly temporary)

problem in the interface between the card
reporting error and the switch fabric. Either
the switch fabric is not able source or drain
the data packets to this LC. This error is
traffic affecting. Error recovery will be
triggered. The From Fabric or To Fabric
direction, the detailed error string and the
slot number are provided as part of the
message.

[chars] [chars] ([hex])

This error indicates a (possibly temporary)

problem in the interface between the card
reporting error and the switch fabric. The
error recovery will be triggered and the
process should recover after a reset of the
affected ASIC. The From Fabric or To Fabric
direction, the detailed error string and the
slot number are provided as part of the
message.

Unexpected [chars] interrupt

An unexpected error has occurred. This

error will trigger an error recovery and is
traffic affecting. The direction in which the
error occurred is specified as part of the
meassage. This error message indicates a
masked interrupt occured, even though its
handled by the driver, this error should not
have happened.

Persistent LOS on serial link (from fabric

plane [dec])

This error indicates a problem (Loss of

Sync) in the interface between the card
reporting error and the switch fabric card in
the indicated fabric plane. This error is
traffic affecting. Error recovery is triggered
by this error.

Persistent LOS on serial link (from fabric

plane [dec])

This error indicates a problem (Loss of

Sync) in the interface between the card
reporting error and the switch fabric card in
the indicated fabric plane. This error is
traffic affecting. Error recovery is triggered
by this error.

An earlier reported error (Loss of Sync) is

LOS cleared on serial link (from fabric plane now cleared. Normal operations can
[dec])
resume.
An earlier reported error (Loss of Sync) is
LOS cleared on serial link (from fabric plane now cleared. Normal operations can
[dec])
resume.

[chars] Multi destination unicast software

request error [hex]

An unexpected error has occurred. This

error typically means that a unicast data
packet was received by the fabric interface
ASIC to be forwarded across the switching
fabric with more than one destination slot.
The direction of the error and the slot are
indicated by the parameter in the
message.

Unexpected [chars] interrupt without halt

An unexpected error has occurred. This

error will trigger an error recovery
procedure & is traffic affecting. The
direction in which the error occurred is
specified as part of the meassage.

Error report timer wheel failure detected

An internal data structure was missing a

field. Some errors may not be reported to
the fabric control software. This error
indicates data corruption in internal
structures.

Error report timer wheel failure detected

An internal data structure was missing a

field. Some errors may not be reported to
the fabric control software. This error
indicates data corruption in internal
structures.

Forced timeout of an internal timer failed,

error [chars]

The library call failed. This indicates

internal data corruption on the LC. Certain
errors may not be reported to the fabric
control software. The error string as
returned by the library call is included in
the message.

Forced timeout of an internal timer failed,

error [chars]

The library call failed. This indicates

internal data corruption on the LC. Certain
errors may not be reported to the fabric
control software.

Unexpected error case

An unexpected error has occurred. This

error will trigger an error recovery and is
traffic affecting.

Unexpected error case

An unexpected error has occurred. This

error will trigger an error recovery and is
traffic affecting. An error other than the
CRC or LOS has occurred.

[chars] - ErrStr [chars]\n

FIA driver encountered an Error in

operation. The error string updates the
reason for this error.

[chars] -ErrStr [chars] [dec]\n

FIA driver encountered an Error in

operation. The error string updates the
reason for this error.

[chars] - ErrStr [chars] [chars] [dec]\n

FIA driver encountered an Error in

operation. The error string updates the
reason for this error.

[chars] -ErrStr [chars] [chars]\n

FIA driver encountered an Error in

operation. The error string updates the
reason for this error.

Error in [chars], slot:[dec] rc[[hex]]:[chars] FIA ENS lib has an access error

Init error in [chars], data:[hex] rc[[hex]]:

[chars]

FIA ENS client library initialization error

Error in [chars], data:[dec], handle[[hex]],

rc[[hex]]:[chars]

Fabric FIA ENS library producer error

[chars]: [chars] [hex]

This error usually indicates an internal

hardware problem on the card. A corrupted
packet was received from the Rx BMA, this
indicates communication bus between the
FIA and Rx BMA on the hardware datapath
may have signal integrity issues. This error
will trigger an error recovery. The LC may
not be able to forward data packets and
traffic loss may be observed due to this
error. If this error is seen due to manual
CSC switchover, this ios message can be
safely ignored and no action is needed.

[chars]: [chars] [hex]

This error usually indicates an internal

hardware problem on the card. The internal
parity error affects the communication bus
between adjacent ASICs on the hardware
datapath. The LC may not be able to
forward data packets and traffic loss may
be observed due to this error. The From
Fabric or To Fabric direction, the detailed
error string and the slot number are
provided as part of the message.

Failed to [chars] checkpoint record for a

device. Err : [chars]

The FIA driver encountered an error while

updating or accessing its checkpoint
information. Further high availability of the
driver may be impacted.

Failed to [chars] (despite connection to

SysDB being open). Err : [chars]

The FIA driver was unable to become an

external data manager (EDM) despite
having a connection to SysDB. The
operation will be retried.

Failed to register [chars] (despite

connection to SysDB being open). Err :
[chars]

The FIA driver was unable to become an

external data manager (EDM) despite
having a connection to SysDB. The
operation will be retried.

Warning: This is an unsupported SIP-600

card with lower revision Fabric Interface
ASIC

This warning indicates that this is an older

version of SIP-600 card which does not
have a supported Fabric Interface ASIC
(FIA). As a result, any CSC switch-over, RP
fail-over or fabric card OIR may result in FIA
ASIC errors, and the router may experience
abnormal behavior.

Driver has not discovered ASIC instance

[dec] yet [[chars]], retrying....

The FIA driver is polling for the device.

FIA-driver: Fabric isolate called: [chars] [chars]

FIA driver received an isolate request.

pcds_get_timestamp failed for fia stats

This is a message indicating FIA PCDS a

debugging information collection has faced
a problem in getting the time stamp to be
associated with the statistics collected.

pcds_get_timestamp failed for superfish

stats

This is a message indicating FIA PCDS a

debugging information collection has faced
a problem in getting the time stamp to be
associated with the statistics collected.

Failed to initialize checkpoint library. Err:

[chars], exiting...

The FIA driver failed to initialize the

checkpoint library. The System Manager
process (sysmgr) will automatically
respawn this process, up to a fixed number
of times the error is encountered, to
recover. If the problem continues, sysmgr
will trigger MSC reload. After a certain
number of MSC reloads, the shelf manager
will permanently shutdown the MSC.

Failed to register checkpoint table. Err:

[chars], exiting...

The FIA driver failed to register the

checkpoint table. The System Manager
process (sysmgr) will automatically
respawn this process, up to a fixed number
of times the error is encountered, to
recover. If the problem continues, sysmgr
will trigger MSC reload. After a certain
number of MSC reloads, the shelf manager
will permanently shutdown the MSC.

Failed to attach [chars] to event manager.

Err : [chars]. exiting...

The FIA driver was unable to attach the

indicated event / handler to the event
manager. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger MSC
reload. After a certain number of MSC
reloads, the shelf manager will
permanently shutdown the MSC.

Failed to attach an asynchronous [chars]

handler to event manager. Err : [chars].

The FIA driver was unable to attach the

indicated asynchronous handler to the
event manager. In case this is reported for
timer, driver may exit and the System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger MSC reload.
After a certain number of MSC reloads, the
shelf manager will permanently shutdown
the MSC.

Failed to create event manager for

'[chars]'. Err : [chars], exiting...

The FIA driver was unable to create an

event manager for processing messages
and hence failed to initialize. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger MSC reload.
After a certain number of MSC reloads, the
shelf manager will permanently shutdown
the MSC.

LWM Event Manager event block failed on

[chars] thread. Err : [chars]

The FIA driver LWM event manager has

failed to block on the indicated thread.

Failed to send LWM message reply to client. The FIA driver failed to send messaging
Err : [chars].
reply.

Failed to allocate [dec] bytes memory for

[chars]. exiting....

FIA driver memory allocation error. Memory

allocation failures will happen if the the
router runs out of memory or memory leak
in this process or other processes. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger MSC reload.
After a certain number of MSC reloads, the
shelf manager will permanently shutdown
the MSC.

Failed to [chars] SYSDB EDM datalist. Err :

[chars].

The FIA driver has failed to either create /

add a external data manager datalist.

Failed to open EDM event connection

manager: [chars], exiting...

The FIA driver to failed open the SysDB

EDM connection by binding to it and
registering using the event connection
manager. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger MSC
reload. After a certain number of MSC
reloads, the shelf manager will
permanently shutdown the MSC.

The FIA driver failed to create the specified

thread. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger MSC
reload. After a certain number of MSC
Failed to create [chars] thread. Err: [chars], reloads, the shelf manager will
exiting....
permanently shutdown the MSC.

fatal s/w error encountered - [chars],

[chars]

An unrecoverable fatal s/w error was

encountered, which results in severe board
malfunction. The exact cause is appended
to the error msg.

event manager create failed: [chars]

FSDB FADB encountered an error while

attempting to create an event manager for
process fsdb_fadb

nodeid_extract_fields failed: [chars]

FSDB FADB encountered an error while

attempting to extract info from node id in
process fsdb_fadb

platform_get_my_nodeid failed: [chars]

FSDB FADB encountered an error while

attempting to get node id in process
fsdb_fadb

respawn count get failed: [chars]

FSDB FADB encountered an error while

attempting to attach sync event handler for
process fsdb_fadb

sync event handler attach failed: [chars]

FSDB FADB encountered an error while

attempting to attach sync event handler for
process fsdb_fadb

sysdb bind failed: [chars]

FSDB FADB encountered an error while

attempting to bind to the rack endpoint to
get router inventory

sysdb list free failed: [chars]

FSDB FADB encountered an error while

attempting to free a list while getting the
sysdb inventory

Shared memory creation failed: [chars]

FSDB FADB encountered an error while

attempting to create the FADB shared
memory.

shm_open failed: [chars]

FSDB FADB encountered an error while

attempting to open the FADB shared
memory

FSDB FADB encountered an error while

[chars]: shared memory file truncate failed: attempting to truncate the FADB shared
[chars]
memory file

[chars]: shared memory mapping failed:

[chars]

FSDB FADB encountered an error while

attempting to map the FADB shared
memory

Rack is brought down if RPs on the rack are

detected stalling on fabric barriers. If the
rack is isolated from fabric via CLI, then
Rack [dec] reloading due to fabric barrier
this is expected. If this message occurs
stall on the rack. Fabric shutdown log saved otherwise, it could be due to a software
in file [chars].
error or an unexpected hw error.

Router is brought down if RPs on the dsc

rack are detected stalling on fabric
barriers. If the dsc rack is isolated from
fabric via CLI, then this is expected. If this
message occurs otherwise, it could be due
Router reloading due to fabric barrier stall. to a software error or an unexpeced hw
Fabric shutdown log saved in file [chars].
error.

[chars] reloading due to loss of fabric

connectivity

A line-card is reloading after detecting that

it has totally lost connectivity to the fabric.
If all the fabric boards are OIR'ed or
brought down through CLI, this is expected.
If this message occurs otherwise, it could
be due to a software error.

The fabric plane configuration for this

multi-chassis system cannot be
implemented with the hardware that has
been discovered. This error may cause one
or more fabric planes to stay down which
will affect the bringup of the rest of the
system. Possible causes could be incorrect
admin plane configuration (ie the
configuration states that slot 1 is the first
Fabric hardware found at location [chars] is card in a plane whereas slot 0 really is) or
inconsistent with current configured
an incorrectly sized fiber module is inserted
values : [chars]
in a slot.

Fabric admin config [chars]

If the admin startup config is not received,

then the fabric planes cannot be configured
and brought up. If the fabric is not UP,
system cannot be used for any data traffic.

Fabric [chars] for data traffic

If the fabric is reported down, it means that

none of the fabric planes are UP. If the
fabric is not UP, system cannot be used for
any data traffic.

Plane [dec] state changed to [chars]%s;

[chars]

If the plane is reported down other than

when administratively brought down, it
means that the sprayer cannot reach *any*
destination on the plane. This is a symptom
of too many other fabric errors
(DESTINATION_UPDOWN) than an error
itself. The plane can no longer be used to
send any traffic. If the plane is reported
mcast_down, it means that certain fabric
destinations are not reachable on this
plane.It is still good for unicast traffic, but
for destinations which are reachable on this
plane.

[chars], Error - [chars]

This is to indicate that the process has

failed to connect or send message to the
fabric management process to get
information on Max. groups per rack.

Rack [dec] sent illegal fabric control

message. Error : [chars]

Fabric control software running in another

rack has notified a status change that is
impossible or illegal.

Plane [dec] is reported to be defective.

Unable to shut down the plane: [chars]

This indicates that fsdb aserver process

has received the request to shut down a
fault plane. The plane is not shut down by
the fsdb aserver due to the reason
mentioned.

Cannot connect to fabric management

process to report plane [dec] defective

This is to indicate that the process has

failed to connect to the fabric management
process to report that the plane is
defective.

This is to indicate that the process has

failed to send an IPC message to the fabric
Cannot send report of plane [dec] defective management process that the plane is
to the fabric management process
defective.

Fabric rack [dec] went down!!!

This message indicates fabric rack is been

removed.

FSDB AIPC ERR FOR CLIENT PID: [dec].

Error: [chars]

Error occured during the use of FSDB AIPC

Client for the given process id(name).

Fabric control software failed to

synchronize configuration details between
the fsdb_server and fsdb_aserver
processes. If the affected rack is being
added to the system it cannot be brought
into service. If the affected rack is already
Fabric configuration download [chars]. Error in service, then it cannot respond to fabric
: [chars]
failures or changes.

Fabric driver(FSDB) encountered invalid

ASIC reset Reset type: [dec], Name:
[chars], Status: [dec]

Error occured during fabric driver asic

status change. Its equivalent to sending
OPER_DOWN for an asic and each of its link
ports.

System failed to read rommon variable

[chars]

Fabric Status Database server (FSDB) failed

to read a rommon variable.

[chars] in bundle [chars] on plane [dec]

This is to indicate that the no. of down links

in a bundle has changed from zero to nonzero or vice versa.

Bundle [chars] on plane [dec] is [chars]

Bundle state has changed. This can be

because the state of one of the bundle
ports comprising the bundle has changed.
A bundle port is considered down if all the
links comprising the bundle port go down.

Failed to register checkpoint record:

[chars]. Exiting...

FSDB server encountered an error while

updating or accessing its checkpoint
information. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
respective RP/SC switchover.

Failed to initialize check point library:

[chars]. Exiting...

FSDB was unable to setup the

checkpointing facility to offer high
availability functionality. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger respective
RP/SC switchover.

Failed to setup the debugging services:

[chars]. Exiting...

FSDB was unable to initialize the

debugging services. The System Manager
process (sysmgr) will automatically
respawn this process, up to a fixed number
of times the error is encountered, to
recover. If the problem continues, sysmgr
will trigger respective RP/SC switchover.

FSDB Server: DSC Error [[chars]]. Error :

[chars]

Fabric Status Database server (FSDB) failed

to communicate with the DSC server. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger respective
RP/SC switchover.

Failed to create the event connection

manager for [chars]. Error : [chars].
Exiting...

FSDB encountered an error while

attempting to create an event connection
manager for the specified path. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger respective
RP/SC switchover.

FSDB encountered an error while

attempting to install an ECM notification
handler for the specified path. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
Failed to install ECM notification hanlder for continues, sysmgr will trigger respective
[chars] path: [chars]. Exiting...
RP/SC switchover.

Failed to create the event manager:

[chars]. Exiting...

FSDB encountered an error while

attempting to create an event manager.
The System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger respective
RP/SC switchover.

FSDB Server: Failed to [chars]. Error :

[chars]

FSDB server failed to obtain either its node

ID or extract rack/slot/instance information
(having obtained the node ID). The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger respective
RP/SC switchover.

FSDB Server detected an internal error

[chars]. Error : [chars]

An internal error occurred that was

expected to succeed.

Parse error in fabric definition file [chars],

line [dec]

A file describing switch fabric components

has errors. Some fabric components cannot
be brought into service.

Restarting to recover from resync timeout

During the deferral window, fsdb_server

didnt hear from a driver or rack due to
some connection/transport issue.
Restarting fsdb_server will try to recover it.

When FSDB starts up it attempts to

resynchronise the state with all current
entities. This message indicates that one or
more of these entities has not responded
within the timeout period. This could lead
to FSDB having an inconsistent view of the
Timeout during initial synchronization with fabric, and can potentially cause traffic
[chars]
loss.

Sysdb unable to [chars]. Error : [chars]

FSDB encountered a Sysdb communication

failure. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
respective RP/SC switchover.

FSDB failed to open a connection to the

Sysdb Server process for one of the paths.
The System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
Connection to the sysdb server failed. Error continues, sysmgr will trigger respective
: [chars]
RP/SC switchover.

FSDB Server: Failed generating [chars]

notification. Error : [chars]

FSDB external data manager failed to

generate a trap notification. Process would
continue to run normally.

Failed to register as an EDM for [chars].

Error : [chars], exiting...

The FSDB was unable to become an

external data manager (EDM) for the
specified path. The System Manager
process (sysmgr) will automatically
respawn this process, up to a fixed number
of times the error is encountered, to
recover. If the problem continues, sysmgr
will trigger respective RP/SC switchover.

FSDB external data manager failed to

register for notifications for the specified
FSDB Server: Failed to register notification path. Process would continue to run
for [chars] path. Error : [chars]. SNMP traps normally, except that SNMP traps will not
will not be generated for this path
be generated for changes in fabric state.

Cannot find fabric definition file [chars]

A file describing switch fabric components

is not present on the router.

Fabric driver(FSDB) recieved invalid handle

Handle name: [chars], Status: [dec]
Error occured during fabric driver handler.

Error occured while getting start address

Fabric error, Node : [dec] is out of IngressQ for bar_Crab/Sponge/Crab instance 0 given
HW entries in chassi: [dec]
node ID.

Unable to open [chars] after [dec] retries

Fabric Status Database server (FSDB) failed

to open a rommon file.

Rack num:[dec] is > max rack num that

can be run in back-to-back mode

Back-to-back mode is only supported

between chassis with rack nums 0 and 1

Node ([chars]) is not reachable on plane

[dec]

This is to indicate that a node has lost

connectivity to a plane. Most likely, back
plane connectivity between the node and
the fabric card has failed.

Fabric LED internal software error occurred.

It is possible to continue operation,
although some LEDs on fabric led board
may incorrectly illuminate. However, if this
functionality is necessary then restart the
process by issuing the following command
at the CLI of the active RP after collecting
all the output of all the specified
[chars] : [chars], LED(Row [dec], col [dec]), commands. 'admin process restart
corresponding to node [dec]
fsdb_server loc <loc>' *SUPPORT*

FSDB Server detected a minor internal

error [chars]. Error : [chars]

FSDB encountered a minor internal

software error. It is possible that fabric
operates normally without any issues.

FSDB encountered an error while

attempting to signal a thread conditionally.
The operation related to the resource will
Failed thread conditional signal on [chars]. be affected and the process will continue to
Error : [chars].
run normally.

Failed thread conditional wait on [chars].

Error : [chars].

FSDB encountered an error while

attempting to wait conditionally on a
thread. The operation related to the
resource will be affected and the process
will continue to run normally.

Failed to lock [chars] mutex : [chars].

FSDB encountered an error while locking a

mutex to access the specified shared
resource. The operation related to the
resource may be affected while the process
continues to run normally.

Failed to unlock [chars] mutex : [chars].

FSDB encountered an error while locking

unlocking a mutex to access the specified
shared resource. The operation related to
the resource may be affected while the
process continues to run normally.

The fabric card [chars] cannot run in back

to back mode

This indicates that the fabric card in the

mentioned slot is incompatible with the
admin configs done for the plane
participated by this card

In a CRS-16 system, at least one odd plane

and at least one even plane is required. In
It is advisable to have [chars] to be up.
others, at least one plane is required. If all
Shutting down all the planes will leave the the planes are shutdown, the router goes
router in unrecoverable state.
into an unrecoverable state.

FSDB Aserver: System will boot without

waiting for fabric to be up

System is booting up without waiting for

fabric to be up.

This message gives additional information

related to a plane in multicast-down state.
It reports the number of operating fabric
links from the plane to the destination. The
threshold reported is the number of fabric
Fabric address [dec] unreachable on plane links that are required for the destination to
[dec]. [dec] links up. Threshold [dec]
be considered reachable.

Disabled fabric traffic from group [dec] of

rack [dec] in plane [dec]. [dec] links up.
Threshold [dec]

This message gives additional information

related to a plane in multicast-down state.
It reports that a group of fabric cards are
unable to send traffic to any destination.
For CRS-1 16-slot chassis, group 0 is the
upper shelf containing line cards 0 to 7.
Group 1 is the lower shelf containing line
cards 8 to 15 and both RPs The message
reports the number of operating data links
from the specified group to the fabric plane
that are operating. The reported threshold
is the number of data links that should be
operating in order to make the fabric group
usable.

All fabric addresses in group [dec] of rack

[dec] unreachable on plane [dec]. [dec]
links up. Threshold [dec]

This message gives additional information

related to a plane in multicast-down state.
It reports that a group of fabric addresses
have become unreachable. For CRS-1 16slot chassis, group 0 is the upper shelf
containing line cards 0 to 7. Group 1 is the
lower shelf containing line cards 8 to 15
and both RPs. The message reports the
number of data links that are operating
from the fabric plane to the specified
group. The threshold is the number of data
links that should be operating in order to
make the fabric group reachable.

Plane [dec] reported in multicast-down

state by rack(s)[chars]

This message gives additional information

related to a plane in multicast-down state.
The message contains a comma-separated
list of the line card racks that reported the
multicast-down state.

Failed to allocate memory.

FSDB has failed to allocate memory for its

resources. This would affect proper
functioning of fabric.

FSDB Server: SYSDB Bag encode[[chars]].

Error : [chars]

FSDB server encountered error in sysdb

bag encode operation. This could affect
output of some of the fabric CLI
commands.

Bag register error is detected; [chars].

Fabric statistics aggregator process

encountered an error to register the bag to
bag infrastructure that is useful for
packaging up complex data into single
SysDB items. This software error will cause
process termination for recovery The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover.

Failed to clear fabric statistics for plane

[dec], err: [chars]

Fabric Plane Statistics CLI encountered an

error in trying to clear the fabric plane
statistics as a result of sysdb call failure.
This software error will cause the following
fabric plane statistics getting appended to
the previous ones. No other system
functionality will get affected due to this.

Failed to clear fabric statistics for all

planes, err: [chars]

Fabric Plane Statistics CLI encountered an

error in trying to clear the fabric plane
statistics as a result of sysdb call failure.
This software error will cause the following
fabric plane statistics getting appended to
the previous ones. No other system
functionality will get affected due to this.

Debug initialization for the

fstats/aggregator/[chars] event failed, err:
[chars]

Fabric statistics aggregator process

encountered an error to initialize debug
facility and hence failed to initialize. This
software error will cause process
termination for recovery. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Debug registration for fabric statistics

aggregator failed, err: [chars]

Fabric statistics aggregator process

encountered an error to register debug
facility and hence failed to initialize. This
software error will cause process
termination for recovery. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Failed to create event manager; [chars]

Fabric statistics aggregator process

encountered a fatal error to create its
event manager for receiving events. This
software error will cause process
termination for recovery. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Fabric statistics aggregator process

encountered an error to create group for
GSP communication. This software error
will cause process termination to recover.
The System Manager process (sysmgr) will
automatically respawn this process, up to a
GSP group [chars] creation/join was failed. fixed number of times the error is
err: [chars].
encountered, to recover.

Internal software error: [chars][[chars]]

Fabric statistics aggregator process

encountered an internal software error.
(e.g., timer service error or system call
errors) This software error will cause
process termination to recover. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. *RECUR*

Fabric statistics aggregator process

encountered an error to bind to admin
plane sysdb server. This software error will
cause process termination for recovery. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
Can't bind to SysDB at [chars], err: [chars] encountered, to recover.

Failed to register SysDB EDM [chars], err:

[chars]

Fabric statistics aggregator process

encountered an error to register EDM to
admin plane sysdb server. This software
error will cause process termination for
recovery. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover.

Failed to report process ready to sysmgr,

err: [chars]

Fabric statistics aggregator process

encountered an error to report process
ready to sysmgr. This software error will
cause process termination for recovery. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover.

Fabric statistics client library encountered

GSP group [chars] creation/join was failed; an error while creating group for GSP group
[chars].
communication.

Debug cleanup for fabric statistics client

library failed. err: [chars]

Fabric statistics client library encountered

debug facility clean up failure.

Debug initialization for the fstats/client/

[chars] event failed. err: [chars]

Fabric statistics client library encountered

debug facility initialization failure. When
this error happens, the library will not able
to enable debug.

Debug registration for fabric statistics

client library failed, err: [chars]

Fabric statistics client library encountered

debug facility registration failure. When
this error happens, the library will not able
to enable debug.

GSP lightweight group [chars] lookup was

failed; [chars].

Fabric statistics client library encountered

failure when it looks up Fabric server light
weight group for light weight group
communication. Normally, this is a
transient error. It can be a true error if the
error is persistent.

Bag register error is detected; [chars].

Fabric statistics server process encountered

an error to register the bag to bag
infrastructure that is useful for packaging
up complex data into single SysDB items.
This software error will cause process
termination for recovery The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Debug initialization for the fstats/server/

[chars] event failed; [chars]

Fabric statistics server process encountered

an error to initialize debug facility and
hence failed to initialize. This software error
will cause process termination for recovery.
The System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Debug registration for fabric statistics

server failed; [chars]

Fabric statistics server process encountered

an error while registering debug facility and
hence failed to initialize. This software error
will cause process termination for recovery.
The System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Failed to create event manager; [chars]

Fabric statistics server process encountered

an error to create its event manager for
receiving events. This software error will
cause process termination for recovery. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Fabric statistics server process encountered

an error while creating group for GSP
communication. This software error will
cause process termination to recover. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
GSP group [chars] creation/join was failed. shelf manager will permanently shutdown
err: [chars].
the node.

Internal software error: [chars] [[chars]]

Fabric statistics server process encountered

an internal software error. (e.g., timer
service error or system call errors) This
software error will cause process
termination to recover. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Could not allocate memory for [chars].

Fabric statistics server process encountered

memory allocation error for creating
statistics database or storing statistics
data. This software error will cause process
termination to recover during process
initialization. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

Fabric statistics server process encountered

an error to bind to admin plane sysdb
server. This software error will cause
process termination for recovery. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
Can't bind to SysDB at [chars] due to error: shelf manager will permanently shutdown
[chars]
the node.

Failed to register SysDB EDM [chars]; err:

[chars]

Fabric statistics server process encountered

an error to register EDM to admin plane
sysdb server. This software error will cause
process termination for recovery. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Failed to report process ready to sysmgr;

[chars]

Fabric statistics server process encountered

an error while reporting process ready to
sysmgr. This software error will cause
process termination for recovery. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

[chars]: fabric resource registration error

due to inconsistent value.

Fabric statistics server process encountered

a transient error due to the inconsistent
value of the received message. This error
message will be a true error if many error
message is logged and the error is
persistent.

ltrace initialization operation failed for error The FSDB FADB ltrace lib failed to initialize
traces: [chars]
the error ltrace

ltrace initialization operation failed for

events: [chars]

The FSDB FADB ltrace lib failed to initialize

the events ltrace

ltrace initialization operation failed for

internal traces: [chars]

The FSDB FADB ltrace lib failed to initialize

the internal ltrace

INGRESSQ: device halted, sub-block:

[chars], halted entity: [chars]

INGRESSQ, ASIC got halted. The halted

block and its parent block are provided

BRM BlocK: Barrier sync up failed for this

node.

There might be a fabric disconnect in the

system.

BRM BlocK: Barrier sync up failed for this

node.

There might be a fabric disconnect in the

system.

Ingressq encountered a device error :

[chars]

Ingressq encountered a device error that

has exceeded its threshold value. Driver
takes appropriate action to log and fix the
error which may include a device reset.

[chars]

Ingressq encountered a device error that

has exceeded its threshold value. Driver
takes appropriate action to log and fix the
error which may include a device reset.

Error during [chars] BIST

BIST failed for the mentioned block. The

driver should trigger a device reset to fix
this error.

Error during [chars] BIST

BIST failed for the mentioned block. The

driver should trigger a device reset to fix
this error.

[chars]

The Ingressq driver failed to initialize the

device resulting in the restart of the
Ingressq driver process.

Error during initialization : [chars]

The Ingressq driver failed to initialize the

device resulting in the restart of the
Ingressq driver process.

[chars] Error: [chars]

Ingressq Driver encountered an error

during access to the ASIC. The error may
have been caused because of expected or
unexpected software and hardware errors.
In case, the error is a hardware error,
Ingressq driver will reset the ASIC to
recover.

[chars] Error: [chars]

Ingressq Driver encountered an error

during access to the ASIC. The error may
have been caused because expected or
unexpected software and hardware errors.
In case, the error is a hardware error,
Ingressq driver will reset the ASIC to
recover.

Message : [chars]

Ingressq Driver encountered an error

during imdr event. This may have been
caused because expected or unexpected
software and hardware errors. In any case,
imdr on the line card will be aborted.

[chars] fatal error

--

Taking the node down, Reason: [chars]

Ingressq DLL encountered an fatal error

mentioned above. The driver triggers MSC
node-down to recover from the error.

Taking the node down, Reason: [chars]

Ingressq DLL encountered an fatal error

mentioned above. The driver triggers MSC
node-down to recover from the error.

EIO link training threshold exceeded, link:

[dec]

An attempt to train the EIO links to the

neighboring Asic have failed. The ingressq
driver retries the eio link training. If this
error is seen repeatedly, please contact
TAC support.

Taking the node down, Reason: [chars]

Ingressq DLL encountered an fatal error

mentioned above. The driver triggers MSC
node-down to recover from the error.

Barrier sync up failed for this node. Last

sync state = [dec]

This may be a transient error seen if fabric

components are powered down incorrectly.
The system should recover from this error
automatically. If the error persists, please
contact TAC support.

Assert Error valid: [dec], block: [dec],

debug_info: [dec]

Ingressq encountered an assert error in the

FCRAM. The driver triggers a device reset.
The device should be reinitialized.

Multiple Bit Error in Block: [chars] Error:

[chars] at Memory Address [hex].

Ingressq encountered a multiple bit error in

the mentioned block. This error is an
uncorrectable error. Driver takes
appropriate action to log and fix the error
which may include a device reset.

Error during BIST operation: [chars]

BIST failed for the mentioned block. The

driver should trigger a device reset to fix
this error.

Initialization Failed. Err : [chars]

The Ingressq driver failed to initialize the

device resulting in the restart of the
Ingressq driver process.

Error Allocating memory for <[chars]>

The Ingressq dll Memory Allocation Error

message.

Error Allocating memory for <[chars]>

The Ingressq dll Memory Allocation Error

message.

Error Allocating memory for <[chars]>

Ingressq encountered a fatal memory

allocation error. If a new configuration
being applied, the configuration will be
rejected. The user may reapply the
configuration. If the error happens normal
operation, the process will restart to
recover from this error.

[chars] Resetting IQM ASIC Device with halt

status [hex] due to [chars]
Ingressq Seal ASIC error halt occur.

[chars] Resetting IQM ASIC Device with halt

status [hex] due to [chars]
Ingressq Seal ASIC error halt occur.

Resetting IQM ASIC Device

Ingressq, cpuctrl net interface encountered

a CRC/Sync Error. This will result in the PIO
or CDMA failure.

Sequencer state: [dec], reason: [chars] :

[chars], #retries: [dec]

Ingressq driver state machine encountered

a failure in initializing the device above
threshold number of times. Driver will
continue to initialize the device. If the error
persists, please contact TAC support.

Sequencer state: [dec], reason: [chars] :

[chars], #retries: [dec]

Ingressq driver state machine encountered

a failure in initializing the device above
threshold number of times. Driver will
continue to initialize the device.

Sequencer state: [dec], reason: [chars] :

[chars], #retries: [dec]

Ingressq driver state machine encountered

a failure in initializing the device above
threshold number of times. Driver will
continue to initialize the device.

Exiting. sequencer state: [dec], reason:

[chars] : [chars]

Ingressq driver state machine encountered

an unrecoverable error. This will result in
driver restart.

Exiting. sequencer state: [dec], reason:

[chars] : [chars]

Ingressq driver state machine encountered

an unrecoverable error. This will result in
driver restart.

Sequencer state: [dec], reason: [chars] :

[chars]

Ingressq driver state machine encountered

an error.Driver will continue to retry.

shm init for pla failed, retried [dec] times

Initialization of shared memory for PLA has

failed for atleast 10 times. This happens
when there is failure in creating POSIX
shared memory object.

Destination [chars] (fabric destination

[dec]) card type is unknown. Disabling
traffic to it.

Fabric Destination card type is invalid

although the plane is available. Traffic is
being disabled to this. This might happen if
the destination is down or has been
removed.

Spiller Seg blk is hung, reseting spiller pkt_fifo [hex], ctrl_fifo [hex], icf_fifo [hex]

Watchdog detected that spiller seg block is

hung, reseting spiller to recover

Seal Seg blk is hung, reseting seal - pkt_fifo Watchdog detected that Seal seg block is
[hex], ctrl_fifo [hex], icf_fifo [hex]
hung, reseting spiller to recover

Seal Seg blk is hung, reseting seal - pkt_fifo

[hex], ctrl_fifo [hex], icf_fifo [hex]
--

BRM aggr delta, spo link: [dec], cast: [dec], There might be a fabric disconnect in the
threshold: [unsigned long int]
system.

BRM aggr delta, egress link: [dec], cast:

[dec], threshold: [unsigned long int]

There might be a fabric disconnect in the

system.

BRM aggr delta, egress link: [dec], cast:

[dec], threshold: [unsigned long int]

There might be a fabric disconnect in the

system.

BRM delta threshold, spo link: [dec], cast:

[dec], threshold: [unsigned long int]

There might be a fabric disconnect in the

system.

BRM delta threshold, egress link: [dec],

cast: [dec], threshold: [unsigned long int]

There might be a fabric disconnect in the

system.

BRM delta threshold, egress link: [dec],

cast: [dec], threshold: [unsigned long int]

There might be a fabric disconnect in the

system.

BRM double in delta culprit, egress link:

[dec], cast: [dec]

There might be a fabric disconnect in the

system.

BRM double in delta culprit, spo link: [dec], There might be a fabric disconnect in the
cast: [dec]
system.

BRM double in delta culprit, egress link:

[dec], cast: [dec]

There might be a fabric disconnect in the

system.

BRM invalid input; egress: [dec], cast:

There might be a fabric disconnect in the
[dec], current_barr: [hex] input_barr: [hex] system.

BRM invalid input; egress: [dec], cast:

There might be a fabric disconnect in the
[dec], current_barr: [hex] input_barr: [hex] system.

BRM invalid input; spo: [dec], cast: [dec],

current_barr: [hex] input_barr: [hex]

There might be a fabric disconnect in the

system.

BRM, phase didn't change, spo link: [dec],

cast: [dec], phase: [hex], phase to counter: Barrier Manager encountered a phase
[hex], phase to thr: [hex]
change error.

BRM, phase didn't change, egress link:

[dec], cast: [dec], phase: [hex], phase to
counter: [hex], phase to thr: [hex]

Barrier Manager encountered a phase

change error.

BRM, phase didn't change, egress link:

[dec], cast: [dec], phase: [hex], phase to
counter: [hex], phase to thr: [hex]

Barrier Manager encountered a phase

change error.

CpuCtrl driver was not able to complete the

CDMA request for the above specified
address location. This may be caused if the
CpuCtrl error, addr:([hex],[hex]), dir: [dec], device is not initialized correctly or
rc: [dec]
synchronized correctly.

CpuCtrl driver was not able to complete the

CDMA request for the above specified
address location. This may be caused if the
CpuCtrl error, addr:([hex],[hex]), dir: [dec], device is not initialized correctly or
rc: [dec]
synchronized correctly.

CpuCtrl driver was not able to complete the

CDMA request for the above specified
address location. This may be caused if the
CpuCtrl error, addr:([hex],[hex]), dir: [dec], device is not initialized correctly or
rc: [dec]
synchronized correctly.

Ingressq buildup queue(s). [chars]

Ingressq has various queues that are used

by Ingress ASICs to send specific stream of
traffic. These queues are specifically
configured before they are used to forward
traffic. Ingressq recived a few packets in
queues that were misconfigured or not
configured at all. The driver will
automatically try to recover from the
condition.

CRC Error: Block:[chars] Error:[chars]

Count: [dec]

Ingressq block received a packet with a

CRC error. It is primarily caused by either
the link errors between the devices or
packet corruption in the upstream asic.
This error may cause performance
degradation.

CRC Error: Block:[chars] Error:[chars]

Count: [dec]

Ingressq block received a packet with a

CRC error. It is primarily caused by either
the link errors between the devices or
packet corruption in the upstream asic.
This error may cause performance
degradation.

CRC Error: Block:[chars] Error:[chars]

Count: [dec]

Ingressq block received a packet with a

CRC error. It is primarily caused by either
the link errors between the devices or
packet corruption in the upstream asic.
This error may cause performance
degradation.

Block: [chars] encountered error: [chars]. It Ingressq received a packet with

received a packet with SOP/EOP/MAC
SOP/EOP/MAC error It is primarily caused
error(s)
by either software or mac issue.

Ingressq received a packet with incorrect

length either from cpuctrl or Ingress PSE. It
Block: [chars] encountered error: [chars]. It is primarily caused by either the link errors
received a packet with length error(s),
between the devices or packet corruption
expected: [dec], received: [dec]
in the upstream asic.

Ingressq received a packet with incorrect

length either from cpuctrl or Ingress PSE. It
Block: [chars] encountered error: [chars]. It is primarily caused by either the link errors
received a packet with length error(s),
between the devices or packet corruption
expected: [dec], received: [dec]
in the upstream asic.

Ingressq received a packet with incorrect

length either from cpuctrl or Ingress PSE. It
Block: [chars] encountered error: [chars]. It is primarily caused by either the link errors
received a packet with length error(s),
between the devices or packet corruption
expected: [dec], received: [dec]
in the upstream asic.

CpuCtrl Interface RxFIFO Error: [chars]

Ingressq, cpuctrl net interface Rx FIFO last

sync.

CpuCtrl Interface RxFIFO Error: [chars]

Ingressq, cpuctrl net interface Rx FIFO last

sync.

CpuCtrl Interface RxFIFO Error: [chars]

Ingressq, cpuctrl net interface Rx FIFO last

sync.

Error encountered during Checkpoint

Initialization

Ingressq Checkpoint Init error

Error encountered during Checkpoint

Initialization

Ingressq Checkpoint Init error

Error encountered during Checkpoint

Initialization

Ingressq Checkpoint Init error

Error encountered during [chars]

Checkpoint Insertion

Ingressq Checkpoint Insert error

Error encountered during [chars]

Checkpoint Insertion

Ingressq Checkpoint Insert error

Error encountered during [chars]

Checkpoint Insertion

Ingressq Checkpoint Insert error

Error : [chars]

Ingressq driver monitors the ASIC every 5

seconds to look for any problems. If an
error is reported momentarily, it could be a
false positive seen during a transient state,
or during oversubscription. In case, the
error is seen repeatedly, please contact
TAC support.

Interrupt enable at addr: [hex] mask: [hex]

failed.
Hardware state is not correct.

Interrupt enable at addr: [hex] mask: [hex]

failed.
Hardware state is not correct.

Interrupt enable at addr: [hex] mask: [hex]

failed.
Hardware state is not correct.

control cell fifo overflow error

Ingressq LNS control cell fifo overflow.

control cell fifo overflow error

Ingressq LNS control cell fifo overflow.

control cell fifo overflow error

Ingressq LNS control cell fifo overflow.

Ingressq dropped a few cells because of

unavailability of enough planes to forward
the cells to its destination. If the cells are
dropped intermittently during system
reconfiguration (LC reload, RP fail over,
etc), then these drops are expected.
System will recover after the hardware
reprogramming completes. If these drops
are seen continuously for long periods,
Error: Cells dropped due to low availability then this indicates that either the node is
of planes, aggr cell drop count: [unsigned not programmed correctly, or there is an
long long int]
error in data plane software.

Ingressq dropped a few cells because of

unavailability of enough planes to forward
the cells to its destination. If the cells are
dropped intermittently during system
reconfiguration (LC reload, RP fail over,
etc), then these drops are expected.
System will recover after the hardware
reprogramming completes. If these drops
are seen continuously for long periods,
Error: Cells dropped due to low availability then this indicates that either the node is
of planes, aggr cell drop count: [unsigned not programmed correctly, or there is an
long long int]
error in data plane software.

Ingressq dropped a few cells because of

unavailability of enough planes to forward
the cells to its destination. If the cells are
dropped intermittently during system
reconfiguration (LC reload, RP fail over,
etc), then these drops are expected.
System will recover after the hardware
reprogramming completes. If these drops
are seen continuously for long periods,
Error: Cells dropped due to low availability then this indicates that either the node is
of planes, aggr cell drop count: [unsigned not programmed correctly, or there is an
long long int]
error in data plane software.

parity error in plane RA, name: [chars],

link: [dec], RA: [dec], Addr: [dec]

Ingressq, cpuctrl net interface Rx FIFO last

sync. Driver may reset the ASIC to recover.

parity error in plane RA, name: [chars],

link: [dec], RA: [dec], Addr: [dec]

Ingressq, cpuctrl net interface Rx FIFO last

sync.

parity error in plane RA, name: [chars],

link: [dec], RA: [dec], Addr: [dec]

Ingressq, cpuctrl net interface Rx FIFO last

sync.

Block: [chars], entity: [chars] had parity

error(s), addr: [dec], parity: [dec]

In the specified block a parity error

encountered at mentioned addr offset. If
the error exceeds its threshold, the driver
trigger a corrective action which may
include device reset or MSC reload.

Block: [chars], entity: [chars] had parity

error(s), addr: [dec], parity: [dec]

In the specified block a parity error

encountered at mentioned addr offset. If
the error exceeds its threshold, the driver
trigger a corrective action which may
include device reset or MSC reload.

Block: [chars], entity: [chars] had parity

error(s), addr: [dec], parity: [dec]

In the specified block a parity error

encountered at mentioned addr offset. If
the error exceeds its threshold, the driver
trigger a corrective action which may
include device reset or MSC reload.

Single Bit Error in Block: [chars] Error:

[chars] at Memory Address: [hex]

Ingressq encountered a single bit error in

the mentioned block. Persistent errors are
corrected by the software. Non-persistent
errors are automatically corrected by the
next write operation.

Barrier synced up on this node.

This message indicates that system

barriers synced on this node. This message
is expected during normal operation.

Block: [chars], Generic Error [chars] at

Memory Address [hex].

Ingressq encountered a device error that

has exceeded its threshold value. Driver
takes appropriate action to log and fix the
error which may include a device reset.

Block: [chars], entity: [chars] had Out Of

Resources error(s), count: [dec]

Ingressq block is unable to get packet

memory for the incoming packets. This
condition is caused by over subscription or
hitting the Packet Per Second rate. This will
affect the QOS. Thus it is recommended to
reduce the packet rate to this MSC.

Block: [chars], entity: [chars] had Out Of

Resources error(s), count: [dec]

Ingressq block is unable to get packet

memory for the incoming packets. This
condition is caused by over subscription or
hitting the Packet Per Second rate. This will
affect the QOS. Thus it is recommended to
reduce the packet rate to this MSC.

Block: [chars], entity: [chars] had Out Of

Resources error(s), count: [dec]

Ingressq block is unable to get packet

memory for the incoming packets. This
condition is caused by over subscription or
hitting the Packet Per Second rate. This will
affect the QOS. Thus it is recommended to
reduce the packet rate to this MSC.

Ingressq ASIC has 32 TX links into the

Ingressq links to plane(s) [chars] could not fabric planes. This message lists the fabric
be brought up. Please check the connected planes that cannot be used by the Ingressq
planes
ASIC for data traffic.

Message : [chars]

Ingressq driver monitors the ASIC every 5

seconds to look for any
problems/inconsistencies. If an error is
reported momentarily, it could be a false
positive seen during a transient state, or
during oversubscription. Driver may trigger
a corrective action which may include
process restart or MSC node-down to
recover from the error.

[chars]

Ingressq driver monitors the ASIC every 5

seconds to look for any
problems/inconsistencies. If an error is
reported momentarily, it could be a false
positive seen during a transient state, or
during oversubscription. In case, the error
is seen repeatedly, please contact TAC
support.

[chars]

Just info

Info : [chars]

Just for information. Message is self

explanatory.

sequencer state: [dec], threshold: [dec],

reason: [chars], #retries: [dec]

Ingressq sequencer state threshold

exceeded. Driver will wait for operation and
retry.

sequencer state: [dec], threshold: [dec],

reason: [chars], #retries: [dec]

Ingressq sequencer state threshold

exceeded.

sequencer state: [dec], threshold: [dec],

reason: [chars] [chars], #retries: [dec]

Ingressq sequencer state threshold

exceeded.

[chars]: barrier stall cleared.

Ingressq, Barrier stall cleared on one of the

casts

[chars]: barrier stall cleared.

Ingressq, Barrier stall cleared on one of the

casts

[chars]: barrier stall cleared.

Ingressq, Barrier stall cleared on one of the

casts

[chars]: barrier stalled.

Ingressq, Barrier stalled on one of the casts

[chars]: barrier stalled.

This may be a transient error seen if fabric

components are powered down incorrectly.
The system should recover from this error
automatically. If the error persists, please
contact

[chars]: barrier stalled.

Ingressq, Barrier stalled on one of the casts

Register get failed for address [hex],

Reason: [chars]

An attempt to read a Hardware register

failed. This could result in inconsistent
behavior of the device.

Register get failed for address [hex],

Reason: [chars]

An attempt to read a Hardware register

failed. This could result in inconsistent
behavior of the device.

Register get failed for address [hex],

Reason: [chars]

An attempt to read a Hardware register

failed. This could result in inconsistent
behavior of the device.

Register set failed for address [hex],

Reason: [chars]

An attempt to write a Hardware register

failed.

Register set failed for address [hex],

Reason: [chars]

An attempt to write a Hardware register

failed.

Error during Resource Programming:

[chars] Reason: [chars]

Ingressq encountered an error during

resource programming. If there are no
further attempts to reprogram the device,
the device behavior may be inconsistent.

Error during Resource Programming:

[chars] Reason: [chars]

Ingressq encountered an error during

resource programming. If there are no
further attempts to reprogram the device,
the device behavior may be inconsistent.

Error during Resource Programming:

[chars] Reason: [chars]

Ingressq encountered an error during

resource programming. If there are no
further attempts to reprogram the device,
the device behavior may be inconsistent.

Ingressq Lib: LWM Message send failed

msg: [dec], retried: [dec] time(s), errno:
[chars]

Unable to send a LWM message to the

Ingressq server.

Ingressq: Error encountered during

Ingressq ASIC [dec] reset.

Ingressq ASIC is reset before the MSC is

powered down. If this reset fails, the fabric
ASICs might complain of barrier errors.
These errors should be transient, and the
system will recover from it. In case, the
errors aren't transient, please contact TAC
support

Driver encountered an error,

reason=[chars]

The Ingressq driver failed to initialize the

device resulting in the restart of the
Ingressq driver process.

Error Allocating <[dec]> bytes of memory

Ingressq encountered a fatal memory

allocation error. If a new configuration
being applied, the configuration will be
rejected. The user may reapply the
configuration. If the error happens during
normal operation, the process will restart to
recover from this error.

Unknown event type received while

received unknown event: [dec] from fsdb in receiving mcd msg from fsdb during FDI
mcd req_id [dec]
init.

Ingressq: [chars] Error Code [dec] Reason

[chars]

A general major error occurred. The

explanation is in the message itself.

Ingressq aborted the iMDR upgrade

The IngressQ process aborted the iMDR

upgrade.

There was a problem [chars] the imdr

process Error=[dec], Reason: [chars]

A problem was encountered while trying to

connect with the imdr process. There are a
few steps involved while connecting and
the error message indicates which step in
the process failed and the reason that it
failed.

A problem was encountered while trying

initialize with the IMDR EOC library. This
library is used during IMDR to keep track of
the client requests to Ingressq and to
determine when to notify the imdr process
that all client requests have been received.
If the ISSU/IMDR upgrade is in progress, the
upgrade may not complete sucessfully. If
the ISSU/ IMDR action is not in progress,
An error was encountered while initializing the initialization will not complete until
with the IMDR EOC Library. Error=[dec],
such time as a IMDR EOC library
Reason: [chars]
initialization completes sucessfully.

A Null or Invalid parameter was passed to

Function: [chars] - Parameter : [chars]

A null or invalid parameter was passed to

the above named function. This *may*
indicate a serious problem.

Error encountered during Checkpoint Init.

Exiting

Ingressq encountered an error during

Checkpoint Init.

Initialization Warning: [chars] Reason:

[chars].

Ingressq encountered an error but was able

recover or continue execution. This is not a
serious error, but for informational
purposes only.

Ingressq: Link [dec] of Asic Instance [dec]

has been administratively shut down.

Ingressq link has been shut down due to

admin configuration. Ingressq ASIC won't
be able to use this link for data traffic.

Bag register failed for rules

EDM Bags are used to share information

between components using sysdb. This
Error indicates that bag registration failed.

Error encountered during [chars]

Checkpoint Deletion

Ingressq encountered an error during

Checkpoint delete.

Error encountered during [chars]

Checkpoint Insertion

Ingressq encountered an error during

Checkpoint Insert.

Client [chars] failed. Error: [chars]

Ingressq client failed to Register/Unregister

with Ingressq Server process. This error is
also detected from the client's side. Retrial
attempts would be made by the client.

Dll registration for [chars] failed

Ingressq driver tried to register for a dll but

it encountered an error. The driver might
lose some of its functionality.

Event Manager create failed for [chars]

Ingressq Event Manager create error

Event Manager notify failed for [chars]

Ingressq Event Manager notify error

Event Manager create failed. Error([dec])

[chars]

Ingressq failed to create an Event Manager

LWM Event Manager event block failed

Ingressq Event Manager failed to create an

event block

An Error occurred during LWM message

reply. Reason: [chars]

An error occured while sending Ingressq

LWM reply

Error during Resource Programming:

[chars] Reason: [chars]

Ingressq encountered an error during

resource programming. If there are no
further attempts to reprogram the device,
the device behavior may be inconsistent.

Sysdb Bind failed.

Ingressq Sysdb Bind error. The driver

should retry by itself.

Sysdb Register EDM failed.

Ingressq Sysdb Register EDM error.The

driver might lose some of its functionality.

Sysdb Registration verification failed.

Ingressq Sysdb Registration verification

error. The driver should retry by itself

Sysdb Item Set Failed : [chars]

Ingressq Sysdb Set error for the iqm

configuration changes.

\n[chars]: Can not get evm\n

Failed to get the evm.

\n[chars]: fail to register with pm-ifh

[dec]\n

Failed to bind with the uidb.

shared memory allocation error [chars]

Failed to allocate the shared memory.

shared memory free error [chars]

Failed to free the shared memory.

Cannot get platform specific info for shared Failed to get the shared memory platform
mem [dec]: [chars]\n
information.

booster special adj create failed

Failed to allocate the address.

Arg is wrong \n

Arguments does not have the expected

value.

[chars]: bag register failed for rules\n

Failed to register all the booster bags.

Unable to get counters: invalid offset\n

Failed to get the base address of the

counters.

Alloc failed in bitmap [dec]\n

Failed to allocate the bitmap.

Failed to init shm_head \n

Failed to get the shared memory header.

[chars] ERROR : start index and end index

are errorenous \n

Start and end index does not have the

valid values.

[chars] : MNODE ALLOCATION FAILED \n

Failed to allocate the mnode.

[chars] : MNODE DELETION FAILED \n

Failed to delete the mnode.

[chars] ERROR : pointer to p_edge_mnode

is NULL \n

Pointer to the mnode does not have a valid

value.

[chars] PCI read burst error ,rc = [dec] \n

Failed to read to the PCI.

[chars] PCI write burst error ,rc = [dec] \n

Failed to write to the PCI.

[chars] PCI write burst error ,rc = [dec] \n

Failed to write to the PCI.

booster memmgr adj alloc failed

Failed to allocate the memory for ADJ.

booster memmgr lspa array alloc failed

Failed to allocate the memory for LSPA.

[chars]: sysdb_bind Failed [chars]\n

Failed to bind with the SYSDB.

booster_sysdb_conn_clear_counters_registe
r failed\n
Failed to clear the counter registers.

[chars]: sysdb_conn_to_coid Failed:

[chars]\n

Failed to connect with the sysdb.

booster_sysdb_conn_register failed rc: \n

Failed to register connection with SYSDB.

[chars]: sysdb_register_edm failed\n

Failed to register with the SYSDB.

booster memmgr tbm alloc. Illegal no

nodes = [dec]\n

The node value is not legal.

\nassertion '[chars]' failed in [chars]

([chars]:[dec])

Assertion Failure.

\nassertion '[chars]' failed in [chars]

([chars]:[dec])

Assertion Failure.

\nassertion '[chars]' failed in [chars]

([chars]:[dec])

Assertion Failure.

A runtime error occurred in GSR adj's egine

layer. The reason for the failure is
GSR edge adj dll layer internal error [chars] displayed. Please call Cisco Support with
: [chars]
the error information.

\nassertion '[chars]' failed in [chars]

([chars]:[dec])

Assertion Failure.

Failed to access [chars] field of [chars]

object, error: [dec] [chars]

A runtime error occurred while trying to

access the specified field of the specified
object in the Platform Independent SW
Data Structures. The reason for the failure
is also displayed. Please call Cisco Support
with the error information.

GSR adj internal error: [chars]

A runtime error occurred in GSR adj

module.The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

Backwalk on [dec] object due to [chars]

event failed, error: [dec] [chars]

A runtime error occurred while trying to

walk and update dependent objects in the
forwarding chain. The reason for the failure
is also displayed. Please call Cisco Support
with the error information.

GSR ECD internal error: [chars]

A runtime error occurred in GSR ecd

module.The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

GSR ECD internal error: [chars]

A runtime error occurred in GSR ecd tracker

module.The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

A runtime error occurred while apply the

Fast convergence CLI. The reason for the
failure is also displayed. Please call Cisco
FastConvergence CLI: [chars], error: [chars] Support with the error information.

HAL FRR-Backup NH object create failed,

Primary Ifh = [hex], Secondary Ifh = [hex]

Maximum Limit of 2048 Primary-Backup

path combinations reached

[chars]: Could not map to the classic ECMP Failed to get the correct hash index for
paths
mapping to the path.

GSR IDB internal error: [chars]

A runtime error occurred in GSR IDB

module.The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

[chars], error: [dec] [chars]

A runtime error occurred while initalizing

GSR Hardware Abstraction Layer (HAL)
module. The reason for the failure is
displayed. Please call Cisco Support with
the error information.

A runtime error occurred in GSR FIB

module.The reason for the failure is also
GSR FIB internal error: [chars] failed to get displayed. Please call Cisco Support with
parent [chars] obj - [chars]
the error information.

GSR loadinfo internal error: [chars]

A runtime error occurred in GSR loadinfo

module.The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

GSR mpls label operational internal error:

[chars]

A runtime error occurred in GSR mpls

module.The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

[chars]: No local path available

Local path is not available.

MTRIE Mode CLI: [chars], error: [chars]

A runtime error occurred while connecting

to SysDB Please call Cisco Support with the
error information.

pak_netio_write failed

NETIO write failed.

[chars]: pak offset calc failed

Failed to calculate the correct offset.

HAL MPLS recursive LI collapse on Null

PBTS LDI: [pointer]

During recursive LI create, PBTS LDI is

NULL and not updated yet this could be
due to race condition, please do verify if
there are any traffic loss. If no traffic loss
we can ignore the error message. Else
please do collect the required logs and
contact technical support.

GSR prefix internal error: [chars]

A runtime error occurred in GSR prefix

module.The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

[chars], error: [dec] [chars]

A runtime error occurred while operating

on a shared memory window. The reason
for the failure is displayed. Please call Cisco
Support with the error information.

A runtime error occurred while trying to

register the specified interface with Stats
module for stats collection. The reason for
Failed to register interface [hex] with Stats the failure is also displayed. Please call
module, error: [dec] [chars]
Cisco Support with the error information.

Failed to unregister interface [hex] from

Stats module, error: [dec] [chars]

A runtime error occurred while trying to

unregister the specified interface from
Stats module for stats collection. The
reason for the failure is also displayed.
Please call Cisco Support with the error
information.

Stats validation error: [chars] ([dec]):

[chars]

A validation error occurred while doing an

LSP/TE statistics operation. Please call
Cisco Support with the error information.

GSR l3VPNOIP internal error: [chars]

A runtime error occurred in GSR L3VPNOIP

module.The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

[chars]: txl is NULL

TX pointer does not have the valid value.

[chars]: txl->path_map is not updated

TX path map does not have the valid value.

Forwarding requested unsupported

platform HW resource recovery and
platform is forcing line card reset to
recover hardware resources

The FIB encountered an unrecoverable

error afer one or more crashes. It is
attempting to purge all hardware and
software resources before starting a clean
initialization. The platform does not support
hardware resource recovery and is
resetting the line card to recover all
hardware resources. Please call Cisco
Support with the error information.

Used by BGP status changed from [chars]

to [chars] on obj 0x[pointer]

Used by BGP status on the loadinfo

changed. This is not generally expected
and config needs to be examined to
understand the cause. Please call Cisco
Support with the error information.

HAL-FIB: terminate File create [chars] failed Failed to open the open.

hal_ecd_ldi_create_and_modify_guts_rp,
Failed

Failed to fill the OCE info.

fib_get_ctx_from_gtrie_leaf failed \n

Failed to get the context from the tree leaf.

hal_prefix_get_data_from_pi_prefix failed \n Failed to get the prefix data from PI prefix.

hal_mpls_rewrite_li_update: default: [dec]\n LI type does not have the valid value.

hal_shm_alloc: malloc() failed proto [dec]

size [dec]

Failed to allocate the memory for the given

size.

MPI_PTR NULL

MPI Pointer does not contain the valid

value.

Failed to initialize the shared memory for

[chars]: shmwin_init() failed shmwinid [dec] NH.

hal_shm_alloc: shmwin_malloc() failed

shmwinid [dec]

Failed to allocate the shared memory for

NH.

[chars]: Failed to get Nodeid for Card

Family [hex] CardType [hex] Nodeid [hex],
Slotid [hex]

Failed to get the slot from node id.

ECD GP INFO mol_ctx NULL

Pointer does not have the proper value.

ECD GP INFO NOT LSM [dec]

parent object type does not contain the

needed value.

A runtime error occured, whereby Platform

Manager returned an unexpected error
while looking up an interface. If the error is
'Resource temporarily unavailable' then the
Platform Manager returned an error looking error is not fatal. Any other error is
up interface [hex]: [chars]
unexpected, and more serious.

Error encountered by HAL ppinfo

notification library while receiving ppinfo
notification batch. Error: [chars]

An error was encountered while processing

a notification of a change to the packet
path info for one or more adjacencies.
Forwarding for the affected adjacencies
may now be inconsistent.

An error was encountered while processing

a message of the given type from client for
HAL notifications of changes to the packet
Error handling a [chars] message from a
path info for adjacencies for a given
HAL ppinfo notification client. Error: [chars] interface type. Forwarding for the affected
([chars])
adjacencies may now be inconsistent.

hal_shm_free: shmwin_free() failed addr

0x[pointer]

Failed to free the shared memory.

[chars]: hal_bgp_nh_shm_init() failed

shmwinid [dec]

Failed to initialize the shared memory.

hal_shm_alloc: shmwin_malloc() failed

shmwinid [dec] size [dec]

Failed to allocate the shared memory for

the given size.

[chars]: shmwin_pool_create_v2() failed,

return: cerr: [dec]

Failed to create the memory pool for

shared memory.

WARNING: Mtrie mode you selected will

only take effect on Engine 3 linecards and
will be effective on each linecard after it
has been reloaded. Please reload using the
command: hw-module reload location
This command requires reprogramming all
r/s/CPU0
the prefixes in the LC hardware.

WARNING: This command will take effect

This command will take effect only after
only after reloading the node. Please reload reloading the node. Please reload the node
the node using the command hw-module
using the command hw-module reload
reload location r/s/CPU0
location r/s/CPU0
The number of TxList's for the IGP peer has
reached its max
This is a PI error to be fixed in Release 42
A runtime error occurred in GSR MPLS
module.The reason for the failure is also
[chars] - GSR HAL internal error: hal object displayed. Please call Cisco Support with
([chars]) getting a NULL hw_oce
the error information.

Failed to access [chars] field of [chars]

object, error: [dec] [chars]

A runtime error occurred while trying to

access the specified field %s - Indicates the
field that is accessed %s - Indicates the
Specified Object %d - is the decoded
reason %s - Indicates the reason for the
failure

L2 HAL action [chars] update failed for

[chars] [hex] error: [chars]

A runtime error occurred in GSR L2HAL

module.The reason for the failure is also
displayed.

Backwalk on [dec] object due to [chars]

event failed, error: [dec] [chars]

A runtime error occurred while trying to

while trying to walk and update dependent
objects. %s - Indicates the Specified Object
being accessed %s - Indicates the Specified
Object %d - is the decoded reason %s Indicates the reason for the failure A
runtime error occurred while trying to walk
and update dependent objects in the
forwarding chain. The reason for the failure
is also displayed.

Engine 3 LC cannot be edge and core

simultaneously. Revert those configs.

A runtime error occurred in GSR L2HAL

module.The reason for the failure is also
displayed.

Engine 3 LC cannot have different types of A runtime error occurred in GSR L2HAL
encaps under same bridge domain. Revert module.The reason for the failure is also
those configs.
displayed.

[chars] - GSR L2 HAL internal error: hal

object ([chars]) getting a NULL hw_oce

A runtime error occurred in GSR MPLS

module. %s - Indicates the function where
the error is seen %s - Indicates the object
being accessed.

[chars], error: [dec] [chars]

A runtime error occurred while initializing

GSR Layer 2 VPN Hardware Abstraction
Layer (L2 HAL) module. %s - Indicates the
Specific Error seen. %d - is the decoded
reason %s - Indicates the reason for the
failure

GSR L2 FIB internal error: [chars] failed to

get parent [chars] obj - [chars]

A runtime error occurred in GSR L2 FIB

module. %s - Indicates the internal HAL
object being accessed %s - Indicates
whether it is 'FWD_WALK' or 'BACK_WALK'
%s - Indicates the reason for failure.

[chars], error: [dec] [chars]

A runtime error occurred while initalizing

GSR Layer 2 VPN Hardware Abstraction
Layer (L2 HAL MCAST QoS) Multicast QoS
module. %s - Indicates the place where
error is seen %d - Is the decoded error code
%s - Indicates the reason for failure

[chars], error: [dec] [chars]

A runtime error occurred while operating

on a shared memory window. %s Indicates where the error is seen %d - Is
the decoded error code %s - Indicates the
reason for failure.

L2 HAL duplicate bind received for [chars]

object [hex]

A transient error occurred while initializing

GSR Layer 2 VPN Hardware Abstraction
Layer (L2 HAL) module. The reason for the
failure is displayed. No action is required as
this does not affect the forwarding
operation.

[chars], error: [dec] ([chars])

A transient error occurred while initializing

GSR Layer 2 VPN Hardware Abstraction
Layer (L2 HAL) module. %s - Indicates what
has failed to INIT %d - Is the decoded
reason %s - Indicates the reason for failure
No action is required as this initialization
will be retried.

GSR PRINT FUNC: default type: [dec],

length [dec]\n

The print function failed.

Booster PCI Lib Init failed

Failed to initialize the PCI.

[chars] FIB object [chars], action [chars],

HAL_OBJ [chars], Ctx 0x[pointer] FIB Ctx
[hex], ifh [hex], error1 [chars], error2
[chars]

This is a supplementary error message

generated by c12000 platform FIB mgr to
provide additional information with
platform specific error codes. We would
expect platform independent FIB Mgr
generate the main error message
FORWARDING FIB PLATF_UPD_FAIL to drive
main error message.

[chars] FIB object [chars], action [chars],

HAL_OBJ [chars], Ctx 0x[pointer] FIB Ctx
[hex], error [chars]

This is a supplementary error message

generated by c12000 platform FIB mgr to
provide additional information with
platform specific error codes. We would
expect platform independent FIB Mgr
generate the main error message
FORWARDING FIB PLATF_UPD_FAIL to drive
main error message.

ltrace_init failed for '[chars]': [chars]

Initialization failed. Both the initialization

type and the error code are displayed. The
sysmgr process will restart the ip_tunnel if
this condition happens.

Failed to send bandwidth notification for

tunnel-ip [unsigned int]. [chars]

Failed to send the bandwidth notification to

its clients for the specified tunnel. The
configured bandwidth (or default
bandwidth if not configured) for this tunnel
will not take effect.

Failed to [chars] checkpoint for tunnel-ip

[unsigned int]. [chars]

Failed to write/delete the checkpoint entry

for the specified tunnel. This may result in
inconsistent state after tunl_gre_ma
restarts.

IP tunnel MA failed to add a tunnel to one

of its databse. This may result in
inconsistent behavior for this tunnel. It may
Tunnel-IP MA: Failed to add tunnel-ip
cause errors while modifying/deleting this
[unsigned int] to [chars] database. [chars] tunnel.

It is invalid for a tunnel destination to be a

local IP address. When this message is
displayed, the user must change the tunnel
Tunnel-IP MA: Interface tunnel-ip [unsigned destination or change the IP address on the
int] uses destination [chars], which is a
local interface. When this is corrected, the
local IP address on interface
tunnel will re-evaluate its state and come
<<CH[hex]>>. This is not allowed and
UP if other criteria for tunnel to be up are
tunnel interface state will remain DOWN.
satisfied.

On some platforms, it is not allowed for a

tunnel to be reachable through another
tunnel. This is because the platform has to
encapsulate the packet more than once on
the same router. When this message is
displayed, the user must change the tunnel
Tunnel-IP MA: Interface tunnel-ip [unsigned destination or change the route for tunnel
int] with destination [chars] has route over destination address. When this is corrected,
another tunnel, interface '<<CH[hex]>>'. the tunnel will re-evaluate its state and
This is not allowed and the tunnel interface come UP if other criteria for tunnel to be up
state will remain DOWN.
are satisfied.

Tunnel-IP Lookup DLL failed to initialize

[chars]: '[chars]'.

Tunnel IP Lookup DLL failed to initialize a

critical component and might not function
properly.

The Tunnel-IP EA process could not allocate

Tunnel-IP EA failed to allocate %zu bytes of memory needed to update tunnel
memory: '[chars]'
interface.

Tunnel-IP EA failed to program interface

<<CH[hex]>> after [unsigned int] retries: The Tunnel-IP EA has failed to program a
[chars].
tunnel interface after 1 or more retries.

EA IDB error: [chars]

This message indicates that an error has

occurred in IP Tunnel Execution Agent IDB.
IDB can't be found or created. Particular
reason is included in this message.

Error initializing EA of IP Tunnel: [chars]

This message indicates that initialization of

IP Tunnel's Execution Agent failed.
Particular reason is included in the
message. This error prevents IP Tunnel
from functioning

Client [chars] failed to read data from

server (ip_tunnel_ma) : [chars]

This message indicates that a client

process issued ens_read and it failed. This
failure is because the server, IP Tunnel
Management Agent, is either busy or there
is problem in GSP communicatoin.

Error from Event_Manager: [chars] [[dec]:

[chars]]

This message indicates that an unexpected

event has been delivered to the process
that printed this message. An error
occurred within event manager.

FEA internal error: [chars]

This message indicates that IP Tunnel

Execution Agent process can't synchronize
with FEA.

Failed to create interface for tunnel-ip

[unsigned int]. [chars]

An error was encountered in creating the

interface for the specified tunnel.

Failed to delete interface for tunnel-ip

[unsigned int]. [chars]

An error was encountered in deleting the

interface for the specified tunnel.

IMP Server error: [chars] [[dec]: [chars]]

This message indicates that an error has

occurred in IMP Server. Particular failure
reason is included in the message. This
error happens when IP Tunnel Execution
Agent tries to connect to IMP server.

IP Tunnel debug initialization: [chars]

[[dec]: [chars]]

This message indicates that an error has

occurred during the initialization of the
debug events for IP tunnel. Specific event
type is included in the message. This error
prevents IP Tunnel from printing debug
messages if the corresponding debug flags
are turned on.

Failed to send the specified event from

tunl_gre_ma's main thread to the keepalive thread or vice-versa. This may result
Failed to enqueue keep-alive event '[chars]' in errorneous keep-alive behavior for the
for tunnel-ip [unsigned int]. [chars]
tunnel specified.

Keep-alives should not be configured on a

GRE tunnel on which Key is configured. This
is a system limitation. Corresponding
Tunnel-IP MA: Keep-alive is not supported tunnel interface will go down if keep-alive
for tunnel-ip [unsigned int] as tunnel key is and tunnel key both are configured on a
configured
tunnel.
The Tunnel-IP MA process could not allocate
Tunnel-IP MA failed to allocate %zu bytes of memory needed to update tunnel
memory: '[chars]'
interface.
Tunnel-IP MA process failed to update the
interface state of tunnel-ip [unsigned int]:
'[chars]'

The Tunnel-IP MA process failed to update

the state of a tunnel interface.

Tunnel-IP MA process failed to update the

state of [unsigned int] interfaces: '[chars]'
due to internal system error

The Tunnel-IP MA process failed to update

the state of interfaces.

Error initializing MA of IP Tunnel: [chars]

[[dec]: [chars]]

This message indicates that initialization of

IP Tunnel's Management Agent failed.
Particular reason is included in the
message. This error prevents IP Tunnel
from functioning.

Memory operation error: [chars]

This message indicates that an error has

occurred during memory allocation. This
error is due to insufficient memory
available in the system.

NetIO IDB error: [chars]

This message indicates that NetIO IDB

can't be found by the process that printed
this message.

Failed to process P2MP tunnel updates:

[chars] [[dec]: [chars]]

This message indicates that an error has

occurred when processing P2MP tunnel
updates.

It is not allowed to configure a tunnel with

same pair of source and destination as an
existing tunnel in the system. On display of
this message user must change the source
Tunnel-IP MA: Interface tunnel-ip [unsigned address or destination address to a unique
int] uses source [chars] and destination
pair of addresses that does not exist in the
[chars] which is in conflict with another
system. On successful resolution of this
tunnel-ip [unsigned int] with the same
conflict, the tunnel interface state will be
source-destination pair. tunnel-ip [unsigned set back to UP state, provided the other
int] state will remain DOWN because of this criteria to bring up the interface are
conflict.
satisfied.
This message indicates that an error has
occurred during packet decapsulation.
IP Tunnel Decapsulation fail: [chars] [[dec]: Particular reason is included in the
[chars]]
message.

Tunnel-IP EA process failed to initialize

[chars]: '[chars]'

The Tunnel-IP EA process failed to initialize

a critical component. The process cannot
proceed and will restart to recover.

Tunnel-IP EA has retried [unsigned int]

times to update interface <<CH[hex]>>.

The Tunnel-IP EA process has retried

programming tunnel interface(s) because
other processes are not ready.

IP Tunnel Encapsulation fail: [chars]

This message indicates that an error has

occurred when IP Tunnel Execution Agent
was creating encapsulation header for
payload traffic. Particular failure reason is
included in the message.

FIB Initialization failed: [chars] [[dec]:

[chars]]

This message indicates that an error has

occurred when initializing FIB event
connection. Particular failure reason is
included in the message.

The Tunnel-IP MA process failed to initialize

Tunnel-IP MA process failed to initialize the a critical component. The process cannot
state of [chars]: '[chars]'
proceed and will restart to recover.

Tunnel-IP EA shared memory reset

complete

The Tunnel-IP EA needed to reset its shared

memory due to a non-graceful reset
scenario. The Tunnel-IP EA may have
crashed due to a problem in its own
process, or it may have induced a crash on
itself due to a critical client error.

ltrace initialization failed for '[chars]':

[chars]

This message indicates that ltrace

initialization failed. Both the initialization
type and the particular reason are
displayed. This error prevents IP Tunnel
Execution Agent process from printing
ltrace information.

Failed to alloc ([unsigned int] hdr) +

([unsigned int] items)*([unsigned int]
bytes) = ([unsigned int] total bytes) for
'[chars]', errno [hex]:[chars].

This message indicates that the pbr_ea

process has failed to allocate memory. This
may be due to low memory conditions on
this particular node, or pbr_ea may be
using more memory than it is allowed.

Dropping invalid packet for interface

<<CH[hex]>> ([hex]).

This message indicates that PBR failed to

process an invalid packet. The expected
forwarding action will not be taken.

Failed to receive event from EVM, [hex]:

[chars].

This message indicates that the event

processing infra has returned an error.
Particular reason is included in the
message.

Failed to initialize '[chars]', [hex]:[chars].

This message indicates that an error has

occurred during the 'pbr_ea' process
initialization and it may prevent PBR from
functioning. Particular reason is included in
the message

Failed at '[chars]' during shutdown, [hex]:

[chars].

This messages indicates that a failure has

occured while PBR is gracefully shutting
down. Particular reason is included in the
message.

Failed to alloc ([unsigned int] hdr) +

([unsigned int] items)*([unsigned int]
bytes) = ([unsigned int] total bytes) for
'[chars]', errno [hex]:[chars].

This message indicates that the pbr_ma

process has failed to allocate memory. This
may be due to low memory conditions on
this particular node, or pbr_ma may be
using more memory than it is allowed.

Failed to receive event from EVM, [hex]:

[chars].

This message indicates that the event

processing infra has returned an error.
Particular reason is included in the
message.

Failed to initialize '[chars]', [hex]:[chars].

This message indicates that an error has

occurred during the 'pbr_ma' process
initialization and it may prevent PBR from
functioning. Particular reason is included in
the message

Failed at '[chars]' during shutdown, [hex]:

[chars].

This messages indicates that a failure has

occured while PBR is gracefully shutting
down. Particular reason is included in the
message.

A client library returned an empty buffer:

[chars] [chars]

A NULL pointer was encountered

unexpectedly.

Buffer size mismatch: [dec]: [dec]

A NULL pointer was encountered

unexpectedly.

An invalid argument was passed: [chars]

An argument was passed with an invalid

value.

Something is incosistent .heap index 0x

%zx , seg [dec] , offset [dec] , segsize [dec]
global chunk [dec], global pages mapped Internally heap pointers are kept as offset
[dec] , my cur chunk [dec], my pages
indices. A given heap index was found to
mapped [dec]
be outside the heap.

Bad heap page block pointer: [chars]:

[pointer]

A heap page address is misaligned or lies

in some invalid range.

heap pointer cannot be mapped to

segment offset: [pointer]

Internally heap pointers are kept as offset

indices. A given heap pointer was found to
be outside the heap.

Bad record pointer to free ([char]):

[pointer]

Bad NCT record is being freed.

CDM heap corruption was detected

([chars]). Process will be cold restarted.

The process crashed during CDM heap

modification, resulting in an unrecoverable
heap. Process will be started from an
empty heap.

Data corruption is detected in CDM data

Data corruption: [chars]: 0x[dec], 0x[dec], structures. This will generally result in a
0x[dec], 0x[dec]
single process failure.

unmap and reserve failed: addr [hex] len

[dec], [chars]

When attempting to free memory that is no

longer in use, the CDM library received an
error from the kernel.

NCT: requested size too large: %zd

Higher layers of heap are requesting a size

for a variable-size record that is too large.

Objid [hex] in table [hex] could not be

found

The object could not be found in the given

table when attempting to map the object
ID to a memory address.

CDM segment operation failed: Process

[chars] tag [chars] is running on node
[chars].

A request to move or copy CDM data from

one node to another has failed because an
instance of the process is running on the
destination node.

CDM file [chars] has been renamed to

[chars] for later analysis due to corruption
found during restart.

A corrupted CDM segment has been

renamed for later analysis.

Tblid [hex] objid [hex] segment mismatch

(tbl-seg [dec] obj-seg [dec])

When the table ID and object ID are

mapped to segment numbers, they do not
match. Since an object belongs to a table
and therefore resides in the same segment,
this indicates a coding error.

[chars].[dec]: hit assert condition.

'val1=[hex]' expected to be [chars]
'val2=[hex]'

Cdm hit an internal assert.Some api call

didnot work as expected. assert will
generate core dump.

[chars]() could not open mqueue pid/chid

[dec]/[dec].

Process hit a messege queue error.

[chars]() mq_send() mqd: [dec] error:

[chars]

Process hit a messege queue error.

ltrace_init2 for [chars] trace failed

Failed to register ltrace context structure.

Tracing will not be functioning properly.

Process has been restarted without CDM

data due to request from sysmgr

Due to too many contiguous failed restarts,

sysmgr has requested that the process be
restarted without CDM data.

Ignoring sysmgr cold restart flag

The process has failed to restart multiple

times. By design, the process will continue
to restart with its existing CDM data.

Debug register failed ([hex]): [chars]

Registration of debug services failed.

[chars]: User key [dec] is in use by object

[hex] in table [hex]

A client of the CDM library attempted to

create an object with a key that was
already in use.

initialization error: [chars]: [dec] ([chars])

An error was encountered during

intialization of the CDM library. The
message should indicate the error
condition. This is most likely due to a
coding error.

function not implemented yet: [chars]

Unimplemented functionality.

Error during table registration: [chars]:

name: [dec] version: [dec]

An error was encountered during table

registration. The message should indicate
the error condition. This is most likely due
to a coding error.

OS/System error: [chars]: [dec] ([chars])

This message signals an unrecoverable

condition reported from the underlying
system services. The severity of such
errors cannot be determined locally by
CDM, so it treats them all such conditions
as non-fatal, transient errors. The CDM user
must abort its immediate operation.

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error, but may help
with debugging other problems elsewhere.

Warning: [chars]: [chars]: 0x%zx

This provides information about non-error

conditions which may even be expected
under certain circumstances. Nevertheless,
these are not considered 'desirable'
conditions.

Index not aligned: 0x%zx

A heap index was not word aligned.

Cold restart: Reason: [chars]: Application

[chars]: table [dec]: version [dec]

A process failed to restore state from a

table in the CDM store.

Duplicate table found: Application [chars],

table [dec]

During registration, two copies of a table

were found in the CDM store at the same
version. This indicates corruption in the
CDM store.

No translator found: [chars]: [chars]:

[chars]

A required translator was not loaded.

Errors (most likely lack of memory) prevent

CDM from creating an index structure
associated with an indexed table. This
unable to setup index structure for indexed condition does not affect the functionality
table: [chars]: [hex]: [dec]
at all, only the performance will suffer.
A table's object count is not what it's
supposed to be. This is an internal
accounting error and does not cause any
problems inside CDM, but it may cause
table object count not correct: [hex]: [dec] applications which depend on this
(!= [dec])
accounting info to mis-behave.

Bad object length: [chars] tblname: [hex]:

object size: [dec] record length: [dec]

An object save or get operation is being

done with the wrong length buffer. This
points to a logical bug in the client
application.

table attributes changed upon re-register:

<[hex], [hex]>

An application is trying to register for its

table. A table with the same <name,
version> exists, but other attributes have
changed, so the table is not allowed to be
used.

Fatal translation error: [hex]

An error occurred during data translation.

The process will restart without CDM data.

Checkpoint hit an assert condition,

returned 'val=[hex]'

Checkpoint related internal data structures

gone wrong. Checkpoint cannot continue
further hence, process will crash and
restart immediately after this message.

[chars]:[dec]:
chk_shmheap_seg_unlink(FALSE,
[dec],FALSE) returned rc=[dec],
errno=[dec]([chars])\n

Unlink of shared memory segments failed.

While initializing checkpoint.

ltrace_init2 for [chars] trace failed

Failed to register ltrace context structure.

Tracing will not be functioning properly.

Mutex destory for mutex '[pointer]' has

failed with '[hex]'

An attempt to destroy a Mutex has failed,

this message is not harmful and its
informational only.

Process has been restarted without

checkpoint data due to request from
sysmgr

Due to too many contiguous failed restarts,

sysmgr has requested that the process be
restarted without checkpoint data.

Ignoring sysmgr cold restart flag

The process has failed to restart multiple

times. By design, the process will continue
to restart with its existing checkpoint data.

Debug register failed ([hex]): [chars]

Registration of debug services failed.

[chars]: User key [dec] is in use by object

[hex] in table [hex]

A client of the checkpoint library attempted

to create an object with a key that was
already in use.

Inconsistent versioning information:

[chars]: native_version: [dec],
storage_version: [dec], VS_version: [dec]

An invalid combination of version numbers

was encountered during table registration
or table versioning. This is most likely due
to a coding error.

initialization error: [chars]: [dec] ([chars])

An error was encountered during

intialization of the checkpoint library. The
message should indicate the error
condition. This is most likely due to a
coding error.

function not implemented yet: [chars]

Unimplemented functionality.

[chars]:[dec]: chk_raw_seg_unlink([dec],
[dec]) returned rc=[dec], errno=[dec]
([chars])\n

Unlink of shared memory raw segments

failed. No impact on process.

Error during table registration: [chars]:

name: [dec] version: [dec]

An error was encountered during table

registration. The message should indicate
the error condition. This is most likely due
to a coding error.

Process [chars] jid [dec] is removing chkpt While initialising Checkpoint. Process is
shared memory.\n
removing shared memory segments .

Process [chars] jid [dec] is re-using chkpt

shared memory.\n

While initialising Checkpoint . Process is

reusing shared memory segment because
some unprocessed imdrs exist.

OS/System error: [chars]: [dec] ([chars])

This message signals an unrecoverable

condition reported from the underlying
system services. The severity of such
errors cannot be determined locally by
Checkpointing, so it treats them all such
conditions as non-fatal, transient errors.
The chkpt user must abort its immediate
operation.

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error, but may help
with debugging other problems elsewhere.

Warning: [chars]: [chars]: [hex]

This provides information about non-error

conditions which may even be expected
under certain circumstances. Nevertheless,
these are not considered 'desirable'
conditions.

A client library returned an empty buffer:

[chars] [chars]

A NULL pointer was encountered

unexpectedly.

Buffer size mismatch: [dec]: [dec]

A NULL pointer was encountered

unexpectedly.

An invalid argument was passed: [chars]

An argument was passed with an invalid

value.

Conflicting ISSU flag specified for process

[chars] jid [dec] component [dec]. Existing
shared memory reuse flag is [dec] and new
flag is [dec].

When chkpt is used by multiple DLLs from

within the same process context, they all
need to specify same value for shared
memory reuse flag.

Mirroring enabled for this client but

translator DLL not provided.

Every chkpt client that requires mirroring

should provide call back DLL to handle the
endian neutral transformation. If DLL is not
provided, check pointed records might get
corrupted in mixed endian mode RP.

Some clients wishes to store their records

Checkpoint client has not registered
in NBO format. In such cases, there is no
translator DLL with chkpt. Chkpt assumes need to register callback DLL with chkpt
that the endianess is handled by the client since no X86 transformation is needed in
appropriately.
such cases.
heap index 0x%zx (seg [dec] offset [dec]
segsize [dec] maxseginuse [dec]) cannot
be mapped to segment pointer

Internally heap pointers are kept as offset

indices. A given heap index was found to
be outside the heap.

Bad heap page block pointer: [chars]:

[pointer]

A heap page address is misaligned or lies

in some invalid range.

heap pointer cannot be mapped to

segment offset: [pointer]

Internally heap pointers are kept as offset

indices. A given heap pointer was found to
be outside the heap.

Bad record pointer to free ([char]):

[pointer]

Bad NCT record is being freed.

Checkpoint heap corruption was detected

([chars]). Process will be cold restarted.

The process crashed during checkpoint

heap modification, resulting in an
unrecoverable heap. Process will be started
from an empty heap.

Data corruption is detected in

Data corruption: [chars]: 0x[dec], 0x[dec], checkpointing data structures. This will
0x[dec], 0x[dec]
generally result in a single process failure.
When attempting to free memory that is no
unmap and reserve failed: addr 0x[pointer] longer in use, the checkpoint library
len %zd, [chars]
received an error from the kernel.

NCT: requested size too large: %zd

Higher layers of heap are requesting a size

for a variable-size record that is too large.

Objid 0x%zx in table 0x%zx could not be

found

The object could not be found in the given

table when attempting to map the object
ID to a memory address.

checkpoint segment operation failed:

Process [chars] tag [chars] is running on
node [chars].

A request to move or copy checkpoint data

from one node to another has failed
because an instance of the process is
running on the destination node.

Checkpoint file [chars] has been renamed

to [chars] for later analysis due to
corruption found during restart.

A corrupted checkpoint segment has been

renamed for later analysis.

Tblid 0x%zx objid 0x%zx segment

mismatch (tbl-seg [dec] obj-seg [dec])

When the table ID and object ID are

mapped to segment numbers, they do not
match. Since an object belongs to a table
and therefore resides in the same segment,
this indicates a coding error.

[chars]: [chars] failed with error [hex]

[chars]:[dec]
[chars]

A call to a system function failed with the

specified error code.
Internal Information messages
Internal Debug Messages

Lib/replicator returned a non-retryable error

after the asynchronous retry thread was
spawned. There is no way to return an error
Chkpt was unable to asynchronously
to the client process, so the library will
initialise the Replicator Library (error [hex] force an exit to try again. A voluntary core
- [chars]). The client process will be
dump should accompany this message to
restarted in order to attempt to recover.
allow further debugging.

Checkpoint Initial Data Transfer failed at

[chars] with status code [hex]

An error occurred during checkpoint Initial

Data Transfer which resulted in its failure. A
retry of IDT will happen automatically.

[chars]: message lengths invalid (msglen

[dec] srcmsglen [dec] error [hex] ([chars])

The source message length is less than the

message length. This is a situation which
should never happen.

[chars]: message type [dec] invalid; error

[hex] ([chars])

The message type has the checkpoint

component ID, but does not have a
message type in the correct range. This is a
situation which should never happen.

[chars]: Bad request type [dec] msglen

%zd

A bad message request was received by

the event handler function.

[chars]: request type [dec] had sequence

number [dec] (expected [dec])

The mirroring request had an incorrect

sequence number. This indicates either an
algorithm error, or data corruption on the
active node or in the data transfer between
nodes. Initial Data Transfer will be redone,
and no data loss should occur.

The message header totalsize value must

[chars]: msg totalsize ([dec]) != srcmsglen be equal to the source message length. If
(%zd error [hex] ([chars])
not, this indicates an IPC or coding error.

The message buffer assigned to the

checkpoint library by the application is less
than the minimum size for successful
Checkpoint library message buffer must be messaging functionality. The application
at least [dec] bytes; [dec] bytes is too
should increase the size of its event
small for correct operation.
manager message buffer.
An attempt to exclusive-create on a local
channel failed. This indicates that there's
[chars]: process name \[chars]\ tag \
already a copy of this same process
[chars]\ is already running - this should not running, and it cannot be allowed to
happen: aborting
continue, since corruption can result.

[chars]: call to [chars] failed with errno

[dec]

A call to an event manager function failed.

msg_chan_create failed for [chars]

ret=[dec] err=[chars] \n

A call to message channel create api failed.

process will abort with error.

[chars]: [chars] failed with error [hex]

([chars])

Extracting message or source message

length failed.

All attempts to do Initial Data Transfer to

standby failed (error [hex])

Multiple attempts to transfer initial

mirrored data to the standby have failed,
and the attempts have been stopped.

IDT received from different endian node

type. Endian transformation needed.

Just debug information to know that active

RP is of different endian type.

Endian transformation of IDT portion of

data completed.

--

[chars]: call to [chars] failed with error

[hex] ([chars])

A call to a LightWeight Messaging function

failed. This may be due to a server being
unavailable at the time of the call.

[chars]: malloc of %zd bytes failed; errno

[dec]

A call to allocate memory failed.

[chars]: msg_read (case [dec]) failed with

return [dec]; status [hex] ([chars])

A msg_read call in the message handler

failed.

[chars]: msg_reply (reqtype [dec]) failed

with errno [dec]

A msg_reply call in the message handler

failed.

[chars]: msg_send_event failed with return A msg_send_event call in a checkpoint

[dec]
mirroring function failed.

[chars]:[dec]: Non-checkpoint message

received: comp-id [dec] req type [dec]

A message request for a non-checkpoint

component was received by the handler
function.

[chars]: call to [chars] failed with errno

[dec]

A call to a Posix Pthreads function failed.

Replica name [chars]%s[chars] exceeded

the maximum length permitted by Group
Services, and has been truncated to
[chars]. Replication problems may result if
the truncated replica name is non-unique.

A replica name passed to the Replicator

Library was truncated. This is not an issue
in itself, but may cause problems further
down the line, if the replica name becomes
non-unique within the system.

Attempts to open standby channel [chars]

failed after [dec] retries - continuing

Multiple attempts to open the messasge

channel to the standby node (either the
application itself or the checkpoint proxy)
failed due to either the proxy not running
on the standby or the application itself not
running on the standby. If the application
should run on the standby, then it must call
chkpt_init() in order for mirroring to
succeed.

Multiple attempts to spawn a copy of the

checkpoint proxy for this application on the
All attempts to spawn checkpoint proxy on standby were done, and the attempts have
the standby failed (error [hex])
been stopped.

Call to sysmgr_is_standby_capable failed

with error (error [hex])

The call to sysmgr_is_standby_capable

failed. This may be due to the application
not having a startup file, and so being
unknown to sysmgr.

[chars]: call to sysmgr_get_proc_role failed A call to sysmgr_get_proc_role failed with

with status [hex] ([chars])
the given status.

After conversion:[chars]

To print the values after conversion.

Before conversion:[chars]

To print the values before conversion.

[chars]:[dec] - [chars]

For UT

IPC request type [dec] had bad length %zd An IPC message with invalid length was
(expected [dec])
received by the proxy process.

Bad IPC request type [dec] received with

message length %zd

An invalid IPC request type was received by

the proxy process.

[chars]

Internal Debug Message

[chars]: a call to group_create failed with

error [dec]

The proxy process uses group_create() to

join the proxy control group. A call to
group_create() failed with the specified
error.

[chars]: [chars] failed with error [dec]

As part of IPC operation, a call to a function

failed with the specified error.

[chars]: could not allocate [dec] bytes of

memory

Memory allocation failed. This is likely to be

a resource shortage rather than a coding
error.

The proxy process uses putenv() to

communicate with the checkpoint library. A
[chars]: a call to putenv([chars]) failed with call to putenv() failed with the specified
error [dec]
error.

Proxy not spawned for LR-plane process

'[chars]' due to admin boot hold

Admin boot hold has ben set for this node

(normally due to an install operation) so a
chkpt_proxy has not been spawned for this
process.

[chars]: [chars] failed with error [hex]

A call to a system function failed with the

specified error code.

Checkpoint data on active and standby

nodes is out-of-sync: Reason: [chars]:
Application [chars]: table [dec]: native
version [dec], storage version [dec], VS
version [dec]

A process failed to restore state from a

table in the checkpoint store.

Index not aligned: 0x%zx

A heap index was not word aligned.

Cold restart: Reason: [chars]: Application

[chars]: table [dec]: native version [dec],
storage version [dec], VS version [dec]

A process failed to restore state from a

table in the checkpoint store.

Duplicate table found: Application [chars],

table [dec]

During registration, two copies of a table

were found in the checkpoint store at the
same version. This indicates corruption in
the checkpoint store.

While attempting to version a checkpoint

Application passed an invalid native
table, an application using checkpoint
version during a checkpoint table
attempted to pass a native version that
versioning operation. Table: [unsigned int], was inconsistent with the native version
New version: [dec], Heap version: [dec]
recorded in the checkpoint heap.

No translator found: [chars] : [chars] :

[chars]

A required translator was not loaded.

Errors (most likely lack of memory) prevent

checkpointing from creating an index
structure associated with an indexed table.
This condition does not affect the
unable to setup index structure for indexed functionality at all, only the performance
table: [chars]: [hex]: [dec]
will suffer.

A table's object count is not what it's

supposed to be. This is an internal
accounting error and does not cause any
problems inside checkpointing, but it may
table object count not correct: [hex]: [dec] cause applications which depend on this
(!= [dec])
accounting info to mis-behave.

Bad object length: [chars] tblname: [hex]:

object size: [dec] record length: [dec]

An object save or get operation is being

done with the wrong length buffer. This
points to a logical bug in the client
application.

table attributes changed upon reregistration: name [unsigned int], version

[dec], new attributes: <[unsigned int],
[unsigned int],[unsigned int]>, existing
attributes: <[unsigned int],[unsigned int],
[unsigned int]>

An application is trying to register for its

table. A table with the same name and
version exists, but other attributes have
changed, so the table is not allowed to be
used.

Fatal translation error: [hex]

An error occurred during data translation.

The process will restart without
checkpointed data.

[chars]@[dec]: Null Data Pointer

Encountered Handle = 0x[pointer] Counter
= 0x[pointer]
An expected data pointer was not found.

Registration of error strings failed with

error [hex]

Error string registration failed.

[chars]@[dec]: A Non-Fatal Internal Error

was encountered.

A Non-Fatal condition was encountered.

This is not necessarily an error, but
information gathered here may help with
debugging other problems elsewhere in the
system.

[chars]@[dec]: An Unexpected condition

was encountered - [chars]

An unexpected condition was encountered.

This is not necessarily an error, but
information gathered here may help with
debugging other problems elsewhere in the
system.

[chars]

The action_syslog call from tcl script.

[chars]

The action_syslog call from tcl script.

[chars]

The action_syslog call from tcl script.

[chars]

The action_syslog call from tcl script.

[chars]

The action_syslog call from tcl script.

[chars]

The action_syslog call from tcl script.

[chars]

The action_syslog call from tcl script.

[chars]

The action_syslog call from tcl script.

Could not register for asynchronous

message events: [chars]

The event detector has failed to attach an

event handler for asynchronous messages.

Could not register for asynchronous

message events: [chars]

The event detector has failed to attach an

event handler for asynchronous messages.

The event detector has failed to initialize

the sigevent structure to be used by the
Could not initialize event structure: [chars] Event Manager.

The event detector has failed to initialize

the sigevent structure to be used by the
Could not initialize event structure: [chars] Event Manager.

Could not register for sychronous message The event detector has failed to attach an
events: [chars]
event handler for synchronous messages.

Could not register for sychronous message The event detector has failed to attach an
events: [chars]
event handler for synchronous messages.

Could not create event manager: [chars]

The event detector has failed to create an

Event Manager.

Could not create event manager: [chars]

The event detector has failed to create an

Event Manager.

An error occurred while waiting for an

event: [chars]

The event infrastructure will ignore this

error and continue to wait for the next
event. If this error is seen repeatedly, the
process may not be able to function and
will need to be restarted.

An error occurred while waiting for an

event: [chars]

The event infrastructure will ignore this

error and continue to wait for the next
event. If this error is seen repeatedly, the
process may not be able to function and
will need to be restarted.

Failed to open file [chars] : [chars]

Failed to open the given file due to some

internal error.

Failed to obtain a messaging channel ID:

[chars]

An error was reported trying to obtain the

channel ID.

[chars] guard word corrupted; [pointer]

The guard word for the specified control

block does not contain what is expected.

Not enough memory ([dec] bytes)

Allocating memory failed due to a lowmemory condition.

[chars]: Failed to attach to handle Event

Detector [chars] pulse code; [chars]

The event_pulse_attach_event function

reported an error trying to attach to handle
the Event Detector handler pulse code.

Unable to do an event_file_attach for

[chars]: [chars]

The event_file_attach function reported an

error.

event_init_event for Embedded Event

Detector [chars] failed: [chars]

The event_init_event function reported an

error.

Failed to attach to eem message channel:

[chars]

The msg_chan_attach function reported an

error trying to attach to the Embedded
Event Manager server channel.

Failed to attach to handle synchronous

messages: [chars]

The event_message_attach function

reported an error trying to attach to handle
synchronous messages.

The msg_chan_connect function reported

Failed to connect to eem message channel an error trying to connect to the specified
[chars]: [chars]
Embedded Event Manager server channel.

Failed to disconnect from eem message

channel [chars]: [chars]

The msg_chan_disconnect function

reported an error trying to disconnect from
the specified Embedded Event Manager
server channel.

The msg_send function reported an error

trying to send a message to the specified
Failed to send a message to [chars]: [chars] process.

Could not send a pulse to a connection:

[chars]

An internal error was detected when trying

to send a pulse to a connection.

Failed to send an event to [chars]: [chars]

The msg_send_event function reported an

error trying to send an asynchronous
message to the specified process.

Could not register for QSM notification:

[chars]

An internal error was detected when

registering for QSM notification.

MSG1[[chars]] ID[[dec]] MSG2[[chars]]

Debug message

Call to debug_register() failed with error

[dec] ([chars])

An internal error was detected when

registering with the debug library.

Call to debug_register() failed with error

[dec] ([chars])

An internal error was detected when

registering with the debug library.

Call to remonitor evm failed: [chars]

The resmon server returned an error to a

client in response to a request to remonitor
an event manager.

Call to remonitor evm failed: [chars]

The wdsysmon server returned an error to

a client in response to a request to
remonitor an event manager.

Call to monitor evm failed: [chars]

The resmon server returned an error to a

client in response to a request to stop
monitoring an event manager.

Call to monitor evm failed: [chars]

The wdsysmon server returned an error to

a client in response to a request to stop
monitoring an event manager.

[chars]: [chars]

A wdsysmon library was called with an

invalid argument.

[chars]: [chars]

A resmon library was called with an invalid

argument.

[chars]: [unsigned int]

During a re-registration, an internal context

structure was not found. This is probably a
coding error.

[chars]: [unsigned int]

During a re-registration, an internal context

structure was not found. This is probably a
coding error.

[chars]: not enough memory: [chars]

Allocating memory failed due to a lowmemory condition.

[chars]: not enough memory: [chars]

Allocating memory failed due to a lowmemory condition.

[chars]: Server failed to return memory

information: [chars]

An internal error was detected when trying

to communicate with wdsysmon to retrieve
a node's memory information.

[chars]: Server failed to return memory

information: [chars]

An internal error was detected when trying

to communicate with resmon to retrieve a
node's memory information.

[chars]: failed to register with WDSysMon

server: [chars]

An internal error was detected when trying

to register with WDSysMon server with an
initialization message.

[chars]: failed to register with resmon

server: [chars]

An internal error was detected when trying

to register with resmon server with an
initialization message.

[chars]:[chars]: failed to unregister with

wdsysmon resource notification server:
[chars]

An internal error was detected when trying

to unregister with wdSysmon server

[chars]:[chars]: failed to unregister with

An internal error was detected when trying
resmon resource notification server: [chars] to unregister with wdSysmon server

[chars]: failed to unregister with resmon

server: [chars]

An internal error was detected when trying

to unregister with resmon server with a
close message.

[chars]: failed to unregister with

WDSysMon server: [chars]

An internal error was detected when trying

to unregister with WDSysMon server with a
close message.

[chars]: [chars](): [chars]

A system call failed in the resmon library.

[chars]: [chars](): [chars]

A system call failed in the wdsysmon

library.

[chars]:[chars]: failed to initialize

WDSysMon resource notification thread
context: [chars]

An internal error was detected when trying

to initialize the WDSysMon resource
notification thread context

[chars]:[chars]: failed to initialize resmon

resource notification thread context:
[chars]

An internal error was detected when trying

to initialize the resmon resource
notification thread context

[chars], Aborting.

The system is experiencing CPU Hog, If this

condition persists for 30 seconds, the node
will be reloaded.

[chars], Aborting.

The system is experiencing CPU Hog, If this

condition persists for 30 seconds, the node
will be reloaded.

Process [chars] pid [dec] tid [dec] prio

[dec] using [dec]% is hogging CPU and will
be terminated
This message is displayed

Process [chars] pid [dec] tid [dec] prio

[dec] using [dec]% is hogging CPU and will
be terminated
This message is displayed

Process [chars] pid [dec] tid [dec] prio

[dec] using [dec]% is the top user of CPU.

This message is displayed after the CPU

hog detector trips. It shows the percentage
of CPU used by the busiest thread in the
top consumer of CPU.

Process [chars] pid [dec] tid [dec] prio

[dec] using [dec]% is the top user of CPU.

This message is displayed after the CPU

hog detector trips. It shows the percentage
of CPU used by the busiest thread in the
top consumer of CPU.

Persistent Hog detected for more than

[dec] seconds

The system is experiencing CPU Hog, If this

condition persists for 30 seconds, the node
will be reloaded.

Persistent Hog detected for more than

[dec] seconds

The system is experiencing CPU Hog, If this

condition persists for 30 seconds, the node
will be reloaded.

A monitored device [chars] is above [dec]%

utilization. Current utilization = [dec].
Please remove unwanted user files and
When some monitored disk's usage is
configuration rollback points.
above 99%.
A monitored device [chars] is above [dec]%
utilization. Current utilization = [dec].
Please remove unwanted user files and
When some monitored disk's usage is
configuration rollback points.
above 99%.
A monitored device [chars] is above [dec]%
utilization. Current utilization = [dec].
Please remove unwanted user files and
When some monitored disk's usage is
configuration rollback points.
above 95%.
A monitored device [chars] is above [dec]%
utilization. Current utilization = [dec].
Please remove unwanted user files and
When some monitored disk's usage is
configuration rollback points.
above 95%.

Call to debug_register() failed with error

[dec] ([chars])

An internal error was detected when

registering with the debug library.

Call to debug_register() failed with error

[dec] ([chars])

An internal error was detected when

registering with the debug library.

[chars]: line [dec]: devctl() on file [chars]

failed with error [dec] ([chars])

Failed to open procfs file or directory.

[chars]: line [dec]: devctl() on file [chars]

failed with error [dec] ([chars])

Failed to open procfs file or directory.

An internal error was detected when

[chars]: could not attach handler for Event attaching a handler for an Event Manager
Manager asynchronous event: [chars]
asynchronous event.

An internal error was detected when

[chars]: could not attach handler for Event attaching a handler for an Event Manager
Manager asynchronous event: [chars]
asynchronous event.

[chars]: could not create event manager:

[chars]

An internal error was detected when

creating Event Manager.

[chars]: could not create event manager:

[chars]

An internal error was detected when

creating Event Manager.

[chars]: failed to block waiting for Event

Manager events: [chars]

An internal error was detected when block

waiting for Event Manager events.

[chars]: failed to block waiting for Event

Manager events: [chars]

An internal error was detected when block

waiting for Event Manager events.

[chars]: failed to initialize a sigevent

structure: [chars]

An internal error was detected when trying

to initialize a sigevent structure.

[chars]: failed to initialize a sigevent

structure: [chars]

An internal error was detected when trying

to initialize a sigevent structure.

An internal error was detected when

[chars]: could not attach handler for Event attaching a handler for an Event Manager
Manager synchronous message: [chars]
synchronous message.

An internal error was detected when

[chars]: could not attach handler for Event attaching a handler for an Event Manager
Manager synchronous message: [chars]
synchronous message.

[chars]: unable to initialize event manager An error occured when attempting to

thread: [chars]
initialize the event manager thread.

[chars]: unable to initialize event manager An error occured when attempting to

thread: [chars]
initialize the event manager thread.

An internal error was detected when trying

[chars]: could not set up a managed timer to allocate a managed timer identifier and
identifier: [chars]
assign to it an event handler.

An internal error was detected when trying

[chars]: could not set up a managed timer to allocate a managed timer identifier and
identifier: [chars]
assign to it an event handler.

An internal error was detected when trying

[chars]: could not set up a managed timer to remove a managed timer registration
identifier: [chars]
from an event manager.

An internal error was detected when trying

[chars]: could not set up a managed timer to remove a managed timer registration
identifier: [chars]
from an event manager.

An internal error was detected when trying

[chars]: could not create a managed timer to create a managed timer tree leaf for the
tree leaf: [chars]
event manager.

An internal error was detected when trying

[chars]: could not create a managed timer to create a managed timer tree leaf for the
tree leaf: [chars]
event manager.

Process [chars], pid [dec] is using [dec] file

descriptors out of a max of [dec]. Critical
A process is potentially leaking FDs. Critical
limit ([dec]%) crossed.
limit has been crossed.

Process [chars], pid [dec] is using [dec] file

descriptors out of a max of [dec]. Critical
A process is potentially leaking FDs. Critical
limit ([dec]%) crossed.
limit has been crossed.

[chars]: failed to initialize fault detector:

[chars]

An internal error was detected when

initializing the fault detector.

[chars]: failed to initialize fault detector:

[chars]

An internal error was detected when

initializing the fault detector.

Unable to get address of free memory

variable from kernel.

Wdsysmon was not able to get access to

free memory information from kernel.

Unable to get address of free memory

variable from kernel.

Wdsysmon was not able to get access to

free memory information from kernel.

Failed to init helper lib. [chars]: [chars]

The system failed to initialize helper library.

This is a fatal error for wdsysmon.

Failed to init helper lib. [chars]: [chars]

The system failed to initialize helper library.

This is a fatal error for resmon.

[chars]: could not get channel id from the

channel handler: [chars]

An internal error was detected when trying

to get channel id from a channel handler.

[chars]: could not get channel id from the

channel handler: [chars]

An internal error was detected when trying

to get channel id from a channel handler.

[chars]: unable to initialize process

memory notification thread: [chars]

An error occured when attempting to

initialize the event manager thread.

[chars]: unable to initialize process

memory notification thread: [chars]

An error occured when attempting to

initialize the event manager thread.

[chars]: could not open procfs file or

directory [chars]: [chars]

Failed to open procfs file or directory.

[chars]: could not open procfs file or

directory [chars]: [chars]

Failed to open procfs file or directory.

[chars]: could not get local node name:

[chars]

An internal error was detected when trying

to get local node name through platform
library.

[chars]: could not get local node name:

[chars]

An internal error was detected when trying

to get local node name through platform
library.

[chars]: could not get my slot number

An internal error was detected when trying

to get the slot number of local node
through platform library.

[chars]: could not get my slot number

An internal error was detected when trying

to get the slot number of local node
through platform library.

[chars]: unmatched stack pop operation

An unmatched stack pop operation was

detected.

[chars]: unmatched stack pop operation

An unmatched stack pop operation was

detected.

[chars]: could not create a POSIX thread

An internal error was detected when trying

to create a POSIX thread.

[chars]: could not create a POSIX thread

An internal error was detected when trying

to create a POSIX thread.

Failed to create thread for service [dec],

name [chars]: [chars]

The system failed to create the thread that

provides the indicated service. This is a
fatal error for wdsysmon.

Failed to create thread for service [dec],

name [chars]: [chars]

The system failed to create the thread that

provides the indicated service. This is a
fatal error for resmon.

[chars]: unable to initialize process cpu

watcher thread: [chars]

An error occured when attempting to

initialize the cpu watcher thread.

[chars]: unable to initialize process cpu

watcher thread: [chars]

An error occured when attempting to

initialize the cpu watcher thread.

wd_config_init failed due to sysdb

[chars]: wd_config_init failed, error: [chars] intialization problem.

wd_config_init failed due to sysdb

[chars]: wd_config_init failed, error: [chars] intialization problem.

[chars] [chars]

Set: When some monitored disk's usage is

above 80%. Cleared: When all monitored
disks' usage are below 80%.

[chars] [chars]

Set: When some monitored disk's usage is

above 80%. Cleared: When all monitored
disks' usage are below 80%.

A monitored device [chars] is above [dec]%

utilization. Current utilization = [dec].
Please remove unwanted user files and
When some monitored disk's usage is
configuration rollback points.
above 80%.
A monitored device [chars] is above [dec]%
utilization. Current utilization = [dec].
Please remove unwanted user files and
When some monitored disk's usage is
configuration rollback points.
above 80%.

[chars]: Failed to register for DSC event

with sysmgr, error: [chars]

sysmgr_register_lr_event failed to register

for DSC notification event

[chars]: Failed to register for DSC event

with processsmgr, error: [chars]

sysmgr_register_lr_event failed to register

for DSC notification event

Process [chars], pid [dec] is using [dec] file

descriptors out of a max of [dec]. Major
A process is potentially leaking FDs. Major
limit ([dec]%) crossed.
limit has been crossed.

Process [chars], pid [dec] is using [dec] file

descriptors out of a max of [dec]. Major
A process is potentially leaking FDs. Major
limit ([dec]%) crossed.
limit has been crossed.

Process [chars], pid [dec] is using [dec] file

descriptors out of a max of [dec]. Minor
A process is potentially leaking FDs. Minor
Limit ([dec]%) crossed.
limit has been crossed.

Process [chars], pid [dec] is using [dec] file

descriptors out of a max of [dec]. Minor
A process is potentially leaking FDs. Minor
Limit ([dec]%) crossed.
limit has been crossed.

Process [chars], pid [dec], is now using

[dec] file descriptors. Status is Normal

--

Process [chars], pid [dec], is now using

[dec] file descriptors. Status is Normal

--

[chars]: Failed to poll for memory usage:

[chars]

An error was encountered during

wdsysmon's poll for system memory usage.

[chars]: Failed to poll for memory usage:

[chars]

An error was encountered during resmon's

poll for system memory usage.

Memory threshold crossed: [chars] with

[unsigned int].[unsigned int]MB free

Set: Free memory on this node is below the

reported threshold. Clear: Free memory is
above the MINOR theshold. In both cases,
the amount of free memory in megabytes
is reported.

Memory threshold crossed: [chars] with

[unsigned int].[unsigned int]MB free

Set: Free memory on this node is below the

reported threshold. Clear: Free memory is
above the MINOR theshold. In both cases,
the amount of free memory in megabytes
is reported.

Process [chars][[dec]] (pid [dec]) has

exceeded its memory limit:[dec] kbytes of
heap allowed, [dec] kbytes of heap used.
(Info:[dec] kbytes of virtual shared memory
used).

The process with the indicated name and

pid has allocated more memory than its
memory limit allows. The process will be
restarted.

Process [chars][[dec]] (pid [dec]) has

exceeded its memory limit:[dec] kbytes of
heap allowed, [dec] kbytes of heap used.
(Info:[dec] kbytes of virtual shared memory
used).

The process with the indicated name and

pid has allocated more memory than its
memory limit allows. The process will be
restarted.

New memory state: [chars]

The free memory state of this node has

changed to the indicated state.

New memory state: [chars]

The free memory state of this node has

changed to the indicated state.

[dec]: Process Name: [chars][[dec]], pid:

[dec][chars], Heap usage [dec] Kbytes,
Virtual Shared memory usage: [dec]
Kbytes.

This process is one of the top memory

users in the system. If the system reaches
critical memory exhaustion, this process is
subject to restart or termination. If the
process is listed as 'Killed', then the system
is in the process of recovering the
resources used by the process.

[dec]: Process Name: [chars][[dec]], pid:

[dec][chars], Heap usage [dec] Kbytes,
Virtual Shared memory usage: [dec]
Kbytes.

This process is one of the top memory

users in the system. If the system reaches
critical memory exhaustion, this process is
subject to restart or termination. If the
process is listed as 'Killed', then the system
is in the process of recovering the
resources used by the process.

Top [dec] consumers of system memory

([dec] Kbytes free):

This message is emitted when system

memory usage crosses a threshold in the
direction of increasing memory exhaustion.
The top memory users will follow in the
next messages. There may be a memory
leak or misconfiguration.

Top [dec] consumers of system memory

([dec] Kbytes free):

This message is emitted when system

memory usage crosses a threshold in the
direction of increasing memory exhaustion.
The top memory users will follow in the
next messages. There may be a memory
leak or misconfiguration.

This process is one of the top

sharedmemory users in the system. If the
system reaches critical memory
exhaustion, this process is subject to
restart or termination. If the process is
listed as 'Killed', then the system is in the
[dec]: File/Directory Name: [chars], Kbytes process of recovering the resources used
used: [dec].
by the process.
This process is one of the top
sharedmemory users in the system. If the
system reaches critical memory
exhaustion, this process is subject to
restart or termination. If the process is
listed as 'Killed', then the system is in the
[dec]: File/Directory Name: [chars], Kbytes process of recovering the resources used
used: [dec].
by the process.

Top [dec] consumers of shared memory

([dec] Kbytes free):

This message is emitted when system

memory usage crosses a threshold in the
direction of increasing memory exhaustion.
The top shared memory users will follow in
the next messages. There may be a
memory leak or misconfiguration.

Top [dec] consumers of shared memory

([dec] Kbytes free):

This message is emitted when system

memory usage crosses a threshold in the
direction of increasing memory exhaustion.
The top shared memory users will follow in
the next messages. There may be a
memory leak or misconfiguration.

All registered event managers on this node All event managers are now sending keep
are sending heartbeats.
alive messages as expected.

All registered event managers on this node All event managers are now sending keep
are sending heartbeats.
alive messages as expected.

[chars]: [chars](): [chars]

A system call failed. The calling function,

the failed call, and error are displayed.

A timeout occurred waiting to hear from an

Event manager from process [chars][[dec]] event manager. This could happen as a
created by thread [dec] at [chars] is not
result of a process being deadlocked on
sending heartbeats.
another event.

A timeout occurred waiting to hear from an

Event manager from process [chars][[dec]] event manager. This could happen as a
created by thread [dec] at [chars] is not
result of a process being deadlocked on
sending heartbeats.
another event.

Event manager from process [chars][[dec]] An event manager has resumed sending
created by thread [dec] at [chars] is not
heartbeats. This happens when a condition
sending heartbeats.
that caused the hang is cleared.

Event manager from process [chars][[dec]] An event manager has resumed sending
created by thread [dec] at [chars] is not
heartbeats. This happens when a condition
sending heartbeats.
that caused the hang is cleared.

Process [chars] with event manager not

sending heartbeats has exited.

A process with an event manager that was

not sending heartbeats has exited.

Process [chars] with event manager not

sending heartbeats has exited.

A process with an event manager that was

not sending heartbeats has exited.

CPU hog: cpu [dec]'s sched count is [dec].

Wdsysmon has detected a cpu starvation

situation - potentially a high priority
process spinning in a tight loop. The sched
count is the number of times the
wdsysmon ticker thread has been
scheduled since the last time the
wdsysmon watcher thread ran.

CPU hog: cpu [dec]'s sched count is [dec].

Wdsysmon has detected a cpu starvation

situation - potentially a high priority
process spinning in a tight loop. The sched
count is the number of times the resmon
ticker thread has been scheduled since the
last time the resmon watcher thread ran.

CPU hog: cpu [dec]'s ticker last ran [dec].

[dec] seconds ago.

Wdsysmon has detected a cpu starvation

situation - potentially a high priority
process spinning in a tight loop.

CPU hog: cpu [dec]'s ticker last ran [dec].

[dec] seconds ago.

Wdsysmon has detected a cpu starvation

situation - potentially a high priority
process spinning in a tight loop.

Wdsysmon has detected a cpu starvation

situation - potentially a high priority
process spinning in a tight loop. A high
Rolling average of scheduling times: [dec]. value for the rolling average indicates that
[dec].
a periodic process is not being scheduled.
Wdsysmon has detected a cpu starvation
situation - potentially a high priority
process spinning in a tight loop. A high
Rolling average of scheduling times: [dec]. value for the rolling average indicates that
[dec].
a periodic process is not being scheduled.

Process [chars] pid [dec] tid [dec] prio

[dec] using [dec]% is the top user of CPU.

This message is displayed after the CPU

hog detector trips. It shows the percentage
of CPU used by the busiest thread in the
top consumer of CPU.

Process [chars] pid [dec] tid [dec] prio

[dec] using [dec]% is the top user of CPU.

This message is displayed after the CPU

hog detector trips. It shows the percentage
of CPU used by the busiest thread in the
top consumer of CPU.

Device [chars] usage [dec].

When all monitored disks' usage are below

80%.

Device [chars] usage [dec].

When all monitored disks' usage are below

80%.

Wdsysmon has been told to stop

monitoring the indicated device, even
Alarmed disk [chars] is no longer monitored though the disk is above 90% utilization.
Wdsysmon has been told to stop
monitoring the indicated device, even
Alarmed disk [chars] is no longer monitored though the disk is above 90% utilization.

New dump files created in [chars]

Information captured by various modules

and stored in bootflash during a previous
reset has been moved to hard disk.

New dump files created in [chars]

Information captured by various modules

and stored in bootflash during a previous
reset has been moved to hard disk.

Process [chars] pid [dec] is present in

Dependency List and will not be killed.

This message is emitted if the misbehaving

process is one that wdsysmon depends on.
It will not be terminated.

Process [chars] pid [dec] is present in

Dependency List and will not be killed.

This message is emitted if the misbehaving

process is one that resmon depends on. It
will not be terminated.

This message is emitted if the top CPU user

Top CPU user process [chars] pid [dec] is a is known to use substantial CPU under
known hog.
some circumstances.

This message is emitted if the top CPU user

Top CPU user process [chars] pid [dec] is a is known to use substantial CPU under
known hog.
some circumstances.

Node physical memory < 256MB

This node is not configured with sufficient

memory to enable memory recovery
support.

Node physical memory < 256MB

This node is not configured with sufficient

memory to enable memory recovery
support.

The process with the indicated name and

pid has been killed in an attempt to recover
Process [chars] (pid [dec]) not managed by system memory. Since this process is not
processmgr using [dec] kbytes of heap
managed by processmgr, it may not be
memory will be killed and not restarted.
restarted. The process can be manually
(Info:[dec] kbytes of virtual shared
restarted if desired, but may continue to
memory).
consume large amounts of memory.

The process with the indicated name and

pid has been killed in an attempt to recover
system memory. Since this process is not
Process [chars] (pid [dec]) not managed by managed by sysmgr, it may not be
sysmgr using [dec] kbytes of heap memory restarted. The process can be manually
will be killed and not restarted.(Info:[dec] restarted if desired, but may continue to
kbytes of virtual shared memory).
consume large amounts of memory.

The processmgr process with the indicated

Process [chars][[dec]] (pid [dec]) (managed name and pid has been killed in an attempt
by processmgr) using [dec] kbytes of heap to recover system memory. The process
memory will be killed and not restarted.
can be manually restarted if desired, but
(Info:[dec] kbytes of virtual shared
may continue to consume large amounts of
memory).
memory.

The sysmgr process with the indicated

Process [chars][[dec]] (pid [dec]) (managed name and pid has been killed in an attempt
by sysmgr) using [dec] kbytes of heap
to recover system memory. The process
memory will be killed and not restarted.
can be manually restarted if desired, but
(Info:[dec] kbytes of virtual shared
may continue to consume large amounts of
memory).
memory.

Process [chars][[dec]] (pid [dec]) using

[dec] kbytes of heap memory will be
restarted. (Info:[dec] kbytes of virtual
shared memory).

The processmgr process with the indicated

name and pid has been restarted in an
attempt to recover system memory.

Process [chars][[dec]] (pid [dec]) using

[dec] kbytes of heap memory will be
restarted. (Info:[dec] kbytes of virtual
shared memory).

The sysmgr process with the indicated

name and pid has been restarted in an
attempt to recover system memory.

[chars]: Process-terminate disabled. Pid

[dec] will not be terminated

wdsysmon process-termination is disabled.

A process which meets the kill criteria
(either because it's in deadlock, or it's a
memory or CPU hog - indicated by the first
parameter [%d]) will not be terminated.

[chars]: Process-terminate disabled. Pid

[dec] will not be terminated

resmon process-termination is disabled. A

process which meets the kill criteria (either
because it's in deadlock, or it's a memory
or CPU hog - indicated by the first
parameter [%d]) will not be terminated.

[dec]: Process Name: [chars][[dec]], pid:

[dec][chars], Heap usage: [dec] kbytes,
Virtual Shared memory usage: [dec]
kbytes.

This process is one of the top memory

users in the system. If the system reaches
critical memory exhaustion, this process is
subject to restart or termination. If the
process is listed as 'Killed', then the system
is in the process of recovering the
resources used by the process.

[dec]: Process Name: [chars][[dec]], pid:

[dec][chars], Heap usage: [dec] kbytes,
Virtual Shared memory usage: [dec]
kbytes.

This process is one of the top memory

users in the system. If the system reaches
critical memory exhaustion, this process is
subject to restart or termination. If the
process is listed as 'Killed', then the system
is in the process of recovering the
resources used by the process.

Top [dec] consumers of system memory

([dec] Kbytes free):

This message is emitted when system

memory usage crosses a threshold in the
direction of increasing memory exhaustion.
The top memory users will follow in the
next messages. There may be a memory
leak or misconfiguration.

Top [dec] consumers of system memory

([dec] Kbytes free):

This message is emitted when system

memory usage crosses a threshold in the
direction of increasing memory exhaustion.
The top memory users will follow in the
next messages. There may be a memory
leak or misconfiguration.

This process is one of the top

sharedmemory users in the system. If the
system reaches critical memory
exhaustion, this process is subject to
restart or termination. If the process is
listed as 'Killed', then the system is in the
[dec]: File/Directory Name: [chars], Kbytes process of recovering the resources used
used: [dec].
by the process.

This process is one of the top

sharedmemory users in the system. If the
system reaches critical memory
exhaustion, this process is subject to
restart or termination. If the process is
listed as 'Killed', then the system is in the
[dec]: File/Directory Name: [chars], Kbytes process of recovering the resources used
used: [dec].
by the process.

Top [dec] consumers of shared memory

([dec] Kbytes free):

This message is emitted when system

memory usage crosses a threshold in the
direction of increasing memory exhaustion.
The top shared memory users will follow in
the next messages. There may be a
memory leak or misconfiguration.

Top [dec] consumers of shared memory

([dec] Kbytes free):

This message is emitted when system

memory usage crosses a threshold in the
direction of increasing memory exhaustion.
The top shared memory users will follow in
the next messages. There may be a
memory leak or misconfiguration.

[chars]: [chars]

Mapping to shared memory provided by

cisco_wrapper failed.

[chars]: [chars]

Mapping to shared memory provided by

cisco_wrapper failed.

An internal error was detected when trying

[chars]: could not get an application datum to retrieve an application datum associated
associated with the channel: [chars]
with the given channel handler.

An internal error was detected when trying

[chars]: could not get an application datum to retrieve an application datum associated
associated with the channel: [chars]
with the given channel handler.

[chars]: could not get process id from

message information: [chars]

An internal error was detected when trying

to get process id from the information of a
message.

[chars]: could not get process id from

message information: [chars]

An internal error was detected when trying

to get process id from the information of a
message.

An internal error was detected when trying

[chars]: could not save an application
to save an application datum associated
datum associated with the channel: [chars] with the given channel handler.

An internal error was detected when trying

[chars]: could not save an application
to save an application datum associated
datum associated with the channel: [chars] with the given channel handler.

[chars]: could not decrement the hold

count of the client info data: [chars]

An internal error was detected when trying

to decrement the hold count of the client
info data of a synchronous message.

[chars]: could not decrement the hold

count of the client info data: [chars]

An internal error was detected when trying

to decrement the hold count of the client
info data of a synchronous message.

[chars]: Failed to create notification

context: [chars]

During registration for memory notification,

an internal error prevented the creation of
an internal context structure. The calling
function and detected error are displayed.

[chars]: Failed to create notification

context: [chars]

During registration for memory notification,

an internal error prevented the creation of
an internal context structure. The calling
function and detected error are displayed.

[chars]: could not find the event manager

context by timeout timer [pointer]

An internal error was detected when trying

to find the event manager context by the
given timeout timer.

[chars]: could not find the event manager

context by timeout timer [pointer]

An internal error was detected when trying

to find the event manager context by the
given timeout timer.

[chars]: could not connect to the message

channel [chars]: [chars]

An internal error was detected when

attaching a handler for an Event Manager
asynchronous event.

[chars]: could not connect to the message

channel [chars]: [chars]

An internal error was detected when

attaching a handler for an Event Manager
asynchronous event.

[chars]: could not disconnect a message

channel: [chars]

An internal error was detected when trying

to disconnect a message channel.

[chars]: could not disconnect a message

channel: [chars]

An internal error was detected when trying

to disconnect a message channel.

[chars]: could not send the message:

[chars]

An internal error was detected when trying

to send a message.

[chars]: could not send the message:

[chars]

An internal error was detected when trying

to send a message.

[chars]: could not send the sigevent:

[chars]

An internal error was detected when trying

to send a sigevent to the client that last
sent a message on the connection.

[chars]: could not send the sigevent:

[chars]

An internal error was detected when trying

to send a sigevent to the client that last
sent a message on the connection.

[chars]: unknown message type [dec]

A message with an unknown type was

received.

[chars]: unknown message type [dec]

A message with an unknown type was

received.

[chars]: not enough memory: [chars]

Allocating memory failed due to a lowmemory condition.

[chars]: not enough memory: [chars]

Allocating memory failed due to a lowmemory condition.

[chars]: The sched_get_priority_max()

function returned an error; [chars]

The sched_get_priority_max() function

returned an error which is indicated in the
message.

[chars]: The sched_get_priority_max()

function returned an error; [chars]

The sched_get_priority_max() function

returned an error which is indicated in the
message.

[chars]: The sched_setscheduler() function The sched_setscheduler() function returned

returned an error; [chars]
an error which is indicated in the message.

[chars]: The sched_setscheduler() function The sched_setscheduler() function returned

returned an error; [chars]
an error which is indicated in the message.

[chars]: [chars](): [chars]

A system call failed. The calling function,

the failed call, and error are displayed.

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error.

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error.

Fabric ping failed. Send critical alarm to

shelf manager to reset the node.

HA Health Monitor Fabric ping failed

HM fabric ping detected [unsigned int]/

[unsigned int] corrupted packets

HA Health Monitor Fabric ping failed. When

a received ping response does not match
the transmitted ping, this indicates some
kind of cell corruption or cell loss in the
fabric or edges of the fabric.

[chars], reason: [chars]

HA Health Monitor failed to initialize due to

internal software errors

HM fabric ping only completed [unsigned

int] of [unsigned int] pings (ret = [hex])

HA Health Monitor Fabric ping test

sequence failed to complete. If there were
any errors before it got disrupted, then
these are reported separately. The test will
be restarted again at next HM fping
interval. If there are no other errors
reported, this warning is rarely a cause for
concern, unless it very frequently causes
only a partial set of HM fabric pings to be
completed.

Fabric ping test failed for attempt: [dec],

Node will be reset after [dec] retries

HA Health Monitor Fabric ping failed but

will retry again

initialization error: [chars]: [dec] ([chars])

An error was encountered during

intialization of the checkpoint library. The
message should indicate the error
condition. This is most likely due to a
coding error.

Unable to register LRd's bag structures.

'[chars]'

LRd was unable to register bag structures.

Unable to register LRd's bag structures.

'[chars]'

LRd was unable to register bag structures.

Failed to allocate %zd bytes of memory:

[chars]

This is a generic error msg for memory

allocation failure. The Process tried to
allocate a memory and it wasn't succesful.
Can happen when system is running low in
memory

Failed to allocated [dec] bytes of memory:

[chars]

Failure in lrd_inv_dll memory allocation

error occurred condition.

Failed to allocated [dec] bytes of memory:

[chars]

The requested operation could not be

accomplished because of a low memory
condition.

Failed to allocated [dec] bytes of memory:

[chars]

The requested operation could not be

accomplished because of a low memory
condition.

[chars], mlr configuration info is NOT

available yet, error: [chars], retrying...

Failed to get the MLR configuration

information.

Could not register dll with error services:

[chars]

The API call to register the dll failed.The

system may not function properly.

Could not register dll with error services:

[chars]

The call to register the dll using

cerr_register_dll failed.

Could not register dll with error services:

[chars]

The call registers the dll using

cerr_register_dll failed.

Could not register dll with error services:

[chars]

The call register the dll using

cerr_register_dll failed.

Error forwarding inventory: '[chars]'

LRd was unable to read or write

information needed to forward inventory in
Admin space to the LR Plane.

Error forwarding inventory: '[chars]'

LRd was unable to read or write

information needed to forward inventory in
Admin space to the LR Plane.

Unrecognized redundancy state [dec]

LRd doesn't recognize redundancy state.

Unrecognized redundancy state [dec]

LRd doesn't recognize redundancy state.

sysdb_item_[chars]([chars]) returned
'[chars]'

SysDB returned an error to LRd.

sysdb_item_[chars]([chars]) returned
'[chars]'

SysDB returned an error to LRd.

LR daemon library could not find the dSC.

LRdlib could not find the designated Shelf

Controller.

LR Daemon library could not find the dSC.

LRdlib could not find the dSC.

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error, but may help
with debugging other problems elsewhere!

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error, but may help
with debugging other problems elsewhere!

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error, but may help
with debugging other problems elsewhere!

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error against on LRD,
but may help with debugging other
problems elsewhere!

WARNING: A node with unknown type or a

non RP/DRP node [chars] is used as
primary for SDR

This is an informational message output

during SDR configuration commit time only
if a non-RP or non-DRP node is being
assigned as primary to the SDR. Please
note that if the node is not in IOX-RUN
state, it's node type will not be determined.

LRd has reset the DRP '[dec]' to

accomodate new pairing configuration.

The DRP pairing configuration was

changed. The card entering or leaving the
pair needs to be reset in order to
accomodate the new configuration.

LRd has reset the DRP '[dec]' to

accomodate new pairing configuration.

The DRP pairing configuration was

changed. The card entering or leaving the
pair needs to be reset in order to
accomodate the new configuration.

LRd has reset the card in slot '[dec]'

because it was assigned to a new LR.

The DRP pairing configuration was

changed. The card entering or leaving the
pair needs to be reset in order to
accomodate the new configuration.

WARNING: A unpaired DRP node [chars] is

being added as primary to SDR

This is an informational message output

during SDR configuration commit time only
if an unpaired DRP node is being assigned
to an SDR.

event attach failure. [chars] [hex]

The LR Daemon encountered an error when

registering for synchronous or
asynchronous events.

Error:[chars] failed to get state of the node Error seen while trying to fetch the state of
event : [hex]
the given node event.

Error: [chars]:[dec], Could not find the

node/pair to remove

Attempt to remove a node from a pair that

did not containt the node or it could be an
attempt to remove the pair which doesn't
exist.

sysmgr get node state failure: [chars].

sysmgr_get_node_state failed.

node role change registration with sysmgr

failed: [chars].

API for registering node state change with

sysmgr failed. This change will be
registered later.No impact on running of
process.

[chars] [chars] unhandled event type [hex]

recieved
This type of event is not handled.

Unable to register LRd's bag structures.

'[chars]'

LRd was unable to register bag structures.

Failed to bind to [chars]: '[chars]'

sysdb_bind failed to bind to inventory

source.

[chars] [chars]

Encountered an error condition.

[chars]:[dec] Failed to extract rsi for [hex]

Failed to extract the fields of relevant node

id. i.e rack, slot, inst.

[chars] Error getting lr inventory for lrid

[dec] ret: [dec]

Failed to get the lr inventory.

[chars]: Failed to init gs vector. Return

value = [dec]

Initialization of gs vector failed.

Failed to allocate %zd bytes of memory:

[chars]

This is a generic error msg for memory

allocation failure. The Process tried to
allocate a memory and it wasn't succesful.
Can happen when system is running low in
memory

Could not register dll with error services:

[chars]

The call register the dll using

cerr_register_dll failed.

Could not register dll with error services:

[chars]

The call register the dll using

cerr_register_dll failed.

Could not register dll with error services:

[chars]

The call register the dll using

cerr_register_dll failed.

Couldn't create nodeid for rsi [hex]/[hex]/

[hex]

Failed to create node id.

sysdb item returned [hex] '[chars]'

SysDB returned an error to LRd.

[chars] encountered unhandled debug op

[dec]

The debug option chosen is not handled.

[chars]-E-lr_id [dec] is bogus

The value of lr ID is either <-1 or >7, which

is wrong.

LR Daemon library could not find the dSC.

LRdlib could not find the dSC.

LR Daemon library could not find the dSC.

LRdlib could not find the dSC.

LR Daemon library could not find the dSC.

LRdlib could not find the dSC.

Headless SDR condition detected,

reloading local node.

Headless SDR condition was detected. The

local card is being reset. This is not
necessarily an error condition!

Signalling SDR Plane Ready for SDR [chars]

([dec]) (mgmt nodes [dec] of [dec] are NOT SDR Plane ready is being signalled due to
READY yet) -[chars]
SDR plane ready timeout.

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error, but may help
with debugging other problems elsewhere!

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error, but may help
with debugging other problems elsewhere!

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error, but may help
with debugging other problems elsewhere!

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error, but may help
with debugging other problems elsewhere!

Management node [hex] in SDR [chars]

([dec]) is READY after SDR Plane Ready is
signalled

A management node in the specified SDR

came up after SDR Plane ready for that
SDR was signalled.

[chars]: [chars]: [hex]: [chars]

A redcon client API failed in the indicated

function, for the specified reason.

[chars]: Failed to send [chars] message to

redcon: [hex]: [chars]

An attempt to send a message to the

redcon server failed with the specified
reason. It may be the case that redcon had
been restarted.

backup process groups between [chars]

and [chars] are NOT ready

RMF has determined that the backup

process groups are NOT ready because of
the failure of one or more events the
prevent it from being in-sync with the
primary process groups.

backup process groups between [chars]

and [chars] are ready

RMF has determined that the backup

process groups on the specified card are
ready to take over as primary if it needs to.

standby card is NOT ready

Redcon has determined that the standby

card is NOT ready because of the failure of
one or more events the prevent it from
being in-sync with the active card.

standby card is NOT ready

RMF has determined that the standby card

is NOT ready because of the failure of one
or more events the prevent it from being
in-sync with the active card.

standby card is ready

Redcon has determined that the standby

card is ready to take over as active card if
it needs to.

standby card is ready

RMF has determined that the standby card

is ready to take over as active card if it
needs to.

RMF has attempted to call the platformspecific redundancy driver initialization

initilization of the redundancy driver failed function, but the call failed after several
after [dec] attempts
attempts.
Redcon has attempted to call the platformspecific redundancy driver initialization
initilization of the redundancy driver failed function, but the call failed after several
after [dec] attempts
attempts.

Redcon unable to register with PCDS

infrastructure.

An unexpected error condition

encountered.

RMF unable to register with PCDS

infrastructure.

An unexpected error condition

encountered.

Unexpected: [chars]: [chars]: [hex]

An unexpected error condition

encountered.

[chars]

Set: When the backup process groups

remain in not ready state for a prolonged
period. Cleared: When the card where the
backup process groups are located is
removed, reset or goes ready.

JID [dec], node [chars], group [chars],

process [chars] set the backup not ready:
[chars]

The named process has set the backup

process group in a not ready state with the
supplied reason.

Connection to [chars] failed - retrying...

RMF failed to establish a connection to RMF

on the another card.

Failover has been disabled by config

Redcon has notified the card failover has

been disabled by the configuration.

failover has been requested by operator,

waiting to initiate

RMF on the active card has been told to

failover by request

failover has been requested by operator,

waiting to initiate

Redcon on the active card has been told to

failover by request

client not registered to set SRP not ready : An unexpected error condition
[chars]
encountered.
client ([unsigned int],[chars]) is using
unregistered reason string to set SRP not
ready: [chars]

An unexpected error condition

encountered.

[chars]

Set: When the standby remains in not

ready state for a prolonged period. Cleared:
When the standby is removed, reset or
goes ready.

[chars]

Set: When the standby remains in not

ready state for a prolonged period. Cleared:
When the standby is removed, reset or
goes ready.

JID [dec], node [chars], process [chars] set The named process has set the standby in
the standby not ready: [chars]
a not ready state with the supplied reason.

JID [dec], node [chars], process [chars] set The named process has set the standby in
the standby not ready: [chars]
a not ready state with the supplied reason.

Notice to go active: Card not ready and will RMF attempted to go active without the
be reset
card ready - reset card

Notice to go active: Card not ready and will Redcon attempted to go active without the
be reset
card ready - reset card

Connection to [chars] failed - retrying...

Redcon failed to establish a connection to

redcon on the standby card.

Notice to go active: Not ready but forced

failover has been allowed

Redcon has been forced to go active even

though the card is not ready.

Notice to go active: Not ready but forced

failover has been allowed

RMF has been forced to go active even

though the card is not ready.

Failed to initialize [chars]: [hex]:[chars].

RMF failed to initialize a module.

connection to backup process group

location [chars] is DOWN

RMF has determined that the connection to

the backup process groups location has
gone down.

connection to backup process group

location [chars] is UP

RMF has determined that the connection to

the backup process groups location has
been succesfully completed.

this card going active

The card is going active.

this card going active

The card is going active.

The card has process groupss going to

this card has process groups going backup backup state.

The card has process groups going to

this card has process groups going primary primary state.

this card going standby

The card is going standby.

this card going standby

The card is going standby.

connection to standby card is DOWN

Redcon has determined that the

connection to the standby card has gone
down.

connection to standby card is DOWN

RMF has determined that the connection to

the standby card has gone down.

connection to standby card is UP

RMF has determined that the connection to

the standby card has been succesfully
completed.

connection to standby card is UP

Redcon has determined that the

connection to the standby card has been
succesfully completed.

RMF has determined that the standby card

has backup process groups which are NOT
ready because of the failure of one or more
This card is standby and its backup process events the prevent it from being in-sync
groups are NOT ready
primary process groups.
RMF has determined that the standby card
This card is standby and its backup process is ready to take over as primary if it needs
groups are ready
to.

This card is standby and is NOT ready

Redcon has determined that the standby

card is NOT ready because of the failure of
one or more events the prevent it from
being in-sync with the active card.

This card is standby and is ready

RMF has determined that the standby card

is ready to take over as active card if it
needs to.

This card is standby and is ready

Redcon has determined that the standby

card is ready to take over as active card if
it needs to.

Failover has been enabled by config

Redcon has notified the card failover has

been enabled by the configuration.

msg_send [chars] failed [chars] [dec]

Redcon attempted to call msg_send but it

failed.

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error.

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error.

Failed to create thread for service [dec],

name [chars]: [chars]

The system failed to create the thread that

provides the indicated service. This is a
fatal error for redstatsd.

[chars]: [chars](): [chars]

A system call failed. By system call, it

means that calls like getting a nodeid,
extracting fields from the nodeid or some
tracing function initialization etc. This is
clearly a software related message. Under
such failure conditions, whichever function
wanted to use the values that was
supposed to be returned by that system
call, will not be able to proceed further.
Following the error there is no automatic
correction applied to resolve the issue.
These errors are usually seen during
initialization or the redstatd process
restarts.

Unexpected: [chars]: [hex] : [chars]

An unexpected condition encountered.

These conditions are typically seen with
EDM registration calls, bag initialization,
edm event manager creation etc. So most
of these conditions mean that there are
some issues regarding EDM processing in
general. This is a software related
condition. When these conditions are seen,
some EDM related piece of software did not
successully complete. Apart from giving
this condition through a message on the
console, there is no automatic correction or
resolution that happens following this

[chars]: [chars]: [hex]: [chars]

A rmf client API failed in the indicated

function, for the specified reason.

[chars]: Failed to send [chars] message to

rmf: [hex]: [chars]

An attempt to send a message to the rmf

server failed with the specified reason. It
may be the case that rmf had been
restarted.

[chars]: [chars], ([unsigned int])

A shared memory for statistics area might

be corrupted.

[chars]: [chars], version: [unsigned int],

magic: [hex]

A shared memory for statistics area might

be corrupted.

[chars]: Error. initializing shared memory.

([chars])

Failed to initialize the shared memory.

[chars]: [chars](): [chars]

A system call failed. Error reason will be

displayed on the console.

Encoding of [chars] requires [dec]B

exceeds available space ([dec]B)

A System or Rack scoped advertisement

has not been correctly distributed to all
relevant nodes in the system. Depending
on the service name identified in the
message, features requiring that service
might be impacted.

Group [unsigned int] isolated from the

network core

All configured backbone interfaces for the

ICCP group are down.

Group [unsigned int] no longer isolated

from the network core

At least one configured backbone interface

for the ICCP group is up.

Neighbor [chars] for group [unsigned int],

[chars]

An ICCP neighbor has changed state

(up/down).

ICCP Backbone Interface [chars] for group

[unsigned int], changed state to [chars]

The configured backbone interface

changed state.

Redundancy Group Manager encountered

an unexpected error while defining a batch
Unexpected error [chars] batch of FRR RIB of updates to be sent to the RIB. This is an
updates ([dec])
internal programming error.

Failed to initialize [chars], because of

[chars]

Initialization of RGMGR process failed to

complete.

Unexpected error sending a batch of RIB

updates ([dec])

Redundancy Group Manager encountered

an unexpected error while sending a batch
of FRR updates to the RIB. This may be a
resource starvation problem, or a problem
with RGMGR's connection to the RIB, or an
internal programming error.

SLA Profile Manager ignoring duplicate

packet type capability [chars].

SLA Profile Manager encountered a packet

type capability for which it already has an
entry that differs in configuration. This new
capability will be ignored. This state
indicates a programmatic error of the SLA
clients as either multiple SLA clients are
trying to register the same capability of a
single client is trying to register the same
capability twice but with different
configuration.

SLA Profile Manager failed to initialize

[chars]: [chars]

The SLA Profile Manager failed to initialize

correctly, and will now exit. It should be
restarted by SysMgr.

The SLA Client Library received a profile

that could not be created. This indicates
that there was insufficient memory for
creation of the profile and its associated
SLA Client Library received profile [chars] data. Any operations configured to use this
from the Profile Manager that could not be profile will not become active until the
created: [chars]
profile is successfully created.

SLA Client Library failed to setup the

operations using profile [chars]: [chars]

The SLA Client Library failed to setup the

operations configured to use the profile
following the configuration of the profile.
This indicates that there was insufficient
memory for the setting up of operations
and these operations will not start running
until they are successfully set up.

SLA Client Library failed to update

operations using profile [chars] following
profile configuration change: [chars]

The SLA Client Library failed to update the

operations configured to use the profile
following a change to the configuration of
the profile. This indicates that there was
insufficient memory to meet the
requirements of the new configuration and
these operations will not start running until
they are successfully set up again.

SLA Client Library received update for

profile [chars] from the Profile Manager
that could not be applied: [chars]

The SLA Client Library received updated

configuration for a profile and the update
could not be applied locally. This indicates
that there was insufficient memory for
modification of the profile and its
associated data. Any operations using this
profile have been suspended and their
associated metrics removed until the
profile is successfully updated.

The SLA Client Library has failed to resync

the configured profiles with the Profile
Manager after one minute of retrying.
Further retries will be attempted every 30
seconds. Until the client is resynced with
the SLA Profile Manager any recent
additions or changes to profile
SLA Client Library distribution module
configuration will not be acted upon. Note:
failed to resync the configured profiles with if SLA is not configured for the protocol
the Profile Manager after one minute of
which emitted this error message there is
retrying: [chars]
no effect and this error can be ignored.

The SLA Profile Manager has failed to

resync the configured profiles with its
clients after one minute of retrying. Further
retries will be attempted every 30 seconds.
SLA Profile Manager distribution module
Until the clients become resynced with the
failed to resync the configured profiles with SLA Profile Manager any recent additions or
its clients after one minute of retrying:
changes to profile configuration will not be
[chars]
acted upon.

SLA Profile Manager failed to process

events: [chars]

The process failed to process incoming

events, and will exit. It should be restarted
by System Manager and resynchronize its
internal state.

Failed to respond to operation [chars]

request: [chars]

An error occurred while handling a request

from the management thread to the data
thread; the data thread was not able to
respond to the management thread.

Failed to [chars] lock: [chars]

A system error was encountered when

attempting to acquire or release a mutex.
In rare circumstances, this may result in
unexpected behaviour in the SLA library,
incorrect statistics or unexpected restart of
the protocol process.

SLA Client Library failed to cleanup (or

initiate cleanup of) on demand operation
[unsigned int], [chars]. This must be
manually cleared

The SLA Client Library either failed to

cleanup the on demand operation or failed
to start a timer to cleanup the operation on
its expiry. There will be no retry attempt to
clean this operation up and until it is
cleaned up manually the associated
system resources will still be in use.

SLA Profile Manager failed to cleanup

[chars]: [chars]

The SLA Profile Manager failed to cleanup

correctly. It will exit anyway, and no further
errors should be seen.

Failed to schedule processing of probe

results: [chars]

An error occurred while attempting to

schedule processing of the the queue of
probe results. As a consequence, the
results for any current probes may not be
recorded in the database.

Probe scheduling error for operation

'[chars]': [chars]: [chars]

An error occurred while scheduling a probe,

or scheduling a packet within a probe. This
could indicate a resource issue. The impact
of this error is that some results will be
missing for this operation; in some cases,
no further results will be collected for this
operation.

SLA has a limit on the number of packets in

a probe that have been tracked as sent,
but for which no result has been returned
by the protocol. Once this limit is hit,
further packets in the probe are not
marked as sent, and will eventually be
marked as lost (timed out). This error can
The limit on the number of
only occur for probes containing a large
unacknowledged sent packets ([unsigned number of packets. It may be triggered by
int]) has been hit; further packets for some network problems, where all SLA packets
probes will be marked as lost.
are being dropped.

Unable to signal that process is exiting:

[chars]

The process has failed to inform System

Manager that it is shutting down. The
process will exit anyway, but it is possible
that any configuration entered will not
cause SysMgr to restart the process. In this
case, a timeout will occur when committing
configuration, and the config will fail to
apply.

Unexpected protocol error: [chars]

An error has been detected in the

information passed to the SLA
infrastructure by the protocol process. This
could cause missing SLA results or other
unexpected behaviour.

SLA Profile Manager found configuration for

a profile that was previously valid but has
since become invalid. This will most likely
be the result of the profile's packet type
changing its capabilities resulting in invalid
SLA Profile Manager found profiles that are configuration. This invalid configuration will
no longer valid due to configuration errors. not be applied to the profile and a
Run the SLA configuration-errors show
configuration error will be present against
command for each SLA protocol for details. the profile.

SLA on-demand operation [unsigned int],

[chars] has finished. The results will be
available for up to two weeks.

The SLA Client Library has finished

processing an on demand operation. The
metrics collected for this shall exist for two
weeks before being automatically cleaned
up if not manually cleared before then.

SLA Client Library database module has

cleaned up whilst there were still
operations in the database

SLA Client Library database module

cleaned up whilst there were still
operations in the database causing a
memory dump of the Client Library to be
taken. This has been caused by other
modules failing to cleanup properly whilst
shutting down the library.

SLA Client Library received profile [chars]

from the Profile Manager that failed
verification: [chars]

The SLA Client Library received a profile

that failed verification. This indicates that
the criteria that the Client Library is using
to verify profiles differs from that used by
the Profile Manager. This may occur around
process restart of the protocol or Profile
Manager. Any operations using this profile
shall be suspended and their associated
metrics removed.

During a resync of the SLA Client Library

profile [chars] was found to no longer be
valid and shall be discarded

The SLA Client Library is discarding a

profile that was found to no longer be valid
during a resync. Any operations using this
profile shall be suspended and their
associated metrics removed.

SLA Client Library database module shared

memory window has been reset. This may
have been caused by the process
restarting whilst the shared memory
window was in an invalid state or a change
SLA Client Library database module shared to the database that is not safe over
memory window has been reset
upgrade.

Unable to open boot variable file '[chars]',

error: [chars]

Either the NVRAM file system is in error, or

the boot-variable infrastructure is behaving
incorrectly. A file required for carrying out
the current request or operation could not
be opened, so processing of the operation
will halt. The boot variables may not be
available to the system.

Unable to write boot variable

'[chars]=[chars]', error: [chars]

Either the NVRAM file system is in error, or

the boot-variable infrastructure is behaving
incorrectly. A file required for carrying out
the current request or operation could not
be written to, so processing of the
operation will halt. The boot variables may
not be available to the system.

Could not register DLL '[chars]' with error

services: [chars]

The error services failed to register the

errors of the specified DLL. The system will
continue to operate, but error or warning
messages displayed to the customer may
not be complete.

An internal error has occurred in an

application that has caused it to pass
invalid data to the boot-variable
Invalid parameter ([chars]) passed to boot- infrastructure. The operation in progress
variable infrastructure
may not be carried out.

Unexpected NULL ptr passed to bootvariable infrastructure

An internal error has occurred in an

application that has caused it to pass
invalid data to the boot-variable
infrastructure. The operation in progress
may not be carried out.

Unable to write boot variable

'[chars]=[chars]'. [dec] byte write buffer
exhausted.

Boot variable has exceeded the maximum

size.

[chars]

Errors from the fw server.

[chars]

Information about the firmware client

operation.

Destination path of the file: [chars], \ Bytes

of file copied: [dec] bytes, \ Time for
copying file: [dec] miliseconds, \ MD5 of
the file on destination: [chars] \ File Tranfer Information about the firmware file that is
rate: [dec] bytes/millisecond
copied by the firmware client

Local access path of the file: [chars], \ Size

of the file: [dec] Bytes, \ MD5 of the file:
[chars], \ Access to the file: [chars], \ This Information about the firmware file that is
file is being: [chars]
impacted by the install

Error processing file-path string : [chars]:

[chars]

'One of the function arguments is NULL.'

Device '[chars]' is full. Remove all noncritical files and reload the node.

An attempt to open or write to a file on the

specified device failed because the device
had insufficient free space. The node may
be in an inconsistent state due to a missing
or truncated file; check for other messages
from applications. Remove non-critical files,
such as core files and user-created files,
and reload the node to re-sync its files. If
this is a management node such as an RP,
consider using 'install remove' to free up
space by removing inactive packages.

Could not register tracing, error: [chars]

Failed to register ltrace context structure.

Tracing will not be functioning properly.

Unexpected null pointer passed to the

Install infrastructure

A client of the Install infrastructure passed

a NULL pointer. The current request or
operation may not be carried out.

The dSDRSC was unavailable for

downloading software from.

The node requires software that is only

available on the dSDRSC. It cannot
continue booting until the dSDRSC
becomes available. If this node is supposed
to become the dSDRSC then it is missing
software that it requires to operate.

dumpifs utility reported error while

extracting [chars] [chars] [chars] : [chars]

The dumpifs utility reported errors while

extracting IFS2 file from bootimage into
shared memory

Insthelper encountered a fatal error

Insthelper encountered a fatal error
condition, and is exiting: Operation =
condition, and cannot proceed. Check the
([chars]), Error value = [hex], Error string = operation, error value and error string to
([chars])
determine what has happened.

Insthelper was unable to warm-reload the

node, error: [chars]. Going ahead to coldreload the node

The installation required a warm-reload of

the node, but the warm-reload failed. The
install will be effected by a cold reload of
the node.

Insthelper failed to download package

'[chars]', error: [chars].

Insthelper was unable to download the

package. The node may come up as a
dSDRSC successfully without this package
(only possible if the package is not an
active package) in which case this package
will not be present on that SDR, and should
be added if required.

Install reported a file compression error:

[chars]

The Install File Compression library

reported errors, and was unable to write a
file. This may be due to file corruption.

The packaging infrastructure detected

insufficient diskspace: [unsigned long long
int] bytes available on [chars]. Please
recover some space on this device and
restart insthelper. Alternatively, use the
Disk does not have sufficient space for
'install boot-options format location [chars]' insthelper to continue on. The difference
command in admin mode and then reload from 'INSUFFICIENT_DISKSPACE' is node is
this node.
not being held in MBI.

Insthelper on non-dSC management nodes

requires the same install device as instdir's
install device on dSC. However, after
Insthelper detected that the required install waiting for some time, the required install
device ([chars]) did not become available device did not become ready. If it was a
after waiting for [dec] seconds. Error:
managed node, then its bootflash device is
[chars]
not available.

The packaging infrastructure detected

insufficient diskspace: [unsigned long long
int] bytes available on [chars]. This node
will be held from proceeding further. Please
recover some space on this device.
Alternatively, use the 'install boot-options
format location [chars]' command in admin Disk does not have sufficient space for
mode and then reload this node.
insthelper to continue on.

MBI download failed, error: [chars]

DRP MBI copying failed. This card will not

be able to boot.

Could not complete operation due to lack

of memory: could not allocate %zu bytes

The requested operation could not be

accomplished because of a low memory
condition.

Managed node running software on a non

persistent device. Software changes are
directed to memory.

A Managed node is running software from a

non persistent device when it was
instructed to use a persistent device at
bring up time. Persistent device not
available so software will be stored in
memory. Expect longer boot times. The
node will continue to operate on a besteffort basis but should be looked at soon.
You may see out-of-memory errors and
problems with package activations on the
node.

Install helper encountered a system

resource error: [chars] ([dec])

A non fatal run time error has occured

caused by insufficient system resources

Can't find persistent device to store

packages. Continuing with memory
instead.

Could not find the persistent device on a

managed device when the instdir
instructed to store packages on it.
Proceeding to use memory instead of the
expected persistent device. Expect longer
boot times. The node will continue to
operate on a best-effort basis but should
be looked at soon. You may see out-ofmemory errors and problems with package
activations on the node.

This node has been booted with the wrong

image type. Composite has already been
used to boot dSC at [chars]. Please boot
insthelper detected that a wrong image has
this node with an MBI image.
been booted.

Selected device could not be formatted for

Selected install device '[chars]' failed to be one reason or another. Performing removal
formatted. Attempting to remove only
of packages and MBIs from the device to
packages and MBIs from the device ...
see if we can continue.

Insthelper is formatting device [chars]

Either due to a format directive at

turboboot time, or because the indicated
device is not available, insthelper will now
try to (re)format the device to make it
available.

The packaging infrastructure detected

sufficient diskspace has become available
on device [chars].

The device now has enough diskspace for

install code to proceed.

On bootup the node attempted to contact

the Install Director on the dSC. The Install
Director was contacted and informed the
node that it could not boot because an
installation was in progress. The Install
Director then became unavailable.
Therefore, to ensure that this node boots
from an up to date Install Director it will
reboot itself after a sufficient pause to
This node is pausing for [dec] seconds prior ensure that the node the previous Install
to rebooting itself following an attempt to Director was on has had time to reboot.
boot during an installation
This message will only be seen on an RP.

On bootup the node attempted to contact

the Install Director on the dSC. The Install
Director was contacted and informed the
node that it could not boot because an
installation was in progress. The Install
Director then became unavailable.
Therefore, to ensure that this node boots
from an up to date Install Director it will
This node is rebooting following an attempt reboot itself. This message will only be
to boot during an installation
seen on an RP.
Node '[chars]': software mismatch,
resetting self...

Status information after two or more nodes

were brought in parallel during the initial
boot of the system.

The dSC node was booted with an incorrect

MBI. There are a few cases where this can
occur: 1) User manually boots an MBI that
is different from the MBI that RP should
boot. 2) User manually sets BOOT
ROMMON variable that is different from the
MBI that RP should boot. 3) An install
causing an MBI change without 'install
commit' will have the BOOT ROMMON
This node was booted with an incorrect MBI variable set to MBI from uncommitted
([chars]), rebooting self with correct boot
software set if the dSC is subsequently
image ([chars]).
rebooted.

Nodes can not boot up while the platform

determines that they have to be held in
This node is attempting to boot while it has MBI. Once the platform lifts the hold then
to be held in MBI. The node will not be
the node will be allowed to complete its
allowed to boot up further until the hold is boot as normal. recommended_action:
lifted.
*NONE*

This node is attempting to boot while an

install is in progress. The node will not be
allowed to boot up further until the install
has completed.

Nodes can not boot up mid-install as this

will invalidate the runnning software set.
Once the install has completed then the
node will be allowed to complete its boot
as normal.

download of new MBI from RP complete

(autobake complete)

Status information for completion of MBI

download.

As part of install operation [unsigned int]

this node ([chars]) will [chars]reload.

The installation required a reload of this

node, and this is now going ahead.

MBI download complete, rebooting self with Status information after MBI download to
new boot image
local flash.

Attempt to clean path on non-boot device

[chars] (boot device [chars])

Install helper made an attempt to clean a

path that wasn't on the specified boot
device.

Successfully cleaned stale packages &

meta-data

Clean successfully completed.

Successfully sync'ed packages & metadata.

Sync successfully completed.

Found integrity issue with digest backup

file, digest table not restored, all the
packages will be copied again..

The digest backup file is found being

tempered with, insthelper will discard the
file, and all the packages will be copied
again.

Failed to receive an event [[chars]]

Either an operation requested of the Install

infrastructure has not been received
successfully (and hence hasn't been
processed), or an invalid message has
been sent to the Install infrastructure. The
Install infrastructure should continue to
operate as expected for subsequent
requests.

The Install Helper failed to sync the local

Failed to sync activated packages & meta- cache of active directories from remote
data.
node.

Failed to copy from '[chars]' to '[chars]'.

The Install Helper failed to copy the

directories from remote node to local node.

Failed to [chars] file '[chars]', error: [chars] The Install Helper failed to read/write a file

Failed to update loadpath ([chars]), error:

[chars]

The Install Helper failed to update the

LOADPATH for the node.

Failed to disconnect from install manager.

The Install Helper failed disconnect from

install manager server.

Install helper failed to clean stale packages

& meta-data, error: [chars]
Clean successfully completed.

Failed to stat '[chars]', error: [chars]

The Install Helper failed to stat a file.

Failed to sync packages & meta-data.

The Install Helper failed to sync the local

cache of install directories from remote
node.

Failed to notify sysmgr about change in

LOADPATH.

The Install Helper failed to notify sysmgr

about change in LOADPATH.

Failed to create a thread, error: [chars].

The Install Helper failed to create a thread.

Failed to initialize the memory cache on

this node (details: [chars])

The memory cache owner failed to initialize

the memory cache. The install
infrastructure will continue to work, but the
booting time for nodes may be slow.

Failed to connect to an SDS, trying Install

Director directly.

A node was unable to connect to a

Software Download Server and will try to
directly connect to the Install Director on
the dSC as a result. This may be due to a
failure in updating the LRd inventory
following a change in the state of an SDS.
The install operation should download
software directly from the dSC and should
not be impacted. However, if many nodes
attempt to get software directly from
instdir other processes may be impacted
by high CPU usage.

retrying to contact sysdb after %zd

seconds

Insthelper was unable to connect to local

sysdb, insthelper will retry

Failed to open file '[chars]', error [chars]

Failed to open the specified required file, so

processing of the current request or
operation will halt. The filesystem may be
in error, or the Install infrastructure may be
behaving incorrectly.

Initialization failed [[chars]], error: [chars]

An error occurred during initialization. The

Install infrastructure will not be able to
function.

Internal error: [chars]

An internal software error occurred.

Internal error: [chars] val [dec]

An internal software error occurred.

Reply from install director indicated that

the passed in node [chars] was incorrect

Install director detected that the passed in

node was incorrect.

Error while processing notification: [chars], The Install Helper failed to extract the
error: [chars].
notification information.

Failed to [chars], error: [chars]

There was an internal locking problem

within the Install Helper.

downloading new MBI from RP (autobake in Status information while starting MBI
progress)
download.
Unexpected null pointer passed to Install
infrastructure

Unexpected parameter value passed to

function.

MBI running; starting software download

Status information while starting package

download.

Can't update pkgfs during initial boot.

Continuing with current mapping

Could not update the package file system's

list of active files.

Software stored to persistent device

The persistent device now has its software

copied. Node will now ask instdir if it can
proceed to launch the software. During
turboboot, node may never get permission,
and just waits in MBI-RUNNING state until
all nodes reload.

Cleaning stale packages & meta-data

Status information cleaning old package

information prior to sync'ing a node.

Sync'ing packages & meta-data from

'[chars]'

Status information while starting install file

sync.

The Install infrastructure was unable to

connect to the system database, error:
[chars]

This may be because the communications

infrastructure is not yet up. If this problem
persists, the operations of the Install
infrastructure may not be able to proceed.

Failed to allocate %zu bytes of memory

The requested operation could not be

accomplished because of a low memory
condition.

Unexpected NULL pointer passed to Install Unexpected parameter value passed to

infrastructure
function.

An install command was unable to get a

platform type, error [chars].

An install command was unable to get a

platform type. As a result, the command
may not be able to continue with its
operations.

Insthelper was unable to reload the node,

error: [chars]. Software could be
inconsistent

The installation required a reload of the

node, but the reload failed. This is a critical
error, as the software installed will now be
in an inconsistent state. No future
installations will work correctly, and
process restarts can not be guaranteed to
be successful.

Configuration will be lost during the reload

of the installation if both of the following
apply 1. Binary configurations are not
compatible between the current software
and the software that runs after the reload
2. Some parts of the running configuration
have not been committed to configuration
Failed to save config prior to reload: [chars] manager's hidden ASCII config file.

While trying to synchronize the install state

Failed to update state files on this node
files to the local node, an error occurred.
(error: [chars]). A full update will be retried An attempt to re-sync all the state files will
in [unsigned int] seconds.
be automatically re-tried.

While initializing instdir on the dSC, failed

to sync instdir with running nodes, error:
[chars]

While trying to synchronize the install state

files of the dSC instdir, an error occurred.
The synchronization with remote nodes is
attempted once the dSC has been
successfully assigned and is required to
either: a) update the new dSC with newer
files found on remote nodes, b) update
remote nodes with state files on the dSC.
Should an error occur during either of
these, the synchronization should be reattempted.

Failed to send a reply message to a client,

error: [chars]

An error occurred while sending a reply

LWM message to a client. It can be a data
or an error number reply.

Install infrastructre has waited [unsigned

int] seconds for Install Director to be able
to process a message.

A part of the install infrastructure has been

waiting for the stated time for the install
director to be able to process the image.
This can happen if other processes are
taking a long time to initialize.

Node did not download all files before

reload.

During a reload operation, some nodes

download as much information as possible
before the reload occurs, and then
complete the download after the reload.
Under extreme circumstances, this can
result in the node having to reload twice.

A client of the Install infrastructure

A client of the Install infrastructure
unexpectedly returned an error during
returned an error from its callback function, processing, and so the requested operation
error: [chars]
may not be completed.

Failed in the config postinstall notification

Error:[chars].

Failed in postinstall notification to config

manager at package activation

Failed in the config preinstall notification

Error:[chars].

Failed in preinstall notification to config

manager at package activation

The database used by the Install

Unable to add directory '[chars]/[chars]' (or infrastructure could not be updated.
its meta data) to install database, error:
Further installations may not behave as
[chars]
expected, or be possible at all.

The Install infrastructure was unable to

create the install database at '[chars]',
error: [chars]

The database used by the Install

infrastructure could not be initialised.
Installations will not be possible.

An install database ([chars]) contained

data of invalid format, error: [chars]

An install database was unable to be

accessed. The current install operation, or
the Install infrastucture, will not be able to
continue successfully.

The Install infrastructure was unable to

The database used by the Install
determine the name of an install database, infrastructure could not be accessed.
error: [chars]
Installations will not be possible.

An install database '[chars]' could not be

opened, error: [chars]

An install database was unable to be

opened. The current install operation, or
the Install infrastucture, will not be able to
continue successfully.

An install database was unable to be

accessed. The current install operation, or
An operation on an install database failed: the Install infrastucture, will not be able to
[chars]. Error: [chars]
continue successfully.

A path of the install database, '[chars]', is

invalid ([chars]), error: [chars]

An error has been encountered in the

install database. The current install
operation, or the Install infrastucture, will
not be able to continue successfully.

An install database ([chars]) record could

not be accessed, error: [chars]

An install database record was unable to be

accessed. The current install operation, or
the Install infrastucture, will not be able to
continue successfully.

[chars], error: [chars]

Unable to access an install subdirectory.

The current install operation, or the Install
infrastucture, will not be able to continue
successfully.

An ens consumer response failed with

[chars] after [dec] attempts

Insthelper failed to respond to instdir.

Instdir will notice this and, after a timeout
will attempt to re-retrieve the response
from insthelper.

Insthelper received an unknown payload

message type ([dec])

Insthelper received an unknown message

type from instdir.

Failed to register error messages in

'[chars]' [[chars]].

The DLL containing the messages

associated with the install manager error
codes failed to be registered. The system
will continue to work, but clients that
receive install manager error codes will not
be able to retrieve the textual description
of the error.

Received reply too large message for a

message buffer that was big enough for
reply message. (message buffer size =
[dec], instdir reply size = [dec])

Install director gave an incorrect message

reply size to a client

LWM client failed to send a message to

instdir, error: [chars]

An instdir LWM client failed to send a

message to instdir.

Failed to output user error message

concerning install operation [dec] (details: A user error occurred but failed to be
[chars])
output to the user.

An install-related file '[chars]' failed

validity-checking ([chars]), error: [chars]

A file used by the Install infrastructure

failed validity checking. The current install
operation, or the Install infrastucture, will
not be able to continue successfully.

The Install infrastructure was unable to

determine the information about file
'[chars]', error: [chars]

The Install infrastructure was unable to

access a file. The current install operation,
or the Install infrastucture, will not be able
to continue successfully.

Failed to open file '[chars]', error [chars]

Failed to open the specified required file, so

processing of the current request or
operation will halt. The filesystem may be
in error, or the Install infrastructure may be
behaving incorrectly.

The Install infrastructure was unable to

read file '[chars]', error [chars]

Failed to read the specified required file, so

processing of the current request or
operation will halt. The filesystem may be
in error, or the Install infrastructure may be
behaving incorrectly.

The Install infrastructure was returned an

error by the blobbify library when [chars],
error: [chars]

The Install infrastructure was unable to

access some of the data that it requires,
and so the requested operation may not be
completed.

Internal error: [chars]: [chars]

An internal software error occurred.

The Install infrastructure encountered an

error when accessing a list of internal
structures. [chars], error: [chars]

The Install infrastructure encountered an

error when accessing a list of internal
structures, and so the requested operation
may not be completed.

The Install infrastructure was unable to

load pie '[chars]', error: [chars]

The Install infrastructure was unable to

load a pie file. It will not be able to be used.

Could not register tracing, error: [chars]

Failed to register ltrace context structure.

Tracing will not be functioning properly.

Failed to allocate %zd bytes of memory

There is not enough memory to continue

with current operations.

The Install infrastructure was unable to get

The Install infrastructure was unable to get the class of a node, and so the requested
the class of a node, error: [chars]
operation may not be completed.

The Install infrastructure was unable to

The Install infrastructure was unable to use access and use a package. It will not be
package in '[chars]' ([chars]), error: [chars] able to be utilised.

One or more parameters were

unexpectedly NULL!

An NULL parameter has been unexpectedly

passed to the Install infrastructure. This is
a coding error.

Path '[chars]': [chars], error: [chars]

An install path was found to be in error. The

current install operation, or the Install
infrastucture, will not be able to continue
successfully.

Path '[chars]': [chars], error: [chars]

An install path could not be cleaned up or

destroyed. This will have no effect for now,
but may affect install paths later on.

[chars], error: [chars]

A pie file contains invalid data, and cannot

be used.

The Install infrastructure was unable to

construct the information about a pie file,
error: [chars]

The Install infrastructure was unable to use

all the contents of a pie file. The current
install operation, or the Install
infrastucture, will not be able to continue
successfully.

The Install infrastructure encountered an

error when attempting to load a package
from loadpath '[chars]', error: [chars]

The Install infrastructure encountered an

error when loadng a package, and so the
requested operation may not be
completed.

Failed to get platform type in function

[chars]. As a result, process instmgr does
not have platform type information. Some
instmgr execution path may result in
failure.

Failed to get platform type.

The requested reload installation is not

allowed for a membooted management
node

A reload installation is not allowed to a

membooted management node.

[chars]

An install operation has failed because of

an internal error in the stack logic.

An error occurred while the Install

An error occurred while the Install
infrastructure was interacting with System
infrastructure was interacting with System Manager, and so the requested operation
Manager. [chars], error: [chars]
may not be completed.

Sleeping for [dec] seconds before MDR

Informs the user how many seconds the

node is sleeping before MDRing during a
'test ISSU-run' operation.

Sleeping for [dec] seconds before reload

Informs the user how many seconds the

node is sleeping before reloading during a
'test ISSU-run' operation.

The auto-abort timer started in install

operation [dec] has expired. Reloading
[chars].

The auto-abort timer has expired, reloading

the router/SDR.

The auto-abort-timer, started in install

operation [dec][chars] expires in [dec]
seconds. [chars]

The auto-abort timer is about to expire.

The installation required a reload of the

dSC node, but the reload failed. The
The primary install director failed to reload software installed will now be in an
the node, error: [chars]
inconsistent state.

Critical: Install operation [dec] will autoabort in [dec] minutes. [chars]

The install operation will abort in the given

time unless the user starts either the
accept phase or the complete phase using
the supplied instructions. The critical
version is shown if the abort timer has less
than 30 minutes left on it.

A system error occurred during an install

operation. This may indicate a transitive
problem within the system, a problem with
the code or a user error not verified by the
Error occurred during install operation
install system. The system does not know
[dec]: Please collect diagnostic information what software is running on the specified
using '[chars]' (details: [chars]). The
nodes and it may be the case that the
following nodes are in an inconsistent
software on the nodes cannot operate
state: [chars]. Use 'show install log [dec]
correctly within its own node or with other
detail' for more details.
nodes in the system.

Further information supplied to be used in

conjunction with the
SYSTEM_ERROR_SPECIFIC_NODES_INCONSI
STENT_HDR message. One of the nodes
possibly now in an inconsistent state with
[chars] is in an inconsistent state ([chars]) itself and the rest of the system.

A system error occurred during an install

operation. This may indicate a transitive
problem within the system, a problem with
the code or a user error not verified by the
install system. The system does not know
what software is running on the specified
Error occurred during install operation
nodes and it may be the case that the
[dec]: Please collect diagnostic information software on the nodes cannot operate
using '[chars]'. Use 'show install log [dec] correctly within its own node or with other
detail' for more details.
nodes in the system.

A system error occurred within the install

While trying to output information about a system, possibly during an install
system error [chars]during an the install
operation, but the install code could not
operation, the install subsystem was
output information about the system error
unable to obtain the data to output:
because an error occurred within the error
Context: [chars], error: [chars]
output code.

Initialization failed [[chars]], error: [chars]

An error occurred during initialization,

causing the process to terminate.

Initialization failed [[chars]], error: [chars]

An error occurred during initialization,

causing the process to terminate.

An unexpected dSC switchover occurred

during ISSU. ISSU operation is being
aborted

During ISSU operation, a dSC switchover

occurred unexpectedly thus the current
ISSU operation is aborted.

Node [chars] which is a fabric node was

During ISSU operation, the specified fabric
reloaded during ISSU. Thus ISSU operation node was reloaded unexpectedly thus the
is being aborted
current ISSU operation is aborted.

During ISSU operation, the specified fabric

Node [chars] which is a fabric node was
node removal was detected by the install
removed during ISSU. Thus ISSU operation ISSU infrastructure and thus the current
is being aborted
ISSU operation is aborted.

Node [chars] which is a standby node was During ISSU operation, the specified
reloaded during ISSU. Thus ISSU operation standby node was reloaded unexpectedly
is being aborted
thus the current ISSU operation is aborted.

During ISSU operation, the specified

Node [chars] which is a standby node was standby node removal was detected by the
removed during ISSU. Thus ISSU operation install ISSU infrastructure and thus the
is being aborted
current ISSU operation is aborted.
A previously requested install operation
that was incomplete was attempted to be
applied. However the operation was
An incomplete install (request id [dec]) was detected as being before any state had
encountered and aborted.
changed so was aborted.

An incomplete 'install add' (request id

[dec]) was encountered and aborted.

A previously requested install add

operation was found to be incomplete. The
operation has been aborted and install
infrastructure has removed any partially
installed packages.

The auto-abort-timer, started in install

operation [dec][chars] expires in [dec]
minutes. [chars]

The auto-abort timer is running and soon to

expire.

Invalid operation type ([dec]) passed to

Install infrastructure

The function does not support the given

install operation.

Failed to build Package Dependency table

from file '[chars]'

Unexpected null string.

Checkpoint data for the Install process is

corrupt. The data will be deleted and the
install process restarted. Any install
operation in progress will be stopped.

Checkpoint data for the Install process is

corrupt. The data will be deleted and the
install process restarted. Any information
about any install operation that is in
progress has been lost.

Install director was unable to initialise its

event notification service. [chars] failed:
[chars]

The install director was not able to initialise

its event notification service. The system
will not be able to perform any installs
without this initialisation succeeding.

Install director was unable to send an event The install director was not able to send an
notification after [dec] attempts, error:
event notification. This will cause the
[chars]
system's install to fail in some way.

Initialization failed [[chars]], process

terminated, error: [chars]

An error occurred during initialization,

causing the process to terminate.

Install has encountered an error. User input

is required in order to move forward. Use
the command 'install operation [dec]
attach' in admin mode to answer the
question.

The incremental install operation has

encountered an error. And no 'nopromppt'
is supplied in the activation command. The
install would ask the user a question as
how to proceed.

A system error occurred during an install

Error occurred during install operation
operation. This may indicate a transitive
[dec]: Please collect diagnostic information problem within the system, a problem with
using '[chars]' (details: [chars]). Use 'show the code or a user error not verified by the
install log [dec] detail' for more details.
install system.

[chars] ([chars])

Further information supplied to be used in

conjunction with the
INSTALL_OPERATION_SYSTEM_ERROR_SPEC
IFIC_NODES_HDR message.

Error occurred during install operation

[dec]: Please collect diagnostic information
using '[chars]'. Use 'show install log [dec]
detail' for more details.

A system error occurred during an install

operation. This may indicate a transitive
problem within the system, a problem with
the code or a user error not verified by the
install system.

User error occurred during install operation Information provided by the user or by
[dec]. See 'show install log [dec] detail' for binaries referenced by the user command
more information.
were inaccurrate.

A system error occurred within the install

system, not during an install operation.
Error occurred within the install system.
This may indicate a transitive problem
Please collect diagnostic information using within the system or a problem with the
'[chars]' (details: [chars]).
code.

[chars] ([chars])

Further information supplied to be used in

conjunction with the
INSTALL_SYSTEM_ERROR_SPECIFIC_NODES_
HDR message.

A system error occurred within the install

system, not during an install operation.
Error occurred within the install system.
This may indicate a transitive problem
Please collect diagnostic information using within the system or a problem with the
'[chars]'.
code.

Failed to [chars], error: [chars]

Interpret the error string.

Failed to [chars], error: [chars]

Interpret the error string.

Detected reload event on SPA in [chars]

during ISSU, this SPA will be placed in
disable state for the rest of ISSU operation.
After the operation has completed, the SPA
will be brought up with the active software.

The indicated SPA was reloaded during

ISSU and is being placed in disable state
for the duration of the ISSU operation. This
is safety measure to prevent the reload
event of this SPA affecting the overall ISSU
operation on the system.

Detected reload event on SPA in [chars]

during ISSU, this SPA will be placed in
disable state for the rest of ISSU operation.
After the operation has completed, the SPA
will be brought up with the active software.

The indicated SPA was reloaded during

ISSU and is being placed in disable state
for the duration of the ISSU operation. This
is safety measure to prevent the reload
event of this SPA affecting the overall ISSU
operation on the system.

Failed to shutdown [chars] SPA [chars] [chars].

The shutdown operation to the indicated

SPA has failed.

Failed to shutdown [chars] SPA [chars] [chars].

The shutdown operation to the indicated

SPA has failed.

Failed to unshutdown [chars] SPA [chars] [chars].

The unshutdown operation to the indicated

SPA has failed.

Failed to unshutdown [chars] SPA [chars] [chars].

The unshutdown operation to the indicated

SPA has failed.

The Install (ISSU/iMDR) operation timed out The ISSUMgr FSM timed out on some
in the ISSUMgr state [chars] ([dec]). The
node(s) during the ISSU/iMDR operation
operation will be aborted.
and the operation is being aborted.

Node [chars] failed to comply to install

ISSU infrastructure as it reloaded, in the
midst of ISSU. It will be held in MBI until
ISSU operation is completed and then will
be brought up with the new version of the
software

As part of ISSU operation, the specified

node did not comply to ISSU infrastructure
as it got reloaded. Thus it will be held in
MBI until the current ISSU operation is
completed and then will be will be booted
with the new version of the software.

Node [chars] is being reloaded by install

ISSU infrastructure due to [chars] failure

As part of ISSU operation, the specified

node that was warm reloaded (iMDRed) has
encountered the specified failure and thus
is being reloaded by the install ISSU
infrastructure.

During a high memory usage install

operation, the install director has received
a memory state change notification from
Received a [chars] memory condition
wdsysmon. In order to allow routing
during an install operation. The Install
application to continue, the install director
Director will restart to free memory for
will restart to free any memory it is using.
routing applications, but this will abort the However, this will cause the current
operation.
operation to abort.

Failed to allocate %zu bytes of memory

The requested operation could not be

accomplished because of a low memory
condition.

Failed to send a reply message to a client,

error: [chars]

An error occurred while sending a reply

LWM message to a client. It can be a data
or an error number reply.

ISSU abort procedure failed while waiting

for [chars] to roll back to previous image.
The system will be in an unstable state.

After the install/ISSU operation is aborted,

during roll-back the card group fails to
revers back to previous image.

The SAM certificate expired. This error

could also be because the system date is
SAM certificate expired. Please check
set to a very old data. Check the system
system date. Current system date: [chars] data.

Unable to access the system database,

error: [chars]

An error occurred when accessing the

system database

Registration with SysDB failed [[chars]],

error: [chars]

An error occurred when registering with the

system database

Unable to spawn script via sysmgr even

after [dec] retries in [dec] seconds

Timed out while trying to spawn a script via

sysmgr

Failed to start timer for request id [dec] The request has been aborted.

A timer creation failed for the active

request. In order to prevent the potential
indefinite blocking of the Install Manager
request processor, the request has been
aborted.

While trying to determine the order of two

packages (or two sets of packages), the
packages in question were found to have
Unable to determine the order of two
conflicting prerequisites information. The
packages with respect to their prerequisite packages will be ordered by build-time
information.
instead.
Aborting LOAD phase of install operation
[dec], force reload of node [chars]

Reload the node while aborting LOAD

phase of install issu operation.

The currently active software is [chars]

The currently active software has not yet

been 'committed' to the system. This
means that if the system reboots then the
committed software will become active.
Note that a failover will not cause the
committed software to become active.

The auto-abort timer, started in install

operation [dec][chars] expires in [dec]
minutes. [chars]

The auto-abort timer is running.

[chars] the auto-abort timer for install

operation [dec][chars]. The auto-abort
timer expires in [dec] minutes. [chars]

The auto-abort timer has started/resumed.

The auto-abort-timer, started in install

operation [dec][chars] has been stopped.

The auto-abort timer has been stopped.

The install manager needs to call the

platform API to reload the router to
complete the parallel install operation. If
Install manager is about to request a router the call fails, the user may have to call:
reload to complete the install operation
reload location all in admin mode.

The install manager needs to call the

platform API to reload the ndoes listed, in
order to complete the parallel install
operation. If the call fails, the user may
In order to complete operation [dec] Install have to manually reload each node
manager is about to request the reload of manually, by calling reload location <loc>
the following nodes [chars]
from admin mode

In order to complete the install operation

Install Manager requested the reload of the
entire router. The call to reload failed
(reason: [chars]). The dSC will be reloaded
thereby triggering an indirect router reload

The Install Manager called the platform API

to reload all nodes in order to complete the
parallel install operation. The platform call
failed, so the dSC is going to be reloaded
directly which will trigger a router reload

In order to complete operation [dec] Install

manager requested the reload of the
following nodes [chars]. The call to reload
failed (reason: [chars]). Please reload each
node separately by calling: reload location
<loc> from admin mode

The install manager needs to call the

platform API to reload the ndoes listed, in
order to complete the parallel install
operation. The platform call failed, so the
user will have to manually reload each
node, by calling reload location <loc> from
admin mode

Install operation [dec] has been

suspended. Use the command 'install
resume' in admin mode to resume the
operation.

The incremental install operation will be

suspended indefinitely, at the pre-defined
suspension point. User needs to issue
'install resume' in admin mode in order to
resume the operation.

Auto-abort timer was expected for ISSU

operation [dec], but not found after RUN
phase completion.

Auto-abort timer was expected (per user

options specified) but not running after
RUN phase.

A warning occurred during install operation The behavior of the install operation may
[dec]. See 'show install log [dec] detail' for not have been entirely what the user
more information.
expected.

Warning: Install operation [dec] will autoabort in [dec] minutes. [chars]

The install operation will abort in the given

time unless the user starts either the
accept phase or the complete phase using
the supplied instructions. The warning
version is shown if the abort timer has 30
minutes or more left on it.

Failed to [chars] - rc=[dec]

Shows the error messages other than the

CE connection errors

ISM CE warning occurred while validating

CE connection, found that the active RP is
connected to standby SC. Due to that the
following RP(s) may get into isolated state
during ISSU operation. Please make sure
that active RP(s) are connected to active
SC(s) and then run the ISSU.

During ISSU, verifying the CE connection's

having that all active RPs are connected to
active SC. If there is no valid active CE
connection between active RP and active
SC then that particular racks goes into
isolated state.

Node [chars] is not allowed to boot during

this phase of install operation [dec]. After Node rebooted while ISSU install operation
the operation has completed, the node will is in progress, it will not be allowed to
be brought up with the active software.
come up until the operation completes.
Node [chars] is not allowed to boot during
this phase of install operation [dec]. After Node rebooted while ISSU install operation
the RUN phase has completed, the node
is in progress, it will not be allowed to
will be brought up with the active software. come up until the RUN phase completes.
Node [chars] is unexpectedly booting
during install operation [dec].

This node boot is not expected in the given

phase of ISSU install, install should abort
with an error.

After install operation [unsigned int], the

install history log is larger than the
recommended maximum size of [unsigned
int] kB ([unsigned int] kB). This may have a
detrimental effect in later install
operations, so it is recommended to delete
some old logs using (admin) 'clear install
log-history oldest <>'.

The install history logs are larger than the

recommended size. Depending on the
system and its usage, this can cause
replication timeouts during later install
operations. By clearing some of the old
logs (from install operations unrelated to
the current upgrade scenario), these
detrimental effects can be mitigated.

Install manager has been calling the API

[chars] since [chars]; after [dec] tries the
call still returns EAGAIN.

The install manager needs to call some

APIs to retrieve information during its
initialization. If the information is not
retrieved successfully install director will
retry after a small time interval until
success.

'The primary install director takes several

seconds doing some processing ' 'prior to
Install director has encountered an
reload, which is not expected. This
unexpected delay ([unsigned int].[unsigned situation may result in ' 'a different RP to
int] seconds in function [chars]) while
the current active being elected as the
preparing to reload.
active when ' 'the system reboots.'
The creation of a rollback point for install
operation [unsigned int] failed (details:
[chars]). The operation will continue, but
this operation ID cannot be used as a
rolback point.

There was an error when trying to create

the loadpath file for this rollback point. The
operation will continue successfully (given
no other errors), but this point cannot be
used as a rollback point.

Install director found a standby node

[chars] not ready, all standby (D)RPs are
required to be ready to proceed.

Install director expected standby nodes to

be ready, however, when verifying found at
least one that is not ready.

iMDR completion timeout: Re-arming the

timer for %zd seconds as still [dec] nodes
left (retries left: [dec])

As part of ISSU operation, iMDR done on

LCs has timedout and an extension is being
done by install ISSU infrastruture. This is an
informational message that iMDR
completion has not been seen.

Install operation [dec]: Complete Phase has The complete phase of an ISSU operation
finished.
has finished successfully.
The complete phase of an ISSU operation
Install operation [dec]: Complete Phase has has started - another message will be
started.
output when the phase finishes.
Install operation [dec] has not completed
yet. Please check - '(admin) show install
The run phase of an ISSU operation has
request' to continue with the next phase of finished successfully. Inform the user the
the operation.
operation has not completed yet.
Install operation [dec]: Load Phase has
finished.

The load phase of an ISSU operation has

finished successfully.

Install operation [dec]: Load Phase has

started.

The load phase of an ISSU operation has

started - another message will be output
when the phase finishes.

Install operation [dec] aborted

An install operation was aborted by the

system. This is usually due to the Install
Director restarting or an RP failover during
the initial phase of an install operation.

Aborting install operation [dec] by [chars]

due to a system error.

An error occurred in the ISSU install

operation, and the operation will be
aborted using the stated method to recover
the system back to it's running state.

Install operation [dec] cancelled by user

'[chars]'

An install operation was cancelled via a

user prompt. Use 'show install log <install
ID> detail' for more details.

Install operation [dec] completed

successfully

An install operation has completed

successfully.

Install operation [dec] completed with

failure

An install operation completed with error.

Use 'show install log <install ID> detail' for
more details.

Install operation [dec] failed

An install operation failed. Use 'show install

log <install ID> detail' for more details.

Install operation [dec] '[chars]' started by

user '[chars]'

An install operation has been started another message will be displayed when it
is finished.

Install operation [dec] aborted by user

'[chars]'

An install operation was aborted by a user.

Install operation [dec] has been resumed.

The install operation has been resumed

after pausing for user input.

Install operation [dec]: Run Phase has

finished.

The run phase of an ISSU operation has

finished successfully.

Install operation [dec]: Run Phase has

started.

The run phase of an ISSU operation has

started - another message will be output
when the phase finishes.

Node: [chars]

Shows the invalid CE connections node

informations

[chars] is being reloaded dunring iMDR

because its partner [chars] has reloaded

This message is seen during ISSU/iMDR if

service processor on the linecard reloads
and the corresponding CPU on the
linecards must be reloaded as well.

[chars] is being reloaded dunring iMDR

because its partner [chars] has reloaded

This message is seen during ISSU/iMDR if

service processor on the linecard reloads
and the corresponding CPU on the
linecards must be reloaded as well.

Initiating shutdown operation to [chars]

SPA in [chars]

The shutdown operation is being performed

on the indicated SPA.

Initiating shutdown operation to [chars]

SPA in [chars]

The shutdown operation is being performed

on the indicated SPA.

Initiating un-shutdown operation to [chars] The shutdown operation is being performed

SPA in [chars]
on the indicated SPA.
Initiating un-shutdown operation to [chars] The shutdown operation is being performed
SPA in [chars]
on the indicated SPA.

ISSU in progress. Percentage done: [dec].

[dec], State info: [dec] nodes-left: [dec]

This message is seen during ISSU after

switchover or instdir process restart> The
ISSUMgr is registering with checkpoint and
found existing data. This is expected in the
RUN phase of ISSU operation where a
switchover happens or when instdir
process restarts in any phase of ISSU and is
not an error condition.

Initiating dSC switchover as part of the

ISSU operation. Percentage done: [dec].
[dec], State info: [dec] (rc [hex])

The ISSUMgr is doing dSC node switchover

as part of the ISSU operation. This is
expected in the RUN phase of ISSU
operation and is not an error condition.

The Install (ISSU/iMDR) operation timed out The ISSUMgr FSM timed out on some
in the ISSUMgr state [chars] ([dec]).
node(s) during the ISSU/iMDR operation.

Node [chars] which was WARM reloaded

will now be brought out of MBI (new
version) as part of ISSU operation

As part of ISSU operation, the specified

node that was warm reloaded (iMDRed) will
now be brought out of MBI to XR RUN in the
new version of the software.

Node [chars] encountered [chars] failure,

However the install ISSU infrastructure is
NOT reloading the node as on-abort noreload is set

As part of ISSU operation, the specified

node has encountered the mentioned
failure but the node is not being reloaded
by the install ISSU infrastructure as the
debug flag is set.

When initiating the ISSU operation, the

user specified the on-abort no-reload
option. This message indicates that on
The Install (ISSU) operation [dec] was
abort, no recovery or clean up will be
aborted but, the on-abort no-reload option performed. The user has indicated 'onwas set for the install hence, no abort
abort no-reload' hence, no recovery will be
related recovery or clean-up will be
performed as part of abort. This is a nonperformed.
error condition.

When initiating the ISSU operation, the

user specified the on-abort no-reload
option. This message indicates that on
The Install ISSU operation was aborted in
abort, no recovery will be done by ISSUMgr.
the ISSUMgr state [chars] ([dec]). However, The user has indicated 'on-abort no-reload'
the on-abort no-reload option was set for
hence, no abort actions will be performed
the install hence, no abort related reloads as part of abort. This is a non-error
will be performed by ISSUMgr.
condition.

Install ISSU [chars] phase completed,

waiting for [chars] phase to start

After an ISSU operation was initiated, the

install infrastructure goes thru internal sub
phases. This message indicates that a
particular sub phase is done and within
install infrastructure the next phase is
being waited for.

Install ISSU state machine is now FROZEN

in state [chars] ([dec]). Waiting for user to
unfreeze (Line [dec]).

When initiating the ISSU operation, the

user specified that the install infrastructure
should freeze the ISSU state machine in
every state before transitioning to the next
state. The operation will not continue until
the user either indicates that install
unfreeze the state machine using the
supplied command (run ismdbg -T) or clear
the freeze of the state machine using the
supplied command (run ismdbg -C).

Install ISSU state machine is now THAWed

in state [chars] ([dec]) and will continue
transitioning to the next state (Line [dec])

When initiating the ISSU operation, the

user specified that the install infrastructure
should freeze the ISSU state machine in
every state before transitioning to the next
state. This message indicates that the user
has indicated install infrastructure to
proceed with the state transitioning. The
user has indicated to unfreeze from the
current ISSU state. This is a non-error
condition.

Node [chars] is booting with boot option

'[chars]'.

This message indicates the boot options of

the specified node.

The boot options of node [chars] were

cleared.

The boot options of the specified node are

cleared when the node preparation is
complete.

Install operation [unsigned int] is pausing

before the config lock is applied. Apply any
additional config before resuming the
operation using '[chars]install operation
[unsigned int] complete'.

When initiating the operation, the user

specified that the install infrastructure
should pause before locking the config for
the first time. The operation will not
continue until the user indicates that it is
safe to do so using the supplied command.

Install operation [unsigned int] is pausing

before reloading any nodes for this
operation. Complete any necessary checks
before resuming the operation using
'[chars]install operation [unsigned int]
complete'.

When initiating the operation, the user

specified that the install infrastructure
should pause before doing any reloads. The
operation will not continue until the user
indicates that it is safe to do so using the
supplied command.

Install director has reloaded the standby or

Install director is waiting for the standby RP has switched over. Now it is waiting for the
to be ready.
standby RP to be ready.
Install director has triggered the reload
software change on the target nodes. Now
it is waiting for the Install helpers on the
Install director is waiting for Install helpers reloaded nodes to come up and ready to
on the reloaded nodes to be ready.
receive messages.

dSC and install director has migrated to a

new head.

An unexpected dSC migration has

happened. The install manager detects this
condition and also finds it may continue.

Failed to output user error message

concerning install operation [dec] (details: A user error occurred but failed to be
[chars])
output to the user.
Failed to output useful information
concerning install operation [dec] (details: Useful information was available but failed
[chars])
to be output to the user.
Failed to output a warning concerning
install operation [dec] (details: [chars])

A warning occurred but failed to be output

to the user.

Failed to [chars], error: [chars]

Interpret the error string.

Failed to open file '[chars]', error: [chars]

Failed to open the specified file.

Internal error: [chars]

An internal software error occurred.

Could not register tracing, error: [chars]

Failed to register ltrace context structure.

Tracing will not be functioning properly.

Failed to store log information for install

operation: [dec] (details: [chars])

The install operation normally stores the

result of the install operation for the 'show
install log <install ID> detail' command to
use. However, this was not possible for the
reason given.

Unexpected null pointer passed to Install

infrastructure

Unexpected parameter value passed to

function.

Path '[chars]': [chars], error: [chars]

An install path was found to be in error. The

current install operation, or the Install
infrastucture, will not be able to continue
successfully.

Install director is still waiting for the initial

RDS sync to complete (waited [unsigned
int] seconds so far)

The install director is not able to continue

its initialization until the initial RDS sync
from the admin install director to the local
install helper process has completed.

The primary install director will now restart The installation required a reload of the
this node using '[chars]'
pID's node, and this is now going ahead.

Failed to process a request message while

[chars], error: [chars]

An error occurred during processing of a

LWM message from a client.

Failed to retrieve request from request

queue [[chars]].

The request processor thread failed to

obtain a request from the request queue.

An incomplete install (request id [dec]) was

encountered - attempting to resume the
An incomplete install was encountered - we
install
will attempt to resume the install.

The requested operation requires that

nodes be reloaded for the software change
to take affect. The install infrastructure will
automatically reload nodes with files that
Software change transaction [unsigned int] are removed, added or modified by the
will reload affected nodes
software change.
After switching over, the data w.r.t the
switchover are not available. This could be
due to data loss or unplanned switchover.
Critical switchover data is not present. The The install manager detects this condition
install operation is proceeding.
and also finds it may continue.

Sleeping for [dec] seconds before

switchover

Informs the user how many seconds the

dLRSC is sleeping before switching over
during a 'test ISSU-run' operation.

Warning: The timeout for processing the

install message '[chars]' almost expired
(available time: [unsigned int] secs, spare
time: [unsigned int] secs)

The timeout associated with an install

message was close to expiring. This is a
non-error condition.

Failed to start timer for request id [dec] This entry will not be automatically
removed.

A timer creation failed, which means that

the information for the request will not
automatically be removed.

An unknown error type ([dec]) was

received for install [chars] message

An incorrect parameter was passed to the

error reporting function. The errors for this
install operation will not have been
reported correctly.

A file was downloaded whose size was

Downloaded a file with an unexpected size: unexpectedly zero, or was different to the
[chars].
size recorded in the file meta-data.

Downloaded a file from [chars] with an

unexpected size: [chars].

A file was downloaded whose size was

unexpectedly zero, or was different to the
size recorded in the file meta-data.

A file could not be opened from this node

Failed to open file '[chars]' while creating a when as a file stream was being
file stream: [chars].
constructed.

Internal error: [chars]

An internal software error occurred.

Could not register tracing, error: [chars]

Failed to register ltrace context structure.

Tracing will not be functioning properly.

Failed to allocate %zu bytes of memory

The requested operation could not be

accomplished because of a low memory
condition.

Unexpected null pointer passed to Install

infrastructure

Unexpected parameter value passed to

function.

Cannot initialize debugging, error: [chars]

There is a problem with the system

infrastructure - perhaps the communication
infrastructure has not yet stabilised. The
process which encountered this problem
will automatically restart. If other processes
exhibiting similar behaviour, this is a
system-wide issue.

The Install infrastructure encountered an

internal error

The Install infrastructure has reached an

unexpected state. Operations will continue,
but the logging and debugging capabilities
of the Install infrastructure may not
function as expected.

Failed to [chars] mutex, error [chars].

To be filled in later

Could not register dll '[chars]' with error

services, error: [chars]

The error services failed to register the

errors of the specified DLL. The system will
continue to operate, but error or warning
messages displayed to the customer may
not be complete.

Function is not supported on this

architecture.\n

This function cannot be called on the

current platform.

Function is not supported on this

architecture.\n

This function cannot be called on the

current platform.

Tools version does not match data!

Tools=[unsigned int].[unsigned int],
Data=[unsigned int].[unsigned int].

The tooling version does not match the

installed package. The operation will not be
able to proceed.

Tools version does not match data!

Tools=[unsigned int].[unsigned int],
Data=[unsigned int].[unsigned int].

The tooling version does not match the

installed package. The operation will not be
able to proceed.

Blobbifier rejected item #[dec].

An invalid parameter may have been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Blobbifier rejected item #[dec].

An invalid parameter may have been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
Cannot get blob size! Item #[unsigned int]. completed.
An invalid parameter has been
unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
Cannot get blob size! Item #[unsigned int]. completed.
An invalid parameter has been
unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
Cannot get blob size! Item #[unsigned int]. completed.
An invalid parameter has been
unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
Cannot get blob size! Item #[unsigned int]. completed.

Cannot get name of calling process

(pid=[dec])

A process' name cannot be determined, so

the current request or operation will not be
able to proceed successfully.

Cannot get name of calling process

(pid=[dec])

A process' name cannot be determined, so

the current request or operation will not be
able to proceed successfully.

Deblobbifier rejected item #[dec].

An invalid parameter may have been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Deblobbifier rejected item #[dec].

An invalid parameter may have been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Cannot create event connection manager,

error: [chars]

The library failed to create a connection for

registering for install notifications.

Cannot create event connection manager,

error: [chars]

The library failed to create a connection for

registering for install notifications.

Cannot register for notifications on

connection, error: [chars]

The library failed to register for

notifications on a connection.

Cannot register for notifications on

connection, error: [chars]

The library failed to register for

notifications on a connection.

Cannot open connection, error: [chars]

The library failed to open a connection for

registering for install notifications.

Cannot open connection, error: [chars]

The library failed to open a connection for

registering for install notifications.

Failed to initialise trace buffers, error:

[chars]

The install notification library was unable to

initialise the trace buffer.

Failed to initialise trace buffers, error:

[chars]

The install notification library was unable to

initialise the trace buffer.

Internal error

The Install infrastructure has encountered

an unexpected state, and will not be able
to continue operating successfully.

Internal error

The Install infrastructure has encountered

an unexpected state, and will not be able
to continue operating successfully.

Internal data consistency error

The Install infrastructure has encountered

an unexpected state, and will not be able
to continue operating successfully.

Internal data consistency error

The Install infrastructure has encountered

an unexpected state, and will not be able
to continue operating successfully.

Unable to find item.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Unable to find item.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Unable to add element to list. List is full

(contains [unsigned int] elements).

The Install infrastructure has encountered

an unexpected state, and will be unable to
process the current request or operation

Unable to add element to list. List is full

(contains [unsigned int] elements).

The Install infrastructure has encountered

an unexpected state, and will be unable to
process the current request or operation

Unable to find item 0x%zx in list.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Unable to find item 0x%zx in list.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Unable to allocate %zu bytes of memory

The system is running out of memory and

was not able to allocate sufficient memory
to carry out the requested operation

Unable to allocate %zu bytes of memory

The system is running out of memory and

was not able to allocate sufficient memory
to carry out the requested operation

Operation is allowed only on a

Management Node\n

A function available only on management

nodes was called on a non-management
node.

Operation is allowed only on a

Management Node\n

A function available only on management

nodes was called on a non-management
node.

Event parameter value is bad ([unsigned

int]).

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Event parameter value is bad ([unsigned

int]).

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Transaction ID parameter value is bad

([unsigned int]).

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Transaction ID parameter value is bad

([unsigned int]).

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Dynamic type checking revealed that a

pointer parameter referenced an object of
wrong type.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Dynamic type checking revealed that a

pointer parameter referenced an object of
wrong type.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

String parameter is incomplete.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

String parameter is incomplete.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Blobbifier for type not provided.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Blobbifier for type not provided.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Parameter #[dec] of the parameter list is

NULL or missing.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Parameter #[dec] of the parameter list is

NULL or missing.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

One or more parameters were

unexpectedly NULL!

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

One or more parameters were

unexpectedly NULL!

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
A parameter has been passed with a value current request or operation will not be
outside the expected range.
completed.
An invalid parameter has been
unexpectedly passed to the Install
infrastructure. This is a coding error. The
A parameter has been passed with a value current request or operation will not be
outside the expected range.
completed.

A non-NULL parameter unexpectedly

referenced a NULL pointer.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

A non-NULL parameter unexpectedly

referenced a NULL pointer.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

An invalid parameter type ([unsigned int])

was encountered.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

An invalid parameter type ([unsigned int])

was encountered.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Unable to acquire write lock on resource

before timeout occurred

This may be a resource issue, or the Install

infrastructure may be behaving incorrectly.
The current request or operation cannot be
completed.

Unable to acquire write lock on resource

before timeout occurred

This may be a resource issue, or the Install

infrastructure may be behaving incorrectly.
The current request or operation cannot be
completed.

The Install infrastructure was unable to

connect to the system database, error:
[chars]

The communications infrastructure may

not yet be up. If this error persists, the
Install infrastructure may not be able to
operate

The Install infrastructure was unable to

connect to the system database, error:
[chars]

The communications infrastructure may

not yet be up. If this error persists, the
Install infrastructure may not be able to
operate

Cannot complete the transaction of items

for an operation, error: [chars]

The current operation could not complete

the transaction of items which are needed
to activate it.

Cannot complete the transaction of items

for an operation, error: [chars]

The current operation could not complete

the transaction of items which are needed
to activate it.

Cannot delete data from the system

database, error: [chars]

This may not affect the current request or

operation, but subsequent operations may
be affected.

Cannot delete data from the system

database, error: [chars]

This may not affect the current request or

operation, but subsequent operations may
be affected.

Cannot retrieve data from the system

database, error: [chars]

The Install infrastructure was unable to

obtain some information which it requires
to complete the current request or
operation.

Cannot retrieve data from the system

database, error: [chars]

The Install infrastructure was unable to

obtain some information which it requires
to complete the current request or
operation.

Cannot retrieve data from the system

database, error: [chars]

The Install infrastructure was unable to

obtain some information which it requires
to complete the current request or
operation.

Cannot retrieve data from the system

database, error: [chars]

The Install infrastructure was unable to

obtain some information which it requires
to complete the current request or
operation.

Cannot unregister with system database

for notification, error: [chars]

The notification services from the system

database failed to shut down. This will not
have any adverse effect on the running of
the box.

Cannot unregister with system database

for notification, error: [chars]

The notification services from the system

database failed to shut down. This will not
have any adverse effect on the running of
the box.

The Install infrastructure was unable to

Cannot set item in system database, error: write some information which is required to
[chars]
complete the current request or operation.

The Install infrastructure was unable to

Cannot set item in system database, error: write some information which is required to
[chars]
complete the current request or operation.

Cannot begin the transaction of items for

an operation, error: [chars]

The current operation could not start the

transaction of items which are needed to
activate it.

Cannot begin the transaction of items for

an operation, error: [chars]

The current operation could not start the

transaction of items which are needed to
activate it.

Cannot disconnect from the system

database, error: [chars]

The connection to the system database

failed to shut down. This will not have any
adverse effect on the running of the box.

Cannot disconnect from the system

database, error: [chars]

The connection to the system database

failed to shut down. This will not have any
adverse effect on the running of the box.

SysMgr has failed to respond to a software SysMgr appears to have become

change within [dec] seconds. Continuing to unresponsive, potentially requiring
wait, node may require a reload ...\n
operator intervention.

SysMgr has failed to respond to a software SysMgr appears to have become

change within [dec] seconds. Continuing to unresponsive, potentially requiring
wait, node may require a reload ...\n
operator intervention.

Too many timeout resets. Reset request

refused.

The maximum number of time extensions

to the current install command have
already been granted, so the current
request for an extension is denied.

Too many timeout resets. Reset request

refused.

The maximum number of time extensions

to the current install command have
already been granted, so the current
request for an extension is denied.

Incorrect type found for key.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Incorrect type found for key.

An invalid parameter has been

unexpectedly passed to the Install
infrastructure. This is a coding error. The
current request or operation will not be
completed.

Package '[chars]' only supports nodes of

type [chars] and can't be activated on
nodes of type [chars]

Instructions in package conflict with

requested operation.

Unexpected NULL pointer passed to the

Install infrastructure by a client

Unexpected parameter value passed to

function.

Package '[chars]' supports no node types

Instructions in package list no node types

for which the package can be activated.

Could not initialize library, error: [chars]

'Failed to initialize the library. The system

may not ' 'function properly. '

Could not register tracing, error: [chars]

'Failed initialising the tracing library.'

'Traces for instdir process will not function
properly.'

'Function: [chars] : Corrupt parameter

passed to Package infrastructure'

Value of a parameter passed to function

appears to be corrupt. The current request
or operation will not be carried out.

Error on line [dec] of ldpath file '[chars]':

[chars]%s

Either the installation is corrupt, or the

Package infrastructure is behaving
incorrectly. Processing of the current
operation will halt.

Can't load paths from '[chars]': ldpath

string is '' on line [unsigned int], buf:
[chars]

An intermittent error occurred for which the

root cause is not yet known. The system
will continue working correctly. However,
the information from the error message will
be very useful for tracking down and fixing
the bug.

An attempt to remove the ignore commit

ldpath file failed. This could be due to a file
system error. The result of this failure is
Failed to remove the ignore commit ldpath that committed install information will not
file '[chars]' ([chars])
be interpreted correctly.

Failed to close file '[chars]', error: [chars]

Either the file system is in error, or the

loadpath infrastructure is behaving
incorrectly. A file involved in the current
request or operation could not be closed.
This will not affect the current operation,
but subsequent operations may be
affected.

Failed to open file '[chars]', error: [chars]

Either the file system is in error, or the

loadpath infrastructure is behaving
incorrectly. A file required for carrying out
the current request or operation could not
be opened, so processing of the operation
will halt.

Failed to read from file '[chars]', error:

[chars]

Either the file system is in error, or the

loadpath infrastructure is behaving
incorrectly. A file required for carrying out
the current request or operation could not
be read, so processing of the operation will
halt.

Failed to rename file from '[chars]' to

'[chars]', error: [chars]

Either the file system is in error, or the

loadpath infrastructure is behaving
incorrectly. A file required for carrying out
the current request or operation could not
be moved, so processing of the operation
will halt.

Failed to go to specific position in file

'[chars]', error: [chars]

Either the file system is in error, or the

loadpath infrastructure is behaving
incorrectly. A file required for carrying out
the current request or operation could not
be read, so processing of the operation will
halt.

An internal error has occurred in an

application that has caused it to pass
'Function: [chars] : Unexpected null pointer invalid data to the Package infrastructure.
passed to Package infrastructure in the
The current request or operation will not be
function'
carried out.

Failed to sort packages correctly, error:

[chars]

The sorting algorithm used for sorting

packages that are to be output using a
'show install active' type command, failed
to perform correctly. Although the packages
will be output, they may not be in the
standard order.

An internal error has occurred in an

application causing it to send invalid data
to the packaging infrastructure. The current
An invalid (NULL) parameter was passed to request or operation may not be carried
the packaging infrastructure
out.

Internal error: [chars]

An internal software error occurred.

Internal error: [chars]

An internal software error occurred.

Failed to read or write to the specified file,

The packaging infrastructure was unable to which is required to proceed further. The
carry out an I/O operation to a file ([chars]), current request or operation may not be
error: [chars]
carried out.

Failed to read or write to the specified file,

The packaging infrastructure was unable to which is required to proceed further. The
carry out an I/O operation to a file ([chars]), current request or operation may not be
error: [chars]
carried out.

Failed to read or write to the specified file,

The packaging infrastructure was unable to which is required to proceed further. The
carry out an I/O operation to a file ([chars]), current request or operation may not be
error: [chars]
carried out.

Failed to read or write to the specified file,

The packaging infrastructure was unable to which is required to proceed further. The
carry out an I/O operation to a file ([chars]), current request or operation may not be
error: [chars]
carried out.

Failed to read or write to the specified file,

The packaging infrastructure was unable to which is required to proceed further. The
carry out an I/O operation to a file ([chars]), current request or operation may not be
error: [chars]
carried out.

Failed to read or write to the specified file,

The packaging infrastructure was unable to which is required to proceed further. The
carry out an I/O operation to a file ([chars]), current request or operation may not be
error: [chars]
carried out.

Either the card type is invalid, or the

The packaging infrastructure was unable to infrastructure is behaving incorrectly. The
determine the type of the current node:
current request or operation may not be
[chars]
carried out.
Either the card type is invalid, or the
The packaging infrastructure was unable to infrastructure is behaving incorrectly. The
determine the type of the current node:
current request or operation may not be
[chars]
carried out.

Failed to allocate [unsigned int] bytes of

memory

The requested operation could not be

accomplished because of a low memory
condition.

Failed to allocate %zu bytes of memory

The requested operation could not be

accomplished because of a low memory
condition.

Failed to allocate %zu bytes of memory

The requested operation could not be

accomplished because of a low memory
condition.

Failed to allocate [unsigned int] bytes of

memory

The requested operation could not be

accomplished because of a low memory
condition.

Failed to allocate [unsigned int] bytes of

memory

The requested operation could not be

accomplished because of a low memory
condition.

Failed to allocate %zu bytes of memory

The requested operation could not be

accomplished because of a low memory
condition.

Failed to allocate [unsigned int] bytes of

memory

The requested operation could not be

accomplished because of a low memory
condition.

An internal error has occurred in an

application causing it to send invalid data
to the packaging infrastructure. The current
An invalid (NULL) parameter was passed to request or operation may not be carried
the packaging infrastructure
out.
An internal error has occurred in an
application causing it to send invalid data
to the packaging infrastructure. The current
An invalid (NULL) parameter was passed to request or operation may not be carried
the packaging infrastructure
out.
An internal error has occurred in an
application causing it to send invalid data
to the packaging infrastructure. The current
An invalid (NULL) parameter was passed to request or operation may not be carried
the packaging infrastructure
out.
An internal error has occurred in an
application causing it to send invalid data
to the packaging infrastructure. The current
An invalid (NULL) parameter was passed to request or operation may not be carried
the packaging infrastructure
out.
An internal error has occurred in an
application causing it to send invalid data
to the packaging infrastructure. The current
An invalid (NULL) parameter was passed to request or operation may not be carried
the packaging infrastructure
out.
An internal error has occurred in an
application causing it to send invalid data
to the packaging infrastructure. The current
An invalid (NULL) parameter was passed to request or operation may not be carried
the packaging infrastructure
out.
An internal error has occurred in an
application causing it to send invalid data
to the packaging infrastructure. The current
An invalid (NULL) parameter was passed to request or operation may not be carried
the packaging infrastructure
out.

Failed to open the specified file, which is

The packaging infrastructure was unable to required to proceed further. The request or
open a file ([chars]), error: [chars].
operation may not be carried out.

Failed to open the specified file, which is

The packaging infrastructure was unable to required to proceed further. The request or
open a file ([chars]), error: [chars].
operation may not be carried out.

Failed to open the specified file, which is

The packaging infrastructure was unable to required to proceed further. The request or
open a file ([chars]), error: [chars].
operation may not be carried out.

Failed to open the specified file, which is

The packaging infrastructure was unable to required to proceed further. The request or
open a file ([chars]), error: [chars].
operation may not be carried out.

Failed to open the specified file, which is

The packaging infrastructure was unable to required to proceed further. The request or
open a file ([chars]), error: [chars].
operation may not be carried out.

Failed to open the specified file, which is

The packaging infrastructure was unable to required to proceed further. The request or
open a file ([chars]), error: [chars].
operation may not be carried out.

Failed to open the specified file, which is

The packaging infrastructure was unable to required to proceed further. The request or
open a file ([chars]), error: [chars].
operation may not be carried out.

Either the card type is invalid, or the

infrastructure is behaving incorrectly. The
The packaging infrastructure was unable to current request or operation may not be
determine the type of a card ([hex])
carried out.
Either the card type is invalid, or the
infrastructure is behaving incorrectly. The
The packaging infrastructure was unable to current request or operation may not be
determine the type of a card ([hex])
carried out.
Either the card type is invalid, or the
infrastructure is behaving incorrectly. The
The packaging infrastructure was unable to current request or operation may not be
determine the type of a card ([hex])
carried out.
Either the card type is invalid, or the
infrastructure is behaving incorrectly. The
The packaging infrastructure was unable to current request or operation may not be
determine the type of a card ([hex])
carried out.
Either the card type is invalid, or the
infrastructure is behaving incorrectly. The
The packaging infrastructure was unable to current request or operation may not be
determine the type of a card ([hex])
carried out.
Either the card type is invalid, or the
infrastructure is behaving incorrectly. The
The packaging infrastructure was unable to current request or operation may not be
determine the type of a card ([hex])
carried out.
Either the card type is invalid, or the
infrastructure is behaving incorrectly. The
The packaging infrastructure was unable to current request or operation may not be
determine the type of a card ([hex])
carried out.

Install file '[chars]' is corrupted

'An install file is corrupt.This may affect the

system in a number of ways' 'including
preventing nodes from booting or
preventing install operations.'

Install file '[chars]' is corrupted

An install file is corrupt. This may affect the

system in a number of ways including
preventing nodes from booting and
preventing install operations.

Failed to allocate %zu bytes of memory

The requested operation could not be

accomplished because of a low memory
condition.

Failed to allocate %zu bytes of memory

'The requested operation could not be

accomplished because of low' 'memory.'

Install manager has been calling the API

[chars] since [chars]; after [dec] tries the
call still returns EAGAIN.

The install manager needs to call some

APIs to retrieve information during its
initialization. If the information is not
retrieved successfully install director will
retry after a small time interval until
success.

Install manager has been calling the API

[chars] since [chars]; after [dec] tries the
call still returns EAGAIN.

The install manager needs to call some

APIs to retrieve information during its
initialization. If the information is not
retrieved successfully install director will
retry after a small time interval until
success.

Package index file for '[chars]' lists nonexistent package '[chars]'. Going ahead to 'The package index file was found to be
clean up package index file.
incorrect. Instdir will attempt to' ' repair it.'

Package index file for '[chars]' lists nonexistent package '[chars]'. Going ahead to 'The package index file was found to be
clean up package index file.
incorrect. Instdir will attempt to' ' repair it.'

Dir prefix '[chars]' contains unknown card

type '[chars]'

The Package infrastructure could not

determine which cards a particular file
belongs to. Either the PIE file is corrupt, or
the Package infrastructure is behaving
incorrectly. The current request or
operation will not be carried out.

Dir prefix '[chars]' contains unknown card

type '[chars]'

The Package infrastructure could not

determine which cards a particular file
belongs to. Either the PIE file is corrupt, or
the Package infrastructure is behaving
incorrectly. The current request or
operation will not be carried out.

INSTDB file '[chars]' is in unsupported

format [dec].[dec].

INSTDB file is in an obsolete format or is

unknown.

INSTDB file '[chars]' is in unsupported

format [dec].[dec].

INSTDB file is in an obsolete format or is

unknown.

PIE file '[chars]' is in unsupported format

[dec].[dec].

The PIE file is in an obsolete format or is

unknown.

PIE file '[chars]' is in unsupported format

[dec].[dec].

The PIE file is in an obsolete format or is

unknown.

An internal datastructure could not be

sorted, so the resultant list will be
unsorted. This will only have a cosmetic
Unsupported sort type ([dec]) encountered effect.

An internal datastructure could not be

sorted, so the resultant list will be
unsorted. This will only have a cosmetic
Unsupported sort type ([dec]) encountered effect.

Can't add file '[chars]' to table, error:

[chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not creat a
required new file node with given view and
actual paths and insert it into the table, so
processing of the current operation will
halt.

Can't add file '[chars]' to table, error:

[chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not creat a
required new file node with given view and
actual paths and insert it into the table, so
processing of the current operation will
halt.

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not change to
a required directory, so processing of the
Can't change cwd to '[chars]', error: [chars] current operation will halt.
Either the file system is in error, or the
infrastructure is behaving incorrectly. The
Package infrastructure could not change to
a required directory, so processing of the
Can't change cwd to '[chars]', error: [chars] current operation will halt.

Can't get files, error: [chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
required the list of files that this package
contains, so processing of the current
operation will halt.

Can't get files, error: [chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
required the list of files that this package
contains, so processing of the current
operation will halt.

Can't get actual install path [dec], error:

[chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
required installation path for file on nodes
of given type, so processing of the current
operation will halt.

Can't get actual install path [dec], error:

[chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
required installation path for file on nodes
of given type, so processing of the current
operation will halt.

Can't get node table, error: [chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not create a
required new node table, so processing of
the current operation will halt.

Can't get node table, error: [chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not create a
required new node table, so processing of
the current operation will halt.

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
required view path for file. This is the view
that pkgfs uses, so processing of the
Can't get relative path [dec], error: [chars] current operation will halt.

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
required view path for file. This is the view
that pkgfs uses, so processing of the
Can't get relative path [dec], error: [chars] current operation will halt.

Can't get signature [dec], error: [chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
required string representation of signature
of this file, so processing of the current
operation will halt.

Can't get signature [dec], error: [chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
required string representation of signature
of this file, so processing of the current
operation will halt.

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not create a
required directory, so processing of the
Can't make directory '[chars]', error: [chars] current operation will halt.
Either the file system is in error, or the
infrastructure is behaving incorrectly. The
Package infrastructure could not create a
required directory, so processing of the
Can't make directory '[chars]', error: [chars] current operation will halt.

Unable to read PIE file '[chars]': [chars]

PIE file appears to be damaged. Package

read failed due to network connectivity
issue.

Unable to read PIE file '[chars]': [chars]

PIE file appears to be damaged. Package

read failed due to network connectivity
issue.

Can't remove directory '[chars]', error:

[chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not remove a
required directory, so processing of the
current operation will halt.

Can't remove directory '[chars]', error:

[chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not remove a
required directory, so processing of the
current operation will halt.

Can't sort node table, error: [chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not sort
required all nodes, so processing of the
current operation will halt.

Can't sort node table, error: [chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not sort
required all nodes, so processing of the
current operation will halt.

Unable to uncompress [chars] from file

'[chars]'

Either the file system is in error, or the

infrastructure is behaving incorrectly. A file
required for carrying out the current
request or operation could not be
uncompressed, so processing of the
operation will halt.

Unable to uncompress [chars] from file

'[chars]'

Either the file system is in error, or the

infrastructure is behaving incorrectly. A file
required for carrying out the current
request or operation could not be
uncompressed, so processing of the
operation will halt.

Could not register DLL '[chars]' with error

services, error: [chars]

The call to register the error messages of

the Package infrastructure failed. Any
errors returned from the Package
infrastructure will not be decoded into userfriendly strings.

Could not register DLL '[chars]' with error

services, error: [chars]

The call to register the error messages of

the Package infrastructure failed. Any
errors returned from the Package
infrastructure will not be decoded into userfriendly strings.

Can't close file '[chars]', error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file involved in the current
request or operation could not be closed.
This will not affect the current operation,
but subsequent operations may be
affected.

Can't close file '[chars]', error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file involved in the current
request or operation could not be closed.
This will not affect the current operation,
but subsequent operations may be
affected.

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file involved in the current
request or operation could not be copied.
Cannot copy file '[chars]' to '[chars]', error: This may impact install infrastructure
[chars]
functioning.
Either the file system is in error, or the
Package infrastructure is behaving
incorrectly. A file involved in the current
request or operation could not be copied.
Cannot copy file '[chars]' to '[chars]', error: This may impact install infrastructure
[chars]
functioning.

Corrupt parameter passed to Package

infrastructure

Value of a parameter passed to function

appears to be corrupt. The current request
or operation may not be carried out.

Function: [chars] : Corrupt parameter

passed to Package infrastructure

Value of a parameter passed to function

appears to be corrupt. The current request
or operation will not be carried out.

PIE file '[chars]' is corrupt: [chars]

PIE file appears to be damaged.

PIE file '[chars]' is corrupt: [chars]

PIE file appears to be damaged.

Cannot create symlink from '[chars]' to

'[chars]', error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A symlink file involved in the
current request or operation could not be
created. This may impact install
infrastructure functioning.

Cannot create symlink from '[chars]' to

'[chars]', error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A symlink file involved in the
current request or operation could not be
created. This may impact install
infrastructure functioning.

Can't delete file '[chars]', error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file involved in the current
request or operation could not be deleted.
This will not affect the current operation,
but subsequent operations may be
affected.

Can't delete file '[chars]', error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file involved in the current
request or operation could not be deleted.
This will not affect the current operation,
but subsequent operations may be
affected.

Package index file for '[chars]' lists nonexistent package '[chars]'. Instdir failed to 'An unexpected error occured in cleaning
repair the package index file. Error - [chars] the package index file.'
Package index file for '[chars]' lists nonexistent package '[chars]'. Instdir failed to 'An unexpected error occured in cleaning
repair the package index file. Error - [chars] the package index file.'

Unable to locate [chars] file in loadpath

'[chars]'

Either the installation is corrupt, or the

Package infrastructure is behaving
incorrectly. An expected file was not found
in the package directories, so processing of
the operation will halt.

Unable to locate [chars] file in loadpath

'[chars]'

Either the installation is corrupt, or the

Package infrastructure is behaving
incorrectly. An expected file was not found
in the package directories, so processing of
the operation will halt.

Failed while getting api_name report:

[chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
required API name information, so
processing of the current operation will
halt.

Failed while getting api_name report:

[chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
required API name information, so
processing of the current operation will
halt.

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
required file information, so processing of
Failed while getting file information: [chars] the current operation will halt.

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
required file information, so processing of
Failed while getting file information: [chars] the current operation will halt.

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
Failed while getting Providers report, error: required providers report, so processing of
[chars]
the current operation will halt.

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
Package infrastructure could not get a
Failed while getting Providers report, error: required providers report, so processing of
[chars]
the current operation will halt.

INSTDB files may be in an inconsistent

state due to error encountered while
Creation of INSTDB files for piefile '[chars]' creating them. This issue may affect sanity
encountered problems
of install infrastructure data.

INSTDB files may be in an inconsistent

state due to error encountered while
Creation of INSTDB files for piefile '[chars]' creating them. This issue may affect sanity
encountered problems
of install infrastructure data.

Internal error: [chars]

An internal software error occurred.

Internal error: [chars]

An internal software error occurred.

Invalid parameter passed to Package

infrastructure. Problem: [chars]

An internal error has occurred in an

application that has caused it to pass
invalid data to the Package infrastructure.
The current request or operation may not
be carried out.

Invalid parameter passed to Package

infrastructure. Problem: [chars]

An internal error has occurred in an

application that has caused it to pass
invalid data to the Package infrastructure.
The current request or operation may not
be carried out.

Could not register tracing, error: [chars]

Failed to register ltrace context structure.

Tracing will not be functioning properly.

Could not register tracing, error: [chars]

Failed to register ltrace context structure.

Tracing will not be functioning properly.

An MBI config file has been incorrectly

changed '[chars]'

Configuration definitions have changed for

an MBI file and this has only done by
changing the MBI config namespace file,
not by moving the MBI config namespace
file out of the MBI as is required by the
system.

An MBI config file has been incorrectly

changed '[chars]'

Configuration definitions have changed for

an MBI file and this has only done by
changing the MBI config namespace file,
not by moving the MBI config namespace
file out of the MBI as is required by the
system.

Failed to obtain package MD5 [chars] :

[chars]

Failed to retrieve the package MD5 from

the specified package's md5_manifest file,
so processing of the current operation will
halt.

Failed to obtain package MD5 [chars] :

[chars]

Failed to retrieve the package MD5 from

the specified package's md5_manifest file,
so processing of the current operation will
halt.

Failed to convert package MD5 [chars] :

[chars]

Failed to convert package MD5, so

processing of the current operation will
halt.

Failed to convert package MD5 [chars] :

[chars]

Failed to convert package MD5, so

processing of the current operation will
halt.

Failed to perform file validity check

device=[chars],package root=[chars] :
[chars]

Failed to perform file validity check on each

file to see if they are valid or not, so
processing of the current operation will
halt.

Failed to perform file validity check

device=[chars],package root=[chars] :
[chars]

Failed to perform file validity check on each

file to see if they are valid or not, so
processing of the current operation will
halt.

'A non-critical memory allocation failed.

The operation can and will ' 'proceed. There
A memory allocation failed in a non-critical may be cosmetic errors such as incoherent
path ([chars]). The operation will continue. error messages.'

'A non-critical memory allocation failed.

The operation can and will ' 'proceed. There
A memory allocation failed in a non-critical may be cosmetic errors such as incoherent
path ([chars]). The operation will continue. error messages.'

PIE file '[chars]' is corrupt: Missing '[chars]'

from info section '[chars]'
PIE file appears to be damaged.

PIE file '[chars]' is corrupt: Missing '[chars]'

from info section '[chars]'
PIE file appears to be damaged.

Can't get cwd, error: [chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
current working directory could not be
determined, so processing of the current
operation will halt.

Can't get cwd, error: [chars]

Either the file system is in error, or the

infrastructure is behaving incorrectly. The
current working directory could not be
determined, so processing of the current
operation will halt.

PIE file '[chars]' specifies 'ISSU' install

method but '[chars]' restart type

The restart information in the PIE file is

invalid. PIEs that use the 'ISSU' install
method must use a restart type of 'reload'
or 'MDR'.

PIE file '[chars]' specifies 'ISSU' install

method but '[chars]' restart type

The restart information in the PIE file is

invalid. PIEs that use the 'ISSU' install
method must use a restart type of 'reload'
or 'MDR'.

The restart information in the PIE file is

PIE file '[chars]' specifies 'parallel-lr' install invalid. PIEs that use the 'parallel-lr' install
method but '[chars]' restart type
method must use a restart type of 'reload'.

The restart information in the PIE file is

PIE file '[chars]' specifies 'parallel-lr' install invalid. PIEs that use the 'parallel-lr' install
method but '[chars]' restart type
method must use a restart type of 'reload'.

'[chars]' is not a directory: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A directory was expected, but a
non-directory was passed, so processing of
the current operation will halt.

'[chars]' is not a directory: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A directory was expected, but a
non-directory was passed, so processing of
the current operation will halt.

File '[chars]' is not in PIE format.

A PIE file is of the correct format, either

because the wrong file has been specified,
or the file is corrupt. The current request or
operation will not be carried out.

File '[chars]' is not in PIE format.

A PIE file is of the correct format, either

because the wrong file has been specified,
or the file is corrupt. The current request or
operation will not be carried out.

PIE file '[chars]' is corrupt: Attribute

'[chars]' from info section '[chars]' is not a
singleton value. Count=[unsigned long int] PIE file appears to be damaged.

PIE file '[chars]' is corrupt: Attribute

'[chars]' from info section '[chars]' is not a
singleton value. Count=[unsigned long int] PIE file appears to be damaged.
An internal error has occurred in an
application that has caused it to pass
invalid data to the Package infrastructure.
Unexpected null pointer passed to Package The current request or operation may not
infrastructure
be carried out.

An internal error has occurred in an

application that has caused it to pass
Function: [chars] : Unexpected null pointer invalid data to the Package infrastructure.
passed to Package infrastructure in the
The current request or operation will not be
function
carried out.

The Package infrastructure was unable to

open file '[chars]', error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file required for carrying out
the current request or operation could not
be opened, so processing of the operation
will halt.

The Package infrastructure was unable to

open file '[chars]', error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file required for carrying out
the current request or operation could not
be opened, so processing of the operation
will halt.

PIE file '[chars]' is corrupt: Mismatch

between sizes of lists for [chars] ([unsigned
long int]) and [chars] ([unsigned long int])
in info section '[chars]'.
PIE file appears to be damaged.

PIE file '[chars]' is corrupt: Mismatch

between sizes of lists for [chars] ([unsigned
long int]) and [chars] ([unsigned long int])
in info section '[chars]'.
PIE file appears to be damaged.

Predict tool failed an AVL tree operation

An unexpected error occured in the internal

datastructures of the Package
infrastructure. The current operation or
request cannot be completed.

Predict tool failed an AVL tree operation

An unexpected error occured in the internal

datastructures of the Package
infrastructure. The current operation or
request cannot be completed.

The Package infrastructure was unable to

read from file '[chars]', error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file required for carrying out
the current request or operation could not
be read, so processing of the operation will
halt.

The Package infrastructure was unable to

read from file '[chars]', error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file required for carrying out
the current request or operation could not
be read, so processing of the operation will
halt.

Cannot rename file '[chars]' to '[chars]',

error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file involved in the current
request or operation could not be renamed.
This may impact install infrastructure
functioning.

Cannot rename file '[chars]' to '[chars]',

error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file involved in the current
request or operation could not be renamed.
This may impact install infrastructure
functioning.

PIE file '[chars]' is in unsupported format

[dec].[dec]. This format was retired [chars]. PIE file is in an obsolete format.

PIE file '[chars]' is in unsupported format

[dec].[dec]. This format was retired [chars]. PIE file is in an obsolete format.

The Package infrastructure is unable to

determine the type of a card

Either the card type may be invalid or the

infrastructure is behaving incorrectly. The
current request or operation has not been
carried out.

The Package infrastructure is unable to

determine the type of a card

Either the card type may be invalid or the

infrastructure is behaving incorrectly. The
current request or operation has not been
carried out.

Cannot remove/unlink file '[chars]', error:

[chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file involved in the current
request or operation could not be unlinked.
This may impact install infrastructure
functioning.

Cannot remove/unlink file '[chars]', error:

[chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file involved in the current
request or operation could not be unlinked.
This may impact install infrastructure
functioning.

The Package infrastructure was unable to

write to file '[chars]', error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file required for carrying out
the current request or operation could not
be read, so processing of the operation will
halt.

The Package infrastructure was unable to

write to file '[chars]', error: [chars]

Either the file system is in error, or the

Package infrastructure is behaving
incorrectly. A file required for carrying out
the current request or operation could not
be read, so processing of the operation will
halt.

Only [dec].X PIE files are supported.

Attempted to load PIE file '[chars]' in
unsupported format [dec].[dec].

The PIE file was passed to the wrong loader

function. The current request or operation
will not be carried out.

Only [dec].X PIE files are supported.

Attempted to load PIE file '[chars]' in
unsupported format [dec].[dec].

The PIE file was passed to the wrong loader

function. The current request or operation
will not be carried out.

'The node boot-up failed while writing

Can't write to default file.File_path: [chars] pkgfs map to file.' 'The node will reload and
Error: [chars]
try to recover.'

'The node boot up failed while trying to

Can't load from Loadpath: [chars] node_id: decode the loadpath string' 'The node will
[hex] Error: [chars]
reload and try to recover.'

Initialization failed [[chars]], error: [chars]

An error occurred during initialization of the

library.

Internal error: [chars]

An internal software error occurred.

Failed to allocate %zd bytes of memory

There is not enough memory to continue

with current operations.

Initialization failed [[chars]], error: [chars]

An error occurred during initialization.

Failure occurred during Package Cache

creation: [chars]

An error occurred while the packages were

being cached to memory.

A problem occurred while re-initializing

from checkpoint

An error occurred during the process's

reinitialisation. The system should continue
to function as normal.

Failed to get state of node [chars] which is While synchronizing a reload between a
partner to [chars] while synchronizing
node and its partner, the state of the
reload
partner node could not be ascertained.

Install helper on node [chars] is

masquerading as node [chars]

Install helper on a particular node passed

an incorrect nodeid to install director. The
error will be returned to install helper.

A problem occurred while handling a

message: [chars]

An unexpected occurrence happened

within the LWM handling code. The code is
able to carry on as normal.

Error returned when [chars]: [chars]

This self-managing component reached an

unexpected state, and was unable to
proceed with the requested operation.

Error [chars] dll '[chars]'.

To be filled in later

Communication error ([chars]).

The communications infrastructure may

not yet be initialised. If this problem
persists, seek guidance.

Internal error: [chars]

This self-managing component reached an

unexpected state, and was unable to
proceed with the requested operation.

Unable to proceed ([chars]).

This self-managing component

encountered an expected error when
attempting to carry out an action required
for the currently requested operation, so
has had to halt processing of the operation.

\[chars]\.

A non-fatal error has been encountered.

The system will continue to operate, but
this error should be brought to the
attention of TAC.

The install infrastructure detected that

[chars] is too small to install IOS-XR
software. Please replace the [dec] byte
device with a larger capacity disk.

Disk is too small for easybake to continue

on.

The requested install device [chars] is

either corrupt or missing. Turboboot cannot
be performed. The turboboot settings will
be cleared, and the node will reset. Please
repair or insert the device and retry the
boot sequence.

The TURBOBOOT setting in ROMMON was

enabled, but the requested device is
unavailable. The EASYBAKE/TURBOBOOT
variables are cleared. The node will be
reset. Please repair the device and retry
the boot sequence.

TURBOBOOT rommon variable not set;

system is membooting. Set TURBOBOOT
rommon variable to 'on' to diskboot the
system. !! Memboot is unsupported.
Behavior could be undefined !!

'The TURBOBOOT rommon variable was not

set to 'on'. The system has ' 'membooted.
Set the TURBOBOOT variable to 'on' to
prepare the system for' 'diskboot.'

Boot environment variables cannot be

reset.

Boot environment variables cannot be

reset.

The install infrastructure could not access

device [chars]. The device may be missing Install device could not be accessed and
or it may be corrupt.
may be corrupt or missing.
The TURBOBOOT setting in ROMMON had
Both device CLEAN and FORMAT option set both the device CLEAN and FORMAT
in the turboboot setting [chars]. This
options enabled. This setting is ignored and
setting is ignored and no device init is
no device initialization would be
performed.
performed.

More than one disk option has been set in

turboboot options.

The TURBOBOOT setting in ROMMON had

more than one disk option set. This will
cause turboboot to abort.

[chars] '[chars]', error [chars]

A Version Manager library was unable to

carry out a filesystem operation.
Installations may not produce the expected
results.

A Version Manager library was unable to

allocate %zu bytes of memory.

The system is running out of memory and

was not able to allocate sufficient memory
to carry out an install-related operation.

An invalid parameter was passed to a

Version Manager library.

A client of a Version Manager library

passed it an invalid argument, and so the
library may not be able to carry out its
operations. Installations may not produce
all the expected results.

A Version Manager library was unable to

bind to SysDB, error [chars].

A Version Manager library was unable to

bind to SysDB (perhaps because the
communications infrastucture is not yet
up), so will not be able to function.
Installations will be unlikely to produce the
expected results.

A Version Manager library was unable to

retrieve some data from SysDB, so may not
A Version Manager library was unable to
be able to function. Installations may not
retrieve an item from SysDB, error [chars]. produce the expected results.

A Version Manager library was unable to

register with SysDB, error [chars].

A Version Manager library was unable to

register with SysDB, so will not be able to
function. Installations will be unlikely to
produce the expected results.

A Version Manager library was unable to

set an item in SysDB, error [chars].

A Version Manager library was unable to

set an item in SysDB, so the system may
now be in an inconsistent state.
Installations will be unlikely to produce the
expected results.

A Version Manager library was unable to

unbind from SysDB, error [chars].

A Version Manager library was unable to

unbind from SysDB. Despite this,
subsequent operation is unlikely to be
affected.

VS Object cached lookup: Name: [chars],

Object id: [hex], Version: [hex]

Test code only - will never be seen by

customers.

VS Object not present in cache: Name:

[chars], Object id: [hex]

Test code only - will never be seen by

customers.

[chars]: [chars]

Test code only - will never be seen by

customers.

Failed to allocate %zu bytes

Test code only - will never be seen by

customers.

Failed to handle selected version

notification: [chars] ([chars])

There was a problem with a notification of

a change to the selected version for a
communication protocol.

VS Notification received: Name: [chars],

Object id: [hex], Version: [hex], Options:
[hex]

Test code only - will never be seen by

customers.

VS Object deleted notification received:

Name: [chars], Object id: [hex], Options:
[hex]

Test code only - will never be seen by

customers.

Failed to respond to selected version

notification: [chars]

There was a problem responding to a

notification of a change to the selected
version for a communication protocol. The
selected version publisher will assume that
the affected process handled the
notification successfully.

VS Client successfully set up

Test code only - will never be seen by

customers.

Failed to handle a client request or

response: [chars] ([chars])

There was a problem with a request to get

the selected version for a communication
protocol, or with a response to a
notification of a change to a selected
version.

There was a problem processing the

Timeout processing version change for
notification of a change to the selected
[unsigned int] communication[chars] (first version for one or more communication
affected communication: [hex])
protocols.

Checkpoint Initialization failed: [chars],

[chars]. Restarting ANCP...

A software error occurred when ANCP

process tried to restore initialization data.

Interface manager initialization failed:

[chars], [chars]. Restaring ANCP...

A software error occurred when the ANCP

process tried to perform initialization with
the interface manager process. The error
could be because Interface Manager is
unavailable at the time of ANCP
initialization or a software error in either of
ANCP or Interface Manager processes.

A software error occurred when the ANCP

process tried to publish rate updates
through the interface manager. One of the
most probable reason for the error is that
Interface Manager process is not available
or is restarting at the time of the operation.
Failed to update rate to [unsigned int], for ANCP will attempt to recover by retrying
port [chars], interface [chars]. Error: [chars] the update in question.

A software error occurred while starting up

of ANCP process. The exact reason for the
error is as specified in the message. The
condition could most probably happen
because of the following: 1) Unavailabilty
of a particular resource at the time of
Initialization failed: Failure reason: [chars], intilization 2) Race condition 3) Memory
Error: [chars]. Restarting ANCP...
initilization error/ shortage

Processing of [chars] message from

adjacency sender [chars] failed for port
circuit [chars]; Failure type: [chars], Error:
[chars]

A port up/down message was received but

the operation failed.

A software error occurred when the ANCP

RP Redundancy Initialization failed: [chars], process tried to initialize the redundancy
[chars]. Restarting ANCP...
data with its standby RP/DRP

An attempt to transmit a valid packet to

Failed to send packet to adjacency [chars], the identified adjacency failed due to an
[chars]
internal software error.

A software error occurred when the ANCP

Socket Initialization failed: [chars], [chars]. process tried to create and open a passive
Restarting ANCP process...
socket through the TCP process.

Error initializing the system database:

[chars], [chars]. Restarting ANCP...

A software error occurred when the ANCP

process tried to perform initialization with
the system database process/routines. The
error could be because sysdb process is
unavailable at the time of ANCP
initialization or a software error in either of
ANCP or sysdb processes.

Received [chars] memory depletion

warning.

ANCP process has received an event that

it's memory usage has reached its
budgeted threshold. Continued increase in
memory usage could result in restart of
ANCP process.

Received [dec] memory event, when

expecting memory usage event

ANCP process has received an unexpected

event, when expecting a memory usage
event. Check memory usage for this
process. This could occur because of an
software error in the ANCP module or the
Memory handler module itself, which could
in turn have been caused because of
memory shortage.

Connection to neighbor sender [chars] is

disconnected due to [chars].

The connection to the identified neighbor

no longer exists. Unless this outage was
intentionally performed by a user, there are
a number of possibilities which can cause
the neighbor to stop responding or remove
the connection: 1) network outage, 2)
ANCP was disabled at the remote side, 3)
ANCP process failure at the remote.

Neighbor sender [chars] was softly reset

due to [chars].

This action does not remove the

communication path to the neighbor. The
connection is restarted with the neighbor.
All mapped ports previously in UP state are
placed in DOWN state while maintaining
locally published rates. Any unmapped
ports in UP state are released. Actions
which can cause this are as follows: 1) User
requested a soft reset of adjacency using
the cli clear ancp nei ... state, 2) User
locally altered the configured timer for this
neighbor, 3) Upon receipt of ANCP protocol
'reset ACK' message.

Packet received from network not

formatted to ANCP Specification.

A packet was received from the network

which was not properly formatted. As a
result, the packet was discarded. If the
packet was destined to an existing
neighbor connection, the connection
remains intact unless the dead timer to our
peer expires.

Unexpected [chars] packet received by

ANCP state logic for neighbor sender
[chars] in state [chars]

A valid formatted ANCP packet was

received for an adjacency, but is
unexpected given the state the adjacency
is currently in.

Memory depletion has subsided. Node

memory back below budgeted memory
threshold.

At some point, memory usage had

exceeded ANCP's budgeted threshold.
Memory has been freed putting it back in a
safe level of memory usage.

Port circuit [chars] moved from adjacency

sender [chars] to sender [chars]

A port up message was received from an

adjacency with a different sender name as
compared to the sender name received
from the previous port up message. The
software has performed operation to
associate this adjacency with the new
sender name; however, it may not be the
desired result, since duplicate ports could
have been configured on external devices.

A port down message was received from an

adjacency with a different sender name as
compared to the sender name from which
the port up message was received. The
Port-down event received for port circuit
software has ignored this event. The reason
[chars] with wrong sender; Current: [chars], for this is existance of duplicate ports on
Requestor: [chars].
external devices.

'Unrecoverable error in event loop. Error:

[chars]'

An error occured while the ARP GMP was

waiting for events. In this situation the
process will terminates and restarts.

The ARP GMP process failed to initialize

correctly. In this situation it restarts, but it
may not recover if there is a persistant
error in the IOSXR system and the ARP GMP
'Failure during intialization of [chars]. Error: is later unable to reestablish its
[chars]'
connections and initialize successfully.

[chars] [chars] [chars] ([chars],[chars])

ARP has overwritten an interface entry with

a static or alias entry. This indicates a
conflict with the IP address configuration on
the interface.

'Failed to initialise the Comms module.

Retrying in 3 ' 'seconds: [chars]'

An error occurred while initialising the

Comms module. ARP has scheduled a retry
for this operation. ARP will not be able to
synchronise data between the V1 and V2
process until this is resolved.

[chars] [chars]

ARP failed to load and initialize a dynamic

library that it requires.

Out of memory (failed attempt to reserve

[unsigned int] bytes)

ARP was not able to allocate the memory

that it needed to complete the operation.
ARP functionality on the affected node may
be reduced until the problem is resolved.

Local Interface entry overwritten by client

[chars] ([chars],[chars])

ARP has overwritten an interface entry with

a client entry. This can sometimes indicate
a conflict with the client configuration on
the interface.

Failed to resync with clients: [chars]

retrying in [dec] seconds

An error occurred while resyncing data with

ARP clients. In this situation ARP will
schedule a retry.

Failed to connect to [chars]. Unable to

retry: [chars]

The connection from ARP to the specified

service has failed and cannot be recovered.
In this situation ARP restarts and this
should resolve the problem.

Failed to initialize [chars]: [chars]

The ARP process failed to initialize

correctly. In this situation ARP restarts, but
ARP may not recover if there is a persistant
error in the IOSXR system and ARP is later
unable to reestablish its connections and
initialize successfully.

Failed to register [chars]: [chars]

Registration for an IOSXR service failed

during ARP's operation. This may indicate a
connection failure with the IOSXR service
as indicated in the error message. In this
situation, ARP restarts, and this should
resolve the problem.

An error occurred while attaching

interfaces to SPIO. ARP has scheduled a
retry for this operation. ARP will not be able
Failed to attach [unsigned int] interfaces to to send or receive ARP packets on these
SPIO. Retrying in 3 seconds: [chars]
interfaces until this is resolved.

ARP has failed to create a thread for the

specified process. In this situation ARP
Failed to create process thread for [chars]: restarts and this should resolve the
[chars]
problem.

Error occurred while waiting for [chars]:

[chars]

An error occurred while waiting for the

specified event. In this situation the
process will terminate and ARP restarts.

Duplicate IP address [chars] on

<<CH[hex]>>, sourced by [chars]

A peer device is configured with the same

interface IP address.

Duplicate MAC address [chars]

ARP request received with the same

destination MAC address as incoming
interface MAC address.

Selected outgoing interface for [chars]

differs from incoming interface

An ARP packet was received from an

unexpected interface. This can happen due
to misconfiguration of the IP addresses on
the participating devices or due to
incorrect bridging configuration.

Failed to add broadcast MAC address

The specified MAC address is invalid as it is

a broadcast address - all the bits are set.
Configuration has therefore been rejected.

Failed to get bfm buffer for transmit, with

size [dec]

Failed in getting a buffer from TX mem pool

of ETH_SERVER for client's usage . This
could lead to failure in sending the data
over the control ethernet to a remote node.

Unable to populate the buffer,tftpserver

failed to get start header ,error code:
[chars]

Unable to process the cilent start header

over the control ethernet. This could lead
to failure in sending the data over the
control ethernet to a remote node.

Tftp client has failed in writing the packet

Writing the packet to tftp client's Tx queue to the Transmit queue for transmission.This
for transmission failed with error code:
could lead to failure in sending the data
[chars]
over the control ethernet.

Blocking call on socket recv exited - most

likely due to mqueue restart

The tftp server process will exit, since it

fails to receive data from a remote client
due to restart of mqueue process.The
process will respawn itself.

Unable to send data over the control

ethernet

Sending the data to a remote node over

the control ethernet has failed.

[chars] error status [dec] ([chars]) seen

over Control Ethernet

A software entity is unable to transfer data

to/from the internal control ethernet server.
This may be caused by momentary
unavailability of internal buffers to the
ethernet server, which will recover by
itself; or, the ethernet server is
inresponsive. This is a n error message that
should only occur infrequently.

EDM initialization failed.\n

Failed to initialize the EDM, for CE-TFTP

server. The system will not be impacted
and will come up. *RECUR*

Failed to register tftpserv edm\n

Since the registration failed, the EDM

initialization for tftpserver will be failed.
System will continue to funtion and will
come up.

[chars]\n

The CE-TFTP server process exitted due to

some reason.

The CE-TFTP server process exited

because,[chars]\n

The CE-TFTP server process exited due to

specified reason mentioned in the message
related to the event handler to handle the
notification event from the EthServer when
a new packet arrives.

Debug event manager creation failed\n

The tftp server event manager which

handles the debug services failed.

Attaching to Event manager to handle the

timer expiry events has failed, with error
code: [chars]\n

The CE-TFTP server process exited since

attaching to the event manager to handle
the timer expiry events.The process will
respawn itself.

Unable to initialize mutex to synchronise

access to :[chars]\n

The CE-TFTP server process exited due to

failure in the Mutex initialisation at the
specified API. The process will be
respawned.

The file [chars] could not be accessed

because [chars]\n

The given file could not be accessed due to

reasons specified. Possible failures are lack
of read/write permissions.

File [chars] not found

The given file was not found at the

specified path

Unable to get the node id , error code:

[chars]\n

This failure can happen in show commands

as well as in main CE-TFTP server
process.The process will exit and respwan
itself.

The given filename is chekced againist '../'

The filename is invalid because of using '../' from getting around the directory
in file name\n
restrictions.

Unable to get out local MAC addresses\n

The CE-TFTP server process exited because

was not able to intitialize the local mac
address.The process will respwan itself.

Insufficient memory for '[chars]', [unsigned The CE-TFTP server process exitted due to
int] bytes\n
memory allocation failure.

Unable to allocate memory\n

Failure in CE-TFTP server - memory

allocation failure occured. The CE-TFTP
server process will exit and respawn itself.

Unable to derive the IP address for the

Conversion of nodeid to internal ethernet IP server from the nodeid. The CE-TFTP
address failed\n
process will exit and respawn itself.

Failed to initialize sock-lite database

The CE-TFTP server process will exit, since

it failed to initialize the sock-lite data base.
The process will respawn itself.

Failed to bind to sysdb namespace at

[chars]\n

The CE-TFTP server process was unable to

initialize the path mentioned in the
message.This is not funtionality
impacting,system will continue to funtion.

[chars] to sysdb failed at [chars], error

[dec] ([chars])\n

The CE-TFTP server process was unable to

work with the config space.

Failed to register verifier on path [chars]\n

The CE-TFTP server process was unable to

register for verification of tuples under the
config space.This is not funtionality
impacting, system will continue to funtion.

Failed to initialize debugging services\n

Failed to initialize debugging services for

CE-TFTP server. The system will continue to
funtion as this is not a system impacting
issue.

Initialization of the Event manager to

handle the timer expiry events failed

The CE-TFTP server process exited since

initialization of the event manager to
handle the timer expiry events failed.The
process will respawn itself.

Bag encode of CE-TFTP server information

has failed,error code : [chars]

As mentioned in the message, the bag

encode has failed for the CE-TFTP server.

Failed to register tftpserv bag\n

Since the registration failed, the EDM

initialization for tftpserver will be failed.
System will continue to funtion and will
come up.

The CE-TFTP server process is exiting

because [chars]\n

The opening/binding of the socket for the

tftpserver thread might be failing as
mentioned in the message. The process
will exit and respawn itself.

The event manager has received an

unknown event\n

The event manager has received an

unknown event.This is not system
impacting,the system will continue to
funtion normally.

The file [chars] could not be accessed

because [chars]\n

The given file could not be accessed due to

reasons specified.

The received packet of type :[[chars]] is

getting dropped because [chars]\n

Received an invalid packet from Ethserver

due to the specified reason in the
message,hence dropping the packet.

[[chars]]: [chars], dropping packet\n

Received an invalid packet. No action

required, this packet will be ignored
(dropped).

Unrecognised protocol field in IP header =

[hex] from [chars], dropping packet\n

Received a packet with an invalid protocol

field from EthServer. No action required,
this packet will be ignored (dropped).

[[chars]]: [chars] = [hex] from [chars],

dropping packet\n

Received a packet with an invalid protocol

field. No action required, this packet will be
ignored (dropped).

[chars] filename: [chars] \n

A kernel dump started/finished to the file

as mentioned in the message from a
remote node via TFTP.

[chars] filename: [chars] \n

A kernel dump started/finished from a

remote node via TFTP.

Failed to register debugging services\n

Failed to register debugging services for

tftp server. The system will continue to
funtion, as this is not ststem impacting
issue.

Process initialization failed with error \

[chars]\: [chars]. Restarting DAPS...

A failure occurred during the initialization

of DAPS process. The exact reason for the
failure is mentioned in the message. This
could happen because of the following
reasons. 1) A problem in allocating local
resource because of memory shortage or
software error. 2) Problem in initiating
connection to an external/dependent
module either because the external module
is not ready or a race condition has
occurred. 3) Software error either in local or
external module.

Client requests an address/prefix from a

[chars]: configured range [chars]-[chars]
specific subnet and the configured range
exceeds the subnet limit ([chars]/[unsigned does not match to the subnet. Address
int])
allocation will fail, as a result.

Utilization exceeded high threshold ([dec]

%) for pool [chars], vrf [chars]

Utilization exceeded high threshold for

specified pool. Pool may deplete very soon
and so it would be good to add more
address ranges for allocation to new
clients. Otherwise new address allocation
requests will fail. Pool utilization can be
monitored using the command 'show pool
ipv4/ipv6 name <pool_name>'.

Utilization exceeded high threshold across

all pools. The unallocated addresses may
deplete very soon and so it would be good
to add more pools or address ranges for
allocation to new clients. Otherwise new
allocation requests will fail. Pool utilization
Utilization exceeded high threshold across can be monitored using the command
all pools
'show pool ipv4/ipv6'.

Utilization dropped below low threshold

([dec]%) for pool [chars], vrf [chars]

Utilization dropped below low threshold for

specified pool. It shows that the pool is not
utilized well at this point of time. If the
utilization is always less than low
threshold, pool size can be reduced. Pool
utilization can be monitored using the
command 'show pool ipv4/ipv6 name
<pool_name>'.

Utilization dropped below low threshold

across all pools

Utilization dropped below low threshold

across all pools. It shows that the existing
pools are not utilized well at this point of
time. If the utilization is always less than
low threshold, pool size can be reduced.
Pool utilization can be monitored using the
command 'show pool ipv4/ipv6'.

Asserting failed at function:[chars] line:

[dec] for:[chars]

Some essential condition to move on in the

system has failed.

[chars] checkpoint failed: [chars]

The error occurred due to failure in

checkpoint creation either due to the
checkpoint were tried to be written on nonactive node or due to some internal error.

[chars] connection down encountered at

[chars]

The DPM/IEDGE connection is down.

[chars] fetch error..!, error: [chars]

DPM interacts with AAA for getting identity

of the session. This error occurs when DPM
tries to get subscriber ifhandle

Initialization failed: [chars]

An error occurred during initialization.

This error occurs when the supplied packet

Cannot setup or duplicate a DHCPD server ptr is NULL. Most likely a resource problem
socket packet
within the system.

Error initializing the system database:

[chars]. Error: [chars]

An error occurred when initializing the

system database.

A failure occurred during the initialization

Failure during intialization of [chars]. Error: of the process. This may have resulted in
[chars]
the restart of the process.

Invalid! default gateway, Client([chars])

Release/Renew send may fail

The error occurs when Server is in process

of sending OFFER/ACK to client, either
without default gateway or subnet of
default gateway and yiaddr mismatched.
Client may not be able to send Renew and
Release.

Address [chars] is not assigned to [chars]

The error occurs when Server is in process

of sending ACK to client and while doing
this tries to get IntF address/Client
State/VRF etc. where it encounters failure.
Thus leading to failure of Address
assignment to client.

Binding database not loaded

Fail to load the DHCPv6 binding database.

Binding database not loaded

Fail to load the DHCPv6 binding database.

Opening [chars]: [chars]

Fail to open a DHCPv6 binding database

file.

Opening [chars]: [chars]

Fail to open a DHCPv6 binding database

file.

Reading file: [chars]

Fail to read a DHCPv6 binding database file.

Reading file: [chars]

Fail to read a DHCPv6 binding database file.

Writing file: [chars]

Fail to write a DHCPv6 binding database

file.

Writing file: [chars]

Fail to write a DHCPv6 binding database

file.

Initialization failed: [chars]

An error occurred during initialization.

Initialization failed: [chars]

An error occurred during initialization.

Failed to join [chars] on [chars] ([chars])

Failed to join a multicast group on the

interface.

Failed to join [chars] on [chars] ([chars])

Failed to join a multicast group on the

interface.

Error mutex lock: [chars]

A mutex lock/unlock problem.

Error mutex lock: [chars]

A mutex lock/unlock problem.

Cannot setup or duplicate a DHCPv6 server Most likely a resource problem within the
socket packet
system.

Cannot setup or duplicate a DHCPv6 server Most likely a resource problem within the
socket packet
system.

Error initializing the system database:

[chars]

An error occurred when initializing the

system database.

Error initializing the system database:

[chars]

An error occurred when initializing the

system database.

Route request failure: [chars]

A route insertion/deletion request failure.

Most likely due to resource issue (memory,
CPU utilization, etc.)

Route request failure: [chars]

A route insertion/deletion request failure.

Most likely due to resource issue (memory,
CPU utilization, etc.)

Specify an outgoing interface for the relay

destination or use the mhost command

Need to specify an outgoing interface if the

relay destination address is multicast. Use
the interface option in the relay command
or the mhost command.

Specify an outgoing interface for the relay

destination or use the mhost command

Need to specify an outgoing interface if the

relay destination address is multicast. Use
the interface option in the relay command
or the mhost command.

Received a DHCPv6 Release/Decline

message from a suspicous client and
Received a suspicious delete request for
ignored the message to be safe. It could be
([chars]) from (src:[chars], client-id:[chars]) a spoofing attack.

Received a DHCPv6 Release/Decline

message from a suspicous client and
Received a suspicious delete request for
ignored the message to be safe. It could be
([chars]) from (src:[chars], client-id:[chars]) a spoofing attack.

The domain_services process failed to

attach an event handler to receive event
messages sent to it. The error is normally
seen during initialization of DNS process
(i.e. domain_services) or while trying to
fetch hostname or address through DNS
query. Such errors should go away with
Failed to attach an [chars] handler: [chars] process restart

Failed to create a channel for [chars]

The domain_services process failed to

create a channel so that other processes
can send event messages to it. The error is
normally seen when initializing DNS
process

The domain_services process failed to

create chunk memory for its domain name,
domain address and domain alias data
structures. The message would appear
during initialization of DNS process (i.e.
Failed to allocate chunk memory for [chars] domain_services).

Failed to create a event connection

structure: [chars]

The domain_services process failed to

create and initialize an event connection
structure. If the connection ever goes
away, event connection manager will
automatically tries to re-connect.

[chars]: [chars]

The domain_services process failed to

create and initialize its various managed
timers.This message would appear during
Initialization of DNS process (i.e.
domain_services). The error should go
away with process restart

[chars]: [chars]

Error in the domain edm server setup. EDM

is used for storing and retrieval of fast
changing data. Due to this error, the show
commands might get impacted.

Unexpected process termination: [chars]

The domain_services process was

terminated unexpectedly. Please check if
the error goes after doing process restart
domain_services loc all.

Failed to get SysDB connection id: [chars]

The domain_services process failed to

obtain the connection id for an SysDB
event connection. The error would normally
appear during configuring sysdb event
connection.

Failed to open a event connection to

[chars]: [chars]

The domain_services process failed to open

a event connection. The message would
appear during initialization of DNS process
(i.e. domain_services) when it is trying to
create sysdb connection. Such errors are
not expected and should go away with proc
restart domain_services

Failed to register for debugging events:

[chars]

The domain_services process failed to

register for notification of changes to the
domain_services debug flag(s).

Failed to register handlers for SysDB

events: [chars]

The domain_services process failed to

register its verification and apply handlers
for SysDB events. Such errors are not
expected and should go away with process
restart domain_services.

Failed to register for RPC service

The domain_services process failed to

register its RPC server with the RPC
portmapper. The message would appear
during initialization of DNS process (i.e.
domain_services) and normally would go
away after process restart domain_services

Domain services failed to notify the

completion of init: [chars]

domain services failed to notify the

completion of initialization

function [chars]([dec] [chars] [dec] [dec])

called

This is the function used for building all

types of queries

[chars]

Displays the debug msgs as they happen

[chars] [chars]

Displays the debug msgs as they happen

Failed to register process's specific error

codes: [chars]

The domain_services process failed to

register its specific cerrno codes and
messages.

The FHRP Output process failed to signal

end of initialization to the Main thread and
FHRP Output Packet thread failed to signal will leave the Main thread hung. The
end of initialization to the Main thread:
process will assert to recover from this
[chars]
condition.
The FHRP Output process Packet thread
was unable to signal to the Main thread to
request a resync with an FHRP protocol and
FHRP Output process is out of sync with the is now out of sync. Process restart may be
FHRP protocols: [chars]
required to recover.
The FHRP output process was unable to
obtain an event connection manager. FHRP
Output process client functionality on the
Failed to create event connection manager: affected node may be reduced until the
[chars]
problem is resolved.

FHRP Output failed to queue a [chars]

event to the Main thread: [chars]

The FHRP Output process failed to queue

an event to the Main thread. If possible
then the FHRP Output process will attempt
to recover and retry. Clients of the FHRP
output process (such as HSRP and VRRP)
will observe inconsistent behavior until this
is resolved.

Out of memory (failed attempt to reserve

%zu bytes)

The FHRP Output process was not able to

allocate the memory that it needed to
complete the operation. FHRP Output
process client functionality on the affected
node may be reduced until the problem is
resolved.

FHRP Output failed to queue a [chars]

event to the Packet thread: [chars]

The FHRP Output process failed to queue

an event to the Packet thread. The FHRP
Output process will attempt to recover and
retry. Clients of the FHRP output process
(such as HSRP and VRRP) will observe
inconsistent behavior until this is resolved.

The FHRP output process communications

failed to initialize correctly. In this situation
the FHRP output process retries the
initialization, but may not recover if the
failure to initialize persists. Clients of the
FHRP output process (such as HSRP and
FHRP output communications initialization VRRP) will not be able to send packets until
failed: [chars]
the initialization succeeds.

More than the maximum supported

number of MAC address filters has been
installed for this interface meaning traffic
to some virtual router IP addresses will be
Maximum MAC address filters for interface dropped. Note that for sub-interfaces the
<<CH[hex]>> exceeded
limit is per parent interface.

Out of [chars] memory (failed attempt to

reserve [unsigned int] bytes)

The process was not able to allocate the

memory that it needed to complete the
operation. FHRP functionality may be
reduced until the problem is resolved.

FHRP Library Initialization failed: [chars]:

[chars]

The FHRP library failed to initialize

correctly. In this situation HSRP/VRRP
restarts, but may not recover if there is a
persistant error in the IOSXR system and
HSRP/VRRP is still unable to reestablish its
connections and initialize successfully.

BGP PA configuration for ifh [hex],

if:<<CH[hex]>> failed due to [chars]

FIB is not committing BGP PA configurations

due to internal error.

Unable to allocated needed stats counters,

Failed to alloc stats counter err [dec]: table accounting features may not be working
[dec]
properly.

[chars] [chars] (errno=[dec])

There was a critical system call failure

resulting in a failure to provide some
system service as indicated in the message
text.

Failed to register transition handler

There was a critical system call failure

resulting in a failure to provide some
system service as indicated in the message
text.

Failed to initialize tracing - [chars]: [chars]

(errno [hex])

There was a system call failure during

initialization of the ltrace logging system.
Ltrace logs may not be available.

Failed to respond to transition request:

[chars] (errno [hex])

There was a critical system call failure.

System may not have handled certain
transitions properly.

[chars] [chars] (errno [hex])

There was an internal failure that may

impact non-essential system function

Failed to create Event Manager

An error occurred while creating the

process event manager.

Error while waiting on next event

An error occurred while using the process

event manager.

Failed to bind to SysDB: error [hex]

('[chars]')

An error occurred while using SysDB.

Failed to scan configuration: error [hex]

('[chars]')

An error occurred while using SysDB.

Failed to register for config verification:

error [hex] ('[chars]')

An error occurred while using SysDB.

Failed to unbind from SysDB: error [hex]

('[chars]')

An error occurred while using SysDB.

Failed to signal process ready: error [hex]

('[chars]')

An error occurred while signalling that

initialization was complete.

Failed to bind to SysDB: error [hex]

('[chars]')

An error occurred while using SysDB.

Failed to unbind from SysDB: error [hex]

('[chars]')

An error occurred while using SysDB.

Call to [chars] from function [chars]

returned error: [chars]

An internal system error occured.

The Addresses configured in the Pool are

now [dec], please confirm if there isn't a
mis confiugration

The Address configured are too many. The

message is to confirm if this is intentional.

[dec] Ranges for [dec] Address. Consider

coalescing Addresses

The number of ranges configured for the

addresses in pools is too large. Having
more addresses in a single range and
thereby having smaller number of ranges is
optimal for memory. An informational
message will be generated if At 1
Thousand Ranges there are < 10 Addr per
range At 10 Thousand Ranges there are <
50 Addr per range At 50 Thousand Ranges
there are < 100 Addr per range At 70
Thousand Ranges there are < 150 Addr per
range

Failed to free the avl tree node

The process has failed to free an avl tree

node.

function [chars] failed: [chars]

A call to some system function to initialize

bcdls failed. ip arm consumer initialization
api would return error back to the client.

Invalid global if_set_type on a LC

A client registration on a Linecard returned

error due to invalid parameter.

Failed to malloc [unsigned int] bytes

The process has failed to acquire the

required amount of memory.

Couldn't decode address TLV for interface

[chars] [TLV 0x[pointer]/[dec]] because
[chars]

This is an internal error. It indicates that an

address information structure couldn't be
decoded correctly. This could leave the
affected process in an inconsistent state.

Event set retry failed, error : [chars]

A call to set the retry timeout for producers

to bind with iparm failed. This will call
default timeout values to be used.

[chars]

Update received

Interface '[chars]' has more visible

addresses than the stored visible count
'[dec]'

This is an internal error. It indicates that the

addresses visible to the clients are more
than expected. This can result in IP ARM
not sending an address update to its
clients.

The [chars] address [chars]/[dec] on

[chars] conflicts with other [chars]
addresses and has been forced down

The specified IP address conflicts with

other IP addresses on the network portion
of their IP addresses and has been forced
down to prevent multiple operational
conflicting IP addresses. This is an
inconsistent configuration.

Conflict data structure not found for

([chars])

An IP info structure with conflict flag set is

not found in the conflict database. This is
an error condition indicating IP ARM
database has erroneous information. This
can cause some unexpected behavior
relating to the ip address not found in the
database.

When multicast routing is turned on PIM

will choose a default interface, based on
whether the default has been configured
and it's enabled state. An error was
An error occured with the default interface encountered in making PIM provided
provided by PIM: [chars]
interface as mhost default interface.

Couldn't decode address TLV for interface

[chars] [TLV 0x[pointer]/[dec]] because
[chars]

This is an internal error. It indicates that an

address information structure couldn't be
decoded correctly. This could leave the
affected process in an inconsistent state.

The [chars] unnumbered interface [chars]

references the unnumbered interface
[chars] and has therefore been forced
down

The IP unnumbered specified in the

message references another unnumbered
interface. This is not consistent
configuration.

The configured mhost default

interface([chars]) is a management
interface, so, can't be used as the active

Management interfaces(on the RPs) are not

allowed to be the mhost default interface
as multicast routing is disabled on the
management interface.

The [chars] address [chars]/[dec] on

[chars] is no longer forced down due to
[chars] address conflicts

The IP address specified in the message

previously conflicted with other configured
IP addresses on some portion of the
network portion of their IP addresses. The
IP address no longer conflicts.

[chars]

The rouer id configuration CLI has been

deprecated. This command has taken on
effect.

The global router id has become

unavailable

The global router id has become

unavailable.

The IP unnumbered specified in the

The [chars] unnumbered interface [chars] message references previously referenced
no longer references another unnumbered another unnumbered interface. This is no
interface
longer the case.

Encountered failure [chars] in binding to

[chars] for [chars]

IP ARM process encountered failure in

binding to SysDB. It will recover itself by
restarting. Typically this error is caused if
sysdb is unavailable for an extended
period.

Initialization failed, module: [chars],

operation: [chars], error: [chars]

Initialization of the IPv4 ARM or IPv6 ARM

process failed. This can happen when the
process is (re)starting and any basic
infrastructure service required by the
process is not available. The process
recovers by restarting itself. If the error
message doesn't persist, it can be ignored.
If the error message persists, depending on
whether IPv4 ARM or IPv6 ARM failed to
initialize, some basic ipv4 or ipv6
functionality may not be available.

Failed to initialize ltrace: [chars]:

IP ARM failed to initialize module to allow

tracing of important events. This may
happen during process (re)start. The
process will exit and try to recover from the
error.

The ipv4/ipv6 EA is trying to program FIB or

the platform and a delay was noticed. This
[chars] update is taking longer than [dec] delay could lead to other undesirable side
secs for [dec] items, please investigate for effects such as failing to apply
blocked processes
configuration etc.

Platform update failed: [chars] - [chars]

(<<CH[hex]>>)

An error occurred while trying to update

the platform code with information about
the interface whose handle is contained in
the message.

Platform update failed for [dec] interface:

[chars] - [chars]

An error occurred while trying to update

the platform code with information about a
batch of interfaces. This update will be
replayed.

Failure [chars] in creating event manager

The IP ICMP library could not create the

event manager to handle the events to be
received by the process. This can happen
when the process is (re)starting. If the error
message doesn't persist, it can be ignored.
If the error message persists, some basic
icmp functionality may not be available.

ip icmp dll initialisation failed. [chars]:

[chars]

There was a software error during process

startup.

Encountered failure [chars] in binding to

[chars] for [chars]

IP ICMP Lib encountered failure in binding

to SysDB. Typically this error is caused if
sysdb is unavailable for an extended
period.

Encountered failure [chars] in registering

notifiee at [chars] for [chars]

IPv4 Management Agent encountered

failure in registering notifiee with SysDB. It
will recover itself by restarting. Typically
this error is caused if sysdb is unavailable
for an extended period.

Encountered failure [chars] in registering

verifier at [chars] for [chars]

IP ICMP library encountered failure in

registering verifier with SysDB. Typically
this error is caused if sysdb is unavailable
for an extended period.

NTP process detected error : [chars],

restarting to recover.

NTP process exits and restarts when it

detects a failure. If the error does not
persist it can be ignored.

NTP process detected error :[chars]

because of [chars], restarting to recover

NTP process exits and restarts when it

detects a failure. If the error does not
persist it can be ignored.

NTP calendar update failed

An error occurred during calendar clock

update. This causes the calendar clock
cannot be adjusted accordingly to NTP
server or peer

Unable to update NTP clock - [chars]

([dec])

An error occurred when updating system

clock with the clock adjust process of clock
hardware. This causes the internal clock on
active RP cannot be adjusted accordingly
to NTP server or peer. The string tells that
which process has failed. The integer
specifies the error for internal usage.

An error occurred during clock drift

checkpoint handling. The string tells the
points of process that error has occurred.
NTP drift update - [chars] - failed with error The integer specifies the error for internal
[dec]
usage.

[chars]

Frequency Error exceeded NTP tolerable

limit (500 PPM).

All NTP peer connections failed.

The ntp server lost all connections with the

clock sources.

High priority NTP peer connection lost Stratum [dec]->[dec].

The ntp server lost the connection with a

high-priority clock source. The Stratum tells
the change of server stratum.

High priority NTP peer connection

recovered - Stratum [dec]->[dec].

The ntp server recovered the connection

with a high-priority clock source. The
Stratum tells the change of server stratum.

The ntp server recovered a connection with

At least a low priority NTP peer connection one of the configured clock source. The
was recovered - Stratum [dec]->[dec].
Stratum tells the change of server stratum.
Clock is in sync with the server with an
offset of [chars] ms

when the node state change to insync with

the ntp server.

Clock goes out of sync with the server

when the node state change to unsync with

the ntp server.

Synchronization lost : [chars] : [chars]

NTP lost synchronization due to one of the

following reasons: 1. Server authentication
failed 2. Access denied by remote server 3.
Peer unreachable or clock selection failed
4. The association was removed 5. The
clock was stepped and needs to be
resynced 6. The ephemeral client
association was timeout 7. ntp clear
command

Detect an unusual offset time value.

The offset between the active clock source

and the system clock exceeds 1000
seconds.

Failed to decode [chars] data

IPV4 could not decode data supplied by the

indicated external data manager.

Failed to encode [chars] data in external

data manager

A process has requested information from

ipv4_io through SysDB, probably as a result
of executing a show command. The data
requested could not be encoded.

IPv4 Management Agent encountered

failure in encoding the bag that is
supposed to carry encoded information to
be passed on clients of IPv4 MA. Typically
the client is a managebility agent like exec
spawned by show CLI. As a result of this
error the client may not receive the
intended information from IPv4 MA. If it is a
managebility request that triggered this,
the request may be retried. Typically this
error is caused if there is mismatch
between the bag format and the
information to be encoded. At other times
the error might be due to process' memory
'Failure [chars] in encoding bag for [chars]' corruption or low memory.

Failed to connect to SysDB in [chars]

([chars])

Failed to connect to SysDB while starting

the indicated subsystem.

'[chars] Failed with [chars]'

IPv4 Management Agent encountered

failure in registering as a server for
managebility requests. It will recover itself
by restarting. Typically this error is caused
if sysdb is unavailable for an extended
period or if there is another process that
instance that is registered as the server for
the same information.

IPV4_IO failed to register the [chars]

external data manager data blocks

The ipv4_io process failed while attempting

to register the indicated external data
manager data blocks with SysDB.

'Encountered [chars] in [chars]'

IPV4 Management Agent encountered

failure in registering bag format used to
encode information sent via SysDB. It will
recover itself by restarting.

The IPv4 IO process could not allocate

IPv4 operation '[chars]' failed due to lack of memory needed to complete the specified
memory
operation.

Cannot update option registry in ipv4_io:

[chars]

The ipv4_io process encountered a

software error while creating an entry in
the option registry requested by an
application

Port arbitrator error. [chars]: [chars]

The ipv4_io process encountered a

software error while connecting to the port
arbitrator.

Error: Port Arbtitrator allocated a NULL

handle

The ipv4_io process was given a NULL

handle by the port arbitrator.

Error. [chars]: [chars]

The ipv4_io process has encountered a

software error during normal operation
from which it cannot recover.

Unknown [chars] received by ipv4_io

([dec])

The IPV4_IO process has received an

unknown event message.

There was a software error during process

Process initialisation failed. [chars]: [chars] startup.

IPv4 was unable to add membership to the

group. Commonly, this is done for
224.0.0.1 by ipv4-ma with no associated
socket when an interface is enabled, or for
all groups (multicast promiscuous mode)
whem multicast routing is enabled. Failure
'IP add multicast group membership failed might result in issues in multicast host
for group [chars] on interface
functionality or multicast fwding
<<CH[hex]>>'
functionality.

'Failed to register create notification for

interface [chars] ([chars]: [chars])'

IPv4 MA registers to be notified of

Forwarder interface creation if its not
already available when IPv4 MA starts. The
process tries to recover by reconnecting to
IM. If the error persists, the forwarder will
not be available for IPv4 packets.

'Failure [chars] in attaching handler for

async pulse [hex]'

The IPv4 MA process could not register the

handler for the indicated event. This can
happen when the process is (re)starting.
The process recovers by restarting itself. If
the error message doesn't persist, it can be
ignored. If the error message persists,
some basic ipv4 functionality may not be
available.

'Failure [chars] in attaching handler for

sync msgid [hex]'

The IPv4 MA process could not register the

handler for the indicated event. This can
happen when the process is (re)starting.
The process recovers by restarting itself. If
the error message doesn't persist, it can be
ignored. If the error message persists,
some basic ipv4 functionality may not be
available.

The IPv4 MA process could not create the

event manager to handle the events to be
received by the process. This can happen
when the process is (re)starting. The
process recovers by restarting itself. If the
error message doesn't persist, it can be
ignored. If the error message persists,
some basic ipv4 functionality may not be
'Failure [chars] in creating event manager' available.

'Failed to get interface name of local fint

([chars])'

Failed to add ipv4 to fint which represents

the fabric interface. This is retried by
reconnecting to IM. If this error is seen only
once, it may not have significant impact. If
this error is persistent, it may mean that it
is not possible to send/receive packets vai
the fabric.

'IP remove multicast group membership

failed for group [chars] on interface
<<CH[hex]>>'

IPv4 was unable to remove membership to

the group. Commonly, this is done for
224.0.0.1 by ipv4-ma with no associated
socket when an interface is disabled, or for
all groups (multicast promiscuous mode)
whem multicast routing is disabled. It
might be ok to ignore the failure.

'Encountered failure [chars] in binding to

[chars] for [chars]'

IPv4 Management Agent encountered

failure in binding to SysDB. It will recover
itself by restarting. Typically this error is
caused if sysdb is unavailable for an
extended period.

'Encountered failure [chars] in registering

notifiee at [chars] for [chars]'

IPv4 Management Agent encountered

failure in registering notifiee with SysDB. It
will recover itself by restarting. Typically
this error is caused if sysdb is unavailable
for an extended period.

'Encountered failure [chars] in registering

verifier at [chars] for [chars]'

IPv4 Management Agent encountered

failure in registering verifier with SysDB. It
will recover itself by restarting. Typically
this error is caused if sysdb is unavailable
for an extended period.

'Proposed IP MTU [dec] of [hex] is smaller

than minimum allowed (68). IPv4 may not
work correctly on this interface'

Minimum IPv4 MTU must be 68 bytes.

Available link MTU is below the minimum
IPv4 link MTU (68). IPv4 may not work
correctly on this interface.'

'interface add: Interface already exists for

[chars] with ifh ([hex]) - by [chars],
returning error'

IPv4 MA already has the interface being

newly added in its internal store. This
potentially indicates that IPv4 MA missed
the delete from SysDB and Interface
Manager for this interface & hence is out of
sync.

'The link payload ([dec]) is less than the

IPv4 link mtu ([dec])'

The link payload is lesser than the IPv4 link

MTU. Hence the operational MTU is set to
the link payload and not the configures
MTU value

'The primary address being unconfigured

([chars]) is different from the current
configured primary address ([chars]). This
will still result in unconfiguring the current
configured primary address([chars]) please take corrective action before the
commit if this is not intended.'

When a unconfig of ipv4 primary address is

performed and the current configured
primary address is different from the one
specified, even then the current one will
get unconfigured. This warning message
warns the user so if need be corrective
action can be taken before the commit.'

'ifhandles mismatched, IM ifh=[hex], MA

ifh=[hex]'

A mismatch in interface handles has been

been detected. This is an indication that IM
is potentially out-of-synched with MA. This
problem occurs when interfaces are
deleted while Interface Manager (IM) is not
available.

'Cannot initialize [chars]: [chars] ([hex])'

Initialization of the IPv4 MA process failed.

This can happen when the process is
(re)starting and any basic infrastructure
service required by the process is not
available. The process recovers by
restarting itself. If the error message
doesn't persist, it can be ignored. If the
error message persists, some basic ipv4
functionality may not be available.

IPv4 MA got an unexpected cookie for the

specified interface. This failure indicates
that the IPv4 data path feature may not
programmed correctly.IPv4 MA tries to
recover from this error by a timer based
retry.If the message is not seen continuosly
'Got invalid cookie for replicating interface for a particular interface and if functionality
<<CH[hex]>>, cookie - [hex], batch cookie looks ok, the recovery might have been
[hex]'
successful.

'Unknown IPC [chars] [dec] received'

The IPV4_MA process has received an

unknown IPC. It will ignore the msg if it is in
the form of an asynchronous pulse. If the
msg is in the form of a synchronous
message, it returns an error to the sender
which in turn is expected to take
appropriate action. This can happen if IPv4
MA receives an IPC for which it doesn't
have a handler registered due to either it
unregistering the handler without updating
the sender or due to the sender sending an
incorrect IPC. It may be safe to ignore this
message if there is no visible loss of
functionality.

'IP add multicast group membership failed

for group [chars] on [chars]'
Unable to add membership to the group.

'IPV6 MA failed to initialize the

configuration sub-system'

The IPV6 MA process failed to initialize its

config handling mechanism and interaction
with sysdb.

'IPV6 MA Event Conn Error - [chars]

([chars])'

The IPV6 MA process failed to initialize its

event conn mgr infra.

'IPV6_MA Event Manager create failed'

The IPV6_MA process failed to create the

event manager.

'Failed to initialize as LAS producer. Error -- Failed to initialize as producer of the Local
[chars]'
Address Service Database

'[chars]: ([chars])'

This might result in failure generating

linklocal address on certain LC.

'IP remove multicast group membership

failed for group [chars] on [chars]'

Unable to add membership to the group.

'IPV6 MA failed to initialize event callback

handlers'

The IPV6 MA process failed to initialize

various callback handlers for various
synchronous and asynchronous events.

'Failed to connect to SysDB in [chars]

([chars])'

Failed to connect to SysDB while starting

the indicated subsystem.

'Failed to initialize as Address Svr. Error -[chars]'

Failed to initialize as local IP Address Server

'IPV6 MA failed to initialize the interface

database'

The IPV6 MA process failed to initialize its

interface database

'IPV6 MA debug initialization failed'

The IPV6 MA process failed to initialize

debug support

'Failed to initialize [chars], Error -- [chars]

([dec])'

Failed to initialize as producer of the Local

Address Service Database

'interface add: Interface already exists for

[chars] with ifh ([hex]) - by [chars],
returning error'

IPv6 MA already has the interface being

newly added in its internal store. This
potentially indicates that IPv6 MA missed
the delete from SysDB and Interface
Manager for this interface & hence is out of
sync.

'[chars] [dec]: <<CH[hex]>>'

Minimum IPv6 MTU must be 1280.

Available ipv6 mtu is not within the valid
range.

'The link payload ([dec]) is less than the

IPv6 link mtu ([dec])'

The link MTU is lesser than the IPv6 link

MTU. Hence the operational MTU is set to
the link MTU and not the configures MTU
value

'ltrace init failed during [chars] [chars]

because [chars]'

There was a failure during an ltrace_init api

call which resulted in the failure as
indicated in the message text.

'Failed to remove [chars] encapsulation

from [chars] ([chars])'

An error encountered while removing caps

for batch of interfaces.

'Error recovery failed because ([chars])'

The IPV6 MA process failed to add context

to timer.

The IPV6 MA process failed to initialize its

'IPV6 MA Timer initialization failed - [chars]' timers.

'IM API Failure ([chars]) : [chars]'

Failure encountered while updating

Interface informations.

The IPv6 Link local duplicate address

detection is restarted as interface was
down earlier due to DAD. Now the interface
reset occurred indicating that the earlier
physical loop condition might have been
'Restarting IPv6 LL DAD on <<CH[hex]>>' cleared.

'Failed to initialize [chars]: [chars] ([hex])'

The IPv6 MA process failed to init software.

This can happen when the process is
(re)starting and any basic infrastructure
service required by the process is not
available.

Duplicate address [chars] has been

detected

Address duplication has been detected.

This error is caused by a a misconfiguration. More than one system,
connected to the same media, are
configured with the same ip address. Once
an address is found to be duplicated, it is
set in DUPLICATE state and is not available
for use by upper layers. If the duplicated
address is a Link Local address, then the
ipv6 interface is also taken to DOWN state.

Unable to [chars] adjacency [chars] AIB.

A problem occurred while attempting to

add/delete an adjacency into/from AIB. This
error happens when the AIB process is
temporarily unavailable. The problem is
normally recovered once the AIB process
becomes operational.

Unable to [chars] a connection to AIB

[chars] ([dec])

The attempt to communicate with AIB

failed. This is normally a transient error, it
occurs when the AIB process is temporarily
unavailable. The error will be recovered
once the AIB process becomes operational.
If the error persists, it is an indication that
the AIB process is not operational or being
blocked by other process.

[chars] unable to create the event

manager.

IPv6 ND has failed to create the event

manager. It will try to recover from the
error by exiting.

[chars] [chars] (err=[chars])

An error in the system trace facility has

occurred. This condition might have been
caused by lack of system resources. The
error will disable IPV6 Neighbor Discovery's
tracing function, but no other IPv6 ND
fuctionalities will be impacted.

The attempt to communicate with IFH

server failed. This is normally a transient
error, it occurs when IFH server process is
temporarily not available. If the error
Unable to [chars] connection handle to IFH persists, it is an indication that the ifh
[chars] ([dec])
server process is not operational.

The attempt to communicate with IM failed.

This is normally a transient error, it occurs
when Interface Manager is temporarily not
available. If the error persists, it is an
indication that the interface manager
process is not operational or it is being
Failed to bind to IM ([chars]): [chars] ([dec]) blocked by some other process.

[chars] [chars]

IPv6 Neighbor Discovery (ND) does not

operate on this interface type. This error
occurs when ND process receives a punted
data packet from the L2 for MAC address
resolution on a point-to-point interface.
This problem could happen due to some
transient errors in the layer-2 switching
software.

The maximum RA interval must be in the

range of 4-1800. Minimum RA interval must
Minimum RA interval must be in the range be between 3 - 0.75 * maximum RA
of 3 - [dec] (0.75 * max RA interval)
interval.

Failed to [chars]: [chars] ([dec])

An attempt to communicate with sysdb

failed. This error is normally transient and
could be recovered. If the error condition
could not be recovered, IPv6 ND will not
function properly.

Interface <<CH[hex]>>, over cache limit

count: [dec], resetting every [dec] hits

After IPV6 Neighbor Discovery (ND) cache

limit for an interface is reached, next hit
will trigger this message. Also, the
message is shown every 1000 hits to the
cache limit per interface scoped.

clear mapping ipv6 ([dec]) from media

[chars] failed: [chars]

--

couldn't attach FSV, err: [chars]

The IPv6 NetIO component was unable to

attach the required FSV before passing the
packet to the IPv6 partner process. The
Packet was dropped.

[chars] : Failed for ipv6 proto to [chars]

([chars])

netio media register or callback error.

Cannot lock packet mutex in function

[chars], err: [chars]

The IPv6 NetIO component was unable to

lock packet mutex while doing a control
action. The control action failed.

IPv6 received a packet bound to a

nonexistent interface, err: [chars]

--

couldn't duplicate packet (no redirect

generated), err: [chars]

A packet has been sent to us when the

sender should have been able to directly
reach the destination. We were therefore
also trying to generate an ICMP redirect
message, but were unable to do so. The
original packet would have been forwarded
normally.

Protocol Initialization failed, error -- [chars] IPv6 Protocol failed to intialize the netio
([dec])
datapath.

couldn't read punt reason, err: [chars]

The IPv6 NetIO component was unable to

read the Packet Punt Reason supplied by
the Hardware forwarding component. The
Packet was dropped.

IPv6 can't access pak [pointer] header in \

[chars]\ - need slow routine

The IPv6 base header in the packet could

not be directly accessed in the named
routine, and hence the packet was
dropped. This is due to the packet not
being within the first particle or the header
not being completly contained within one
particle. If the slow switching routines
(using pak_netio_ API calls) had been
compiled in then the packet could have
been switched.

set mapping ipv6 ([dec]) to media [chars]

failed: [chars]

--

A error occurred during debug initialization, The IPv6 NetIO component encountered an
err: [chars]
error during debug initialisation

'Failed to add [chars] encapsulation to

[chars] ([chars])'

Failed to add pre-switch and pre-route caps

to FINT

'IPv6 IO Debug Initialisation Failed'

IPv6 IO failed to initialise debugging

'Failed to open external data manager in

[chars]'

While processing the indicated show

command, the ipv6_io process could not
connect to the SysDB server.

'IM API Failure ([chars]) : [chars]'

Failed to create and control FINT

'[chars] ([chars])'

IPv6 IO failed to initialise some services.

'[chars] [chars] [chars]'

There was a failure during an ltrace_init api

call which resulted in the failure as
indicated in the message text.

'Error: Port Arbtitrator allocated a NULL

handle'

Handle allocated by port arbitrator is

invalid. This might be because the system
is low in memory.

'IPv6 IO Packet Manager connection Failed: The IPv6 IO process failed to connect to the
([dec]) [chars]'
packet manager

'IPv6_IO could not transfer packet to the

transport layer ([unsigned int], [chars])'

IPv6_IO attempted to write a packet to the

transport layer and failed.

'Failed to connect to SysDB in [chars]

([chars])'

Failed to connect to SysDB while starting

the indicated subsystem. This usually
happens when the process is starting up.

'Default connection to SysDB failed

([chars], [chars])'

Could not connect to SysDB.

'IPv6 IO failed to create evm conn for

[chars]: ([dec]) [chars]'

The IPv6 IO process failed to create a

connection to a server

'Couldn't bind with Port Arbitrator for local

interest, error = [chars]'

A call made to pa_client_bind has failed.

'Error in binding [chars] for local interest

with Port Arbitrator'

A certain ICMP6 type couldn't be registered

with PA.

'Failed trying to create the SysDB item

[chars] ([chars])'

Failed to create an item in SysDB.

'Invalid IPv6 packet on input: [chars] (got

[dec], should be [dec]), s: [chars] d:
[chars]'

IPV6 received an invalid format IP packet.

'Failed to decode [chars] data'

IPV6 could not decode data supplied by the

indicated external data manager.

'Failed to encode [chars] data in external

data manager'

A process has requested information from

ipv6_io through SysDB, probably as a result
of executing a show command. The data
requested could not be encoded.

'IPV6_IO failed to register its external data

manager - [chars]'

The ipv6_io process failed when attempting

to register its external data manager with
SysDB.

'[chars], (source: [chars], destination:

[chars])'

IPV6_IO discarded a packet due to the

indicated error.

'Could not write packet specific feature

IPv6_IO could not write the packet specific
vectors in [chars] ([chars], [unsigned int])' features.

While trying to create a shared memory

object for ipv6 traffic statistics,
'Failed to initialize shm for ipv6 traffic stats' encountered an error

[chars]%s

An software error occured when the

L2SNOOP process try to do debug related
initialization.

[chars]%s

An software error occurred while starting

up of L2SNOOP process. If this occurred
during process startup, then the process
may be restarted.

[chars] ([dec])

An software error occured when the

L2SNOOP process attempts to retry one of
its initialization tasks with a network layer.

[chars] ([chars]): [chars]

An software error occured when the

L2SNOOP process try to request more
memory. The requested operation by
l2snoop could not be accomplished
because of a low memory condition.

[chars] - [chars]

An software error occured when the

L2SNOOP process try to do redundancy
related init with System Manager for the
node state changes.

Failed to register L2SNOOP protocol with

the network layer ([chars]): [chars]

An software error occured when the

L2SNOOP process try to register itself with
the network process and net io process for
datapath.

[chars] ([chars]): [chars]

An software error occured when the

L2SNOOP process do socket related
initialization.

[chars]: [chars]

An software error occured when the

L2SNOOP process attempts to register with
Install Manager for notification of software
package installation and deinstallation on
the system.

[chars]: [chars]

An software error occured when the

L2SNOOP process sets up and initializes
the various L2SNOOP timers.

[chars]: [chars]

An software error occured when the

L2SNOOP process attempts to set up
connection with the RSI agent during the
startup of l2snoop process.

[chars] - [chars]

An software error occured when the

L2SNOOP process try to do initialization
related with sysdb process.

Failure ([chars]) reason - ([chars])

An error occurred during sysdb operation

between pim and sysdb.

Convergence item failure ([chars]) reason - An error occurred processing a BGP

([chars])
convergence item operation.

Helper address datalist operation failed,

[chars], [chars]

The sysdb process fails to find the address

of a specified active interface or of all
active interfaces.

ICMP error generation failure: Failed to

register with pakman for hssd use.

For generation of ICMP error packets, the

ICMP generation library needs to register
for an internal packet resource called
HSSD. Since, it couldn't register for that, an
ICMP error couldn't be generated.

Failed to read IP header in packet (hl =

%zd, read = [dec])

There was a problem reading the full IP

header for a packet being sent. The packet
would be dropped.

Failed to read IP header - [chars]: [chars]

There was a problem with reading the IP

header in the packet, so, can't process it.

Failed to get total packet header count

[chars]: [chars]

There was a problem while getting total

packet header count for this node.

PLIB_INIT failed [chars], [chars]

There was a problem initializing the IPv4

protocol library within a transport process.
The message indicates what part of the
initialization failed.

The transport fails to open the ipv6-io stats

Failed to open IO stats shared mem, [chars] shared memory

FSV registration failed for [chars], [chars]

This is a transient error and it happens

when the packet mamager process is
temporarily unavailable.

FSV resource busy, [chars]

The packet FSV resources are busy and a

packet FSV could not be written. It is a
transient error and it could happen in a
heavy loaded system.

Failed to get the MTU, [chars]

The transport fails to get the MTU from the

network protocol process.

IPSEC_HANDLE creation failed [chars],

[chars]

An error is encountered in handling an IP

Security packet

Failed IPv6 Local Address Server (LAS)

initialization, [chars]

This is a transient error and it happens

when the underlying communication layer,
Group Service Process (GSP), is temporarily
unavailable.

Failed to connect to netio, [chars]

The transport fails to open the connection

to netio. This error is normally transient
and it occurs when the netio process is
temporarity unavailable.

Network protocol process is not up

The transport detects that the network

protocol process is not running. The
problem is usually transient and is
recovered once the network process
becomes available.

Failed to allocate [dec] bytes of memory,

[chars]

One of the memory allocation routines such

as malloc() fails.

Failed to send a packet to the network

layer, [chars]

The transport fails to send a message with

packet to the network layer.

Local map request source address not

available for [chars]%s.

'No map request source address is

available, meaning ' 'the router cannot
send any map requests.'

Internal LISP error ([chars])[chars]\n

'LISP control plane code execution

encountered an unexpected condition.'

No route to local EID database prefix

[chars].

'There is no RIB route that covers or is a

more specific ' 'of the configured local EID
database prefix. This means ' 'that the ETR
will not be able to forward decapsulated '
'packets to their destination.'

Inconsistent LISP routing locator

configuration detected in the local EID
database for instance-ID [unsigned int]
[chars] address family.

'All the LISP local EID prefixes for an

address family ' 'must be configured with
the same set of routing locators. ' 'LISP
detected that there are routing locators
configured ' 'on some local EID prefixes and
not on other local EID ' 'prefixes of the
same address family.'

LISP [chars] RIB import warning[chars],

reached [unsigned int] routes (limit set to
[unsigned int]).

'The LISP route import limit specified

through the ' '<CmdBold>route-import
maximum-prefix <limit>' '<noCmdBold>
configuration has been reached.'

[chars] RLOC [chars] in EID database

configuration in record for [chars] from
[chars].

'While probing other xTRs in our own site

we received a map ' 'reply mapping record
listing a different set of locators ' 'than
those we have configured in database
commands.'

'The platform has indicated it does not

This platform does not support local [chars] support local RLOCs of this ' 'address
RLOCs, [chars] will be marked as down.
family.'

DDT resolver received two Map-Requests

from [chars] for different EID prefixes but
with the same nonce.

'An xTR issuing LISP Map-Requests includes

a nonce value ' 'in each request. The xTR
must use a different nonce value ' 'for each
Map-Request for a new EID prefix. The
identified ' 'xTR has sent us two MapRequests, each for a different EID ' 'prefix,
and they both carried the same nonce
value. ' 'When querying the DDT hierarchy,
duplicate nonce values ' 'prevent the DDT
resolver from associating received ' 'MapReferral messages with the correct request.
To protect ' 'against this problem the DDT
resolver has dropped the ' 'second of the
two received requests.'

The HMAC computation library in not

available so LISP cannot generate and
process Map-Register messages or perform
LISP security operations.
''

'Failed to allocate memory'

The Multicast Port Arbitrator consumer

library failed to allocate memory during
mpa/mhost group creation/duplication and
its record restoration, filling up their group
information.

Unable to download multicast joins to a

restarted csmr on node [chars] : [chars]

The Multicast Port Arbitrator was unable to

download one or more multicast joins to a
restarting instance of its consumer on the
specified node.

Failed to allocate memory

The Multicast Port Arbitrator failed to

allocate memory.

[chars]: failed to send group message to

node [hex]: [chars]

An internal error was detected when trying

to send a GSP message to the given node.

mutex failed: [chars]: [chars]

Failure of thread operations on the mutex

protecting the multicast group
memberships.

Radix operation [chars] failed for node

[chars]([hex])

An internal error occured while updating an

internal node database.

Failed to insert an entry in MPA multicast

database radix tree

A radix tree internal error occured while

inserting in MPA multicast database.

Unable to delete client node ([chars]) from An AVL tree internal erorr occurred while
AVL tree
deleting a client node.

Cannot initialize [chars]: [chars]

The indicated initialization of the MPA failed

and the process restarted.

Failed to initialize [chars], because of

[chars]

Initialization failed. Both the initialization

type and the error code are displayed. The
sysmgr process will restart the ipv4_aclmgr
if this condition happens.

Failure ([chars]) reason - ([chars])

An error occured while reading requests or

processing a write request from the pim
mldp consumer. The specific reason is
provided in the message displayed. This
message indicates that an error occurred in
the ENS or NRS communication channel
between the PIM and the MLDP process on
the consumer side.

Failure ([chars])

An error occurred while processing the

request on the pim mldp producer. The
producer received an unkown message
type or an unexpected request.

Ipv4 io stats init failed. rc: [chars]

An error occurred while trying to map to

the ipv4 io netio shared memory stats. The
error will provide the reason why stats init
failed.

Fatal Error: couldn't allocate chunk mem for couldn't allocate chunk memory for packet
packet queue
queue in pre-route process.

Fatal Error: Couldn't create [chars] for

[chars] interaction

A certain call to an event_conn_*() api

failed in pre-route manager.

An event api failure happened in pre-route

Fatal Error: [chars] for [chars], error = [dec] manager process.

Pre-route: [chars]

An internal error occurred in pre-route

manager process, exiting the process.

[chars], ([dec], [chars])

Pthread create failed in pre-route manager

process.

Timer api failure happened in pre-route

Fatal Error: [chars] for [chars], error = [dec] manager process.

Failed to initialize handler for netio

connection [chars] ([chars])

Failed to initialize handler for netio

connnection in pre-router manager
process.

[chars]%s

An software error occured when the RAW

process try to do debug related
initialization.

[chars]%s

An software error occurred while starting

up of RAW process. If this occurred during
process startup, then the process may be
restarted.

[chars] ([dec])

An software error occured when the RAW

process attempts to retry one of its
initialization tasks with a network layer.

[chars] ([chars]): [chars]

An software error occured when the RAW

process try to request more memory. The
requested operation by raw could not be
accomplished because of a low memory
condition.

Failed to register RAW protocol with the

network layer ([chars]): [chars]

An software error occured when the RAW

process try to register itself with the
network process and net io process for
datapath.

[chars]: [chars]

An software error occured when the RAW

process attempts to register with Install
Manager for notification of software
package installation and deinstallation on
the system.

[chars]: [chars]

An software error occured when the RAW

process sets up and initializes the various
RAW timers.

[chars]: [chars]

An software error occured when the RAW

process attempts to set up connection with
the RSI agent during the startup of raw
process.

[chars] ([chars]): [chars]

An software error occured when the RAW

process do socket related initialization.

[chars] - [chars]

An software error occured when the RAW

process try to do initialization related with
sysdb process.

[chars]: [chars]

rlogin client application's child process has

invalid pid

[chars]: the child stopped with signal

number [dec]

rlogin client application's child process was

stopped abnormally

[chars]: the child terminated with signal

number [dec]

rlogin client application's child process

terminated abnormally.

No route to destination host exists\r\n

Socket operation failed.

Couldn't create evmgr

Internal error.

tcflush failed

tcflush() call failed.

Can't fork child process

Internal error in forking child process.

socket: [chars]

Socket operation failed.

[chars]: [chars]

rlogin client's call to wait() system call

failed

[chars]

The rlogin encountered some problem in

genric nature or plain information.

Couldn't create evmgr in function [chars]() Internal error.

Failed to init debug in function [chars]()

Internal error.

Rlogind: fatal error [chars]

Fatal error.

Cannot allocate memory in function [chars] Internal error. System is out of memory ()
malloc failed.
Failed to open a device file for a session
([dec])

An unexpected error occurred when

RloginD tried to open a VTY character
special file.

Can't spawn login

Internal error in spawning login child

process.

Unexpected SysDB error encountered:

[hex], '[chars]'

The Telnet Server has encountered an error

using the SysDB Library.

Failed to retrieve the details of a TTY

Device ([hex], '[chars]')
usage : rlogind [-alnd]

An unexpected error occurred when

RloginD tried to retrieve the details of a
VTY from a utility library
Usage error.

Failed to obtain a VTY for a session:

'[chars]'

An error occurred when RloginD requested

a VTY for a session. This might occur if the
requested rlogin session cannot be
satisfied by any of the unused VTYs in the
configured vty pool(s), e.g. if all VTYs are in
use, if transport-input is not allowed for
rlogin, or if the configured ACL does not
match.

Socket operation failed: [chars]

Internal warnings related to socket

operations.

Rlogind: [chars]

The rlogind encountered some problem in

genric nature or plain information.

Illegal port: [chars]

The connection between rsh client and

server must from/to a privileged port (5121023)

Kerberos rsh denied to [chars].

[chars]@[chars]

Kerberos authentication failed.

Failed to create event manager: [chars]

Attempt to create an event manager fails

for some reason

Failed to allocate [dec] bytes of memory:

[chars]

The server has failed to acquire the

required amount of memory

Failed to register for debugging events:

[chars]

Attempt to register with the event magager

for debugging events fails

Socket operation failed: [chars]: [chars]

[chars]

Internal warnings related to socket

operations
Usage error.

[chars]%s, restarting to recover

An error occurred while starting up SCTP

process. SCTP process will restart in an
attempt to recover

'Cannot initialize [chars]: ([chars])'

An error was detected during initialization

of the IPv4 Single Management IP Address
Process (SMIAP). This indicates an internal
software error. The SMIAP process will be
terminated.

A call to checkpoint function failed for the

'the check point function [chars] rc: [chars]' virtual ip address of that vrf

'IP address [chars] configured on

management interface [chars] same as' '
virtual IP address [chars]'

IP address on the management interface

specified is conflicting with the virtual IP
address.

'Interface '[chars]' is supposed to be a

management interface, but, cannot' ' find
information about it'

Management interface information needs

to be known in SMIAP so that it can make
the virtual IP address functional.

'IP address [chars]/[dec] on the

management interface [chars] does not
belong to same' ' network as virtual IP
address [chars]/[dec]'

IP address on the management interface

on the active/standby RP should be in the
same network as the virtual IP address.

'Failed to signal sysmgr about - [chars],

error [chars]'

SMIAP failed to signal sysmgr about its

process state.

'Virtual IP address [chars] same as [chars]

configured on management interface
[chars]'

IP address on the management interface

specified is conflicting with the virtual IP
address.

ASYNC socket ([chars]) aborted due to an

error ([chars])

The socket library aborted a socket

because of system instability.

The socket library has noticed an attempt

to close an ASYNC listen socket in error.
This could place the system in an
An ASYNC listen socket was quite possibly inconsistent state. The message may be
closed in error. App PID [unsigned int], PCB ignored, if it was seen when a TCP
0x[pointer], so 0x[pointer], state [hex]/
application crashed or was either restarted
[hex]
or shut.

The socket library couldn't deliver a pulse

as part of its processing. This can place the
process in an inconsistent state. The
problem manifests, typically, during low
Error is delivering ASYNC I/O [chars] pulse. memory conditions, so it is important to
Reason: [chars], Socket: FD [dec], session- check for any widespread issues in either
ID [unsigned int]
the system or the process state.

Sequence number mismatch for [chars]; fd

[dec], sess [dec]/0x[pointer], expected
seqno [unsigned int], data seqno [unsigned
int]

The socket library has encountered an error

while operating on ASYNC sockets. This
could place the system in an inconsistent
state.

The socket library has encountered an error

while allocating shmwin for ASYNC sockets.
Transport has run out of shmwin for ASYNC This indicates that more than the
sockets, App JID [unsigned int], PID
supported number of applications is trying
[unsigned int]
to use ASYNC sockets.

ASYNC sockets aborted due to an error

condition. App PID [unsigned int], state
[hex].

The socket library aborted sockets

belonging to the application due to system
instability.

The socket library has disallowed creation

of a new socket. The system is likely
undergoing churn or is throttled, so that
ASYNC socket(s) couldn't be created
new sockets are no longer being allowed.
because of prevailing conditions on the
Once the system gets back to stability,
router. App PID [unsigned int], state [hex]. socket creation will be allowed.

Close was called on the socket 0x[pointer]

([chars], owned by proc [dec]) more than
The socket library expect close to be called
once
only once by os.

Socket XIPC : [chars]

The socket library has taken corrective

measures or noticed a non-critical issue
with the XIPC queue operations.

The socket library encountered a throttle

condition, when operating on an XIPC
queue. This might place the socket
connection in an inconsistent state. The
condition may be temporary, but if it
XIPC queue throttle : [chars] [chars] queue persists, please collect the necessary
(0x[pointer]) [chars]; [chars]
information.

Failed to initialize debug event: [chars]

The socket library (used by transports)

failed to initialize a debug event.

Failed to register with the debug library to

have the library automatically handle
Failed to register with debug library: [chars] changes to any of the SOCKET debug flags.

Failed to create event manager: [chars]

The socket library failed to create event

manager.

NOFDREF flag on socket 0x[pointer]

([chars], owned by proc [dec]) is already
set where we expect it is not set

The socket library expect the NOFDREF flag

to be not set and find it is already set.

[chars]: Failed to generate [chars]: [chars]

HSRP has failed to notify the system that

the specified event has occurred.

Failed to get [chars] type from Interface

Manager: [chars]

HSRP has failed to retrieve required

information about the interface from the
Interface Manager.

Failed to [chars] interface [chars] on

Multicast group: [chars]

The HSRP process failed to start/stop

receiving HSRP packets on an interface
correctly. This is an internal error.

Failed to add unicast MAC address on

interface [chars]: [chars]

HSRP has failed to assign a MAC address to

the interface.

More than the maximum supported

number of MAC address filters has been
installed for this interface meaning traffic
to some virtual IP addresses will be
Maximum MAC address filters for interface dropped. Note that for sub-interfaces the
[chars] exceeded
limit is per parent interface.

Out of memory (failed attempt to reserve

[unsigned int] bytes)

HSRP was not able to allocate the memory

that it needed to complete the operation.
HSRP functionality may be reduced until
the problem is resolved.

Registration for [chars] failed: [chars]

Registration for an IOSXR service failed

during HSRP's operation. This may indicate
a connection failure with the IOSXR service
as indicated in the error message.

Bad authentication from [chars], group

[unsigned int], remote state [chars]

The peer HSRP router has mismatching

authentication settings. The authentication
string in the HSRP packet did not match the
locally configured value. Consequently this
peer is ignored.

The peer HSRP router has mismatching

virtual IP address settings. The virtual IP
address in the HSRP packet did not match
the locally configured value. Consequently
this peer is ignored. This may result in
duplicate traffic forwarding due to the
Mismatching virtual IP address of [chars], presence of 2 Active devices with the same
from group [unsigned int]. Local address is virtual MAC addresses but different virtual
[chars].
IP addresses.

Outputting debug information failed:

[chars]

The HSRP process failed to output a debug

message. This may not impact functionality
but it does impair the debuggabilty of the
VRRP process. And may indicate that there
is a failure with the IOSXR debug
infrastructure.

HSRP Initialization failed: [chars]: [chars]

The HSRP process failed to initialize

correctly. In this situation HSRP restarts,
but HSRP may not recover if there is a
persistant error in the IOSXR system and
HSRP is later unable to reestablish its
connections and initialize successfully.

HSRP control packet received from [chars]

on MGO slave group: [chars] group
[unsigned int]

The peer HSRP router has mismatching

configuration. The group which is
configured as a slave on the router on
which this message is seen is configured as
a standard non-slave HSRP group on the
peer.

Holdtime ([dec]) is less than or equal to

twice the hellotime ([dec])

The holdtime has been set to a value which

is less than (or equal to) twice the hello
time. This is not recommended as any lost
packet may result in an unnecessary state
change.

Disabling HSRP filtered ICMP redirects

when ICMP redirects are enabled may
cause hosts to use real IP addresses as
ICMP redirects may still be enabled on this their default routes, and first hop
interface
redundancy may be lost.

ICMP redirects may be ignored by hosts if

HSRP secondary addresses are used

If a host uses HSRP secondary addresses,

HSRP filtered ICMP redirects may be
ignored by the host (depending on the host
implementation).

SB[dec]: [chars]: state [chars]\011 ->

[chars]

The HSRP router has changed state for the

specified group and interface.

TCP in active role has failed. Initiating failover to keep NSR up.

TCP's NSR module is initiating a fail-over to

maintain NSR because TCP in active role
has failed (either crashed or shut down)
and fail-over is currently configured as the
recovery action.

Not all NSR clients in NSR Ready State,

hence fail-over will not be requested.

TCP's NSR module is trying to initiate a failover to maintain NSR, but either all NSR
clients are not yet ready or NSR clients with
the highest weight are not yet ready. So, a
failover will not be attempted.

During sso functionality init [chars]%s

An software error occurred while initializing

the TCP SSO functionality. If this occurred
during process startup, then the process
may be restarted.

One or more NSR control messages could

not be delivered to partner TCP.

One or more control messages could not be

delivered, after several retries, to the
partner TCP stack. This can leave the TCP
stacks in a state that prevents NSR from
being restored. However, periodic self-audit
should correct the mismatch in state and
should result in NSR being restored.

[chars]:[dec] <-> [chars]:[dec]:: NSR

disabled for TCP connection because
[chars]

TCP stack detected NSR functionality

impairment and has disabled NSR for the
connection.

Bring NSR down for sessions protected on

node [chars]

NSR is brought down for sessions protected

on partner node because of missing
keepalives

The peer is sending an authentication

Invalid [chars] digest from [chars]:[dec] to digest that doesn't match what is
[chars]:[dec]
configured locally.

Aborting connection [chars]:[dec] <->

[chars]:[dec] because [chars]

The TCP connection was aborted due to an

internal error.

During debug init [chars]%s

An software error occured when the TCP

process try to do debug related
initialization.

Send key-id [dec] for keychain '[chars]'

(peer [chars]) greater than Enhanced
Authentication max(63)

TCP Enhanced Authentication header has 6

bits for the keyid, hence, the send key
can't be more than 63.

Received unsupported MAC

algorithm([dec]) in the Enhanced
Authentication option from peer [chars]

Received a TCP packet with the Enhanced

Authentication option header with a
MAC(Message Authentication Code)
algorithm value not supported, from the
specified peer.

Invalid or no-active send-key for key-chain

'[chars]' for the Enhanced Authentication
option to send to peer [chars], error [chars]

Either there is no active send-key for the

specified keychain or the active send-key
has some problem. Hence can't send data
to the peer.

No active send-key for key-chain '[chars]'

for the Enhanced Authentication option to
send to peer [chars], error - [chars]

There is no active send-key for the

specified keychain and hence can't send
data to the peer.

The send-key from the specified keychain

has a MAC(Message Authentication Code)
Unsupported MAC algorithm([dec]) for
algorithm which is not supported by the
keychain '[chars]' (send-key [dec]) for peer TCP Enhanced Authentication (EA) draft
[chars]
and/or the IOS-XR implementation.

During IM init [chars]: [chars]

An software error occured when the TCP

process try to do initialization with ifmgr

During init [chars]:[chars]

An software error occurred while starting

up of TCP process. If this occurred during
process startup, then the process may be
restarted.

The local application did not program the

authentication information (MD5 or key
chain) for the peer with which it is trying to
connect. It is likely that the application
programmed the information for a different
Authentication info not programmed for the peer on the socket opened for connection
peer [chars].
to the specified peer.

An software error occured when the TCP

process try to request more memory. The
requested operation by tcp could not be
While registering as a resource mgr [chars] accomplished because of a low memory
([chars]): [chars]
condition.

During timer init [chars]: [chars]

An software error occured when the TCP

process sets up and initializes the various
TCP timers.

An software error occured when the TCP

During socket init [chars] ([chars]): [chars] process do socket related initialization.

During sysdb init [chars] - [chars]

An software error occured when the TCP

process try to do initialization related with
sysdb process.

Unexpected SysDB error encountered:

[hex], '[chars]'

The Telnet client has encountered an error

using the SysDB Library.

Error imc_control_server_bind: [chars]

([dec]:[chars]). Cannot continue.

An error occured while trying to bind to IM

server.

Invalid adress family: [dec]

'The api has returned invalid address

family'

Error converting the port number to

numerical representation: [chars]

'The port specified on the command line

can not be converted'

Unable to bind to the RIB

An error occurred while attempting to bind

to the RIB.

Error retrieving source address from RIB:

[chars]. Cannot continue.

An error occured while trying to retrieve

the IP address of the source interface from
the RIB.

[chars]: [chars]

'Unable to get/read an item from sysDB '

Error in [chars]. errno [dec]: [chars]

'There was an error during invocation of a

system call'

Error communicating with the network:

[chars] Exiting.

An error occurred whilst trying to set an

option on the TCP socket used for this
connection.

[chars]: [chars]

'The call to tty_details_from_device_file()

failed '

[chars]: [chars]

'Unable to get the sysDB path of an item

from TTY nmspc library'

An error occurred whilst trying to extract

Couldn't extract dscp setting([chars]([dec]: dscp configured value. Client will use
[chars])).
default dscp value instead.
Couldn't set dscp setting([chars]([dec]:
[chars])).

An error occured while trying to set dscp

value to socket. Telnet will start without
spefified dscp value.

Setsockpt operation failed '[chars]'.

An error occurred whilst trying to
Operation ([dec]:[dec]:[dec]:[dec]). Please setsockopt on the socket. Session will be
retry.
closed.
Error: [chars]

'The call to ip_addr_c_get_v4/v6_best()

failed'

Couldn't bind [chars]([chars]).

An error occurred whilst trying to bind the

local address.

Couldn't connect to remote host [chars]

([chars]).

An error occurred whilst trying to

connecting to the remote host.

Specified source interface is down

'The source interface is down, therefore it

can not be used.'

Couldn't get interface handle for [chars],

[chars]

'Interface lookup failed for source-interface'

Source interface has an invalid address

'The call to ip_addr_c_get_v4/v6_best()

returned an invalid address'

The specified source interface is invalid

Error: [chars]

'The specified source interface can not be

used. Will use default interface'
'The call to ip_addr_c_init() failed'

An error occurred whilst trying to

Setsockpt operation failed '[chars]'.
setsockopt on the socket. Session will
Operation ([dec]:[dec]:[dec]). Please retry. continue.

An error occurred whilst trying to

Setsockpt operation failed '[chars]'.
setsockopt on the socket. Session will
Operation ([dec]:[dec]:[dec]). Please retry. continue.

Setsockpt operation failed '[chars]'.

Operation ([dec]:[dec]:[dec][[pointer]]).
Please retry.

An error occurred whilst trying to

setsockopt on the socket. Session will
continue.

An error occurred whilst trying to

Setsockpt operation failed '[chars]'.
setsockopt on the socket. Session will
Operation ([dec]:[dec]:[dec]). Please retry. continue.

An error occurred whilst trying to

Setsockpt operation failed '[chars]'.
setsockopt on the socket. Session will
Operation ([dec]:[dec]:[dec]). Please retry. continue.

Couldn't open socket for [chars] vrfid:[dec] An error occurred whilst trying to open tcp
([chars]).
socket.

Failed to set TCP_NODELAY on this

session([dec]). Telnet session might get
slower performance.

Nagle's algorithm was not disabled; there is

a small chance the telnet session will
appear jerky. Telnet will otherwise function
normally.

Failed to set SO_OOBINLINE on this

session([dec]).

Telnet client failed to set SO_OOBINLINE

flag on the tcp socket. We can't continue
telnet session, so exit process. Retry would
help opening session.

[chars]: [chars] errno=[dec] [chars]

There was a critical system call failure

resulting in a failure to provide some
system service.

The source or destination address [chars] is The telnetd server was passed a bad
invalid
adress.

The telnet connection from [chars] has

been Timed out

A telnet session from the specified peer

has been timed out because no response
was received from the remote end for the
terminal-type query.

The address family [dec] is invalid

The telnetd server was passed a bad

adress family.

Bad port number

The telnetd server was passed a bad port

number.

Failed to obtain a VTY for a session:

'[chars]'

An error occurred when TelnetD requested

a VTY for a session. This might occur if the
requested telnet session cannot be
satisfied by any of the unused VTYs in the
configured vty pool(s), e.g. if all VTYs are in
use, if transport-input is not allowed for
telnet, or if the configured ACL does not
match.

Couldn't create evmgr in function [chars]() Internal error.

Failed to init debug in function [chars]()

Internal error.

Function cleanup() has been called due to

an error

The Telnet Server has encountered an

unexpected error while using the system
library.

[chars]: The call to [chars] failed. Error:

[dec], '[chars]'

The Telnet Server has encountered an

unexpected error while using the system
library.

Failed to allocate %zd bytes of memory

The server has failed to acquire the

required amount of memory

Failed to open a device file for a session

([dec])

An unexpected error occurred when

TelnetD tried to open a VTY character
special file.

telnetd: panic state = [dec]

Panic error.

Unexpected SysDB error encountered:

[hex], '[chars]'

The Telnet Server has encountered an error

using the SysDB Library.

Failed to retrieve the details of a TTY

Device ([hex], '[chars]')

An unexpected error occurred when

TelnetD tried to retrieve the details of a VTY
from a utility library

usage : telnetd -debug <portNo>

-no_tty_server

Usage error.

Error: [chars]

The invocation of a system call returned

error condition.

Error communicating with the network:

[chars] Exiting.

An error occurred whilst trying to set an

option on the TCP socket used for this
connection.

[chars]: Warning - configuration

inconsistencies

The configuration inconsistencies is

detected for the indicated configuration.

An error occurred whilst trying to extract

Couldn't extract dscp setting([chars]([dec]: dscp configured value. Server will use
[chars])).
default dscp value instead.

The TCP keepalive timeout was not set

Failed to set the TCP keepalive timeout
during initialisation. The default value of 2
during socket initialisation: [chars]; default hours will apply. Telnet will otherwise
will apply
function normally.

Failed to disable Nagle's algorithm during

TCP socket initialisation: [chars];

Nagle's algorithm was not disabled; there is

a small chance the telnet session will
appear jerky. Telnet will otherwise function
normally.

event manager create failed\n

In a telnetd session, creation of event

manager failed . Internal error.

tty_map_stat_init failed rc [dec]\n

Initialization of stat file in telnetd session

failed , It is created only for statistics
purpose.

register with sysmgr failed \n

Registering with sysmgr failed while

getting tty details. Internal error.

thread create failed \n

In a telnetd session. The vty thread

creation failed .Internal error.

An error occurred whilst trying to extract

Couldn't extract dscp setting([chars]([dec]: dscp configured value. Server will use
[chars])).
default dscp value instead.
Couldn't set dscp value([dec])([chars]
([dec]:[chars])).

An error occured while trying to set dscp

value to socket. Process will use default
dscp value instead.

An error occurred while trying to verify

dscp configuration. This failure can occur
due to any of the following reasons. 1.
when Item name not specified. (item name
will be like <vrfname>/<proto_name>/dscp) 2. If the size
of the buffer used to store the Item name is
Couldn't verify dscp setting([chars][[chars]] less than the required 3. Fail to open the
([dec]:[chars])([dec]:[dec])).
file pointed by the Item name.

[chars]

This message indicates that write to tftp

was not completed successfully.

this message indicates that the specified

application did not write any data to the
No data was written for [dec] seconds by
tftp destination for a long time. This can
the application with PID [dec] - the file
cause the remote server to abort the
transfer may abort or the file transfer may transfer thereby resulting in a partially
be incomplete.
transferred file.

tts init [chars]

A software error occurred while starting up

the TTS process. TTS will not be restarted
by sysmgr.

Error occurred during [chars] on fd [dec]

A software error occurred during I/O an
([dec]<->[dec]), bytes [dec], errno [chars] operation.

tts wrong command [chars]

A software error occurred while exeucting a

TTS command.

tts event [chars]

An informational message about an event

that occurred.

[chars]%s

An software error occured when the UDP

process try to do debug related
initialization.

[chars]%s

An software error occurred while starting

up of UDP process. If this occurred during
process startup, then the process may be
restarted.

[chars] ([dec])

An software error occured when the UDP

process attempts to retry one of its
initialization tasks with a network layer.

[chars] ([chars]): [chars]

An software error occured when the UDP

process try to request more memory. The
requested operation by udp could not be
accomplished because of a low memory
condition.

[chars]: [chars]

An software error occured when the UDP

process sets up and initializes the various
UDP timers.

[chars]: [chars]

An software error occured when the UDP

process attempts to set up connection with
the RSI agent during the startup of udp
process.

[chars] ([chars]): [chars]

An software error occured when the UDP

process do socket related initialization.

[chars] - [chars]

An software error occured when the UDP

process try to do initialization related with
sysdb process.

Failed to obtain snmp index for [chars]:

[chars]

The VRRP process failed to obtain the snmp

index for this interface. There may be a
problem with the connection to certain
IOSXR services.

More than the maximum supported

number of MAC address filters has been
installed for this interface meaning traffic
to some virtual router IP addresses will be
Maximum MAC address filters for interface dropped. Note that for sub-interfaces the
[chars] exceeded
limit is per parent interface.

Out of [chars] memory (failed attempt to

reserve [unsigned int] bytes)

The VRRP process was not able to allocate

the memory that it needed to complete the
operation. VRRP functionality may be
reduced until the problem is resolved.

Bad authentication from [chars], vrid

[unsigned int]

The peer VRRP router has mismatching

authentication settings. The authentication
string in the VRRP packet did not match the
locally configured value. Consequently this
peer is ignored.

[chars] vrid [dec]: packet source [chars],

configured [chars]

The VRRP virtual router has received a

packet for which the packet source does
not match the IP address that the BFD
session associated with this virtual router is
monitoring. The BFD remote IP is statically
configured therefore this error is due to a
misconfiguration in which the true remote
IP of the peer vrouter does not match the
configured remote IP.

Outputting debug information failed:

[chars]

The VRRP process failed to output a debug

message. This may not impact functionality
but it does impair the debuggabilty of the
VRRP process. And may indicate that there
is a failure with the IOSXR debug
infrastructure.

VRRP Initialization failed: [chars]: [chars]

The VRRP process failed to initialize

correctly. In this situation VRRP restarts,
but VRRP may not recover if there is a
persistant error in the IOSXR system and
VRRP is later unable to reestablish its
connections and initialize successfully.

Registration for [chars] failed: [chars]

Registration for an IOSXR service failed

during VRRP's operation. This may indicate
a connection failure with the IOSXR service
as indicated in the error message.

VRRP shared memory reset on version

mismatch failed: [chars]

There was a version mismatch in the VRRP

shared memory and in handling this, the
resetting of the shared memory failed. This
may result in a memory leak.

VRRP control packet received from [chars]

on MGO slave: [chars] VRID [unsigned int]

The peer VRRP router has mismatching

configuration. The group which is
configured as a slave on the router on
which this message is seen may be
configured as a standard non-slave VRRP
virtual router on the peer.

[chars] vrid [dec] address family [chars]:

state [chars]\011 -> [chars]

The VRRP router has changed state.

ERR: [chars]: cerrno [dec]

Eagle driver might run into an error that is

not a FATAL.

Physical layer interface module hardware

restart for error recovery failed: [chars]:
[chars]

The PLIM driver failed in soft error recovery.

When a soft error is detected with any ASIC
on the datapath, the Fault Manager will
start the soft error recovery on the whole
datapath. If the PLIM soft error recovery
failed, the PLIM hardware state may not be
in the correct state, and the traffic may be
affected. %s - indicates the reason for the
failure %s - is the decoded error reason

Physical layer interface module driver

initialization failed: ([chars]/[chars]).

The physical layer interface module (PLIM)

driver on the linecard failed to initialize.
The PLIM driver creates the SONET
controller and POS interface, handling the
all the SONET event, applying SONET/POS
configuration to the layer-1 device
hardware. If the PLIM driver fails to
initialize, no traffic will pass, therefore no
higher level protocol will work. %s indicates the reason for the failure %s - is
the decoded error reason

The wrong timer type is detected while

handling the timer event, the timer will be
stopped. The POS interface counter will not
Unknown timer type detected, the timer is work if the timer is stopped, but the traffic
stopped.
will not be affected.

Debug initialization failed with [chars].

Debug message initialzation failed.

Port [chars] reports [chars] [chars]([chars])

PM TCA with current value [unsigned long
long int], threshold [unsigned long long int]
in current [chars] interval window
The specified PM TCA has been declared.

msg: [dec], retried: [dec] time(s), failed to

send, errno: [chars]

This error message indicates a s/w

problem. The details of the problem and
traceback are appended to the error msg.
Contact support with this information.

[chars]

A harmless s/w problem occurred. The

details of the problem and traceback are
appended to the error message.

fatal error encountered by h/w - [chars],

[chars]

An unrecoverable fatal error was detected

by the service linecard h/w, which resulted
in linecard reload. The exact cause is
appended to the error message. Contact
support with this information.

fatal s/w error encountered - [chars],

[chars]

An unrecoverable fatal s/w error was

encountered, which resulted in process
restart. The exact cause is appended to the
error msg. Contact support with this
information.

board PLL error : IOFPGA register

PLL_STATUS - [hex][[hex]]

There is unexpected h/w state

A nonfatal error was detected by the

service linecard h/w. The exact cause is
nonfatal error encountered by h/w - [chars], appended to the error message. Contact
[chars]
support with this text.

[chars] i/f PLL is unlock : register PLS [hex]

There is unexpected h/w state

[chars]

Unexpected event occurred in the service

linecard with no effect on functionality

[chars]

Service linecard's driver informational

message

ERR: [chars]: cerrno [dec]

ut2 driver might run into an error that is

not a FATAL.

fatal error encountered by h/w - [chars]

An unrecoverable fatal error was detected

by service card h/w, which resulted in
linecard reload. The exact cause is
appended to the error msg. Contact
support with this information.

fatal s/w error encountered - [chars],

[chars]

An unrecoverable fatal s/w error was

encountered, which resulted in process
restart. The exact cause is appended to the
error msg. Contact support with this
information.

Daughter board identified by above nodeid

is not supported by Cisco 12000 Series Inserted node [chars] is not supported by Multi-Service Blade Controller. The
Cisco 12000 Series - Multi-Service Blade
Daughter board should be removed
Controller. Results are unpredictable.
immediately because results are
Please remove the unsupported hardware. unpredictable.

[chars]

Unexpected event occurred in service

linecard with no effect on functionality

Interface [chars], Detected RX Fault

The PLIM received an Rx fault on the given

interface which will result in a link flap.

Interface [chars], Detected PLA Fault

The PLIM PLA ASIC had an unkown fault on

the given interface which will result in a
link flap.

PLIM Process Error: [chars]

The PLIM process failed to spawn correctly.

This PLIM is no longer supported

This PLIM is a prototype and is not longer

supported

An XGXS RX lane failed to synchronize for

port [dec].

The XGXS Rx Lanes failed to synchronize

after a Xenpak OIR or Link Flap.

An XGXS TX lane failed to synchronize for

port [dec].

The XGXS Tx Lanes failed to synchronize

after a Xenpak OIR or Link Flap.

Port [dec], XFP unable to reach ready state, The XFP inserted encountered a fault
powering off
condition when powering on.

An Optic Interface Module error occurred at A fatal error occurred in 10GE PLIM driver
port [dec], reason : [chars]
OIM rule validation.

Failed to get MAC address for Slot [dec],

Port [dec], Interface assigned random MAC PLIM driver was unable to get a MAC
address.
address for the interface.

Interface [chars], Detected RX Loss of

Signal

The PLIM received an Rx LOS or LF on the

given interface which will result in a link
flap.

Interface [chars], [chars]

The PLIM received a remote fault on the

given interface which will result in a link
flap.

[chars]

This is a Informational message in the

plim_8p_10ge driver to indicate an
operation.

Optic Interface Module [chars] for port

[dec]

The Optic Interface Module (OIM) for the

specified port has either been inserted or
removed.

Port [dec], Unsupported Xenpak inserted

The Xenpak inserted in the given interface

is not supported on this PLIM.

Port [dec], Unsupported XFP inserted

The XFP inserted in the given interface is

not supported on this PLIM.

Port [dec], Retrying XFP EEPROM read :

(retry_count [dec])

The Reading of XFP EEPROM failed; Retry is

attempted

Address of acct_svr_config_g moved after

restart. acct_svr_config_g->base_address:
[hex], acct_svr_config_g: [hex]

After restart of Accounting server the

memory occupied by account server
configuration is not same.

init error: [chars] - restarting process to

recover.

The process acct_svr encountered a

software error while initializing. The
process is exiting and will be restarted.
System will not be affected.

software internal error: [chars] - restarting

process to recover.

The process acct_svr encountered an

internal error. The process is exiting and
will be restarted. System will not be
affected.

init error: [chars] - restarting process to

recover.

The process acct_svr encountered a

software error while initializing. The
process is exiting and will be restarted.
System will not be affected.

software internal error: [chars] - restarting

process to recover.

The process acct_svr encountered an

internal error. The process is exiting and
will be restarted. System will not be
affected.

Failed to initialize the shared memory for

[chars]: shmwin_init() failed shmwinid [dec] NH.

hal_shm_alloc: shmwin_malloc() failed

shmwinid [dec]

Failed to allocate the shared memory for

NH.

[chars]: shmwin_pool_create_v2() failed,

return: cerr: [dec]

Failed to create the memory pool for

shared memory.

The process acct_svr has failed to get the

HFA clock delta for the given consecutive
times. The flow report uses the forwarding
asic clock which may be slightly off from
the system clock. To correct the timestamp,
the HFA clock delta is retrieve and on
failure, the previously recorded delta is
used. This log is printed out after so many
consecutive failures to retrieve the clock
HFA get clock delta has failed consecutively delta, which may lead to skewed
[dec] out of [dec] total times.
timestamps in the flow report.

The process acct_svr has failed to get the

HFA clock delta for the given consecutive
times.This log is printed out after so many
consecutive failures to retrieve the clock
HFA get clock delta has failed consecutively delta, which may lead to skewed
[dec] out of [dec] total times.
timestamps in the flow report.

ISR FIFO ring buffer usage is [chars]

threshold ([dec]). direction: [dec]
num_items = [dec]

The process acct_svr detected the

condition of ISR FIFO ring buffer usage
above or below the threshold. If the usage
is above the threshold, the process
acct_svr will bring the ISR FIFO ring buffer
usage back to below the threshold after a
while. Traffic will not be affected by this
condition.

ISR FIFO ring buffer usage is [chars]

threshold ([dec]). direction: [dec]
num_items = [dec]

The process acct_svr detected the

condition of ISR FIFO ring buffer usage
above or below the threshold. If the usage
is above the threshold, the process
acct_svr will bring the ISR FIFO ring buffer
usage back to below the threshold after a
while. Traffic will not be affected by this
condition.

\n [chars], rc = [hex], [chars]

This is a error message in the HFA Alpha

driver to indicate tcam carving error.

Memory access error: [chars]: Err=[chars]

A memory access error occurred in

programable switching engine (PSE) driver
which involves exiting the process. %s indicates the reason for the failure. %s - is
the decoded error reason.

\n[chars] [chars]: [hex] [hex]

This is a error message in the HFA Alpha

driver to indicate either anomolies which
are not service impacting. Some of the
messages may indicate a failure to allocate
resources needed by applications. This
error may occur during the error recovery
mechanism for programmable switching
engine (PSE) while HFA Alpha driver fixes
the parity errors in the memories after
restart of the PSE.

Alpha SDRAM assertion failed: Address:

[hex]

The read/write address is not within the

range which causes the assertion.

Previous Count: [unsigned int], current

Count: [unsigned int].

This is an informational message when the

thread 20 count is incrementing. If it is
seen continuously, it indicates hardware
issue. Or else, it is safe to ignore. %u indicates previous thread 20 count. %u indicates current thread 20 count.

Ipmc disable: Rx: Prev [unsigned int],curr

[unsigned int]::Tx Ipv4: Prev [unsigned
int],curr [unsigned int]::Tx IPv6: Prev
[unsigned int],curr [unsigned int]

This is an informational message when the

Multicast is disabled on Rx or Tx engine
and all the multicast packets are dropped
due to this. Prev - Previous thread count.
Curr - Current thread count. Check the
values of the registers by using the
following commands on the engine:
Rx:show_alpha -S rx -u
prep,regmem=proto_config Tx:show_alpha
-S tx -u prep,regmem=proto_config
(Note:above commands to be executed
carefully.Execute as it is as shown
above.Do not give Contr + C during
execution.It causes a PSE reload.) Sample
output: ksh-LC>show_alpha -S rx -u
prep,regmem=proto_config
proto_config@0xa1: 3 (0x3) Interpretation:
Proto_config: 3 (both ipv4 and ipv6 mcasts
are enabled) Proto_config: 2 (Only Ipv4
mcast is disabled) Proto_config: 1 (Only
Ipv6 mcast is disabled) Proto_config: 0
(both Ipv4 and Ipv6 mcasts are disabled)
The log messages will be printed every 1
minute in case the thread counter
increments. To Enable or Disable the
message logging by using the following
command on the LC: Enable: show_alpha -k
on Disable: show_alpha -k off Show:
show_alpha -k show

7 Tuple L4 LBA not supported on E3, will

continue to load balance using L3 LBA

This is a informational message in the

programable switching Engine driver to
indicate that Alpha doesn't support 7 tuple
and hence will continue forwarding with L3
LBA.

[chars] [chars] error [hex]

This is an informational message in the

programable switching Engine driver to
indicatng unsupported version of
programmable Switching engine (PSE) for
some features. %s - is the warning
message. %s - is the decoded warning
reason. %x - is the decoded error code.

[chars] [chars]

This is an informational message in the

programable switching Engine driver to
indicate an operation. %s - indicates the
direction of the PSE. %s - is the decoded
informational reason.

This is a debug message to display PHB

dump of programable switching engine
(PSE).

\n[hex]: [hex] [hex] [hex] [hex]

[hex] plu_int_reg [hex]\n plu_int_en_reg
[hex] plu_err_en_reg [hex]
plu_ecc_error_reg [hex]\n
plu_ecc_syndrome_reg [hex] tlu_int_reg
[hex] tlu_sdram_adr_err_reg [hex]\n
tlu_sdram_ecc_syndrome_reg [hex]
mip_int_status_reg [hex] mip_pc_reg
[hex]\n pc2_status_reg [hex] pst_status_reg
[hex] cam_status_reg [hex]\n nf_stat_reg
[hex] pop_int_status_reg [hex] pop_pc_reg
[hex]\n ssram_adr_err_reg [hex]
ssram_err_data_reg [hex]
pl_pipeline_ctl_reg [hex]\n
pl_aa_pak_avl_1_reg [hex] pl_aa_end_reg
[hex] pl_aa_fatal_err_reg [hex]\n
gather_int_stat_reg [hex]
xbm_read_status_reg [hex]
xbm_rcl_w_status_1_reg [hex]\n
xbm_rcl_w_status_2_reg [hex]
xbm_rcl_r_status_reg [hex]
xbm_tail_w_status_1_reg [hex]\n
xbm_tail_w_status_2_reg [hex]
xbm_tail_w_status_reg [hex]
xbm_control_status_1_reg [hex]\n
xbm_control_status_2_reg [hex] fs_pcr_reg
[hex] prep_pair_reg[0] [hex]\n plu_pcr_reg
[hex] pc1_pcr_reg [hex] tlu_pcr_reg [hex]\n
dummy_pcr_reg [hex] mip_pair_reg[0]
[hex] pc2_pcr_reg [hex]\n
cam_match_pcr_reg [hex] pst_pcr_reg [hex] This is a debug message to display
pop_pair_reg[0] [hex]
registers of programable switching engine
gather_pcr_reg[hex]\n
(PSE).
ASIC Error library has failed to create an
Event Connection Manager. Reason:
[chars].

The ASIC Error library encountered an error

during the creation of the Error Connection
Manager.

ASIC Error library has failed to create an

Event Connection Manager. Reason:
[chars].

The ASIC Error library encountered an error

during the creation of the Error Connection
Manager.

ASIC Error library has failed to create an

Event Connection Manager. Reason:
[chars].

The ASIC Error library encountered an error

during the creation of the Error Connection
Manager.

ASIC Error library has failed to create an

Event Connection Manager. Reason:
[chars].

The ASIC Error library encountered an error

during the creation of the Error Connection
Manager.

ASIC Error library has failed to register a

connection notification handler with the
Event Connection Manager. Reason:
[chars].

ASIC Error library encountered an error

while setting up a SYSDB notofication
handler with the event connection
manager.

ASIC Error library has failed to register a

connection notification handler with the
Event Connection Manager. Reason:
[chars].

ASIC Error library encountered an error

while setting up a SYSDB notofication
handler with the event connection
manager.

ASIC Error library has failed to register a

connection notification handler with the
Event Connection Manager. Reason:
[chars].

ASIC Error library encountered an error

while setting up a SYSDB notofication
handler with the event connection
manager.

ASIC Error library has failed to register a

connection notification handler with the
Event Connection Manager. Reason:
[chars].

ASIC Error library encountered an error

while setting up a SYSDB notofication
handler with the event connection
manager.

ASIC Error library failed to [chars]. Reason: ASIC Error library encountered an error
[chars].
during the specified SYSDB operation.

ASIC Error library failed to [chars]. Reason: ASIC Error library encountered an error
[chars].
during the specified SYSDB operation.

ASIC Error library failed to [chars]. Reason: ASIC Error library encountered an error
[chars].
during the specified SYSDB operation.

ASIC Error library failed to [chars]. Reason: ASIC Error library encountered an error
[chars].
during the specified SYSDB operation.
ASIC Error library: Encountered SYSDB Bag ASIC error library encountered a SYSDB
encode error <[chars]> during [chars]
encode error while performing the
operation.
indicated operation.
ASIC Error library: Encountered SYSDB Bag ASIC error library encountered a SYSDB
encode error <[chars]> during [chars]
encode error while performing the
operation.
indicated operation.
ASIC Error library: Encountered SYSDB Bag ASIC error library encountered a SYSDB
encode error <[chars]> during [chars]
encode error while performing the
operation.
indicated operation.
ASIC Error library: Encountered SYSDB Bag ASIC error library encountered a SYSDB
encode error <[chars]> during [chars]
encode error while performing the
operation.
indicated operation.

ASIC Error library has failed to register an

EDM. Reason: [chars].

The ASIC Error library was unable to

become an external data manager despite
having a connection to the SYSDB.

ASIC Error library has failed to register an

EDM. Reason: [chars].

The ASIC Error library was unable to

become an external data manager despite
having a connection to the SYSDB.

ASIC Error library has failed to register an

EDM. Reason: [chars].

The ASIC Error library was unable to

become an external data manager despite
having a connection to the SYSDB.

ASIC Error library has failed to register an

EDM. Reason: [chars].

The ASIC Error library was unable to

become an external data manager despite
having a connection to the SYSDB.

[chars]: sending request to asic scan

server...

This is informational message indicating

that the ASIC SCAN is started from CLI.

ASIC Scan is completed successfully.

Informational message indicating the ASIC

SCAN is completed.

ASIC Scan Server exits after a successful

scan

ASIC scan server exits, expected behavior.

[chars]

This is a message in the Asic Scan Server

to indicate that it has triggerred a critical
alarm and will result in node bringdown.
The reason for the failure and the status of
the scan operation is reported.

ASIC Scan is started.

Informational message indicating the ASIC

SCAN is started.

[chars]

ASIC scan server xsvf execution

encountered an error condition, usually this
could be caused by hardware failure in
JTAG chain.

ASIC scan server has failed to create the

ASIC Scan Server failed to create the event event manager. This would result in the
manager: Reason = [chars].
automatic restart of the process.

ASIC Scan Server failed to get the card

type: Reason = [chars].

ASIC scan server has failed to get the card

type. This would result in termination of the
server process.

ASIC Scan Server encountered error

[[chars]]: Reason = [chars].

ASIC scan server has failed the initialization

sequence due to the specified reason. This
would result in the automatic restart of the
process.

ASIC Scan Server failed to [chars]: Reason

= [chars].

ASIC scan server has failed the specified io

operation.

IM error: [chars] :: interface/PVC: [chars]

Error in IM(Interface Manager) operation

first %s - Type of the failure second %s Interface/PVC which failed the lookup This
error happens on an LC with ATM
interfaces.

An internal error detected--> [chars] :

[chars]

Internal error message. first %s - Type of

failure second %s - reason for failure The
error could be from various reasons. The
message itself contains a good info.

SYSDB Tuple error: [chars]

Error in sysdb operation. The datatype sent

by sysdb is invalid w.r.t atm_ilmi %s invalid datatype that we received

An internal failure occured during the

initialization of debug registration. Failure is
Debug registration failed with failure return related with debugging. It would not affect
value: [chars]
the router's other functions.

Operation failed due to memory shortage,

function: [chars]

Memory on the box is critically low.

Failed to open card specific dll [chars]

Card specific dll may not be present. Due

to the above reason, this message will be
flashed while setting up the NetIO chain
elements.

Insertion to ATM Netio Dictionary fails

The env variable setting may not be set up

for load path variable

DLL not found for the specified card :

[chars]

Check the installation Dlls missing from

package

Failed to get load path env variable for dll

[chars]

The env variable setting may not be set up

for load path variable

Failed to allocate [unsigned int] bytes of

memory

The DLL has failed to acquire the required

amount of memory. There might be some
other process consuming more memory
which creates memory shortage for this.

Failed to parse atm_netio.rules at line:

[chars]

The file atm_netio.rules has been modified

and parsing fails

Path to load the atm_netio.rules is NULL

The path to atm_netio.rules file cannot be

located.

Debug registration failed: [chars]

Debug message registration failed. This will

not leave much impact on the functionality,
this is just an info to the user that no
debugging will be available for the ATM
NetIO dll.

IM operation faced an error: [chars] :

[chars]

Error in IM(Interface Manager) operation %s

- Type of error %s - reason for the error This
error happens on the LC with ATM
interfaces

Internal error. %s - Failure %s ifhandle/interface_name/function name

An internal error occurred: [chars] : [chars] This happens on the LC with ATM interfaces

sysdb operation faced an error: [chars]

Error in sysdb operation. %s - Type of the

error. This error happens on the LC with
ATM interfaces It could be one of the
following types: - Unknown parameter Sysdb Tuple is not of proper type - Sysdb
Tuple fetched is corrupt - Parameter was
out of range - Invalid Configuration

Unable to set [chars] in sysdb: [chars]

Error in sysdb operation. Error while setting

the value in sysdb. first %s - type of the
error second %s - reason of the error.

A critical function failed that expected to

The function got errored internally: [chars] : succeed. first %s - type of error second %s
[chars]
- reason for the error

Failed to allocate [dec] bytes due to

memory shortage

Memory on the router is critically low. %d amount of memory that is tried to be

allocated

Insufficient bandwidth available. possible

cause: Too many vc's inheriting QoS from
class parameters %s - gives the name of
the interface %u - gives the available
[chars] : Bandwidth available [unsigned int] bandwidth size %u - gives the bandwith
: Failed to reserve [unsigned int]
that failed to apply

Failed to initialise ATM SAAR: [chars]

([chars])

There was an error initialising the ATM

SAAR component. first %s --> Describes
the error second %s --> return code string

Debug registration failed: [chars]

Debug message registration failed A very

corner scenario with no functional impact
this is just an info to the user that no
debugging will be available.

Unable to init socket_evm: [chars]

The initialization of socket with event

manager failed due to some reason. The
argument depicts the reason of the failure.

Error while receiving messages. Exiting

A very rare event where a message read

was errored. The error should not be
persistent.

Allocation of [dec] bytes failed due to

memory shortage

Memory on the router is critically low. %d amount of memory that was tried to be
allocated.

pak client cleanup failed: [chars]

The cleanup API failed due to some reason.

The argument represents the reason for
the failure.

Failed to setup atm socket as a resource

manager: [chars]

The atm_io process failed to advertise itself

to the system as a resource manager. %s reason for failure.

The SOP FPGA has been interrupted due a

ATM SOP Intr: [chars]: [dec]: [chars]: [dec] hardware error %s - Error message %d [chars]
Interrupt %s - Data1 %s - Data2 %s - Data3
ATM SOP DEBUG: [chars]: [hex]: [hex]:
[hex]

ATM SOP debug message %s - Debug

message %lx - Asic %x - Data1 %x - Data2

Just in case, the parameter is not found

w.r.t. ifhandle, default demux limit gets set.
[chars]: Setting DEFAULT demux limit [dec] first %s - Happened at second %d - demux
for interface [chars]
limit value third %s - interface name

VCM-IM faced: [chars] : [chars]

Error in IM(Interface Manager) operation

first %s - Failure second %s - reason for the
failure This happens on the LC with ATM
interfaces

Ifhandle/Name--> [chars] : Error-->

[chars] : Reason--> [chars]

Internal error. Type of error and reason will

be there in the msg %s - ifhandle/ name of
errored interface %s - Type of the error
occured %s - Reason for the error This
happens on the LC with ATM interfaces

An internal sysdb error encountered:

[chars]

Error in initialization of verification

functions with Sysdb or the registration of
the debug %s - reason for the error. This
error happens on the LC with ATM
interfaces

Can't connect to configuration [chars]

Connection Traffic Table manager

registration with SYSDB verification errored
somehow, the argument will show the
reason of the error.

[chars]: Signal handler caught SIGSEGV

[dec]\n

Connection Traffic Table manager kicked

the bucket, an overflow condition reached.

Starting CTT_MGR

A notification that Connection Traffic Table

manager is going to be started.

[chars]: pci= [hex]

An info regarding the ATM PCI, while

converting it to VPI and VCI. first %s Happened at second %x - Hex value for the
PCI

Inside the method: [chars]\n

An info regarding a particular method

getting hit in atm_vcm. It eases the
debugability part and has no functional/
operational impact.

[chars]: im_iftype is [dec]

An info regarding the type of interface/VC

from interface manager corresponding to
the main idb. first %s - Happened at
second %d - decimal number for the iftype

error, reason:[chars]

GSR SPA Driver encountered an error while

bringing up the SPA devices. %s - Error
message

[chars], [dec] error, reason:[chars]

PLIM Drivers for the ATM have encountered

an error.

[chars] - [dec]: [chars] rc=[hex]

connid=[dec] key=[hex]

atmdrv error occurred while updating the

canonical header for a connection.

[chars] (rc = [hex])

GSR SPA Driver encountered an error while

initializing the SPA device. %s - Error
message %x - Error Code

[chars] - [dec]: [chars] (rc = [hex])

atmdrv error occurred when initializing any

of the devices in E3 ATM card or while
programming a VC.

[chars] - [dec]: [chars] (connid = [dec])

atmdrv error occurred when trying to add,

modify or delete a VC. The error can be
returned from the SAR or the CPK Asic.

Initialization error at [chars]:[dec] suberror: [chars] error-code: [dec]

Above run time error occurred while

initializing atm driver.

Failed to load PAL dll at [chars]:[dec] suberror: [chars] error-code: [dec]

ATM driver failed to load PAL DLL

[chars]. Port [dec]: number of occurance = atmdrv cpk24 interrupt handling related
[unsigned int] intr_status = [hex]
errors, or alerts

[chars], [dec] warning, reason:[chars]

atmdrv warning message while working

with a wred profile

reason:[chars] port:[dec], vpi/vci:[dec]/

[dec], connid:[dec], channels(r/s):[hex]/
[hex], shape:[dec], encap:[dec]

atmdrv debug message

[chars]: failed to initialize debug events,

with failure message [chars].

A failure occurred during the initialization

of the debug events.

[chars]: failed to initialize process, with

failure message [chars].

A failure occurred during the initialization

of the process. This resulted in the restart
of the process.

[chars]:datagram adjust failed.

This is due to failure in datagram field

adjustment during conversion to generic
header.

Neighbor device advertised the same

configured Auto-IP address([chars]) as on
the local device

Auto-IP Ring feature requires each device

to configure a unique auto-ip address,
different from those on other devices. The
local device is configured with an Auto-IP
address. However the local device has also
received the same Auto-IP address from a
neighbor device. This may indicate that
two devices are configured with the same
Auto-IP address.

Port([chars]): Received the same

priority([dec]) as the peer device

The Auto-IP Ring feature requires two peer

devices to exchange different Auto-IP
priorities, in order to facilitate the IP autonegotiation process. If they advertise the
same Auto-IP priority, then IP autonegotiation will not happen. This may
indicate that the ring ports of the two
devices are wrongly wired.

Error: Adding batched channelized

interface caps failed. Reason: [chars]

'There is an error when adding batched

channelized interface caps.'

Error: Failed to modify channelized

interface caps. Reason: [chars]

'There is an error when modifying

channelized interface caps.'

Failed during create ECM initialization, Err: 'There is a software error when creating
[chars]
ECM connection between SPA and b-shim'

Error: Setting call-back to IM failed. Reason: 'There is a software error when trying to set
[chars]
call-back to IM.'

Error: Failed to bind to IM. Reason: [chars]

'There is a software error when trying to

bind to IM.'

Error: Failed to unbind to IM. Reason:

[chars]

'There is a software error when trying to

unbind to IM.'

Failed to initialize AIB connection: [chars].

Exiting...

BFD SSE was unable to setup the

cwconnection to AIB for processing
adjcency changes events. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will reload the MSC.

BFD SSE was unable to initialize CPU

Controller interface for sending/receiving
BFD packets or messages via PDMA. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
Failed to initialize CPU Controller interface: encountered, to recover. If the problem
[chars]. Exiting...
continues, sysmgr will reload the MSC.

Failed to register component error

messages: [chars]. Exiting...

BFD SSE was unable to register to

component error message services. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger respective
MSC reboot.

Failed to create the event connection

manager for [chars]: [chars]. Exiting...

BFD Agent encountered an error while

attempting to create an event connection
manager for the specified path. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger respective
MSC reboot.

BFD Agent encountered an error while

attempting to install an ECM notification
handler for the specified path. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
Failed to install ECM notification hanlder for continues, sysmgr will trigger respective
[chars] path: [chars]. Exiting...
MSC reboot.

[chars] : [chars]

An internal error occurred that was

expected to succeed.

Failed to initialize interface database:

[chars]. Exiting...

bfd_agent encountered an error while

initializing its interface database
information. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will reload the
MSC.

Failed to setup the tracing services:

[chars]. Exiting...

BFD SSE was unable to initialize the tracing

services. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
respective MSC reboot.

Failed to allocate memory.

BFD Agent has failed to allocate memory

for its resources. This would affect proper
functioning of BFD Agent.

Sysdb unable to [chars]: [chars]

BFD Agent encountered a Sysdb

communication failure. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger respective
MSC reboot.

Connection to the sysdb server failed:

[chars]

BFD Agent failed to open a connection to

the SysDB Server process for one of the
paths. The System Manager process
(sysmgr) will automatically respawn this
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
respective MSC reboot.

Failed to register as an EDM for [chars]:

[chars], exiting...

The bfd_agent was unable to become an

external data manager (EDM) for the
specified path. The System Manager
process (sysmgr) will automatically
respawn this process, up to a fixed number
of times the error is encountered, to
recover. If the problem continues, sysmgr
will trigger respective MSC reboot.

[chars] : [chars]

BFD Agent encountered a minor internal

software error. It is possible that BFD Agent
operates normally without any issues.

BFD Agent: SYSDB Bag encode[[chars]]:

[chars]

BFD Agent server encountered error in

sysdb bag encode operation. This could
affect output of some of the BFD CLI
commands.

BFD session [chars] has failed to update

echo source address to [chars].

Failed to change echo source address and

construct echo packet hdr for BFD session.

One or more PROT_BFD_SESSION_DOWN

event(s) has been lost due to lack of
protect server initialization

One or more PROT_BFD_SESSION_DOWN

PFI fast protect event has been lost. If a
link which BFD session failed happened to
be fast-reroute protected, fast-reroute may
not have been triggered.

BFD could not initialize itself as PFI fast

protect server, PROT_SERVER_BFD, since
PFI fast protect infrastructure returned
failure. BFD will continuously retry
initialization in the background until
successful. However, until successfully
initialized, BFD session failure can not
generate PFI fast protect event for
Failed to initialize protect server with error PROT_BFD_SESSION_DOWN, which may
'[chars]'
prevent fast-reroute from being triggered.
BFD session [chars] has failed to revert
echo source address to [chars].

Failed to revert echo source and construct

echo packet hdr for BFD session.

BFD session [chars] has reverted echo

source address to [chars].

Revert echo source and construct echo

packet hdr for BFD session successfully.

BFD Async Detect timer expired [chars]

even when async pkt received within timer
duration, timer_duration =[unsigned int]
BFD Async Detect timer expired even when
ms, [unsigned int] ms elapsed since last
async pkt received within timer duration,
async pkt received
timer_duration
BFD PPS allocation exceeds 90 percent of
maximum.

BFD has allocated 90 percent of its packet

per second allowance on this LC.

BFD PPS allocation now less than 85

percent of maximum.

BFD has released some of the previously

allocated packet per second usage and is
now at less than 85 percent of its
allowance on this LC.

BFD has allocated 90 percent of its

multipath-specific packet per second
BFD multipath resource allocation exceeds allowance or maximum number of BFD
90 percent of maximum on all multipathsessions on every multipath-configured
configured linecards
linecard in the system

BFD has released some of the previously

allocated packet per second usage or
number of BFD sessions and is now less
BFD multipath resource allocation now less than or equal to 85 percent of its allowance
than or equal to 85 percent of maximum on on at least one multipath-configured
at least one multipath-configured linecard linecard.

BFD has detected resource leak in [chars]

area(s)

BFD was not able to free certain resources,

such as allocated memory, discriminator or
checkpoint object, due to infrastructure API
returning error from free/deletion
operation(s). BFD should be able to
continue processing by allocating new
resources. However, support personel
should be contacted to investigate the
cause of resource leak.

Adjacency [chars] was deleted

The adjacency for neighbor ip address was

deleted.

Forwarding is not ready [chars]

The forwarding for session is not ready.

Number of requested sesssions has

exceeded limit [dec]

Each linecard is only able to host specific

number of BFD sessions. This message
indicates that maximum number of hosting
BFD sessions has reached its maximum.
Those session creating requests after
reaching this limit will purposely be
prevented from being created. These
prevented sessions will continuously be
retried to be created in the These
prevented sessions will continuously be
retried to be created in the background,
and they will be once resources are
available (ex: once some existing essions
are deleted). Those sessions in the retry
queue can be viewed via 'show bfd session
pending' command.

Successfully initialized protect server

After failing to initialize itself as PFI fast

protect server, PROT_SERVER_BFD, once or
more, BFD was able to successfully
complete initialization.

BFD session [chars] is not running in all

member mode

The specified BFD session is not running in

all member mode.

BFD session [chars] is running in all

member mode

The specified BFD session is now running in

all member mode.

No resources for session [chars] to run

echo mode, continuing with async mode

This BFD over bundle session cannot run

echo mode due to lack of PPS resources.
The session will continue to run in async
mode until PPS is available. Once PPS
resources have been cleared up, then
disable and enable echo mode on this
interface via configuration to startup up the
echo mode.

Lack of resources condition has cleared for Resources are now available for this BFD
session [chars] to run echo
over bundle session to run echo mode.

Dampening for BFD session to neighbor

[chars] on interface [chars] has been
cleared

Exponential backoff dampening for BFD

session has been cleared for specified BFD
session. When/if same session gets created
by application(s), only calculated initial
wait time will be applied.

BFD session [chars] is not inheriting state

from session over [chars]

The specified BFD session is no longer

inheriting BFD state from another BFD
session.

BFD session [chars] is inheriting state from The specified BFD session is now inheriting
session over [chars]
BFD state from another BFD session.

No resources for session [chars],

interval=[unsigned int] ms[chars]

The BFD session can not be created or

modified due to lack of resources.

Lack of resources condition has cleared for Resources are now available for this
session [chars]
session.

BFD session [chars] has been removed

The BFD session has been removed. This is

due to the application(s) removing the BFD
session. This can happen as a result of BFD
being unconfigured under the
application(s) or as a result of the
application(s) adjacency being removed.

BFD session [chars] has gone down.

Reason: [chars]
BFD session [chars] is up

The BFD session has gone down. This may

be as a result of the forwarding path being
down.
The BFD session is now up.

BFD session [chars] is administratively

down due to version change from version
[unsigned int] to version [unsigned int]

The BFD session has been brought

administratively down to change protocol
version.

Failed to allocate a label block

'This error happens when the system had

failed to allocate a label block ' 'as it may
be running out of the label blocks. ' 'Note
that when label blocks are freed, they go to
zombie state for ' '30 minutes. During this
period, repeated addition/removal of the
same ' 'configuration will result in
allocating different label blocks each time. '
'This can lead to running out of label blocks
quickly '

A failure occurred during the registration of

the DLL for decoding error codes from the
Failure registering cerrno DLL with subsys bundle manager component. This may
num [unsigned int] and DLL name [chars]. render certain codes unprintable, but
Error: [chars]
otherwise has no negative impact.

A failure occurred during the registration of

the DLL for decoding error codes from the
Failure registering cerrno DLL with subsys component. This may render certain codes
num [unsigned int] and DLL name [chars]. unprintable, but otherwise has no negative
Error: [chars]
impact.

A failure occurred during the registration of

the DLL for decoding error codes from the
Failure registering cerrno DLL with subsys component. This may render certain codes
num [unsigned int] and DLL name [chars]. unprintable, but otherwise has no negative
Error: [chars]
impact.

A failure occurred during the registration of

the DLL for decoding error codes from the
Failure registering cerrno DLL with subsys component. This may render certain codes
num [unsigned int] and DLL name [chars]. unprintable, but otherwise has no negative
Error: [chars]
impact.

Failure registering ErrorCode DLL with

subsys num [unsigned int] and DLL name
[chars]. Error: [chars]

A failure occurred during the registration of

the DLL for decoding error codes from the
component. This may render certain codes
unprintable, but otherwise has no negative
impact.

A failure occurred during the initialization

Failure during intialization of [chars]. Error: of the LC platform dependent bundle
[chars]
manager DLL.

A failure occurred during the initialization

of the platform dependent adjacency
Failure during intialization of [chars]. Error: programming DLL. This will result in the
[chars]
hosting process being restarted.

A failure occurred during the initialization

of the platform dependent bundle Manager
adjacency programming DLL. This will
Failure during intialization of [chars]. Error: result in the hosting process being
[chars]
restarted.

A failure occurred during the initialization

of the platform dependent adjacency
Failure during intialization of [chars]. Error: programming DLL. This will result in the
[chars]
hosting process being restarted.

A failure occurred during the initialization

of the platform dependent adjacency
Failure during intialization of [chars]. Error: programming DLL. This will result in the
[chars]
hosting process being restarted.

A failure occurred during the initialization

of the platform dependent adjacency
programming DLL. This will result in the
hosting process being restarted. This
condition can occur while : 1. Trying to get
Failure during intialization of [chars]. Error: the host Event Manager 2. Initializing the
[chars]
debug library

Failure initializing tracing ([chars] buffer).

Error: [chars]

A failure occurred during the initialization

of tracing for the adjacency management
DLL. This will cause the DLL to be
unloaded, and adjacency programming will
not happen.

Failure initializing tracing ([chars] buffer).

Error: [chars]

A failure occurred during the initialization

of tracing for the LC bundle manager DLL.

Failure initializing tracing ([chars] buffer).

Error: [chars]

A failure occurred during the initialization

of tracing for the adjacency management
DLL. This will cause the DLL to be
unloaded, and adjacency programming will
not happen.

Failure initializing tracing ([chars] buffer).

Error: [chars]

A failure occurred during the initialization

of tracing for the adjacency management
DLL. This will cause the DLL to be
unloaded, and adjacency programming will
not happen.

Failure initializing tracing ([chars] buffer).

Error: [chars]

A failure occurred during the initialization

of tracing for the adjacency management
DLL. This will cause the DLL to be
unloaded, and adjacency programming will
not happen.

Failure initializing tracing ([chars] buffer).

Error: [chars]

A failure occurred during the initialization

of tracing for the adjacency management
DLL. This will result in not registering the
debug DLLs. The adjacency programming
will continue.

Unable to obtain base MAC address

LRd returned a NULL MAC address to be

used as the base MAC address for the
system and bundle MAC addresses.

A failure occurred during the initialization

of the platform independent adjacency
Failure during intialization of [chars]. Error: completion DLL. This will result in the
[chars]
hosting process being restarted.

Failure during intialization: [chars]. Error:

[chars]

A failure occurred during the initialization

of the platform independent adjacency
completion DLL. This will result in the
hosting process being restarted.

A failure occurred during the initialization

of the platform independent adjacency
Failure during intialization of [chars]. Error: completion DLL. This will result in the
[chars]
hosting process being restarted.

A failure occurred during the initialization

of the platform independent adjacency
Failure during intialization of [chars]. Error: completion DLL. This will result in the
[chars]
hosting process being restarted.

A failure occurred during the initialization

Failure during intialization of [chars]. Error: of the bundlemgr adjacency process. This
[chars]
resulted in the restart of the process.

A failure occurred during the initialization

of the platform independent adjacency
Failure during intialization of [chars]. Error: completion DLL. This will result in the
[chars]
hosting process being restarted.

Failure during intialization: [chars]. Error:

[chars]

A failure occurred during the initialization

of the process. This resulted in the restart
of the process.

A failure occurred during the initialization

Failure during intialization of [chars]. Error: of the process. This resulted in the restart
[chars]
of the process.

A failure occurred during the initialization

Failure during intialization of [chars]. Error: of the process. This resulted in the restart
[chars]
of the process.

A failure occurred during the initialization

Failure during intialization of [chars]. Error: of the process. This resulted in the restart
[chars]
of the process.

Internal Error: String [chars]

This is an informational message in the

Bundle Mgr to indicate that an internal
software error was seen

[chars]

This is an informational message in the

Bundle Manager to indicate an operation
like retry or recovery after retry due to
previous error.

Unable to decode [chars] attribute for

bundle ([chars]). Error: [chars]

Updates to bundle membership parameters

have been ignored because the received
data could not be decoded.

Failure during activation of [chars]. Error:

[chars]

A failure occurred during the activation of

the process. Activation occurs when the
card transitions to ACTIVE state. This error
resulted in the restart of the process.

Unable to interpret member or load

balance data specified by IM for [dec]
[chars] interfaces (out of batch of [dec]).
Sample error, on <<CH[hex]>>: [chars]

The data specified in the IM attribute

notification cannot be interpretted. The
information is invalid and the result is that
adjacencies for these bundles or subs
cannot be programmed in hardware.

Unable to recreate object ID [unsigned int] When recovering data from checkpoint, an
after restart. Error: [chars]
error occurred and the data is lost.

Could not error-disable interface [chars];

driver returned [chars]

A member interface could not be errordisabled as the driver claims not to support
this feature. If the member is running in
Ether/POSChannel mode, traffic may still
be received on this member - this may
breach configured QoS policies and will
prevent an mLACP brute-force switchover
from taking place.

Unrecoverable error in event loop. Error:

[chars]

An error (other than EINTR) occured in the

event loop. The process has exited and
restarted.

After attempting to resend or query

information a number of times, the retry
threshold has been hit and no more
attempts will be made for any global
operations. The effect of the message will
therefore be lost. The impact will depend
on the message which was lost, but the
Exceeded threshold for the number of
error will give an indication as to the
retries for [unsigned int] global operations. failure. Further information may also be
First error [chars], retries performed for
found in <CmdBold>show
[chars]
bundle<noCmdBold>.

Creation of the group used to communicate

Unable to create GSP group ([chars]). Error: between Bundle Manager processes failed.
[chars]
This resulted in the restart of the process.

Unable to report IIR op failure for b_ifh

[hex], m_ifh [hex] (op [chars], state
[chars]). Error: [chars]

An error occurred processing the IIR event

and the bundle EA process was unable to
report this error back to IIR. This may lead
to some inconsistency with the bundle
membership in the data plane not
matching what is intended according to the
control plane.

A failure occurred during the initialization

Failure during intialization of [chars]. Error: of the process. This resulted in the restart
[chars]
of the process.

Link [chars] is attached to [chars] that is

thought to have no attached members.

This process believes that there are no

aggregatable links, but this link is marked
as attached. This error is most likely
caused by failing to attach or detach a link
correctly.

Unable to allocate [unsigned int] bytes of

memory.

Memory allocation failed.

Failure during cleanup of [chars] in the

dot3ad MIB DLL. Error: [chars]

A failure occurred during the cleanup of the

DLL. This may result in the DLL not being
completely cleaned up, possibly causing
errors in a subsequent re-initialization of
the DLL.

A failure occurred during the initialization

of the DLL. This resulted in the DLL not
Failure during intialization of [chars] in the being loaded into the SNMP agent, and
dot3ad MIB DLL. Error: [chars]
thus the MIB services will not be available.

Failure [chars] in the bundle NetIO DLL

during [chars]. Error: [chars]

A failure occurred during the initialization

of the bundle NetIO DLL. If this occured
during an upgrade operation then it will
cause the NetIO process to reload.
Otherwise this will cause the capsulation to
be unloaded, and an error returned to the
user. One possible reason for the error is a
low memory condition, particularly if the
failure was in allocating trace buffers.

Exceeded threshold for the number of

retries for [unsigned int] operations on
[chars]. First (and error) [chars] ([chars]),
retries performed for [chars]

After attempting to resend or query

information a number of times for a set of
objects, the retry threshold has been
exceeded and no more attempts will be
made for any in this set. The effect of the
message will therefore be lost. The impact
will depend on the message which was
lost, but the error will give an indication as
to the failure. Further information may also
be found in <CmdBold>show
bundle<noCmdBold>.

A packet manager corruption has been

reported and the Bundle Manager process
has failed to cleanup to recover from the
problem. The process will exit and be
Unable to handle pakman corruption error: automatically restarted to recover from this
[chars]. Process exiting
situation.

Unable to recreate bundle <<CH[hex]>>.

Error: [chars]

When recovering the checkpointed data for

a bundle, an error occurred and the data is
lost.

Unable to repair bundle <<CH[hex]>>

checkpoint structures. Error: [chars]

When repairing the checkpoint structures

for the bundle database an error occurred
for named bundle and the bundle was not
checkpointed. The next time an attempt is
made to checkpoint the bundle it will fail
and the checkpoint table will be
reconstructed again, perhaps more
successfully.

Unable to repair [chars] database. Failure

during checkpoint [chars]. Error: [chars]

When repairing the checkpoint structures

for the named database an error occurred
in the database checkpoint registration. As
a result the process was intentionally
restarted.

Replication failed for [chars], to [unsigned

int] node(s). First node: [chars]. Error:
[chars]

When attempting to replicate the bundle to

one or more new interface locations, the
replication operation failed. This probably
happened because some hardware
resource on the specified LC(s) was
exhausted. The record of the new
member(s) which triggered this replication
will be removed from the bundle process
on the RP but will still be referenced by the
bundle process on the LC.

Exceeded the IIR resync limit for [chars].

Process exiting.

The maximum number of attempts to

resync with IIR have been exceeded for this
bundle. The safest course of action is to
restart the process and this has been done.

Unable to schedule an IIR resync for

[chars]. Process exiting.

An attempt to schedule a resync with IIR

has failed for this bundle. The safest course
of action is to restart the process and this
has been done.

Exceeded maximum number of retries for

[chars]

After attempting to resend or query

information a number of times, the retry
limit has been exceeded and no more
attempts will be made. The effect of the
message will therefore be lost. The impact
will depend on the message which was
lost. If the message refers to a global error
then the process will exit and be restarted.

Retry limit for GSP initialization exceeded:

[chars]

After attempting to create the GSP group

used for communications with the Bundle
Manager process on another node a
number of times, the retry limit has been
exceeded. The cause of the failure is very
likely to be some external communication
failure - so check for evidence of this. The
process will exit and be restarted
automatically so no futher action is needed
for Bundle Manager to retry.

Exceeded the retry limit for IMP events.

The maximum number of attempts to retry

an IMP message has been exceeded. An
error has occurred in the clean up of a
bundle, so there may be residual data for
the bundle in the linecard components
which could cause subsequent problems.
Restart the process that reported the error
to recover.

Retry limit for Protect initialization

exceeded: [chars]

After attempting to initialize the Protect

module a number of times, the retry limit
has been exceeded. The cause of the
failure is very likely to be some external
communication failure - so check for
evidence of this. The process will exit and
be restarted automatically so no futher
action is needed for Bundle Manager to
retry.

Retry limit for system MAC address query

exceeded: [chars]

After attempting to query the system MAC

address from SDRd a number of times, the
retry limit has been exceeded. The cause
of the failure is likely to be an issue with
SDRd or Shelfmgr - so check for evidence
of this. The process will exit and be
restarted automatically so no futher action
is needed for Bundle Manager to retry.

Unable to retrieve the control parent from

IM for a subinterface or satellite
(<<CH[hex]>>)

IM could not provide information on the

control parent for a given subinterface. This
means that adjacencies for this
subinterface cannot be programmed in
hardware.

The process was initialized successfully but

Failure communicating readiness to System was unable to inform System Manager of
Manager. Error: [chars]
the success.

After a resync has occurred between

Bundle Manager and the MAC allocation
process, the MAC address assigned for use
as the system MAC has not been found in
the addresses allocated to bundle
manager. Bundle manager will choose a
Existing system MAC address not found in new MAC address for use for this purpose.
allocation. System MAC address for bundles A flap will be seen on bundle links running
is being reset
LACP.

Failed to create non-existent entry for

interface <<CH[hex]>> while attempting
to [chars]: [chars]

An attempt to create a new database entry

for a port failed. In addition to indicating
that the line card is running low on system
resources, this suggests that the sharedmemory database is out-of-sync with the
main database. Once some system
resources have been released, the
bundlemgr_local process should be
restarted to retry the timer creation.

An attempt to create or start a timer for

periodic sending failed. Regular LACPDUs
will NOT be sent out. This suggests that the
line card is running low on system
resources. Once some system resources
have been released, the bundlemgr_local
Failed to [chars] periodic timer for interface process should be restarted to retry the
<<CH[hex]>>: [chars]
timer creation.

Unreplication failed for [chars], to

[unsigned int] node(s). First node: [chars].
Error: [chars]

When attempting to unreplicate the bundle

from the specified location(s), the
unreplication operation failed. Some
hardware resources may continue to be
used for the bundle on the specified
location(s). It is also possible that there
could be a problem replicating the bundle
to those locations again if a new member is
added.

Unable to generate Ethernet header data

for interface [chars]. Error: [chars]

The LACP protocol will not be able to run on

this interface. This may be because the
interface has a complex encapsulation
configured, which is not supported in
conjunction with LACP. Complex
encapsulations include: - Matching on
source or destination MAC addresses Matching on payload ethertype - Matching
on VLAN tags using the 'any' keyword. In
these cases, it cannot be determined how
to format the ethernet header for sending
LACP packets, and hence LACP is not
supported in these scenarios.

A locally or partner-allocated Link Ordering

Number which is larger than the maximum
Prolonged mismatch between Link Ordering active links value has been detected. The
Numbers and maximum active links
link order signaling feature has been
settings on [chars]%s
disabled until the mismatch is rectified.

Could not form consistent set of partnersupplied Link Order Numbers on [chars]
within [unsigned int] seconds

The local system has been unable to form a

consistent set of Link Order Numbers from
the data supplied by the LACP partner. This
means that the links may not be ordered
identically on the two ends of the bundle.

When resyncing with LRd, bundlemgr has

unexpectedly found that a bundle member
Bundle member [chars] is being referenced is on a card that no longer exists. The
from a non-existent node [hex]
member will be cleaned up.

Selection Logic for bundle [chars]: [chars]

There has been a misconfiguration

resulting in the problem described being
hit in the Selection Logic operation for the
bundle.

Failed to elevate thread priority. The

response time of bundle interface failure
notifications may be impacted. Error:
[chars]

A failure occurred when trying to set the

priority of the Protect thread. This will not
cause any loss of functionality, e.g.
notifications of bundle interface failure will
still be delivered to trigger fast reroute.
However, such notifications may be
delivered with higher latency.

Actor churn has either been detected (due

to the failure of a link to synchronize soon
enough) or has been cleared. If the link is
in Standby state, then actor churn will be
detected after the churn timeout; this is
Interface [chars] in [chars] [chars] on actor expected behavior. Otherwise, this
system
indicates a possible misconfiguration.

Incompatible configuration [chars]for

[chars]%s

A configuration change has meant that a

bundle now has incompatible configuration.
All links have been disabled. The reason for
the incompatibility at the time of raising
the alarm is supplied in the message.

After a resync with the MAC address

allocation server, the Bundle Manager
process found that it had more MAC
addresses than required by the bundle
configuration settings and tried to release
some to the server. However, this
operation failed, so these extra MACs were
kept in the Bundle Manager allocation. This
is not an issue unless there is a shortage of
Could not release reserved MAC addresses MAC addresses for another feature (e.g.
from allocation
Interflex).

Unable to queue LACP packet for ingress

processing on interface <<CH[hex]>>
(reason: [chars]). Processing will resume
with next received LACP packet.

An attempt to queue a received packet for

processing failed. An occasional message
of this type indicates that bundlemgr_local
has temporarily been blocked from
processing the queue leading to this
harmless condition.

The received partner sequence number is

too far behind the last sent actor sequence
number. This indicates either that one or
Possible dropped or delayed packet on
more LACPDUs sent to the partner device
[chars]: Received partner seq: [unsigned
have been dropped, or there is a long delay
int], Expected: [unsigned int] or [unsigned on the partner device in processing the
int]
LACPDUs.

Possible dropped packet on [chars]:

Received actor seq: [unsigned int],
Expected: [unsigned int]

There has been a jump in the received

actor sequence number, indicating that a
LACPDU from the partner has been
dropped. Note that rate limiting on
transmission takes place before the
sequence numbers are incremented, so the
warning will not be related to rate limiting
on transmission. However, it is possible
that rate limiting on receipt will cause a
sequence number discrepancy.

Possible dropped packet detected by

partner on [chars]: Received actor seq:
[unsigned int], Received partner seq:
[unsigned int]

There has been a jump in the actor

sequence numbers received by the
partner, indicating that a LACPDU from this
device to the partner has been dropped.
This condition has been signalled from the
partner to this device. Note that rate
limiting on transmission takes place before
the sequence numbers are incremented, so
the warning will not be related to rate
limiting on transmission. However, it is
possible that rate limiting on receipt will
cause a sequence number discrepancy.

The BFD session on the member has

transitioned to NBR_CONFIG_DOWN state,
indicating that the configuration has been
removed from the neighbor. The member
will continue to transmit packets for as long
The BFD session on link [chars] in [chars] as the message specifies, at which point, if
has indicated that its neighbor session has the session has not gone back UP, the
been unconfigured. [chars]
member will be brought down.

The BFD session on link [chars] in [chars]

has timed out. The member will be
removed from the active members of the
bundle.

There are 3 possible reasons for the BFD

session to time out: - the session did not
transition to state UP within the given time
period after initial start-up. - the BFD
session transitioned to state DOWN. - the
BFD session timed out after receiving a
message indicating that the neighbor's BFD
session was unconfigured.

This is an informational message reporting

that a bundle is operationally down
because the configuration for minimum
active links and maximum active links
conflicts. The number of active links
required for the bundle to come up is
greater than the number of links permitted
[chars] [chars]has conflicting configuration to be active in the bundle, and there are at
and is [chars]held down: Maximum-active least enough links held in standby state for
links [unsigned int], minimum-active links the bundle to come up if the maximum
[unsigned int]
active link criteria were removed.

There was an error reading a message sent

by the specified mLACP peer device from
Failed to parse the mLACP message for a
the ICCP RX buffer. This message will now
[chars] event from [chars]. Reason: [chars] be lost.

Could not perform mLACP switch[chars]

requested by user for bundle [chars]:
[chars]

A switchover or switchback was requested

by the user, but this could not be
performed because the bundle is not in an
appropriate state or is not configured in the
required manner.

It was not possible to connect to the

Failed to connect to another mLACP device specific to a peer device in the specified
in ICCP Group [unsigned int]. Reason:
ICCP Group. mLACP will not be running
[chars]
over the specified ICCP Group.

[chars] [chars] as isolated due to [chars]

[chars] able to connect to the core

Core network connectivity status for the

ICCP Group has changed, affecting the
bundle. If the bundle is isolated then it
cannot be active for MC-LAG.

[chars]

There is a misconfiguration between a peer

device and the local device.

[chars] [chars].

If there is a misconfiguration for an item

that may be resolved without user
intervention, then the item will be
temporarily ignored. Once the
misconfiguration is resolved, either by a
resync of mLACP data or by the user, the
item will no longer be ignored.

[chars] [chars].

If there is a misconfiguration for an item

that may be resolved without user
intervention, then the item and its children
will be temporarily ignored. Once the
misconfiguration is resolved, either by a
resync of mLACP data or by the user, the
item will no longer be ignored. Note that
peer data which is rejected will be deleted
from the local database so the information
which caused the issue may not be visible
in show commands.

Disconnecting from [chars] due to an

inconsistency in the mLACP data that could
not be resolved with a resynchronization.
A resync failed to solve an inconsistency
Reason: [chars]
and so the local device has disconnected.
The ROID ([unsigned long long int])
received from [chars] for [chars], does not
match that expected ([unsigned long long The peer device has transmitted a different
int]). Please ensure that the ROID for the
Redundancy Object ID for the bundle to
bundle is the same on both devices
that expected.

Disconnecting from [chars] due to an

unresolvable misconfiguration: [chars]

The misconfiguration supplied could not be

resolved by arbitration and so the mLACP
system disconnected from the peer node
on the given ICCP Group.

Interface [chars] in [chars] [chars] on

partner system

Partner churn has either been detected

(due to the failure of the partner to be
marked as synchronized on this link soon
enough) or has now cleared. If the link is in
Standby state on the peer router, then
partner churn will be detected after the
churn timeout; this is expected behavior.
Otherwise, this indicates a possible
misconfiguration.

Redundancy Management for bundle

[chars]: [chars]

There has been a misconfiguration

resulting in the problem described being
hit in the redundancy handling for the
bundle.

[chars] [chars] Active as part of [chars]%s

This is an informational message reporting

that a link has entered or left Active state
as part of a bundle interface. The link
configuration may have just been changed
or there may be an operational reason for
the event such as a state change or LACP
protocol update.

The BFD session on link [chars] in [chars]

has gone UP.[chars]

The BFD session on the link has indicated

that it is UP state. The link has fast-protect
BFD protection on it until further notice.

BFD sessions have been started on all the

members of the given bundle. If the BFD
session has not gone UP by the time
specified in the message, the BFD session
on the member of the bundle will be
The BFD session on link [chars] in [chars] is marked as DOWN, which may impact
starting. [chars]
traffic.

Interface [chars] in [chars] is

[chars]incompatible with the bundle
operational state[chars]

A configuration change has meant that a

link is now incompatible (or compatible)
with the other members of the bundle, or
the bundle is operating in a mode that is
incompatible with the member's
configuration. The reason for the
incompatibility at the time of raising the
alarm is supplied in the message.

When running mLACP on a bundle, the

system ID must be common on both
The configured system id for [chars] has no devices, so cannot be configured on a pereffect as the bundle is running mLACP.
bundle basis.

This device is [chars] the active device for

[chars]

The role of the mLACP device for this

bundle has changed.

The MAC address for [chars] [chars]

Each mLACP peer specifies a MAC address

for a bundle. If the MAC addressess are
different, arbitration must occur. However,
if the peer that has supplied the value
selected through arbitration disconnects,
there will be a flap in the bundle state.

[chars] is [chars]peering with [chars].

[chars]%s

The mLACP peer device for the bundle has

changed.

Connected to [chars]

An mLACP connection has been established

to the specified device.

Disconnected from [chars]

mLACP has disconnected from the specified

devices.

An invalid mLACP port priority [chars] has

been received for [chars] on [chars].
[chars]Reason: [chars]

An mLACP peer device has requested that

the priority of the specified member be
changed. This is currently an invalid
operation due to the reason specified. If
the message indicates that the priority
request has been ignored, then the peer
will be notified that the priority change has
not been made.

The system id for ICCP Group [unsigned

int] has been established by [chars]

Each mLACP peer specifies a system id for

the ICCP group. If the system id's are
different, arbitration must occur. However,
if the peer that has supplied the values
selected through arbitration disconnects,
there will be a flap in the bundle state.

[chars] [chars] a Satellite fabric uplink,

configuration incompatiblity [chars]

This is an informational message reporting

that a bundle has or had configuration
present that could not be applied while it
was a Satellite fabric uplink. The
configuration would be ignored but the
bundle would otherwise operate normally.

Buffers full for TLV capture on ICCP group

[unsigned int]. TLV capture halted.

TLV capture has been halted on the

specified ICCP group due to lack of buffer
space. If further capture is required, the
current TLVs must be cleared (using the
<CmdBold>clear mlacp tlvcapture<NoCmdBold> command) and TLV
capture explicitly restarted. Captured TLVs
may be viewed using the <CmdBold>show
mlacp tlv-capture command<NoCmdBold>.

A failure occurred during the initialization

of the platform dependent adjacency
Failure during intialization of [chars]. Error: programming DLL. This will result in the
[chars]
hosting process being restarted.

Failure initializing tracing ([chars] buffer).

Error: [chars]

A failure occurred during the initialization

of tracing for the adjacency management
DLL. This will cause the DLL to be
unloaded, and adjacency programming will
not happen.

Unable to obtain base MAC address

LRd returned a NULL MAC address to be

used as the base MAC address for the
system and bundle MAC addresses.

[chars] failed to connect to the PIRD

database: [chars]

The specified process failed to connect to

PIRD shared memory database on
initialization.

A failure occurred during the initialization

of the platform independent adjacency
Failure during intialization of [chars]. Error: completion DLL. This will result in the
[chars]
hosting process being restarted.

A failure occurred during the initialization

Failure during intialization of [chars]. Error: of the process. This resulted in the restart
[chars]
of the process.

bvi_ma process initialization failure, Error:

([hex]) [chars]

An unrecoverable error has happened while

initializing BVI MA process. bvi_ma will be
restarted automatically. BVI interfaces may
get created later.

Failed during AIB initialization, err: [chars]

The C-shim Partner initialization failed

while trying to connect to AIB.

Failed during AIB initialization, err: [chars]

The C-shim Partner initialization failed

while trying to connect to AIB.

Fatal Error: Adding batched channelized

interface caps failed. Reason: [chars]

'There is an error when adding batched

channelized interface caps.'

Fatal Error: Adding batched channelized

interface caps failed. ifh [hex],Reason:
[chars].

'There is an error when adding batched

channelized interface caps.'

Fatal Error: Failed to modify channelized

interface caps. Reason: [chars]

'There is an error when modifying

channelized interface caps.'

Fatal Error: Failed to modify channelized

interface caps. Reason: [chars]

'There is an error when modifying

channelized interface caps.'

'The Channelized Caps definition file is

missing. There may have a packaging issue
Fatal Error: Channelized caps definition file or someone just accidently removed that
is missing. Reason: [chars]
file.'

'The Channelized Caps definition file is

missing. There may have a packaging issue
Fatal Error: Channelized caps definition file or someone just accidently removed that
is missing. Reason: [chars]
file.'

Failed during create ECM initialization, Err: 'There is a software error when creating
[chars]
ECM connection.'

Failed during create ECM initialization, Err: 'There is a software error when creating
[chars]
ECM connection.'

Fatal Error: Setting call-back to IM failed.

Reason: [chars]

'There is a software error when trying to set

call-back to IM.'

Fatal Error: Setting call-back to IM failed.

Reason: [chars]

'There is a software error when trying to set

call-back to IM.'

Fatal Error: Failed to unbind to IM. Reason:

[chars]

'There is a software error when trying to

unbind to IM.'

Fatal Error: Failed to unbind to IM. Reason:

[chars]

'There is a software error when trying to

unbind to IM.'

Warning: Failed to bind to IM. Reason:

[chars]

'There is a software error when trying to

bind to IM.'

Warning: Failed to bind to IM. Reason:

[chars]

'There is a software error when trying to

bind to IM.'

Warning: Wrong if-handle [hex] [chars]

'Receive a message with wrong interface

handle. This may be ignored.'

Warning: Wrong if-handle [hex] [chars]

'Receive a message with wrong interface

handle. This may be ignored.'

Warning: [chars] failed. Reason: [chars]

'There is a software error when handling

messages from IM.'

Warning: [chars] failed. Reason: [chars]

'There is a software error when handling

messages from IM.'

FR Subinterface counter is not initialised

Initialisation of subinterface counter in the

shared memory failed

Initialization failed: ([chars]%s)

The classification control list (ccl) DLL failed

to initialize. This DLL does a generalization
of an Access Control List to include
matching on MQC match criteria like QOS
group, MPLS EXP, etc. If the ccl DLL fails to
initialize, the access control list cannot be
programmed into the hardware. %s indicates the reason for the initialization
failure. %s - is the decoded error reason.

Connection error on [chars]: [chars]

An error occurred on one of the event

connections managed by CDP which CDP
could not recover automatically.

Unable to register for duplex change

notifications: [chars]

CDP registration for duplex change

notifications failed. This means that duplex
information will be missing from outgoing
CDP packets

Failed to add the CDP capsulation to

interface [chars]: [chars]

CDP could not install the CDP capsulation

on the specified interface and hence it is
not possible for CDP to send or receive any
packets on this interface.

Failed to remove the CDP capsulation on

interface [chars]: [chars]

CDP could not uninstall the CDP

capsulation on the specified interface and
hence CDP may be in an inconsistent state.

Failed to register for MTU size changes on

interface [chars]: [chars]

CDP failed to register with the interface

manager for MTU size changes on this
particular interface. This may cause
problems sending CDP packets.

Failed to register for state changes on

interface [chars]: [chars]

CDP failed to register with the interface

manager for state changes on this
particular interface. This means CDP will be
unable to track the state of the interface.
CDP functionality may be impaired.

Initialisation of CDP on interface [chars]

failed: [chars].

CDP is unable to run on the specified

interface. It is likely that this is due to a
lack of available resources.

It was not possible to register for stats

collection on the specified interface. The
entry in the 'show interface <name>
No CDP protocol statistics can be collected accounting' command is likely to be
on [chars]: [chars]
inaccurate for CDP packets.

[chars]: Failed to scan the IPv4 addresses

for this interface: [chars]. This means that
IPv4 information will be missing from
outgoing CDP packets

A scan of the IPv4 addresses on this

interface has failed. This means that IPv4
address information for this interface will
not be included in outgoing CDP packets.
The neighboring device will not see the
IPv4 address information for this interface.

CDP registration with the IP address library

has failed. This means that IPv4 address
information for interfaces local to this node
Unable to register for IPv4 address
will not be included in outgoing CDP
notifications: [chars]. This means that IPv4 packets. The neighboring devices will not
information will be missing from outgoing see the IPv4 address information for this
CDP packets.
router's interfaces.

[chars]: Failed to scan the IPv6 addresses

for this interface: [chars]. This means that
IPv6 information will be missing from
outgoing CDP packets

A scan of the IPv6 addresses on this

interface has failed. This means that IPv6
address information for this interface will
not be included in outgoing CDP packets.
The neighboring device will not see the
IPv6 address information for this interface.

CDP registration with the IP address library

has failed. This means that IPv6 address
information for interfaces local to this node
Unable to register for IPv6 address
will not be included in outgoing CDP
notifications: [chars]. This means that IPv6 packets. The neighboring devices will not
information will be missing from outgoing see the IPv6 address information for this
CDP packets.
router's interfaces.

Out of memory (failed attempt to reserve

[unsigned int] bytes)

CDP was not able to allocate the memory

that it needed to complete the operation.
CDP functionality on the affected node may
be reduced until the problem is resolved.

It was not possible for CDP to register for

per-interface CDP protocol stats collection.
The entries in the 'show interface
No per-interface CDP protocol statistics can accounting' command are likely to be
be collected: [chars]
inaccurate for CDP packets.

CDP received a notification to update a TLV

that it sends but failed to do so due to the
On [chars] the [chars] TLV is not up to date: error given. The information stored by CDP
[chars]
is now out of date.
Duplex mismatch discovered on [chars]
([chars]), with [chars] [chars] ([chars]).

CDP discovered mismatching duplex

configuration on neighboring interfaces.

The driver returned an error while setting

up the CDP multicast address. It is possible
Error setting up the CDP multicast address that CDP packets will be dropped and not
on [chars] (media [chars]): [chars]
reach the CDP process.

Not enough memory to clear and resize the CDP ran out of memory when trying to
CDP table
resize the CDP hash table.

The CDP cache on this node is full. It

contains [dec] neighbor entries

The limit for neighbors in the CDP cache

has been reached. No more neighbors will
be added to the neighbor cache until some
existing entries have been removed. The
number of entries is limited to defend
against DoS attacks.

CDP did not find any recognized media to

run over

CDP failed to initialize the media module

because it could not find any media that it
recognizes. This may be a normal situation
if CDP does not support the interface types
on this node. In other circumstances CDP
should recover automatically by restarting.

CDP did not find any recognized media

drivers

CDP failed to initialize the media module

because it could not find any media drivers
that it recognizes. This may be a normal
situation if CDP does not support the
interface types on this node. In other
circumstances CDP should recover
automatically by restarting.

Initialization warning, module: [chars],

operation: [chars]: [chars]

A failure occurred during the initialization

of CDP. CDP will restart and this should
resolve the problem.

Termination warning, module: [chars],

operation: [chars]: [chars]

A failure occurred during CDP's

termination. In this situation CDP should
recover automatically.

An entry has been removed from the CDP

neighbors table. Notification of deleted CDP
CDP Neighbour [chars] on interface [chars] neighbors requested through 'cdp log
has been deleted, remote interface [chars] adjacency changes'.

New CDP neighbor [chars] detected on

interface [chars], remote interface [chars]

A new entry has been added to the CDP

neighbors table. Notification of new CDP
neighbors requested through 'cdp log
adjacency changes'.

[chars] - [dec]: [chars]

Error in cem operation.

[chars] - [dec]: [chars] ([hex])

Error in cem operation.

[chars] - [dec]: [chars] ifh=[hex] rc=[hex]

Error in cem operation.

[chars] - [dec]: [chars] ([dec])

Error in cem operation.

[chars] - [dec]: [chars] ([chars])

Error in cem operation.

[chars] - [dec]: [chars] (rc = [hex])

Error in cem operation.

Wavl deletion failed for [chars]. Please

restart the g_spa process

Due to wavl deletion failure, g_spa process

needs to be restarted. A very rare event,
the process restart will take care of this.

[chars]. Reason: ([chars])

An API or a function call in cem_class

process failed. First %s - Type of Error
Second %s - Reason

[chars] [chars] Initialization failed - Reason Failure occured during the initialization of
[chars]
CEM component Logs the reason for failure.

Calloc failed for stats array. Please restart

the g_spa process

Due to memory allocation failure for stats

array, g_spa process needs to be restarted.

Inherited CEM params from class [chars]

attached to parent controller

Inherited values from the class attached to

the parent controller. If the parent
controller of the interface has a cem-class
attached, its values are applied, else
reverted back to default values.

Payload [dec] is not compatible with

Dejitter [dec] for interface [chars]. Value
ignored

A value in class attach onto interface or

controller not inherited.

[chars] [dec] is not in range [dec]-[dec] for A value in class attach onto interface or
interface [chars]. Value ignored
controller not inherited.
Payload [dec] is not multiple of 8*N
(N:channels) for interface [chars]. Value
ignored

A value in class attach onto interface or

controller not inherited.

CEMA Fatal Error: [chars]

An internal fatal error was detected in

CEMA module operation

CEMA Mismatch Error: [chars]

A process on the line card that manages a

SPA was restarted. As a part of restart, a
mismatch was detected between user
specified configuration and the actual
configuration of SPA hardware.

CEMA Unsupported Feature Error: [chars]

A request was made for information on a

feature that is unsupported on the device
specified in the request. This error may
affect the usability of the device if the
feature is necessary for proper operation.

CEMA Internal Error: [chars]

An internal error was detected in CEMA

module operation

Failed to [chars] the generation of AIS for

[unsigned int] local MEPs as a result of
configuration or network change: [chars]

A failure occurred when attempting to

generate or disable AIS messages for a
number of local MEPs. This event was
triggered by either a change within the
network (e.g. to a remote MEP or to an EFP
state) or a change in configuration (e.g. a
CoS bit or AIS transmission interval
change). This may result in AIS being sent
at the wrong level or interval, no AIS being
sent at all, or AIS being sent when it should
not be. If the error persists, CFM may not
operate correctly.

An error occurred while starting or

Failed to start AIS generation timer in
restarting the AIS generation timer. No
[chars]%s[chars]%s with timeout [unsigned further AIS messages will be sent for
int]ms, jitter [unsigned int]ms: [chars]
MEPs/EFPs in this service/bridge domain.

Failed to start CCM generation timer in

domain [chars], service [chars] with
timeout [unsigned int]ms, jitter [unsigned
int]ms: [chars]

An error occurred while starting or

restarting the CCM generation timer. No
further CCM messages will be sent for
MEPs in this domain/service.

Failed to [chars] for [unsigned int] of

[unsigned int] local MEPs as a result of
[chars]; first error: [chars]

A failure occurred when attempting to

generate or disable CCM messages for a
number of local MEPs. This may result in
outgoing CCM messages containing
incorrect flags, interface state information
or CoS bits, no CCMs being sent at all, or
CCMs being sent when they should cease.
If the error persists, CFM may not operate
correctly. The regeneration event that has
failed was triggered by the protocol event
mentioned in the message description.

A failure occurred when attempting to send

CCM messages for a number of local MEPs,
some CCMs will not have been sent. If the
error persists, CFM may not operate
Failed to send CCMs for [unsigned int] local correctly. The failure was triggered by the
MEPs. First failed MEP - domain: [chars],
protocol event mentioned in the message
service: [chars], MEP ID: [unsigned int],
description. Further errors of this nature
interface: <<CH[hex]>>, error : [chars]
will be supressed for the next 30 minutes.

[chars] failed to apply new CFM

Configuration. It is likely that the protocol
will not operate as intended: [chars]

The CFM Global Manager or the CFM

Daemon on the specified node was unable
to enact a set of valid configuration
changes. Future configuration changes may
be adversely affected and the protocol is
likely not to operate as intended. The
problem could be caused by a system
resource issue.

Error processing [chars] changes for

[unsigned int] interfaces. Outgoing CCMs
may contain incorrect information: [chars]

CFM was unable to update internal state

following a change to an interface attribute
on a group of interfaces.

A notification from another part of the

system indicates that some operation
should be performed on an interface that
does not exist in Interface Manager. The
CFM Daemon's internal state will be
updated in accordance with the requested
operation, but no Maintenance Points will
be created on the affected interface. This
Received new configuration for an interface indicates an inconsistency between the
that is not expected to exist. Configuration Interface Manager and other infrastructure
operation: [chars]. Interface <<CH[hex]>> components.

Failed to create Maintenance Points

following a change to CFM configuration:
[chars]

CFM encountered an error while trying to

create new Maintenance Points and
retrying the operation has not resolved the
problem. This situation could indicate that
system resources are low. The operational
state of CFM will now be out-of-sync with
configuration as some Maintenance Points
will not have been created.

Failed to update MP config on interface

<<CH[hex]>>: [chars]

CFM encountered an error while trying to

delete and/or create Maintenance Points on
the specified interface and retrying the
operation has not resolved the problem.
This situation could indicate that system
resources are low. The operational state of
CFM will now be out-of-sync with
configuration as some Maintenance Point
deletes and/or creates have failed.

The creation of an SLA operation failed:

[chars]

CFM encountered an error while trying to

create new SLA operations. This situation
could indicate that system resources are
low. The operational state of CFM will now
be out-of-sync with configuration as some
SLA operations will not have been created.

CFM encountered an error while trying to

create new cross-check MEPs This situation
could indicate that system resources are
low. The operational state of CFM will now
Failed to create cross-check MEPs following be out-of-sync with configuration as some
a change to CFM configuration on interface cross-check MEPs will not have been
<<CH[hex]>>: [chars]
created.

Failed to delete [chars] object (ID [chars])

from the [chars] database, because the
object wasn't found

A user requested that an object be

removed from a database in which it was
not present. The process should recover
from this event, but it may indicate an
internal inconsistency which could cause
other problems.

An internal inconsistency was identified

while performing some operation on the
database. The process will attempt to
recover a consistent state, and should be
An error condition that indicates an internal able to continue operating. It is possible
inconsistency in a database was
that some parts of CFM may become out of
encountered: [chars]
sync.

Failed to perform [chars] operation on

[chars] lock in database: [chars]

An error was encountered while trying to

perform an operation on a lock. The thread
will continue without retrying the
operation. In most cases, no further
adverse behaviour should be observed.

CFM EA failed to process the new CFM

configuration on interface <<CH[hex]>>.
[chars]

CFM encountered an error while trying to

update the hardware packet handling after
a configuration update, and retrying the
operation has not resolved the problem.
This situation could indicate that system
resources are low, or a problem with
another part of the system. It is possible
that CFM will not receive packets that it
should be processing, or packet processing
may operate more slowly than expected.

CFM encountered an error while attempting

to schedule a retry for a failed operation.
The operation will not be retried. It is likely
that some Maintenance Points will not be
Failed to schedule a retry attempt using the created. This may indicate that system
Event Connection Manager library: [chars] resources are low.

Failed to retrieve the 802.3 Ethernet Link

OAM loopback state of some physical
interfaces. [chars]

CFM encountered an error while trying to

retrieve the 802.3 Ethernet Link OAM
loopback state of some physical interfaces,
in order to report the state correctly in
outgoing CCMs. This situation could
indicate a problem in the Ethernet Link
OAM daemon (elod) process, or that
system resources are low, or a problem
with another part of the system. It is likely
that the interworking state reported in
outgoing CCM messages will be incorrect.

CFM was unable to process a change in

interface encapsulation. As a result packets
sent by CFM may be sent with the incorrect
encapsulation. This indicates that either
Failed to process an encapsulation change. system resources are low, or that there is
Error: [chars]
an internal problem with CFM.

Failed to process engine timer: [chars]

An error occurred while processing the

engine thread timer wheel. This may cause
CCMs not to be sent, or peer MEPs not to
time out after the configured loss time.

Failed to generate a fault notification for a

local MEP - domain: [chars], service:
[chars], MEP ID: [unsigned int], interface:
<<CH[hex]>>: [chars]

An error was encountered when trying to

generate a fault notification for a local MEP,
as a result of a defect detected from a peer
MEP. This will mean that the corresponding
SNMP trap will not be raised. If the error
persists, CFM may not operate correctly.

The CFM debug library was notified about

the creation of a debug item in SysDB
which had an unexpected number of filter
parameters. The corresponding debugging
flag has not been enabled in CFM, which
Failed to enable the requested debugging. may lead to some debug not being printed
Invalid debug filter string: [chars]
as expected.

Failed to communicate with the L2FIB

Infrastructure: [chars]

The L2FIB Infrastructure reported an error

which could not be handled. The operation
will not be retried - the internal state of
CFM may not match the global system
state.

The LWM subsystem indicated an error

when trying to send a message between
threads in the CFM Daemon, which could
Failed to send a [chars] LWM message from not be handled. The operation will not be
[chars] to [chars] thread in the CFM
retried - the internal state of CFM may not
Daemon - message type: [chars]: [chars]
match the global system state.

Attempt to delete [unsigned int] MEPs

while some MEPs are having CCM
generation enabled/disabled.

The CFM MA tried to delete a number of

MEPs whilst some of those MEPs were
scheduled to have CCM generation enabled
or disabled. The CCM generation batches
have been cleared, which may cause an
inconsistency between CFM's internal state
and the requested configuration.

Failed to create Maintenance Point [chars]

in the database. Error [chars]

The CFM MA was unable to create a new

Maintenance Point in the database. This
indicates that either system resources are
low, or that there is an internal problem
with CFM. The set of Maintenance Points
created by CFM will not match the
requested configuration.

CFM is unable to allocate [unsigned int]

bytes.

The system is low on memory.

CFM is unable to allocate memory.

The system is low on memory.

Failed while processing packet in [chars]:

[chars]

An error occurred unexpectedly while

calling the packet management
infrastructure to handle a CFM packet
during packet send.

The CFM MA attempted the maximum

number of retrys for a failed operation. The
operation will not be retried again. The MA
will attempt to recover, but it is possible
that the Maintenance Points created will
Reached the maximum number of retry
not match those specified in configuration.
attempts for [chars]. Failed updates for
The problem could be caused by a system
[unsigned int] interfaces will not be applied resource issue.

Failed to update [unsigned int] interface

states in CCMs.

There were insufficient system resources to

provide the CFM Protocol Manager with
interface state updates. The state update
notifications will not be delivered, and the
interface states in Continuity Check
Messages will be incorrect for the affected
interfaces. Other CFM functionality is
unaffected.

Failed to schedule Maintenance Point

[chars] processing for [chars]. [chars]

The CFM MA failed to schedule an

operation required to modify Maintenance
Point configuration for an interface. This is
likely to be a system resource issue.

Failed to restart AIS expiry timer for MEP in

domain [chars], service [chars], local MEP
ID [unsigned int] on interface
<<CH[hex]>>: [chars]

An error occurred while restarting the AIS

expiry timer for the local MEP specified in
the error message. This could cause a
received AIS or LCK signal to be incorrectly
reported as having stopped.

Failed to allocate memory for batched

delete of unused bridge domains.

Following a configuration change, CFM no

longer needs to retain information about
some bridge domains but has failed to
delete the information from its database.
The process will continue to operate
correctly but is using more memory than is
necessary.

An error occurred while processing a

Failed to process CCM received by MEP in received CCM message - the error string
domain [chars], service [chars], local MEP gives more details. This error is not caused
ID [unsigned int] on interface
by malformed or invalid packets. If the
<<CH[hex]>>, CCM received from [chars]: error persists, CFM may not operate
[chars]
correctly.

CFM recieved a configuration update that

can not be processed because it is not
Configuration change requested is
consistent with the current internal state.
inconsistent with the current state: [chars] The requested update will be rejected.

Failed to shut down interface

<<CH[hex]>>: [chars]

A failure occurred when attempting to shut

down an interface using EFD after a fault
condition was detected by one of the local
MEPs on the interface. This event was
triggered by either a change within the
network (e.g. detecting a defect with a
remote MEP) or a change in configuration
that enabled EFD on a service. This will
result in the interface remaining up, when
it should be shut down.

A failure occured when attempting to

update E-LMI. This event was triggered by
either a change within the network (e.g. a
remote MEP going missing), a change to
local MEP or cross-check configuration or ELMI starting up and requesting information.
The result is that E-LMI will not have the
Failed to update E-LMI with EVC and remote most up to date information to report to
UNI details: [chars]
the CE device.

Set: CFM PDUs cannot be sent from the

interface mentioned in the message, for
one of the following reasons: - The
interface has no encapsulation configured.
- The interface has a complex
encapsulation configured, which is not
supported in conjunction with CFM.
Complex encapsulations include: Matching on source or destination MAC
addresses - Matching on payload ethertype
- Matching on VLAN tags using the 'any'
keyword. In these cases, it cannot be
determined how to format the Ethernet
header for sending CFM PDUs, and hence
CFM is not supported in these scenarios. The interface encapsulation is such that
more than 2 VLAN tags are needed. Clear:
the error condition no longer holds; either a
supported encapsulation has been
configured and CFM PDUs can be sent, or
all CFM Maintenance Points have been
[chars]: [chars] on Interface <<CH[hex]>> removed and CFM PDUs no longer need to
- CFM [chars] on this interface
be sent.

Conflicting encapsulation for sending

[chars] packets on [chars]: [chars]

There is a conflict between the interface

encapsulation and rewrite configuration
and the CFM configuration. AIS or CCM
packets cannot be sent from the interface
or MEP mentioned in the message, for one
of the following reasons: - CoS bits are
configured, but there are no VLAN tags in
which to carry them in the packet. - An
attempt is being made to send packets
inwards, but the interface is not configured
in L2 mode. - The service is configured with
a number of tags to use when sending
packets, but either the packets are being
sent outwards, or the encapsulation has
fewer tags than the number specified.

Failed to notify SysMgr that [chars] is

exiting: [chars]

The specified process failed to notify the

system manager that it was exiting. In very
rare cases, this could result in the process
not being restarted when it ought to be.

Failed to initialize [chars]: [chars]%s

An error was encountered while the

specified process was initializing. The error
message contains details about the source
of the error.

Failed to restart loss timer for MEP in

domain [chars], service [chars], local MEP
ID [unsigned int] on interface
<<CH[hex]>>, peer MAC [chars], peer
MEP ID [unsigned int]: [chars]

An error occurred while restarting the loss

timer for the peer MEP specified in the
error message. This could cause the peer
MEP to incorrectly be timed out some time
later.

[chars] lost event: [chars]

The specified process failed to receive an

event that was sent to it.

Failed to manage the checkpointed state:

[chars]. [chars]

CFM encountered an error while trying to

maintain its checkpoint database. The
checkpoint database is used to manage
persistent MIB index values for accessing
Domains and Services over SNMP. If an
error was encountered then CFM has been
unable to guarantee that MIB index values
will be correctly maintained across process
restarts, and existing database objects may
have their MIB indices re-assigned.

Failed to manage the checkpointed state

for a single item: [chars]. [chars]

CFM encountered an error while trying to

maintain its checkpoint database, for a
single item in the database. The checkpoint
database is used to manage persistent MIB
index values for accessing Domains and
Services over SNMP. If an error was
encountered then CFM has been unable to
guarantee that MIB index values will be
correctly maintained across process
restarts, and existing database objects may
have their MIB indices re-assigned.

The CFM packet handling module has

detected that an AIS signal has changed
(started or expired), but has failed to notify
the management module. As a result, the
Failed to relay information about [chars] for proper handling for this event (eg
MEP in domain [chars], service [chars],
generating log messages) will not take
local MEP ID [unsigned int]: [chars]
place.

The CFM packet handling module has

detected that a peer MEP has timed out (ie
that no CCM has been received for the loss
Failed to relay information about loss of
time), but has failed to notify the
connectivity for MEP in domain [chars],
management module. As a result, the
service [chars], local MEP ID [unsigned int], proper handling for this event (eg
peer MEP ID [unsigned int], peer MAC
generating log messages and SNMP traps)
[chars]: [chars]
will not take place.

Failed to decode [unsigned int] offload

[chars] messages - first error: [chars]

An error occurred while attempting to

decode a batch of offload messages which
had been received. The source of the error
is the offload infrastructure. The received
messages will be dropped as a result of this
error.

Failed to decode [unsigned int] ethernet

packets. First failed interface:
<<CH[hex]>>, first error: [chars]

An error occurred while attempting to

decode a batch of ethernet frames which
had been received. The source of the error
is the Ethernet Packet Infrastructure. The
received packets will be dropped as a
result of this error. This could cause peer
MEPs to time out, or ping/traceroute
operations to fail.

A packet containing an unexpected TLV

was received on the given interface. The
packet has been processed normally and
the unexpected TLV has been ignored. This
message indicates that the device from
which this packet originated is creating
packets which deviate from the expected
A packet of type [chars] was received on
format of packets of this type according to
interface <<CH[hex]>> from source MAC the IEEE specification (IEEE 802.1ag-2007
[chars] in domain [chars] (level [unsigned or ITU-T Y.1731 02/2008). While the
int]) service [chars], with an unexpected
message is harmless, the user may wish to
TLV of type [unsigned int]. The unexpected check the standards compliance of the
TLV was ignored and the packet was
remote device, which is indicated by the
processed.
provided source MAC address.

Failed to re-register to receive packets on

[unsigned int] interfaces and to offload
CCM processing for [unsigned int]
interfaces. First error: [chars]

After a system event, CFM was requested

to re-register to receive packets on all the
interfaces where it is enabled, and to reprogram the offload service for sending
and receiving CCMs for all offloaded MEPs,
but one or both of these operations failed
for some interfaces. CFM packets may no
longer be sent and/or received on the
affected interfaces.

The local MEP for a Satellite Fabric Link

could not be created. This means CFM will
not run over the Satellite Fabric Link, and
Failed to create the local MEP on nV
so will be unable to detect Satellite Fabric
Satellite Fabric Link <<CH[hex]>>: [chars] Link failures.

The local MEP for a Satellite Fabric Link

could not be removed. The MEP, Service,
Failed to remove the local MEP on nV
Domain will still show in CFM manageability
Satellite Fabric Link <<CH[hex]>>, service commands despite the Satellite Fabric
[chars] (domain [chars]): [chars]
Link's removal.

The local MEP for a Satellite Fabric Link

could not be removed. The MEP, Service,
Domain will still show in CFM manageability
Failed to remove the local MEP on nV
commands despite the Satellite Fabric
Satellite Fabric Link <<CH[hex]>>: [chars] Link's removal.

An error occurred while processing a

received SLM message, resulting in a
failure to send a SLR reply. - the error string
gives more details. This is a problem
Failed to send SLR in response to SLM
because the SLR is needed in order for the
received by MEP in domain [chars], service sender to correctly calculate packet loss
[chars], local MEP ID [unsigned int] on
measurements. This error is not caused by
interface <<CH[hex]>>, SLM recieved
malformed or invalid packets. The SLM test
from [chars]: [chars]
session will now be invalid.

Internal SPIO Error : [chars]

SPIO PD software error has occured. Exact

reason given by the error string

Some received CCMs have not been

counted by the CCM error counters domain: [chars], service: [chars], MEP ID:
[unsigned int], interface: <<CH[hex]>>

The CCM counters displayed in 'show

ethernet cfm peer meps' may have missed
some CCMs. This is due to a transient issue
for offloaded MEPs. Counters will continue
to be updated correctly after this message
is seen.

One or more of the CCM error counters

have wrapped - domain: [chars], service:
[chars], MEP ID: [unsigned int], interface:
<<CH[hex]>>

The CCM error counters displayed in 'show

ethernet cfm peer meps' are only able to
store a value of up to 4294967295. One or
more of the error counters have gone over
this limit and the counter has wrapped
around to zero.

CFM-D was unable to determine whether

[unsigned int] satellites were up during
initialization.

CFM was unable to ascertain the status of

one or more satellites within 5 seconds of
starting up. This means CFM will not run
over satellite links to these satellites, even
though they may be up.

[chars] on local MEP in domain [chars],

service [chars] with MEP ID [unsigned int]
on interface <<CH[hex]>>[chars]

A new AIS or LCK signal was received by a

local MEP or an existing signal expired. This
message appears because the service to
which the local MEP belongs has AIS
logging configured.

Peer MEP error change: [chars] - domain

[chars], service [chars], local MEP ID
[unsigned int], local interface
<<CH[hex]>>, peer MEP ID [unsigned int],
peer MAC address [chars], errors [chars]

A change in the errors reported by a CCM

message from a peer MEP was detected.
This message appears because the service
which the local MEP belongs to has
continuity-check error change logging
configured.

An interface was shut down or brought up

by a local MEP after a fault condition was
detected or cleared. The action is taken
because the service to which the local MEP
Interface <<CH[hex]>> [chars] by MEP ID belongs has EFD configured; this message
[unsigned int] in domain [chars], service
appears because the service has EFD
[chars]
logging configured.

A CCM message was received from a new

peer MEP, or a previously-known peer MEP
Peer MEP change: [chars] - domain [chars], timed out (i.e. its configured loss threshold
service [chars], local MEP ID [unsigned int], was exceeded). This message appears
local interface <<CH[hex]>>, peer MEP ID because the service which the local MEP
[unsigned int], peer MAC address [chars], belongs to has continuity-check state
errors [chars]
change logging configured.

Resetting CFM shared memory data:

[chars]

The CFM shared memory window is being

reset. All shared memory data will be lost.
This means that all per-interface, per-MEP
and per-peer-MEP counters are reset to
zero.

More than the supported number of TLVs

were found while processing [chars] (total
length [unsigned int])

While processing a received CFM PDU,

more than the supported number (32) of
TLVs were found. This is very unlikely to
occur in normal operation, and may
therefore indicate a denial-of-service
attack.

A change in the cross-check status of a

peer MEP was detected. This may indicate
an expected peer MEP configured by crosscheck is missing, or a CCM message has
been received unexpectedly from a peer
MEP which was not configured for crossCross-check error change for local MEP in check, or that one of the above errors has
domain [chars], service [chars] with MEP ID been cleared. This message appears
[unsigned int] on interface <<CH[hex]>> because the service which the peer MEP
for configured cross-check MEP ID
belongs to has cross-check error change
[unsigned int][chars]: [chars]
logging configured.

In the initialization of the DOT1AG MIB DLL

an error occurred while attempting to
register for debugging. Consequently there
will be no debug output from the DOT1AG
MIB DLL, retrieval of elements of the MIB
should be unaffected, but any issues with
MIB retrieval may be hard to diagnose. The
error message should point to a more
Unable to register for DOT1AG MIB debug. precise reason, possibly indicating an out
No further debugging will occur: [chars]
of resource issue.

In the initialization of the DOT1AG MIB DLL

an error occurred while trying to set up a
Unable to set up
filtered interface table for stack entry
Dot1agCfmStackEntryTable filtered view.
lookups. As such, items in the
Items in the Dot1agCfmStackEntryTable will Dot1agCfmStackEntryTable will not be
not be accessible: [chars]
accessible via SNMP requests.

In the initialization of the DOT1AG MIB DLL

an error occurred while trying to enable
Unable to register for SNMP traps. Traps will SNMP trap support. No traps will be sent
not be sent regardless of trap events
until the mibd_interface process is
occurring: [chars]
restarted and this registration succeeds.

Error receiving an event: [chars]. The

cHDLC EA process will restart

An error occured in the event loop. The

process will restart which should recover
the situation.

Failure during initialization of the [chars].

Error [chars]. The cHDLC EA process will
restart

A failure occured during the initialization of

the process. The process will restart which
should recover the situation.

A batch from IM contained multiple

notifications for a single interface. This
<<CH[hex]>>: Multiple [chars]
should not occur but the situation has been
notifications received in a single batch from recovered successfully by the cHDLC EA.
IM
No problems should be seen as a result.

An error has occured resulting in the

interface state being UP, and the line state
being DOWN on interface <<CH[hex]>>.
Because keepalives are disabled the line
will never come up. The situation may be
resolved by shutting and no shutting the
interface, or enabling keepalives.

If keepalives are disabled and certain errors

occur then the interface and line state can
end up being out of step. Without
keepalives enabled, SLARP has no way to
recover by discovering the correct line
state, so user intervention is required for a
chance of recovery.

Startup of the cHDLC Socket feature has

unexpectedly failed: [chars]

The cHDLC socket feature unexpectedly

failed to be started by sysmgr. This may
mean that processes which use cHDLC
sockets to send and receive packets will be
unable to do so, and may not be working
correctly. Symptoms would include loss of
SLARP keepalive packets causing the line
state to go down, loss of CDP packets and
loss of LACP packets on cHDLC
encapsulated interfaces.

Error receiving an event: [chars]. The

cHDLC MA process will restart

An error occured in the event loop.The

process will restart which should recover
the situation.

Failure during initialization of the [chars].

Error [chars]. The process will restart

A failure occured during the initialization of

the process. The cHDLC MA process will
restart which should recover the situation.

Failure during the handling of an event

received from the packet thread in [chars]: A failure occured whilst handling an event
[chars].
received from the packet thread.

Failure during the handling of a packet

event in [chars]: [chars].

A failure occured whilst handling a packet

event.

Failure during a cross thread operation in

[chars]: [chars].

A failure occured during thread handling.

A batch from Interface Manager contained

multiple notifications for a single interface.
This should not occur but the situation has
<<CH[hex]>>: Multiple [chars]
been recovered successfully by the cHDLC
notifications received in a single batch from MA. No problems should be seen as a
Interface Manager
result.

Error receiving an event: [chars]. The

cHDLC socket server process will restart

An error occured in the event loop. The

process will restart which should recover
the situation.

Failure during intialisation of the

chdlc_socket process - specifically [chars].
Error: [chars]. The process will restart

A failure occurred during the initialisation

of the cHDLC socket process. The process
will restart which should recover the
situation.

A packet manager corruption has been

reported and the cHDLC Socket process has
failed to cleanup to recover from the
problem. The process will exit and be
Unable to handle pakman corruption error: automatically restarted to recover from this
[chars]. chdlc_socket process restarting
situation.

Could not register for debug events :

[chars]

There was an error registering the cHDLC

Netio debug with the debug library. No
debug will be available for the cHDLC Netio
DLLs.

Encapsulation of HDLC packet failed.

Packet type-code [hex]

The encapsulation of an HDLC packet failed

for the network protocol with the ethernet
type code specified. The packet has been
dropped.

Could not register with tracing

infrastructure: [chars]

An attempt to register with the tracing

infrastructure failed. This will mean that
tracing for the cHDLC Netio DLLs will not be
available.

[chars]

A high severity error has occurred in PLIM

FPGA. This might result in the PLIM being
reset. %s - error message

Error mapping to SPA bridge controller

configuration buffer

An error has occurred in the Extended Flow

Control Manager. EFCM was unable to map
shared memory for debug.

Error opening SPA bridge controller

configuration buffer.

An error has occurred in the Extended Flow

Control Manager. EFCM was unable to open
shared memory for debug.

Unable to set extended flow control

calendar entry : bay([dec]) interface
handle([hex]), [chars]

An error has occurred in the Extended Flow

Control Manager. An attempt to set an
entry in the Flow Control calendar failed.
This error indicates that messaging
between the SPA process and the Jacket
process failed.

SPA client initialization failed during

extended flow control calendar
initialization, [chars]

An error has occurred in the Extended Flow

Control Manager. An attempt to set an
entry in the Flow Control calendar failed.
This error indicates that messaging
between the SPA process and the Jacket
process failed.

An error has occurred in the Extended Flow

Control Manager. This is caused by an out
Invalid parameters while setting extended of bounds Flow Control channel number or
flow control manager entry. Channel [dec] bay number trying to be used during the
bay [dec]
configuration of Flow Control for the SPA.

Unexpected error has lead to an incoming

message being dropped: [chars]

An incoming control message could not be

fully processed. The node ID corresponding
to the sender of this message could not be
established. The error message string may
provide further information as to the nature
of the problem.

Checkpoint data for this connection (id

%hu) has invalid id (%hu)

The Checkpoint table contained

unexpected data. This is likely to indicate
checkpoint memory corruption.

Failed to save Checkpoint sequence

information for connection [chars]

The client failed to save its own sequence

data to Checkpoint. If the process restarts
before the save is successfully retried,
remote clients may get out of sync, and
data loss could occur.

The client failed to save data to

Checkpoint. If the process restarts before
Failed to save Checkpoint entry [hex]/[hex] the save can be retried, then data loss
on connection [chars]
could occur.

Duplicate Checkpoint entry for ID %hu on

node [hex]

When reloading the list of known nodes

from checkpoint, a duplicate entry was
encountered. This is unexpected, and likely
indicates a software fault, but is otherwise
harmless. The duplicate entry has been
removed and the process should continue
to operate as expected.

CPP [dec] [chars] memory recovered [dec] percent depleted

Exmem resource cross under its threshold

CPP [dec] [chars] memory low - [dec]

percent depleted

Exmem resource cross over its threshold

Reason of failure: [chars]: Err=[hex]

The process is exiting due to a failure in

CPP Infra Stats Block Service.

Init failure at [chars]:[dec], sub-error:

[chars], error-code: [dec]

An error occurred in CPP TCAM RM which

involves exiting the process.

Message delivery failed at [chars]:[dec]

sub-error: [chars] error-code: [dec]

Unable to send a message to the CPP TCAM

RM server.

Nonfatal error: [chars]: Err=[dec]

This is a error message in the CPP TCAM

RM to indicate anomalies which are not
FATAL. Some of the messages may indicate
a failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temporary situation is resolved.
*RECUR*

Info: [chars]

This is an informational message in the CPP

TCAM RM.

CPP [dec] microcode crashdump creation

completed

CPP HA process has completed crashdump

creation.

CPP [dec] failure [chars] detected

A CPP HA failure has been detected.

CPP [dec] fault:[chars] det:[chars] class:

[chars] sev:[chars] idx:[dec] cppstate:
[chars] res:[chars] flags:[hex] cdmflags:
[hex]

A CPP HA failure has been detected.

CPP [dec] unresolved fault detected,

initiating crash dump.

A CPP HA has detected unresolved fault.

CPP [dec] fault:[chars] det:[chars] class:

[chars] sev:[chars] idx:[dec] cppstate:
[chars] res:[chars] flags:[hex] cdmflags:
[hex]

A CPP HA fault has occurred.

CPP [dec] initialization failed - [chars]

([hex])

A CPP HA initialization failed.

CPP [dec] CDM not running.

A CPP HA has detected that CDM is not

running.

Failed to cleanup: ([chars]).

A function failed to cleanup.

[chars] encountered an error

A process encountered error.

Failed to initialize: ([chars]).

A function failed to initialize.

packet will be dropped due to its length

([unsigned int]) exceeds fabric limit
([unsigned int])

The client is requesting to set packet

length to a value that exceeds CRS fabric
limit. Such a packet will be dropped. This
may be caused by an internal software
error or by the router's receiving of
malformed packets.

The chain build function failed because

'[chars]' (error: [chars])

The software forwarding support for

IEEE802.1Q VLANs was unable to set up an
interface. Software forwarding VLAN
functionality on the affected node may be
impaired.

The software forwarding support for

IEEE802.1Q VLANs was unable to process a
message sent to a particular interface
because the interface does not exist in
NetIO. Software forwarding VLAN
functionality on the affected interface may
be impaired. The interface can be
determined from its handle with
The Netio IDB associated with handle [hex] <CmdBold>show im chains ifhandle
could not be found
[handle]<noCmdBold>.

Unable to create the protocol registries

during capsulation initialization

The 802.1Q NetIO component could not

necessary data structures during its
initialization. Software forwarding VLAN
functionality on the affected is likely not to
work.

802.1Q Netio failed to register the

dot1q_ether subblock (error: [chars])

The software forwarding support for

IEEE802.1Q VLANs was unable to initialise
on the specified node. Software forwarding
VLAN functionality on the affected is likely
not to work.

The 802.1Q NetIO component encoutered

an error during trace buffer initialization.
A error occurred during trace initialization, This is likely to cause VLAN interface setup
err: [chars]
to fail.

The chain unbuild function failed because

'[chars]' (error: [chars])

The software forwarding support for

IEEE802.1Q VLANs was unable to clean up
an interface. Forwarding should not be
affected.

An error occurred during debug

initialization (error: [chars])

The 802.1Q NetIO component encoutered

an error during debug initialization. This is
likely to cause VLAN interface setup to fail.

Unsupported NetIO devctl code ([dec])

received

The 802.1Q NetIO component received an

unexpected message. The message has
been ignored. This may indicate that there
is a version mismatch among the VLAN
components.

802.1Q NetIO termination failed because

'[chars]' (error: [chars])

The software forwarding support for

IEEE802.1Q VLANs was unable to clean up.
Forwarding should not be affected.

[chars] Reason:[chars]

TDatapath FPGA API generated errors.

[chars]

TDatapath FPGA API generated errors.

driver manager: service degrading error,

reason = [chars]

Driver manager encountered an error that

would lead to degraded service.

Driver manager: init. error encountered,

reason=[chars]

Driver manager encountered an error and

is not able recover frm it. A reason text will
be supplied. Call support with this text.

Driver manager: memory allocation error

for <%zd> bytes

Driver manager encountered a fatal

memory allocation error

[chars]: Tuple read failed with error [hex]

[chars]

An error occured when trying to read the

tuple from sysdb.

dwdm: srlg debug init got failed with code

[chars], [dec]

This error will not cause any functional

impact.Only log creation and reporting
won't be available.

dwdm: service degrading error, reason =

[chars]

The dwdm encountered an error that would

lead to degraded service.

dwdm: an internal error encountered,

reason = [chars]

dwdm encountered an internal error and an

attempt to recover from this condition
failed . Possible reasons can be the inability
to find node-id.

dwdm: this function <[chars]> is not yet

implemented

dwdm, a function was not implemented.

Port id: [chars], Forced Maintenance:

[chars], Reason: [chars]

If Forced Maintenance has started at a port,

it means that the port was put into
Transport Admin State of 'maintenance'
when this activity was actually disallowed
for it. Forced Maintenance ends when,
either maintenance at the port is allowed
again by the administrator, or when the
Transport Admin State is changed back to
some other rather than 'maintenance'.

Port id: [chars], [chars]

When optical layer maintenance for an

interface is disabled by the administrator,
an hourly syslog notification is logged
regarding this, until maintenance is
enabled back again. One should not put
the port into OOS-MT state when
maintenance is disabled, otherwise it will
lead to a forced maintenance activity and
there might be loss of traffic.

Port id: [chars], The number of SRLGs for

this port is too high - only the first [dec]
have been recorded

Maximum 100 SRLGs can be configured per

DWDM port at the CRS. If some application
like CTC has more than this number to
configure, it indicates this situation by
configuring the 101st value with a positive
integer. The above ios_msg gets logged in
this scenario.

Cleared counters on [chars]

Counters on a dwdm controller has been

cleared by the user. This message is for
information only.

Practive protection event injected. Start

Port [dec] number of Ports [dec] Event
[dec] Value [dec]

This is for information that g709_api has

been used to inject Proactive protection
event with above mentioned attributes.

[chars] Wavelength Channel [dec] on

[chars]

DWDM Controller has provisioned optics to

[HW Default | Configured | GMPLS
Signaled] wavelength.

DWDM Controller Interface owner has lost

contact with GMPLS Client. The controller
shall continue to operate on the existing
wavelength, resync to happen after
GMPLS Signaled Wavelength Channel [dec] reconnect with GMPLS Client. This is an
is stale on [chars]
informational message.

Detected multiple interface types within

the Virtual Machine. Mixed interface types
are currently not supported in IOS XRv.

Virtio and E1000 drivers cannot both be

configured for interfaces on the hypervisor.
Some or all of the interfaces may not be
enabled and pass traffic as a result of this.

Initialization of dynamic-nic failed, return

code [dec].

The SPP node dynamic-nic has failed to

initialize properly.

Failed to allocate [dec] bytes from [chars]

([chars])

The process failed to allocate memory.

Most likely, all system memory has been
allocated already.

Failed to lock mutex

The process failed to obtain a software

mutex lock. Software mutex are used to
protect certain operations from being
executed simultaneously by concurrent
processes. This indicates a software error
which could lead to data corruption and
loss of traffic.

Failed to unlock mutex

The process failed to obtain a software

mutex unlock. Software mutex are used to
protect certain operations from being
executed simultaneously by concurrent
processes. This indicates a software error
which could lead to data corruption and
loss of traffic.

[chars] (size [hex] addr [hex]) - [chars]

The process could not map the egress asic

SDRAM into its memory space.

[chars]: error [hex]

The egress queueing asic was reset, but

could not be reconfigured. This may result
in partial or complete loss of functionality
of the asic.

Failed to open shared memory window

[chars] ([chars])

The process failed to open the specified

shared memory window. This problem can
be caused by a lack of system memory.

Failed to free [chars] ([chars])

The process failed to free memory. This is

likely a symptom of software corruption.
The system may be in an unstable
condition. The software failed to free
memory, and this can eventually lead to an
out-of-memory condition.

MQS counter utilization [dec] exceeds the

high threshold of [dec]

The multicast counter utilization has

exceeded the high threshold. This may
impact the delay and/or jitter of multciast
traffic egressing out of this line card. The
maximum counters available are 2048.

Failed to [chars] ([chars])

The process failed to initialize a software

mutex. Software mutex are used to protect
certain operations from being executed
simultaneously by concurrent processes.
This indicates a software error which could
lead to eventual data corruption and loss of
traffic.

The process failed to register for mutex

revival. In the event of a software error
where another process would crash while
holding a shared mutex, this process would
not self-recover. This warning does not
cause any degradation in the router
operation. The warning simply means that
a particular error recovery mechanism will
Failed to register for mutex revival ([chars]) not be effective.

Failed to obtain platform info for [chars]

([chars])

The process failed to obtain information on

the specified shared memory window. This
will prevent proper initialization and
operation multicast feature. This indicates
a software error condition.

[chars]: reg [hex]

The E3EGRESSQ asic experienced an

interrupt, and will be reset. After reset,
normal operation should resume.

MQS max threshold [dec] is not in

supported limit (1 - 2048)

The new multicast counter max-threshold

is crossing platform supported limit.

MQS min threshold [dec] is not in

supported limit (1 - 2048)

The new multicast counter min-threshold is

crossing platform supported limit.

MQS max-th [dec] is lesser than current

min-th [dec]

The new multicast counter max-threshold

is lesser than current min-threshold.

MQS min-th [dec] is greater than current

max-th [dec]

The new multicast counter min-threshold is

greater than current max-threshold.

MQS counter utilization [dec] within the low The multicast counter utilization has eased
threshold of [dec]
off to below the low threshold.

[chars]: error [hex]

The ingress queueing asic was reset, but

could not be reconfigured. This may result
in partial or complete loss of functionality
of the asic.

[chars]: reg [hex]

The E3INGRESSQ asic experienced an

interrupt, and will be reset. After reset,
normal operation should resume.

[chars]: error [hex]

The egress queueing asic was reset, but

could not be reconfigured. This may result
in partial or complete loss of functionality
of the asic.

MQS counter utilization [dec] exceeds the

high threshold of [dec]

The multicast counter utilization has

exceeded the high threshold. This may
impact the delay and/or jitter of multciast
traffic egressing out of this line card. The
maximum counters available are 16384.

[chars]: error [hex]

The e5 egress queue driver encountered an

internal error. The router may/may not
continue to function normally.

[chars]: reg [hex]

The E5EGRESSQ asic experienced an

interrupt, and will be reset. After reset,
normal operation should resume.

MQS max threshold [dec] is not in

supported limit (1 - 16384)

The new multicast counter max-threshold

is crossing platform supported limit.

MQS min threshold [dec] is not in

supported limit (1 - 16384)

The new multicast counter min-threshold is

crossing platform supported limit.

MQS max-th [dec] is lesser than current

min-th [dec]

The new multicast counter max-threshold

is lesser than current min-threshold.

MQS min-th [dec] is greater than current

max-th [dec]

The new multicast counter min-threshold is

greater than current max-threshold.

MQS counter utilization [dec] within the low The multicast counter utilization has eased
threshold of [dec]
off to below the low threshold.

[chars]: error [hex]

The ingress queueing asic was reset, but

could not be reconfigured. This may result
in partial or complete loss of functionality
of the asic.

[chars]: reg [hex]

The E5INGRESSQ asic experienced an

interrupt, and will be reset. After reset,
normal operation should resume.

[chars], Failed to add feature for [chars],

err: [chars]\n

edge_l2fwd_rewrite failed to add specific

feature in FM.

[chars], Failed to del feature for [chars],

err: [chars]\n

edge_l2fwd_rewrite failed to delete specific

feature in FM.

[chars]: [chars] is not supported on E3

Linecards \n

The feature is not supported on E3

Linecards

[chars], Failed to read [chars] from FWD

MemMgr, err: [chars]\n

edge_l2fwd_rewrite failed to read adj

counters/PLU/TLU through FWD Memory
manager.

[chars],Failed to create gather index in

HFA\n

edge_l2fwd_rewrite failed to create gather

index in HFA

[chars],Failed to program [chars] ucast in

HFA\n

edge_l2fwd_rewrite failed to program

feature specific ucast in HFA

[chars],Unable to open connection with

HFA\n

edge_l2fwd_rewrite Connection open with

the HFA failed

[chars], Insert encap string failed for

Ifhandle=[hex] err:[chars]

edge_l2fwd_rewrite failed while removing

the encap string

[chars], Error while registering with

Forwarding Memory Manager

edge_l2fwd_rewrite Registration with the

forwarding Memmgr Failed !

[chars],PLU free failed, error:[chars]

edge_l2fwd_rewrite Failed to free PLU

though the forwarding Memory Manager

[chars], Failed to allocate memory for the

PLU Leaf

edge_l2fwd_rewrite Forwarding memory

module failed to allocate memory for the
PLU leaf

[chars],[dec],PLU write error:[chars]

edge_l2fwd_rewrite Failed while writing into

the PLU though the forwarding Memory
Manager

[chars], remove encap string failed

OI=[hex] err:[chars]

edge_l2fwd_rewrite failed while removing

the encap string

[chars], [dec] error, reason:[chars]

edge_l2fwd_rewrite Encap Resource

Manager Initialisation error

[chars],TLU free error:[chars]

edge_l2fwd_rewrite Failed to free TLU

through forwarding Memory manager.

[chars], Failed to allocate memory for the

TLU Leaf

edge_l2fwd_rewrite Forwarding memory

module failed to allocate memory for the
TLU leaf

[chars], Invalid TLU write size, TLU size:

[dec], Write Size:[dec]

edge_l2fwd_rewrite failed to write to TLU as

the write size is not less than the actual
TLU size

[chars],[dec],TLU write error:[chars]

edge_l2fwd_rewrite Failed while writing into

the TLU though the forwarding Memory
manager.

[chars],Uidb read failed - err: [chars]\n

edge_l2fwd_rewrite Uidb read failed

[chars],Uidb set failed for xconnid:[dec],

err: [chars]\n

edge_l2fwd_rewrite Uidb set failed

[chars], Failed to add mcast entry, err:

[chars]\n

edge_l2fwd_rewrite failed to add mcast

entry in XBMA.

[chars], Failed to connect to XBMA server,

err: [chars]\n

edge_l2fwd_rewrite failed to connect to

XBMA server.

[chars], Failed to del mcast entry, err:

[chars]\n

edge_l2fwd_rewrite failed to delete mcast

entry in XBMA.

[chars], Failed to initialize XBMA library, err: edge_l2fwd_rewrite failed to initialize XBMA
[chars]\n
lib.

\nassertion '[chars]' failed in [chars]

([chars]:[dec])

Assertion Failure.

[chars], Failed to delete [chars] for [chars]

in FAD

edge_l2fwd_table failed to delete l2fwd

lookup entry in FAD

[chars], Failed to initialize FAD, reason:

[chars]

edge_l2fwd_table FAD module failed to get

initialized.

[chars], Failed to insert lookup entry for

[chars] in FAD

edge_l2fwd_table failed to insert l2fwd

lookup entry in FAD

edge_l2fwd_table failed to program TCAM

[chars], Failed to program [chars] region in region in FAD. The region is specific to
FAD
feature(L2TPv3/VPLS etc)

[chars], Failed to program [chars] TCAM

format in FAD

edge_l2fwd_table failed to program feature

specific TCAM format in FAD layer.

[chars], Failed to update lookup entry for

[chars] in FAD

edge_l2fwd_table failed to update l2fwd

lookup entry in FAD

[chars], Failed to set [chars] feature config edge_l2fwd_table failed to set feature
in FM
specific config processing in FM.

[chars], Failed to allocate memory for the

PLU Leaf

edge_l2fwd_rewrite Forwarding memory

module failed to allocate memory for the
PLU leaf

[chars],[dec],PLU write error:[chars]

edge_l2fwd_rewrite Failed while writing into

the PLU though the Forwarding Memory
Manager

[chars],[dec] Table registeration failed !

Table type:[chars], direction:[dec]\n

edge_l2fwd_table failed to register the

memory requirement and populate the
memory handle

[chars], Failed to allocate memory for the

Table: [chars]

edge_l2fwd_rewrite Forwarding memory

module failed to allocate memory for the
Table

[chars], Failed to allocate memory for the

TLU Leaf

edge_l2fwd_rewrite Forwarding memory

module failed to allocate memory for the
TLU leaf

[chars],[dec],TLU write error:[chars]

edge_l2fwd_rewrite Failed while writing into

the TLU though the forwarding memory
manager

[chars], [dec] error, reason:[chars]

edge_l2fwd_table generic error

\nassertion '[chars]' failed in [chars]

([chars]:[dec])

Assertion Failure.

Sharq ENQ packet logic error occurred,

shq_enq_reg_debug_mux [hex]

Egress Queue Manager encountered a ENQ

packet logic error. Possible cause for this
error condition is a faulty hardware.

Failed to allocate memory for [chars]

System failed to allocate memory. It's likely

that the system is running low on memory.
Following are some reasons: 1) Failed to
allocate memory for Egressq client add. 2)
Failed to allocate memory for Egressq
mapping table. 3) Failed to allocate
memory for Queue leaky bucket limit table
Memory. 4) Failed to allocate memory for
Queue leaky bucket limit table memory. 5)
Failed to allocate memory for Group leaky
bucket limit table memory. 6) Failed to
allocate memory for Group leaky bucket
limit table memory. 7) Failed to allocate
memory for Port leaky bucket limit table
memory. 8) Failed to allocate memory for
PLIM Asic back pressure table memory.

Failed to allocate memory for [chars]

System failed to allocate memory. It's likely

that the system is running low on memory.
Following are some reasons: 1) Failed to
allocate memory for Egressq client add. 2)
Failed to allocate memory for Egressq
mapping table. 3) Failed to allocate
memory for Queue leaky bucket limit table
Memory. 4) Failed to allocate memory for
Queue leaky bucket limit table memory. 5)
Failed to allocate memory for Group leaky
bucket limit table memory. 6) Failed to
allocate memory for Group leaky bucket
limit table memory. 7) Failed to allocate
memory for Port leaky bucket limit table
memory. 8) Failed to allocate memory for
PLIM Asic back pressure table memory.

Failed to get backpressure map from Plim

ASIC [dec]. reason [chars]

Sharq driver invoke Plim ASIC dll to retrieve

the per port backpressure map but failed.

FCRAM BIST failed, channel: [dec], count:

[dec], error_addr: [hex]

Egress Queue Manager encountered a

FCRAM BIST failure error. Possible cause for
this error condition is a faulty hardware.

Egressq driver detected that packets were

Forward packets sent to unallocated egress sent to an Egressq queue which is
queue [dec]. (queue state: [chars], queue unallocated. These packets will not be
length: [dec] bytes, DFLT Q: [chars], HPQ: serviced and will remain in the queue until
[chars]), group [dec] (dflt group: [chars]), this queue is allocated and becomes
port [dec]
active, or asic reset or linecard reload.

Tor HW error: [chars]

Egress Queue Manager encountered a HW

error. This is a severe error and ASIC will be
reset by the driver.

[chars]

Egress Queue Manager encountered a HW

error. This is a severe error and ASIC will be
reset by the driver.

IMDR Mapping error: ([chars]# [dec])

[chars]

There is a discrepancy between the

egressq configuration before and after
IMDR. The egressq configuration after IMDR
should normally be the same as before.
This could indicate an internal software
error.

[chars] [chars] access error. [chars]

Egressq ASIC encountered a read or write

access error or its Host Processor Interface
block has gone down and come back up.
The access error is classified into two
classes - software or hardware. Hardware
access error refers to an error at the PCI
link used to connect the ASIC to the host
processor. Software access error refers to
the error, caused by a un-discovered
software bug, which makes software to
perform un-supported access to an ASIC
location, like writing to a read-only
location.

EgressQ detected packets sent to Illegal

queue (counter value [hex])

Egressq driver detected that packets are

sent to Q0, which is invalid queue.

EgressQ Stuck condition detected (PLIM

link [dec], link trained: [chars], Port [dec],
Group [dec], Queue [dec], Queue state:
[chars])

Egressq driver detects the queue stuck

condition (CSCsj48554). There is no packet
output from one or more of the PLIM links
and the queue length for related queue(s)
is building up.

ASIC Tor status: [chars]

Log the key asic registers when a queue

stuck condition was detected.

RLDRAM BIST test failed

Egress queueing ASIC encountered a

failure when doing BIST testing on its
external Redunced-Latency-DRAM
(RLDRAM). Possible cause for this error
condition is a faulty hardware.

Single Bit Error rate exceeded configured

high threshold value: <[chars]>

Egressq SBE rate has exceeded the

configured high threshold value. This is a
self healing error condition.

Packets sent to unallocated egress queue

[dec]. (queue size [dec] bytes)

Egressq driver detected that packets were

sent to an Egressq queue which is
unallocated. These packets will not be
serviced and will remain in the queue until
this queue is allocated and becomes
active. This situation should normally not
happen, but may possibly happen during
transient conditions when egress queue
information is being updated (for e.g. on
SPA OIR). During this brief time period, one
or few packets may be sent to an incorrect
queue.

Packets present in unallocated egress

queue [dec]. (queue state: [chars], queue
length: [dec] bytes, DFLT Q: [chars], HPQ:
[chars]), group [dec] (dflt group: [chars]),
port [dec]

Egressq driver detected that packets were

present in an Egressq queue which is
unallocated. These packets will not be
serviced and will remain in the queue until
this queue is allocated and becomes
active. This situation should normally not
happen, but may possibly happen during
transient conditions when egress queue
information is being updated (for e.g. on
SPA OIR). During this brief time period, one
or few packets may be sent to an incorrect
queue.

[chars]

This is an informational message in the

Egressq/Tor Driver to indicate an operation.

[chars]

This is an informational message in the

Egressq/Sharq Driver to indicate an
operation.

QDR BIST failed, [chars]

Egress Queue Manager encountered a QDR

BIST failure error. Possible cause for this
error condition is a faulty hardware.

EVM error : [chars] reason : [chars]

An internal error was detected when trying

to create EVM connection. It can fail during
following scenarios: 1) EDM
registration/connect/notify. 2) BAG's rule
registration failed.

Internal error : [chars] reason : [chars]

An internal error was detected. There are

several scenarios which can cause this
error condition. Error message describes
the cause. Some of these error conditions
are serious and result in driver process
restart, e.g. ASIC Init/remap, enable/disable
failure. Following are some of the reasons
for this internal error: 1) Obsolete API
usage, it can be caused due to
uncompatible component installed in the
system. 2) Interface creation failed due to
egressq port creation failure. 3) Can't map
Interface handle to egressq port, it could
be because of: a) Invalid interface handle
passed. b) Internal interface to port
mapping table is corrupted. 4) Egressq
ASIC reinitialization failed, this is an
irrecoverable situation, and Egressq driver
will be restarted. 5) Egressq Group/Queue
creation/ deletion failed. 6) ASIC enable
/disable failed.

Internal error : [chars] reason : [chars]

An internal error was detected. There are

several scenarios which can cause this
error condition. Error message describes
the cause. Some of these error conditions
are serious and result in driver process
restart, e.g. ASIC Init/remap, enable/disable
failure. Following are some of the reasons
for this internal error: 1) Obsolete API
usage, it can be caused due to
uncompatible component installed in the
system. 2) Interface creation failed due to
egressq port creation failure. 3) Can't map
Interface handle to egressq port, it could
be because of: a) Invalid interface handle
passed. b) Internal interface to port
mapping table is corrupted. 4) Egressq
ASIC reinitialization failed, this is an
irrecoverable situation, and Egressq driver
will be restarted. 5) Egressq Group/Queue
creation/ deletion failed. 6) ASIC enable
/disable failed.

LWM message send failed: [chars] reason:

[chars]

An internal error was detected when trying

to send a LWM message. There are several
scenarios which can cause this error
condition. Error message describes the
exact cause.

Client registration failed: [chars] reason:

[chars]

An internal error was detected while clients

are registering to Egressq process.

EVM error : [chars] reason : [chars]

An internal error was detected when trying

to create EVM connection. It can fail during
following scenarios: 1) EDM
registration/connect/notify. 2) BAG's rule
registration failed.

Internal error : [chars] reason : [chars]

Obsolete API usage, it can be caused due

to incompatible component installed in the
system.

Internal error : [chars] reason : [chars]

Egressq ASIC reinitialization failed, this is

an irrecoverable situation, and Egressq
driver will be restarted.

LWM message send failed: [chars] reason:

[chars]

An internal error was detected when trying

to send a LWM message. There are several
scenarios which can cause this error
condition. Error message describes the
exact cause.

Failed to allocate memory for [chars]

System failed to allocate memory. It's likely

that the system is running low on memory.
Following are some reasons: 1) Failed to
allocate memory for Egressq client add. 2)
Failed to allocate memory for Egressq
mapping table. 3) Failed to allocate
memory for Queue leaky bucket limit table
Memory. 4) Failed to allocate memory for
Queue leaky bucket limit table memory. 5)
Failed to allocate memory for Group leaky
bucket limit table memory. 6) Failed to
allocate memory for Group leaky bucket
limit table memory. 7) Failed to allocate
memory for Port leaky bucket limit table
memory. 8) Failed to allocate memory for
PLIM Asic back pressure table memory.

Internal error : [chars] reason : [chars]

Interface creation failed due to egressq

port creation failure. Can't map Interface
handle to egressq port, it could be because
of: Invalid interface handle passed.

Internal error : [chars] reason : [chars]

Egressq Group/Queue creation/ deletion

failed.

EgressQ Stuck condition detected (PLIM

link [dec], Port [dec], Group [dec], Queue
[dec], Len [dec])

Egressq driver detects the queue stuck

condition (CSCsj48554). There is no packet
output from one or more of the PLIM links
and the queue length for related queue(s)
is building up.

[chars] failed to connect to the PIRD

database: [chars]

The specified process failed to connect to

PIRD shared memory database on
initialization.

A failure occurred during the initialization

Failure during intialization of [chars]. Error: of the process. This resulted in the restart
[chars]
of the process.

[chars] lost event: [chars]

The specified process failed to receive an

event that was sent to it.

Not supported: [chars] on <<CH[hex]>>

The specified configuration is not

supported by the dataplane.

Unexpected AIPC error encountered while

[chars]: [chars]

ELMI encountered an error using the AIPC

infrastructure. The error message describes
what operation has failed and why it failed.
This is most likely to be due to a low
memory condition but may also be an
internal programming error.

Unexpected bag error encountered while

[chars]: [chars]

ELMI encountered an error using the Bag

Client library. The error message describes
what operation has failed and why it failed.
The most likely reason for this a low
memory condition but the error could also
be caused by a programming error. The
error will affect ELMI's ability to provide
operational management data, but won't
otherwise affect ELMI's operation.

ELMI encountered an error using the debug

service. The error message describes what
operation has failed and why it failed. The
Unexpected debug error encountered while error could be caused by low memory
[chars]: [chars]
resource or programming error.

Unexpected Event Manager error while

[chars]: [chars]

ELMI encountered an error using the Event

Manager library. The error message
describes what operation has failed and
why it failed. The most likely reason for this
is a low memory resources or programming
error.

Unexpected IM error encountered while

[chars]: [chars]

ELMI encountered an error communicating

with Interface Manager. The error message
describes what operation has failed and
why it failed. The most likely reason for this
is a temporary connection problem with the
Interface Manager Control Server, but the
error could also be caused by low memory
resource or programming error.

ELMI encountered an error using the

Lightweight Tracing service. The error
message describes what operation has
failed and why it failed. This is a fatal error
and the ELMI process cannot continue. It
Unexpected ltrace error encountered while will abort and subsequently be restarted by
[chars] the [chars] buffer: [chars]
SysMgr in an attempt to recover.

Failed to allocate [unsigned int] bytes

The process failed to allocate memory for

the specified resource.

Unexpected managed timer error

encountered while [chars]: [chars]

ELMI encountered an unexpected error

using the Managed Timer library. This is
most likely to be due to a low memory
condition but may also be an internal
programming error. The error message
should provide more information about the
cause.

The E-LMI specification assumes that the

MTU of the media that it is running over is
exactly 1500 bytes. However, the protocol
can run on lower values than this so long
as the MTU is large enough to include a
header, the report type IE, the sequence
numbers IE, the data instance IE and a
maximum length UNI IE. The message has
been issued because the configured MTU is
[chars] has a payload MTU of [unsigned int] too small to meet this condition. The
which is smaller than the minimum value protocol will continue to run assuming that
([unsigned int]) required for correct
the MTU is this minimal required value and
operation
so may not operate correctly.

E-LMI protocol error occured on

<<CH[hex]>>: [chars]

The entire PDU, or one or more IEs in the

PDU, were ignored due to the given error.
This indicates that the last PDU sent by the
peer device was not formatted correctly.

E-LMI protocol error occured on

<<CH[hex]>>: [chars] [chars]

The entire PDU, or one or more IEs in the

PDU, were ignored due to the given error.
This indicates that the last PDU sent by the
peer device was not formatted correctly.

E-LMI protocol error occured on

<<CH[hex]>>: [chars]: [unsigned int]

The entire PDU was ignored due to an

unexpected message type being received.
This indicates that the last PDU sent by the
peer device was not formatted correctly.

E-LMI protocol error occured on

<<CH[hex]>>: [chars]: [unsigned int]

The entire PDU was ignored due to an

invalid protocol version being requested.
This indicates that the last PDU sent by the
peer device was not formatted correctly.

E-LMI reliability error occured on

<<CH[hex]>>: [chars]. Report type
received: [unsigned int].

The report type of the message received

was inappropriate relative to the interface's
protocol state. For example, receiving an
'E-LMI Check' while processing a 'Full'
STATUS report. This indicates that the last
PDU sent to the peer device was not
received.

E-LMI reliability error occured on

<<CH[hex]>>: Invalid received sequence
number. Received [unsigned int], expected
[unsigned int].

The sequence number received does not

match the last sequence number sent. This
indicates that the last PDU sent to the peer
device was not received.

E-LMI reliability error occured on

<<CH[hex]>>: Polling Verification Timer
has expired.

The Polling Verification Timer has timed out

because no STATUS ENQUIRY message has
been received in the configured interval.

ELMI encountered an error using the SysDB

service. The error message describes what
operation has failed and why it failed. The
most likely reason for this is a connection
problem with the SysDB server, but the
Unexpected SysDB error encountered while error could also be caused by low memory
[chars]: [chars]
resources or programming error.

Unexpected SysMgr error encountered

while [chars]: [chars]

ELMI encountered an error while

communicating with SysMgr. The error
message describes what operation has
failed and why it failed. This is a fatal error
and the ELMI process will abort and be
restarted to recover.

Error initializing the WAVL tree used to

store ELMI IDBs: [chars].

ELMI encountered an unexpected error

which prevents it from functioning. This
error may be caused by low memory
resources. The process will abort and be
restarted in an attempt to recover.

The Ethernet LMI protocol is unable to

report EVCs for subinterfaces which have
conflicting encapsulations. In this context,
two subinterfaces have conflicting
encapsulations if they belong to the same
parent interface and any of the following
conditions are true: they have at least one
The EVC for <<CH[hex]>> will not be
VLAN ID in common in the outermost tag;
reported because the subinterface's
one matches untagged packets while the
encapsulation of '[chars]' conflicts with that other matches priority-tagged packets; one
of subinterface <<CH[hex]>>. The total
is configured to match any VLAN ID in the
number of EVCs not reported due to
outermost tag while the other is configured
conflicts is [unsigned int].
as the default match.
The EVC for [chars] will not be reported
because the subinterface number ([dec]) is The E-LMI protocol can report at most
larger than 65535. Including this one,
65535 EVCs per interface. Subinterfaces
[unsigned int] such EVCs will not be
with numbers above this value are not
reported.
reported to the peer device.

E-LMI protocol [chars] on <<CH[hex]>>

The operational status of the E-LMI protocol

on the interface has changed. If undesired,
the notification of protocol events can be
turned off by configuring 'log events
disable' on the interface.

The operational status of the E-LMI protocol

on the interface has changed. If undesired,
the notification of protocol events can be
E-LMI operational status on <<CH[hex]>> turned off by configuring 'log events
has changed to [chars]
disable' on the interface.

Unable to signal that process is exiting:

[chars]

The process has failed to inform System

Manager that it is shutting down. The
process will exit anyway, but it is possible
that any configuration entered will not
cause SysMgr to restart the process. In this
case, a timeout will occur when committing
configuration, and the config will fail to
apply.

Unable to block on sysmgr on the node

which is in standby role: [chars]

The process failed to block on System

Manager on a node which is in standby role
and wait for the node to go active.

Unable to signal process ready: [chars]

The process failed to inform System

Manager that it is ready, and will be
restarted.

Failed to cleanup common verification

module: [chars]

Whilst exiting, an error was encountered

cleaning up a common module. The
process will exit anyway, and no further
errors should be seen.

Failed to initialize common verification

module: [chars]

The process has failed to initialize a

module, and will be restarted.

Invalid configuration values applied:

[chars]

Invalid configuration has been incorrectly

applied. This can potentially indicate a
recent change in acceptable configuration
values, or an internal fault.

Failed to apply new Link OAM

Configuration. It is likely that the protocol
will not operate as intended: [chars]

The ELO Daemon on the specified node

was unable to enact a set of valid
configuration changes. Future configuration
changes may be adversely affected and
the protocol is likely not to operate as
intended. The problem could be caused by
a system resource issue.

The Ethernet Link OAM Daemon failed to

determine the ID of the node on which it is
Ethernet Link OAM Daemon failed to
running. It will exit, and should be restarted
determine the node it is running on: [chars] by System Manager.

Failed to remove PFI caps from interface

'<<CH[hex]>>': [chars]

The Ethernet Link OAM Daemon failed to

clean up a caps entry in PFI for the named
interface. This error is not fatal in itself,
although it may prevent OAM from being
re-enabled on the given interface until the
problem is resolved.

Ethernet Link OAM Daemon failed to

initialize [chars]: [chars]

The Ethernet Link OAM Daemon failed to

initialize correctly, and will now exit. It
should be restarted by SysMgr.

<<CH[hex]>>: failed to Error-Disable the

port: [chars]

The port should have been Error Disabled,

but an unexpected error has prevented it
from being shut down. The port is still up,
and will not be disabled.

Ethernet Link OAM Daemon failed to

process events: [chars]

The Ethernet Link OAM Daemon failed to

process an event, and will now exit. It
should be restarted by SysMgr, allowing it
to resynchronise its internal state.

Unable to lookup platform capabilities for

interface '<<CH[hex]>>' : [chars]

The ethernet_link_oam_daemon has failed

to determine the capabilities of a particular
interface. 802.3 OAM configuration will be
verified according to the global card
capabilities. For certain interface types,
this may result in configuration for a
particular feature such as UDLF being
incorrectly applied to an interface that does
not support it. Operation of the protocol is
unaffected and any unsupported
configuration will be ignored.

[chars]: Failed to initialise the interface:

[chars]

The Ethernet Link OAM Daemon was

unable to initialise the specified interface.
This is likely caused by a memory resource
allocation error. The exact error can be
found in the 'show ethernet oam interface'
command.

An attempt to change the Loopback state

of an interface failed. This will either be in
response to a local command to change
the remote peer's Loopback state, or a
[chars]: Failed to change Loopback state in command on the remote peer to put this
the platform: [chars]
interface in slave loopback mode.

The LWM subsystem indicated an error

when trying to send a reply from the
packet thread to the main thread in the
Ethernet Link OAM Daemon. The operation
will not be retried - the internal state of
Failed to send an LWM reply message in the Ethernet Link OAM may not match the
Ethernet Link OAM Daemon: [chars]
global system state.

Failed to perform a [chars] operation:

[chars]

An error was encountered while trying to

perform an operation on a lock. The thread
will continue without retrying the
operation. In most cases, no further
adverse behaviour should be observed.

Failed to unegister with IMC for attribute

notifications. Error message: [chars]

The Ethernet Link OAM daemon was unable

to unregister for interface notifications with
IM. The Ethernet Link OAM daemon may
continue to receive notifications for
interfaces it is not longer configured on.

Failed to successfully receive an OAMPDU

from SPIO: [chars]

The Ethernet Link OAM Daemon was

unable to receive an OAMPDU successfully
from SPIO. This could be due to the
OAMPDU not being received properly or
being corrupt such that the OAMPDU can't
be properly processed.

Failed to signal the end of a resync with

SPIO: [chars]

The Ethernet Link OAM Daemon failed to

resync with SPIO upon startup or a process
restart. This is due to an LWM failure when
sending a message between the main and
packet threads within Ethernet Link OAM
daemon. The operation will not be retried the internal state of Ethernet Link OAM
may not match the global system state.

Failed to register for packet IO on

initialisation: [chars]

The Ethernet Link OAM Daemon was

unable to register the module to send and
receive packets. This is likely caused by a
memory resource allocation error.

<<CH[hex]>>: failed to save checkpoint

entry: [chars]

The Ethernet Link OAM Daemon failed to

save the checkpoint entry for the given
interface. Although this error is not
immediately fatal, information will be lost if
the process restarts before successfully
saving its checkpoint data.

Ethernet Link OAM Daemon failed to

cleanup [chars]: [chars]

The Ethernet Link OAM Daemon failed to

cleanup correctly. It will exit anyway, and
no further errors should be seen.

Failed to shut down interface

<<CH[hex]>>: [chars]

A failure occurred when attempting to shut

down an interface using EFD after a fault
condition was detected on the interface.
This event was triggered by either a
change in stateful condition of the link, a
process restart or a change in configuration
that enabled EFD on a particular action.
This will result in the interface remaining
up, when it should be shut down.

Platform event triggered on interface

'<<CH[hex]>>' for which OAM is not
configured

The platform has triggered an event for an

interface that has not been configured for
Ethernet Link OAM. This indicates a bug in
the software.

The platform has triggered an event that is

An unknown event of type '[hex]' has been not recognized. This is most likely due to a
triggered by the platform
bug in the platform layers.

The Ethernet Link OAM Damon has failed to

Etherenet Link OAM Daemon has failed to initiate loopback mode. Loopback mode is
initiate loopback mode with a remote peer unavailable until the issue is resolved.

[chars]: Unable to exit Slave Loopback

mode as requested, because we're not
currently in loopback mode

A requset has been made by the remote

peer to stop Slave loopback mode.
However, we are not currently in Slave
loopback mode. This indicates that the
remote peer is out of sync with our current
state.

<<CH[hex]>>: [chars] notification

received from PFI, but interface does not
have OAM configured

Unexpected updates have been received

by the Ethernet Link OAM Daemon
regarding interfaces on which OAM is not
configured. This indicates that a resync is
required between the OAM process and PFI.

[chars]: Failed to send a [chars] message:

[chars]

Failed to send a message out of the given

interface. The message has been lost, and
will not be delievered to the remote peer.

The Ethernet Link OAM Daemon received

an OAMPDU on an interface that was not
configured with Ethernet Link OAM. The
Unexpected OAMPDU received on interface OAMPDU has been ignored. This message
<<CH[hex]>>.
is harmless.

Ethernet Link OAM Daemon has been

unable to send heartbeats for [unsigned
long long int] ms

The Ethernet Link OAM Daemon has been

blocked or starved of CPU time. As a result,
it will not have been able to send out
periodic heartbeats regularly, potentially
causing OAM sessions to drop. The problem
is likely due to unusually high load on the
system.

An interface was shut down or brought up

using EFD after a fault condition was
detected or cleared, or due to a change in
configuration. This has occurred because
Interface <<CH[hex]>> [chars] using EFD EFD is the configured action for this fault
due to [chars]
condition.

[chars]: Configuration conflict

Discovery mode cannot complete due to a

conflict in the required configuration of the
remote peer.

[chars]: OAM discovery failed to complete

in the specified time

Discovery mode has been ongoing for the

configured timeout, but no suitable
response has been received from the
remote peer.

[chars]: Remote critical event detected

The remote peer has indicated a critical

event.

The remote peer has indicated a dying

[chars]: Remote dying gasp detected, with gasp. This means that the remote peer is
reason: [chars]
coming down.

[chars]: Remote link fault detected

The remote peer has indicated that a link

fault has occurred. This indicates a unidirectional link.

[chars]: OAM [chars] loopback has been

[chars] on the interface

The OAM session has either entered or

exited local or remote loopback. If loopback
has been entered then traffic flow will be
disrupted until it is exited at which point
normal functionality will resume.

[chars]: OAM session has gone down

The OAM session has ended. Either it has

been deconfigured, or no response has
been received from the OAM peer in the
configured time interval.

[chars]: OAM session has come up

The OAM session has been fully

established, and regular heartbeat
messages are being sent and received.

[chars]: [chars] [chars] event breached

local high threshold - Window size:
[unsigned long long int], Errors: [unsigned
long long int], Threshold: [unsigned long
long int], Total errors: [unsigned long long
int]

A threshold has been breached in the

hardware. This is an indication of a
deteriorating link.

[chars]: Cancelling loopback mode as our

MAC is lower than the remote MAC

An attempt has been made to start

loopback mode from both peers
simultaneously. As per the IEEE 802.3 OAM
specification, this OAM client has cancelled
the request as the local MAC address is
lower than the remote MAC address.

A profile can be configured that has

configuration parameters that are not
supported for all interfaces on the router. If
that profile is later attached to an interface
for which not all its values are supported,
this message is generated. The interface
will use the default values for any
parameter that is out of range. The
configuration parameters that may not be
supported are support for remote loopback
The profile configuration from profile
and support for link monitoring events.
'[chars]' cannot be applied as the platform Further, the window size of a link monitor
does not support all the configured values: event must be a multiple of the interface's
[chars]
statistics' poll interval.

[chars]: Mis-wiring detected

The Mis-Wiring Detection feature of

Ethernet Link OAM has detected a miswiring situation. Mis-wiring occurs when
the TX wire of an interface is not connected
to the same remote interface as the RX
wire.

Profile '[chars]' is not configured, but has

been attached to an interface

A profile has been attached to an interface.

However, that profile has not yet been
configured. Until the named profile is
created, the interface will use the default
profile configuration.

While running the link in OAM Loopback

mode, with the local peer as the Slave, the
Master peer abruptly ended Loopback
[chars]: Local client in Slave Loopback, and mode without first informing this peer to
remote Master has abruptly left Loopback end it. This may indicate a problem with
mode. Exiting Slave loopback locally
the remote peer.

[chars]: Remote client has abruptly left

Slave loopback mode. Exiting loopback
state

While running the link in OAM Loopback

mode, with the local peer as the Master,
the Slave peer abruptly ended Loopback
mode without being told to do so by this
peer. This may indicate a problem with the
remote peer.

[chars]: An unexpected multiplexer and

parser state have been received from the
remote peer.

While running the link in OAM Loopback

mode the local peer received an
unexpected multiplexer and parser state
combination from the remote peer. This
may indicate a problem with the remote
peer.

A variable response from the remote peer

contained invalid state.

Whilst parsing a variable response packet

an invalid state was found. This could be
an indication of a faulty implementation on
remote peer.

Whilst exiting, the Global Manager failed to

cleanup the debug module. The process
Ethernet Link OAM Global Manager failed to will exit anyway, and no further errors
cleanup debug: [chars]
should be seen.

During initialization, the Global Manager

failed to initialize the debug module and
will now exit. It should be restarted by
Ethernet Link OAM Global Manager failed to System Manager and resynchronize it's
initialize debug: [chars]
internal state.

The process failed to process incoming

events, and will exit. It should be restarted
Ethernet Link OAM Global Manager failed to by System Manager and resynchronize its
process events: [chars]
internal state.

During initialization, an unexpected error

Ethernet Link OAM Global Manager failed to was encountered. The process will exit and
initialize: [chars]
be restarted by System Manager.

Failure during activation of [chars]. Error:

[chars]

A failure occurred during the activation of

the process. Activation occurs when the
card transitions to ACTIVE state. This error
resulted in the restart of the process.

Unrecoverable error in event loop. Error:

[chars]

An error (other than EINTR) occured in the

event loop. The process has exited and
restarted.

A failure occurred during the initialization

Failure during intialization of [chars]. Error: of the process. This resulted in the restart
[chars]
of the process.

The process was initialized successfully but

Failure communicating readiness to System was unable to inform System Manager of
Manager. Error: [chars]
the success.

The batch of available MAC addresses

supplied is invalid. A zero size range will be
used, resulting in any MAC address
Batch of MAC addresses retrieved is
requests from client features being
invalid: contains invalid MAC address: [hex] rejected unless any valid MAC addresses
%2.2x.[hex]%2.2x.[hex]%2.2x
are configured.

Range of available MAC addresses

retrieved is invalid: [dec] MACs starting
from Base MAC [hex]%2.2x.[hex]%2.2x.
[hex]%2.2x

The range of available MAC addresses

supplied by the platform is invalid. A zero
size range will be used, resulting in any
MAC address requests from client features
being rejected.

A repeated failure occurred when

requesting the range of available MAC
addresses. A zero size range will be used,
Unable to retrieve values of available MAC resulting in any MAC address requests from
addresses. Error: [chars]
client features being rejected.
MAC allocation process unable to provide
client [chars] with the requested number of A client has request more MAC addresses
MAC addresses: requested [unsigned int]
than the MAC allocation process can
supplied [unsigned int]: [chars]
provide.

Failed to notify a client of a change to

interface attributes - out of memory

The Ethernet Packet Infrastructure (EPI)

library was unable to notify a client of a
change to some interface attributes
because it was unable to allocate memory.
This may result in the client of the EPI
library attempting to send packets with
incorrect tag or encapsulation information.

Failed to initialize, [chars] failed: [chars]

An error was encountered while the

ethernet packet infrastructure (EPI) library
was initializing debug. The error message
contains details about the source of the
error.

The maximum number of packets being

stored for interface: <<CH[hex]>> has
been exceeded

The Ethernet Packet Infrastructure (EPI)

library has been asked to create a packet
for an interface which already has the
maximum number of supported packets in
storage. EPI has created the packet, but
may have difficulty updating packets on
this interface in future.

An error was received while waiting for an

event: (error: [chars])

The indicated process encountered an error

while listening for events. The process will
automatically restart and retry.

Initialization failed: [chars] (error: [chars])

The indicated process failed to initialize.

Previous messages may give the reason.
The process will automatically restart and
retry. Until it succeeds, Ethernet
functionality may be impacted.

There was an error upon initialization in the An error was encountered while the
[chars] module: [chars].
process was trying to initialize.

An internal error has occurred in the

process.

An internal error has occurred, causing the

feature to not be able to function properly.

No memory was available to be allocated.

An error was encountered while the

memory was being allocated.

Failed to resume an apply request to a

loopback session

An error was encountered while attempting

to return the status of a config apply
request. The CLI may be blocked, or may
have returned an error despite the
operation having succeeded.

Failed to stop loopback sessions after a

config deletion event.

A loopback session or sessions could not be

stopped after Ethernet Loopback
configuration was removed. The
configuration has been removed but
loopback sessions are still running.

The database was cleaned up before all

interfaces were deleted.

The database received a cleanup call

before all interfaces had been deleted.

Failed to resume a SysDB EDM request to

[chars] a loopback session

An error was encountered while attempting

to return the status of a loopback
start/stop/extend request. The CLI may be
blocked, or may have returned an error
despite the operation having succeeded.

An event was lost in the [chars] module:

[chars]

The specified process failed to receive an

event that was sent to it.

Failed to stop loopback session [unsigned

int] on interface <<CH[hex]>> after the
expiry timer fired.

A loopback session could not be stopped

after the expiry timer had fired. The
loopback session is still running, and will
attempt to be stopped every five seconds.

The pool of session IDs has been

exhausted. No more sessions can be
started until all currently active sessions
have stopped and session ID pool has been
reset.

A very large number of loopback sessions

have been started. All active sessions must
be stopped before any more can be
started.

There was an error upon starting the

loopback session with ID [unsigned int].
The error returned was: [chars].

The platform failed to start a loopback

session when requested to do so during a
resync.

The loopback session with ID [unsigned int]

could not be stopped in the platform. The The platform failed to stop a loopback
error returned was [chars].
session when requested to do so.
Session [unsigned int] on interface
<<CH[hex]>> has successfully been
extended.

A loopback session has successfully been

extended. This is for informational
purposes only.

Session [unsigned int] on interface

<<CH[hex]>> has successfully started.

A loopback session has successfully

started. This is for informational purposes
only.

Attempt to stop session [unsigned int] on

interface <<CH[hex]>> has completed.

A best-effort attempt to stop a session has

been made. If an error occurred in cleaning
up the session on a particular LC the
SESSION_NOT_STOPPED message will be
generated on that LC.

ETHER EA PD DLL INIT FAILED\n

Ether EA Platform Independent DLL

Initialization failed

Debug registration failed: [chars]

It was not possible for the Ethernet slow

path support to initialize its debugging
support. Some of the output from
<CmdBold>debug ethernetio<noCmdBold> output may be
incomplete.

DWDM Error :[chars] Reason : [dec]

SPA driver has detected an error in the

DWDM init routine.

Memory Allocation Failed :[chars]

The SPA driver detected a memory error on

the SPA card. The Error has occurred
because the requested amount of memory
is not available.

[chars] not locked after [dec] retries [hex]. The SPA driver failed to initialize the PLL.

Burst of [chars] occurred for [dec]/[dec]/

[dec]. No Manual intervention required

A burst of interrupts have occurred and the

interrupt manager has throttled the
interrupt. It will be re-enabled
automatically after the pause timer expires
and no further intervention is required.

A Maximum MAC Error recovery retries has

occurred for [dec]/[dec]/[dec]. PORT
DISABLED after exceeding maximum
retries. LINK force DOWN. Manual
intervention required to bring port back
into operation.

A MAC Frame Corruption occurred on the

interface, concerned port is in error
condition after maximum recovery retries.
The concerned port has been permanently
disabled. Manual intervention required to
re-enable the port.

A Maximum MAC ECC Auto Error recovery

retries has occurred in bay [dec]. SPA is
shutting down

MAC TX/RX FIFO ECC errors have occured.

Auto-recovery attempts have also failed to
recover the SPA. This is indicative of a
hardware issue. Manual intervention is
required.

A Hardware or Software error occurred.

Reason : [chars] Automatic Error recovery
initiated. No further intervention required.

An error occurred in the SPA, recovery

would be attempted. If recovery succeeds
no further messages would be logged and
no intervention would be required.

[chars] port [dec] security check failed .

Transceiver module is disabled

The Transceiver module inserted in the

specified port is not supported.

Ethernet: Invalid configuration, [chars] is

not supported by this interface

Invalid configuration

Ethernet: [chars]() line [dec]: interface

manager call [chars] failed: [chars]

The call to im failed for some reason.

[chars]: calloc failed

Memory allocation for sub-info structure of

ethernet rp driver failed.

Ethernet: [chars]: devctl failed with code

[hex]

A devctl call failed.

Ethernet: [chars]() line [dec]: out of

memory, unable to create [chars]

Card has no more memory available.

The driver failed to initialize

Ethernet: Sysdb registration failed ([chars]) communication with sysdb.

Ethernet: Unknown asynchronous event

[dec] in [chars]

An invalid asynchronous event was

received by the driver.

The ethernet driver failed to process a

bundle IIR notification message. Further it
is not able to propagate the message back
to the virtual interface owner, and hence it
The basecaps failed to process a bundle IIR is possible that the Ether basecaps is out of
[chars] message on [chars], error: [chars] step with the bundle configuration.

Ethernet: [chars]() line [dec]: failed to

[chars].

A dilb call failed, preventing

communication between
threads/processes.

Ethernet: [chars]() line [dec]: DPC call to

[chars] failed.

A direct procedure call failed.

intialisationi of rx tx ring for this interface

failed

The initialization of ethernet rp driver chip

failed.

Ethernet: [chars]() line [dec]: Bad sysdb

call for tuple [chars]: [chars]

An edm sysdb call was improperly formed.

Ethernet: [chars]() line [dec]: init failed in

function [chars]: [chars]

Basic initialization failed due to problem in

a called function.

Ethernet: Incompatible structure definition A structure passed is the wrong size due
for [chars] in [chars]
most likely to compilation problem.

An invalid timer type was found in an

Ethernet: [chars](): Invalid timer type [dec] expired timer.

Restarting the driver failed for some

Ethernet: [chars]() line [dec]: [chars]: [dec] reason.

Ethernet: Failure initializing asynchronous

timers: [chars]() - [chars]

A failure occured while creating or

initializing the timers for the driver.

Ethernet: Unsupported stats request [dec]

in [chars]

A driver has requested an unsupported

stats type.

The bundle MAC address failed to be

The bundle MAC address: [chars] failed to programmed as the MAC address is
be programmed or deleted on [chars] as it currently associated with another client
is already associated with HSRP or VRRP.
(most likely HSRP/VRRP).

Failure during receipt of message. Error:

[chars]

A failure occurred handling a message

arriving at one of the Ethernet capsulation
processes. Under normal circumstances the
process restarts with no impact to
functionality. If this error message is seen
repeatedly then Ethernet services may be
affected on all Ether type interfaces on the
given node.

Failure during intialisation of [chars] in a

Ether basecaps process. Error: [chars]

A failure occurred during the initialisation

of one of the Ethernet capsulation
processes. Under normal circumstances the
process restarts with no impact to
functionality. If this error message is seen
repeatedly then Ethernet services may be
affected on all Ether type interfaces on the
given node.

[chars]: 83800 Error RXB: Bad RX Pkt

This is a debug message which says

received Bad Rx packet

[chars]: 83800 Error TXB: Bad TX Pkt.

TSR=[hex]

This is a debug message which says Bad

TX packet is received

[chars]: Interrupt without vector

This is a debug message which says an

Interrupt had raised without a vector

This is a debug messgae which says the

[chars]: 83800 Error MIB: Counter overflow MIB counters overflow

[chars]: 83800 Error RFE: RX fifo error

This is a debug message which says

receiver FIFO buffer interrupt has occured

[chars]: 83800 Error RXT: RX Threshold is

hit

This is a debug message which says RX

threshold had reached

[chars]: 83800 Error TFE: TX fifo error

This is a debug message which says

Transeiver FIFO buffer interrupt has
occured

[chars]: 83800 Error SWI: Unexpected

Software Interrupt

This is a debug message which says

unexpected sofware interrupt has occured

[chars]: An unknown interrupt had raised:

[dec]

This is a debug message which says an

unknown ethernet rp driver interrupt has
occured

Failed to initialize interface [chars], due to

error: [chars]

It was not possible to initialize the physical

interface due to a driver error or a system
error. The interface's config may not have
been restored and the interface will not be
usable.

It was not possible to register for statistics

Failed to register for MAC accounting stats collection due to a error reported by the
collection, error: [chars]
statistics infrastructure.

Unable to fetch requested Etherlike MIB

data for interface [hex]: [chars]

An error occured while trying to collect MIB

data requested by the SNMP infrastructure.
The data for which an error was
encountered will not be presented in SNMP
'get' request results.

Error initializing Etherlike MIB: [chars]

An error occured while trying to initialize

the etherlikemib DLL with the SNMP
infrastructure. The error may result in the
inability to retrieve data from the
ETHERLIKE-MIB.

Failed to set MTU of [unsigned int] on

[chars]

The specified MTU could not be applied on

this interface.

Port state FSM operation failed [chars] on

[chars], due to error: [chars]

An operational error occured when

handling a port state event in the port
state machine, and the internal state may
be left in an inconsistent state without user
intervention.

Interface [chars], link [chars]forced down

due to remote signalling

L2VPN Mgr has signalled at the remote AC

has changed state. Due to this the local
interface has been enabled/disabled in the
TX direction if supported, or
enabled/disabled in both directions
otherwise.

interface: [chars], alarm: [chars], status:

[chars]

The specified Bit Error Rate Alarm has been

declared or released. interface: interface
on which alarm is set/cleared alarm: alarm
being asserted e.g: SF-BER or SD-BER
status: set/cleared

Initialization of the G-Ether library failed at A error occurred during the initialization of
stage '[chars]', due to error: [chars]
the common Ethernet driver library.

Interface creation failed due to error:

[chars]

It was not possible to create some or all

physical ethernet interfaces due to a driver
error or a system error.

Interface [chars]%s[chars]%s, [chars]

addresses for MAC accounting

Some MAC addresses have not been

programmed for MAC accounting in the
hardware. This means that MAC accounting
statistics will not be collected for these
MAC addresses. This is most likely due to a
lack of hardware resources due to a large
number of MAC addresses being
programmed for MAC accounting.

The MTU on the interface, including any

sub-interface overheads, is larger than the
The MTU of [unsigned int] on [chars] is
H/W MTU limit. Hence large frames bigger
over the H/W limit, and hence large frames than the maximum frame size supported
may be dropped as oversized frames
on the interface may be dropped.

[chars]: [hex], [chars]

An error occurred in 1p OC12-ch-ds1 PLIM

process. This may cause features to not
work properly.

[chars]

An error occurred in 1p OC12-ch-ds1 PLIM

process, which might involve exiting the
process. Some features may not work if
this error is seen.

[chars]: failed to read card type. trying

again...

Failed to read card type.

[chars]: [hex], [chars]

An error occurred initialization of 1p OC12ch-ds1 PLIM process, which will involve

exiting the process and recover.

[chars]

An error occurred in the 1p OC12-ch-ds1

Multilink platform dependent component.
This may cause the multilink feature to not
function properly.

[chars]

An error occurred in the 1p OC12-ch-ds1

PLIM multilink pulse message processing.
This may cause the multilink feature to not
function properly.

[chars]: [hex], [dec]

An invalid input condition detected.

[chars]: cmd_queue = 0x[pointer],

cmd_size = [dec]

The size of the command is greater than a

specified size.

[chars]: [chars], [hex]

The SHIM information not found for the

interface given.

[chars]: [chars], [dec]

The shim values cannot be extracted as the

encapsulation is of unexpected type.

Unexpected error has lead to an incoming

message being dropped: [chars]

An incoming control message could not be

fully processed due to an unexpected error.

Checkpoint data for this connection (id

%hu) has invalid id (%hu)

The Checkpoint table contained

unexpected data. This is unexpected, and
could indicate memory corruption of some
sort.

Failed to save Checkpoint sequence

information for connection [chars]

The client failed to save its own sequence

data to Checkpoint. If the process restarts
before the save is successfully retried,
remote clients may get out of sync, and
data loss could occur.

The client failed to save data to

Checkpoint. If the process restarts before
Failed to save Checkpoint entry [hex]/[hex] the save can be retried, then data loss
on connection [chars]
could occur.

Duplicate Checkpoint entry for ID %hu on

node [hex]

The Checkpoint table contained a duplicate

entry. This is unexpected, and likely
indicates a software fault.

[chars] ifh: [hex], [chars]

Platform IPv4 FIB, adjacency error

[chars] ifh: [hex], [chars]

A runtime failure occurred in FIB engine

layer while processing/updating adjacency
information. The message string indicates
the reason for the This message also
provides a string interpretation of the error
code and the interface handle.

[chars] ifh: [hex], [chars]

A runtime error occurred in ASR9K

adjiacency module. The reason for the
failure is also displayed. Please call Cisco
Support with the error information.

IPV4 Adjacency Creation Warning [chars]

ifh: [hex], [chars]

A runtime error occurred in ASR9K

adjiacency module. The reason for the
failure is also displayed. Please call Cisco
Support with the error information.

[chars] [dec]

Platform IPv4 FIB, error information

[chars] [dec]

A runtime error occurred in ASR9K IPv4 FIB

module. The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

[chars] [unsigned int]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

FIB error [chars] [unsigned int]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars], [chars] ([unsigned int])

Platform IPv4 FIB, error information

[chars], [chars] ([unsigned int])

A runtime error occurred in ASR9K IPv4 FIB

module. The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

[chars], [chars] ([unsigned int])

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

FIB error [chars], [chars] ([unsigned int])

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]

Platform IPv4 FIB, error

[chars]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card whee the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

FIB error: [chars]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card whee the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]

A runtime error occurred in ASR9K IPv4 FIB

module. The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

FIB IPV4 error: [chars]

An IPV4-specific software error occurred

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
initialize objects. This condition indicates a
problem with the software on the card.
Typically, this occurs when the software
tries to initialize invalid objects. Unexpected events. This condition
indicates a problem where an event is
triggered in the software unexpectedly on
the card. - Invalid objects. This condition
Operation failed [chars]: [chars] ([unsigned indicates a problem where the object being
int])
processed by the software is invalid.

Operation failed: [chars]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Unexpected events. This condition
indicates a problem where an event is
triggered in the software unexpectedly on
the card. - Invalid objects. This condition
indicates a problem where the object being
processed by the software is invalid.

FIB trace [chars]: type [dec]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card whee the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

IPV4 Context Creation Warning:[chars]

A runtime error occurred in ASR9K IPv4 FIB

module. The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

IPV4 API Context Initialization

Warning[chars] ErrCode[dec]

A runtime error occurred in ASR9K IPv4 FIB

module. The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

API context Initialization [chars],Warning:

[chars] ([unsigned int])

A runtime error occurred in ASR9K IPv4 FIB

module. The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

FIB IPV4 recursive loop: [chars]

Recursive loop was detected. The route

update will be dropped

IPV4 Processing Info:[chars]

This is an information message in the

ASR9K platform FIB specific code software.
The message is for debug purposes only
and not an error.

[chars]

This is an information message in the

ASR9K platform FIB specific code software.
The message is for debug purposes only
and not an error.

[chars] ifh: [hex], [chars]

Platform IPv6 FIB, adjacency error

IPV6 Adjacency creation warning [chars]

ifh: [hex], [chars]

A runtime error occurred in ASR9K IPv6 FIB

module. The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

[chars] [dec]

Platform IPv6 FIB, error information

[chars] [dec]

Platform IPv6 FIB, error information

[chars] [unsigned int]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars] [unsigned int]

[chars] [chars] [chars] [dec]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.
Platform IPv6 FIB, error information

[chars] [chars] [chars] [dec]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. It provides more verbose information.
Here is a list of possible reasons for this
message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars] [chars] [chars] [dec]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. It provides more verbose information.
Here is a list of possible reasons for this
message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars], [chars] ([unsigned int])

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars], [chars] ([unsigned int])

Platform IPv6 FIB, error information

[chars], [chars] ([unsigned int])

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]

Platform IPv6 FIB, error

[chars]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]

Platform IPv6 FIB, error

[chars]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

FIB IPV6 error: [chars]

An IPV6-specific software error occurred

IPV6 memory allocation Warning:[chars]

A runtime error occurred in ASR9K IPv6 FIB

module. The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

A runtime error occurred in ASR9K IPv6 FIB

module. The reason for the failure is also
IPV6 context/memory Initialization Warning: displayed. Please call Cisco Support with
[chars] ErrCode:[dec]
the error information.

[chars], [chars] ([unsigned int])

A runtime error occurred in ASR9K IPv6 FIB

module. The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

FIB IPV6 recursive loop: [chars]

Recursive loop was detected. The route

update will be dropped

IPV6 context initialization Info:[chars]

PLATFORM IPv6 FIB, Information Message

[chars]

PLATFORM IPv6 FIB, Information

[chars] [dec]

Platform MPLS FIB, error information

[chars], [chars] ([unsigned int])

Platform MPLS FIB, error information

[chars]

Platform MPLS FIB, error

Failed to Initialize MPLS context Warning:

[chars]

A runtime error occurred in ASR9K IPv6 FIB

module. The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

MPLS context initialization info

Warning[chars] ErrCode:[dec]

A runtime error occurred in ASR9K IPv6 FIB

module. The reason for the failure is also
displayed. Please call Cisco Support with
the error information.

A runtime error occurred in ASR9K IPv6 FIB

module. The reason for the failure is also
MPLS context Initialization [chars],Warning: displayed. Please call Cisco Support with
[chars] ([unsigned int])
the error information.

[chars]: failure occured in Frame-Relay

External-Data-Manager (EDM) processes.
Probable Reason [chars]

Failure occured during creating EventManager (EVM) or initialization of FrameRelay's External Data Manager (FR EDM)
process

unable to get statistics data for VirtualCircuit (vc),Current Data Link Connection
Identifier is [dec]

The statistics manager returned null data

for Virtual-Circuit (vc), a Non-Zero, not-Null
value is expected. Operation Failed for the
reported Data-Link Connection.

Unable to allocate [dec] bytes of memory

The system is low on memory and not

enough was available to complete the
request

failure on IM connection: [chars]

This error indicates a problem with

InARP/IM interaction.

failed to initialize: [chars]

During process start up an unrecoverable

error occurred. The component will exit and
should be restarted by the System
Manager.

unable to apply class [chars] to interface

[chars]: [chars]

A vc-class was configured on an interface

but couldn't be applied for the given
reason

received an event on unknown fd [dec]

An event was received with an unknown fd

unable to allocate [dec] bytes of memory

The system is low on memory and not

enough was available to complete the
request

unable to apply class [chars] to interface

[chars].[dec]: [chars]

A vc-class was configured on an interface

but couldn't be applied

could not send on socket: [chars]

Socket returned an error, not EAGAIN or

EINTR

received an unknown event [hex]

An unknown event was received

received information about an

unrecognised interface

A set of IDBs are kept with information on

each InARP interface. Somehow this
information has become inconsistent with
the system.

received an event for an unknown interface The system sent a messages which wasn't
type: [dec]
expected. It will be ignored.

received an unknown message: [dec] on

interface [chars]

An unknown InARP message was received it will be ignored

LMI failed to initialize: [chars]

During process start up an unrecoverable

error occurred. The component will exit and
should be restarted by the System
Manager.

Configured values of [chars] and [chars]

conflict during application. Changing
[chars] to [dec] to maintain consistency

LMI parameters N392 and N393 are codependent - they must obey the rule N392
<= N393. Somehow SysDB is attempting
to apply config which conflicts
unreconcilably. The parameter being
configured is adjusted to be equal to the
other.

Unable to process Frame Relay

encapsulation request

An error occurred processing a request to

set Frame Relay encapsulation on an
interface. LMI will not be able to control the
interface.

FSM in STOPPED state while timer is

running: Interface [chars]

This indicates that FSM has gone into an

error condition. We should not have a valid
timer expiry event if the FSM for this
particular interface was in STOPPED state.

Interface creation within fr_lmi process

IDB initialization failure for [chars] - [chars] failed for the named interface.

The interface specified by a handle is not

one that LMI recognizes as running Frame
Relay

A call to rt_search failed to return an idb

object.

[chars]

Error in IM operation. Ex: Connection to IM

not getting established, or some IM API
errored out.

An error occured while inserting the vc_idb Dangling VC found. Possible reasons: VC
into the tree, a invalid vc_idb(ifh [hex], dlci deletion failed in previous attempt or LMI
[dec]) exists
did not get a deletion nfn from IM

An error occurred informing the VC

Manager that LMI is [chars] responsible for An error occurred in the VCM call to set the
the line state of an interface: [chars]
keepalive state.

An error occurred informing the VC

Manager of the line state: [chars]

The VC Manager returned an error after

receving a request to set the line state.

Memory allocation failed: [chars]

A call to malloc failed.

An error occurred receiving a packet:

[chars]

The socket call recvfrom returned an error.

An error occurred sending a packet: [chars] The socket call sendto returned an error.

An error occurred sending the updated VC

states to the VC Manager: [chars]

The VC Manager returned an error after

receving a request to update VC states.

Unable to create LMI DLCI [dec]: [chars]

LMI was unable to create a VC it needed to

function properly.

An error occurred sending the VC states to

the VC Manager. This could have occurred
LMI was unable to send all VC states to the searching LMI's internal database or in the
VC Manager
call to the VCM.

Changing defaulted value of [chars] to

[dec] due to configured value of [chars]

LMI parameters N392 and N393 are codependent - they must obey the rule N392
<= N393. Sometimes when one is changed
the other must be changed as well to keep
the protocol functioning properly.

Failed to allocate [unsigned int] bytes

The DLL has failed to acquire the required

amount of memory.

Debug registration failed: [chars]

Debug message registration failed No

significant impact on functionality.

SFRAR failed to initialize with an error:

[chars]

During process start up an unrecoverable

error occurred. The component will exit and
should be restarted by the System
Manager. Once restarted, it should work
fine. The performance will be affected in
the only manner that the Static Frame
Relay Address Resolution will not be
initialized in the worst case.

SFRAR process ready call failed with an

error: [chars]

The call to inform the System Manager that

SFRAR is running failed. The SysMg library
API failed. This was attempted to setup
message handler for message syncing.

Socket failed to initialize: [chars]

During process start up an unrecoverable

error occurred. The component will exit and
should be restarted by the System
Manager.

Failed to setup fr socket EVM connection:

[chars]

The fr_socket process failed to connect to

the event manager.

Failed to register [chars] protocol in netio

The fr_socket process failed to send dpc

message to Netio

Failed to send packet out to Netio: [chars]

The fr_socket process failed to send packet

out to Netio.

unable to allocate [dec] bytes of memory

The system is low on memory and not

enough was available to complete the
request

Failure in packet manager connection:

[chars]

The fr_socket process failed to connect to

packet manager

Failed to setup fr socket as a resource

manager: [chars]

The fr_socket process failed to advertise

itself to the system as a resource manager.

Failed to send async pulse [dec]: [chars]

The fr_socket process failed to send async

pulse to FR socket EVM

SysMgr process ready call failed: [chars]

The call to inform the System Manager that

the FR socket is running failed.

The FR Uberverifier process has detected a

misconfiguration. It was not able to cleanup
its internal DB while handling aborted
encap creations. FR UberVerifier process
identifies failed creates on abort and
[dec] encap aborts failed: The system may attempts best effort to correct the internal
now be in an inconsistant state.
state.

Unrecoverable error in event detection

loop. Error: [chars]

An error occured in the system level event

detection loop, which couldn't be corrected
automatically in the next iteration(run)
through this loop. The process must exit
under this circumstance.

A failure occurred during the initialization

of the process. This may result in the
restart of the process. The failure could be
one of the following: - Event Manager Debug Library - LWM bind Module - Sysdb
Failure during intialization of [chars]. Error: verification registration - Data Storage
[chars]
Module - Detach pulse handler

Misconfiguration: Item [chars] on interface

[chars] is incompatible with other
configuration. The system may now be in
an inconsistant state.

The FR Uberverifier process has detected a

misconfiguration. It was not detected in the
verification phase, so the Uberverifier
process cannot correct this.

The process was initialized successfully but

was unable to inform System Manager of
the success. This should not occur more
Failure communicating readiness to System than once as the process should restart
Manager. Error: [chars]
itself.

FR VCM EA failed to initialize: [chars]

During process start up an unrecoverable

error occurred. The component will exit and
should be restarted by the System
Manager.

[chars]

Internal error.

Failed during AIB initialization, err: [chars]

The FR VCM EA process initialization failed

whilst trying to connect to AIB.

Error during messaging: [chars]

The FR VCM EA process has detected an

error during messaging. Possible memory
corruption or out of resource.

Internal database access error

The FR VCM EA process code/data is

inconsistent. Possible coding error or data
corruption.

Failed DLCI match, err: [chars]

The FR VCM EA has a wrong value of the

DLCI and is not the same as what the MA
sends.

Failed to initialize FR VCM subinterface

stats collection, err: [chars]

The FR VCM EA subinterface stats

collection initialization failed.

Configuration registration failed: [chars]

Unable to register for configuration

changes.

Connection initialization failed: [chars]

Unable to initialize connections to one or

more servers.

Connect to L2VPN server failed: [chars]

FR VCM process on linecard tried to

connect to L2VPN server on RP. Connect
registration failed. FR L2 sub-interfaces will
not be operational on this linecard.

Unable to specify [chars] encaps type for

interface [chars]: [chars]

The configuration in the NetIO DLL could

not be updated, the system may continue
with the existing encapsulation type

FR [chars] IDB [chars] failed: [chars]

Unexpected error on Interface Descriptor

Block

FR [chars] on [chars] failed: [chars]

The operation on the named item is not

completing successfully when it is
expected to, and hence the FR support
may be disabled

FR interface [chars] not found

An action has been performed on a FR

interface, but FR doesn't have any
information about the interface.

FR error on main interface [chars]: [chars]

Unexpected error on the main interface

unable to allocate [dec] bytes of memory

The system is low on memory and not

enough was available to complete the
request

FR PVC create (dlci [dec]) on PTP

subinterface failed - only one PVC is
allowed

Point-to-point (PTP) subinterfaces only

allow one PVC and an attempt to create a
second PVC is being rejected

FR error on sub-interface [chars]: [chars]

Unexpected error on the sub-interface

Unexpected failure performing a SysDB

FR SysDB [chars] on [chars] failed: [chars] operation.

FR VC with DLCI [dec] already exists

The DLCI is unique per 'main' interface and

this dlci is already used

FR VC with DLCI [dec] not found

An operation was performed which

expected a VC with the specified DLCI to
exist, but it doesn't

Debug registration failed: [chars]

Debug message registration failed

FR MIB: Message: [chars]: reported in:

[chars]: with likey cause: [chars]

This message indicates the FR MIB library

fails to perform a SYSDB operation. Trap
initialization will be affected. The error
could be related to the following: - failed
event attach - timer tree initialization
failure - Trap handler registration failure EDM handler registration failure - IPC issues
- Trap OID conversion problem

Communications error for node [chars]:

[chars]%s

A error occurred in the communication

between Frequency Synchronization
processes. Frequency Synchronization
information may be out of sync.

An error occurred when attempting to rearm the ESMC SSM send timer. No further
Failed to re-arm the ESMC SSM send timer: SSMs will be sent from interfaces on the
[chars]
card on which this message was seen.

Communications retry failed: [chars]%s

A Frequency Synchronization process has

failed to send a message and attempts to
retry the send have also failed.

Failed to re-arm the ESMC SSM receive

timer for [chars]: [chars]

An error occurred when attempting to rearm the ESMC SSM receive timer for the
specified interface. Any SSMs received on
the interface will continue to be handled,
but any future peer timeouts (i.e. loss of
SSMs) on the interface will go undetected.

Failed to initialize: [chars]%s

An error was encountered while the

specified process was initializing. The error
message contains details about the source
of the error.

Failed to program the inputs for selection

point [chars]: [chars]

The Frequency Synchronization manager

that generated the message failed to
program the inputs for the specified
selection point into the platform. Any
changes to the inputs (for example, if an
input is no longer available or if it's QL has
changed) will not take effect.

Interface manager failed to [chars] for

[chars]: [chars]

*SUPPORT*

Failed to handle interface status change for

[chars]: [chars]
*SUPPORT*

[chars] lost event: [chars]

The specified process failed to receive an

event that was sent to it.

Frequency Synchronization MIB DLL error:

[chars]%s

An error was encountered in the Frequency

Synchronization MIB DLL. Some
functionality of the Frequency
Synchronization DLL may be impaired. The
error message contains details about the
source of the error.

Frequency Synchronization MIB index

checkpoint error: [chars]

An error was encountered while

checkpointing Frequency Synchronization
MIB indices. Frequency Synchronziation
SNMP data may be inconsistent over
Frequency Synchronization process restart.

MIB indices exhausted

The pool of MIB indices to assign to

Frequency Synchronization sources has
been exhausted. MIB data from the
Frequency Synchronization feature may be
inaccurate.

Failed to [chars] the [chars] timer for

[chars]: [chars]

*SUPPORT*

Failed to handle selection update for

selection point [chars]: [chars]

The Frequency Synchronization manager

that generated the message encountered
an error during handling of an update to
the inputs selected at the specified
selection point. The message contains
more details of the error. The change to
which inputs are selected, or to the QL or
priority of the selected input, may not take
effect.

Could not determine whether to exit:

[chars]

A Frequency Synchronization process could

not determine whether all Frequency
Synchronization configuration has been
removed and so cannot exit safetly.
Frequency Synchronization processes may
be running despite no Frequency
Synchronization configuration existing.

The Frequency Synchronization manager

that generated the message failed to
update its database, either in response to a
message received from a remote
Frequency Synchronization manager on
another node, or after a change to the
selected inputs in another selection point
on this node. This is most likely due to an
Failed to create object representing signal out-of-resource condition. The
from [chars] to local Selection Point [chars]: corresponding frequency signal will not be
[chars]
used.

Failed to process a timer event: [chars]

A Frequency Synchronization process has

failed to process a timer event.

New selection for selection point [chars]:

[unsigned int] inputs selected[chars]

A new set of inputs has been selected at

the specified selection point, to drive the
output of the selection point.

Selection point [chars] is no longer

externally synchronized: [chars]

There is no longer a line or external source

available for the specified selection point,
so it has fallen back to the internal
oscillator if available, or otherwise disabled
the outputs.

adj engine layer internal error [chars] :

[chars]

A runtime failure occurred in adjacency

engine layer resulting in a failure to provide
some system service as indicated in the
message text. This is most likely an
internal error. %s - indicates the reason for
the failure. %s - is the decoded error
reason.

Adjacency HW pointer is NULL for path

[dec] fwd_type [dec]

A runtime failure occurred in fib ip engine

layer resulting in a failure to provide some
system service as indicated in the message
text. This is most likely an internal error.
path %d - indicates the path index
fwd_type %d - the forward type

fib ip engine layer internal error [chars] :

[chars]

A runtime failure occurred in fib ip engine

layer resulting in a failure to provide some
system service as indicated in the message
text. This is most likely an internal error. %s
- indicates the reason for the failure. %s - is
the decoded error reason.

Shared memory init failed rc =[dec]

Failed to initialize the shared memory.

\nassertion '[chars]' failed in [chars]

([chars]:[dec])

Assertion Failure.

[chars] : [chars] [chars]

The specified G709 Alarm has been

declared or released.

[chars] Failed - Reason [chars]

The dwdm encountered an error that would

lead to degraded service.

The logging buffers have overflowed, and

On Port [dec], read Index [dec] write Index reached a point were there is no buffers
[dec]
available.

[chars] [chars]

This is an informational message in the

G709 PI component to indicate an
operation.

Port[[chars]] event[[chars]] changes

proactive protection state to [[chars]]

This is an informational message from

proactive state machine to indicate an
operation.

Debug: [chars]: [chars] value [dec]

This is an debug message in the G709 PI

component to indicate an operation.

No longer receiving R-APS messages for

ethernet ring [chars] instance [dec]

A ring node has not received R-APS

messages on the APS channel for an
extended period of time. A properly
functioning ring will have an R-APS
message transmitted nominally every 5
seconds. This indicates that the requesting
(transmitting) remote node on the ring,
such as the RPL owner, has gone down or
there is a network connectivity problem
with the APS channel.

Updates to the port states have errored for

the indicated ring instance. Any further
state updates on these ports cannot be
sent until the error is cleared, potentially
blocking important updates. It is also
Port state updates may have failed for ring possible that the current state has not
[chars] instance [dec]
been correctly implemented.

Failed to notify SysMgr that [chars] is

exiting: [chars]

The specified process failed to notify the

system manager that it was exiting. In very
rare cases, this could result in the process
not being restarted when it ought to be.

Node received an R-APS message with

Node Id [chars], level [dec] which is lower
than configured level [dec] for Ethernet
ring [chars] instance [dec]

A ring node detects an R-APS message with

a lower level than the configured G.8032
instance level for that APS Channel. This is
a Failure of Protocol - Provisioning Mismatch
- Level due to a misconfiguration of the APS
level of nodes in the ring.

RPL Owner node detects a No Request RAPS message with the RPL Blocked status
flag set, and the Node Id differs from its
RPL Owner node received an R-APS(NR,RB) own. This is a Failure of Protocol - Provision
message from another RPL Owner with
Mismatch due to a misconfiguration where
Node Id [chars] for Ethernet ring [chars]
there are multiple RPL Owner nodes
instance [dec]
configured in the ring.

Failed to initialize [chars]: [chars], [chars]

An error was encountered while the

specified process was initializing. The error
message contains details about the source
of the error.

The configuration specifies a topology

change notification (TCN) propagation
which is not valid, and consequently, the
system will ignore this propagation path. A
ring configured as a source of TCN
propagation must not have port1
configured as a regular protected interface
(i.e. port1 must be None or virtual
channel). A ring referenced as a destination
of TCN propagation must have port1
Invalid TCN propagation configured [chars]- configured as a regular protected interface
>[chars], ring [chars] is not a valid [chars] (i.e. port1 must not be None nor virtual
of TCN
channel)

A ring node, which was had previously not

received R-APS messages for an extended
period of time, is now receiving R-APS
messages. A properly functioning ring will
Now receiving R-APS messages for ethernet have an R-APS messages transmitted
ring [chars] instance [dec]
nominally every 5 seconds

Non-revertive ethernet ring [chars]

instance [dec] is ready to be cleared by
user

Faults have disappeared from a nonrevertive ethernet ring instance, so now it

is ready to be cleared by the user. A nonrevertive ring instance by definition
requires user action because it does not
revert automatically. The act of clearing the
ring will cause the location of the block to
move to the RPL link and the state to
transition to Idle.

Ethernet ring [chars] instance [dec]

changed state to [chars]

Informational message to notify the state

transitions for a ring instance.

[chars]: AIB registration message: [chars]

Error in gatm operation. The message

informs about the status of registration
with AIB. (SUCCESSFUL/FAIL/DISCONNECT)

Error in gatm operation. The error message

can be related to any of the following: Memory allocation - Data unavailability AIB registration failure - Attribute
modification failure - A minor method error
- Duplicate attribute settting - NULL
Method: [chars] - Line: [dec]: Error: [chars] detection

Error in gatm operation. Error message

here describes that the gatm method was
expected to succeed, but failed somehow
as either the attribute fetch/ operation
corresponding to the interface handle(in
Method: [chars] - Line: [dec]: Error: [chars] parenthesis) did not succeed Or, the
(ifhandle: [hex])
ifhandle itself was invalid.

Error in gatm operation. This gatm

operation message basically denotes the
Method: [chars] - Line: [dec]: Error: [chars] shim update failure. ifh and rc are ifhandle
ifh=[hex] rc=[hex]
and return codes in hex.

Error in gatm operation. Error message

here describes that the gatm method was
expected to succeed, but failed as an
Method: [chars] - Line: [dec]: Error: [chars] invalid value (in parenthesis) was detected.
(Value: [dec])
This value is a decimal number.

Error in gatm operation. The error message

denotes the gatm operation being
unsuccessful with a particular return code
Method: [chars] - Line: [dec]: Error: [chars] string. This string has been used to signify
(return code string: [hex])
the reason of the failed gatm operation.

Error in gatm operation. The error message

denotes the gatm operation being
unsuccessful with a particular return code.
Method: [chars] - Line: [dec]: Error: [chars] The return code has been used to signify
(return code = [hex])
the reason of the failed gatm operation.

[chars]: admin state has changed.

Admin_UP is [chars] for ifh [hex]

Informs about the admin state change. first

%s --> The method name next %s -->
TRUE/FALSE %x --> interface handle.

[chars]: admin up is [chars] oper up is

[chars] for ifh [hex] and main ifh [hex]

Informs about the state changes of the

subinterface. first %s --> The method
name next two %s --> TRUE/FALSE next
two %x --> interface handles for the sub
and main interfaces respectively.

[chars]

ATM SPA GDO L-AIS insertion/removal

notification messages

[chars]

ATM SPA GDO L-AIS insertion/removal

debug messages

GigE hardware initialization failed.

Reason=[chars], Error Decode=[chars]

The GE hardware managment subsystem

encountered an error during initialization.
This process monitors and controls
hardware components required for the RP
management ethernet port. A failure in this
subsystem will disable the the RP's
onboard ethernet. %s - indicates the
reason for the failure %s - indicates the
decoded error reason

GigE hardware packet error.

Reason=[chars]

The GE hardware managment subsystem

encountered an error during receiving of
packets. This process monitors and controls
hardware components required for the RP
management ethernet port. A failure in this
subsystem will disable the the RP's
onboard ethernet. %s - indicates the
reason for the failure

GigE hardware initialization failed.

Reason=[chars], Error Decode=[chars]

The GE hardware managment subsystem

encountered an error during initialization.
This process monitors and controls
hardware components required for the RP
management ethernet port. A failure in this
subsystem will disable the the RP's
onboard ethernet. %s - indicates the
reason for the failure %s - indicates the
decoded error reason

PRP Gigabit Ethernet execution agent

initialization failed. [chars]/[chars]

The PRP Gigabit ethernet execution agent

failed to initialize. The PRP gigabit ethernet
execution agent provides the support for
packet forwarding over the GE port present
on the Performance Route Processor. A
failure of this execution agent likely means
that packets being sent to or from the
PRP's GE ports are going to be lost. %s indicates the reason for the failure %s - is
the decoded error reason

Error: [chars]: Err=[chars]

A error occurred in GSR aib Driver resulting

in a failure to provide some system service
as indicated in the message text. This is
most likely any internal error. %s - reason
for the failure. %s - dll causing the error.

Info: [chars]

This is a Informational message in the GSR

aib driver to indicate an operation.

LSM Clone errir

LSM Clone is NULL.

[chars]: Err=[chars]

An error occurred in Edge fowarding lib

resulting in a failure to provide some
system service as indicated in the message
text. %s - indicates the reason for the
failure. %s - is the decoded error reason.
This error indicates there is problem in LC
Forwarding resources

\nassertion '[chars]' failed in [chars]

([chars]:[dec])

Assertion Failure.

Memory allocation failed for internal data

storage

Memory was not available for an internal

data structure. The requested operation
could not be accomplished because of a
low memory condition. The LC may not
boot up successfully and will not be able to
participate in data forwarding.

[chars] : Hardware initialization of Fabric

interface ASIC failed. Node will be reloaded
for recovery after collecting diag
information

During boot-up or fabric configuration

change or error handling, there was a
problem in the initialization of fabric
interface ASIC. Problem causes the node to
be reloaded and will be restored by itself.

An internal OS library returned an error.

The system will usually recover from this
error automatically. If the frequency of this
alert increases noticeably it could indicate
a OS kernel problem on the card. The LC
will not boot up successfully and will not be
able to participate in data forwarding. This
Internal OS call to create additional threads condition can impact various processes on
failed, [chars]
the LC. The LC is in unstable condition.

An internal OS library returned an error.

The system will usually recover from this
error automatically. If the frequency of this
alert increases noticeably it could indicate
a OS kernel problem on the card. The LC
will not boot up successfully and will not be
able to participate in data forwarding. This
Internal OS call to create additional threads condition can impact various processes on
failed, [chars]
the LC. The LC is in unstable condition.

Call to checkpoint library failed,

status=[chars]

An internal support library returned an

error. The driver was not able to save data
for restart ability. A restart of the FIAD
process may not be NSF compliant. Any
software upgrade requiring FIAD to be
restarted will result in traffic loss. The
system will usually recover from this error
automatically. If the frequency of this alert
increases noticeably it could indicate a OS
kernel problem on the card.

The driver is coming up in normal mode,

but checkpoint information already exists.

When a driver comes up in

NORMAL_MODE, checkpointing data should
not already exist. This indicates a
mismatch in the driver state. The
checkpointed data may be corrupted on
the LC. Restart ability of processes may be
affected.

The driver is coming up in restart mode,

but the checkpoint info does not exist.

When a driver comes up in

RECOVERY_MODE, checkpointing data
should have already been saved to the
checkpointing record by the previous life of
the driver. This can impact the drivers
ability to restart without affecting traffic.

Unsupported devctl case [dec]

An unexpected error has occurred.

Failed to load [chars]

The library (dll) named could not be found

or there was an error while loading.
Indicates a software installation problem.
The LC will not boot up successfully and
will not be able to participate in data
forwarding.

An internal OS library returned an error.

Some error conditions on the LC may not
be reported correctly. The system will
usually recover from this error
automatically. If the frequency of this alert
increases noticeably it could indicate a OS
Internal OS call to process interrupts failed kernel problem on the card.

([chars]): no memory for chip data.

An unexpected error has occurred.

([chars]): FIA failed to initialize memory.

Exiting

An unexpected error has occurred.

([chars]): FIA memory mapping failed.

Exiting

An unexpected error has occurred.

FIA was not reset before programming

An unexpected error has occurred.

([chars]), Illegal size of input for FIA startup

data structure
An unexpected error has occurred.

([chars]): FIA failed to sync, los_status

[hex], los_error [hex], fia_config [hex]

This error usually indicates an internal

hardware problem on the card.

Could not unhalt [chars]

An unexpected error has occurred.

Unsupported cdb version

An unexpected error has occurred.

Unsupported opaque data version

An unexpected error has occurred.

[chars] : [hex]\n

EE192 SerDes retimer driver error. An

internal OS library returned an error. The
system will usually recover from this error
automatically. If the frequency of this alert
increases noticeably it could indicate a OS
kernel problem on the card. The LC will not
boot up successfully and will not be able to
participate in data forwarding. This
condition can impact various processes on
the LC. The LC is in unstable condition.

[chars] : [chars] : [hex]\n

EE192 Spabrg driver error

[chars] : [chars] : [hex] [hex]\n

EE192 Spabrg driver error

[chars] : [chars] : [hex] [hex] [hex]\n

EE192 Spabrg driver error

[chars] : [hex] [hex] \n

EE192 Spabrg driver error

[chars] : [chars] : [hex] [hex]\n

EE192 Spabrg driver single-bit error

[chars] : [chars] : [hex] [hex] [hex]\n

EE192 Spabrg driver single-bit error

[chars] : [hex] [hex] \n

EE192 Spabrg driver error

system database item set failed [chars]

Error in communication channel with the

system database. There was a problem
accessing the named item. This could be a
temporary problem caused by an outage in
the connection to the server. The
connection will be restored, but the
operation itself was aborted.

system database access failed [chars]

Error in communication channel with

clients. There was a problem accessing the
system database item. This could be a
temporary problem caused by an outage in
the connection to the server. The
connection will be restored, but the
operation itself was aborted.

debug init [dec] failed [hex]

debug_init_event failed due to any of the

following 1.Invalid arguements were
passed to the function. 2.Duplicate entries
recieved. 3.mutex init got errored.

debug register failed [hex]

debug_register failed due to event

manager or sysdb error.

[chars]

This is a Informational message in the FIA

Driver to indicate an operation.You need
not take any action.

[chars] failed, slot = [dec], error info =

[chars]

This is a message indicating FIA PCDS a

debugging information collection has faced
a problem.

pcds_get_timestamp failed for fishstick

stats

This is a message indicating FIA PCDS a

debugging information collection has faced
a problem in getting the time stamp to be
associated with the statistics collected.

Recvd test lwm [chars] [dec].\n

Received a light weight message for a

specific port.

[chars] : [chars] : [hex]\n

EE192 Spabrg driver critical info

[chars] : [chars] : [hex]\n

EE192 Spabrg driver informational

message

[chars] : [chars] : [hex], [hex]\n

EE192 Spabrg driver informational

message

[chars] : [chars] : [hex], [hex], [hex]\n

EE192 Spabrg driver informational

message

[chars] failed, slot = [dec], error info =

[chars]

An interprocess call returned an error.

Possibly a timeout. The central switch
fabric software may not recognize the LC
that exhibits this error. Maintenance bus
may not be operating as desired.

Fatal error: [chars]: [dec]

A fatal error occurred during GT64115 PCI

Driver cofiguration %s - error message %d data

Fatal error: [chars]

A fatal error occurred during GT64115 PCI

Driver initialization %s - PCI init error
message

PCI Bridge Intr: [chars] [dec] [dec]

This is an error message resulted from an

interrupt from the PCI device. %s - Info
message %d - Interrupt %d - Interrupt
mask

Fatal error: [chars]: [chars]: [dec]

A fatal error occurred in gulf Driver which

involves exiting the process.

An error occurred in gulf Driver which

Underrun Interrupt Occured on Port [hex]\n involves exiting the process.

warning: [chars]: [chars]: [dec]

A warning condition is detected in gulf

Driver which involves exiting the process.

Info: [chars]: [chars]: [dec]

This is a Informational message in the gulf

driver to indicate an operation.

Debug: [chars]: [chars]: [dec]

This is a debug message in the gulf driver

to indicate anomolies which are not FATAL.
Some of the messages may indicate a
failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temperory situation is resolved.

[chars] , [chars], [chars]

This message indicates a failure in

allocating memory for MQS extension. The
causes for this error could be lack of
memory or a hardware resource.

[chars], [chars], Route ([chars],[chars])

This message indicates a failure in

committing route (S, G). This means QoS
feature will not be applied for the specified
route; Traffic through this route would go to
the default queue. The causes for this error
could be lack of memory, a hardware
resource limitation, or an internal error. %s,
%s - indicates the (S, G)

[chars] , [chars], [chars]

This message indicates a failure in

allocating memory for QOS extension. The
causes for this error could be lack of
memory or a hardware resource limitation.

[chars] , [chars]

This message indicates a failure in

allocating memory for replicorder
extension. The causes for this error could
be lack of memory or a hardware resource
limitation.

\nassertion '[chars]' failed in [chars]

([chars]:[dec])

Assertion Failure.

[chars] , [chars]

This message indicates a failure in

allocating memory for TCAM extension. The
causes for this error could be lack of
memory or a hardware resource limitation.

[chars]: [chars]

A SW exception occurred in TCAM

extension Library

\nassertion '[chars]' failed in [chars]

([chars]:[dec])

Assertion Failure.

Alpha SDRAM assertion failed for bcc:

Address:[hex] Source:[chars] Group:[chars]
bidir cluster: [hex] cluster:[hex] bmainfo:
[hex]
Assertion failed for BCC in Alpha SDRAM

Alpha SDRAM assertion failed for bcc qc:

Address:[hex] Source:[chars] Group:[chars]
qos cluster:[hex] bidir cluster: [hex] cluster:
[hex] bmainfo:[hex]
Assertion failed for BCC QC in Alpha SDRAM

Alpha SDRAM assertion failed for def

cluster: Address:[hex] Source:[chars]
Group:[chars] cluster:[hex] bmainfo:[hex]

Assertion failed for def cluster in Alpha

SDRAM

[chars] , [chars]

This message indicates a failure in

allocating memory for TLU extension. The
causes for this error could be lack of
memory or a hardware resource limitation.

\nassertion '[chars]' failed in [chars]

([chars]:[dec])

Assertion Failure.

Fatal error: [chars]: Err=[chars]

A fatal error occurred in HFA common

Driver which involves exiting the process.

[chars] failed to construct fromfab

mapping\n

Failed to create the sid to hardware queue

mapping.

[chars] failed to publish [chars]\n

Failed to publish the hardware queue to

QMM.

[chars]

A SW exception of unexpected condition or

an out of resources (memory, HW profiles,
etc) situation.

[chars] [chars]

This is a Informational message in the HFA

common Driver to indicate an operation.

[chars] err [hex]

This is a Informational message in the HFA

common Driver to indicate an operation.

HFA BLWM message failure

Software exception. Quite probably a SW

bug.

Unable to configure BLWM client

hfa: blwm client configuration failed, error: functionality.Will not be able to send any
[hex] [chars]
BLWM mesages from HFA.

hfa: blwm client rebind failed, error: [hex]

[chars]

Unable to rebind with BLWM client

functionality after a connection reconnect.
Will not be able to send any BLWM
mesages from HFA.

hfa: blwm msg send/flush: retried: [dec]

time(s), failed to send, error: [hex] [chars]

Unable to send/flush a BLWM message to

the HFA server.

hfa: Received a failure reply code for a

batched request, reply code: [dec]

This is the message printed by the default

handler installed by HFA to process the
replies received for batched requests. The
default handler's behavior is to just print
this message. The BLWM might be
processed completely but the return code
in the reply message indicates failure. The
application should install its own handler to
handle the replies to batched requests.

hfa: msg: [dec], retried: [dec] time(s),

failed to send, errno: [chars]

Unable to send a message to the HFA

server.

Error action should[chars] have parameter, The action does not have the parameter
size:[dec]\n
and the correct size.

hfa: Replaying a batched request of type

[dec] that might have been partially
processed before.

Due to a server restart, a batched request

might have been partially processed. The
default handler installed by HFA simply
replays the request. Applications that can
not afford to replay a request should install
their own handler.

[chars] error on [chars], rc=[dec]

An error occurred when un/locking HFA HW.

Some of the Harware programming may be
inconsistent.

[chars]: [dec]

This is a Informational message in the HFA

client LIB to indicate an operation.

Fatal error: [chars]: [chars]: [dec]

A fatal error occurred in plim pos 4p oc12

Driver which involves exiting the process.

Info: [chars]: [chars]

This is a Informational message in the plim

pos 4p oc12 driver to indicate an operation.

Debug: [chars]: [chars] errno [dec]

This is a debug message in the plim pos 4p

oc12 driver to indicate anomolies which are
not FATAL. Some of the messages may
indicate a failure to allocate resources
needed by applications. In many cases
these messages must not keep appearing
after the temperory situation is resolved.

Failed to build [chars]: [chars] ([chars])

Internal error in the routing policy library.

There was an internal error in the routing

Failed to build ORA[chars]: [chars] ([chars]) policy library.

Could not apply policy operation [chars] to

attribute [chars] because [chars]
Internal error in the routing policy library.

Applications are providing state change to

the layer 2 multicast data plane hardware
faster than the hardware can be
programmed. Internal message to the
hardware have been dropped such that
IGMP snooping state is now out of sync
with the hardware. The user must slow the
rate of IGMP state change being received
by the system. The system will
automatically recover from this condition
Layer 2 multicast data plane programming once the rate of IGMP state change has
congestion
been reduced.

Initialization failed: [chars]

An error occurred during initialization.

These errors include timers, L2FIB or
packet i/o.

Initialization failed: [chars], [chars]

An error occurred during initialization of the

port details or bridge-domain details or
igmp snooping profile.

[chars] : [chars]

This error indicates that the igmp snooping

process failed to send out a packet or a
pulse.

Error initializing the system database:

[chars]

An error occurred when initializing the

system database or we failed to scan the
igmp snooping configs.

The layer 2 multicast data plane hardware

Layer 2 multicast data plane programming programming has been resynced with the
congestion cleared
state in the IGMP snooping application.

IMA Group [chars] with bandwidth [dec].

Link ifh [hex] with bandwidth [dec]

When the indicated member link was

deactivated, group bandwidth could not be
updated correctly as decrementing the
link's bandwidth would have made the
group bandwidth to go below zero. Group
bandwidth is now made zero.

Failed to add/remove member link [chars]

into ima group [chars]

The link addition/removal from a IMA Group

has failed due to a software error.

Failed to set MTU of [unsigned int] on

[chars]

The specified MTU could not be applied on

this interface.

[chars]: [chars] [chars]

The specified IMA Alarm has been declared

or released.

[chars]([dec]): not enough memory for

[chars]

The process is out of memory.

[chars]([dec]): [chars] failed ([chars]) [chars]

A general failure occured while executing

the function in question. The message
contains info about the location and cause
of the failure and possibly anticipated
actions/effects.

[chars]: [chars] [chars]

The specified IMACTRLR Alarm has been

declared or released.

[chars]: [chars] [chars]

The specified IMACTRLR is operationally

down due to alarm. Check alarm status
using show controller Mlt command on the
cli.

[chars]([dec]): [chars] - [chars]

A non-fatal error occured while executing

the function in question. The message
contains info about the location and cause
of the failure and possibly anticipated
actions/effects.

IOB Intr: [chars]

The IOB FPGA has been interrupted due to

an access fault %s - error message

Unknown IOB Intr: [chars]: [dec]: [dec]

This is a message in the IOB FPGA driver to

indicate that it has detected an unknown
interruption %s - description %d - level %d
- mask

Failed to initialize [chars], because of

[chars]

Initialization process such as getting an

evm failed.

'Failed to initialize [chars], because of

[chars]'

Initialization process such as getting an

evm failed.

'IPv6 EA failed to program '[chars]' due to

low memory'

The IPv6 EA process could not allocate

memory needed to program some IPv6
feature.

'Platform update failed: [chars] - [chars]

(<<CH[hex]>>)'

Platform update failed.

'Platform update failed for [dec] interface:

[chars] - [chars]'
Function [chars] failure errno [chars]

Platform update failed for all interfaces in a

batch.
IPCP communication failure.

Nonfatal error: [chars] error code [dec]

This is a error message of the IXP2800

forwarding driver to indicate either
anomalies which are not fatal. Some of the
messages may indicate a failure to allocate
resources needed by applications.

Test DLL failed to open log file [chars]

([chars])

The NPU test DLL failed to open the log file

Function [chars] invoked

An unexpected function invocation occured

ixp2800 HW driver Could not allocate

memory

'ixp2800 HW driver has failed to aquire the

required amount of memory.'

[chars]()[[dec]]: [chars]: [chars] ([dec])

A fatal error occurred in IXP2800_HW Driver

which involves exiting the process.

[chars]()[[dec]]: [chars]: [chars] ([dec])

A warning condition occurred in

IXP2800_HW Driver which involves exiting
the process.

[chars]

SERVICE card ixp2800_hw driver

informational message

ixp2800 HW driver DLL failed to open log

file [chars] ([chars])

The NPU HW driver DLL failed to open the

log file

'ixp2800 service has failed to aquire the

ixp2800 service Could not allocate memory required amount of memory.'

[chars]()[[dec]]: [chars]: [chars] ([dec])

A fatal error occurred in IXP2800_SERVICE

Driver which involves exiting the process.

[chars] Fatal error - [chars]

A fatal error occurred in SPU common

Driver

Function [chars] failure errno [chars]

IPCP communication failure.

[chars]()[[dec]]: [chars]: [chars] ([dec])

A warning condition occurred in

IXP2800_SERVICE Driver which involves
exiting the process.

[chars]

SERVICE card ixp2800_service driver

informational message

ixp2800 service DLL failed to open log file

[chars] ([chars])

The NPU service DLL failed to open the log

file

[chars] FPGA is running rollback image, no The FPGA is running rollback image, this
SPA in jacket will be UP before the FPGA is could be caused by previous FPD failure.
upgraded to the correct version
%s - device name, Rx MAC or Tx MAC.

FPGA software revision mismatch, the

FLEX-PLIM may not be fully functional, to
upgrade fpga Use the upgrade hw-module
fpd CLI in admin mode

The FPGA software revision is different with

the one supported by the running software,
this could be caused by software upgrade
which supports the new FPGA software
revision.

Failed to [chars] to jacket process

Client to the SPA THOR jacket process had

a communications failure

Failed to initiliaze CPU Ctrl: err [chars]

Unable to initialize CPU Ctrl device.

Failed to [chars] CPU Ctrl register id [dec]:

err [chars]

Unable to enable/disable/clear a CPU Ctrl

interruprt register.

Failed to [chars] CPU Ctrl register id [dec]:

err [chars]

Unable to read/write to a CPU Ctrl register.

Failed to enable CPU Ctrl register lock: err

[chars]

Unable to obtain register access lock for

CPU Ctrl.

[chars]: [chars]: [hex]

A critical error occurred in jacket driver

which involves exiting the process. The
jacket driver will restart and unless the
same error occurs on the next attempt the
driver will function normally. If the error is
persistent, it indicates the system error or
HW error which needs further investigation.

SPA Jacket init failure :[chars]

SPA Jacket error

IMDR SIP hardware init :[chars]: [chars]

failed

Error encountered during iMDR SIP upgrade

Internal error with [chars] in [chars](), at

line [dec]

Internal error has occured

A critical error occurred while accessing the

hardware in jacket driver which involves
exiting the process. The driver will restart
and attempt normal functionality. If the
error is transient, the jacket driver and the
SPAs will continue normal operation. If the
Asic PIO failure : [chars], instance [dec]: rc error is persistent, the jacket card hardware
[dec] cerr [chars] errno [dec] data1 [hex]
needs to be checked out for access
data2 [hex]
failures.

SPA subslot [dec]: FAILED: [chars] for

[chars]

A critical error occurred in jacket driver

rules validation for a SPA which results in
the SPA not being enabled. This does not
affect the other slots on the jacket card.
Please check the SW support for the SPA
slot for which this message is seen.

[dec] requests to disable SPA [dec] due to

spa bus error

This is an error message indicating a

Hardware access error for a SPA and
disable the SPA to avoid LC reload

SPA subslot [dec]: had [chars] error when

accessing address [hex] with fault code
[dec]

This is an error message indicating a

Hardware access error for a SPA. If this is a
recurrent message, it usually is due to
faulty hardware, loose connection at the
SPA connector on the jacket card. Try
reseating the SPA and see if the issue is
resolved. If not, please check with TAC.

SPA [dec] is being reset due to spa bus

error

This message indicates an error on spa bus

for which internal recovery action (i.e., SPA
reset) has been initiated.

This is an error message indicating a

Hardware access error for a SPA. If this is a
recurrent message, it usually is due to
faulty hardware, loose connection at the
SPA connector on the jacket card. Try
[chars] has requested to disable SPA [dec] reseating the SPA and see if the issue is
due to spa bus error
resolved. If not, please check with TAC.

SPAQFP Bridge error in SPA [dec]: [chars]

SPAQFP bridge has encounted an error in

SPA related operation

SPA QFP Bridge [dec] init failed: [chars]

SPAQFP Bridge has encounted an error

during initialization

Failed to bind to the QFP SPA bridge

controller server: [chars]

Failed multiple attempts to bind to QFP SPA

bridge controller server

Failed to bind to the QFP generic interface

client library: [chars]

Failed to bind to the QFP Generic Interface

Client

Failed to acknowledge a requested from

the QFP high availability server: [chars]

After servicing a request from the QFP high

availability server, the acknowledgement
of the request failed

Failed to bind to the QFP high availability

server: [chars]

Failed to bind with the QFP high availability

infrastructure

Failed to allocate [unsigned int] bytes for

'[chars]'

The process failed to allocate memory for

the specified resource

SPA bridge controller [unsigned int] failed

to find [chars] QFP connection: [chars]

Failed to find existing QFP connection

Failed to configure the SPA bridge

controller: [chars]

Failed to configure attributes on a SPA

bridge controller

Failed to notify the QFP about SPA bridge

controller [unsigned int]: [chars]

The line card initialization sequence failed

to discover a SPA bridge controller

Failed to remove SPA bridge controller

[unsigned int]: [chars]

Failed to remove a SPA bridge controller

Failed to update the QFP about SPA bridge

controller [unsigned int]: [chars]

Failed to update the QFP SPA bridge

controller client about the SPA bridge
controller initialization

Failed to inform QFP about [chars] of SPA

from bay [unsigned int]: [chars]

Failed to propagate information about SPA

insertion or removal

Invalid internal structure for bay on SPA

[chars]

Null pointer to data structure when

attempting to update SPA status

SPA bridge controller [unsigned int] failed

SP4I RX PHY reset on QFP SPI4 link
[unsigned int]: [chars]

Failed enable/disable interrupts on the

specified SPI link

SPA bridge controller [unsigned int] failed

to [chars] on QFP SPI4 link [unsigned int],
direction [chars]: [chars]

Failed enable/disable specified SPI4 link

Failed to [chars] SPI4 [chars] interrupts for Failed to enable/disable interrupts on the
SPA bridge controller [unsigned int]: [chars] specified SPI4 link

Failed to synchronize SPI4 bus between SPA

Failed to synchronize SPI4 bus between SPA bridge controller and packet processing
bridge controller [unsigned int] and QFP
engine

SPA Bridge controller [unsigned int] QFPSPI4 synchronization check failed in [chars] The SPA bridge controller detected a SPI4
direction: [chars]
error between itself and QFP
SPA subslot [dec]: [chars] for [chars], driver This is an informational message in the
[chars]
jacket driver to indicate an operation.

[chars]: [chars]

This is an informational message in the

jacket driver to indicate an operation.

SPA [chars] is not allowed in bay [dec]:

[chars]

Either an unsupported SPA was inserted, or

an error occurred when a full rate SPA and
another SPA tried to use the same SPA
bridge controller resources. This is not
allowed due to bandwidth limitations. SPA
bays 0 and 2 share one controller, and SPA
bays 1 and 3 share a second controller.

Thor jacket process Spa FPD upgrade

procedure :[chars]

Upgrade SPA FPGA message

Debug: [chars]: [chars] errno [dec]

This is a debug message in the jacket

driver to indicate anomolies which are not
critical. Some of the messages may
indicate a failure to allocate resources
needed by applications. In many cases
these messages must not keep appearing
after the temperory situation is resolved.

[chars]:[dec] ERROR RETURN

This error message indicates an error

condition in JDAM driver which says
Memory allocation failed - Null pointer
returned

[chars]:[dec] fail:[chars]

This error message indicates an error

condition in JDAM driver which says the
check point library initialization has failed.

Fatal error: [chars]: [chars]: [dec]

A fatal error occurred in JDAM Driver which

involves exiting the PLIM process.

Invalid VC Type 4 for Port mode.. Can not

handle\n

This error message indicates that it is not a

valid JDAM vlan type. Hence, cannot
handle.

[chars] [dec] No memory

No free memory available for JDAM vlan

hash entry

[chars]: vlan_table_ptr null for [dec]

JDAM VLAN Table Pointer is NULL

[chars] [dec] failed port [dec]

Updating Tcam entry into the tcam table

failed for this port.

port_mapping. Bad port number [dec],

ignoring.\n

This error message indicates an error

condition in JDAM driver. Ignoring Port
Mapping due to bad portnumber. The port
number should be between 0 and 3.

[chars]: error port:[dec] is out of range

This error message indicates an error

condition in JDAM driver. Port number is out
of range. It should be between 0 and 3.

JDAM TCAM invalid shm index

Invalid shared memory index for JDAM

tcam entry.

JDAM TCAM invalid shm address

Invalid shared memory address for JDAM

tcam entry

VLAN entry: invalid shm address

Invalid shared memory address for JDAM

vlan entry

VLAN entry: no more shared memory

No more shared memory available to store

JDAM vlan information.

No more shared memory available for JDAM

VLAN TCAM entry: no more shared memory vlan tcam entry

[chars] [chars] [dec]

This is a Informational message in the JDAM

driver to indicate an operation.

-----jdam_sb_info (top=[dec] ,
objid=[dec])---\n vlan_id_outer=[dec],
vlan_id_inner=[dec] \n
vlan_prio_enable=[dec],
vlan_prio_vector=[dec],
uidb_index=[dec]\n l2_op=[dec],
tunnel_enable=[dec], l2pt_enable=[dec],
permit=[dec]\n
pbits_shim=[dec],pbits_shim_sel=[dec],ce_
vlan_sel=[dec],crc=[dec]\n pbits_rw=[dec],
vlan_rw==[dec], l2_tunnel==[dec],
punt==[dec]\n jdam_vlan_rx_index=[dec], This message prints the JDAM sub-block
jdam_vlan_tx_index=[dec]\n
information on the console

l2sram=[unsigned int],
old_val_pro=[unsigned int],[unsigned long
long int]\n old_val_anti= [unsigned long
long int], [unsigned long long int],
old_val_over=[unsigned long long int],
This message prints the JDAM vlan tcam
[unsigned long long int]--\n
information.

--tcam_element[[dec]]--\n

This is just an informational message which

prints the JDAM tcam element number.

Debug: [chars]: [chars] errno [dec]

This is a debug message in the JDAM driver

to indicate anomolies which are not FATAL.
Some of the messages may indicate a
failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temperory situation is resolved.

Misconfiguration: Item [chars] on interface

[chars] is incompatible with other
configuration. The system may now be in
an inconsistent state.

The L2VPN Uberverifier has detected a

misconfiguration. It was not detected in the
verification phase, so the Uberverifier
cannot correct this.

Event loop error: [chars]

The L2VPN Uberverifier has encountered a

problem in its event loop and cannot
continue. In this situation it should restart.

Failed to initialize [chars]: [chars]

The L2VPN Uberverifier process failed to

initialize correctly. In this situation it
restarts, but may not recover if there is a
persistant error in the IOS-XR system and
the L2VPN Uberverifier is later unable to
reestablish its connections and initialize
successfully.

Some error occurred in operations related

to Shared Memory area, such as debug
intialization failed. This could have
occurred due to overuse of memory. This
can result in - 1) Not programming
hardware for proper forwarding. 2) Not
L2FIB Shared Memory Error, [chars]: [chars] creating new bridge.

L2FIB has run out of [chars] resource

memory. No more updates will be handled
by the L2FIB. Please delete ACs to resume
normal operation on this node

The l2fib_mgr process on the node has

detected an out of resource condition for
the indicated resource. Normal operation
cannot resume until routes are deleted.

'L2FIB cannot handle updates, because a

necessary process is restarting. ' 'Normal
operation will resume on this node once
the process has restarted'

The l2fib_mgr process on the node has

detected that a process required to handle
updates is restarting. Normal operation will
resume once the process has restarted.

Some error occurred in operations related

to Shared Memory area such as Shared
Memory lock/unlock, Shared Memory
corruption, memory allocation or freeing
Shared Memory. This could have occured
due to overuse of memory. This can result
in- 1) Not programming hardware for
L2FIB Shared Memory Error, [chars] failed: proper forwarding. 2) Not creating new
[chars]
bridge.

L2FIB API Error, [chars]

This error could have occurred due to

specifying invalid object

The l2fib_mgr process has detected that

average utilization for specified resource
has risen above a predefined high
watermark value, and has entered resource
L2FIB running low on [chars] resource
contrained forwarding mode. In this mode,
memory. L2FIB will now begin resource
the l2fib will only handle route deletes
constrained forwarding. Only route deletes which may potentially freeup some
will be handled in this state, which may
memory. Due to this operational mode, the
result in mismatch between L2VPN
L2VPN mgr/AIB/L2FIB and L2FIB will be out
mgr/AIB/L2FIB and L2FIB. Traffic loss on
of sync. Once ACs are deleted and resource
certain ACs can be expected. The L2FIB will utilization level drops to acceptable levels
automatically resume normal operation,
again, l2fib will come out of this
once the resource utilization returns to
operational mode and resume normal
normal level
operation.

BDXC Error, [chars]

An IPC between L2FIB and its client process

failed; the message will be retried. If the
error message appears just once, it can be
ignored as IPC between L2FIB and its client
process will be retried and connection will
be established. But if the error message
recurs, it could mean that IPC mechanism
has failed.

Some error occurred in operations related

to Shared Memory area. This could have
occurred due to overuse of memory. This
can result in- 1) Not programming
L2FIB Shared Memory Error, [chars] failed: hardware for proper forwarding. 2) Not
[chars]
creating new bridge.

L2FIB initialization failure: [chars] [chars]

This error message is thrown when,

resource monitor initialization failed to
intialize the shared memory or when we
fail to get l2fib timestamp.

L2FIB thread [chars] received an invalid

message: [chars] [unsigned int]

L2FIB thread got an invalid message.

L2FIB shared memory initialization failed:

[chars]

L2fib shared memory initialization failed

because server failed to map shared
memory. If shared memory is not
initialised, it can result in wastage of
shared memory.

L2FIB BDXC Error, [chars]: [chars]

This L2FIB error has occurred due to errors

in BDXC (Bridge Domain Cross-connect)
operations.

L2FIB IMC Error, [chars]: [chars]

An error occurred in the L2VPN manager

while communicating with the system
interface management service.

L2FIB Internal Software Error, [chars]

An internal software error occurred in L2FIB

manager process. This could be due to an
internal processing error or an illegal state
has been detected.

L2FIB IRB Error, [chars]: [chars]

This error occurred due to inconsistent IRB

(Integrated Routing and Bridging)
information being received. This could
result in improper routing of protocol
between routed interfaces and bridges.
This could have happened due to improper
configuration of BVI (Bridge Virtual
Interface)

L2FIB MCAST gtrie Error, [chars]: [chars]

An error occurred in L2FIB manager process

due to failure in initialization of ipv4
multicast gtrie. This could have happened
if gtrie has not been registered properly to
the L2FIB manager.

L2FIB Pulse Error, [chars]: [chars]

An error has occurred in the L2FIB manager

process due to a failure to attach a pulse
handler to a process.This could have
happened due to following reasons: 1)
Pulse code could be out of range 2)
Insufficient memory

L2FIB MCAST/EVPN Route Handler Error,

[chars]: [chars]

An error occurred in the L2FIB manager

process. This could have occurred due to
failure in receiving a valid route type for
Multicast or EVPN. The message may not
be delivered correctly if this error occurs.
The error message prints the name of the
route type.

Error occurred in operations related to

Shared Memory area. Initialization of the
server side of shared memory failed. This
could have happened due to overuse of
memory. This results in - 1) Not
L2FIB Shared Memory Error, [chars] failed: programming hardware for proper
[chars]
forwarding. 2) Not creating new bridge.

[chars] failed due to version mismatch:

[hex]

The platform-dependent FIB failed to free

shared memory due to a version mismatch.
This could eventually lead to memory
exhaustion.

L2FIB Statistics Error, [chars]: [chars]

This error occurs when client or DLL

initialization fails.

Dynamic ARP inspection in AC [chars]

detected violated packet - source MAC:
[chars], destination MAC: [chars], sender
MAC: [chars], target MAC: [chars], sender
IP: [chars], target IP: [chars]

The dynamic arp inspection in attachment

circuit has detected violated packet. This
might be a security attack. The packet
failed dynamic arp inspection has been
dropped.

IP source guard in AC [chars] detected

The IP source guard in attachment circuit
violated packet - source MAC: [chars],
has detected violated packet. This might
destination MAC: [chars], source IP: [chars], be a security attack. The packet failed IP
destination IP: [chars]
source guard inspection has been dropped.

The MAC secure in attachment circuit has

detected violated packet. This might be a
security attack. A relearn attempt had been
made on the attachment circuit for a MAC
address which had been already learned by
another secure port. One of following
action might be configured and will be
taken on this attachment circuit: - Restrict:
drop the packet and disable the learn
attempt - None: forward the packet and
allow the MAC to be relearned - Shutdown:
shutdown the port on which the learn
MAC secure in AC [chars] detected violated attempt was made If no action has been
packet [chars]- source MAC: [chars],
configured, the restrict action will be taken
destination MAC: [chars]; action: [chars]
by default and packet has been dropped.

The MAC secure in the Virtual Instance Port

has detected violated packet. This might
be a security attack. A relearn attempt had
been made on the Virtual Instance Port for
a MAC address which had been already
learned by another secure port. One of
following action might be configured and
will be taken on this Virtual Instance Port: Restrict: drop the packet and disable the
learn attempt - None: forward the packet
and allow the MAC to be relearned Shutdown: shutdown the port on which the
MAC secure in PBB Virtual Instance Port on learn attempt was made If no action has
bridge id [unsigned int] detected violated been configured, the restrict action will be
packet [chars]- source MAC: [chars],
taken by default and packet has been
destination MAC: [chars]; action: [chars]
dropped.

MAC secure in PW neighbor: [chars], ID:

[unsigned long int] detected violated
packet [chars]- source MAC: [chars],
destination MAC: [chars]; action: [chars]

The MAC secure in the pseudowire has

detected violated packet. This might be a
security attack. A relearn attempt had been
made on the pseudowire for a MAC address
which had been already learned by another
secure port. One of following action might
be configured and will be taken on this
pseudowire: - Restrict: drop the packet and
disable the learn attempt - None: forward
the packet and allow the MAC to be
relearned - Shutdown: shutdown the port
on which the learn attempt was made If no
action has been configured, the restrict
action will be taken by default and packet
has been dropped.

The resynchronization of the MAC address

table is complete [chars]

The command to resynchronize the MAC

address table may take a while to
complete. This message indicates that
resynchronization is complete and the MAC
address table can be displayed..

XC/BP delete-and-create: [chars]

The L2VPN provision message has been

handled by deleting the old Crossconnect/Bridge port, and creating a new
one.

L2TP initialization failure: [chars] [chars]

L2TP initialization failed

Invalid l2tp-class [chars] for new session;

expecting [chars]

A new session maps to an existing L2TP

tunnel, but the session references a L2TP
class different than what this tunnel is
using.

[chars]: [chars]

An internal software error occurred

L2TP internal error: [chars]

An internal software error occurred

L2TP IPC transport error: [chars] [chars]

An IPC transport software error occurred

No acknowledgement for transmission of

L2TPv2 tunnel accounting records

L2TP has not received acknowledgements,

either positive or negative, for tunnel
accounting records it sends to Radius in an
extended period of time.

L2TP has no source IP for [chars]

CEF lookup has returned no suitable source

IP for L2TP to use

L2TP [chars] received an L2TP [chars]

packet
Debug library cleanup error: [chars]

A packet is delivered to local L2TP stack,

but it is meant for a different version of
L2TP protocol
Debug library cleanup failed

Debug libraray initialization error: [chars]

Debug library initialization failed

Ltrace library initialization error: [chars]

Ltrace library initialization failed

L2VPN Redundancy iccp-group [dec]

[chars] VLAN configuration mismatch has
cleared.

Mis-configuration under l2vpn redundancy

has been cleared. The primary set of VLANs
now matches the secondary set of VLANs
on the other member of the redundancy
group.

Received an invalid multi-homing node-id

[dec] from group [dec].

One or both of the PoAs in the redundancy

group have an invalid node-id.

Misconfiguration caused by an invalid

multi-homing node-id [dec] from group
[dec] has cleared.

The misconfiguration that had been caused

by invalid multi-homing node IDs has
cleared either through local configuration
or by the remote peer.

L2VPN Redundancy iccp-group [dec]

[chars] VLAN local configuration mismatch.
Primary and Secondary VLANs have been
set to blocking.

The set of primary or secondary VLANs on

a bundle interface of the iccp-group does
not match the secondary or primary set of
VLANs for the same bundle interface on the
other member of the redundancy group.

L2VPN Redundancy iccp-group [dec]

[chars] VLAN remote configuration
mismatch. Primary and Secondary VLANs
have been set to blocking.

The set of primary or secondary VLANs on

a bundle interface of the iccp-group does
not match the secondary or primary set of
VLANs for the same bundle interface on the
other member of the redundancy group.

A configuration conflict has been detected:

Interface [chars] is already used by the
MCLAG feature. ICCP-SM will not work until
the conflict is resolved.

A configuration conflict has been detected:

Interface %s already used ' ' by MCLAG
feature. ICCP-SM will not work until the
conflict is resolved.

A configuration conflict has been cleared:

Interface [chars] can be used by ICCP-SM
feature.

A configuration conflict has been cleared:

Interface %s can be used by ' 'ICCP-SM
feature.

ICCP-SM has detected a local Access Main

Port failure: Attempting to failover [chars]
ports in redundancy group [dec]

ICCP-SM has detected a failure with the

interface main port and has attempted to
failover.

ICCP-SM has recovered from local [chars]

main-port failure. Attempting to recover
ports in redundancy group [dec].

ICCP-SM has recovered from the local

access failure and has attempted to
recover the ports in the redundancy group.

ICCP-SM Local Core Isolation Failure.

Attempting to failover [chars] ports in
Redundancy group [dec].

ICCP-SM has detected isolation in the core

and has attempted to failover.

ICCP-SM has recovered from a local core

isolation failure. Attempting to recover
[chars] ports in redundancy group [dec].

ICCP-SM has recovered from local core

isolation and has attempted to recover the
ports in the redundancy group.

A configuration conflict has been detected:

Interface [chars] is already used by the
ICCP-SM feature. MCLAG will not work until
the conflict is resolved.

A configuration conflict has been detected:

Interface %s already used by ICCP-SM
feature. MCLAG will not work until the
conflict is resolved.

A configuration conflict has been cleared:

Interface [chars] can be used by MCLAG
feature.

A configuration conflict has been cleared:

Interface %s can be used by ' 'MCLAG
feature.

ICCP-SM has detected a peer node

restored: Attempting to recover [chars]
ports in redundancy group [dec]

ICCP-SM has detected that the peer node

has been restored and has attempted to
recover the ports in the redundancy group.

ICCP-SM has detected a peer node failure:

Attempting to failover [chars] ports in
redundancy group [dec]

ICCP-SM has detected a failure with the

peer node and has attempted to failover.

ICCP-SM has detected a remote Access

Main Port failure: Attempting to failover
[chars] ports in redundancy group [dec]

ICCP-SM has detected a failure with the

access main port and has attempted to
failover.

ICCP-SM has recovered from remote [chars] ICCP-SM has recovered from the remote
main-port failure. Attempting to recover
access failure and has attempted to
ports in redundancy group [unsigned int]. recover the ports in the redundancy group.

ICCP-SM Remote Core Isolation Failure.

Attempting to failover [chars] ports in
Redundancy group [dec].

ICCP-SM has detected isolation in the

peer's core and has attempted to failover.

ICCP-SM has recovered from a remote core ICCP-SM has recovered from remote core
isolation failure. Attempting to recover
isolation and has attempted to recover the
[chars] ports in redundancy group [dec].
ports in the redundancy group.

pwhe_ma process initialization failure,

Error: ([hex]): [chars]

An error has happended while initializing

L2VPN MA PWHE process. pwhe_ma will be
restarted automatically.

Interface replication failure; interface

name: [chars]; error code: [chars].

An interface replication failed with the error

code displayed in the message. The error
might have been caused by a
misconfiguration or a lack of resources. The
replication might have failed for more than
one interface; only one interface name and
one error code are included in each
instance of this message.

Replication done for interface [chars].

The interface mentioned in the message

has been successfully replicated, and
recovered from previous failed attempt.

Pseudowire with address [chars], id [chars], L2VPN Pseudowire state is changed to UP

state is changed to: [chars]
or DOWN

An existing PW configured with same pw-id

[chars] and neighbor with LDP router-id
[chars] (Cfg Dest [chars]) is moved to UR
state.

The system is configured with multiple PWs

with same pw-id and with neighbor
addresses that are owned by the same LDP
peer. This configuration is invalid and the
last configured PW is maintained.

Pseudowire with address [chars], id [chars], L2VPN Pseudowire state is changed to

state is changed to: StandBy
standby.
Pseudowire with address [chars], id [chars], L2VPN Pseudowire state is changed to
state is changed to: StandBy-Ready
standby-ready.
PWHE EA failed to program interface
<<CH[hex]>> after [unsigned int] retries: The PWHE EA has failed to program a pwhe
[chars].
interface after 1 or more retries.

PWHE EA process failed to update the state The PWHE EA process failed to update the
of interface [unsigned int]: '[chars]'
state of a tunnel interface.

The PWHE EA process failed to initialize a

PWHE EA process failed to initialize [chars]: critical component. The process cannot
'[chars]'
proceed and will restart to recover.

PWHE EA has retried [unsigned int] times

to update interface <<CH[hex]>>.

The PWHE EA process has retried

programming PWHE interface(s) because
other processes are not ready.

[chars] process shutting down due to

'Critical' memory state.

The system has notified a process that it is

critically short of memory and the process
is shutting down.

L2VPN problem registering bag(s): [chars]

L2VPN encountered a problem registering

the data containers (bags) for show
commands. The text of the message
displays the decoded return code.

L2VPN ID MGR attempted to remove an

unknown key [chars].

L2VPN ID Mgr keeps track of IDs for

different features. A key was attempted to
be removed that it does not know about.

[chars] process being re-spawned due to

problem initialising: [chars] returned
[chars].

The process encountered a problem in the

main event loop with a basic initialisation
or with an event/event manager/event
connection operation and has exited. The
text of the message displays the process
and operation which failed to complete
successfully with the decoded return code.

L2VPN sanity check failed for Pseudowire ID An internal error has been encountered and
[chars] pw-id [chars]: [chars]. Limit is [dec] the Pseudowire cannot be established.

L2VPN problem binding to SysDB for the

provided path: '[chars]', and received the
following message [chars]

L2VPN attempted to bind with SysDB at the

specified path and could not establish a
connection. The text of the message
displays the specific bindpoint and the
decoded SysDB return code. As L2VPN was
not successful in connecting using this
path, configuration or show commands
specific to this path will not be handled by
L2VPN.

L2VPN problem registering with SysDB,

'[chars]' returned the following message
[chars]

L2VPN could not register callbacks with

SysDB for show command or configuration
handling. The text of the message displays
the registration operation attempted and
decoded SysDB return code.

Bridge-domain [chars]: [chars] virtual MAC

([chars]) conflicts with another interface
The HSRP or VRRP MAC conflicts with that
static mac address
of another interface in the bridge-domain.

Potential MST forwarding loop in Bridge

Domain [chars] (BD ID: [unsigned int]) for
interface [chars] and msti: [unsigned int]

A potential mis-configuration with more

than one sub-interfaces in this bridge
domain from the same main port and
having the same msti value.

[chars] mtu of [dec] does not match bridge The interface MTU does not match the
mtu of [dec]
bridge payload MTU.

Pseudowire encapsulation is deleted, nonstatic pseudowires attached with pw-class

'[chars]' will become unresolved

Encapsulation in the pw-class is deleted, all

non-static pseudowires attached with this
pw-class will be unresolved as
encapsulation type becomes unspecified.

L2VPN manager is unable to re-connect

with peers via ENS/GSP

'L2VPN manager is unable to re-connect

with peers via ENS/GSP due to ENS API
failures. Will retry.'

Number of MAC addresses in the

attachment circuit has reached the
Number of MAC addresses in AC '[chars]'
configured maximum. Since 'shut' action
has reached the configured MAC limit
has been configured for MAC limit event on
maximum and hence it has been shutdown the port, it has been shut down.

Number of MAC addresses in the bridgedomain has reached the configured

maximum. Since 'shut' action has been
Number of MAC addresses in bridgeconfigured for MAC limit event on the
domain '[chars]' has reached the
bridge-domain, it has been shut down. All
configured MAC limit maximum and hence the ports under the bridge too are
it has been shutdown
automatically shutdown.

Number of MAC addresses in PW '[chars],

[chars]' has reached the configured MAC
limit maximum and hence it has been
shutdown

Number of MAC addresses in the

pseudowire has reached the configured
maximum. Since 'shut' action has been
configured for MAC limit event on the port,
it has been shut down.

LDP session [chars] has failed to

synchronize

That is due to NSR being enabled and

L2VPN not able to synchronize the L2VPN
LDP session.

L2VPN sanity check failed for Attachment

Circuit on node [chars]: [chars]. Limit is
[dec]

An internal error has been encountered and

the Attachment Circuit cannot be
established.

State of Bridge Domain [chars] (BD ID:

[unsigned int]) has been changed to
[chars]

The state of specified BD, with the BD ID,

has been changed. The possible states are:
- up - down - admin down The trigger of the
BD state change are: - Shut/No Shut BD
from CLI - BD operational state changed

L2VPN EVPN RD Auto ([chars] - [chars])

conflicts with statically configured RD

L2VPN EVPN RD Auto is generated from

BGP Router-id and VPN-ID in the form
RID:EVI. A static RD was configured before
this RD Auto was generated and conflicts
with this newly generated RD Auto.

L2VPN receives the CE's System ID from

LACP for use in EVPN as the PBB-BSA on
L2VPN received LACP System ID more than two or more interfaces. It cannot be used
once from CE ([chars] - [hex].[hex].[hex]) more than once as a PBB-BSA MAC.

L2VPN received LACP System ID with

Multicast bit set from CE ([chars] - [hex].
[hex].[hex])

L2VPN receives the CE's System ID from

LACP for use in EVPN as the PBB-BSA. It
cannot be used if the Multicast bit is set.

L2VPN has run out of IDs when trying to

get an ID for [chars]. New configuration
added will not become resolved.

L2VPN ID Mgr keeps track of IDs for

different features. If a feature runs out of
IDs, new instances cannot be provisioned.

Main port [chars] is already protected by

[chars] and now in conflict with recently
added protocol [chars]

Configuration conflicts for STP protocols are

not detectable by l2vpn at configuration
time. Recently added configuration is now
in conflict with existing configuration.

License is required for L2VPN feature to

L2VPN AC manager could not get a license work, but AC manager could not get a
for node [chars], [chars]
license for the node from License manager.

Changed state to [chars]

The NSR state of L2VPN application. The

possible states are: - NSR-Disabled (L2VPN
NSR is not enabled) - Not NSR-Ready
(L2VPN synchronization in progress) - NSRready (L2VPN synchronization complete) Declared NSR-Ready (Declared NSR-Ready
to Redundancy Management Framework)

State of VFI [chars] under Bridge Domain

[chars] (BD ID: [unsigned int]) has been
changed to [chars]

The state of specified VFI, under the BD

with BD ID, has been changed. The
possible states are: - up - down - admin
down The trigger of the VFI state change
are: - Shut/No Shut BD from CLI - Shut/No
Shut VFI from CLI - BD operational state
changed

[chars] mtu of [dec] now matches bridge

mtu

The interface MTU now matches the bridge

payload MTU.

Global L2VPN capabilities have been

[chars]

Global L2VPN capabilities indicate the

maximum number of L2VPN service
instances which are programmed on all
nodes and are computed by default as the
minimum capability among the LCs, or as
the maximum if 'l2vpn capability highmode' is configured. This message
indicated that the global L2VPN capabilities
have been upgraded/downgraded and an
extended ID pool has been
activated/deactivated. Use 'show l2vpn
capability' to check the new capabilities in
use. UPGRADE The upgrade can happen
either if a LC OIR occurred and the
remaining LCs in the box support higher
global L2VPN capabilities, or if 'l2vpn
capability high-mode' is configured and at
least one LC in the box supports higher
global L2VPN capabilities. DOWNGRADE
The downgrade can happen if 'l2vpn
capability high-mode' is configured and all
inserted LCs become low-scale or if a lowscale LC is inserted in an empty chassis.

Unresolved pseudowire encapsulation has

been resolved for pw-class '[chars]'

Encapsulation in the pw-class is set, all

pseudowires attached to this pw-class
should be out of the unresolved state.

Number of MAC addresses in AC '[chars]'

has gone below 75 percent of the
configured MAC limit maximum, [chars]

Number of MAC addresses in the

attachment circuit has gone below 75% of
the configured maximum. If MAC learning
or/and unicast flooding was disabled on the
port due to MAC limit action, then it would
get re-enabled automatically.

Number of MAC addresses in AC '[chars]'

has reached the configured MAC limit
maximum, [chars]

Number of MAC addresses in the

attachment circuit has reached the
configured maximum. If MAC limit action to
disable MAC learning and unicast flooding
has been configured on the port, then that
particular action might have been taken
automatically.

Number of MAC addresses in bridgedomain '[chars]' has gone below 75

percent of the configured MAC limit
maximum, [chars]

Number of MAC addresses in the

attachment circuit has gone below 75% of
the configured maximum. If MAC learning
or/and unicast flooding was disabled on the
bridge-domain due to MAC limit action,
then it would get re-enabled automatically.

Number of MAC addresses in bridgedomain '[chars]' has reached the

configured MAC limit maximum, [chars]

Number of MAC addresses in the bridgedomain has reached the configured

maximum. If MAC limit action to disable
MAC learning and unicast flooding has
been configured on the port, then that
particular action might have been taken
automatically.

Number of MAC addresses in PW '[chars],

[chars]' has gone below 75 percent of the
configured MAC limit maximum, [chars]

Number of MAC addresses in the

pseudowire has gone below 75% of the
configured maximum. If MAC learning
or/and unicast flooding was disabled on the
port due to MAC limit action, then it would
get re-enabled automatically.

Number of MAC addresses in PW '[chars],

[chars]' has reached the configured MAC
limit maximum, [chars]

Number of MAC addresses in the

pseudowire has reached the configured
maximum. If MAC limit action to disable
MAC learning and unicast flooding has
been configured on the port, then that
particular action might have been taken
automatically.

Send async pulse to lacp lite process fails;

Error [chars]

Attempt to send pulse to LACP lite process

fails

Cannot connect to lacp lite process; Error

[chars]

Attempt to connect to LACP lite process

channel fails

Cannot mmap file [chars]; Error [chars]

Attempt to mmap the shared memory fails

Cannot open shmem file [chars]; Error

[chars]

Attempt to open the shared memory fails

Cannot truncate file [chars] to [dec] bytes; Attempt to truncate the shared memory file
Error [chars]
fails

LACP lite SHMEM can accommodate only

[dec] records (request for [dec] records)

BM-Local has requested transfer of more

interface records than shared memory can
accommodate

LACP lite API is called with unsupportd flag BM-Local has called LACP lite API with
(request for [dec])
unsupported flag

[chars] li ea failed on interface

<<CH[hex]>>. [chars]

1) Li MD could not be applied to hardware

because of one of the following reasons: a)
TCAM max limit has been reached. b) RLB
resources are not available. This error can
happen when a new bundle member is
added and the MD can not be programmed
successfully.

[chars] failed due to [chars]

permit/deny entries for IPv4/IPv6. These

entries are needed for
programming/removal of hardware entries
for IPv4/IPv6 security ACLs. 5) Failed to
initialize connection with interface
manager proxy service. 6) Failed to
initialize RLB (range logic block)
checkpoint. This is needed for
checkpointing range logic block information
for restore on process restart. 7) Failed to
initialize Feature EA DLL API needed for
programming of hardware resources. 8)
Failed to initialize callback function from
Feature EA DLL for compiling IPv4/IPv6
TCAM entries needed for security ACL
programming in hardeare. 9) Failed to
initialize callback function from Feature EA
DLL to handle reprogramming of RLB and
IPv6 source prefix compression table
request from TCAM manager. 10) Failed to
initialize feature checkpoint info. This is
needed for checkpointing IPv4 and IPv6
security ACLs programmed in hardware.
11) Failed to initialize callback functions
from ACL configuration manager to perform
hardware resource checks and ACE
resequencing. 12) event_block failed. This
indicates process has encountered
unexpected error while waiting for events.
13) Failed to initialize callback functions for
receiving incremental updates for IPv4/IPv6
security ACL configuration.

[chars] failed due to [chars]

reasons: 1) Failed to initialize event

manager. This would prevent process from
receiving events. 2) Failed to register with
debug. This would prevent process from
logging debug messages. 3) Failure to
connect with SYSDB. 4) Failed initialize
internal permit/deny entries for IPv4/IPv6.
These entries are needed for
programming/removal of hardware entries
for subscriber li TAP and MD table. 5) Failed
to initialize connection with interface
manager proxy service. 6) Failed to
initialize RLB (range logic block)
checkpoint. This is needed for
checkpointing range logic block information
for restore on process restart. 7) Failed to
initialize Feature EA DLL API needed for
programming of hardware resources. 8)
Failed to initialize callback function from
Feature EA DLL for compiling TCAM entries
needed for security ACL programming in
hardeare. 9) Failed to initialize callback
function from Feature EA DLL to handle
reprogramming of RLB source prefix
compression table request from TCAM
manager. 10) Failed to initialize feature
checkpoint info. This is needed for
checkpointing subscriber li md
programmed in hardware. 11) event_block
failed. This indicates process has
encountered unexpected error while
waiting for events.

Failed to create channel : [chars]

Failed to create marvel-test (driver)

channel using event_manager_create.

Debug initialization failed

Initialization of the debug event failed.

Debug registration failed : [chars]

debug_register() call failed.

[chars] : [chars]

Generic failure of any event manager API.

Failed to map device address : [chars]

mmap() system call failed to map the

device physical address.

Failed to send reply message : [chars]

This error is reported when msg_reply()

(LWM call) fails.

Failed to allocate memory

This error is reported when malloc()/calloc()

type system call fails.

Failed to open file [chars] : [chars]

This error is generated when the open()

system call fails.

Invalid asynchronous message received.

This error is generated when an invalid

asynchronous message is received.

Debug Msg : [chars]: [chars]

This is a debug message in the Hardware

Stats Manager Library to indicate
anomalies. In most cases these messages
will stop once the temporary condition is
resolved. Examples of when this error
occurs are: 1. The client connection handle
received is NULL 2. The arguments to the
bind message are incorrect 3. Unable to
bind to the hardware IPC driver 4. Error
while trying to initialize debug event. 5.
Not enough memory to bind to the client

DLL INIT : [chars]: [chars]

This error indicates that there was an error

while initializing the stats dll.

Locking issues: [chars]: [chars]

This error indicates that the Hardware Stats

Manager Library is unable to
initialize/destroy locking for client's
attributes and tables.

Stats Counters Exhausted Msg : [chars]

[dec] [chars] [dec] [chars] [chars]

This is a debug message in the Hardware

Stats Manager Library to indicate the stats
reserve limit is reached. In most cases
these messages will stop once the
temporary condition is resolved. Examples
of when this error occurs are: 1. The client
tries more counters than that are free for
that type

Stats Exhausted: [chars] [chars] [chars]

[dec] [chars] [dec] [chars] [dec]

This is a debug message in the Hardware

Stats Manager to indicate the stats
counters of the particular stat type is
exhausted. In most cases these messages
will stop once the temporary condition is
resolved. Examples of when this error
occurs are: 1. The client tries more
counters than that are free for that type

[chars]: [chars]

These errors are encountered at mstats

process initialization time. The types of
errors are: 1 Unable to determine hardware
version. 2 Unable to create event manager.
This will prevent stats process from
receiving events. 3 Unable to create timer.
4 Unable to initialize client database. This
will result in clients not being able to
register with stats server to collect stats. 5
Unable to allocate Ingress/Egress stats.
This will result in Stats manager not being
able to maintain/update any hardware
stats. 6 Unable to register with debug. This
will prevent stats process from logging
debug messages. 7 Unable to initialize or
register with checkpoint service. This will
prevent stats manager from restoring the
information required at restart. 8 Unable to
connect with SYSDB. This includes failure
to connect, bind, register with SYSDB. 9
Unable to Initialize hardware packet
service.

Memory error: [chars]: [chars]

An error occurred in Hardware Stats

Manager during shared memory
operations. This may be because the
system is running low on memory. The
types of errors are: 1 Cannot
open/reset/close shared memory window 2
Cannot allocate/free shared memory. This
will cause Stats Server to not be able to
have a shadow copy of stats for all clients.

ltrace dll operation detected: [chars]

MFR EA ltrace dll operation failure The

cause may be related to the symbol file
corruption.

The MFR EA ltrace lib failed to initialize the

ltrace initialization operation failed for error error ltrace This has zero impact on the
traces: [chars]
functionality.

ltrace initialization operation failed for

events: [chars]

The MFR EA ltrace lib failed to initialize the

events ltrace This has zero impact on the
functionality.

ltrace initialization operation failed for

internal traces: [chars]

The MFR EA ltrace lib failed to initialize the

internal ltrace This has zero impact on the
functionality.

MFR EA failed handling a DPC [chars]

Internal error. Might occur while distributing

data path control to IM

An internal error occurred: [chars]

Internal error. The argument tells the

reason. This could be due to several
reasons, below are a few of them: Database walk/insert/delete error Operation not supported - EA connection
trouble - Invalid arguments

Failed during AIB initialization, err: [chars]

The MFR EA process initialization failed

whilst trying to connect to AIB. The
argument depicts the error.

Interface [chars] operation failed for

ifhandle [hex] err: [chars]

The MFR EA process failed whilst trying to

change interface state. The first argument
is hex and shows the ifhandle.

Memory allocation failed: [chars]

Memory allocation failure detected. The

node might have run out of memory.

Failed during AIB remove, err: [chars]

The MFR EA process failed whilst trying to

remove entry from adjacency information
base.

Failed during AIB set , err: [chars]

The MFR EA process failed whilst trying to

insert entry to adjacency information base.

Failed during caps set, err: [chars]

The MFR EA process failed whilst trying to

set caps.

Failed during caps remove, err: [chars]

The MFR EA process failed whilst trying to

remove caps.

Failed during encaps remove, err: [chars]

The MFR EA process failed whilst trying to

remove encaps.

Failed during encaps set, err: [chars]

The MFR EA process failed whilst trying to

set encaps.

Failed to collect member link inforamtion,

err: [chars]

The MFR EA process failed whilst trying to

collect member link info.

Failed to initialize MFR interface stats

collection, err: [chars]

The MFR EA interface stats collection

initialization failed.

Failed during interface state change, err:

[chars]

The MFR EA process failed whilst trying to

change interface state.

During process start up an unrecoverable

error occurred. The component will exit and
MFR MA failed to [chars]. Thread id is [dec]. should be restarted by the System
[chars]
Manager.

Trying to delete a [chars] idb.

The mentioned idb in the argument, itself

is NULL.

An error occurred during the Data Path

Control send operation. The DPC message
sent here is to update state change/db in
[chars] DPC failed for ifhandle [hex] [chars] EA.

Unable to process mfr encapsulation

request

An error occurred processing a request to

set mfr encapsulation on an interface.

An internal error encountered during an

operation under Multilink Frame
Relay(MFR) Management Agent(MA)'s
MFR MA IMC encountered: [chars] : [chars] interaction with Interface manager(IM).

An error occurred during an operation. The

error could be related to socket, SysDb, idb
An internal error occurred: [chars] : [chars] or timers.

Unable to create [chars] list

The list here refers to the ifhandle list or

the idb list for the bundle or its members.
Also, it could be the STATE change list as
well for IM. The argument shows up the
type of list which was failing to get created.

Cannot add [chars] to bundle with nodeid

[hex] and group [dec]

Could not find the bundle interface with the

nodeid and group. Hence cannot add the
member interface to bundle.

Mutex lock failed. [chars]

Locking the mutex governing the access to

MFR MA IDB database failed.

IPC thread received an async event pulse

Received unexpected Async Event [hex] for for which there is no handler under FSM
ifhandle [hex]
Status msg handlerroutine.

[chars] SysDB bind failed: [chars]

SysDb bind API fails for some reason. This

should be analyzed. first %s - Type of
SysDb bind second %s - Error string

Incorrect [chars] count, Trying to

decrement 0.

During checkpoint delete or idb cleanup, a

rare case when the count is zero and an
attempt is made to decrement it.

The mentioned idb in the argument, itself

is NULL. That's why converting it to a
Trying to make a [chars] idb with a null idb. regular/zombie idb can't be done.

Memory allocation failed: [chars]

A call to malloc failed.

An error occurred receiving a packet:

[chars]

The socket call recvfrom returned an error.

[chars] . Thread id is [dec]. [chars]

An error occurred in a thread during an

operation.

Unexpected error encountered whilst

[chars]: [chars]

MFR MA encountered an error using the

Checkpoint Service. The error message
describes what operation has failed and
why it failed. The most likely reason for this
a low memory condition but the error could
also be caused by a programming error.

Corrupt [chars] checkpoint record found:

[chars]

Whilst restoring one of its checkpoint

tables MFR MA found a corrupt checkpoint
entry. The entry will be ignored and so the
relevant interface's MFR session will be
renegotiated after the restart and as a
result there may be a short period where
traffic is lost.

Duplicate [chars] checkpoint record found

for [chars]

Whilst restoring one of its checkpoint

tables MFR MA found multiple entries for
the same interface. MFR MA will use the
first checkpoint entry it finds for each
interface and ignore any subsequent
duplicates. This is caused by a
programming error.

After detecting an error with the connection

to the specified service, MFR MA failed to
reset that connection. This is an internal
error. It requires a restart of the process for
Error resetting '[chars]' connection: [chars] recovery.

Failed to allocate [unsigned int] bytes for

'[chars]'

The process failed to allocate memory for

the specified resource.

Unexpected error encountered whilst

[chars]: [chars]

MFR MA encountered an unexpected error

using the Managed Timer library. This is
most likely due to a low memory condition
but may also be an internal programming
error. The error message should provide
more information about the cause.

Failed to create '[chars]' thread: [chars]

MFR MA encountered an unexpected error

creating a new thread. The process will
restart to attempt to recover. This is
possibly due to a low memory condition but
may also be an internal programming error.
The error message should provide more
information about the cause.

Packet send attempt timed out: [chars]

The socket call to send a control packet

timed out.

Mickey Intr: [chars]: [dec]: [dec]

A high severity error has interrupted the

Mickey FPGA. This might result in the PLIM
being reset. %s - Error message %d Interrupt %d - Mask

Unknown Mickey Intr: [chars]: [dec]: [dec]

This message indicates the Mickey FPGA

has detected an unknown interrupt. %s Error message %d - Status register %d Interrupt mask

[chars]([dec]): not enough memory for

[chars]

The process is out of memory.

[chars]([dec]): [chars] failed ([chars]) [chars]

A general failure occured while executing

the function in question. The message
contains info about the location and cause
of the failure and possibly anticipated
actions/effects.

[chars]: [chars] [chars]

[chars] [chars]

The specified MLCTRLR Alarm has been

declared or released.
New Far End Alarm Code received.

[chars] [chars]

A configurable controller loopback status.

[chars]: [chars] [chars]

The specified MLCTRLR is operationally

down due to alarm. Check alarm status
using show controller Mlt command on the
cli.

[chars]([dec]): [chars] - [chars]

A non-fatal error occured while executing

the function in question. The message
contains info about the location and cause
of the failure and possibly anticipated
actions/effects.

'There has been a fatal error ([chars])

during protocol ' 'processing. Restarting
MMRP process'

A fatal error has been hit during protocol

processing. The process is restarting to
attempt recovery.

'Failed to create registration for I-SID

[unsigned int] on the pseudowire
(neighbor: [chars], pwid, [chars]): [chars]'

A failure occurred when attempting to add

the registration to the internal process
database. This pseudowire will not have
traffic flooded to it for this I-SID.

A failure occurred when attempting to

'Failed to create platform route resource for create the platform route resource. This
I-SID [unsigned int]: [chars]'
route has not been installed.

A failure occurred when attempting to

delete the platform route resource. This
may prevent other routes for other I-SIDs
being created in the future. It is likely that
the route will have been removed (even
though an error occurred), but to check
'Failed to delete platform route resource for which routes are currently installed, run
I-SID [unsigned int]: [chars]'
'show l2vpn bridge-domain mmrp'.

[chars]. Reason: [chars]

An error occurred in the PSE ASIC client

library after which the client code cannot
continue. This error is encountered when a
client module (e.g. cli command) has
difficulty retrieving information from the
PSE driver. The root cause may be located
in either hardware or software.

Fatal error: [chars]: [chars]: [hex]

A fatal error occurred in mothra Driver

which involves exiting the process.

Asic PIO failure : [chars], instance [dec]: rc

[dec] cerr [chars] errno [dec] data1 [hex]
A fatal error occurred in Santa Driver which
data2 [hex]
involves exiting the process.

Info: [chars]: [chars]

This is a Informational message in the

mothra driver to indicate an operation.

Debug: [chars]: [chars] errno [dec]

This is a debug message in the mothra

driver to indicate anomolies which are not
FATAL. Some of the messages may indicate
a failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temperory situation is resolved.

Mouse Intr: [chars]: [dec]: [dec]

A high severity error has interrupted the

Mouse FPGA. This might result in the PLIM
being reset. %s - Error message %d Interrupt %d - Interrupt Mask

Unknown Mouse Intr: [chars]: [dec]: [dec]

This message indicates the Mouse FPGA

has detected an unknown interrupt. %s Error Description %d - Status register %d Interrupt mask

The destination MAC address of the

incoming MRPDU does not match the MAC
[chars]: Received an MRPDU with an invalid address expected for this interface. The
destination MAC address: [chars] (expected specific MRPDU will be dropped and the
MAC [chars])
protocol will continue to operate.

An MRPDU packet has been received but

Received an MRPDU which could not be
the direction of the packet is unknown or
decoded. The packet's direction is unknown invalid. The specific MRPDU will be dropped
or invalid: [chars]
and the protocol will continue to operate.

Received an MRPDU which could not be

decoded. The packet's interface handle is
unknown: [chars]

An MRPDU packet has been received but

the interface the packet was received on is
unknown. The specific MRPDU will be
dropped and the protocol will continue to
operate.

[chars]: Received an MRPDU which could

not be decoded. The MRPDU could not be
parsed correctly: [chars]

An MRPDU packet has been received which

MRP could not decode. The MRP
infrastructure was unable to parse the
packet correctly because certain fields are
missing or truncated. The specific MRPDU
will be dropped and the protocol will
continue to operate. The error string
includes details of the position in the
packet where parsing failed.

[chars]: Received an MRPDU which could

not be decoded. The MRPDU's attribute
values could not be parsed correctly at
octet [unsigned int]: [chars]

An MRPDU packet has been received which

MRP could not decode. The MRP
infrastructure was unable to parse the
packet correctly because certain fields are
missing or truncated. The specific MRPDU
will be dropped and the protocol will
continue to operate. The message includes
details of the position in the packet where
parsing failed.

[chars]: Received an MRPDU which could

not be decoded. The protocol data could
not be retrieved from the packet: [chars]

An MRPDU packet has been received but

the contents of the packet cannot be
determined. This is due to packet metadata
fields set by the platform being invalid. The
specific MRPDU will be dropped and the
protocol will continue to operate.

A memory allocation failure has occured

from which MRP could not recover

A memory allocation has failed in a

situation where MRP cannot continue
without possibly being in the wrong state.

[chars]: Received an MRPDU on this

interface but no MRP participant present

An MRPDU was received on an interface

where there is no participant. The specific
MRPDU will be dropped and the protocol
will continue to operate.

Misconfiguration: Item [chars] on interface

[chars] is incompatible with other
configuration. The system may now be in
an inconsistant state.

The Multilink Uberverifier has detected a

misconfiguration. It was not detected in the
verification phase, so the Uberverifier
cannot correct this.

Unrecoverable error in event loop. Error:

[chars]

An error (other than EINTR) occured in the

event loop. The process must exit.

A failure occurred during the initialization

Failure during initialization of [chars]. Error: of the process. This resulted in the restart
[chars]
of the process.

The process was initialized successfully but

Failure communicating readiness to System was unable to inform System Manager of
Manager. Error: [chars]
the success.

Bundle [chars] with bandwidth [dec]. Link

ifh [hex] with bandwidth [dec]

When the indicated member link was

deactivated, bundle bandwidth could not
be updated correctly as decrementing the
link's bandwidth would have made the
bundle bandwidth to go below zero. Bundle
bandwidth is now made zero.

Failed to add/remove serial link [chars] into The link addition/removal from a Multilink
multilink bundle [chars]
bundle has failed due to a software error.

Failed to set MTU of [unsigned int] on

[chars]

The specified MTU could not be applied on

this interface.

[chars]: [chars] [chars]

The specified Multilink Alarm has been

declared or released.

Failed to initialise [chars] in [chars]

process: [chars]

A failure occurred during the initialization

of the process. This resulted in the restart
of the process.

The MVRP IO process has failed to initiate

VLAN ID flush with L2VPN after five
seconds of retrying. Further retries will be
attempted every 3 seconds. Until the flush
MVRP failed to initiate VLAN ID flush with
succeeds the currently registered VLAN IDs
L2VPN after one second of retrying: [chars] may be inconsistent.

MVRP failed to reinitialise with the MAD

following a change in bridging
configuration: [chars]

The MVRP IO process has failed to

reinitialise with the MAD following a change
in bridging configuration. Periodic retries
will occur to successfully reinitialise with
the MAD. Until the MAD is initialised the
protocol will not run.

A failure occurred during shutdown of the

MVRP process, and it was unable to notify
the System Manager that it was about to
exit. In rare cases, this could result in a
Failed to notify SysMgr of intention to exit: failure by the System Manager to restart
[chars]
the process when it ought to do so.

Process initialisation failed. [chars]: [chars] There was a software error during process
([hex])
startup.

[chars]. Reason: [chars]

An error occurred in the NPU client library

after which the client code cannot
continue. This error is encountered when a
client module (e.g. cli command) has
difficulty retrieving information from the
NPU driver. The root cause may be located
in either hardware or software.

Exit on error: [chars]: Caused by [chars]

An critical error occurred in NPU Driver

which requires exiting (and, hence,
restarting) the process.

NPU_INST [dec]: DRAM instance [dec]

The NPU driver was unable to initalize
initialization failed for memory type [chars] DRAM. and must trigger a node bringdown
at the phase [chars]
to effect recovery.

NPU [dec] Imp Comp values [[chars]] [hex] The NPU ASIC has VTP issue. HW init will
appear out of range
fail

[chars] device: Caused by [chars]

The NPU driver was unable to perform a

critical function and must trigger a node
bringdown to effect recovery.

Instance [dec]: [chars] [chars] [hex]

This is a error message in the NPU Driver to

indicate DMA operation failed

Exit on error: [chars]: Caused by [chars]

An error occurred in NPU Driver which

requires exiting (and, hence, restarting) the
process.

[chars]

This is a debug message in the NPU Driver

to indicate an operation or condition or a
failure. It indicates * timer failures * readwrite failure * ftruncate, map failures * null
event or arguments

[chars]

NPU driver health monitor detected error

conditions

NPU[dec]: Init Failed. Caused by:[chars]

This is a debug message in the NPU Driver

to indicate an operation or condition.

[chars] device: Caused by [chars]

This is an error message in the NPU Driver

to indicate that it failed to perform cold
reset of specified NPU instance due to the
specified reason.

NPU[dec]: [chars]

This is an error message in the NPU Driver

to indicate that it failed to perform warm
reset of specified NPU instance due to the
specified reason.

NPU[dec]: [chars]

This is a informational message in the NPU

Driver to indicate an operation.

Unable to register for OAM MIB debug. No

further debugging will occur: [chars]

In the initialization of the OAM MIB DLL an

error occurred whilst attempting to register
for debugging. Consequently there will be
no debug output from the OAM MIB DLL.

Unable to create the OAM MIB interface

table. All MIB items will be unavailable:
[chars]

In the initialization of the OAM MIB DLL an

error occurred while trying to create the
internal interface table used for identifying
interfaces running ethernet link OAM.

In the initialization of the OAM MIB DLL an

error occurred while trying to register a
callback function for the enabling of SNMP
Unable to register for SNMP traps. Traps will traps. Alternatively whilst trying to enable
not be sent regardless of trap events
traps there was a failure in binding to
occurring: [chars]
SysDB for trap notifications.

[chars]: [chars]: [hex]

OC768 Framer ASIC Driver encountered a

critical error which causes the process to
exit.

[chars]: [chars]

This is a informational message from

OC768 Framer ASIC driver to indicate an
operation.

Debug: [chars]: [chars] errno [dec]

This is a debug message in OC768 Framer

ASIC driver to indicate anomolies which are
not FATAL. Some of the messages may
indicate a failure to allocate resources
needed by applications. In many cases
these messages must not keep appearing
after the temperory situation is resolved.

[chars]: [dec]

OVS reported an alert. The text of the

message displays the failed operation with
error code.

bag(s) [chars] failed: [chars]

Some error occured with a bag operation.

The text of the message displays the failed
operation with error code.

bag(s) registration failed: [chars]

Some error occured while trying to register

edm bags. The text of the message
displays the failed operation with error
code.

bridge domain [chars] is already associated Bridge domain is already associated with
with logical switch [dec], first remove it
logical switch, first remove this association.

Unable to assign bridge domain because

logical switch is not layer2 type

Unable to assign bridge domain because

logical switch is not layer2 type.

Unable to add bundle to logical switch with Unable to add bundle interface to logical
pipeline [dec]
switch with specific pipeline id.

controller is already associated with logical Controller is already associated with logical
switch [dec], first remove it
switch, first remove this association.

Debug [chars] [chars] failed : [chars]

Some error occured while trying to

initialize/register debugs. The text of the
message displays the failed operation with
error code.

[chars] failed: [chars]

Some error occured in event/event

manager/event connection operations. The
text of the message displays the failed
operation with error code. The traceback
can be used to get the function/line
number of error generating code.

[chars] failed: [chars]

Some requested operation failed. The text

of the message displays the failed
operation with error code.

[chars] failed, rc=[dec]: [chars]

Some requested operation failed. The text

of the message displays the failed
operation, error code and error message (if
available).

Openflow Plug-in aborting HA recovery,

[chars]

Openflow plug-in has encountered an error

during HA restart and needs to be cold
started.

interface [chars] is already associated with Interface is already associated with logical
logical switch [dec], first remove it
switch, first remove this association.

Unable to assign interface because logical

switch is not layer3 type

Unable to assign interface because logical

switch is not layer3 type.

Unable to assign interface to logical switch Unable to assign interface because it is

because it is already part of bridge domain part of existing bridge domain, first remove
[chars]
this association.

Unable to add interface because it is

already part of logical switch [dec]

Unable to add interface because it is part

of a openflow logical switch. Remove this
interface from the switch to proceed.

Unable to assign interface because it is

Unable to assign interface to logical switch part of existing named VRF, first remove
because it is already part of VRF [chars]
this association.

logical switch [dec] already exists with

different layer

Check of HW layer failed. You are trying to

create/edit logical switch, but it is already
registered in sysdb and its layer value
(layer2 or layer3) is diffent than requested
one. *SUPPORT*

switch [chars] loopback address

unavailable, packet punt disabled

Loopback address must be valid,

configured on a looback and associated to
a switch

loopback [chars] is already associated with Loopback is already associated with logical
logical switch [dec], first remove it
switch, first remove this association.

[chars]: [dec]

OVS reported an error. The text of the

message displays the failed operation with
error code.

sysdb failed for '[chars]': [chars]

Some error occured in sysdb bind operation

bind. The text of the message displays the
failed operation for the bindpoint with error
code.

[chars] failed: [chars]

Some error occured in sysdb operation. The

text of the message displays the failed
operation with error code. The traceback
can be used to get the function/line
number of error generating code.

sysmgr failed for '[chars]': [chars]

Some error occured while interacting with

sysmgr. The text of the message displays
the failed operation with error code.

VRF [chars] is already associated with

logical switch [dec], first remove it

VRF is already associated with logical

switch, first remove this association.

Unable to assign VRF because logical

switch is not layer3 type

Unable to assign VRF because logical

switch is not layer3 type.

[chars] failed, rc=[dec]: [chars]

Request ONEP failed. It may caused by

ONEP configuration lost or ONEP process
failed.

[chars]
[chars]
[chars]

OVS reported a warning. The text of the

message displays the failed operation with
error code.
OVS info message.
OVS debug message.

Ether xcvr code is [hex]

The xcvr code is displayed for both

supported and unsupported sfp/xfp types
for the following actions - OIR of SFP/XFP Soft and Hard OIR of SPA/LC - unshut of SPA
- Enabling power for LC

PID is [chars]

The PID information is displayed for both

supported and unsupported sfp/xfp types
for the following actions - OIR of SFP/XFP Soft and Hard OIR of SPA/LC - unshut of SPA

PN is [chars]

The Product Number information is

displayed for both supported and
unsupported sfp/xfp types for the following
actions - OIR of SFP/XFP - Soft and Hard OIR
of SPA/LC - unshut of SPA

[chars] xcvr type [dec] not

matched,INVALID SFP

This message indicates that the

unsupported SFP type is inserted.

Sonet xcvr code is [hex]

The xcvr code is displayed for both

supported and unsupported sfp/xfp types
for the following actions - OIR of SFP/XFP Soft and Hard OIR of SPA/LC - unshut of SPA
- Enabling power for LC

Transceiver location is [chars]

The Transceiver location is displayed for

both supported and unsupported sfp/xfp
types for the following actions - OIR of
SFP/XFP - Soft and Hard OIR of SPA/LC unshut of SPA - Enabling power for LC

VID is [chars]

The VID information is displayed for both

supported and unsupported sfp/xfp types
for the following actions - OIR of SFP/XFP Soft and Hard OIR of SPA/LC - unshut of SPA
- Enabling power for LC

xcvr code is [hex]

The xcvr code is displayed for both

supported and unsupported sfp/xfp types
for the following actions - OIR of SFP/XFP Soft and Hard OIR of SPA/LC - unshut of SPA
- Enabling power for LC

xcvr type [dec] not matched,INVALID XFP

This message indicates that the

unsupported XFP type is inserted.

Optical init failure: [chars]: [chars]: [hex]

A critical error occurred in OPTICS Driver

which involves exiting the process.

Info: [chars]: [chars]

This is an informational message in the

OPTICS driver to indicate an operation.

Debug: [chars]: [chars] value [dec]

This is a debug message in the optics

driver to indicate anomolies which are not
FATAL. Some of the messages may indicate
a failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temperory situation is resolved.

[chars]

Driver HW error interrupt occurs, it will

cause HW reset.

[chars]

Driver initialization error

[chars]

Driver software error

[chars]

HW interrupt occurs.

Initialization failed: ([chars]%s)

The PAL ACL CGM DLL failed to initialize

because of memory alloc failure. This DLL
does a generalization of an Access Control
List to include matching on MQC match
criteria If the ccl DLL fails to initialize, the
access control list cannot be programmed
into the hardware.

Initialization failed: ([chars]%s)

The PAL ACL CGM DLL failed to initialize

because of memory alloc failure. This DLL
does a generalization of an Access Control
List to include matching on MQC match
criteria If the ccl DLL fails to initialize, the
access control list cannot be programmed
into the hardware.

IP Header Compression EA : [chars]:

[chars]: rc=[hex] ([chars])\n

IPHC pal ea critical error

IP Header Compression EA : [chars]:

[chars]=[hex] [chars]\n

IPHC pal ea error

IP Header Compression EA : [chars] :

[chars] : [hex]\n

IPHC pal ea informational message

[chars]: acl [chars] failed on interface

<<CH[hex]>> ([chars])

unsupported configuration

debug_init_event failed

Failed to initialize the debug event.

debug_register failed

This error indicates that debug registration

failed.

[chars] acl failed on interface

<<CH[hex]>>. [chars]

1) An ACL could not be applied to hardware

because of one of the following reasons: a)
TCAM max limit has been reached. b) RLB
resources are not available. c) IPv6 address
compression table is full. This error can
happen when a new bundle member is
added and the ACL can not be programmed
successfully. 2) An ACL could not be
removed from hardware.

[chars] acl failed on interface

<<CH[hex]>>. [chars]

1) An ACL could not be applied to hardware

because of one of the following reasons: a)
TCAM max limit has been reached. b) RLB
resources are not available. c) IPv6 address
compression table is full. This error can
happen when a new bundle member is
added and the ACL can not be programmed
successfully. 2) An ACL could not be
removed from hardware.

[chars] acl [chars] v4 [dec] failed on

interface <<CH[hex]>>. [chars]

1) An ACL could not be applied to hardware

because of one of the following reasons: a)
TCAM max limit has been reached. b) IPv6
address compression table is full. c) The
ACL doesn't exist (invalid acl). This error
can happen when a new bundle member is
added and the ACL can not be programmed
successfully. 2) An ACL could not be
removed from hardware.

[chars] acl failed on interface

<<CH[hex]>>. [chars]

1) An ACL could not be applied to hardware

because of one of the following reasons: a)
TCAM max limit has been reached. b) RLB
resources are not available. c) IPv6 address
compression table is full. d) UIDB set failed,
possible UIDB/PRM down This error can
happen when a new bundle member is
added and the ACL can not be programmed
successfully. 2) An ACL could not be
removed from hardware.

[chars] failed due to [chars]

failed to initialize with IMP server

'[chars] failed due to [chars]'

Failed to initialize callback functions from

ACL configuration manager to perform
hardware resource checks and ACE
resequencing.

'[chars] failed due to [chars]'

Failed to initialize callback functions for

receiving updates for IPv4/IPv6 security
ACL configuration.

Process initialization failed: ([chars]%s)

The pfilter_ea process failed to initialize.

This pfilter_ea process programs the
'packet filter' security access control list in
the hardware. If the pfilter_ea process fails
to initialize, the access control list cannot
be programmed into the hardware. %s indicates the reason for the initialization
failure. %s - is the decoded error reason.

Process initialization failed: ([chars]%s)

The pfilter_ea process failed to initialize.

This pfilter_ea process programs the
'packet filter' security access control list in
the hardware. If the pfilter_ea process fails
to initialize, the access control list cannot
be programmed into the hardware. %s indicates the reason for the initialization
failure. %s - is the decoded error reason.

Process initialization failed: ([chars]%s)

The pfilter_ea process failed to initialize.

This pfilter_ea process programs the
'packet filter' security access control list in
the hardware. If the pfilter_ea process fails
to initialize, the access control list cannot
be programmed into the hardware. %s indicates the reason for the initialization
failure. %s - is the decoded error reason.

'[chars] failed due to [chars]'

event_block failed. This indicates process

has encountered unexpected error while
waiting for events.

'[chars] failed due to [chars]'

Failed to initialize event manager. This

would prevent process from receiving
events.

'[chars] failed due to [chars]'

Failed to initialize feature checkpoint info.

This is needed for checkpointing IPv4 and
IPv6 security ACLs programmed in
hardware.

'[chars] failed due to [chars]'

Failed to initialize Feature EA DLL API

needed for programming of hardware
resources

'[chars] failed due to [chars]'

Failed to initialize ltrace. This would

prevent process from receiving traces.

'[chars] failed due to [chars]'

Failed initialize internal permit/deny entries

for IPv4/IPv6. These entries are needed for
programming/removal of hardware entries
for IPv4/IPv6 security ACLs.

'[chars] failed due to [chars]'

Failed to register with debug. This would

prevent process from logging debug
messages.

'[chars] failed due to [chars]'

Failed to initialize RLB (range logic block)

checkpoint. This is needed for
checkpointing range logic block information
for restore on process restart.

'[chars] failed due to [chars]'

Failed to connect with sysdb. Failed to

connect to pfilter_ea_clr_edm_init()

[chars] failed due to [chars]

ship_infra registration failed.

[chars] failed due to [chars]

Connection to sysmgr_proc_ready() has

failed.Sysmgr process ready API failed.

[chars] failed due to [chars]

Shared memory initialization has failed for

TCAM

Event Failure: ([chars])

The pfilter_ea process received a bad

event. This pfilter_ea process programs the
'packet filter' security access control list in
the hardware. %s - is the decoded error
reason.

Event Failure: ([chars])

The pfilter_ea process received a bad

event. This pfilter_ea process programs the
'packet filter' security access control list in
the hardware. %s - is the decoded error
reason.

Event Failure: ([chars])

The pfilter_ea process received a bad

event. This pfilter_ea process programs the
'packet filter' security access control list in
the hardware. %s - is the decoded error
reason.

[chars] failed due to [chars]

Initialization of packet filter process has

failed due to one of the following reasons:
1) Failed to initialize event manager. This
would prevent process from receiving
events. 2) Failed to initialize SSE Pfilter EA
Library. This would prevent process from
doing any of its tasks. 3) event_block
failed. This indicates process has
encountered unexpected error while
waiting for events.

[chars] failed due to [chars]

permit/deny entries for IPv4/IPv6. These

entries are needed for
programming/removal of hardware entries
for IPv4/IPv6 security ACLs. 5) Failed to
initialize connection with interface
manager proxy service. 6) Failed to
initialize RLB (range logic block)
checkpoint. This is needed for
checkpointing range logic block information
for restore on process restart. 7) Failed to
initialize Feature EA DLL API needed for
programming of hardware resources. 8)
Failed to initialize callback function from
Feature EA DLL for compiling IPv4/IPv6
TCAM entries needed for security ACL
programming in hardeare. 9) Failed to
initialize callback function from Feature EA
DLL to handle reprogramming of RLB and
IPv6 source prefix compression table
request from TCAM manager. 10) Failed to
initialize feature checkpoint info. This is
needed for checkpointing IPv4 and IPv6
security ACLs programmed in hardware.
11) Failed to initialize callback functions
from ACL configuration manager to perform
hardware resource checks and ACE
resequencing. 12) event_block failed. This
indicates process has encountered
unexpected error while waiting for events.
13) Failed to initialize callback functions for
receiving incremental updates for IPv4/IPv6
security ACL configuration.

[chars] failed due to [chars]

Initialization of packet filter process has

failed due to one of the following reasons:
1) Failed to initialize event manager. This
would prevent process from receiving
events. 2) Failed to initialize SSE Pfilter EA
Library. This would prevent process from
doing any of its tasks. 3) event_block
failed. This indicates process has
encountered unexpected error while
waiting for events.

[chars] failed due to [chars]

permit/deny entries for IPv4/IPv6. These

entries are needed for
programming/removal of hardware entries
for IPv4/IPv6 security ACLs. 5) Failed to
initialize connection with interface
manager proxy service. 6) Failed to
initialize RLB (range logic block)
checkpoint. This is needed for
checkpointing range logic block information
for restore on process restart. 7) Failed to
initialize Feature EA DLL API needed for
programming of hardware resources. 8)
Failed to initialize callback function from
Feature EA DLL for compiling IPv4/IPv6
TCAM entries needed for security ACL
programming in hardeare. 9) Failed to
initialize callback function from Feature EA
DLL to handle reprogramming of RLB and
IPv6 source prefix compression table
request from TCAM manager. 10) Failed to
initialize feature checkpoint info. This is
needed for checkpointing IPv4 and IPv6
security ACLs programmed in hardware.
11) Failed to initialize callback functions
from ACL configuration manager to perform
hardware resource checks and ACE
resequencing. 12) event_block failed. This
indicates process has encountered
unexpected error while waiting for events.
13) Failed to initialize callback functions for
receiving incremental updates for IPv4/IPv6
security ACL configuration.

[chars] failed to connect to the PIRD

database: [chars]

The specified process failed to connect to

PIRD shared memory database on
initialization.

[chars] lost event: [chars]

The specified process failed to receive an

event that was sent to it.

Failed to delete [chars] object (ID [chars])

from the [chars] database, because the
object wasn't found

A user requested that an object be

removed from a database in which it was
not present. The process should recover
from this event, but it may indicate an
internal inconsistency which could cause
other problems.

An internal inconsistency was identified

while performing some operation on the
database. The process will attempt to
recover a consistent state, and should be
An error condition that indicates an internal able to continue operating. It is possible
inconsistency in a database was
that some parts of the dataplane may
encountered: [chars]
become out of sync.

An internal inconsistency was identified

while performing some operation on the
database. The process will attempt to
A client tried to free a block (offset
recover a consistent state, and should be
[unsigned int]) with an invalid garbage
able to continue operating. It is possible
collector epoch ([unsigned int]) in the PIRD that some parts of the dataplane may
database at [hex] ([chars])
become out of sync.

An internal inconsistency was identified

while performing some operation on the
database. The process will attempt to
recover a consistent state, and should be
A client tried to free an invalid block (offset able to continue operating. It is possible
[unsigned int]) in the PIRD database at
that some parts of the dataplane may
[hex] ([chars])
become out of sync.

Failed to perform [chars] operation on

[chars] lock in database: [chars]

An error was encountered while trying to

perform an operation on a lock. The thread
will continue without retrying the
operation. In most cases, no further
adverse behaviour should be observed.

An internal inconsistency was identified

while performing some operation on the
database. The process will attempt to
A client tried to free a block (offset
recover a consistent state, and should be
[unsigned int]) in the PIRD database which able to continue operating. It is possible
has been corrupted (magic [hex]) at [hex] that some parts of the dataplane may
([chars])
become out of sync.

[chars] failed to schedule a retry attempt

using the Event Connection Manager
library: [chars]

The specified process encountered an error

while attempting to schedule a retry for a
failed operation. The operation will not be
retried. This may indicate that system
resources are low.

PIRD encountered an error while trying

send a state message to Interface
Manager, and the error could not be
recovered from by retrying. Interface
Manager is likely to continue to wait for a
Failed to reply to Interface Manager with
response, and then shut down the affected
states for [unsigned int] interfaces: [chars] interfaces.

The PIRD debug library was notified about

the creation of a debug item in SysDB
which had an unexpected number of filter
parameters. The corresponding debugging
flag has not been enabled in PIRD, which
Failed to enable the requested debugging. may lead to some debug not being printed
Invalid debug filter string: [chars]
as expected.

Recovered [chars] shared memory lock

after process [chars] ([dec]) died holding
the lock

The PIRD database uses a number of

shared-memory locks to protect against
concurrent access by clients. A client
process died whilst holding one of these
locks, and it was forcibly recovered. This
may have resulted in an internal
inconsistency which could cause other
problems.

Failed to initialize load balancing library in

[chars] ([dec]): [chars]

An error was encountered while the

specified library was initializing.

[chars] failed to connect to the PIRD

database after [dec] attempts

The specified process failed to connect to

PIRD shared memory database on
initialization.

Failed to notify SysMgr that [chars] is

exiting: [chars]

The specified process failed to notify the

system manager that it was exiting. In very
rare cases, this could result in the process
not being restarted when it ought to be.

Failed to initialize [chars]: [chars]%s

An error was encountered while the

specified process was initializing. The error
message contains details about the source
of the error.

Invalid packet field: [chars]

A packet containing an invalid field was

detected in a batch passed to the PIRD
plug-in or fabric header library.

[chars] lost event: [chars]

The specified process failed to receive an

event that was sent to it.

Plug-in failed to [chars] PIRD database:

[chars]

The PIRD SPP plug-in failed to

attach/detach the PIRD shared memory
database after receiving an asynchronous
message instructing it to do so.

[chars]: [chars]: [hex]

PLAOC768 system checkout Library

encountered a critical error which involves
exiting the process.

Debug: [chars]: [chars] errno [dec]

This is a debug message from the

PLAOC768 system checkout Library to
indicate either anomolies which are not
FATAL. Some of the messages may indicate
a failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temporary situation is resolved.

[chars] : block [dec] error [dec], [chars]

An ASIC error occurred in PLAOC768 ASIC

which is reported here.

[chars]: [chars]: [dec]

PLAOC768 Driver encountered an critical

error condition which involves exiting the
process.

Asic PIO failure : [chars], instance [dec]: rc

[dec] cerr [chars] errno [dec] data1 [hex]
A critical error occurred in PLAOC768 Driver
data2 [hex]
which involves exiting the process.

[chars]: [chars]

This is a informational message in the

PLAOC768 driver to indicate an operation.

Debug: [chars]: [chars] errno [dec]

This is a debug message from the

PLAOC768 driver to indicate anomolies
which are not FATAL. Some of the messages
may indicate a failure to allocate resources
needed by applications. In many cases
these messages must not keep appearing
after the temperory situation is resolved.

PLATFORM-L2FIB-VPLS: Error - [chars]

[chars] [chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB VPLS component.

PLATFORM-L2FIB-VPLS: Error - [chars]

Failed to initialize the VPLS module in the

platform L2FIB VPLS component.

PLATFORM-L2FIB-VPLS: Error - [chars] [dec] Failed to initialize the ltrace module in the
[chars] [dec]
platform L2FIB VPLS component.

ATM OAM PKT RX failure: [chars]

There was a software failure while

processing received OAM cell

ATM OAM PKT RX error:[chars]

There was a software error while

processing received OAM cell

Packet size: [unsigned int], contents

[[chars]]

Display the contents of the debug buffer

and the packet size after dumping the OAM
packet.

Process failed to allocate memory [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialized due to
unavailable memory and will be restarted.
It may affect traffic passing through the
ports located on the PLIM. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller,...

Process init failed [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller,... %s - error
code

Debugging subsystem initialization failed

Physical Layer Interface Module(PLIM)

driver failed to initialize it's debug
subsystem. As result plim debug
commands will not work on the PLIM
module in question. The rest of
functionality of the PLIM driver remains
unaffected by the failure. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller.

Physical Layer Interface Module(PLIM)

driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller. As result of
such failure no trafiic may pass on all 4
oc12 ports located on the 4 port linecard.
The interfaces associated with failed PLIM
Interface module driver initialization failed will not come up.

process received invalid event [chars]

Physical Layer Interface Module(PLIM)

driver experience an errorr while awaiting
for event arrival. PLIM driver is responsible
for initializing/configuring PLIM hardware
such as sonet framer, Packet Over
Sonet(POS) controller. As result of the error
the PLIM process will be restarted. Traffic
may be interrupted on all affected
interfaces. %s - error code

PLIM port init failed [dec] stage-[chars]

Physical Layer Interface Module(PLIM)

driver failed to initialize port. As result of
the failure affected interfaces will not come
up. %d - failed port number %s - specific
stage of port initialization that failed PLIM
driver is responsible for
initializing/configuring PLIM hardware such
as sonet framer and Packet Over
Sonet(POS) controller.

Process initialization error [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialized and will be
restarted. It will affect traffic passing
through the ports located on the PLIM. PLIM
driver is responsible for
initializing/configuring PLIM hardware such
as sonet framer, Packet Over Sonet(POS)
controller,... %s - error code

Port failed to become available [chars]

[dec]

Physical Layer Interface Module(PLIM)

driver failed to make port available for
forwarding. The interface in question will
not forward packets. %s - error code %d port number

PLIM reset failed [chars]

The Physical Layer Interface Module(PLIM)

driver failed to reset PLIM hardware. %s error code PLIM driver is responsible for
initializing/configuring PLIM hardware such
as sonet framer, Packet Over Sonet(POS)
controller.

Physical Layer Interface Module(PLIM)

driver failed to register PLIM interface
statistics collector. No interface statistics
such as sonet counters and packet
counters will be available on the specified
Statistics collector registration error [chars] interface. %s - contains interface name %s
[chars]
- contains error code

Process initialization error [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialized and will be
restarted. It will affect traffic passing
through the ports located on the PLIM. PLIM
driver is responsible for
initializing/configuring PLIM hardware such
as sonet framer, Packet Over Sonet(POS)
controller,... %s - error code

Process init failed [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller,... %s - error
code

Failed to retrieve tx clock source

Physical Layer Interface Module(PLIM)

driver was unable to determine transmit
clock source for the sonet port. The error
may appear during show or configuration
of the sonet port.

Physical Layer Interface Module(PLIM)

driver failed to make configure transmit
clock source for the sonet port. The sonet
port hardware configuration is invalid and
may result in traffic being dropped or high
error count on the port. This error may
Failed to configure tx clock source for sonet appear during attempt to configure clock
port
source for the sonet port.

Invalid timer [dec]

Physical Layer Interface Module(PLIM)

driver received unknown timer event. %d timer type

No Framer/RAC devices are generating

excessive interrupts

The previously reported excessive

interrupts condition has been cleared.
Interrupt rate limiting has been disabled.

Excessive interrupts from the [chars]

device of port [hex]

The specified device is generating

excessive interrupts. This message
indicates that we are rate limiting the
interrupt coming from this device. This
indicates a potential HW issue, traffic
forwarding (protection switching) may be
impacted.

Initialization of PLIM driver failed: [chars] :

rc = [chars] ; exiting...

PLIM driver encountered the annunciated

error during the driver initialization. The
System Manager process (sysmgr) will
automatically respawn the (plim_4P_oc192)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

[chars]

fail to init debug service event manager

fails to provide its service

Error: [chars] [chars] [hex]

A generic error is occurred in

plim_4p_oc192 PLIM driver. Cause of the
error will be mentioned in the message
displayed. This message is for debugging
purposes.

[chars] : rc = [chars]

PLIM driver failed to obtain either its node

ID or extract rack/slot/instance information
(having obtained the node ID).

[chars]
[chars] Reason:[chars]

fail to allocate memory.

BAMBI API generated errors.

An PLA SW error has occurred and requires

Health Monitor Power On Reset recovery for pon-reset to recover. The PLA ASIC was in a
PLA ASIC instance [dec]
Halt state for and extended period..
An ASIC error has occurred multiple times
and has failed to recover despite power on
reset. The board has been requested to be
PLIM ASIC instance [dec] has not recovered reloaded in an attempt to clear the
from fault so reload is requested.
problem.

Instance [dec]. Operation: [chars]. Error:

[chars]. Software action: Abort

The operation is failed due to an internal

software error. %d - instance. %s description of the operation. %s description of the error.

PLASPA: [chars]

EIO training errors. The EIO link to the

PLASPA failed to train. This will result in
traffic loss through this PLIM.

[chars]

Plim asic driver errors. Typically these

errors indicate failure in system services or
bad programming of the hardware.

An Beluga SW error has occurred and

requires pon-reset to recover. The Beluga
Health Monitor Power On Reset recovery for ASIC was in a Halt state for and extended
Beluga ASIC instance [dec]
period..

plaspa instance [dec] [chars], [chars]

Plim Asic errors. Typically these indicate

errors detected by the ASIC. Too many of
these errors might indicate problem with
the board, and can trigger a reload of the
LC.

[chars]

Plim asic driver imdr errors. Typically these

errors indicate failure in system services
during the imdr procedure.

Ltrace init for file [chars] failed [chars]

--

The PIO operation on PLIM ASIC failed due

to a hardware or software error. %s description of the error. %s - description of
A [chars] error occured during PIO [chars] the operation. %d - PLIM ASIC instance
operation on PLIM ASIC instance [dec] port number %d - port number. %08x_%08x [dec] at address [hex]_[hex]. Error detail:
address of the operation %s - description of
[chars]. Software action: [chars].
the error details.

The PIO operation on PLIM ASIC failed due

to a hardware or software error. %s description of the error. %s - description of
A [chars] error occured during PIO [chars] the operation. %d - PLIM ASIC instance
operation on PLIM ASIC instance [dec] port number %d - port number. %08x_%08x [dec] at address [hex]_[hex]. Error detail:
address of the operation %s - description of
[chars]. Software action: [chars].
the error details.

Instance [dec]. Operation: [chars]. Error:

[chars]. Software action: Abort

The operation is failed due to an internal

software error. %d - instance. %s description of the operation. %s description of the error.

The XSN access on PLIM ASIC failed due to

a hardware or software error. %d - PLA ASIC
A timeout error occured during XSN access instance. %s - description of the error
on PLIM ASIC instance [dec]. Details:
details. %s - description of the software
[chars]. Software action: [chars].
action to recover. %s - description of the
Recommended user action: [chars]
recommended user action.

The XSN access on PLIM ASIC failed due to

a hardware or software error. %d - PLA ASIC
A timeout error occured during XSN access instance. %s - description of the error
on PLIM ASIC instance [dec]. Details:
details. %s - description of the software
[chars]. Software action: [chars].
action to recover. %s - description of the
Recommended user action: [chars]
recommended user action.

plaspa instance [dec]: [chars]

Plim Asic errors. Typically these indicate

errors detected by the ASIC. Too many of
these errors might indicate problem with
the board, and may trigger packet loss.
These errors seen during LC boot up or SPA
OIR are harmless.

PLIM ASIC instance [dec] [chars] is not

proceeded because [chars]

An ASIC error has occurred and requires

pon-reset or hard-reset, the reset will not
happen due to the other critical activity is
ongoing.

PLIM ASIC instance [dec] [chars] is not

proceeded because [chars]

An ASIC error has occurred and requires

pon-reset or hard-reset, the reset will not
happen due to the other critical activity is
ongoing.

PLIM process is restarted because of a

failure in Clock Selection Library
initialization: ([chars]/[chars]).

The initilaization of the Clock Selection

Library failed. The Clock Selection Library is
used by the physical layer interface
module (PLIM) driver on the linecard. The
PLIM driver creates the SONET controller
and POS interface, handling the all the
SONET event, applying SONET/POS
configuration to the layer-1 device
hardware. If the PLIM driver fails to
initialize, no traffic will pass, therefore no
higher level protocol will work. %s indicates the reason for the failure %s - is
the decoded error reason

Debug initialization failed with [chars].

Debug message initialzation failed.

Port [dec], subport [dec]: failure detected

while [chars] at physical layer

A problem is encountered at hardware

layer for a given port

Interface [chars], Detected Local Fault

The PLIM received a Local Fault on the

given interface which will result in a link
down.

Interface [chars], Detected Local Fault

The PLIM received a Local Fault on the

given interface which will result in a link
down.

Interface [chars], Detected Local Fault

The PLIM received an Rx LOS or LF on the

given interface which will result in a link
down.

Interface [chars], Detected Remote Fault

The PLIM received a Remote Fault on the

given interface which will result in a link
down.

Interface [chars], [chars]

The PLIM received a Remote Fault on the

given interface which will result in a link
down.

Interface [chars], Detected Rx Unknown

Fault

The PLIM received an unknown fault on the

given interface which will result in a link
down.

Interface [chars], Detected Rx Unknown

Fault

The PLIM received an unknown fault on the

given interface which will result in a link
down.

Interface [chars], Optic Interface Module

inserted

The optic interface module was inserted on

the given interface.

Interface [chars], Optic Interface Module

removed

The optic interface module was removed

on the given interface which will result in a
link down.

Port [dec] Rx data path issues between PLA The PLA MAC xgxs DTE layer went down
and PHY, software recovery complete
due to loss of sync or lane alignment.

Port [dec] subport [dec] Rx data path

issues between PLA and PHY, software
recovery complete

The PLA MAC xgxs DTE layer went down

due to loss of sync or lane alignment.

Port [dec] Rx XGXS lost ready state, Link

disabled.

The PLA MAC xgxs DTE layer went down

due to loss of sync or lane alignment. The
link could not be recovered so the port was
disabled

The PLA MAC xgxs DTE layer went down

due to loss of sync or lane alignment. The
Port [dec] subport [dec] Rx XGXS lost ready link could not be recovered so the port was
state, Link disabled.
disabled

The PLA MAC xgxs DTE layer went down

due to loss of sync or lane alignment. The
Port [dec] Rx data path issues between PLA daily event threshold was crossed so the
and PHY, threshold: port disabled
serdes was reset

Port [dec] subport [dec] Rx data path

issues between PLA and PHY, threshold:
port disabled

The PLA MAC xgxs DTE layer went down

due to loss of sync or lane alignment. The
daily event threshold was crossed so the
serdes was reset

Port [dec], subport [dec] Rx data path

issues between PLA and PHY, software
recovery complete

The PLA MAC xgxs DTE layer went down

due to loss of sync or lane alignment.

Port [dec], Rx data path issues between

PLA and PHY, software recovery complete

The PLA MAC xgxs DTE layer went down

due to loss of sync or lane alignment.

Port [dec], subport [dec] Failed to recover

Rx data path between PLA and PHY,
disabling port

The PLA MAC xgxs DTE layer went down

due to loss of sync or lane alignment. The
link could not be recovered so the port was
disabled

Port [dec], Failed to recover Rx data path

between PLA and PHY, disabling port

The PLA MAC xgxs DTE layer went down

due to loss of sync or lane alignment. The
link could not be recovered so the port was
disabled

[chars]

Plim asic driver imdr errors. Typically these

errors indicate failure in system services
during the imdr procedure.

Please remove the configuration on

interface [chars] as vlan id:[dec] already
exists. Otherwise system will be in
inconsistent state.

The user is trying to configure a dot1q vlan

or qinq vlan that shares the same outer
vlan id with that of an already configured
qinq or dot1q outer vlan id. An error has to
be reported to inform the user to remove
the inconsisent configuration. The
inconsistent configuration is that the same
outer vlan id has been configured, and the
software can only accept one sub-interface,
so the last configured sub-interface is not
applied.

[chars]

A software error is detected on PLIM.

Port [dec], Subport [dec]: [chars] failed,

reason: [chars]

Internal software error

INIT Error: [chars]

Internal software error in initialization.

INIT Error: [chars]

Internal software error in initialization.

Link [chars] went down but software reason

is up
Internal software error in interface state.

Link [chars] went down but software reason

is up
Internal software error in interface state.
PLIM interface mode changed to 'LAN' or
Interface [chars] changed to [chars] mode 'WAN' from CLI.
PLIM interface mode changed to 'LAN' or
Interface [chars] changed to [chars] mode 'WAN' from CLI.

A hardware error reached threshold on the

Datapath FPGA. Software will take action as
described in the error message to try to
recover from the error. Take the
recommended user action as it is described
in the error message. Device: %s indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Software action: %s - the
action that software will take to try to
Device: [chars]. Error: [chars]. Software
recover from the error. Recommended user
action: [chars] Recommended user action: action: %s - description of the
[chars]
recommended user action.

Device: [chars]. Error: [chars] threshold

exceeded. Software action: [chars]

A hardware error reached threshold on the

Datapath FPGA. Software will take action as
described in the error message to try to
recover from the error. The hardware error
and the software recovery action will cause
linecard reload. Device: %s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error.

Device: [chars]. Error: [chars]. Software

action: [chars]

A hardware error is detected on the

Datapath FPGA. Software will take action as
described in the error message to try to
recover from the error. The hardware error
and the software recovery action will cause
linecard reload. Device: %s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error.

PLASPA: [chars]

EIO training errors. The EIO link to the

PLASPA failed to train. This will result in
traffic loss through this PLIM.

[chars]: [chars]: [hex]

PLIM FPGA ASIC Driver encountered a

critical error as described in the error
message. This error causes PLIM OC768
process to exit.

[chars]

Plim datapath fpga driver errors. Typically

these errors indicate failure in system
services or bad programming of the
hardware.

Device: [chars]. Error: [chars]. Software

action: [chars]

A hardware error is detected on the

Datapath FPGA. Software will take action as
described in the error message to try to
recover from the error. The hardware error
and the software recovery action will cause
hard reset of a device in the data path and
will impact traffic. Device: %s - indicates
the device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error.

Device: [chars]. Error: [chars] threshold

exceeded. Software action: [chars]

A hardware error reached threshold on the

Datapath FPGA. Software will take action as
described in the error message to try to
recover from the error. The hardware error
and the software recovery action will cause
hard reset of a device in the data path and
will impact traffic. Device: %s - indicates
the device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error.

datapath-fpga instance [dec] [chars],

[chars]

Plim datapath fpga errors. Typically these

indicate errors detected by the ASIC. Too
many of these errors might indicate
problem with the board, and can trigger a
reload of the LC.

[chars]

Plim datapath fpga driver imdr errors.

Typically these errors indicate failure in
system services during the imdr procedure.

Ltrace init for file [chars] failed [chars]

--

Asic PIO failure : [chars], instance [dec]: rc

[dec] cerr [chars] errno [dec] data1 [hex]
A critical error occurred in PLIM FPGA Driver
data2 [hex]
which involves exiting the process.

datapath-fpga instance [dec]: [chars]

Plim datapath fpga errors. Typically these

indicate errors detected by the ASIC. Too
many of these errors might indicate
problem with the board, and may trigger
packet loss. These errors seen during LC
boot up or SPA OIR are harmless.

[chars]: [chars]

This is a informational message from PLIM

FPGA driver to indicate an operation.

Debug: [chars]: [chars] value [dec]

This is a debug message in PLIM FPGA

driver to indicate anomolies which are not
FATAL. Some of the messages may indicate
a failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temperory situation is resolved.

Initialization error: [chars]: [chars]

The 4 port Gigabit Ethernet (GE) driver

failed to initialize properly. This driver
provides the system access to the
hardware. A failure during initialization of
this process may render the interfaces
provided by the hardware unusable. %s indicates the reason for the failure %s - is
the decoded error reason

[chars] [dec]

This is an Informational message in the

plim_iox_4p_ge driver to indicate operation
that may be of interest to the user.

SFP Rx LOS Interrupt: port: [dec],

count=[dec]

This is an informational message in the

gigE driver driver to indicate a Loss of
Signal (LOS) has occurred on the indicated
port.

Physical layer interface module library

failed to reply to the Fault Manager for
error recovery: [chars]

The PLIM driver soft error recovery failed

because the PLIM library function failed
with replying to the Fault Manager request.
If the PLIM soft error recovery failed, the
PLIM hardware state may not be in the
correct state, and the traffic may be
affected. %s - is the decoded error reason

When a soft error is detected with any ASIC

on the datapath, the Fault Manager will
start the soft error recovery on the
datapath. If the Fault Manager cannot send
request to the PLIM driver, the soft error
recovery will not be completed, therefore
The Fault Manager cannot send message to the traffic will not go through the datapath.
physical layer interface module driver to
%s - indicates the reason for the failure %s
start soft error recovery: [chars]/[chars]
- is the decoded error reason

Physical layer interface module library

initialization failed: ([chars]/[chars]).

The physical layer interface module (PLIM)

library on the linecard failed to initialize.
The PLIM library is used by PLIM driver
which creates the SONET controller, POS
interface, handling the all the SONET event
and applying SONET/POS configuration to
the layer1 devices. If the PLIM driver failed
to initialize, no traffic will pass, therefore
no higher level protocol will work. %s indicates the reason for the failure %s - is
the decoded error reason

error: [chars]: [chars]: [hex]

A fatal error occurred in the plim library

driver which involves exiting the process.

error: [chars]: [chars]: [hex]

A fatal error occurred in the plim library

driver which involves exiting the process.

error: [chars]. reason: [chars]

A fatal error occured during

sysdb_register_notification for PLIM
process. With this, config change in the
syslogTXfault will not be notified to the
respective PLIM process.

error: [chars]. reason: [chars]

A fatal error occured during

sysdb_register_notification for PLIM
process. With this, config change in the
syslogTXfault will not be notified to the
respective PLIM process.

Physical layer interface module library

failed in receiving the message: [chars]

The PLIM library detects a failure condition

when receiving the message. The message
is used only for error recovery, the process
should not receive the message in normal
case. This error means a error condition is
detected while the process is waiting for a
message, it can be ignored if the error does
not persist. Otherwise, if the error persists,
it is recommended to restart the process,
restarting process will not affect the traffic.

[chars]

This is a debug message in the PLIM library

driver to indicate anomolies which are not
FATAL. Some of the messages may indicate
a failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temperory situation is resolved.

[chars]

This is a debug message in the PLIM library

driver to indicate anomolies which are not
FATAL. Some of the messages may indicate
a failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temperory situation is resolved.

[chars]: [chars] errno [dec]

This is a debug message in the PLIM library

driver to indicate anomolies which are not
FATAL. Some of the messages may indicate
a failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temperory situation is resolved.

[chars]: [chars] errno [dec]

This is a debug message in the PLIM library

driver to indicate anomolies which are not
FATAL. Some of the messages may indicate
a failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temperory situation is resolved.

Process failed to allocate memory [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialized due to
unavailable memory and will be restarted.
It may affect traffic passing through the
ports located on the PLIM. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller, optical
transceiver. %s - error code

Process failed to allocate memory [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialized due to
unavailable memory and will be restarted.
It may affect traffic passing through the
ports located on the PLIM. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller, optical
transceiver. %s - error code

Process init failed [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller, optical
transceiver %s - error code

Process init failed [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller, optical
transceiver %s - error code

DSU bandwidth change for E3 controller is This is a known hardware limitation. The
not supported
bandwidth will be defaulted to 34010 kbps.

Physical Layer Interface Module(PLIM)

driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller. As result of
such failure no trafiic may pass on the oc48
port located on the linecard. The interfaces
associated with failed PLIM will not come
Interface module driver initialization failed up.

Physical Layer Interface Module(PLIM)

driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller. As result of
such failure no trafiic may pass on the oc48
port located on the linecard. The interfaces
associated with failed PLIM will not come
Interface module driver initialization failed up.

process received invalid event [chars]

Physical Layer Interface Module(PLIM)

driver experience an errorr while awaiting
for event arrival. PLIM driver is responsible
for initializing/configuring PLIM hardware
such as sonet framer, Packet Over
Sonet(POS) controller. As result of the error
the PLIM process will be restarted. Traffic
may be interrupted on all affected
interfaces. %s - error code

process received invalid event [chars]

Physical Layer Interface Module(PLIM)

driver experience an errorr while awaiting
for event arrival. PLIM driver is responsible
for initializing/configuring PLIM hardware
such as sonet framer, Packet Over
Sonet(POS) controller. As result of the error
the PLIM process will be restarted. Traffic
may be interrupted on all affected
interfaces. %s - error code

Optical parameter measurement error

[chars]

Physical Layer Interface Module(PLIM)

driver failed to measure laser bias or
optical receive power. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller, optical
transceiver. PLIM driver performs periodic
measurements of the laser bias and
received signal optical power. The results of
such measurements are represented in the
'show controller pos 0/slot/0/0' command
under the 'optical power monitoring'
section. %s - error code

Optical parameter measurement error

[chars]

Physical Layer Interface Module(PLIM)

driver failed to measure laser bias or
optical receive power. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller, optical
transceiver. PLIM driver performs periodic
measurements of the laser bias and
received signal optical power. The results of
such measurements are represented in the
'show controller pos 0/slot/0/0' command
under the 'optical power monitoring'
section. %s - error code

PLIM port init failed [dec] stage-[chars]

Physical Layer Interface Module(PLIM)

driver failed to initialize port. As result of
the failure affected interfaces will not come
up. %d - failed port number %s - specific
stage of port initialization that failed PLIM
driver is responsible for
initializing/configuring PLIM hardware such
as sonet framer and Packet Over
Sonet(POS) controller.

PLIM port init failed [dec] stage-[chars]

Physical Layer Interface Module(PLIM)

driver failed to initialize port. As result of
the failure affected interfaces will not come
up. %d - failed port number %s - specific
stage of port initialization that failed PLIM
driver is responsible for
initializing/configuring PLIM hardware such
as sonet framer and Packet Over
Sonet(POS) controller.

Process initialization error [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialized and will be
restarted. It will affect traffic passing
through the ports located on the PLIM. PLIM
driver is responsible for
initializing/configuring PLIM hardware such
as sonet framer, Packet Over Sonet(POS)
controller, optical transceiver. %s - error
code

Process initialization error [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialized and will be
restarted. It will affect traffic passing
through the ports located on the PLIM. PLIM
driver is responsible for
initializing/configuring PLIM hardware such
as sonet framer, Packet Over Sonet(POS)
controller, optical transceiver. %s - error
code

[chars]: [chars] Not IM Initialized yet

IM is not initialised yet

[chars]: Null chn ctx

Gulf Channel Context is Null

Port failed to become available [chars]

[dec]

Physical Layer Interface Module(PLIM)

driver failed to make port available for
forwarding. The interface in question will
not forward packets. %s - error code %d port number

Port failed to become available [chars]

[dec]

Physical Layer Interface Module(PLIM)

driver failed to make port available for
forwarding. The interface in question will
not forward packets. %s - error code %d port number

PLIM reset failed [chars]

The Physical Layer Interface Module(PLIM)

driver failed to reset PLIM hardware. %s error code PLIM driver is responsible for
initializing/configuring PLIM hardware such
as sonet framer, Packet Over Sonet(POS)
controller.

PLIM reset failed [chars]

The Physical Layer Interface Module(PLIM)

driver failed to reset PLIM hardware. %s error code PLIM driver is responsible for
initializing/configuring PLIM hardware such
as sonet framer, Packet Over Sonet(POS)
controller.

Physical Layer Interface Module(PLIM)

driver failed to register PLIM interface
statistics collector. No interface statistics
such as sonet counters and packet
counters will be available on the specified
Statistics collector registration error [chars] interface. %s - contains interface name %s
[chars]
- contains error code

Process initialization error [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialized and will be
restarted. It will affect traffic passing
through the ports located on the PLIM. PLIM
driver is responsible for
initializing/configuring PLIM hardware such
as sonet framer, Packet Over Sonet(POS)
controller, optical transceiver %s - error
code

Process init failed [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller, optical
transceiver. %s - error code

Process init failed [chars]

Physical Layer Interface Module(PLIM)

driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM
hardware such as sonet framer, Packet
Over Sonet(POS) controller, optical
transceiver. %s - error code

Failed to retrieve tx clock source

Physical Layer Interface Module(PLIM)

driver was unable to determine transmit
clock source for the sonet port. The error
may appear during show or configuration
of the sonet port.

Failed to retrieve tx clock source

Physical Layer Interface Module(PLIM)

driver was unable to determine transmit
clock source for the sonet port. The error
may appear during show or configuration
of the sonet port.

Physical Layer Interface Module(PLIM)

driver failed to make configure transmit
clock source for the sonet port. The sonet
port hardware configuration is invalid and
may result in traffic being dropped or high
error count on the port. This error may
Failed to configure tx clock source for sonet appear during attempt to configure clock
port
source for the sonet port.

Physical Layer Interface Module(PLIM)

driver failed to make configure transmit
clock source for the sonet port. The sonet
port hardware configuration is invalid and
may result in traffic being dropped or high
error count on the port. This error may
Failed to configure tx clock source for sonet appear during attempt to configure clock
port
source for the sonet port.

Invalid timer [dec]

Physical Layer Interface Module(PLIM)

driver received unknown timer event. %d timer type

Invalid timer [dec]

Physical Layer Interface Module(PLIM)

driver received unknown timer event. %d timer type

[chars]: Gulf chip version(=[dec]) lesser

than [dec] is not supported.

This Gulf Chip Version is not supported as it

is lesser than working version.

[chars]: Disabling the LASER\n

Turning off the Laser while disabling the

Port

[chars]: Enabling the LASER\n

Turning on the Laser while enabling the

Port

[chars]: [chars]: [hex]

PLIM OC768 driver encountered a critical

error as described in the error message.
This error causes PLIM OC768 process to
exit.

[chars]: [chars]

This is an informational message from PLIM

OC768 driver to indicate an operation.

Debug: [chars]: [chars] errno [dec]

This is a debug message in the plim_oc768

driver to indicate anomolies which are not
FATAL. Some of the messages may indicate
a failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temperory situation is resolved.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will put linecard in
RESET state. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
Device: [chars]%s. Error: [chars]. Software software will take to try to recover from the
action: [chars]
error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause linecard
reload. Device: %s%s - indicates the device
on which the error is detected. Error: %s description of the hardware error. Software
Device: [chars]%s. Error: [chars]. Software action: %s - the action that software will
action: [chars]
take to try to recover from the error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause linecard
reload. Device: %s%s - indicates the device
on which the error is detected. Error: %s description of the hardware error. Software
Device: [chars]%s. Error: [chars]. Software action: %s - the action that software will
action: [chars]
take to try to recover from the error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause linecard
reload. Device: %s%s - indicates the device
on which the error is detected. Error: %s description of the hardware error. Software
Device: [chars]%s. Error: [chars]. Software action: %s - the action that software will
action: [chars]
take to try to recover from the error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause linecard
reload. Device: %s%s - indicates the device
on which the error is detected. Error: %s description of the hardware error. Software
Device: [chars]%s. Error: [chars]. Software action: %s - the action that software will
action: [chars]
take to try to recover from the error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause linecard
reload. Device: %s%s - indicates the device
on which the error is detected. Error: %s description of the hardware error. Software
Device: [chars]%s. Error: [chars]. Software action: %s - the action that software will
action: [chars]
take to try to recover from the error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause linecard
reload. Device: %s%s - indicates the device
on which the error is detected. Error: %s description of the hardware error. Software
Device: [chars]%s. Error: [chars]. Software action: %s - the action that software will
action: [chars]
take to try to recover from the error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message, if not none, to try to
recover from the error. The hardware error
and the software recovery action will not
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error. Recommended user action: %s recommended action to the user. Possible
Device: [chars]%s. Error: [chars]. Software values: 'none' 'replace XFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM.

Software will take action as described in
the error message, if not none, to try to
recover from the error. The hardware error
and the software recovery action will not
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error. Recommended user action: %s recommended action to the user. Possible
Device: [chars]%s. Error: [chars]. Software values: 'none' 'replace XFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
linecard reload. Device: %s%s - indicates
the device on which the error is detected.
Error: %s - description of the hardware
error. Threshold of %s - the defined
Device: [chars]%s. Error: [chars]. Threshold threshold for this error. Software action: %s
of [chars] has been crossed. Software
- the action that software will take to try to
action: [chars]
contain or recover from the error.

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
linecard reload. Device: %s%s - indicates
the device on which the error is detected.
Error: %s - description of the hardware
error. Threshold of %s - the defined
Device: [chars]%s. Error: [chars]. Threshold threshold for this error. Software action: %s
of [chars] has been crossed. Software
- the action that software will take to try to
action: [chars]
contain or recover from the error.

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
linecard reload. Device: %s%s - indicates
the device on which the error is detected.
Error: %s - description of the hardware
error. Threshold of %s - the defined
Device: [chars]%s. Error: [chars]. Threshold threshold for this error. Software action: %s
of [chars] has been crossed. Software
- the action that software will take to try to
action: [chars]
contain or recover from the error.

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
linecard reload. Device: %s%s - indicates
the device on which the error is detected.
Error: %s - description of the hardware
error. Threshold of %s - the defined
Device: [chars]%s. Error: [chars]. Threshold threshold for this error. Software action: %s
of [chars] has been crossed. Software
- the action that software will take to try to
action: [chars]
contain or recover from the error.

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
linecard reload. Device: %s%s - indicates
the device on which the error is detected.
Error: %s - description of the hardware
error. Threshold of %s - the defined
Device: [chars]%s. Error: [chars]. Threshold threshold for this error. Software action: %s
of [chars] has been crossed. Software
- the action that software will take to try to
action: [chars]
contain or recover from the error.

PLA: [chars], [chars]

EIO training errors. The PLA EIO failed to

train... this will result in traffic loss and the
MSC will fail to send traffic thru the PLIM.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause hard
reset of a device in the data path and will
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
Device: [chars]%s. Error: [chars]. Software software will take to try to recover from the
action: [chars]
error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause hard
reset of a device in the data path and will
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
Device: [chars]%s. Error: [chars]. Software software will take to try to recover from the
action: [chars]
error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause hard
reset of a device in the data path and will
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
Device: [chars]%s. Error: [chars]. Software software will take to try to recover from the
action: [chars]
error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause hard
reset of a device in the data path and will
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
Device: [chars]%s. Error: [chars]. Software software will take to try to recover from the
action: [chars]
error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause hard
reset of a device in the data path and will
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
Device: [chars]%s. Error: [chars]. Software software will take to try to recover from the
action: [chars]
error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause hard
reset of a device in the data path and will
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
Device: [chars]%s. Error: [chars]. Software software will take to try to recover from the
action: [chars]
error.

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause hard
reset of a device in the data path and will
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
Device: [chars]%s. Error: [chars]. Software software will take to try to recover from the
action: [chars]
error.

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
hard reset of a device in the data path and
will impact traffic. Device: %s%s - indicates
the device on which the error is detected.
Error: %s - description of the hardware
error. Threshold of %s - the defined
Device: [chars]%s. Error: [chars]. Threshold threshold for this error. Software action: %s
of [chars] has been crossed. Software
- the action that software will take to try to
action: [chars]
contain or recover from the error.

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
hard reset of a device in the data path and
will impact traffic. Device: %s%s - indicates
the device on which the error is detected.
Error: %s - description of the hardware
error. Threshold of %s - the defined
Device: [chars]%s. Error: [chars]. Threshold threshold for this error. Software action: %s
of [chars] has been crossed. Software
- the action that software will take to try to
action: [chars]
contain or recover from the error.

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
hard reset of a device in the data path and
will impact traffic. Device: %s%s - indicates
the device on which the error is detected.
Error: %s - description of the hardware
error. Threshold of %s - the defined
Device: [chars]%s. Error: [chars]. Threshold threshold for this error. Software action: %s
of [chars] has been crossed. Software
- the action that software will take to try to
action: [chars]
contain or recover from the error.

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
hard reset of a device in the data path and
will impact traffic. Device: %s%s - indicates
the device on which the error is detected.
Error: %s - description of the hardware
error. Threshold of %s - the defined
Device: [chars]%s. Error: [chars]. Threshold threshold for this error. Software action: %s
of [chars] has been crossed. Software
- the action that software will take to try to
action: [chars]
contain or recover from the error.

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
hard reset of a device in the data path and
will impact traffic. Device: %s%s - indicates
the device on which the error is detected.
Error: %s - description of the hardware
error. Threshold of %s - the defined
Device: [chars]%s. Error: [chars]. Threshold threshold for this error. Software action: %s
of [chars] has been crossed. Software
- the action that software will take to try to
action: [chars]
contain or recover from the error.

[chars] FPGA is running rollback image, no The FPGA is running rollback image, this
interface on the PLIM will be up before the could be caused by previous FPD failure.
FPGA is upgraded to the correct version
%s - device name, Rx MAC or Tx MAC.

The FPGA is running rollback image, this

[chars] FPGA is running rollback image, no could be caused by previous FPD failure.
interface on the PLIM will be up before the %s - device name, PLIM FPGA or OPTICS
FPGA is upgraded to the correct version
FPGA

[chars] FPGA is running rollback image, no The FPGA is running rollback image, this
interface on the PLIM will be up before the could be caused by previous FPD failure.
FPGA is upgraded to the correct version
%s - device name, Rx MAC or Tx MAC.

[chars] FPGA is running rollback image, no The FPGA is running rollback image, this
interface on the PLIM will be up before the could be caused by previous FPD failure.
FPGA is upgraded to the correct version
%s - device name, Rx MAC or Tx MAC.

The FPGA is running rollback image, this

[chars] FPGA is running rollback image, no could be caused by previous FPD failure.
interface on the PLIM will be up before the %s - device name, PLIM FPGA or OPTICS
FPGA is upgraded to the correct version
FPGA

FPGA software revision mismatch, the PLIM

may not be fully functional, please upgrade
FPGA with the FPD CLI. The FPGA software
revision: [hex], the revision needed by the
software: [hex]

The FPGA software revision is different with

the one supported by the running software,
this could be caused by software upgrade
which supports the new FPGA software
revision.

FPGA software revision mismatch, the PLIM

may not be fully functional, to upgrade
fpga Use the upgrade hw-module fpd CLI in
admin mode

The FPGA software revision is different with

the one supported by the running software,
this could be caused by software upgrade
which supports the new FPGA software
revision.

FPGA software revision mismatch, the

FLEX-PLIM may not be fully functional, to
upgrade fpga Use the upgrade hw-module
fpd CLI in admin mode

The FPGA software revision is different with

the one supported by the running software,
this could be caused by software upgrade
which supports the new FPGA software
revision.

FPGA software revision mismatch, the PLIM

may not be fully functional, to upgrade
fpga Use the upgrade hw-module fpd CLI in
admin mode

The FPGA software revision is different with

the one supported by the running software,
this could be caused by software upgrade
which supports the new FPGA software
revision.

Hardware initialization failed. Reason:

[chars]

The PLIM process failed to spawn due to

failure in the PLIM hardware initialization
process. The PLIM process is the driver for
all PLIM hardware devices. %s - indicates
the reason for the failure.

Hardware initialization failed. Reason:

[chars]

The PLIM process failed to spawn due to

failure in the PLIM hardware initialization
process. The PLIM process is the driver for
all PLIM hardware devices. %s - indicates
the reason for the failure.

Hardware initialization failed. Reason:

[chars]

The PLIM process failed to spawn due to

failure in the PLIM hardware initialization
process. The PLIM process is the driver for
all PLIM hardware devices. %s - indicates
the reason for the failure.

Hardware initialization failed. Reason:

[chars]

The PLIM process failed to spawn due to

failure in the PLIM hardware initialization
process. The PLIM process is the driver for
all PLIM hardware devices. %s - indicates
the reason for the failure.

OBI FPGA has seen excessive Single Bit

Errors. Disabling SBE interrupt.

OBI FPGA has seen excessive Single Bit

Errors. Disabling the SBE interrupt. Reload
the linecard during next maintenance
window.

OBI FPGA has seen excessive Watchdog

timeout Errors. Disabling WDT interrupt.

OBI FPGA has seen excessive Watchdog

timeout Errors. Disabling the WDT
interrupt. Reload the linecard during next
maintenance window.

Port [dec], Distributed clock unable to

recover, disabling the port.

The PHY device experienced a distributed

clocking failure and software could not
recover the problem. The port has been
disabled.

Port [dec], Distributed clock unable to

recover, disabling the port.

The PHY device experienced a distributed

clocking failure and software could not
recover the problem. The port has been
disabled.

Port [dec], Distributed clock unable to

recover, disabling the port.

The PHY device experienced a distributed

clocking failure and software could not
recover the problem. The port has been
disabled.

The XAUI bus between the PLA ASIC and

PHY device experienced a synchronization
problem resulting in a lane failure causing
Port [dec], Tx data path failure between the a link flap. Software could not recover the
PHY and PLA devices, disabling port.
problem and the port has been disabled.

The XAUI bus between the PLA ASIC and

PHY device experienced a synchronization
problem resulting in a lane failure causing
Port [dec], Tx data path failure between the a link flap. Software could not recover the
PHY and PLA devices, disabling port.
problem and the port has been disabled.

The XAUI bus between the PLA ASIC and

PHY device experienced a synchronization
problem resulting in a lane failure causing
Port [dec], Tx data path failure between the a link flap. Software could not recover the
PHY and PLA devices, disabling port.
problem and the port has been disabled.

Software cannot access the PLIM protection Software could not access the PPS device
switch.
during initialization.

Software cannot access the PLIM protection Software could not access the PPS device
switch.
during initialization.

Software cannot access the PLIM protection Software could not access the PPS device
switch.
during initialization.

Port [dec], XFP alarm condition exceeds

threshold of [chars], disabling interrupt.

XFP alarm condition interrupt exceeded the

defined threshold. Software will disable the
interrupt. It is recommended to replace the
XFP module.

Port [dec], XFP alarm condition exceeds

threshold of [chars], disabling interrupt.

XFP alarm condition interrupt exceeded the

defined threshold. Software will disable the
interrupt. It is recommended to replace the
XFP module.

Port [dec], XFP alarm condition exceeds

threshold of [chars], disabling interrupt.

XFP alarm condition interrupt exceeded the

defined threshold. Software will disable the
interrupt. It is recommended to replace the
XFP module.

Port [dec], XFP lost power ok state,

powering off.

The XFP device lost its power OK state

causing the link to flap. Software tried to
recover the issue by reseting the XFP
device but the problem persisted and the
XFP device has been powered off. It is
recommended to replace the XFP module.

Device: XFP port [dec], Error: XFP power

fault, Software Action: Power off XFP,
Recommended User Action: Replace XFP.

The XFP device lost its power OK state

causing the link to flap. Software tried to
recover the issue by reseting the XFP
device but the problem persisted and the
XFP device has been powered off. It is
recommended to replace the XFP module.

Port [dec], XFP lost power ok state,

powering off.

The XFP device lost its power OK state

causing the link to flap. Software tried to
recover the issue by reseting the XFP
device but the problem persisted and the
XFP device has been powered off. It is
recommended to replace the XFP module.

PLA: [chars], [chars]

Checkpoint Initialization Failure. The

pla_server process failed to initialize its
checkpointing data. The process cannot
continue and needs to be restarted.

'[chars]'

fail to init debug events; sysdb fails to

provide services; event mgr fails to
provides its services;

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause
shutting down the port. Device: %s%s indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Software action: %s - the
action that software will take to try to
recover from the error. Recommended user
action: %s - recommended action to the
Device: [chars]%s. Error: [chars]. Software user. Possible values: 'none' 'replace CFP'
action: [chars]. Recommended user action: 'PLEASE MANUAULLY RELOAD THE LC AT
[chars]
NEXT MAINTENANCE WINDOW'

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause
shutting down the port. Device: %s%s indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Software action: %s - the
action that software will take to try to
recover from the error. Recommended user
action: %s - recommended action to the
Device: [chars]%s. Error: [chars]. Software user. Possible values: 'none' 'replace XFP'
action: [chars]. Recommended user action: 'PLEASE MANUAULLY RELOAD THE LC AT
[chars]
NEXT MAINTENANCE WINDOW'

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause
shutting down the port. Device: %s%s indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Software action: %s - the
action that software will take to try to
recover from the error. Recommended user
action: %s - recommended action to the
Device: [chars]%s. Error: [chars]. Software user. Possible values: 'none' 'replace XFP'
action: [chars]. Recommended user action: 'PLEASE MANUAULLY RELOAD THE LC AT
[chars]
NEXT MAINTENANCE WINDOW'

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause
shutting down the port. Device: %s%s indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Software action: %s - the
action that software will take to try to
recover from the error. Recommended user
action: %s - recommended action to the
Device: [chars]%s. Error: [chars]. Software user. Possible values: 'none' 'replace CFP'
action: [chars]. Recommended user action: 'PLEASE MANUAULLY RELOAD THE LC AT
[chars]
NEXT MAINTENANCE WINDOW'

A hardware error is detected on the PLIM.

Software will take action as described in
the error message to try to recover from
the error. The hardware error and the
software recovery action will cause
shutting down the port. Device: %s%s indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Software action: %s - the
action that software will take to try to
recover from the error. Recommended user
action: %s - recommended action to the
Device: [chars]%s. Error: [chars]. Software user. Possible values: 'none' 'replace
action: [chars]. Recommended user action: Optics' 'PLEASE MANUAULLY RELOAD THE
[chars]
LC AT NEXT MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
shutting down the port. Device: %s%s indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace CFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
shutting down the port. Device: %s%s indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace XFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
shutting down the port. Device: %s%s indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace Optics' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
shutting down the port. Device: %s%s indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace CFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
shutting down the port. Device: %s%s indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace XFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message to try to contain or
recover from the error. The hardware error
and the software recovery action will cause
shutting down the port. Device: %s%s indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace XFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

'asic error: [chars]'

Plim Asic errors. Typically these indicate

errors detected by the ASIC. Too many of
these errors might indicate problem with
the board, and can trigger a reload of the
LC.

Hardware Initialization Failed, Reason:

[chars]

The PLIM process failed to spawn as it

could not access PLIM hardware during the
initialization process. The process will not
be re-spawned. The PLIM process is the
driver for all PLIM hardware devices. %s indicates the reason for the failure.

Hardware Initialization Failed, Reason:

[chars]

The PLIM process failed to spawn as it

could not access PLIM hardware during the
initialization process. The process will not
be re-spawned. The PLIM process is the
driver for all PLIM hardware devices. %s indicates the reason for the failure.

Hardware Initialization Failed, Reason:

[chars]

The PLIM process failed to spawn as it

could not access PLIM hardware during the
initialization process. The process will not
be re-spawned. The PLIM process is the
driver for all PLIM hardware devices. %s indicates the reason for the failure.

PLA iMDR: [chars]

PLA driver encountered an error during

iMDR procedure. The pla_server process
encountered an error during iMDR
procedure.

[chars]

As part of trying to configure dot1q vlan

with vlan id same as that of outer vlan of
QinQ configuration or vice versa on another
sub-interface, then error has to be reported
to remove the inconsistent config.

Interrupt handling error.

The PLIM process failed to handle an

interrupt.

Interrupt handling error.

The PLIM process failed to handle an

interrupt.

Interrupt handling error.

The PLIM process failed to handle an

interrupt.

[chars]

fail to allocate memory.

Port [dec], Error: Optics not certified for

[chars] mode line-rate. Software action:
None. Recommended action: Replace
optics or change configuration

Optics unable to support configured linerate; replace optics OR change

configuration.

Port [dec], Access to the PHY device failed, Software could not access the PHY device
disabling port.
during port initialization.

Port [dec], Access to the PHY device failed, Software could not access the PHY device
disabling port.
during port initialization.

Port [dec], Access to the PHY device failed, Software could not access the PHY device
disabling port.
during port initialization.

Port [dec], Software cannot access

SFPPLUS, powering off.

Software could not access the optics

module during initialization.

'[chars]'

squid fails to find the device

Port [dec]. Operation: [chars]. Error:

[chars]. Software action: Abort

The operation is failed due to an internal

software error. %d - port number. %s description of the operation. %s description of the error.

Port [dec]. Operation: [chars]. Error:

[chars]. Software action: Abort

The operation is failed due to an internal

software error. %d - port number. %s description of the operation. %s description of the error.

Port [dec]. Operation: [chars]. Error:

[chars]. Software action: Abort

The operation is failed due to an internal

software error. %d - port number. %s description of the operation. %s description of the error.

Port [dec]. Operation: [chars]. Error:

[chars]. Software action: Abort

The operation is failed due to an internal

software error. %d - port number. %s description of the operation. %s description of the error.

Software Initialization Failed, Reason:

[chars]

The PLIM process failed to spawn due to an

internal software problem during the
initialization process. The process will
automatically respawn up to a fixed
number of times to try and recover. The
PLIM process is the driver for all PLIM
hardware devices. %s - indicates the
reason for the failure.

Software initialization failed. Reason:

[chars]

The PLIM process failed to spawn due to an

internal software problem during the
initialization process. The process will
automatically respawn up to a fixed
number of times to try and recover. The
PLIM process is the driver for all PLIM
hardware devices. %s - indicates the
reason for the failure.

Software initialization failed. Reason:

[chars]

The PLIM process failed to spawn due to an

internal software problem during the
initialization process. The process will
automatically respawn up to a fixed
number of times to try and recover. The
PLIM process is the driver for all PLIM
hardware devices. %s - indicates the
reason for the failure.

Software initialization failed. Reason:

[chars]

The PLIM process failed to spawn due to an

internal software problem during the
initialization process. The process will
automatically respawn up to a fixed
number of times to try and recover. The
PLIM process is the driver for all PLIM
hardware devices. %s - indicates the
reason for the failure.

Software Initialization Failed, Reason:

[chars]

The PLIM process failed to spawn due to an

internal software problem during the
initialization process. The process will
automatically respawn up to a fixed
number of times to try and recover. The
PLIM process is the driver for all PLIM
hardware devices. %s - indicates the
reason for the failure.

Software Initialization Failed, Reason:

[chars]

The PLIM process failed to spawn due to an

internal software problem during the
initialization process. The process will
automatically respawn up to a fixed
number of times to try and recover. The
PLIM process is the driver for all PLIM
hardware devices. %s - indicates the
reason for the failure.

Software initialization failed. Reason:

[chars]

The PLIM process failed to spawn due to an

internal software problem during the
initialization process. The process will
automatically respawn up to a fixed
number of times to try and recover. The
PLIM process is the driver for all PLIM
hardware devices. %s - indicates the
reason for the failure.

Port [dec], Software cannot access XFP,

powering off.

Software could not access the optics

module during initialization.

Port [dec], Software cannot access XFP,

powering off.

Software could not access the optics

module during initialization.

Port [dec], Software cannot access XFP,

powering off.

Software could not access the optics

module during initialization.

Port [dec], Error: XFP EEPROM corruption.

Software action: Putting XFP in low power
mode. Recommended action: Replace XFP

XFP EEPROM got corrupted; replace XFP

Port [dec], XFP failed to reach power ok

state, powering off.

The inserted XFP failed to power on

correctly.

Port [dec], XFP failed to reach power ok

state, powering off.

The inserted XFP failed to power on

correctly.

Device: XFP Port [dec]. Operation: Enable

power. Error: Persistent power fault.
Software action: Powering off XFP.
Recommended user action: Replace XFP.

The inserted XFP failed to power on

correctly.

Port [dec], Error: XFP not certified for

[chars] mode line-rate. Software action:
None. Recommended action: Replace XFP
or change configuration

XFP unable to support configured line-rate;

replace XFP OR change configuration.

Interface [chars], [chars] Alarm [chars]

Warning Alarm is raised due to BIP Error

Threshold Violation Interface is brought
down, if user has configured it. %s Interface Name. %s - BER Type. %s - Alarm
state.

CFP: Operation: [chars]. Warning: [chars].

Information: [chars].

An issue is detected during operation on

Optic interface module. %d - port number.
%s - description of the operation. %s description of the issue. %s - reason for the
issue

CFP: Operation: [chars]. Warning: [chars].

Information: [chars].

An issue is detected during operation on

Optic interface module. %d - port number.
%s - description of the operation. %s description of the issue. %s - reason for the
issue

CFP: Operation: [chars]. Warning: [chars].

Information: [chars].

An issue is detected during operation on

Optic interface module. %d - port number.
%s - description of the operation. %s description of the issue. %s - reason for the
issue

A hardware error is detected on the PLIM.

Software will take action as described in
the error message, if not none, to try to
recover from the error. The hardware error
and the software recovery action will not
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error. Recommended user action: %s recommended action to the user. Possible
Device: [chars]%s. Error: [chars]. Software values: 'none' 'replace CFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM.

Software will take action as described in
the error message, if not none, to try to
recover from the error. The hardware error
and the software recovery action will not
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error. Recommended user action: %s recommended action to the user. Possible
Device: [chars]%s. Error: [chars]. Software values: 'none' 'replace CFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM.

Software will take action as described in
the error message, if not none, to try to
recover from the error. The hardware error
and the software recovery action will not
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error. Recommended user action: %s recommended action to the user. Possible
Device: [chars]%s. Error: [chars]. Software values: 'none' 'replace CPAK/QSFP/SFP+'
action: [chars]. Recommended user action: 'PLEASE MANUAULLY RELOAD THE LC AT
[chars]
NEXT MAINTENANCE WINDOW'

A hardware error is detected on the PLIM.

Software will take action as described in
the error message, if not none, to try to
recover from the error. The hardware error
and the software recovery action will not
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error. Recommended user action: %s recommended action to the user. Possible
Device: [chars]%s. Error: [chars]. Software values: 'none' 'replace XFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM.

Software will take action as described in
the error message, if not none, to try to
recover from the error. The hardware error
and the software recovery action will not
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error. Recommended user action: %s recommended action to the user. Possible
Device: [chars]%s. Error: [chars]. Software values: 'none' 'replace XFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM.

Software will take action as described in
the error message, if not none, to try to
recover from the error. The hardware error
and the software recovery action will not
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error. Recommended user action: %s recommended action to the user. Possible
Device: [chars]%s. Error: [chars]. Software values: 'none' 'replace CFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM.

Software will take action as described in
the error message, if not none, to try to
recover from the error. The hardware error
and the software recovery action will not
impact traffic. Device: %s%s - indicates the
device on which the error is detected.
Error: %s - description of the hardware
error. Software action: %s - the action that
software will take to try to recover from the
error. Recommended user action: %s recommended action to the user. Possible
Device: [chars]%s. Error: [chars]. Software values: 'none' 'replace XFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message, if not none, to try to
contain or recover from the error. The
hardware error and the software recovery
action will not impact traffic. Device: %s%s
- indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace XFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message, if not none, to try to
contain or recover from the error. The
hardware error and the software recovery
action will not impact traffic. Device: %s%s
- indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace CFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message, if not none, to try to
contain or recover from the error. The
hardware error and the software recovery
action will not impact traffic. Device: %s%s
- indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace XFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message, if not none, to try to
contain or recover from the error. The
hardware error and the software recovery
action will not impact traffic. Device: %s%s
- indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace XFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message, if not none, to try to
contain or recover from the error. The
hardware error and the software recovery
action will not impact traffic. Device: %s%s
- indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace CFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message, if not none, to try to
contain or recover from the error. The
hardware error and the software recovery
action will not impact traffic. Device: %s%s
- indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace Optics' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

A hardware error is detected on the PLIM,

and the error threshold has been crossed.
Software will take action as described in
the error message, if not none, to try to
contain or recover from the error. The
hardware error and the software recovery
action will not impact traffic. Device: %s%s
- indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
take to try to contain or recover from the
error. Recommended user action: %s Device: [chars]%s. Error: [chars]. Threshold recommended action to the user. Possible
of [chars] has been crossed. Software
values: 'none' 'replace CFP' 'PLEASE
action: [chars]. Recommended user action: MANUAULLY RELOAD THE LC AT NEXT
[chars]
MAINTENANCE WINDOW'

Optics: Operation: [chars]. Warning:

[chars]. Information: [chars].

An issue is detected during operation on

Optic interface module. %d - port number.
%s - description of the operation. %s description of the issue. %s - reason for the
issue

Port [dec], Access to the PHY device failed, Software could not access the PHY device
software recovery complete.
during port initialization.

Port [dec], Access to the PHY device failed, Software could not access the PHY device
software recovery complete.
during port initialization.

Port [dec], Access to the PHY device failed, Software could not access the PHY device
software recovery complete.
during port initialization.

Port [dec], Distributed clock failure,

software recovery complete.

The PHY device experienced a distributed

clocking failure which resulted in a link
flap. A reset of the PHY device corrected
the issue.

Port [dec], Distributed clock failure,

software recovery complete.

The PHY device experienced a distributed

clocking failure which resulted in a link
flap. A reset of the PHY device corrected
the issue.

Port [dec], Distributed clock failure,

software recovery complete.

The PHY device experienced a distributed

clocking failure which resulted in a link
flap. A reset of the PHY device corrected
the issue.

The XAUI bus between the PLA ASIC and

PHY device experienced a synchronization
Port [dec], Tx data path failure between the problem resulting in a lane failure causing
PHY and PLA devices, software recovery
a link flap. A reset of the PHY device
complete.
corrected the issue.

The XAUI bus between the PLA ASIC and

PHY device experienced a synchronization
Port [dec], Tx data path failure between the problem resulting in a lane failure causing
PHY and PLA devices, software recovery
a link flap. A reset of the PHY device
complete.
corrected the issue.

The XAUI bus between the PLA ASIC and

PHY device experienced a synchronization
Port [dec], Tx data path failure between the problem resulting in a lane failure causing
PHY and PLA devices, software recovery
a link flap. A reset of the PHY device
complete.
corrected the issue.

Access to the PLIM protection switch failed, Software could not access the PPS device
software recovery complete.
during initialization.

Access to the PLIM protection switch failed, Software could not access the PPS device
software recovery complete.
during initialization.

Access to the PLIM protection switch failed, Software could not access the PPS device
software recovery complete.
during initialization.

[chars]: SEU initialization failed. Reason:

[chars]. All SBE in CRAM will be treated as
critical error

The Essential bitmap for MAC FPGA cannot

be obtained. The essential bitmap is used
to determine if a SBE in CRAM is critical.
This failure will not stop the PLIM process
from running, it only changes the behavior
of handling CRAM SBE. %s - Device name.
%s - indicates the reason for the failure.

[chars]: SEU initialization failed. Reason:

[chars]. All SBE in CRAM will be treated as
critical error

The Essential bitmap for MAC FPGA cannot

be obtained. The essential bitmap is used
to determine if a SBE in CRAM is critical.
This failure will not stop the PLIM process
from running, it only changes the behavior
of handling CRAM SBE. %s - Device name.
%s - indicates the reason for the failure.

[chars]: SEU initialization failed. Reason:

[chars]. All SBE in CRAM will be treated as
critical error

The Essential bitmap for MAC FPGA cannot

be obtained. The essential bitmap is used
to determine if a SBE in CRAM is critical.
This failure will not stop the PLIM process
from running, it only changes the behavior
of handling CRAM SBE. %s - Device name.
%s - indicates the reason for the failure.

Port [dec], Access to SFPPLUS failed,

software recovery complete.

Software reset the optics module as it

could not read or write to it during
initialization.

Device: [chars]. Error: [chars]. Software

action: [chars]

SPA hardware detected errron on the PLIM.

For this no software action is needed.

A hardware error is detected on the PLIM

SPA, and the error threshold has been
crossed. Software will take action as
described in the error message. Device: %s
- indicates the device on which the error is
detected. Error: %s - description of the
hardware error. Threshold of %s - the
defined threshold for this error. Software
action: %s - the action that software will
Device: [chars]. Error: [chars]. Threshold of take to try to contain or recover from the
[chars] has been crossed. Software action: error. Recommended user action: %s [chars]. Recommended user action: [chars] recommended action to the user.

Port [dec], Access to XFP failed, software

recovery complete.

Software reset the optics module as it

could not read or write to it during
initialization.

Port [dec], Access to XFP failed, software

recovery complete.

Software reset the optics module as it

could not read or write to it during
initialization.

Port [dec], Access to XFP failed, software

recovery complete.

Software reset the optics module as it

could not read or write to it during
initialization.

Port [dec], XFP hit alarm condition.

XFP hit alarm condition and raised

interrupt.

Port [dec], XFP hit alarm condition.

XFP hit alarm condition and raised

interrupt.

Port [dec], XFP hit alarm condition.

XFP hit alarm condition and raised

interrupt.

Port [dec], XFP failed to reach power ok

state, software recovery complete.

The inserted XFP failed to power on

correctly during initialization.

Port [dec], XFP failed to reach power ok

state, software recovery complete.

The inserted XFP failed to power on

correctly during initialization.

Devic: XFP Port [dec]. Operation: Enable

power. Warning: Power fault. Recoveryaction: Will try one more time.

The inserted XFP failed to power on

correctly during initialization.

Port [dec], XFP lost power ok state,

software recovery complete.

The XFP device lost its power OK state

causing the link to flap. A reset of the XFP
device corrected the issue.

Port [dec], XFP lost power ok state,

software recovery complete.

The XFP device lost its power OK state

causing the link to flap. A reset of the XFP
device corrected the issue.

Device: XFP port [dec], Error: XFP power

fault, Software Action: Reset XFP,
Recommended User Action: none.

The XFP device lost its power OK state

causing the link to flap. A reset of the XFP
device corrected the issue.

Interface TenGigE[chars], RX Low power

warning [chars]

XFP hit/recovered RX Low power warning.

Interface TenGigE[chars], RX Low power

warning [chars]

XFP hit/recovered RX Low power warning.

Interface TenGigE[chars], TX Low power

warning [chars]

XFP hit/recovered TX Low power warning.

Interface TenGigE[chars], TX Low power

warning [chars]

XFP hit/recovered TX Low power warning.

The Optic Module (CFP) for the specified

port has either been inserted or removed.
%s - either 'inserted' or 'removed' %d - port
Port [dec]: Optic interface module is [chars] number.

The Optic Module (CFP) for the specified

port has either been inserted or removed.
%s - either 'inserted' or 'removed' %d - port
Port [dec]: Optic interface module is [chars] number.

The Optic Module (CFP) for the specified

port has either been inserted or removed.
%s - either 'inserted' or 'removed' %d - port
Port [dec]: Optic interface module is [chars] number.

The Optic Module (CPAK/QSFP/SFP+) for

the specified port has either been inserted
or removed. %s - either 'inserted' or
Port [dec]: Optic interface module is [chars] 'removed' %d - port number.

PLA iMDR: [chars]

PLA driver informational message during

iMDR procedure.

Port [dec], Not enough power available to

power SFPPLUS, powering off.

There is not enough available power on the

PLIM to power on the SFPPLUS.

Port [dec], Not enough power available to

power XFP, powering off.

There is not enough available power on the

PLIM to power on the XFP.

Port [dec], Not enough power available to

power XFP, powering off.

There is not enough available power on the

PLIM to power on the XFP.

Port [dec], Error: Not enough power

available to power XFP. Software action:
powering off. Recommended action:
Replace XFP

There is not enough available power on the

PLIM to power on the XFP.

Port [dec], Error: Unsupported optics.

Software action: Power Off. Recommended The SFPPLUS optics inserted in the given
action: Replace optics
port is not supported on this PLIM.

Port [dec], Error: Unsupported XFP.

Software action: Power Off. Recommended The XFP inserted in the given port is not
action: Replace XFP
supported on this PLIM.

Port [dec], Unsupported XFP inserted,

powering off.

The XFP inserted in the given port is not

supported on this PLIM.

Port [dec], Unsupported XFP inserted,

powering off.

The XFP inserted in the given port is not

supported on this PLIM.

Optic Interface Module [chars] for port

[dec]

The Optic Interface Module (XFP) for the

specified port has either been inserted or
removed.

Optic Interface Module [chars] for port

[dec]

The Optic Interface Module (XFP) for the

specified port has either been inserted or
removed.

Optic Interface Module [chars] for port

[dec]

The Optic Interface Module (XFP) for the

specified port has either been inserted or
removed.

Port [dec], Invalid XFP EEPROM, will retry

after XFP power cycle

The Reading of XFP EEPROM failed; Retry is

attempted

Port [dec], Retrying XFP EEPROM read :

(retry_count [dec])

The Reading of XFP EEPROM failed; Retry is

attempted

Port [dec], Retrying XFP EEPROM read :

(retry_count [dec])

The Reading of XFP EEPROM failed; Retry is

attempted

Fatal error: [chars]: [chars]: [dec]

A fatal error occurred in karachi Driver

which involves exiting the process.

Info: [chars]: [chars]

This is a Informational message in the

karachi driver to indicate an operation.

Debug: [chars]: [chars] errno [dec]

This is a debug message in the karachi

driver to indicate anomolies which are not
FATAL. Some of the messages may indicate
a failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temperory situation is resolved.

A fatal error occurred in plim Driver which

[chars](): fatal error: [chars]: [chars]: [dec] involves exiting the process.

[chars](): warning: [chars]: [chars]: [dec]

A warning condition occurred in plim Driver

which involves exiting the process.

[chars]

A high severity error has occurred in PLIM

FPGA. This might result in the PLIM being
reset. %s - Error message indicating reason
for error

: [chars]: [dec]

A fatal error occurred during PM SAR Driver

cofiguration while creating or modifying a
VC or VP.

[chars]() [dec], chan:[dec],[dec],[dec]; cid:

[dec], sar:[dec] reason:[chars] status:[dec], A fatal error occurred when PM SAR Driver
ack:[hex], [hex], [hex], [hex]
collects the VC Stats from SAR hardware.

[chars]() [dec], close cosq failure. rsar:

[dec], ssar:[dec], queue:[dec], cosq_id:
[dec] reason:[chars]; status:[dec] ack:
[hex], [hex], [hex], [hex]

A fatal error occurred when PM SAR Driver

tried to create a COSQ.

[chars]() [dec], close vc failure. rsar:[dec],

ssar:[dec], vpi:[dec], vci:[dec] reason:
[chars]; status:[dec] ack:[hex], [hex], [hex], A fatal error occurred when PM SAR Driver
[hex]
tries to delete or modify the VC.

[chars]() [dec], SAR:[dec] poll incomplete

cmd ack, [chars]

A fatal error detected when Parsing the

command acknowledgement from SAR.

[chars]

This error indicates unsupported traffic

parameters are applied and indicates a
configuration issue.

[chars]() [dec], SAR:[dec] cmd poll timed

out, [chars]

A fatal error occurred during a SAR

Command Execution.

A fatal error occurred when posting

[chars]() [dec], SAR:[dec] post cmd failure. command to SAR. This might occur if the
status:[dec], [chars] [dec] ack:[hex], [hex], SAR is busy at times. In that case, this error
[hex], [hex]
can be ignored.

Fatal error: [chars]: [hex]

SAR device cx27470 initialization failed.

The failure could be at chip level or some
internal datastructure level.

[chars]() [dec], Get SAR:[dec], thread_id:

[dec] mutex timed out, [chars]

A fatal error occurred while trying to lock

SAR semaphore.

[chars]() [dec], open vc failure. rsar:[dec],

ssar:[dec], vpi:[dec], vci:[dec] reason:
[chars]; status:[dec], ack:[hex], [hex],
[hex], [hex]

A fatal error occurred when PM SAR Driver

cofiguration tried to create a new VC.

[chars]() [dec], open vp failure. sar:[dec]

vpi:[dec], reason:[chars]; ack:[hex], [hex],
[hex], [hex]

A fatal error occurred when PM SAR Driver

tries to open a VP tunnel.

[chars]() [dec], port stats failure. sar:[dec]

reason:[chars]; status:[dec], ack:[hex],
[hex], [hex], [hex]

A fatal error occurred when PM SAR Driver

collects the Port Stats from SAR hardware.

[chars] [dec]: reason [chars] errno:[dec]

CX27470 esys generic fatal error during

memory allocation.

[chars] [dec]: file [chars] [chars] [chars]

CX27470 esys load elf input file symbol not

found.

[chars]() [dec], reason:[chars]; sar:[dec],

log_entry_index:[dec], type:[dec], status:
[dec]

An event raised PM SAR Driver, check the

event type

[chars]() [dec], reason:[chars]; sar:[dec],

log_entry_index:[dec]

An unknown event raised PM SAR Driver

[chars]

PM622 TSP CX27470 warning condition

[chars]() [dec], sar:[dec], event type:[dec],

status:[dec]; hex dump:[hex], [hex], [hex],
[hex]
An unknown event raised PM SAR Driver.
[chars] [hex]
PM622 TSP CX27470 information
[chars]

PM622 TSP CX27470 debug information

Fault Injection Module PT [dec] hit [chars]

*RECUR* The requested operation couldn't

be completed as connection to Config
Manager was not proper.

Fault Injection Module PT [dec] hit [chars]

The interface creation in IM faces some

issue as there was some resource failure
detected.

Fault Injection Module PT 2 hit [chars]

The requested operation couldn't be

completed due to a low memory condition.

Fault Injection Module PT 1 has hit

While enabling the POS ports, all ports

were not enabled.

FIM registration failed

While initializing the POS component, the

Fault Injection module (FIM) registration got
failed.

Ltrace init failed, with code [chars], [dec]

Ltrace initialization failed. It shouldn't

hamper the functionality.

Failed to set MTU of [unsigned int] on

[chars]

The specified MTU could not be applied on

this interface.

[chars] failed to connect to the PIRD

database: [chars]

The specified process failed to connect to

PIRD shared memory database on
initialization.

A failure occurred during the initialization

Failure during intialization of [chars]. Error: of the process. This resulted in the restart
[chars]
of the process.

[chars] lost event: [chars]

The specified process failed to receive an

event that was sent to it.

Not supported: [chars] on <<CH[hex]>>

The specified configuration is not

supported by the dataplane.

Failed to create [chars] port [unsigned int]

data: [chars]

An error occurred when attempting to

create a SONET/POS port.

Failed to enable [chars] port [unsigned int]: An error occurred when attempting to
[chars]
enable a SONET/POS port.

Port [unsigned int] notified by SONET not

found in local database

A 'port available' notification was received

by the POS Interface driver from the G-POS
library for a port that is not known about.

The Max bandwidth of the port [dec] is

changed. Changing the soft bandwidth
accordingly.

The soft bandwidth is changed according to

the Max bandwidth of this port.

EOD notification is not received from RSI

for protocol: [dec]

PPInfo consumer didn't receive EOD(End Of

Download) notification from RSI agent. %d Indicates the AFI for which EOD notification
is not received.

STUB: global index scoping not yet

supported\n

Global indexing is not yet supported.

Process Initialization Failed: ([chars]%s)

The PPP execution agent process failed to

initialize. PPP execution agent programs
the Physical Layer Interface Module (PLIM)
for handling PPP encapsulation on a POS
link and also add capsulation for slowpath
packet processing. The reason of the failure
could be that the interface manager could
not set the interface and returned an error,
or could be due to unavailability of memory
resources. This can happen when the
linecard is coming up, or when the
encapsulation is changed to PPP. The effect
is that the interface will not come up using
PPP encapsulation. %s - indicates the
reason for the failure. %s - is the error
reason.

Failed to allocate batch for '[chars]'

The process failed to allocate memory to

handle the event described in the
message.

Error encountered in the event loop:

[chars]. The PPP EA process will restart

An error occured in the event loop. The

process will restart which should recover
the situation.

Failure during initialization of the [chars].

Error [chars]. The PPP EA process will
restart

A failure occured during the initialization of

the process. The process will restart which
should recover the situation.

Failed to allocate %zu bytes for '[chars]'

The process failed to allocate memory for

the specified resource.

Unexpected error whilst [chars]: [chars]

PPP EA encountered an error

communicating with Rewrite Manager. The
error message describes what operation
has failed and why it failed. The most likely
reason for this is a temporary connection
problem with the Rewrite Manager Server
process, but the error could also be caused
by low memory resource or programming
error.

<<CH[hex]>>: Unexpected error whilst

[chars]: [chars]

PPP EA encountered an error

communicating with Rewrite Manager. The
error message describes what operation
has failed and why it failed. The most likely
reason for this is a temporary connection
problem with the Rewrite Manager Server
process, but the error could also be caused
by low memory resource or programming
error.

A batch from IM contained multiple

notifications for a single interface. This
<<CH[hex]>>: Multiple [chars]
should not occur but the situation has been
notifications received in a single batch from recovered successfully by the PPP EA. No
IM
problems should be seen as a result.

[chars]: Socket [chars] failed; [chars]

There is a communication problem with the

PPP socket.

Failure during intialization of [chars]. Error: The PPP GBL CFG process failed to initialize
[chars]
correctly.

<<CH[hex]>>: Cleanup of a subscriber

session has failed: [chars]

A call to AAA to remove subscriber session

state has failed. The error may cause the
LCP session on the subscriber interface to
be left permanently in what should be a
transient unnegotiated state.

[chars] has an interface MTU of [unsigned

int] which is smaller than the PPP packet
header size ([unsigned int]) and so PPP
cannot run on the interface

PPP has been informed that the lower-layer

MTU has been set to a value smaller than
the PPP header size, which makes it
impossible for PPP to operate.

L2 mode is not supported on

<<CH[hex]>>

L2transport has been configured on an

interface that does not support it. The
interface will not enter L2 mode, and will
remain in whichever mode it was in before.
This will occur if the interface capabilities
do not support L2 mode, or if L2 mode is
configured on a multilink bundle member.

AAA authentication list \[chars]\ is not

defined for PPP

One or more PPP interfaces have been

configured to authenticate the peer using
the authentication list identified in the error
message, but this authentication list has
not been configured in AAA itself. As a
result PPP will be unable to authenticate
the peer and the line protocol on the
relevant interface or interfaces will not
come up.

[chars] has a PPP MTU of [unsigned int]

which is smaller than the minimum value
([unsigned int]) required for correct
operation

RFC 1661 requires that the media that PPP

is running over is always able to receive
PPP packets of sizes up to 1500 bytes
(where this value excludes the 4 bytes of
PPP header). This is to ensure that the peer
can always send control protocol packets
up to this size if they ever need to
renegotiate. IOS-XR routers set their MRU
to the same value as the MTU, and this
message has been issued because the
configured MTU is too small to meet the
above condition.

<<CH[hex]>>: Multilink interface

provisioned without IP interworking
configured

PPP MA encountered an error when

receiving a notification from l2vpn_mgr.
Multilink interfaces are only expected to be
provisioned when IP interworking is
configured. The most likely reason for this
is a problem with the l2vpn service and is
likely to be a transient issue.

<<CH[hex]>>: A response with

unexpected properties has been received
from AAA: [chars]

AAA has sent a response which is

unexpected or malformed in the way
explained in the message. The error may
cause the interface to be left in what
should be a transient state permanently.

Unrecognized IfMgr protocol [chars] on

<<CH[hex]>> (caps=[chars])

Interface Manager notified LCP about a

protocol that it doesn't recognize, either by
sending a request to LCP to adopt this node
or by informing LCP that it exists. This is a
programming error as LCP needs to
recognized all of the protocols which run
above it in order to be able to run the
relevant CP.

The PPP MTU is reduced when the PPP MRU

of the peer is less than the PPP MTU
derived from the locally configured
interface MTU. The reduced value will be
used until LCP is renegotated (such as
when the interface goes down and comes
back up, or a new MTU is configured), or if
the PPP encapsulation is removed from the
interface. The MTU then returns to the
configured value and another message will
The PPP MTU for [chars] has been
indicate if a value less than the configured
negotiated to be [unsigned int]. This is less value is negotiated again. The reduced
than the configured PPP MTU of [unsigned MTU is a normal part of PPP operation and
int]
is not indicative of any problems.

The peer has sent a NAK in response to the

local MRRU value. The value it is
suggesting for the MRRU is larger than the
local bundle admin MTU, so it cannot be
accepted. However, suggesting a smaller
<<CH[hex]>>: Unable to complete LCP
value will almost certainly lead to repeated
negotiations. Interface MTU on
NAKs (since the peer should be suggesting
<<CH[hex]>> needs to be reconfigured
its minimum possible MRRU value), so the
taking into account the L2 headers to give LCP session will be closed for a short time
an L3 MTU of at least [unsigned int]
and then negotiations will be retried.

Send async pulse to ppp lite process fails;

Error [chars]

Attempt to send pulse to PPP lite process

fails

Cannot connect to ppp lite process; Error

[chars]

Attempt to connect to PPP lite process

channel fails

Cannot mmap file [chars]; Error [chars]

Attempt to mmap the shared memory fails

Cannot open shmem file [chars]; Error

[chars]

Attempt to open the shared memory fails

Cannot truncate file [chars] to [dec] bytes; Attempt to truncate the shared memory file
Error [chars]
fails

PPP lite SHMEM can accommodate only

[dec] records (request for [dec] records)

PPP MA has requested transfer of more

interface records than shared memory can
accommodate

<<CH[hex]>>: Subscriber IPv4 address

[chars] matches another route

The IPv4 address assigned to this

subscriber interface matches the address
for an existing route in the RIB. ECMP is not
supported for subscriber interfaces, so this
duplicate address causes the subscriber
session to be disconnected. The most likely
reason for this is that another subscriber
session is using the same IPv4 address but it is also possible that a non-subscriber
route is using the same IPv4 address.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error using the

AAA service. The error message describes
what operation has failed and why it failed.
The most likely reason for this is a
temporary problem communicating with
the AAA server, but the error could also be
caused by low memory resource or
programming error.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error using the

AAA attribute service. The error message
describes what operation has failed and
why it failed. The most likely reason for this
is low memory resource or a programming
error.

<<CH[hex]>>: Unexpected error

encountered whilst [chars]: [chars]

PPP MA encountered an error using the

AAA attribute service for the interface
specified. The error message describes
what operation has failed and why it failed.
The most likely reason for this is low
memory resource or a programming error.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error using the

AAA iEDGE service. The error message
describes what operation has failed and
why it failed. The most likely reason for this
is that the AAA iEDGE server is unavailable.
It may also be caused by low memory
resource or a programming error.

<<CH[hex]>>: Unexpected error

encountered whilst [chars]: [chars]

PPP MA encountered an error using the

AAA iEDGE service for the interface
specified. The error message describes
what operation has failed and why it failed.
The most likely reason for this is that the
AAA iEDGE server is unavailable. It may
also be caused by low memory resource or
a programming error.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error

communicating with the AIB server. The
error message describes what operation
has failed and why it failed. The most likely
reason for this is a temporary connection
problem with the AIB server, but the error
could also be caused by low memory
resource or programming error.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error using the

Backend service related to use of either
SysDB or SubDB. The error message
describes what operation has failed and
why it failed. The most likely reason for this
is low memory resources or a programming
error.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error using the Bag

Client library. The error message describes
what operation has failed and why it failed.
The most likely reason for this a low
memory condition but the error could also
be caused by a programming error. The
error will affect PPP MA's ability to provide
operational management data, but won't
otherwise affect PPP MA's operation.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error using the

Checkpoint Service. The error message
describes what operation has failed and
why it failed. The most likely reason for this
a low memory condition but the error could
also be caused by a programming error.

Corrupt [chars] checkpoint record found:

[chars]

Whilst restoring one of its checkpoint

tables PPP MA found a corrupt checkpoint
entry. The entry will be ignored and so the
relevant interface's PPP session will be
renegotiated after the restart and as a
result there may be a short period where
traffic is lost.

Duplicate [chars] checkpoint record found

for [chars]

Whilst restoring one of its checkpoint

tables PPP MA found multiple entries for
the same interface. PPP MA will use the
first checkpoint entry it finds for each
interface and ignore any subsequent
duplicates. This is caused by a
programming error.

Unexpected error encountered whilst

retrieving the value of the [chars] clock:
[chars]

PPP MA encountered an error whilst

retrieving the value of the realtime clock.
The error message includes details of the
reason for the error. This is a fatal error and
the PPP MA process will abort and be
restarted to recover.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error using the

DAPS address pool service. The error
message describes what operation has
failed and why it failed. The most likely
reason for this is a connection problem with
the DAPS service, but the error could also
be caused by low memory resources or
programming error.

<<CH[hex]>>: Unexpected error

encountered whilst [chars]: [chars]

PPP MA encountered an error using the

DAPS address pool service. The error
message describes what operation has
failed and why it failed. The most likely
reason for this is a connection problem with
the DAPS service, but the error could also
be caused by low memory resources or
programming error.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error using the

debug service. The error message
describes what operation has failed and
why it failed. The error could be caused by
low memory resource or programming
error.

Error closing '[chars]' connection: [chars]

PPP MA failed to close a connection to an

essential service. This is an internal error
and it requires a restart of the process for
recovery.

Error creating '[chars]' connection: [chars]

PPP MA failed to create a connection to an

essential service during initialization. This
is an internal error. It requires a restart of
the process for recovery.

After detecting an error with the connection

to the specified service, PPP MA failed to
reset that connection. This is an internal
error. It requires a restart of the process for
Error resetting '[chars]' connection: [chars] recovery.

Error registering for data events on

'[chars]' connection: [chars]

During initialization, PPP MA failed to

register for input or output notifications for
the specified service. This is an internal
error. It requires a restart of the process for
recovery.

PPP MA failed to retrieve the file descriptor

Error retrieving the Connection ID from the associated with the specified service. This
'[chars]' connection: [chars]
is an internal error.

Error registering for critical events on

'[chars]' connection: [chars]

During initialization, PPP MA failed to

register for essential notifications regarding
the state of the connection for the
specified service. This is an internal error. It
requires a restart of the process for
recovery.

Error opening '[chars]' connection: [chars]

PPP MA failed to open a connection to an

essential service during initialization. This
is an internal error. It requires a restart of
the process for recovery.

Failed to register a handler for '[chars]'

messages: [chars]

PPP MA failed to register a handler for the

specified class of event. This is an
initialization error and implies that PPP MA
will not be able to operate correctly. The
PPP MA process will abort and be restarted
in an attempt to recover. The cause may be
a resource starvation problem but is most
likely to be an internal programming error.
The error message should give more
details.

Error creating the PPP MA Event Manager:

[chars]

PPP MA failed to create its Event Manager

which is a critical resource for the
operation of the process. This error may be
caused by low memory resources. The
process will abort and be restarted in an
attempt to recover.

Failed to send '[chars]': [chars]

PPP MA failed to send the specified

message. The cause may be a resource
starvation problem but is most likely to be
an internal programming error. The error
message should give more details.

Error creating event queue for '[chars]':

[chars]

This is an unexpected error. The PPP MA

process will attempt to recover by
restarting. The cause may be a resource
starvation problem. The error message
should provide more details.

This is an unexpected error. The PPP MA

process will attempt to recover by
restarting. The cause may be a resource
starvation problem. The error message
Error dequeuing event for '[chars]': [chars] should provide more details.

Error queuing event for '[chars]': [chars]

This is an unexpected error. The PPP MA

process will attempt to recover by
restarting. The cause may be a resource
starvation problem. The error message
should provide more details.

PPP MA encountered an error

communicating with Interface Manager.
The error message describes what
operation has failed and why it failed. The
most likely reason for this is a temporary
connection problem with the Interface
Manager Control Server, but the error could
Unexpected IfMgr error encountered whilst also be caused by low memory resource or
[chars]: [chars]
programming error.

<<CH[hex]>>: Unexpected IfMgr error

encountered whilst [chars]: [chars]

PPP MA encountered an error on a

particular interface whilst communicating
with Interface Manager. The error message
describes what operation has failed and
why it failed. The most likely reason for this
is a temporary connection problem with the
Interface Manager Control Server, but the
error could also be caused by low memory
resource or programming error.

<<CH[hex]>>: IPCP has negotiated

inconsistent options: [chars]

PPP MA has negotiated inconsistent IPCP

options. The message details which options
are inconsistent. IPCP will be brought up,
but the inconsistencies could cause
problems. The most likely reason for this is
a misconfiguration, either locally or on the
peer.

<<CH[hex]>>: Failed to scan for

configuration, continuing: [chars]

PPP MA encountered an error when

scanning for IPCP configuration. The error
message describes what operation has
failed and why it failed. The most likely
reason for this is a connection problem with
the SubDB service, but the error could also
be caused by low memory resources or
programming error.

<<CH[hex]>>: Failed to scan for

configuration, continuing: [chars]

PPP MA encountered an error when

scanning for IPCPIW configuration. The
error message describes what operation
has failed and why it failed. The most likely
reason for this is a connection problem with
the SysDB service, but the error could also
be caused by low memory resources or
programming error.

PPP MA encountered an error

communicating with IPHC MA. The error
message describes what operation has
failed and why it failed. The most likely
reason for this is a temporary connection
problem with the IPHC MA, but the error
Unexpected IPHC error encountered whilst could also be caused by low memory
[chars]: [chars]
resource or programming error.

<<CH[hex]>>: Invalid IPHC config

received: [chars]

PPP MA received invalid or unsupported

IPHC config for this interface. The error
message describes which piece of config is
invalid. The most likely reason for this is
incorrect IPHC user configuration.

<<CH[hex]>>: IPv6CP has negotiated

inconsistent options: [chars]

PPP MA has negotiated inconsistent IPv6CP

options. The message details which options
are inconsistent. IPv6CP will be brought up,
but the inconsistencies could cause
problems. The most likely reason for this is
a misconfiguration, either locally or on the
peer.

<<CH[hex]>>: Failed to scan for

configuration, continuing: [chars]

PPP MA encountered an error when

scanning for IPv6CP configuration. The
error message describes what operation
has failed and why it failed. The most likely
reason for this is a connection problem with
the SubDB service, but the error could also
be caused by low memory resources or
programming error.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error

communicating with the L2VPN server. The
error message describes what operation
has failed and why it failed. The most likely
reason for this is a temporary connection
problem with the L2VPN server, but the
error could also be caused by low memory
resource or programming error.

Failed to [chars] [chars]: [chars]

IPV6CP encountered an error using the LAS

API. The error message describes what
operation failed. This may be a resource
starvation problem or an internal
programming error.

Unexpected error encountered whilst

[chars] the [chars] buffer: [chars]

PPP MA encountered an error using the

Lightweight Tracing service. The error
message describes what operation has
failed and why it failed. This is a fatal error
and the PPP MA process cannot continue. It
will abort and subsequently be restarted by
SysMgr in an attempt to recover.

Failed to allocate %zu bytes for '[chars]'

The process failed to allocate memory for

the specified resource.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an unexpected error

using the Managed Timer library. This is
most likely to be due to a low memory
condition but may also be an internal
programming error. The error message
should provide more information about the
cause.

PPP MA encountered an error when

resyncing with IM and discovered an NCP
caps where PPP is no longer expected to be
running. The most likely reason for this is a
connection problem with the IM service and
is likely to be a transient issue, but the
<<CH[hex]>>: Stale [chars] caps may still error could also be caused by low memory
be present on interface
resources or programming error.

The connection to packet manager was

errored and the attempt to recover failed.
Error handling pakman corruption problem: Restarting the process should resolve the
[chars]. Process exiting.
problem.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error

communicating with the Platform
Properties DLL. The error message
describes what operation has failed and
why it failed. This will either have occurred
because the Platform DLL failed to be
properly initialized, or because of some
error occurring in the platform dependent
code.

Unexpected error encountered whilst

[chars]

PPP MA encountered an error using the RIB

client library. The error message describes
what operation has failed and why it failed.
The most likely reason for this is a
connection problem with the RIB, but the
error could also be caused by low memory
resources or programming error.

<<CH[hex]>>: Incompatible SSRP

replicated state received: [chars]

PPP MA received replicated SSRP state for

this interface for either which is
incompatible with the local config, as
identified in the error message. This means
the replicated state will not be used to
preprogram the session.

PPP MA encountered an error

communicating with SSRP. The error
message describes what operation has
failed and why it failed. The most likely
reason for this is a temporary connection
problem with the SSRP, but the error could
Unexpected SSRP error encountered whilst also be caused by low memory resource or
[chars]: [chars]
programming error.

Unexpected SubDB error encountered

whilst [chars]: [chars]

PPP MA encountered an error using the

SubDB service. The error message
describes what operation has failed and
why it failed. The most likely reason for this
is a connection problem with the SubDB
server, but the error could also be caused
by low memory resources or programming
error.

<<CH[hex]>>: Unexpected error

encountered whilst [chars]: [chars]

PPP MA encountered an error using the

SubDB service. The error message
describes what operation has failed and
why it failed. The most likely reason for this
is a connection problem with the SubDB
server, but the error could also be caused
by low memory resources or programming
error.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error using the

SysDB service. The error message
describes what operation has failed and
why it failed. The most likely reason for this
is a connection problem with the SysDB
server, but the error could also be caused
by low memory resources or programming
error.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error whilst

communicating with SysMgr. The error
message describes what operation has
failed and why it failed. This is a fatal error
and the PPP MA process will abort and be
restarted to recover.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error whilst

communicating with SysMgr. The error
message describes what operation has
failed and why it failed. Sysmgr will take
action to recover if appropriate. It is
possible that this error has occured after
MDR. If so then the recovery may require a
cold reload of the card

PPP MA encountered an unexpected error

performing a pthread operation. The
process will restart to attempt to recover.
This is possibly due to a low memory
condition but may also be an internal
programming error. The error message
Unexpected pthread error encountered for should provide more information about the
'[chars]' thread whilst [chars]: [chars]
cause.

Unexpected condition error encountered

whilst [chars]: [chars]

PPP MA encountered an unexpected error

performing a condition operation. The
process may restart to attempt to recover.
This is possibly due to a low memory
condition but may also be an internal
programming error. The error message
should provide more information about the
cause.

Failed to create '[chars]' thread: [chars]

PPP MA encountered an unexpected error

creating a new thread. The process will
restart to attempt to recover. This is
possibly due to a low memory condition but
may also be an internal programming error.
The error message should provide more
information about the cause.

Unexpected mutex error encountered

whilst [chars]: [chars]

PPP MA encountered an unexpected error

performing a mutex operation. The process
may restart to attempt to recover. This is
possibly due to a low memory condition but
may also be an internal programming error.
The error message should provide more
information about the cause.

[chars] received packet with unsupported

protocol [hex]

PPP MA received a packet with a protocol

id, and was not recognised by the receiving
control protocol. This error message
indicates that a subsystem is incorrectly
delivering packets to an inappropriate PPP
control protocol, the packets are dropped.

Error initializing the WAVL tree used to

store PPP MA IDBs: [chars].

PPP MA encountered an unexpected error

which prevents it from functioning. This
error may be caused by low memory
resources. The process will abort and be
restarted in an attempt to recover.

Error destroying '[chars]' connection:

[chars]

During process termination PPP MA failed

to destroy a connection to a service
provided by another process. This is an
internal error.

Error blocking waiting for an event to

process: [chars]

This is an unexpected error. The PPP MA

process may recover by itself, or it may
need to be restarted to recover.

Error destroying event queue for '[chars]':

[chars]

During process termination PPP MA failed

to destroy an event queue. The process will
terminate regardless so there should be no
lasting problems.

Failure initializing the PPP NetIO datapath

for <<CH[hex]>>: [chars]%s

The PPP NetIO DLL failed to initialize the

datapath for processing PPP packets on a
particular interface because of an
unexpected error. The message includes
the exact cause of the failure. As a result,
the capsulation will be unloaded from the
interface and the interface will not be able
to send or receive any PPP packets. One
possible reason for the error is a low
memory condition, particularly if the failure
was in creating the interface descriptor.

A failure occurred during an initialization

operation in the PPP NetIO DLL. If this
occured during an upgrade operation then
it will cause the NetIO process to reload.
Otherwise this will cause the capsulation to
be unloaded, and an error returned to the
user. One possible reason for the error is a
low memory condition, particularly if the
Failure [chars] in the PPP NetIO DLL: [chars] failure was in allocating trace buffers.

Dropping [chars] packet on [chars]

([chars])

The PPP NetIO DLL has been forced to drop

a packet because of an unexpected error.
The error message describes the reason for
the drop.

When the PPP NetIO DLL was upgraded the

Incompatible subblock version during
existing data version was incompatible
upgrade. Data has version [unsigned int], with the new software. NetIO will be
but the version supported is [unsigned int] restarted to recover the appropriate state.

Unable to allocate [unsigned int] bytes

Not enough memory was available for the

operation to complete.

The process was initialized successfully but

Failure communicating readiness to System was unable to inform System Manager of
Manager. Error: [chars]
the success.

Error in event loop: [chars]

An error occured in the event loop. The

process will restart which should recover
the situation.

Failed to initialize the ltrace buffer. Error:

[chars]

The buffer used for tracing could not be

allocated. The process will be restarted.

Could not clean up and restart pakman

An unknown error occurred after a pakman
connection. Error: [chars]. Control packet
disconnect event. Restarting the socket
I/O will fail so restarting the socket process. process should have resolved the problem.

A failure occurred during the initialization

Failure during intialization of [chars]. Error: of the process. This resulted in the restart
[chars]
of the process.

Failed to allocate hardware resources for

feature [chars] on ifh [hex], subtype [dec],
stage [chars], instance [chars], loc [dec],
error: [dec] ([chars])

A runtime error occurred while trying to

allocate hardware resources for configuring
a feature. The reason for the failure is also
displayed.

[chars]:[dec] event_conn_create failed

[dec]

Failed to create the event connection.

[chars]:[dec] event_conn_destroy failed

[dec]

Failed to open the event connection.

[chars]:[dec] sysdb_bind failed [dec]

Failed to bind the sysdb file.

[chars]:[dec] sysdb_conn_to_coid failed

[dec]

SYSDB connection to coid failed.

[chars]:[dec] sysdb_register_verification
failed [dec]

SYSDB register verification failed.

IPv6 compression anchor prefixes are

changed. A linecard reload is needed to
make this change effective

The IPv6 compression anchor prefixes are

changed. The linecard needs to be
reloaded to make the changes effective.
This is not an error message or condition.

[chars] failed due to [chars]

Initialization of uidb_svr process has failed

due to one of the following reasons: 1)
Failed to create server context. 2) Failed to
get schedular parameters. 3) Failed to
initialize event manager. This would
prevent process from receiving events. 4)
Failed to register with debug. This would
prevent process from logging debug
messages. 5) Failed to bind UIDB server
with MIPC server. This is needed to
program features in hardware. 6) Failed to
connect to PLIM asic processes. This is
needed to program features in hardware.
7) Failed to initialize checkpoint. This is
needed to checkpoint UIDB data to restore
on process restart. 8) Failed to allocate,
initialize and checkpoint shadow memory.
This is needed to store and restore UIDB
internal data. 9) Failed to get metro asic
version. 10) Failed to attach event handlers
needed to handle LWM messages. This is
needed to enable/disable various features
in hardware. 11) Various Sysdb or EDM
failures 12) event_block failed. This
indicates process has encountered
unexpected error while waiting for events.

Exit on error: [chars]: Caused by [chars]

An critical error occurred in PSE Driver

which requires exiting (and, hence,
restarting) the process.

Exit on error: [chars]: Caused by [chars]

An critical error occurred in PSE Driver

which requires exiting (and, hence,
restarting) the process.

[chars] direction. Data: ([chars])

Inter-processor communcation to the Metro

is stuck.

[chars] device: Caused by [chars]

The PSE driver was unable to perform a

critical function and must trigger a node
bringdown to effect recovery.

[chars] device: Caused by [chars]

The PSE driver was unable to perform a

critical function and must trigger a node
bringdown to effect recovery.

Instance [dec]: [chars] [chars] [hex]

This is a error message in the PSE Driver to

indicate DMA operation failed

Exit on error: [chars]: Caused by [chars]

An error occurred in PSE Driver which

requires exiting (and, hence, restarting) the
process.

Exit on error: [chars]: Caused by [chars]

An error occurred in PSE Driver which

requires exiting (and, hence, restarting) the
process.

[chars]

This is a debug message in the PSE Driver

to indicate an operation or condition.

[chars]

PSE driver health monitor detected error

conditions

[chars]

PSE driver health monitor detected error

conditions

Instance [dec]: [chars]

This is a debug message in the PSE Driver

to indicate an operation or condition.

Error: [chars]: Err=[dec]

A driver internal error occurred which

involves exiting the process. %s - indicates
the reason for the failure. %d - is the error
condition.

Error: [chars]: count=[dec]

This is a error message in the PSE Driver to

indicate either anomolies which are
notservice impacting. Some of the
messages may indicate a failure to allocate
resources needed by applications. In many
cases these messages must not keep
appearing after the temperory situation is
resolved. %s - indicates the reason for the
failure. %d - is the count.

MP Core File saved in [chars].

An error occurred in PSE MP Microcode

Driver which required exiting (and, hence,
restarting) the process. This message
records the location of the MP Core File.

\n[[chars]]:Message reply failed with error

[dec]

The message reply failed.

[chars] device: Caused by [chars]

This is an error message in the PSE Driver

to indicate that it failed to perform cold
reset of specified pse instance due to the
specified reason.

[chars] device: Caused by [chars]

This is an error message in the PSE Driver

to indicate that it failed to perform cold
reset of specified pse instance due to the
specified reason.

[chars] device: High rate of ASIC errors of

type: [chars]

This is an error message in the PSE Driver

to indicate that a high rate of specified
errors is being detected.

[chars] device: High rate of ASIC errors of

type: [chars]

This is an error message in the PSE Driver

to indicate that a high rate of specified
errors is being detected.

[chars] device: High rate of ASIC errors of

type: [chars]

This is an error message in the PSE Driver

to indicate that a high rate of specified
errors is being detected.

[chars] device: High rate of ASIC errors of

type: [chars]

This is an error message in the PSE Driver

to indicate that a high rate of specified
errors is being detected.

[chars] device: Caused by [chars]

This is an error message in the PSE Driver

to indicate that it failed to perform iMDR
reset of specified pse instance due to the
specified reason.

[chars] PSE ASIC prototype hardware

detected. This version ([unsigned int]) is
not supported.

This message indicates that the version of

the PSE ASIC is a prototype, and it is not
supported by the s/w release.

[chars] PSE ASIC prototype hardware

detected. This version ([unsigned int]) will
be unsupported in future releases.

This message indicates that the version of

the PSE ASIC is a prototype, and will be
unsupported in future s/w releases.

[chars] device: Caused by [chars]

This is an error message in the PSE Driver

to indicate that it failed to perform warm
reset of specified pse instance due to the
specified reason.

[chars] device: Caused by [chars]

This is an error message in the PSE Driver

to indicate that it failed to perform warm
reset of specified pse instance due to the
specified reason.

Continuing execution: [chars]: Caused by

[chars]

This message indicates an error occurred

beyond which execution of the pse_driver
may continue, attempting to effect
recovery or work-around internally,
minimizing loss of information/functionality.

Continuing execution: [chars]: Caused by

[chars]

This message indicates an error occurred

beyond which execution of the pse_driver
may continue, attempting to effect
recovery or work-around internally,
minimizing loss of information/functionality.

This message indicates completion of the

automatic correction following the
detection of a mismatch between the LC
CPU software view of TCAM content, and
what was actually found in hardware. The
system attempts to collect troubleshooting
information concerning the mismatch;
however, should there be insufficient line
card memory to do so, this information is
not collected. The text of the message
indicates whether information was
[chars]: troubleshooting data [chars]saved: collected, along with the location of the file
[chars]
containing the information.

[chars] TCAM[dec]: mismatch detected,

recovery initiated

This message indicates the detection of an

inconsistency between the LC CPU software
view of TCAM content, and what is actually
found in hardware. Recovery is initiated
automatically upon detection of such a
mismatch. Once recovery completes,
troubleshooting information is collected.
Further messages, namely
'TCAM_MISMATCH_REPAIRED' and then
'TCAM_MISMATCH_COMPLETED', follow
when the recovery and the data collection
are completed, respectively.

[chars] TCAM[dec]: mismatch corrected,

collecting troubleshooting information

This message indicates the completion of

the automatic correction following the
detection of a mismatch between the LC
CPU software view of TCAM content, and
what was actually found in hardware. It
also marks the start of troubleshooting
data collection, the end of which will be
indicated by a further
'TCAM_MISMATCH_COMPLETED' log
message.

[chars]

This is a informational message in the PSE

Driver to indicate an operation.

[chars]

This is a informational message in the PSE

Driver to indicate an operation.

Info: [chars]

This is a Informational message in the PSE

Driver to indicate an operation. %s indicates the informational message.

[chars] [chars]

This is an informational message in the PSE

Driver to indicate an event on maintenance
processor.

[chars]

This is a debug message in the PSE Driver

to indicate an operation or condition.

[chars]

This is a debug message in the PSE Driver

to indicate an operation or condition.

MP Core File saved in [chars].

An error occurred in PSE MP Microcode

Driver which required exiting (and, hence,
restarting) the process. This message
records the location of the MP Core File.

[chars]. Reason: [chars]

An error occurred in the PSE ASIC client

library after which the client code cannot
continue. This error is encountered when a
client module (e.g. cli command) has
difficulty retrieving information from the
PSE driver. The root cause may be located
in either hardware or software.

Communications retry failed: [chars]%s

A PTP process has failed to send a message

and attempts to retry the send have also
failed.

Failed to initialize: [chars]%s

An error was encountered while the

specified process was initializing. The error
message contains details about the source
of the error.

Failed to [chars] [chars]: [chars]

PTP encountered an error using the IP-ARM

API. The error message describes what
operation failed. This may be a resource
starvation problem or an internal
programming error.

[chars] lost event: [chars]

The specified process failed to receive an

event that was sent to it.

Failed to allocate [unsigned int] bytes for

'[chars]'

The process failed to allocate memory for

the specified resource.

Unexpected error encountered whilst

[chars]: [chars]

PTP encountered an unexpected error using

the Managed Timer library. This is most
likely to be due to a low memory condition
but may also be an internal programming
error. The error message should provide
more information about the cause.

PTP MIB DLL error: [chars]%s

An error was encountered in the PTP MIB

DLL. Some functionality of the PTP DLL may
be impaired. The error message contains
details about the source of the error.

Failed to allocate PTP peer index

PTP was unable to allocate a peer index to

a PTP peer, as all available peer indices are
currently allocated. PTP MIB data may be
unreliable.

PTP was unable to read port number

Port number checkpoint read failed: [chars] information from checkpoint.

Port number [unsigned int] allocation

conflict between <<CH[hex]>> and
<<CH[hex]>>

A PTP port number has been allocated to

more than one interface.

Failed to allocate PTP port number

PTP was unable to allocate a port number

to an interface, as all available port
numbers are currently allocated.

Profile [chars] config ignored as it is not

supported on interface [chars]

PTP has not applied an item of profile

config on this interface because the
interface does not support it.

Could not determine whether to exit:

[chars]

A Precision Time Protocol process could not

determine whether all Precision Time
Protocol configuration has been removed
and so cannot exit safetly. Precision Time
Protocol processes may be running despite
no Precision Time Protocol configuration
existing.

Unexpected error encountered whilst

[chars]: [chars]

PTP MA encountered an error interacting

with SPIO. The error message describes
what operation has failed and why it failed.
The error could also be caused by low
memory resources or programming error.

Unexpected error encountered whilst

[chars]: [chars]

An error was encountered with the PTP

statistics database, packet counters may
be invalid.

Unexpected error encountered whilst

[chars]: [chars]

PTP MA encountered an error using the

timer wheel library. The error message
describes what operation has failed and
why it failed. The error could also be
caused by low memory resources or
programming error.

Failed to generate VLAN tag stack for

[chars]

PTP was unable to generate a VLAN tag

stack for an interface. This is most likely to
be due to configuring PTP on an interface
with a complex VLAN encapsulation, which
is not supported.

Best master clock change, new master

[chars], clock ID [hex]

The best master clock available to PTP has

changed.

A best master clock is no longer available

There is no longer a best master clock

available to PTP.

Failed to recover after an interface error:

[chars]

If an error occurs while retriving subinterface information from the system,

PVSTAG attempts to recover automatically.
This message is seen if that attempt to
recover fails, or if more than the maximum
number of attempts have been made. After
this error is seen, it is likely that PVSTAG
will not operate correctly for some VLANs.

Restarting after failing to process one or

more expired timers: [chars]

An error has occurred processing one or

more timer events driving the PVRST
engine. The process has restarted to
correct this issue.

Failed to apply a batch of [unsigned int]

configuation changes: [chars]

A failure occured when applying a batch of

configuration changes. PVSTAG may not
operate correctly following this error.

Failed to apply [chars] of configuation of

[chars] for [chars] instance [chars],
interface [chars], VLAN [unsigned int]:
[chars]

A failure occured when applying a

configuration change. PVSTAG may not
operate correctly for the instance described
in the message.

Checkpoint data inconsistent: [chars]

A failure occurred while processing

checkpointed information.

Failed to checkpoint [chars] data: [chars]

A failure occurred saving checkpointed

information, most likely due to a memory
allocation failure.

Error while disabling port <<CH[hex]>>.

Reason for disabling is '[chars]': [chars].

The PVSTAG-IO process failed an attempt to

error-disable a port (in response to, for
example, a BPDU being received on a port
with BPDU-guard configured).

Initialization failure: failed to [chars]%s

A failure occurred during the initialization

of the process. This resulted in the restart
of the process.

A packet that was unexpected or

malformed was received. Most commonly
this is the result of a misconfiguration,
Unexpected or malformed packet received causing for example, PVRST packets to be
on interface <<CH[hex]>>, VLAN
received on a port that is configured with
[unsigned int]: [chars]
PVST-AG.

A failure occurred while trying to start the

pre-empt delay timer for the sub-interface
specified in the message. As a result, any
PVSTAG or PVRSTAG VLAN instances for
VLANs matched by that sub-interface will
use the normal values, and not the startup
values, when sending BPDUs. This may
cause peer devices to forward traffic on
those VLANs to this device, before this
Failed to start the pre-empt delay timer for device is ready to accept it. As a result,
<<CH[hex]>>: startup values will not be traffic may be dropped for a short period of
used
time.

A failure occured when notifying the

System Manager that the pvstag-io process
was about to exit. In rare cases, this could
Failed to notify the System Manager about result in the System Manager failing to
process exit: [chars]
restart the process when it ought to do so.

Failed to register to receive PVST BPDUs:

[chars]

A failure has repeatedly occurred when

attempting to register to receive PVST+ or
PVRST BPDUs, and either the retry timer
could not be allocated or the maximum
number of retries has been reached. No
BPDUs will be received on the affected subinterfaces, and hence the MAC table will
not be flushed when a topology change
occurs. This could result in traffic being
forwarded incorrectly or dropped for a
period of time, until the MAC entries time
out or are relearned.

Failed to send BPDUs after [unsigned int]

attempts

A failure has repeatedly occurred when

attempting to send PVST+ or PVRST
BPDUs. This could result in incorrect
protocol behaviour, or in the worst case,
forwarding loops. The failure is most likely
caused by a lack of available memory or
packet buffers on the affected line card.

Failed to synchronize the PVSTAG-IO

process on the standby - restarting. Error:
[chars]

The PVSTAG-IO process on the standby

card was unable to synchronize its state
with the active card. The standby process
will restart in order to force a resync. As
this only affects the standby card, there is
no impact on traffic flow or on regular
PVSTAG operation.

Failed to process subinterface information

for <<CH[hex]>>: [chars]

There was a failure when processing

information about the sub-interface
specified in the message. It is likely that
PVSTAG will not operate correctly on the
port for the VLANs matched by that subinterface.

A BPDU was received on portfast port:

<<CH[hex]>>

A BPDU was received on a port that was

configured for Portfast. This port will now
revert to a 'non-edge' port.

ALARM [chars]: The maximum number of

PVSTAG VLAN instances per line card
([unsigned int]) [chars].

The supported number of PVSTAG VLAN

instances on this line card has been
exceeded, or has been brought back under
the limit. When the limit has been
exceeded, PVSTAG may not operate
correctly or there may be an adverse
performance or scalability impact on the
rest of the system.

CPP [dec] HW [chars]:[chars] schedule

resources recover from depletion - [dec]%
available

CPP BQS HW schedule resources have

recovered from critical threshold.

CPP [dec] HW [chars]:[chars] schedule

resources depleted - [dec]% available

CPP BQS HW schedule resources have

dropped below critical threshold.

[chars]([dec]) Interrupt : [chars] Seq:[dec]

Halt bit set.

A Serious CPP hardware error has occurred.

[chars]([dec]) Interrupt: [chars]

A CPP hardware interrupt has occurred.

[chars]([dec]) CPP Driver LOCKDOWN due

to fatal error.

A fatal error has caused the CPP driver to

LOCKDOWN.

([hex]) Failed to acquire memory lock [chars].

CPP driver failed to acquire shared memory

lock.

CPP[dec]: Failed to allocate data: ([chars]). A CPP driver failed to allocate data.

CPP[dec]: ([hex]) - Failed to attach [chars]. CPP device Failed to attach.

Failed to cleanup data: ([chars]).

A CPP driver failed to cleanup data.

CPP[dec]: ([hex]) - Failed to create [chars] [chars].

CPP driver failed to to create device.

Failed to destroy connection: ([chars]).

A CPP driver failed to destroy a connection.

CPP[dec]: ([hex]) - Failed to get device

details - [chars].

CPP driver failed to get device details.

[chars]([dec]) Interrupt : [chars] Seq:[dec]

repeating interrupt has been disabled.

A repeating hardware interrupt has been

disabled by CPP driver.

CPP[dec]: ([hex]) - Failed to initialize

[chars] - [chars].

CPP driver failed to initialize a device.

INIT failure: [chars]: Failure Code=[dec]

A init failure occurred in CPP Driver which

involves exiting the process.

Failed to initialize: ([chars]).

A CPP driver failed to initialize.

CPP[dec]: Failed to initialize: ([chars]).

A CPP driver failed to notify INIT failure.

CPP[dec]: ([hex]) Failed: internal SW error[chars].

CPP driver failed with internal software

error.

CPP[dec]: ([hex]) Failed to clear memory [chars].

CPP driver failed to clear memory.

CPP[dec]: ([hex]) Failed to acquire memory CPP driver failed to acquire the size of a
size - [chars].
block of memory.

CPP[dec]: ([hex]) Failed to write to memory

[chars].
CPP driver failed to write to memory.

CPP[dec]: ([hex]) - Platform failure

accessing [chars].

CPP driver failed to query platform data

base.

([hex]) Failed to release memory lock [chars]

CPP driver failed to release shared memory

lock.

[chars]([dec]) TCAM Parity error TCAM

device #[dec] at offset [hex].

A Parity error has occurred in a TCAM

device.

Failed to correct a TCAM Parity error and

[chars]([dec]) Failed to correct TCAM Parity further detection has been disabled by CPP
error. Parity error detection disabled.
driver.

CPP[dec]: ([hex]) Unsupported CPP type:

CPP TYPE:[dec]

Unsupported CPP TYPE.

Warning: [chars]: ErrCode=[dec]

A non-fatal condition occurred in the CPP

driver that may affect the functionality of
CPP.

Address space limit [unsigned int] KB

reached, mapping block [chars] size
[unsigned int] dynamically, over limit
space: [unsigned int] KB

The process indicated tried to map more of

the Forwarding Engine's address space
than was allocated for it. A slower access
method will be used instead. This will lower
the performance of some operations which
require accesses to the Forwarding Engine

Access CPP [dec] address [hex] (Blk/Off:

[dec]/[hex]) [chars] [dec] bytes [hex]_[hex]
flags [hex]
A CPP access was traced

Access CPP [dec] address [hex] (Blk/Off:

[dec]/[hex]) [chars] [dec] bytes [hex] flags
[hex]
A CPP access was traced

Reason of failure [chars]: [chars]

Exiting the process because of failure in

CPP external memory manager.

[chars]

This is a debug message

IPv6 compression anchor prefixes are

changed. A linecard reload is needed to
make this change effective

The IPv6 compression anchor prefixes are

changed. The linecard needs to be reload
to make the changes effective. This is not
an error message or condition.

User is trying to use a classification

criterion not supported by the feature. For
example, user is trying to apply a with a
class matching matched on an IPv6 ACL
Matching on field type [unsigned int]
that contains a match on flow-label. The
([chars] value [unsigned int] ([hex])) not
entire rule (e.g. ACE) containing the
supported for client [chars] ([unsigned
unsupported criterion is ignored. In our
int]), rule oid: [chars], seqnos: [unsigned
example, only the ACEs containing match
long long int], [unsigned long long int],
on flow label are ignored. All other ACEs
[unsigned long long int]: RULE *IGNORED* are still downloaded to CPP.

Reason of failure: [chars]: ErrCode=[dec]

Failure occurred in the CPP IFM Library.

Warning: [chars]: ErrCode=[dec]

A failure occured in the CPP IFM Library

that may affect the functionality of CPP.

Failed to initialize [chars], because of

[chars]

Initialization process such as getting an

evm failed. sysmgr will retry to start the
cpp_lpts_ea. In case its persistent, contact
TAC. *RECUR* *REDUCE*

Reason of Failure [chars]: Err=[hex]

The process is exiting, due to Failure in CPP

Infra Metadata Mgr.

[chars]

This is a debug message

Failed to initialize [chars], because of

[chars]

Initialization of cpp_pfilter_ea process has

failed due to one of the following reasons:
1) Failed to initialize event manager. This
would prevent process from receiving
events. 2) Failed to register with debug.
This would prevent process from logging
debug messages. 3) Failed to initialize
connection with pal_pfilter_ea service. 4)
Failed to initialize connection with
cpp_sp_svr (Feature Manager Service). 5)
Failed to initialize connection with UIDB
Manager Service.

Reason of failure [chars]: Err=[hex]

The process is exiting due to a failure in

CPP Infra Stats Block Service.

Init failure at [chars]:[dec], sub-error:

[chars], error-code: [dec]

An error occurred in CPP TCAM RM which

involves exiting the process.

CPP [dec] TCAM resources in the system is The TCAM device has limited number of
limited.
free cells left to allocate.
CPP [dec] TCAM resource is sufficient.

The TCAM device has sufficient number of

free cells left.

Reason of failure: [chars]: [chars]

The process exiting because of failure in

uidb manager.

[chars]

This is a debug message

Cannot configure xconnect port-forwarding

on [chars] if there are subinterfaces
present with VLAN encaps. Remove all
A main interface cannot be configured for
subinterface configurations before
xconnect port-forwarding if subinterfaces
configuring xconnect port-forwarding.
with VLAN encaps are present.

Dumping head: [chars]

To print packet dump.

[chars] : Card will be reset

There is buffer depletion of FreeQs.

Dumping tail: [chars]

To print packet dump.

QM Buffer Depletion: [chars]

There is buffer depletion of FreeQs.

[chars]: [chars] : reg value [hex]

The queueing asic experienced an

interrupt, and will be reset. After reset,
normal operation should resume.

[chars]: [chars] : reg1 [hex]: reg2 [hex]

The queueing asic experienced an

interrupt, and will be reset. After reset,
normal operation should resume.

This is an informational message for single

bit error in ECC. ECC is 'Error Correction
Code' mechanism in hardware itself to auto
correct the detected error bit. This err gets
EGRESSQ: FCRAM sbe detected - error_reg: recovered on its own and no action is
[hex] error_info: [hex]
required.
The queueing asic experienced an
interrupt, and is non-fatal. In some cases
[chars]: [chars]: error_reg: [hex] error_info: its corrected by software and remaining
[hex]
cases its occurences logged.

[chars]: [chars]: error_reg: [hex]

The queueing asic experienced an

interrupt, and is non-fatal. In some cases
its corrected by software and remaining
cases its occurences logged.

[chars]: [chars]: error: [hex] error_reg:

[hex]

The queueing asic experienced an

interrupt, and is non-fatal. In some cases
its corrected by software and remaining
cases its occurences logged.

[chars]: [chars]: error: [hex] error_reg:

[hex] error_info: 0x[unsigned int]llx

The queueing asic experienced an

interrupt, and is non-fatal. In some cases
its corrected by software and remaining
cases its occurences logged.

[chars] : Card will be reset

There is buffer depletion of FreeQs.

QM Buffer Depletion: [chars]

There is buffer depletion of FreeQs.

[chars]: [chars] : reg value [hex]

The queueing asic experienced an

interrupt, and will be reset. After reset,
normal operation should resume.

[chars]: Err=[dec]

A fatal error occurred in QUEUEING ASIC

Driver which involves exiting the process.
The process will be respawned, but if it
continues to fail the linecard will be reset,
as the linecard cannot operate without this
process.

In order to activate this new interface

profile, Please manually reboot all line
cards or router

The user configuration has caused an

inconsistency in the interface hardware
profile.

In order to activate this new interface

profile, Please manually reboot the line
cards at location [chars].

The user configuration has caused an

inconsistency in the interface hardware
profile.

[chars]. Reason: [chars]

An error occurred in the PSE ASIC client

library after which the client code cannot
continue. This error is encountered when a
client module (e.g. cli command) has
difficulty retrieving information from the
PSE driver. The root cause may be located
in either hardware or software.

[chars]. Reason: [chars]

An error occurred in the PSE ASIC client

library after which the client code cannot
continue. This error is encountered when a
client module (e.g. cli command) has
difficulty retrieving information from the
PSE driver. The root cause may be located
in either hardware or software.

Failed to set MTU of [unsigned int] on

[chars]

The specified MTU could not be applied on

this interface.

Detected NULL hw func ptr in Serial

interface instance: [chars]

Failed to program the hardware.

[chars]: [chars] [chars]

The specified Serial Alarm has been

declared or released.

Send async pulse to slarp lite process fails; Attempt to send pulse to SLARP lite process
Error [chars]
fails

Cannot connect to slarp lite process; Error

[chars]

Attempt to connect to slarp lite process

channel fails

Cannot mmap file [chars]; Error [chars]

Attempt to mmap the shared memory fails

Cannot open shmem file [chars]; Error

[chars]

Attempt to open the shared memory fails

Cannot truncate file [chars] to [dec] bytes; Attempt to truncate the shared memory file
Error [chars]
fails

SLARP lite SHMEM can accommodate only

[dec] records (request for [dec] records)

cHDLC MA has requested transfer of more

interface records than shared memory can
accommodate

[chars]

A SW exception occurred in SLOGIC Library

[chars] - [chars]

A non-fatal error occured while executing

the function in question. The message
contains info about the cause of the failure
and possibly anticipated actions/effects.

Connection to [chars]%s [chars]

State change in the APS group internal

communication system detected. Expected
during transitory conditions at config
changes, OIR, etc. The message contains
info about the WP communication
components affected.

[chars] ([chars]) - [chars]

A conflict failure occured The message

contains info about the cause of the failure
and possibly anticipated actions/effects.

[chars] [chars] [dec] [chars] [dec] [chars]

Debug messages for APS.

Group [dec]: Tx K1K2 [hex] [hex] , Rx K1K2 syslog msg to print K1k2 when switchover
[hex] [hex]
happens
APS group [dec] [chars] [dec]: preempted

The user external request is preempted.

Group [dec] Channel [dec] [chars] switch of

[chars] to [chars] [chars]
Debug messages for APS.
[chars] [chars] [dec] [chars] [dec] [chars]

Debug messages for APS.

[chars] failed ([chars]) - [chars]

A general failure occured while executing

the function in question. The message
contains info about the cause of the failure
and possibly anticipated actions/effects.

Not enough memory for [chars]

The process is out of memory.

[chars]([dec]): [chars] failed ([chars]) [chars]

A general failure occured while executing

the function in question. The message
contains info about the location and cause
of the failure and possibly anticipated
actions/effects.

[chars]: [chars] [chars]

The specified SONET Alarm has been

declared or released.

[chars] [chars]

L-AIS insertion/removal notification

messages.

Clear counters on [chars]

Counters on a sonet controller has been

cleared by the user. This message is for
information only.

A SPA identified by nodeid %s above is not

Inserted node [chars] is not supported by supported by Cisco 12000 Series SPA
Cisco 12000 Series SPA Interface Processor- Interface Processor-601 line card. The SPA
601 line card. Please remove to prevent
should be remove immediately to prevent
damages to the hardwares.
damages to the hardwares.
A SPA identified by nodeid %s above is not
Inserted node [chars] is not supported by supported by Cisco 12000 Series SPA
Cisco 12000 Series SPA Interface Processor- Interface Processor-600 line card. The SPA
600 line card. Please remove to prevent
should be remove immediately to prevent
damages to the hardwares.
damages to the hardwares.

[chars]

SPA 192 Jacket error

[chars]

SPA 192 Jacket V2 error

[chars]

SPA 192 Jacket V2 SPA rule internal error

Failed to read card operation mode,

retrying...\n

failed to read the card operation mode

from mbus eeprom.

Failed to get chassis model, retrying...\n

failed to get chassis model of the card

Failed to read card type, retrying...\n

Failure to read the LC type while checking if

it is sashimi or not.

Failed to perform SPArule Init. Exitting \n

failed to initialize the spa rule module.

Failed to initialize spa_cfg_check lock.

Exit...\n

failed to initialize rw_lock for spa_cfg_check

Jacket process create g_spa process for bay jacket process create g-spa process for a
= [dec]
specific bay number

[chars] : calling
qosrm_spa_alloc_reserved_resources\n

This function is called to inform the QoS RM

of the creation of SPA tx reserved resources
if the spa is a channelized spa.

[chars]
[chars]
[chars]

SPA 192 Jacket V2 SPA rule error

Upgrade SPA FPGA message
Upgrade SPA FPGA message

[chars] [chars]

ATM SPA OC3/OC12 driver error messages

[chars]

SPA process failed due to internal software

error.

[chars] [chars]

ATM SPA OC3/OC12 driver error messages

[chars]

SPA process encountered an error during

software initialization. ltrace initialization is
failed. so we will not get any traces using
ltrace cli. It may fail very rarely. It will work
most of the time. we added this message
only for debugging purpose.

[chars]

SPA process encountered an internal

software error. SPA is in not ready state .
Shared memory is initialized with in
inconsistent state.

[chars] [chars]

ATM SPA OC3/OC12 driver warning

messages

[chars] [chars]

ATM SPA OC3/OC12 informational message

[chars] [chars]

ATM SPA OC3/OC12 debug message

[chars]: Non Fatal errors reported by SAR

The count of non fatal errors thrown by SAR
exceeded max value [dec]. SPA will reset\n register has reached a threshold value.

[chars]: SAR stopped responding to host

commands

SAR device is not in ready state.

[chars]: A fatal error was reported by

[chars]:\n [chars] [Error code [dec]].

A Fatal error has been reported to the SAR

device in scenarios such as 1.Firmware
version mismatch 2.SDRAM not ready 3.L3
Qos cant be applied to this spa. 4.Incorrect
channel ID in cmd ack

SPA in subslot [dec]/[dec]/[dec] FAILED to

come up due to incompatible fpd version.
Please upgrade the fpd.

SPA failed to come up due to incompatible

fpd version.

[chars]: TCAM entries corrupted and

corrected exceeded max value [dec]. SPA
will reset\n

TCAM entries are corrupted with non fatal

errors reported by SAR.

ltrace_init(events) failed: [chars]

Ltrace failed to record the events.

[chars]:ERROR message from SAR contain

invalid info\n

The error reported by SAR contains invalid

info

[chars]([dec]):ERROR shared mem

inconsistency. Force recovery\n

Spa is not in ready state

[chars]: zero voltage detected - loop

count=[dec]\n

The voltage reads zero for the spa.

[chars]: An error was reported by [chars]:\n An warning message is specified by SAR

[chars] [Error code [dec]]
device in specified location.

[chars]: Warning message was reported by A Warning message is reported by SAR in

[chars]:\n [chars] [Error code [dec]]
specified location about TCAM entries.

[chars]:SAR register is being dumped

The contents of the SAR register are being

dumped into another buffer when an error
is reported by SAR device.

[chars]: Informational message was

reported by [chars]:\n [chars] [Error code
[dec]]

An informational message is reported by

SAR in specifed location such as TCAM
entries are corrected.

[chars]: c_shim_caps_aib_init failed,

[chars]\n

Establish and open a connection to AIB got

failed.

[chars]: c_shim_caps_aib_init failed,

[chars]\n

Failure occured while trying to establish a

connection with Adjacency Information
Base Process due to one of the following
reasons: 1. Failed to create & initialize
event connection data structure 2. Failed to
register callback function for connection
open requests and error 3. Failure occured
while opening the connection

C_shim_query_internal got failed due to

[chars]: c_shim_query_internal failed for ifh either shim info structure is NULL or getting
[hex]([dec])
shim info for the ifh.

Failure occured while fetching Shim

information due to one of the following
reasons: 1. Invalid arguments passed to
function 2. Shared memory not yet
[chars]: c_shim_query_internal failed for ifh initialized 3. Information pertaining to
[hex]([dec])
requested handle not found

[chars]: event_manager_create failed\n

Failure occured while trying to create a

event manager. It is used to create a
communication (message) channel and
provide the framework for managing the
messages and various events that arrive on
the channel. Possible reasons for failure
could be: 1. Insufficient memory 2. Error
occured while creating message channel 3.
Failure occured while attaching to message
channel

[chars]: event_manager_create failed\n

event manager creation got failed.

[chars]: gsr_spa_smlib_client_find_shim
failed for ifh [hex]: [dec]

The SHIM information not found for the

given interface

[chars]: shmwin_free failed, rc [hex],

[chars]

Failure occured while releasing shim

window memory due to one of the
following reasons: 1. Invalid arguments
passed to the function 2. Error occured
while performing memory related
operations

[chars]: shmwin_free failed, rc [hex],

[chars]

Memory allocated earlier by a call of

shmwin_malloc is not freed as shwin_free()
api got failed

Could not get shim info for ifh [hex]

Could not get shim info for given interface

handle

Could not get shim info for ifh [hex]

Could not get shim info for given interface

handle

gsr_spa_smlib_init_check() failed for the

given interface handle due to the following
reasons, 1. pm lib has not been initialized
[chars]: gsr_spa_smlib_init_check failed for 2. allocation of memory for the shared
ifh [hex]: [chars]
context failed.

[chars]: spa_smlib_init_check failed for ifh

[hex]: [chars]

Failure occured while checking if PM Library

is initialized due to one of the following
reasons: 1. Invalid Arguments passed to
function 2. Unable to find information
pertaining to requested window 3. Error
occured while fetching shim information

[chars]: shmwin_malloc failed for ifh [hex]: shwin malloc failed for the given interface
[chars]
handle

Allocating memory to a shim window failed

due to one of the following reasons: 1.
Invalid arguments passed to the function 2.
[chars]: shmwin_malloc failed for ifh [hex]: Insufficient memory 3. Error occured while
[chars]
performing memory related operations

[chars]: shmwin_malloc failed, shmwin, rc: Memory allocation for shim window failed
[dec], error: [chars] has not initialized
as the identifier is not valid.

Null shim info structure for ifh [hex]

Null shim info encountered for given

interface handle

Null shim info structure for ifh [hex]

Null shim info encountered for given

interface handle

[chars]: shmwin_platform_info failed :

[chars]

Reading of the platform_shmwin file and

reteriving the header base adrress and size
got failed.

[chars]: pthread_create failed\n

pthread creation got failed.

[chars]: pthread_create failed\n

Failure occured while creating shim partner

thread.

c-shim query failed for ifh [hex]

Unexpected c-shim query failure for given

interface handle

c-shim query failed for ifh [hex]

Unexpected c-shim query failure for given

interface handle

[chars]: unable to reset fn ptrs in btree :

[hex], [chars]

Failure occured while reseting memory

allocation and delete function pointers in
btree due to one of the following reasons:
1. Invalid tree reference handle 2. Function
Pointers are null

[chars]: unable to reset fn ptrs in btree :

[hex], [chars]

Unable to reset function pointers in btree

[chars]:
c_shim_caps_control_server_open_bay
failed\n

failed due to one of the following reasons:

1. Failed to create & initialize event
connection data structure 2. Failed to
register callback function for connection
open requests and error 3. Failure occured
while opening the connection

[chars]:
c_shim_caps_control_server_open_bay
failed\n

c_shim_caps_control_server_open_bay
routine got failed because event
connection notify or open failed or ECM is
not success.

[chars]: shmwin_open failed : [chars]

shmwin_open got failed since the malloc of

user area size is not successful.

[chars]: shmwin_open failed : [chars]

Create/Attach to a shared memory window

failed due to one of the following reasons
1. Invalid arguments passed to the function
2. Error occured while performing memory
related operations

[chars]: spa_smlib_client_find_shim failed

for ifh [hex]: [dec]

Failed to get Shim Header Information due

one of the following reasons: 1. Invalid
Arguments passed to function 2. Shared
Memory not yet initialized 3. Mutex Access
Error 4. Information pertaining to given
handle not found

%s: spa_smlib_shim_tree_lock() failed for

ifh [hex]

Failure occured while locking a mutex.

%s: gsr_spa_smlib_shim_tree_lock() failed

for ifh [hex]

gsr_spa_smlib_shim_tree_lock got failed for

the given interface handle.

%s: gsr_spa_smlib_shim_tree_unlock()
failed for ifh [hex]

The gsr_spa_smlib_shim_tree_unlock api

failed for the given interface handle

%s: spa_smlib_shim_tree_unlock() failed for

ifh [hex]
Failure occured while unlocking a mutex

[chars]: shmwin_platform_info failed :

[chars]

Failed to fetch Header base address &

Window size information from shmwin
window file, due to one of the following
reasons: 1. Invalid arguments passed to
the function 2. Error occured while
opening/accessing the file 3. Required
information not available in the file

[chars]: c_shim_query_internal entered for Debug information - Indicates control

ifh [hex]
reached a particular functionality.
[chars]: c_shim_query_internal entered for Entered the c_shim_query_internal rountine
ifh [hex]
for the specific ifh
[chars]: creating shim_info entry for ifh
[hex]

Creating shim info entry for the given

interface handle

[chars]: creating shim_info entry for ifh

[hex]

Creating shim info entry for the given

interface handle

[chars]: deleting shim_info entry for ifh

[hex]

Debug Information - Deleting shim info

entry for the given interface handle

[chars]: deleting shim_info entry for ifh

[hex]

Deletes the shim info entry for the given

interface handle

[chars](): encap_type = [hex] ctrl_shim =

[hex], hp_shim = [hex], lp_shim = [hex]
ctrl_ci = [hex], normal_ci= [hex], seq_ci =
[hex]\n

Debug Information - Displaying Shim

information

[chars](): encap_type = [hex] ctrl_shim =

[hex], hp_shim = [hex], lp_shim = [hex]
ctrl_ci = [hex], normal_ci= [hex], seq_ci =
[hex]\n

This message prints shim and CI values.

[chars]: platform_fix_spa_encap for

interface [hex] passed

Querying the C-shim info passed.

[chars]: platform_fix_spa_encap for

interface [hex] passed

Debug Information - Fetching Shim

Information is successful

reading from SHM for [hex] , encap is :[dec]

received Nor_shim is :[hex] rxshim :[hex]
Reading shim information for the given
tx_shim :[hex]
interface handle of encap type MFR.
Debug Information - Displaying
reading from SHM for [hex] , encap is :[dec] Encapsulation, shim and flag for the
received shim is :[hex], flag is :[hex]
requested handle
Reading the shim information from the
reading from SHM for [hex] , encap is :[dec] shared memory for the given ifh of encap
received shim is :[hex]
type HDLC.
Reading shim information from the shared
reading from SHM for [hex] , encap is :[dec] memory for the given interface of encap
received shim is :[hex]
type PPP.

Failed during AIB initialization, err: [chars]

The spa cema Partner initialization failed

while trying to connect to AIB.

[chars]:CEM configuration exists.

CEM configurations exist.SPA mode cannot

be changed.

[chars]:Invalid Card Type configured. Will

revert to Default cardtype

Failure occured while changing the port

type.

[chars]: L3QoS configs exist.

L3 Qos configs exist.SPA mode cannot be

changed.

[chars]:Configurations under Sonet

detected

This message indicates that the

configurations under sonet exist

[chars]: Unsupported SPA mode

The mode chosen to be configured is not

supported on this spa.

[chars]:bind to [chars] failed

Creation of sysdb bind point failed.

[chars]:Remove the existing controlleri

T3/E3 configurations

Remove the already existing configurations

while changing the port type

[chars]:Proceeding with SPA reload due to

change in card type.

A SPA reload is needed to have the card

type change into effect.

!!!! ALERT !!!! - SPA in bay [dec]/[dec]

needs to be reset manually due to SONET
framing change using 'hw subslot 0/[dec]/
[dec] reload' command, for proper
operation\n

This message indicates that the SPA in the

particular bay has to be reset manually due
to SONET framing change using the
command 'hw subslot <>/<>/<> reload'
command for proper operation.

SPA in bay [dec]/[dec]/[dec] needs to be

reset using hw subslot [dec]/[dec]/[dec]
reload due to SONET framing change

Due to framing change on SONET port, SPA

need to be reloaded for spa to function
properly.

[chars]: [chars] controller is not yet IM

initialized \n

controller is nt initialized yet aftr 100 msec

SPA [dec]/[dec]: [dec] [chars] events on

HDLC Controller were encountered.\n

The SPA driver detected an error event on

the HDLC Controller

SPA [dec]/[dec]: [dec] [chars] events on

HDLC Controller were encountered.\n

The SPA driver detected an error event on

the HDLC Controller

invalid cmd cmd_queue = [pointer],

cmd_size = [dec]

The size of the given command exceed the

specified size.

Null platform specific field for link [hex],

ifname [chars]

The platform specific name in the link

record is not set.

SPA in bay [dec]/[dec]/[dec] needs to be

reset using hw subslot [dec]/[dec]/[dec]
reload due to SONET framing change

Due to framing change on SONET port, SPA

need to be reloaded for spa to function
properly.

[chars]

Jacket process spawns the SPA process and

waits for the initialization to complete. But
initialization fails putting SPA into FAILED
state. As a part of the above, we find the
mesage Ltrace init failed message.

[chars]

Jacket process spawns the SPA process and

waits for the initialization to complete. But
initialization fails putting SPA into FAILED
state. As part of retry mechansim, the
above message is seen.

To complete the mode change the SPA

must be power-cycled.

SPA WAN mode changed to lan/wan from

CLI. To complete the mode change the SPA
must be power-cycled.

[chars]

The spa_ether_ctx context data cannot be

set.

[chars] [chars]

The Jacket driver failed to parse spa driver

argument.

[chars]

The internal SPA MAC got out of sync. SW

needs to reset the device in order to clear
the issue

[chars] Failed to attach ECM notify handler Failure occured while attaching ECM Notify
for EDM [dec]
Handle for EDM

[chars]: bag_encode failed ([chars])

Failure occured while Bag Encode

[chars] bag registration failed [dec]

Failure occured while Bag Registration

failed to close ether_shim control server

([chars])\n

Failure occured while closing ethernet shim

control server

[chars] Failed to create ECM for EDM [dec] Failure occured while creating ECM for EDM

[chars] failed to destroy sysdb ecm [dec]

Failure occured while destroying SYSDB

ECM

Failure occured while destroying Event

failed to destrory event manager([chars])\n Manager

[chars] EDM ECM open failed [dec]

Failure occured while EDM ECM Open

Failure occured while initializing Ether

[chars]: Ether hw_helper init failed, rc [dec] Hardware Helper

ether_shim_caps_control_server_open_bay( Failure occured while trying to open ether

) failed in [chars]: \n
shim control server

Ether SPA: event_manager_create() failed

in [chars]\n

Failure occured while Creating Ether SPA

Event Manager

ether_spa_init() failed in [chars]: [chars] \n Failure occured while initializing ETHER SPA

not match Ether SPA Type [dec] in [chars]

This error message indicates that SPA type

is invalid

[chars]: Failed to get my_nodeid for port

[dec]/[dec]: rc [dec]

Failure occured while trying to get Node ID

for Port

failed to get process name: [chars]\n

Failure occured while getting Process name

[chars]: Failed to get rx_uidb for m_port

[dec] bay [dec] rc [dec]

Failure occured when getting receiver UIDB

for port

[chars]: Failed to get rx_uidb for b_ifh [hex]: Failure occured while getting Receiver UIDB
rc [dec]
for interface

[chars] failed to get SYSDB file descriptor

for EDM failed [chars]

Failure occured while getting SYSDB FD for

EDM

[chars]: Ether spa [dec] port [dec] get uidb Failure occured while getting Ether SPA port
failed rc [dec]
UIDB

[chars](bay=[dec]): gila/fugu
reconfig_needed() failed rc = [dec] or
reconfig needed ([dec])

Failure occured while checking if

GILA/FUGU Reconfiguration is needed

[chars](bay=[dec]): gila/fugu restart()

failed rc = [dec]

Gila/Fugu restart failed

[chars](bay=[dec]): Gila/Fugu Tcam

reconfig needed ([dec])

Reconfiguration needed for Gila/Fugu Tcam

[chars](bay=[dec]): Gila tcam restart()

failed rc = [dec]

Failure occured while restarting GILA Tcam

[chars]

As part of trying to configure dot1q vlan

with vlan id same as that of outer vlan of
QinQ configuration on other sub-interface,
then error has to be reported to remove the
inconsistent config.

[chars]: Invalid arguments

Null value is passed to the arguments

[chars](bay=[dec]): MAC reconfig_needed() Failure occured while checking if MAC

failed rc = [dec] or reconfig needed ([dec]) Reconfiguration is needed

[chars](bay=[dec]): MAC restart() failed rc

= [dec]

MAC restart failed

[chars](bay=[dec]): MAC SetPortype()

failed rc = [dec]

Failure occured while setting MAC Port Type

[chars]: naming ether spa thread for bay

[dec] failed ([chars])

Failure occured while naming Ether SPA

Thread for Bay

[chars]: NULL ether_spa

Received ETHER SPA is null

[chars]: run out of memory

Running out of memory

plugin_analyze() failed in [chars] \n

Failure occured while analyzing Plugin

[chars]: plugin context is null

Plugin Context is NULL

[chars] [dec]

Port deletion failed to complete within the

timeout period.

[chars]: Ether spa [dec] port [dec] could

not enable port rc [dec]

Port enabling for Ether SPA Port failed

pthread_cancel failure in [chars]:

Failure while cancelling Thread

pthread_create failure in [chars]:

Failure occured while Creating Thread

[chars]: Ether spa [dec] port [dec] does not This message indicates that this port does
support Q-in-Q config [dec]
not support QinQ Configuration

[chars]: Create QinQ failed for port [dec] rc

[dec]
Failure occured while creating QinQ for port

[chars](bay=[dec]): Serdes
reconfig_needed() failed rc = [dec] or
reconfig needed ([dec])

Failure occured while checking if Serdes

Reconfiguration is needed

[chars]: Ether spa [dec] port [dec] could

not set policy rc [dec]

Policy setting for Ether SPA port failed

[chars]: Set Tunnel Mode failed for port

[dec] rc [dec]

Failure occured when setting Tunnel Mode

for Port

sysdb already registered for path [chars]

SYSDB is already registered for this path

Command failed, internal error for tuple

path [chars]: [chars]\n

This message says Command failed due to

Internal Error for Tuple Path

sysdb bind failed , [chars] \n

Failure occured while binding SYSDB

[chars] SYSDM init failed [dec]

Failure occured while initializing SYSDB

EDM FNS

Command failed, internal error [chars]

[chars]\n

Command failed due to Internal Error

[chars] SYSDB registration for EDM failed

[chars]

SYSDB register EDM failed

Tenabo Restart failed with rc = [dec], in

[chars]

Failure occured while restarting TENABO

A unsuccessful rc [dec] to attach phy in

[chars]

Unsuccessful attach to PHY

A unsuccessful rc [dec] to attach serdes in

[chars]
Unsuccessful rc to attach SERDES

A unsuccessful rc [dec] to attach Tenabo in

[chars]
Unsuccessful rc to attach TENABO

A unsuccessful rc [dec] to attach UT2 in

[chars]

Unsuccessful rc to attach UT2

UT2 Restart failed with rc = [dec], in

[chars]

Failure occured while restarting UT2

[chars]: Create VLAN failed for port [dec] rc Failure occured when creating VLAN for
[dec]
port

vpa_debug_init() failed in [chars]. \n

Failure occured while initializing VPA Debug

vpa_gila_edm_init() failed in [chars]:

[chars] \n

Failure occured while initializing VPA GILA

EDM

Waiting for Wanphy config restore

Waiting for WAN PHY Configuration Restore

Wanphy controller init failed in [chars]:

[chars]. \n

Failure occured while initializing WAN PHY

Controller

[chars]: dev_rc = [dec]

Transceiver information retrieval function

failed

Failed to initialize xcvr on spa [dec]

XCVR initialization on SPA failed

Failed to restart xcvr on spa [dec]

Failure occured while restarting XCVR on

SPA

[chars]: timer for xcvr SM creation failed for

bay [dec]
XCVR SM Creation Timer failed for bay

Failed to get MAC address for port [dec],

Interface assigned random MAC address.

PLIM driver was unable to get a MAC

address for the interface.

[chars] [dec] [chars]

Port deletion is taking longer time as there

is large config to be deleted and so SPA
driver prints out message every 2 min
regarding the same.

[chars]

SFP hit/recovered RX Low power warning.

[chars]

During brinup of Wanphy SPA, the config

has to be restored before init. With this we
can decide whether to get SPA in LAN or
WAN mode. This message indicates that
config restore of wanphy is getting delayed

[chars] [dec] [chars]

[chars]

Port deletion happened after the threshold

time.
This is an informational message.

To complete the mode change the SPA

must be power-cycled

SPA must be Power-Cycled to complete the

mode change

[chars]

An internal system software error has

occurred. This type of errors are in general
SW bugs that are caused by providing
wrong information to SPA FPD API.

[chars][[dec]]: [chars]

An image for an FPD could not be obatined

so that it could be updated. The cause of
the failure is indicated in the message.

[chars][[dec]]: Failed to get FPD version

information.

The version of the FPD could not be

obtained from the specified SPA. The FPD
information will not be available for the
specified SPA. System processing will
continue normally.

[chars][[dec]]: [chars]

An internal software error has occurred on

the specified SPA.

[chars][[dec]]: Failed to update FPD

'[chars]' image

The update operation for the specified FPD

image has failed.

[chars][[dec]]: Cannot perform FPD image

update on '[chars]' OIR state, it should be
in '[chars]' OIR state

The FPD image update operation could not

be performed because the specified SPA is
not in the correct state. The correct OIR
state for the SPA is specified in the
message text.

An attempt has been made to temporarily

change the operaional status of the SPA
from online to offline before the image for
the FPD could be updated on the target
[chars][[dec]]: Changing operational status SPA. For some SPA types, this operation is
to offline for update of FPD image
required.
[chars][[dec]]: Reloading the SPA for the
updated FPD image(s) to take effect

Indicates the reloading operation of the

SPA after the completion of the FPD image
update opearation.

[chars][[dec]]: Successfully updated FPD

'[chars]' image

The FPD image was updated successfully.

[chars][[dec]]: Starting update of FPD

'[chars]' image

The FPD update update operation has

started for the specified image.

Initialization of SPA driver failed: [chars] :

reason = [chars] ; exiting...

SPA driver encountered the annunciated

error during the driver initialization. The
System Manager process (sysmgr) will
automatically respawn the (spa_oc3_oc12)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

[chars]

The SPA driver on the linecard failed to call

SONET controll or POS interface related
system function. The issue may affect the
creation of SONET controller or POS
interface while the SPA is booting,
reloading or SFP OIR with different optics
rate. %s - error message indicating location
and the reason of the error

[chars]

The SPA driver on the linecard failed to call

SONET controll or POS interface related
system function. The issue may affect the
creation of SONET controller or POS
interface while the SPA is booting,
reloading or SFP OIR with different optics
rate. %s - error message indicating location
and the reason of the error

[chars]

The operation on SPA object failed. The SPA

driver controls all the hardware on the SPA.
If the operation on SPA fails, the SPA may
not be able to boot or work properly, and
the traffic may be affected. %s - error
message indicating location and the reason
of the error

[chars]

The operation on SPA object failed. The SPA

driver controls all the hardware on the SPA.
If the operation on SPA fails, the SPA may
not be able to boot or work properly, and
the traffic may be affected. %s - error
message indicating location and the reason
of the error

[chars]

There is an error detected during SPA

process restart. During the process restart,
the software will do: checking the hardware
config compatibility; re-creating SONET
controller and POS interface; restoring
configurations. Any failure in above will
cause restart failed. The traffic may or may
not be affected after restart failed, but the
further operation on SPA, e.g. changing
configuration, may not be carried out
properly. %s - error message indicating
location and the reason of the error

[chars]

There is an error detected during SPA

process restart. During the process restart,
the software will do: checking the hardware
config compatibility; re-creating SONET
controller and POS interface; restoring
configurations. Any failure in above will
cause restart failed. The traffic may or may
not be affected after restart failed, but the
further operation on SPA, e.g. changing
configuration, may not be carried out
properly. %s - error message indicating
location and the reason of the error

[chars]

There is an error detected during SFP

initialization. SFP is the pluggable optics on
the SPA, SFP initialization may happen
when linecard boots up, SFP OIR and SPA
process restart. SFP error is for any
possible error during the initialization. The
optics will not work if SFP OIR operation
failed, therefore no traffic will be affected.
%s - error message indicating location and
the reason of the error

[chars]

There is an error detected during SFP

initialization. SFP is the pluggable optics on
the SPA, SFP initialization may happen
when linecard boots up, SFP OIR and SPA
process restart. SFP error is for any
possible error during the initialization. The
optics will not work if SFP OIR operation
failed, therefore no traffic will be affected.
%s - error message indicating location and
the reason of the error

[chars] : reason = [chars]

SPA OC3/OC12 driver error messages

[chars] : reason = [chars]

SPA driver failed to obtain either its node ID

or extract rack/slot/instance information
(having obtained the node ID).

[chars]: , error desc:[chars]

[chars]

SPA process encountered an error during

software initialization. ltrace initialization is
failed. So we will not get any traces using
ltrace cli. It may fail very rarely. It will work
most of the time. We added this message
only for debugging purpose.
information message %s - message

[chars]

This is an informational message which

indicates, Sonetmib Perf monitoring is not
properly initialized. So, performance stats
will not be collected. This doesnt cause any
traffic loss or cause any issue for normal
operation of SPA. %s - error message
indicating pm_create_sonet_service failed

[chars]

Optics module has inserted %s - message

related to the SFP insertion event

Initialization of SPA driver failed: [chars] :

reason = [chars] ; exiting...

SPA driver encountered the annunciated

error during the driver initialization. The
System Manager process (sysmgr) will
automatically respawn the (spa_oc48)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger SPA
reload. After a certain number of SPA
reloads, the shelf manager will
permanently shutdown the SPA.

The SPA driver on the linecard failed to

initialize. The SPA driver controls all the
hardware on the SPA. If the SPA driver fails
to initialize, no traffic will pass, no SPA
related infrastructure will work. %d - SPA
SPA driver initialization failed in bay [dec]: bay number %s - indicates the reason for
([chars]/[chars]).
the failure %s - is the decoded error reason

The SPA driver on the linecard failed to

initialize. The SPA driver controls all the
hardware on the SPA. If the SPA driver fails
to initialize, no traffic will pass, no SPA
related infrastructure will work. %d - SPA
SPA driver initialization failed in bay [dec]: bay number %s - indicates the reason for
([chars]/[chars]).
the failure %s - is the decoded error reason

SFP OIR error in bay [dec]: ([chars]/

[chars]).

There is an error detected during SFP OIR.

SFP is the pluggable optics on the SPA, SFP
OIR can cause some operation in sw, e.g.
create/delete optics object, SFP
authentication. 'SFP OIR error' is for any
possible error during the operation. The
optics will not work if SFP OIR operation
failed, therefore no traffic can pass. %d SPA bay number %s - indicates the reason
for the failure %s - is the decoded error
reason

SFP OIR error in bay [dec]: ([chars]/

[chars]).

There is an error detected during SFP OIR.

SFP is the pluggable optics on the SPA, SFP
OIR can cause some operation in sw, e.g.
create/delete optics object, SFP
authentication. 'SFP OIR error' is for any
possible error during the operation. The
optics will not work if SFP OIR operation
failed, therefore no traffic can pass. %d SPA bay number %s - indicates the reason
for the failure %s - is the decoded error
reason

[chars] : reason = [chars]

SPA OC48 driver error messages

[chars] : reason = [chars]

SPA driver failed to obtain either its node ID

or extract rack/slot/instance information
(having obtained the node ID).

[chars] [chars]

SPA OC48 informational message

Optics module inserted into SPA in bay

[dec], port [dec]

Optics module has inserted %d - bay

number %d - port number

Optics module inserted into SPA in bay

[dec], port [dec]

Optics module has inserted %d - bay

number %d - port number

Optics module removed from SPA in bay

[dec], port [dec]

Optics module has removed %d - bay

number %d - port number

Optics module removed from SPA in bay

[dec], port [dec]

Optics module has removed %d - bay

number %d - port number

[chars] [chars]

SPA OC48 debug message

error, reason:[chars]

GSR SPA Driver encountered an error while

bringing up the SPA devices. %s - Error
message

[chars] (rc = [hex])

GSR SPA Driver encountered an error while

initializing the SPA device. %s - Error
message %x - Error Code

[chars][[dec]]: Failed to get FPD image

version for [chars]

The FPD image version could not be

retrieved from the SPA for the
pogrammable device that is specified in
the message text. This condition can occur
if the system attempts to retrieve the
version information while the SPA is not in
the correct operational state.

[chars][[dec]]: [chars] image download

error ([chars])

The FPD image download operation for the

indicated device has failed. The cause of
the error is also indicated in the message.

[chars][[dec]]: [chars] image update error

([chars])

The FPD image update operation for the

indicated device has failed. The cause of
the error is also indicated in the message.

[chars][[dec]]: Failed to reply a message

([chars])

A message to the specified SPA did not

receive a reply. The reason for the failure is
specified in the message.

[chars][[dec]]: Failed to send message

([chars]) after retries: [[dec]]

A message to the specified SPA could not

be sent. The reason for the failure is
specified in the message.

[chars][[dec]]: Open channel for [chars]

failed ([chars])

A communication channel could not be

opened with the specified SPA. The reason
for the failure is specified in the message.

[chars][[dec]] ([chars])

The error message in parentheses is

generated by SPA firmware for reason as
mentioned in the error message. This error,
and the message is logged by the plim
holding the SPA.

[chars][[dec]]: [chars]

An internal software error has occurred for

the specified SPA.

When the cardtype of T3E3 SPA is changed

to T3 from E3 or vice versa, it undergoes a
reload. A SPA reload is mandatory to have
[chars] [dec] [chars] [chars] [chars] [chars] the newly configured cardtype in effect.

[chars]: Cannot boot IPSEC SPA. Please

verify that the k9sec package is installed!

Failure in booting Ipsec spa.

[chars]: SPA Bus Device creation failed.

SPA bus Device creation failure

SPA ERR_L interrupt is asserted on subslot

[unsigned int]

SPA ERR_L interrupt is asserted by SPA

when SPA bus protocol violation happens.
This error happens mostly when there is an
issue with hardware itself. The SPA reset is
not going to recover the problem, hence
SPA put into FAILED state.

[chars]: Timeout waiting for CMD Ready

Timeout occurs while waiting for the

command.

[chars]:Failed to create timer.

Failed to create the timer associated with

the event.

Spa debug init failed ([chars])

Trying to use uninitialized debug events

[chars]: Timed out downloading firmware to Timeout occured in downloading firmware

the SPA
to SPA

Event create manager failed

Failed to create and initialize event

manager structures due to * SPA being in
FAILED state * Problem with SIP * SIP/SPA
communication failed

Event create manager failed ([chars])

Failed to create and initialize event

manager structures due to * SPA being in
FAILED state * Problem with SIP * SIP/SPA
communication failed

Xcvr optics [chars] checksum error

detected

The error occurs for the following reasons, When trying to install SFP/XFP into SPA
during SPA bootup. - When bad or
unsupported optics are inserted - During
SFP/XFP initialization failure - Corrupted
IDPROM %s - xcvr opticx location

[chars]: event_create_manager failed

([chars])

Failure in creating the event manager

structure.

[chars]: event_manager_destroy failed

([chars])

Failure in freeing up the existing event

manager structure.

[chars]:Failed to create event mgr.\n

Creation and initialization of event

manager structures failed.

Failed to get FPD version for SPA in subslot Failure in getting the FPD version for spa in
[dec]: [chars].
the given location

[chars]: Failed to get [chars] pid.

joibid=[dec] ([chars])

Failed to get process id and job id from

sysmanager

- mmap failed for the following reasons *

Invalid Virtual-Memory Allocations by jacket
process causing SPA FAILURE * Not enough
memory * The 'base_address' parameter
passed to mmap is not correct - The spa
might go to FAILED state on reload %s mmap() for spa FPGA failed reason: [chars] mmap failed reason %d - maximum
length [dec] offset [hex]
physical address space %x - base address

[chars]: Failed downloading firmware to the Failure occured when trying to downlaod
SPA
the firmware for SPA.
SPA shut and unshut is done based on the
flag value from install director Based on the
flag value in sysdb, API does shut or unshut
spa_bay_oper_api_notify_shut: flags =[hex] of spa.

[chars]: Failed to receive FPD versions

Failure occurs in receiving FPD versions.

[chars]: Failed to complete FPD upgrade

Failure to complete FPD upgrade.

[chars]: Timeout waiting for FPD versions

Timeout occurs while waiting for FPD

versions.

[chars]:fsm_check error for SPA

FSM table is not sorted properly.

[chars]:fsm_create error for SPA

Failure in creating Finite state machine for

SPA

[chars]: fsm_exec failed [dec]

Execution failure for finite state machine.

[chars]:fsm_push error for SPA

Push operation error occured for spa in

Finite state machine.

[chars]: num_fud=[dec], Too much FUDs,

can't allocate it.

FUDs have exceed the maximum allowed

count.

Process [chars]: spa_hlpr_sysdb_init failed

[chars]

The Spa hlpr sysdb init failed due to - A

SysDB client attempted to register for
verification or as an EDM on a path which
was already registered, registering more
than once for verificatin is due to multiple
RP's present in the node. - spa_cfg_hlpr
abort - On restart spa_cfg_hlpr registration
for verification may fail - During RPFO %s Process name %s - error/warning condition

Invalid bay # [unsigned int]

The bay number is invalid

[chars]: Invalid SPA console context

SPA plugin is not initialized properly.

[chars]:Invalid SPA Device parameter

SPA bus device is not initialized properly.

[chars]:Invalid SPA Plugin parameter

SPA plugin parameter is not initialized.

Invalid slot number [dec]

The slot number is invalid

[chars]: Invalid SPA parameter

SPA plugin is not initialized properly.

No Heartbeat from IPSec SPA. Reloading

the SPA

IPsec SPA crashed, has to be reloaded.

[chars]: failed to kill [chars] process.

[chars]

Process kill operation by sysmanager has

failed.

[chars]: Time out waiting for local SPI clock Timedout occured while waiting for SPI
to stabilize
local clock to stabilize.

Process [chars]: failed ([chars]) to run on

the dLRSC

The verifier application would need to

listen to LRd events to figure out if it is
running on a dlrsc The error refers to
processes not running on the dLRSC %s process name %s - error/warning condition

Host side LWM not initialized

Host side LWM is not initialized since the

spa debug structure is null which doesn't
have any impact as this is an informational
message to the user.

munmap() failed addr [hex], len [dec]

Failed to deallocate any mapping for the

region starting at ADDR and extending LEN
bytes %x - base address %d - maximum
physical address space

[chars]: Unable to attach spa message

header ([chars])

Failure in attaching header to the message.

[chars],[chars](): mmap([chars]) failed for

k9_area_magic, err=[dec].\n

Failure in mapping the shared memory

object into address space.

[chars]: End of Memory

Failure to allocate memory to the message

block

[chars]: Not space for allocation memory

([chars])

No space to allocate memory for the buffer

NULL evm

Event manager not created

[chars]:Null SPA ptr

Spa plugin value is not initialized.

[chars]: bay [dec] heartbeat missed,

expected seq# [unsigned int] received
seq# [unsigned int], Time since last
message [dec]s

The IPC communication between local CPU

and host in the specified slot indicated in
the message is not functional. If the
problem persists the SPA will be reloaded
to recover from the failure.

Failed to create pm_service in bay: [dec]

This is an error condition which should not

occur in normal conditions. If this message
is seen, the sonetmib stats will not be
updated. %d - indicates the bay number

[chars]: POST Failed

After FSM(Finite state machine) fails with

present state we boot the FSM with a new
state

[chars]: POST Timeout

After timeout we boot FSM with a new state

SPA_OK and PWR_OK signal is deasserted

on subslot [unsigned int] [chars]

SPA_OK and PWR_OK signal is asserted

after the SPA is powered on by LC. These
signals are deasserted when there is power
failure on SPA and this failure indicates that
it is SPA hardware issue. The SPA is put into
FAILED state.

[chars]: failed to start process [chars].

[chars]

Failure to start the sysmanager start

process.

[chars]: Timeout waiting for PROM

Registration

Timeout for PROM(PROGRAMMABLE READ

ONLY MEMORY) registration while sending
SPACP registration message.

[chars]: pthread_create for

spa_vcon_spacp_lwm_evm failed ([chars])

Failure in spawing a thread to process LWM

message.

[chars]: Timed out waiting for runtime

registration

Timeout occured while waiting for run time

registration

\n[chars] K9 shared memory couldnot

mapped by spa process

Shared memory containing Firmware

cannot be mapped by spa process.

[chars] failed shm_open\n

Shared memory creation failed.

[chars]: Timed out waiting for SPA SPI clock Timeout occured while waiting for SPA SPI
to stabilize
clock to stabilise.

[chars]: Timed out waiting for SPA SPI core Timeout while waiting for SPA SPI core
initialization to complete
initialization to complete.

[chars]: Failed to allocate buffer for SPACP

message.

Failed to allocate buffer for SPACP message

sent to SPA requesting FPD versions.

[chars]:Failed to initialize SPACP. Too many Failure to initialize SPA bus Communication
SPACP message blocks
protocol mesaage block.

[chars]: Failed to allocate buffer for SPACP

message.

Failure in sending SPACP message.

[chars]: SPACP opcode [hex] unknown.

Opcode in the SPACP message is unknown.

[chars]: Failed to configure SPALM window

Failed to configure SPA Large memory

window.

[chars]: Timed out configuring SPALM

window

Timedout occured while configuring SPALM

window.

[chars]: Timeout waiting for SPASM Ready

Timeout occured while waiting for SPA

small memory to get to ready state.

[chars]

The sysdb error occurs for the following

reasons - SPA Infrastructure SysDb error Event manager not created - Trying to use
uninitialized debug event - Unable to get
CPU nodeid

sysmgr blocked until primary failed

([chars])

The process block until the go-primary

notification is received is failed

[chars]: sysmgr_def_attr failed [chars]

failure in setting the sysmgr_proc_attr

structure to default values.

sysmgr get proc role failed: [chars]

Failed to get the redundancy related proc

role information

Process [chars]: sysmgr process ready is

failed [chars]

Indicating to sysmgr that the process is not

ready %s - Process name %s error/warning condition

[chars]:naming
spa_vcon_spacp_lwm_evm_thread failed
([chars])

Failure in naming the created thread for

LWM messages.

Registration of error strings failed with

error [hex]

Error string reistration failed.

SPA ([dec]): WANPHY SPA in ISSU case.

Using 3 mins timeout

If the Wanphy spa exist in ISSU case then 3

mins timeout is used

Downloading SPA Application Image

([chars])...

Downloading SPA Application image as

indicated in the message

Download SPA Application Image failed.

Failed to download the SPA Application

image.

SPA Application image exceeds RAM size: The size of the SPA Application image is too
Image size ([dec]) Shared mem size ([dec]) big.
The specified download method is not
SPA Download method [dec] not supported supported
SPA File exceeds Rdisk size: File size ([dec])
Rdisk size ([dec])
The size of the SPA File is too big.
[chars] [chars]
SPA discovered in bay [dec] [chars]
SPA removed from bay [dec] [chars]

SPA related error as indicated in the msg

For displaying SPA OIR.
For displaying SPA OIR.

Downloading SPA OS Image ([chars])...

Downloading SPA OS image as indicated in

the message

Download SPA OS Image failed

Failed to download the SPA OS image.

SPA OS image exceeds RAM size: Image

size ([dec]) Shared mem size ([dec])

The size of the SPA OS image is too big.

SPA Init Event Server failed

SPA Init SPA Keepavlie Handler failed

Creating SPA event handling server failed.

Creating SPA keepalive server failed.

Reloading [chars] in subslot [unsigned int]

after heartbeat failure ...
Reloading SPA because of heartbeat failure.
SPA in bay [dec] type [chars] [chars]
[chars]

For displaying state of a SPA

Cannot connect to channel [chars]

The channel connection for sending

messages and pulses is failed

Cannot connect to [chars]

Unable to connect to the channel to send

message

[chars]:command too long

The command entered is too long.

Failed to send SPA reset msg [chars]

Unable to send message to the connected

channel

Failed to send spa msg [chars]

The channel which is meant for sending

message is failed

Optics module inserted into SPA in bay

[dec]

Optics module has been inserted. %d indicates the bay number

Optics module inserted into SPA in bay

[dec]

Optics module has been inserted. %d indicates the bay number

Optics module removed from SPA in bay

[dec]

Optics module has been removed. %d indicates the bay number

Optics module removed from SPA in bay

[dec]

Optics module has been removed. %d indicates the bay number

[chars] should be replaced by real

implementation

This is just an informational message

[chars]: Event[[dec]] should be replaced by

real implementation
This is just an informational message

Failed to create pm_service in bay: [dec]

This is an error condition which should not

occur in normal conditions. %d - indicates
the bay number

Failed to create pm_service in bay: [dec]

This is an error condition which should not

occur in normal conditions. %d - indicates
the bay number

[chars] : [chars] : rc = [hex]\n

Marmot spabrg driver error

[chars] : SPAQFPBridgeCtrl INTR: [chars] : rc

= [hex]\n
Marmot spabrg driver error
[chars] : [chars] : [hex]\n

Marmot spabrg driver informational

message

[chars] : debug action: [hex]\n

Marmot spabrg driver informational

message

Vtwin Apps Trace1=[hex]

Failure in receiving the Vtwin version.

[chars]:failed to set BERT interval

Failed to set the bert interval on t3/e3

[chars]:failed to set cablelength on

port_num = [dec]

failed to set dsx3 cable length

[chars]:failed to clear mib bit on port_num Failure to clear Management information

= [dec]
base (MIB) on port.

[chars]:failure to set clock on port_num =

[dec]

Failure occured in setting the clock type

[chars]:failed to set port type

Failure occured while changing the port

type.

[chars] port_num = [dec], invert = [dec]

fails to config data inversion on the port

[chars]:Farend requested fullrate activation Fullrate activation on the controller is

blocked
blocked

[chars]:Farend requested fullrate activation failure to config Fullrate failed on the

failed
controller.

[chars]:Farend requested fullrate

deactivation blocked

fullrate deactivation on the controller is

blocked

[chars]:Farend requested fullrate

deactivation failed

Full rate deactivation on the controller

failed.

[chars] port_num = [dec], interval = [dec]

Failed to set a BERT pattern on a T3/E3 line.

[chars] port_num = [dec], mtu = [dec]

fails to set MTU config

[chars]:sync failed

This message indicates that the resync is

failed while switch over of RPs took place.

[chars]:failed to set bandwidth on

port_num = [dec]

failed to set bandwidth on a t3/e3 line.

[chars]:failed to set bit error rate test on

port_num = [dec]

Failure to configure Bit error rate test.

[chars]:failed to set bit on port_num =

[dec]

Failure occured while trying to set the

national bit.

[chars] port_num = [dec], crc = [dec]

Failure occured while trying to set the CRC

bit

[chars]:faied to set DSU mode on port_num

= [dec]
failed to set the DSU mode.

[chars]:Framing type failure on port_num = Failure occured in changing the frame type
[dec]
under the controller.

[chars]:Loopback set fails on port_num =

[dec]

Failure in setting loopback.

[chars]:fails to set remote bandwidth on

port_num = [dec]

Failure occurs while trying to set the

remote bandwidth on the port

[chars]:Debug added

A debug has been added inside the

function.

[chars]:Debug

A debug has been added inside the

function.

[chars]:Debug

A debug has been added inside the

function.

[chars]: Remove the T3/E3 controller

configurations

Remove the existing configs while

changing the card type

[chars]: Remove the T1/E1 controller

configurations

Remove the configurations on T1/E1 while

changing card type.

debug init [dec] failed ([chars])

SPA related error msg comes when there is

some problem with the initializing the
debug event type structure

SPA debug internal error, flag = [dec]

This is an internal SPA related error msg

SPA debug register failed ([chars])

[chars]

SPA related error msg which indicates

registering with sysdb fails
SPA related error msg

Unexpected NULL evm for SPA debugging

[chars]

Only critical if SPA debugging is not yet

initialized. It means somebody may try to
use uninitialized debug events.
SPA related info

Unable to register for details of session

destinations: [chars]

The SPAN Manager was unable to obtain

the information required to replicate traffic
to the destinations of one or more monitor
sessions. It is possible that traffic will not
be replicated correctly for the affected
monitor-sessions. Standard forwarding will
not be affected. Use 'show monitor-session
status' to identify the affected monitor
sessions and to provide more information
regarding the current state of the affected
destinations.

Unable to process updated destination

information: [chars]

The SPAN MGR was unable to send/recieve

the necessary messages in order to update
the current destination information. It is
possible that traffic will not be replicated
correctly for the affected monitor sessions.
Standard forwarding will not be affected.
Use 'show monitor-session status' to
identify the affected monitor sessions and
to provide more information regarding the
current state of the affected destinations.

Failed to restore hardware state from

checkpoint: [chars]

The SPAN EA encountered an error while

trying to recover hardware programming
information based on checkpointed
records. The records are used to ensure
hardware resources are cleaned up
correctly; if an error has been enountered
then it is possible that traffic will continue
to replicated from sources or to
destinations on the affected node even
after configuration has been removed.
Standard forwarding will not be affected.

Found inconsistent data in checkpoint:

[chars]

The SPAN EA encountered some

inconsistent or invalid data while trying to
recover hardware programming information
based on checkpointed records. The
records are used to ensure hardware
resources are cleaned up correctly; if an
error has been encountered then it is
possible that traffic will continue to be
replicated from sources or to destinations
on the affected node even after
configuration has been removed. Standard
forwarding will not be affected.

Failed to restore Session IDs from

checkpoint: [chars]

The SPAN Manager encountered an error

while trying to restore its database from
checkpoint. The checkpoint database is
used to ensure that internal session IDs are
persistent across process restarts. This
failure indicates that there is a problem
with the table. The table will be deleted,
potentially leading to a brief interruption to
replicated-traffic-flow when the process
restarts, but SPAN should otherwise
continue to operate as normal. Standard
forwarding will not be affected.

Failed to remove an object ([chars]) from

the database

SPAN was unable to remove an object from

its database. The process will attempt to
recover, but it is possible that traffic will
not be replicated correctly, or some traffic
will not be replicated to the correct
interfaces. Standard forwarding will not be
affected.

Failed to record new updated destination

for monitor-session [chars]: [chars]

The SPAN MA was unable to record a

change to the destination interface for the
specified session. It is likely that traffic will
not be replicated to the desired
destination. Standard forwarding will not be
affected. Use 'show monitor-session status'
to identify the set of affected interfaces
and to provide more information about
their current state.

Failed to inform the System Manager that

[chars] is exiting: [chars]

The specified process failed to notify the

System Manager that it was exiting. In very
rare cases, this could result in the process
not being restarted when it ought to be.

Failed to send [unsigned int] [chars]

messages to update SPAN configuration:
[chars]

The SPAN MA was not able to send a

message to update monitor-session
configuration for a set of source interfaces.
It is possible that traffic will not be
replicated correctly at the affected source
interfaces. Standard forwarding will not be
affected. Use 'show monitor-session status'
to identify the set of affected interfaces
and to provide more information about
their current state.

Failed to initialize [chars]: [chars]%s

An error was encountered while the

specified process was initializing. The error
message contains details about the source
of the error.

[chars] lost event: [chars]

The specified process failed to receive an

event that was sent to it.

Failed to update the hardware after

connection loss: [chars]

The SPAN EA was not able to update traffic

replication programming in the hardware. It
is possible that traffic will be replicated
incorrectly at some source interfaces, and
that hardware resources will not be
released. Use 'show monitor-session status'
to determine which interfaces are affected.
Standard forwarding will not be affected.

The SPAN MA was unable to clear statistics

for the specified source interface. The SPAN
MA would normally clear statistics at the
point at which a source interface is
removed from a session. Traffic replication
will continue to operate as normal, but
statistics relating to traffic replicated while
the interface was in the session it has just
Failed to clear statistics for source interface been removed from will persist until they
[hex]: [chars]
are manually cleared.

!!!! ALERT !!!! - SPA in bay [dec]/[dec]

needs to be reset manually due to SONET
framing change using 'hw subslot 0/[dec]/
[dec] reload' command, for proper
operation\n

This message indicates that the SPA in the

particular bay has to be reset manually due
to SONET framing change using the
command 'hw subslot <>/<>/<> reload'
for proper operation.

Invalid packet(s) in batch: [chars]

A malformed packet was detected in a

batch passed to the SPIO platform libraries.

Not supported: [chars] packets for [chars]

The specified action is not supported by

the SPIO platform libraries.

spu: msg: [dec], retried: [dec] time(s),

failed to send, errno: [chars]

Unable to send a message to the SPU

server.

[chars]

This is an informational message in the

SPU client LIB.

SPU fatal error occurred ... [chars] core

dump is created and [chars] stored on CP

A fatal error occurred in SPU h/w. Core

dump process ended' .

A fatal error occurred in SPU h/w. Fast path

ME's are going to be stopped. No future
connection between service blade and RP
will be possible.Default action is to reload
board, but if coredump is not stored on
CP's CF, reload may be prevented by
SPU fatal error occurred ... Fast path ME are appropriate CLI and core dump , which is
stopped . Core dump will [chars] be stored always exists on XScale RAM disk may be
on CP
accessed from IXP console.
SPU fatal error occurred ... Started [chars]
core dump process
Fatal error: [chars]: Err=[dec]

A fatal error occurred in SPU h/w. Core

dump process started .
A fatal error occurred in SPU Driver.

Nonfatal error: [chars]: Err=[dec]

A non fatal error occurred in SPU Driver.

Soft error occurred... [chars] : status 1 :

[hex], status 2 : [hex]

A fatal error occurred in SPU h/w.

[chars]

This is a Informational message in the SPU

Driver.

Corrected soft error ... [chars] : status 1 :

[hex], status 2 : [hex]

Single bit DRAM error was succesfully

corrected on SPU h/w.

[chars] : [chars]

traceback messages

[chars]: Duplicate mac addresses in

topology

Another node on the ring is using the same

MAC address as this node. This can effect
traffic forwarding.

[chars] SRR usage changed ([chars])

SRR ring usage is changed using Inner,

Outer or Both rings. There are/were
multiple faults (or user requests) on the
ring causing potential loss of
traffic/bandwidth.

[chars] [chars] on side [char] ([chars])

The specified side of the interface has

wrapped or unwrapped for the given
reason. There is/was a fault (or user
request) on the ring causing potential loss
of traffic/bandwidth.

[chars] SRR version mismatch detected.

SRR has detected incompatible versions

with other nodes on the ring and cannot
inter-operate.

[chars] Thread synchronization failed:

[chars]

Thread synchronization failure has

occurred. The text of the message displays
the failed operation with error code.

[chars] HFR LC SRP Software Initialisation

failed: [chars]

Some requested operation failed during

initialization. The text of the message
displays the failed operation with error
code.

[chars]: Single node in topology

The topology discovery resulted in a single

node being found. This is most likely a
transient condition during initial ring bringup.

1) An ACE modification can fail in

apply/commit phase because of one of the
following reasons: a) TCAM max limit has
ACE modification apply/commit failed for
been reached. b) RLB resources are not
acl: [chars]. rc:[chars]. To recover remove & available. c) IPv6 address compression
re-attach the concerned ACL
table is full.

[chars] acl failed on interface

<<CH[hex]>>. [chars]

1) An ACL could not be applied to hardware

because of one of the following reasons: a)
TCAM max limit has been reached. b) RLB
resources are not available. c) IPv6 address
compression table is full. This error can
happen when a new bundle member is
added and the ACL can not be programmed
successfully. 2) An ACL could not be
removed from hardware.

[chars] failed due to [chars]

initialize internal permit/deny entries for

IPv4/IPv6. These entries are needed for
programming/removal of hardware entries
for IPv4/IPv6 security ACLs. 5) Failed to
initialize connection with interface
manager proxy service. 6) Failed to
initialize RLB (range logic block)
checkpoint. This is needed for
checkpointing range logic block information
for restore on process restart. 7) Failed to
initialize Feature EA DLL API needed for
programming of hardware resources. 8)
Failed to initialize callback function from
Feature EA DLL for compiling IPv4/IPv6
TCAM entries needed for security ACL
programming in hardeare. 9) Failed to
initialize callback function from Feature EA
DLL to handle reprogramming of RLB and
IPv6 source prefix compression table
request from TCAM manager. 10) Failed to
initialize feature checkpoint info. This is
needed for checkpointing IPv4 and IPv6
security ACLs programmed in hardware.
11) Failed to initialize callback functions
from ACL configuration manager to perform
hardware resource checks and ACE
resequencing. 12) event_block failed. This
indicates process has encountered
unexpected error while waiting for events.
13) Failed to initialize callback functions for
receiving incremental updates for IPv4/IPv6
security ACL configuration.

[chars] failed due to [chars]

Initialization of SSE TCAM Mgr process has

failed due to one of the following reasons:
1) Failed to initialize event manager. This
would prevent process from receiving
events. 2) Failed to initialize the EDM for
the IPv6 Prefix Compresssion Library. 3)
Failed to initialize the IPv6 Prefix
Compresssion Library itself, which inits the
default compression entries. 4) event_block
failed. This indicates process has
encountered unexpected error while
waiting for events.

[chars] failed due to [chars]

Initialization of uidb_svr process has failed

due to one of the following reasons: 1)
Failed to create server context. 2) Failed to
get schedular parameters. 3) Failed to
initialize event manager. This would
prevent process from receiving events. 4)
Failed to register with debug. This would
prevent process from logging debug
messages. 5) Failed to bind UIDB server
with MIPC server. This is needed to
program features in hardware. 6) Failed to
connect to PLIM asic processes. This is
needed to program features in hardware.
7) Failed to initialize checkpoint. This is
needed to checkpoint UIDB data to restore
on process restart. 8) Failed to allocate,
initialize and checkpoint shadow memory.
This is needed to store and restore UIDB
internal data. 9) Failed to get metro asic
version. 10) Failed to attach event handlers
needed to handle LWM messages. This is
needed to enable/disable various features
in hardware. 11) Various Sysdb or EDM
failures 12) event_block failed. This
indicates process has encountered
unexpected error while waiting for events.

Error initializaing the SSRP subsystem:

[chars]

An error was encountered whilst initializing

the SSRP sybsystem: %s.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error using the

Backend service related to use of either
SysDB or SubDB. The error message
describes what operation has failed and
why it failed. The most likely reason for this
is low memory resources or a programming
error.

An SSRP keepalive message has been

received containing a magic number which
is different from expected. This either
indicates a problem on the peer router, or
The SSRP group [unsigned int] is receiving indicates that SSRP has somehow begun
bad packets from the peer. They contain
receiving packets from a different router
the magic number [hex], should be [hex]. altogether.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error using the Bag

Client library. The error message describes
what operation has failed and why it failed.
The most likely reason for this a low
memory condition but the error could also
be caused by a programming error. The
error will affect PPP MA's ability to provide
operational management data, but won't
otherwise affect PPP MA's operation.

An error has occured creating channels for SSRP was unable to create the TCP
SSRP group [unsigned int]: [chars]
channels for this group.

Unexpected error encountered whilst

[chars]: [chars]

PPP MA encountered an error using the

debug service. The error message
describes what operation has failed and
why it failed. The error could be caused by
low memory resource or programming
error.

Error closing '[chars]' connection: [chars]

SSRP failed to close a connection to an

essential service. This is an internal error
and it requires a restart of the process for
recovery.

Error creating '[chars]' connection: [chars]

SSRP failed to create a connection to an

essential service during initialization. This
is an internal error. It requires a restart of
the process for recovery.

After detecting an error with the connection

to the specified service, SSRP failed to
reset that connection. This is an internal
error. It requires a restart of the process for
Error resetting '[chars]' connection: [chars] recovery.

Error registering for data events on

'[chars]' connection: [chars]

During initialization, SSRP failed to register

for input or output notifications for the
specified service. This is an internal error. It
requires a restart of the process for
recovery.

Error registering for critical events on

'[chars]' connection: [chars]

During initialization, SSRP failed to register

for essential notifications regarding the
state of the connection for the specified
service. This is an internal error. It requires
a restart of the process for recovery.

Error opening '[chars]' connection: [chars]

SSRP failed to open a connection to an

essential service during initialization. This
is an internal error. It requires a restart of
the process for recovery.

Failed to register a handler for '[chars]'

messages: [chars]

SSRP failed to register a handler for the

specified class of event. This is an
initialization error and implies that SSRP
will not be able to operate correctly. The
PPP MA process will abort and be restarted
in an attempt to recover. The cause may be
a resource starvation problem but is most
likely to be an internal programming error.
The error message should give more
details.

Failed to send '[chars]': [chars]

SSRP failed to send the specified message.

The cause may be a resource starvation
problem but is most likely to be an internal
programming error. The error message
should give more details.

The SSRP group [unsigned int] appears to

be connected to itself - the peer is using
the same magic number [hex].

An SSRP message has been received

containing the local magic number. This
makes it highly likely that the SSRP TCP
channel is connected to itself. In the
unlikely event that both ends select the
same magic number, a new random
number is chosen locally, so the situation
will recover itself.

Unexpected error encountered whilst

[chars] the [chars] buffer: [chars]

PPP MA encountered an error using the

Lightweight Tracing service. The error
message describes what operation has
failed and why it failed. This is a fatal error
and the PPP MA process cannot continue. It
will abort and subsequently be restarted by
SysMgr in an attempt to recover.

Failed to allocate %zu bytes for '[chars]'

The process failed to allocate memory for

the specified resource.

Unexpected error encountered whilst

[chars]: [chars]

SSRP encountered an unexpected error

using the Managed Timer library. This is
most likely to be due to a low memory
condition but may also be an internal
programming error. The error message
should provide more information about the
cause.

Unable to process SSRP request for

'[unsigned int]' sessions to client [chars]:
[chars]

An error has occured processing an

incoming SSRP request for the client.

Error setting socket options on '[chars]'

connection: [chars]

While creating a TCP socket, SSRP failed to

set the correct options on the socket. This
socket will now not be established
correctly.

The write queue for the TCP socket for

SSRP group [unsigned int] is full

The queue for storing messages to write to

the TCP socket is full for the specified SSRP
group. This means messages will be
dropped.

Unable to process SSRP state for '[unsigned An error has occured processing an
int]' sessions to client [chars]: [chars]
incoming SSRP state for the client.

Unexpected error encountered whilst

[chars]: [chars]

SSRP encountered an error using the

SysDB service. The error message
describes what operation has failed and
why it failed. The most likely reason for this
is a connection problem with the SysDB
server, but the error could also be caused
by low memory resources or programming
error.

Error destroying '[chars]' connection:

[chars]

During process termination SSRP failed to

destroy a connection to a service provided
by another process. This is an internal
error.

A second peer has connected to the Active

TCP channel for the specified SSRP group,
while there was already a connection to the
socket. This can validly occur if the SSRP
peer has gone away temporarily with being
noticed (e.g. due to a process restart, or
shutting the peer's interface), and has now
come back and wants to reconnect.
However, it can also occur if there is a
misconfiguration, meaning that more than
one SSRP peer wishes to connect to the
A second SSRP peer, [chars], has
same SSRP TCP channel. If this is the case,
connected to the TCP channel for SSRP
then SSRP will continually switch between
group [unsigned int]. This has removed the using the two different peers, and never
previous connection
reach a stable state.

STP was unable to initialize IO for one or

more interfaces. BPDUs will not be sent or
Process is restarting after failing to initialize received through these interfaces. The
IO for [unsigned int] interfaces including
process has restarted to attempt to clear
<<CH[hex]>>: [chars]
the error.

Received a BPDU but could not determine

the port. Stage: [chars]: [chars]

A BPDU has been received which STP is

unable to read.

STP only expects to be punted RX packets,

BPDU punted to STP on port <<CH[hex]>> but has received a BPDU with the TX
in TX direction
direction.

Received a packet on port <<CH[hex]>> STP received a BPDU with the wrong MAC
with an incorrect destination MAC address: address, most likely belonging to a
[chars]
different protocol.

Received a BPDU on port <<CH[hex]>>

with incorrect SAP

STP received a BPDU with the wrong SAP,

most likely belonging to a different
protocol.

STP received a BPDU but was unable to

STP was unable to read a BPDU received on read the contents via a call to the Ethernet
<<CH[hex]>>: [chars]
Packet Infrastructure.

Received a BPDU on <<CH[hex]>> which

did not conform to the IEEE specification.

STP received a BPDU which would not be

decoded in accordance with section 14.4 of
the IEEE 802.1Q specfication.

Restarting after failing to process one or

more expired timers: [chars]

An error has occurred processing one or

more timer events driving the MSTP
engine. The process has restarted to
correct this issue.

Failed to process [chars] of [chars] config:

[chars]

The STP IO process has failed to process

the indicated configuration event. This
event will not have taken effect.

Received an internal packet on port

<<CH[hex]>> referencing unknown MSTI
[unsigned int]

A packet has been received referencing an

unknown MSTI, despite the packet being
viewed as internal. This probably indicates
an inconsistency on the other end.

Error while disabling port <<CH[hex]>>.

Reason for disabling is '[chars]': [chars].

The STP IO process failed an attempt to

error-disable a port (in response to, for
example, a BPDU being received on a port
with BPDU-guard configured).

Failed to initialise [chars]: [chars]

A failure occurred during the initialization

of the process. This resulted in the restart
of the process.

Failed to handle the start of the ISSU

operation: [chars]

The STP IO process failed to handle the

start of an ISSU operation. As such, this
node may be out of sync with the rest of
the system. In the worst case, the network
will become disjoint during the ISSU
operation and will re-converge to the
correct topology once the ISSU has
completed.

The STP IO process is restarting due to an

Out of Memory condition. All state should
be resynchronised after restart.

The STP IO process failed to allocate

sufficient memory for one of its operations.
In order to recover from this situation, the
process is restarting and will resync state.

An error occured while determining

whether the IO process should exit, or in
exiting: [chars]

A failure occurred when either checking

whether a shutdown of the STP IO process
was required, or in informing the System
Manager that it was about to exit. In rare
cases, this could result in a failure by the
System Manager to restart the process
when it ought to do so.

STP on this router has been configured in

provider-bridge mode, but has been
connected to a router sending BPDUs in
non-provider-bridge mode (or vice versa).
STP configured in [chars] Mode received a This is a misconfiguration and could result
[chars] Mode BPDU on port <<CH[hex]>>. in loops in the network.

Restarting after failing to reset connection

to Interface Manager: [chars]

STP has encountered an error while

attempting to resynchronize its data with
Interface Manager. The process will restart
automatically to correct the problem.

STP running on a Standby card was unable

to synchronize its state with STP on the
Active card. The Standby process will
Standby process is restarting after failing to restart to attempt to resynchronize fully.
correctly synchronize with the active
This should only impact the Standby node,
process: [chars]
and traffic should remain unaffected.

A BPDU was received on portfast port:

<<CH[hex]>>

A BPDU was received on a port that was

configured for Portfast. This port will now
revert to a 'non-edge' port.

Received an unexpected message from

SysDB, type [unsigned int], path '[chars]'

STP IO has received a message from SysDB

of a form it does not recognise. The
message will be ignored.

Failure during STP Protected state update.

One or more ports may not be placed in
the correct STP state: [chars]

A failure occurred whilst notifying

infrastructure that one or more ports are
under STP control. If this occurs, these
ports may not take the correct STP state, in
the worst case leading to bridging loops
forming in the network.

Failed to update the STP IO processes

about the current ISSU operation: [chars]

The STP controller failed to inform the STP

IO processes about the ISSU operation in
progress after multiple retries. There
should not be any impact to the network
topology, although the STP IO processes
will not be aware that an ISSU operation
has started. The IO processes may emit
errors as they attempt to communicate
with services that are not available during
an ISSU operation.

Port state updates may have failed, and

further updates will be blocked, for
[unsigned int] port instances, including
instance [unsigned int] on port [chars]

Updates to the port states have errored for

the indicated instances. Any further state
updates on these ports cannot be sent until
the error is cleared, potentially blocking
important updates. It is also possible that
the current state has not been correctly
implemented.

<<CH[hex]>>: Failed to save Checkpoint

data: [chars]

An error occurred while checkpointing data

for the indicated interface. Operational
data may have been lost resulting in an
STP process restart being more impactful.

Errors have been seen while attempting to

Failed to checkpoint the latest data,
save updates after processing a batch of
updated after a batch of operations: [chars] operations. The process is restarting to
- restarting
recover from the error.

Port ID [unsigned int] is recorded as used

by interface [chars], but is also marked as
used by another interface

When recovering the existing data from

checkpoint following a restart of the MSTP
controller process, the indicated port ID has
been found to be in use on two or more
ports, including that named. The indicated
port will not be used by MSTP until the
problem is cleared.

Failed to initialise [chars]: [chars]

A failure occurred during the initialization

of the process. This resulted in the restart
of the process.

Invalid state received in L2VPN ACK:

[unsigned int]

When acknowledging a state update, the

L2VPN infrastructure sent an invalid value.

The STP controller failed to handle the start

of an ISSU operation. This should not affect
the network topology and any failure
should be resolved once the RP failover has
occured. The STP controller may emit
errors as it attempts to communicate with
Failed to process an ISSU start notification: services that are not available during an
[chars]
ISSU operation.

STP moved port [chars] to Loop

Inconsistent state

STP Loopguard feature moves a nondesignated port to Loop inconsistent state

when it stops receiving bpdu's on this port.

The MSTP specification dictates that

Portfast state changes should only be
made whilst a port is disabled. In order to
Portfast state changes will only be enacted enact the new portfast configuration, ports
when ports are shutdown
should be shutdown.

A failure occurred during shutdown of the

STP process, and it was unable to notify the
System Manager that it was about to exit.
In rare cases, this could result in a failure
Failed to notify SysMgr of intention to exit: by the System Manager to restart the
[chars]
process when it ought to do so.

Restarting after failing to reset connection

to Interface Manager: [chars]

STP has encountered an error while

attempting to resynchronize its data with
Interface Manager. The process will restart
automatically to correct the problem.

Restarting after failing to process one or

more expired timers: [chars]

An error has occurred processing one or

more timer events driving the MSTP
engine. The process has restarted to
correct this issue.

STP moved port [chars] to Loop consistent STP Loop inconsistency has been removed
state
due to normal reception of bpdu's.

Received a looped-back PDU on port

<<CH[hex]>>

A PDU has been received on a port which

was identical to that sent out of that port.
This suggests that the port may be loopedback into itself.

STP Server not available

stp_process is most likely in a bad state or

basic system services have failed.
stp_process error messages are generally
indicative of health of control-ethernet
which is critical for system operation.
Misbehavior of stp_process can cause
instability in the system.

STP Create Failed : [chars]

stp_process ran into errors while creating

the spanning tree instance for control
ethernet. stp_process error messages are
indicative of health of control-ethernet
which is critical for system operation.
Misbehavior of stp_process can cause
instability in the system.

Message Send Failed : [chars]

stp_process is most likely in a bad state or

basic system services have failed.
stp_process error messages are generally
indicative of health of control-ethernet
which is critical for system operation.
Misbehavior of stp_process can cause
instability in the system.

Stp port creation fail : [chars]

Spanning tree port creation failed on the

node. stp_process error messages are
indicative of health of control-ethernet
which is critical for system operation.
Misbehavior of stp_process can cause
instability in the system.

STP Set Mac Addr Failed : [chars]

MAC address assigned to the spanning tree

was either invalid or was not able to be set
for the spanning tree instance. stp_process
error messages are indicative of health of
control-ethernet which is critical for system
operation. Misbehavior of stp_process can
cause instability in the system.

Failed to start STP instance : [chars]

Spanning tree could not be started on the

control ethernet for the node. stp_process
error messages are indicative of health of
control-ethernet which is critical for system
operation. Misbehavior of stp_process can
cause instability in the system.

Controller [chars], failed to report noise

[chars] to registered features

Noise state on the link has changed for the

controller identified in the message. An
error occurred while attempting to report
an 'crossed' threshold value or 'fallen
below' threshold value. Due to this failure,
any applications such as MLPPP registered
for notification of these events were not
notified. If the error type is 'crossed', then
Voice quality may be affected.

[chars]

An error has occurred in the link noise

monitoring.

Controller [chars], noise [chars] major

warning threshold

Noise on the link identified in the message

has either crossed or fallen below the
threshold value configured by the user for
major warning level on this controller.
Video or voice quality may be affected if
noise is above the configured threshold.

Controller [chars], noise [chars] minor

warning threshold

Noise on the link identified in the message

has either crossed or fallen below the
threshold value configured by the user for
minor warning level on this controller.
Video or voice quality may be affected if
noise is above the configured threshold.

Controller [chars], noise [chars] removal

threshold

Noise on the link has either crossed or

fallen below the threshold value configured
by the user for link removal on the
controller identified in the message. Video
or voice quality may be affected if noise is
above the configured threshold.

Controller [chars], noise monitoring

disabled for level [chars]

Link Noise Monitoring has been disabled for

the level and T1/E1 controller specified in
the message.

Controller [chars], noise monitoring

enabled for level [chars]

Link Noise Monitoring has been enabled for

the warning level and T1/E1 controller
specified in the message.

[chars]([dec]): not enough memory for

[chars]

The process is out of memory.

[chars]([dec]): [chars] failed ([chars]) [chars]

A general failure occured while executing

the function in question. The message
contains info about the location and cause
of the failure and possibly anticipated
actions/effects.

[chars]: [chars] [chars]

The specified T1E1 Alarm has been

declared or released.

[chars] [chars]

A configurable controller loopback status.

[chars]: [chars] [chars]

The specified T1E1 is operationally down

due to alarm. Check alarm status using
show controller t1 command on the cli.

[chars]([dec]): [chars] - [chars]

A non-fatal error occured while executing

the function in question. The message
contains info about the location and cause
of the failure and possibly anticipated
actions/effects.

[chars]([dec]): not enough memory for

[chars]

The process is out of memory.

[chars]([dec]): [chars] failed ([chars]) [chars]

A general failure occured while executing

the function in question. The message
contains info about the location and cause
of the failure and possibly anticipated
actions/effects.

The specified T3E3 Alarm has been

at [chars]: ALARM : [chars] STATE : [chars] declared or released.
port name : [chars] msg : [chars]
New Far End Alarm Code received.
port name : [chars] msg : [chars]

A configurable controller loopback status.

[chars]([dec]): Reason : [chars]

Performance Monitoring Related Warnings.

Failed to get local time.

The specified T3E3 is operationally down

due to alarm. Check alarm status using
at [chars]: ALARM : [chars] STATE : [chars] show controller t3 command on the cli.

FUNCTION : [chars] LINE_No : ([dec]):

[chars] - [chars]

A warning is generated while Updatng

elapsed time from kernel clock. The
message contains info about the location
and cause of the failure and possibly
anticipated actions/effects.

Fatal error: [chars]: Err=[dec]

A fatal error occurred in TCAM RM Carve

Verify which involves exiting the process.

Info: [chars]

This is an informational message in the

TCAM RM Carve for Engine3 linecard.

tcam_rm: blwm client configuration failed,

error: [hex] [chars]

Unable to configure BLWM client

functionality.

tcam_rm: blwm client rebind failed, error:

[hex] [chars]

Unable to rebind with BLWM client

functionality after a connection reconnect.

TCAM RM: [chars] [dec] REGN TYPE [chars] Dump of the value, mask, result, stage,
REG-ID [dec] \n vmrid [hex] vmrid_p
region-id of MSG sent to the TCAM_RM
0x[pointer], \n rc [chars][[dec]]\n
server.

TCAM_RM MASK: [hex]%02x[hex]

%02x[hex]%02x[hex]%02x[hex]\n

Dump of the mask MSG sent to the

TCAM_RM server.

TCAM_RM RESULT: [hex]%02x[hex]

%02x[hex]%02x[hex]%02x [hex]
%02x[hex]%02x[hex]%02x[hex]%02x\n

Dump of the result MSG sent to the

TCAM_RM server.

TCAM_RM VALUE: [hex]%02x[hex]

%02x[hex]%02x[hex]%02x[hex]\n

Dump of the value MSG sent to the

TCAM_RM server.

tcam_rm: blwm msg send/flush: retried:

[dec] time(s), failed to send, error: [hex]
[chars]

Unable to send/flush a BLWM message to

the TCAM_RM server.

This is the message printed by the default

handler installed by TCAM_RM to process
the replies received for batched requests.
The default handler's behavior is to just
tcam_rm: Received a failure reply code for print this message. The application should
a batched request type [dec], failed
install its own handler to handle the replies
reason: [chars]
to batched requests.

Fatal error: [chars]: Err=[dec]

A fatal error occurred in TCAM RM which

involves exiting the process.

tcam_rm: msg: [dec], retried: [dec] time(s), Unable to send a message to the TCAM RM
failed to send, errno: [chars]
server.

Nonfatal error: [chars]: Err=[dec]

This is a error message in the TCAM RM to

indicate anomalies which are not FATAL.
Some of the messages may indicate a
failure to allocate resources needed by
applications. In many cases these
messages must not keep appearing after
the temporary situation is resolved.

tcam_rm: TCAM returned [dec] ([chars])

because [chars]

This is the message printed by the default

handler installed by TCAM_RM to process
the no memory reply received for batched
requests. The default handler's behavior is
to just print this message. The application
should install its own handler to handle the
replies to batched requests.

This is the message printed by the default

handler installed by TCAM_RM to process
the no memory reply received for batched
requests. The default handler's behavior is
tcam_rm: TCAM could not satisfy allocation to just print this message. The application
request, the node may not function as
should install its own handler to handle the
expected.
replies to batched requests.

tcam_rm: Replaying a batched request of

type [dec] that might have been partially
processed before.

Due to a server restart, a batched request

might have been partially processed. The
default handler installed by TCAM_RM
simply replays the request. Applications
that can not afford to replay a request
should install their own handler.

If the error count is incrementing there is a

discrepancy in the vmr_id pointer in the
tcam_rm: Client Cache Insert warning: Error shared memory. These entries which are
Count:[dec] Cache Msg type:[dec] Request being merged do not have the same vmr_id
VMR id: [hex] Cache VMR id: [hex] VMR id and this can cause a potenital memory
pointer: 0x[pointer]
leak.

tcam_rm: prep request warning: prev msg

code :[dec] curr msg code :[dec]

If this error message is seen, the client of

tcam_rm is attempting to send updates in
an unsupported sequence.

tcam_rm: Batch Reply Handler warning:

Error Count:[dec] Cache Msg type:[dec]
Req VMR id: [hex] Expected VMR id: [hex]
Resp VMR id: [hex] Req VMR id pointer:
0x[pointer]

If the error count is incrementing there is a

discrepancy in the vmr_id pointer in the
shared memory. These entries which are
being merged do not have the same vmr_id
and this can cause a potenital memory
leak.

This is an informational message from the

TCAM RM to indicate that it received TCAM
Parity error corrected: ASIC Side=[chars], parity error Interrupt notification message
TCAM Type=[chars] TCAM Dev=[dec], TCAM and corrected the corrupted tcam cell
Offset=[hex]
offset through its shadow image.

Info: [chars]

This is an informational message in the

TCAM RM.

UDLD protocol detects if a link is unidirectional and disables the port. UniUDLD protocol detected Uni-directional link directional links can cause problems in
on [chars], Port Disabled
ethernet networks and should be fixed.

UDLD daemon failed to initialize [chars]:

[chars]

The UDLD Daemon failed to initialize

correctly, and will now exit. It should be
restarted by SysMgr.

Failed to disable port <<CH[hex]>> on

which a UDLD error was detected: [chars]

A failure occurred when attempting to error

disable an interface after a fault condition
was detected on the interface by the UDLD
protocol. This will result in the interface
remaining up, when it should be shut
down.

Could not allocate [unsigned int] bytes of

memory required for operation

A UDLD process failed to allocate sufficient

memory for its processing. This could be
due to a shortage of system resources. The
process will restart and attempt to recover.

UDLD daemon failed to process events:

[chars]

The UDLD Daemon failed to process an

event, and will now exit. It should be
restarted by SysMgr, allowing it to
resynchronize its internal state.

UDLD api mutex lock failed line[[dec]]

err[[chars]]

A mutex lock acqure failed in the api

context, for UDLD lib around the line
number specified in error message.

UDLD api mutex unlock failed line[[dec]]

err[[chars]]

A mutex unlock failed in the api context,

for UDLD lib around the line number
specified in error message.

Port <<CH[hex]>> has mismatched

neighbors ([chars] on [chars] has echoed
information for unrecognized port [chars]
on [chars])

The UDLD protocol has detected a potential

wiring fault on this link. The link will be
disabled.

Port <<CH[hex]>> has no neighbors

remaining

All UDLD neighbors have been aged out.

This could indicate traffic loss on the link. If
UDLD is operating in aggressive mode on
the port, the link will be disabled.

Loopback detected on port <<CH[hex]>>

The UDLD protocol has detected that

packets transmitted from this port are
being received on the same port. The link
will be disabled. This could be caused by
one of the following: - There is a
connection between the Tx and Rx of this
port (directly or via intermediate nonUDLD-aware connections) causing
transmitted packets to be received on the
same port. - This port has a peer which is
using the same device ID and port ID.

Port <<CH[hex]>> is unidirectional

(neighbor [chars] on [chars] has not
echoed data for this port)

The UDLD protocol has detected a problem

with this link: It is unidirectional. The link
will be disabled.

The UDLD session on the interface has

started or been reset, and has not found
any neighbor devices. UDLD protection is
UDLD on port <<CH[hex]>> is waiting for not in place until communications with a
a neighbor device
peer device have been re-established.

UDLD on port <<CH[hex]>> is peering

with neighbor(s)

The UDLD session on the interface has

established communications with a
neighbor device.

[chars]: Can't extract spa type\n

Failed to get the SPA type.

Process initialization failed: ([chars]%s)

The uidb-mgr-main process failed to

initialize. A uidb is defined as a 'Micro
Information Data-Base' used by the
hardware ASIC's in the forwarding path.
The uidb-mgr-main process is responsible
for allocating/de-allocating the hardware
uidb's as configured by sw. If the uidb
manager fails to initialize, no interfaces can
be created or deleted on the linecard. %s indicates the reason for the failure. %s - is
the decoded error reason.

[chars]: failed to malloc id_node

Failed to allocate the memory.

[chars]: Failed to initialize wavl tree

Failed to initialize the tree.

[chars]: failed to insert to uidbid tree [dec]

[dec] [dec]
Failed to insert into the tree.

VCM EA: debug init failed

Internal error. The debugging logs will not

be activated. It should not hamper the
fuctionality though.

VCM_EA detected--> [chars]:[chars]

Internal error with error message.

IM Attribute Error : [chars] : [dec]

Error in IM(Interface Manager) Attribute

operation %s - Failure %s - Reason for the
failure

IM process down: [chars]

IM(Interface Manager) did not come up

before the timer expired

PVC creation Failed [chars] : [chars]

PVC creation got failed . We may get this

error if the connection with PVC does not
exist or not ready.

Connection to IM Failed :[chars] : [chars]

Error in IM(Interface Manager) operation.

We get this error if the connection with IM
does not exist or IM is not ready. This
happens on the LC with ATM/FR interfaces

DEBUG library initialization error: [chars].

System will automatically retry
initialization.

debug library initialization failed

Ltrace library initialization error: [chars].

System will automatically retry
initialization.

ltrace library initialization failed

[dec] interfaces failed to create. The first

interface to fail was [chars]. The system
will continue to retry.

Some interfaces failed to be created. The

system will keep retrying.

[dec] interfaces failed to replicate. The first

interface to fail was [chars]. The system
Some interfaces failed to be replicated. The
will continue to retry.
system will keep retrying.

Global SPP context shortage [chars]

Set: A global SPP context shortage was

detected in the VirtIO plug-in. Reception of
packets from ports and other nodes is likely
to stop at any point. Clear: A previous SPP
context shortage was cleared. Normal
packet I/O operations will resume.

Plug-in initialization failed: [chars]

The VirtIO SPP plug-in failed to initialize.

An error occurred during debug

initialization (error: [chars])

The VLAN NetIO component encoutered an

error during debug initialization. This is
likely to cause VLAN interface setup to fail.

Failed to generate a notification for the

Native VLAN (error: [chars])

The VLAN EA process encountered a

problem while trying to send a Native VLAN
change notification. Native VLAN support
for interfaces on the affected node may not
function correctly.

VLAN EA failed to register with the

statistics server (error: [chars])

The VLAN EA process encountered an error

while registering with the statistics server
process. No VLAN sub-interface statistics
will be gathered on the given linecard.

An error was received while waiting for an

event (error: [chars])

The VLAN EA process encountered an error

while listening for events. The process will
automatically restart and retry.

The VLAN EA process encountered an error

during resynchonization with the IMP
process. This error message either
indicates that the VLAN EA process never
received an end of replay message from
Errors during resynchronization with the IM IM, or it received an inconsistent dataset
infrastructure (error: [chars])
from IM.

The VLAN EA process failed to initialize.

The process will automatically restart and
VLAN EA initialization failed: [chars] (error: retry. Until it succeeds, VLAN functionality
[chars])
may not work on the affected node.

Out of memory (failed attempt to reserve

%zu bytes)

The VLAN EA process was not able to

allocate the memory that it needed to
complete the operation. VLAN functionality
on the affected node may be reduced until
the problem is resolved.

Failed to connect to IM, err: [chars]

The VLAN MA process failed to connect to

the IM server.

When the VLAN MA notices that it has lost

its connection to the L2PVN Manager
process, it needs to update its database to
The handling of a L2VPN Mgr disconnect
reflect this. This error message indicates
notification failed for [unsigned int] trunk
that this the update failed. The only
interface(s). The first failure was on [chars] expected scenario that could cause the
(with error: [chars])
error is a low memory condition.
Couldn't install the default handler for
async msgs, err: [chars]

The VLAN MA process couldn't install the

default event handler for async msgs.

An error was received while waiting for an

event on the [chars] (error: [chars])

The VLAN MA process encountered an error

while listening for events. The process will
automatically restart and retry.

The VLAN MA process failed to initialize.

Previous messages may give the reason.
The process will automatically restart and
VLAN MA initialization failed: [chars] (error: retry. Until it succeeds, VLAN functionality
[chars])
may not work on the affected node.

Failed to handle [chars] for [unsigned int]

interfaces ([unsigned int] failed, first failure
[chars], last failure [chars]), due to the
[chars] error: [chars]

The VLAN MA failed to resynchronize its

configuration with another component in
the system after an earlier failure, or
process restart.

Failed to handle [chars] for [chars], due to

the error: [chars]

The VLAN MA failed to resynchronize its

configuration with another component in
the system after an earlier failure, or
process restart.

Out of memory (failed attempt to reserve

%zu bytes)

The VLAN MA process was not able to

allocate the memory that it needed to
complete the operation. VLAN functionality
on the affected node may be reduced until
the problem is resolved.

A failure occurred while trying to determine

the maximum number of VLAN subinterfaces that can be supported on the
given node. The system may allow
Failed to determine the maximum number configuration of more VLAN sub-interfaces
of VLAN sub-interface that are allowed to
that can be supported, or may not allow
be configured on the given node (error:
the full number supported to be
[chars])
configured.

Initialization of SPA driver failed: [chars] :

reason = [chars] ; exiting...

SPA driver driver encountered the

annunciated error during the driver
initialization. The System Manager process
(sysmgr) will automatically respawn the
(vpa_1_oc192) process, up to a fixed
number of times the error is encountered,
to recover. If the problem continues,
sysmgr will trigger node reload. After a
certain number of node reloads, the shelf
manager will permanently shutdown the
node.

[chars] : reason = [chars]

SPA OC192 driver error messages

[chars] : reason = [chars]

SPA driver failed to obtain either its node ID

or extract rack/slot/instance information
(having obtained the node ID).

[chars]

fail to allocate memory

Optics module inserted into SPA in bay

[dec]

Optics module has inserted

Optics module removed from SPA in bay

[dec]

Optics module has removed

[chars] [dec] [chars]

Port deletion happened after the threshold

time.

[chars] [chars]

SPA OC192 debug message

[chars]
[chars]: bay = [dec] : [chars]

fails to init debug event manager fails to

provide its service
OC192VPA driver general info.

[chars]

Jacket process spawns the SPA process and

waits for the initialization to complete. But
initialization fails putting SPA into FAILED
state. As a part of the above, we find the
mesage Ltrace init failed message.

[chars]

Jacket process spawns the SPA process and

waits for the initialization to complete. But
initialization fails putting SPA into FAILED
state. As part of retry mechansim, the
above message is seen.

[chars]

The spa_ether_ctx context data cannot be

set.

[chars] [chars]

The Jacket failed to parse spa driver

arguments.

[chars]

The internal SPA MAC got out of sync. SW

needs to reset the device in order to clear
the issue

[chars] [dec]

Port deletion failed to complete within the

timeout period.

Failed to get MAC address for port [dec],

Interface assigned random MAC address.

PLIM driver was unable to get a MAC

address for the interface.

[chars] [dec] [chars]

Port deletion happened after the threshold

time.

[chars] [dec] [chars]\n

Internal error. SPA rules library debug

library initilization failed

Bridge domains [chars] and [chars], VPLSID conflict [chars]

'The VPLS ID conflict happens when a

configured VPLS-ID value of a ' 'bridge
domain equals to default value of VPLS-ID
of another bridge ' 'domain. The
consequent action in case of conflict ' 'is
that the bridge domain with default VPLSID remains in the ' 'state of 'NOT
Advertised'. '

Global SPP context shortage [chars]

Set: A global SPP context shortage was

detected in the VTIO plug-in. Reception of
packets from ports and other nodes is likely
to stop at any point. Clear: A previous SPP
context shortage was cleared. Normal
packet I/O operations will resume.

Plug-in initialization failed: [chars]

The VTIO SPP plug-in failed to initialize.

Failed to create port [chars]: [chars]. An

error occurred when requesting a file
descriptor from the EnXR Netserver. No
The VTIO SPP plug-in failed to create a port
packets will be sent or received on this port in its local database.
Receive thread exiting after failure to
The VTIO SPP plug-in failed when
interrupt main thread after [dec] attempts. attempting to communicate between
No more data will be read from ports
threads.

Plug-in inter-thread communcation failed.

No more data will be read from ports:
[chars]

The VTIO SPP plug-in failed when

attempting to communicate between
threads.

Plug-in found no ports to manage

The VTIO SPP plug-in found no ports to

manage. No packets will be sent/received
in SPP (except fabric loopback packets) on
this node.

Memory access Error: [chars]: Err=[dec]

A memory access error occurred in

programable switching engine (PSE) driver
which involves exiting the process. %s indicates the reason for the failure. %d - is
the decoded error reason.

Rx quiesce_wahoo failed\n

Failed to drain the RX Wahoo queue.

TX quiesce_wahoo failed\n

Failed to drain the TX Wahoo queue.

[chars] interrupt [chars]%s

This is an warning message in the

programable switching Engine driver to
indicate an operation during interrupt from
programmable switching engine (PSE). %s indicates the PSE (RX/TX) information is
about. %s - indicates the interrupt name.
%s - indicates the warning message.

Previous Count: [unsigned int], current

Count: [unsigned int].

This is an informational message when the

thread 20 count is incrementing. If it is
seen continuously, it indicates hardware
issue. Or else, it is safe to ignore. %u indicates previous thread 20 count. %u indicates current thread 20 count.

This is an informational message when the

Multicast is disabled on Rx or Tx engine
and all the multicast packets are dropped
due to this. Prev - Previous thread count.
Curr - Current thread count. Check the
values of the registers by using the
following commands on the engine: Rx:
show_wahoo -S rx -u
prep,regmem=proto_config Tx:
show_wahoo -S tx -u
imp,regmem=proto_config (Note:above
commands to be executed
carefully.Execute as it is as shown
above.Do not give Contr + C during
execution.It causes a PSE reload.) Sample
output: ksh-LC>show_wahoo -S tx -u
imp,regmem=proto_config proto_config
@0x73: 3 (0x3) Interpretation:
Proto_config: 3 (both ipv4 and ipv6 mcasts
are enabled) Proto_config: 2 (Only Ipv4
mcast is disabled) Proto_config: 1 (Only
Ipv6 mcast is disabled) Proto_config: 0
(both Ipv4 and Ipv6 mcasts are disabled)
The log messages will be printed every 1
minute in case the thread counter
Ipmc disable: Rx Ipv4: Prev [unsigned
increments. To Enable or Disable the
int],curr [unsigned int]::Rx Ipv6: Prev
message logging by using the following
[unsigned int],curr [unsigned int]:: Tx Ipv4: command on the LC: Enable: show_wahoo
Prev [unsigned int],curr [unsigned int]::Tx -k on Disable: show_wahoo -k off Show:
IPv6: Prev [unsigned int],curr [unsigned int] show_wahoo -k show

[chars] [chars] [chars]: [hex]

This is an informational message in the

programable switching Engine driver to
indicate an operation. %s - indicates the
PSE (RX/TX) information is about. %s indicates the pipeline (0-3) information is
about. %s - indicates the information
message. %x - indicates the register value.

[chars] Interrupt detected - PIPE[dec]:

[hex]: FSRAM SBE detected at addr: [hex]:
FSRAM single bit error corrected.

This is an informational message in the

programable switching Engine driver to
indicate the SBE detected and corrected.
%s - indicates the PSE (RX/TX) information
is about. %d - indicates the pipeline (0-3)
information is about. %x - indicates the
register value. %x - indicates the erroneous
fsram location

[chars]

This is an informational message in the

programable switching Engine driver to
indicate an operation during interrupt from
programmable switching engine (PSE). %s indicates the PSE (RX/TX) information is
about. %s - indicates the information
message.

WahooStats-Info: [chars]

This is an informational message in the

stats collection logic of hfa_main.

Pipe stuck error: [chars]: Err=[dec]

An error occurred in programable switching

engine (PSE) driver during pausing and
resuming the pipe in PSE. %s - indicates
the reason for the failure. %d - is the
decoded error reason.

This is a debug message to display PAIR

\n[chars] [chars] PAIR's PCR register status PCR registers of programable switching
for pipe [dec]: [hex]
engine (PSE).

\n[chars] [chars] PAIR registers for pipe

[dec]:pcr [hex] plu_pirl [hex] pirm1 [hex]\n
pirm2 [hex] pirh [hex] mpls_label [hex]
mpls_info [hex]\n ip_header [hex] l4_port
[hex] start_adr [hex] msq_info [hex]\n ltr
[hex] tlu_force [hex] pre_cam_prof [hex]
lbl1_lo [hex]\n lbl1_hi [hex] lbl2_lo [hex]
lbl2_hi [hex] leaf1_word1 [hex]\n
leaf1_word2 [hex] leaf1_word3 [hex]
leaf1_word4 [hex] leaf2_word1 [hex]\n
leaf2_word2 [hex] leaf2_word3 [hex]
leaf2_word4 [hex] tcam_cont [hex]\n
ipv4/v6_dst_1 [hex] ipv4/v6_dst_2 [hex]
ipv4/v6_dst_3 [hex] ipv4/v6_dst_4 [hex]\n
ipv4/v6_src_1 [hex] ipv4/v6_src_2 [hex]
ipv4/v6_src_3 [hex] ipv4/v6_src_4 [hex]\n This is a debug message to display PAIR
mcast_info [hex] ipv6_info [hex] msq_data registers of programable switching engine
[hex]
(PSE).

\n[chars] [chars] PAIR registers for pipe

[dec]:pcr [hex] plu_pirl [hex] pirm1 [hex]\n
pirm2 [hex] pirh [hex] mpls_label [hex]
mpls_info [hex]\n ip_header [hex] l4_port
[hex] start_adr [hex] msq_info [hex]\n ltr
[hex] tlu_force [hex] pre_cam_prof [hex]
lbl1_lo [hex]\n lbl1_hi [hex] lbl2_lo [hex]
lbl2_hi [hex] leaf1_word1 [hex]\n
leaf1_word2 [hex] leaf1_word3 [hex]
leaf1_word4 [hex] leaf2_word1 [hex]\n
This is a debug message to display PAIR
leaf2_word2 [hex] leaf2_word3 [hex]
registers list of programable switching
leaf2_word4 [hex] cam_cont [hex]
engine (PSE).

\n[hex]: [hex] [hex] [hex] [hex]

This is a debug message to display PHB

dump of programable switching engine
(PSE).

[hex] \n p0_pop_int_status [hex]

p1_pop_int_status [hex] p2_pop_int_status
[hex] p3_pop_int_status [hex]\n p0_pop_pc
[hex] p1_pop_pc [hex] p2_pop_pc [hex]
p3_pop_pc [hex]\n p0_ppc_ctl [hex]
p1_ppc_ctl [hex] p2_ppc_ctl [hex]
p3_ppc_ctl [hex]\n p0_pl_aa_pak_avl_1_reg
[hex] p1_pl_aa_pak_avl_1_reg [hex]
p2_pl_aa_pak_avl_1_reg [hex]
p3_pl_aa_pak_avl_1_reg [hex]\n
p0_pl_aa_end_reg [hex] p1_pl_aa_end_reg
[hex] p2_pl_aa_end_reg [hex]
p3_pl_aa_end_reg [hex]\n
p0_pl_aa_fatal_err_reg [hex]
p1_pl_aa_fatal_err_reg [hex]
p2_pl_aa_fatal_err_reg [hex]
p3_pl_aa_fatal_err_reg [hex]\n
p0_gather_int_stat_reg [hex]
p1_gather_int_stat_reg [hex]
p2_gather_int_stat_reg [hex]
p3_gather_int_stat_reg [hex]\n xbm_err_reg
[hex] ftc_status_reg [hex]
ffc_status_error_reg [hex]\n
ffc_ecc_err_add_reg [hex]
ffc_ecc_err_msb_data_reg [hex]
ffc_ecc_err_lsb_data_reg [hex]\n
ffc_invalid_address_err_reg [hex]
ffc_fcram_addr_err_agent_reg [hex]\n
fsr_invalid_addr_err_reg [hex]
fsr_controller_err_reg [hex]\n
This is a debug message to display
csc_status_reg [hex] cam_status_reg [hex] registers of programable switching engine
nfc_status_reg [hex]\n
(PSE).

failed to initialize: [chars]

During process start up an unrecoverable

error occurred. The component will exit and
should be restarted by the System
Manager.

config error, [chars][[dec]]: [chars]

A configuration update has caused a

problem inside the InARP code - InARP
should continue but may have ignored the
latest config change

possibly unable to allocate [dec] bytes of

memory

The system is low on memory and not

enough was available to complete the
request

recieved an unknown event: [dec]

The system must be sending messages we

didn't register for. They will be ignored.

The fsm state ([dec]) is invalid

The FSM has got into an invalid state

recieved information about an

unrecognised interface

A set of IDBs are kept with information on

each interface. Somehow this information
has become inconsistent with the system.

The type ([dec]) of this IDB is invalid

Information about InARP interfaces has

become corrupted.

The if state ([dec]) is not handled

There is no action assigned to the if state

change, and so nothing has been done
when it was received.

The IDB is not in synch with the vc-class

information

A set of IDBs are kept with information on

each FR interface. A set of VC-CLASSes are
also kept and associated with the IDBs.
Somehow this information has become
inconsistent.

failed lookup of interface: [chars]

The system must be sending messages we

didn't register for. They will be ignored.

unable to allocate [dec] bytes of memory

The system is low on memory and not

enough was available to complete the
request

unknown idb type: [dec]

If IDB type will not be find out in subtree

recursively i.e.it will iterate on each nonleaf child untill all leaves in subtree have
been visited. If this IDB type does not
recognised that means it is not a leaf , not
a root and not a node.

unable to allocate [dec] bytes of memory

The system is low on memory and not

enough was available to complete the
request

unknown idb type: [dec]

The IDB type of this IDB is not recognised.

interface: [chars], alarm: [chars], status:

[chars]

The specified WANPHY Alarm has been

declared or released. interface: interface
on which alarm is set/cleared alarm: alarm
being asserted e.g: SF-BER or SD-BER
status: set/cleared

Failed to [chars] ([chars])

An Error occurred during initialization of

process start up. The process will exit and
should be restarted by the System
Manager which should recover the
situation.

Failed to allocate [unsigned int] bytes for

'[chars]'

The process failed to allocate memory for

the specified resource.

After detecting an error with the connection

to the specified service, IPHC PROFILE MGR
failed to reset that connection. This is an
internal error. It requires a restart of the
Error resetting '[chars]' connection: [chars] process for recovery.

[chars] [chars]

printing the iphc ma info.

IPHC PROFILE MANAGER failed to [chars].

[chars]

During process start up an unrecoverable

error occurred. The process will exit and
should be restarted by the System
Manager which should recover the
situation.

Memory allocation failed: [chars]

The process failed to allocate memory for

the specified resource.

IPv6 ND LITE send async pulse to ipv6 nd

lite process fails; Error [chars]

'IPv6 ND LITE Attempts to send pulse to

IPV6 ND lite process fails'

IPv6 ND LITE cannot connect to ipv6 nd lite 'IPv6 ND LITE attempts to connect to ipv6
process; Error [chars]
nd lite process channel fails'

IPV6 ND Lite self generated fun: [chars]:

line: [dec]

'IPv6 ND Lite process attempts to

create/remove/lmit exceed caused the
shared memory to failed.'

IPV6 ND lite SHMEM can accommodate only 'IPV6 ND has requested transfer of more
[dec] global IP records (request for [dec]
global IP records than shared memory can
records [dec] )
accommodate'

IPv6 ND LITE cannot mmap file [chars];

Error [chars]

'IPv6 ND LITE attempts to mmap the shared

memory fails'

IPv6 ND LITE cannot munmap file [chars];

Error [chars]

'IPv6 ND LITE attempts to munmap the

shared memory fails'

IPv6 ND LITE cannot open shmem file

[chars]; Error [chars]

'IPv6 ND LITE attempts to open the shared

memory fails'

IPv6 ND LITE cannot truncate file [chars] to 'IPv6 ND LITE attempts to truncate the
[dec] bytes; Error [chars]
shared memory file fails.'

IPV6 ND lite SHMEM can accommodate only 'IPV6 ND has requested transfer of more
[dec] records (request for [dec] records
interface records than shared memory can
[dec] )
accommodate'

IPv6 ND LITE cannot unlink file [chars];

Error [chars]

'IPv6 ND LITE attempt to unlink the shared

memory fails'

[chars]: [chars] - [chars]

An internal software error occurred that

prevented Route proxy from working
properly.

Failure occured during the initialization of

[chars] [chars] Initialization failed - Reason route proxy component Logs the reason for
[chars]
failure. Process would restart again.

shared memory failed during [chars]:

[chars]

An internal software error occurred that

prevented Route proxy from working
properly with shared memory.

[chars]

Error messages from virtualization

manager client library.

[chars]

Notice messages from virtualization

manager client library.

[chars]

Info messages from virtualization manager

client library.

[chars]

Debug messages from virtualization

manager client library.

The replicator library got an error back

from NRS indicating that the data handle is
no longer valid. This handle would have
been validated on initialisation, so the
likely cause of this error is memory
Handle name ([chars]) has been corrupted. corruption. The client process will be
rc: [hex] ([chars])
forcibly restarted to try to recover.

The replicator has repeatedly failed to

complete IDT for a system data handle.
There may be problems with
Failed to complete IDT after several retries: communications or other low-level
rc [hex] ([chars])
infrastructure.

Large item handle detected ([hex]/[hex])

The replicator library has received an

exceptionally large item handle from NRS
which may cause conflicts within the
replicator library.

Failed to acquire data handle after several

retries: rc [hex] ([chars])

The replicator has repeatedly failed to

acquire ownership of a system data handle.
The client process may need restarting.

A corrupted peristent data structure was

discovered ([chars])

The replicator library discovered a bad

magic number in a persistent data
structure. This suggests that the data has
been corrupted. The replicator library will
attempt to recover the situation.

The replicator library was unable to access

an internal structure. This may result in
Could not access [chars] context structure: failure of data replication to the standby
rc [hex] ([chars])
node(s).

[chars]: rc [hex] ([chars])

The replicator library has either failed a

function that expected to succeed, or has
got into an inconsistent state.

Failed to [chars] [chars]. Error [dec]

([chars])

The replicator library has either failed to

aquire or release a lock.

Failed to malloc %zu bytes

The replicator has failed to acquire the

required amount of memory.

No completion notification received for

update message [unsigned int]

The replicator library did not receive a

callback from the transport library. The
update will be allowed to continue without
the replication acknowledgement. If any
replicas have not received the update, they
will resync on the next update.

Failed to send update: rc [hex] ([chars])

An error was returned from RDS when

trying to send an update. Clients will
handle this condition differently either by
retrying later, or failing the operation. If
this condition persists, data may be lost on
failover.

Failed to apply [chars] update: rc [hex]

([chars])

The client returned an error when trying to

apply an update. The replicator library will
try to recover by requesting a replay of the
update. If this condition persists, data may
be lost on failover.

Failed to acquire data handle: rc [hex]

([chars])

The replicator has failed to acquire

ownership of a system data handle.

[dec] VRF(s) are configured without a valid

license / license configuration for [chars] in
violation of the Software Right To Use
Agreement. This feature may be disabled
by the system without the appropriate
license. Contact Cisco to purchase the
license immediately to avoid potential
The VRF feature is configured without the
service interruption.\n
necessary Adv-IP license.

[dec] VRF(s) are configured without a valid

license / license configuration for [chars] in
violation of the Software Right To Use
Agreement. This feature may be disabled
by the system without the appropriate
license. Contact Cisco to purchase the
license immediately to avoid potential
The VRF feature is configured without the
service interruption.\n
necessary iVRF license.

G.709 feature is configured without a valid

license / license configuration for [chars] in
violation of the Software Right To Use
Agreement. This feature may be disabled
by the system without the appropriate
license. Contact Cisco to purchase the
license immediately to avoid potential
The G.709 feature is configured without the
service interruption.\n
necessary license.

VidMon feature is configured without a

valid license / license configuration for
[chars] in violation of the Software Right To
Use Agreement. This feature may be
disabled by the system without the
appropriate license. Contact Cisco to
purchase the license immediately to avoid The VidMon feature is configured without
potential service interruption.\n
the necessary license.

[chars], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

gsr_lclm_show: [chars] , [chars]

GSR_LCLM_SHOW encountered an error

Booster Lic:acquired already [chars]

This error indicates that the license is

already acquired.

Booster Lic:default fail[chars]

This error indicates the failure is due to

default case.

Booster Lic:Too few licenses[chars]

This error indicates that there are only few

licenses left.

Booster Lic:handle exists[chars]

This error indicates that the handle exists

already.

Booster Lic:no feature[chars]

This error indicates that there are no such

feature.

gsr_lclm: [chars] , [chars]

The GSR Line Card Licensing Manager has

encountered an error

The system is unable to authenticate the

line card rate mode in node: [chars]

The system has aborted the rate mode

verification due to an operation error. This
message indicates that an error has
occurred during the authentication process
itself, the process is incomplete. Therefore,
we do not know if the line card is a genuine
Cisco product or not. This could indicate a
problem with the linecard hardware and
warrants further investigation.

\n WARNING!!! The module in node [chars]

in this router may not be a genuine Cisco
product. Cisco warranties and support
programs only apply to genuine Cisco
products. If Cisco determines that your
insertion of non-Cisco memory, WIC cards,
AIM cards, Network Modules, SPA cards,
GBICs or other modules into a Cisco
product is the cause of a support issue,
Cisco may deny support under your
warranty or under a Cisco support program
such as SmartNet.

This line card has failed to pass the board

authentication. The warning message is
generated frequently but the operation of
the linecard is not disabled in any way.

The Linecard Licensing Manager was not

able to acquire a throughput license. Traffic
flow through this router may be impacted
Not able to acquire a throughput license for since the a line card is not operating at the
node [chars]
expected throughput rate.

The throughput rate for node [chars] has

[chars] to [chars]

The throughput rate of the specified node

has changed. Traffic flow through this
router will be impacted since the line card
is now operating at a new throughput rate.

Licensing command argments lack

([chars]) [[dec]]

The parameters that liccmd recive args

from parser is lack.

Licensing command library could not

initialize tracing ([chars]) [[dec]]

The license command library could not

initialize internal tracing used for technical
support.

Error creating license management

directory: [chars]

The license manager encountered an error

condition while attempting to create a
directory for storing license information.
Check the error string to determine what
has happened.

The disk utilities library did not return a

device name to license manager where the
persistent license data files can be stored.
License information will be stored in a
temporary location, and will be lost if the
router reloads. Implicit licenses will be
available. Permanent or evaluation licenses
Could not determine device to use for
should not be installed in this state, as they
license database. Reverting to temporary will be lost if the router reloads and will
storage. License data will not persist across need to be regenerated before they can be
reloads.
installed again.

Licensing client library could not initialize

tracing ([chars]) [[dec]]

The license client library could not initialize

internal tracing used for technical support.

License management directory created

The license manager created a directory to

store license information. Normally this will
occur after the disk holding the license
information has been formatted or
replaced, or on first boot of a new system.

License database and this chassis do not

match. If licenses were installed, restore
from a backup or contact Cisco TAC.

The message displays the result of

comparing the license database to the
current state of the chassis. If the chassis
and license database do not match, the
license database will be cleared and
implicit evaluation licenses will be available
for 90 days. This alarm may occur if the
route processor card has been moved from
one chassis to another.

License database has been corrupted and

will be cleared

This message occurs when the license

manager detects corruption in the license
database that cannot be repaired. The
license database will be cleared and
implicit evaluation licenses will be available
for 90 days.

Error saving license database: [chars]

The license manager encountered an error

condition while saving the license
database.This is a error while writing a file
on disk . Licmgr will retrying writing the file
to disk . Check the error string to
determine what has happened.

License manager encounted a fatal error

condition and is exiting: [chars] ([hex])

The license manager encountered a error

condition during intialization this could
happen due to platform service
initialization error like EVM service failed
,trace server init failure etc . All these are
unlikely failure but if it occur it could be
resolved during restart of licmgr process .

The license manager encountered a error

condition while initializing. The condition
where the error occur is failure in setting
up event Handler of eventing IPC , other is
failure in adopting the Role state of Dsc or
License manager could not initialize: Error \ non-Dsc. The restart of licmgr or node
[chars]\ while [chars]
reload should likely resolve the issue.

Could not read chassis serial number:

[chars]

The license manager encountered an error

while attempting to read the chassis serial
number. Without a valid chassis serial
number the license manager will not be
able to support licenses locked to the
affected chassis. Check the error string to
determine what has happened.

The current system opid mismatched with

Local Opid: [dec], Opid in file: [dec], [chars] the restoration license opid.

Problem found during audit [chars] -[chars]

The license manager encountered a

problem during an internal audit. Check the
error string to determine what has
happened.

Problem with datastore [chars] -- [chars]

The license manager encountered a

problem attempting to adjust licenses in
the given datastore. Check the error string
to determine what has happened.

License manager event processing error:

[chars]

The license manager encountered an error

condition while processing an event. Check
the error string to determine what has
happened.

The ninety day implicit license period has

expired.

The period after initial boot during which

licensed features can be used without
licenses has ended. Licensed features
without licenses will cease to operate and
cannot be configured. The message will
appear even if there are no licensed
features configured without licenses at the
time.

An implicit license has been used for the

[chars] feature.

A feature which has no license has been

enabled because the system is still in the
implicit license period, during which
licensed features may be used without
licenses. When the implicit license period
ends the feature will be deactivated unless
a license has been installed.

The implicit license period will end in

[chars]. Contact Cisco if you wish to
purchase permanent licenses.

The period after initial boot during which

licensed features can be used without
licenses will end in the indicated time.
Licensed features without licenses will
cease to operate and cannot be configured
after that time. The message will appear
every day during the implicit license
period, even if there are no licensed
features configured without licenses.

Evaluation license for feature [chars] has

expired

The specified feature's evaluation license

has expired. The feature will no longer be
usable. The message appears even if the
feature is not currently configured.

Problem with licenses from license file

[chars]: [chars]

The license manager encountered an error

attempting to install or remove the licenses
in the given license file. Check the error
string to determine what has happened.

The license database contained a license

pool definition for an SDR that does not
exist. The licenses assigned to this pool
Removed license pool for nonexistant SDR were automatically moved back into the
[chars]
Owner pool.

Licenses for feature [chars] with chassis

serial number [chars] has expired

Licenses for the specified feature which

were installed using the given chassis
serial number have been removed due to
the chassis having been disconnected from
the system. This message appears even if
the removed licenses were not active.

Licenses for feature [chars] with serial

number [chars] will expire in [chars]

Licenses for the specified feature which

were installed using the given chassis
serial number will be removed in the time
indicated unless the chassis is reconnected
from the system. This message appears
even if the removed licenses are not
active.

The specified feature's evaluation license

will expire in the time indicated. After the
Evaluation license for feature [chars] will
license has expired the feature will become
expire in [chars]. Contact Cisco if you wish unusable. This message appears even if
to purchase a permanent license.
the feature is not currently configured.

Could not read operation ID: [chars]

The license manager encountered an error

while attempting to read the license
operation ID. Without a valid license
operation ID the license manager will not
be able to support licenses locked to the
affected chassis. Check the error string to
determine what has happened.

Package [chars] activated on Rack[chars]

and node [chars] without a valid license/
valid configuration

The package exists without a valid license

Feature associated to package [chars]

configured on node [chars] without a valid A feature configuration was done on a
license
location without a valid license

Unable to access the system database,

error: [chars]

An error occurred when accessing the

system database. This a system level issue
and possible issue from licmgr side could
be invalid registration with sysdb.

Registration with SysDB failed [[chars]],

error: [chars]

An error occurred when registering with the

system database

[unsigned int] features cleared

As a result of 'clear license' command

execution, license features installed on this
system were cleared.

There are no features to be cleared

The 'clear license' command was executed,

but there are no feature licenses installed
to be cleared on this system.

There are no license pools to be cleared

The 'clear license' command was executed,

but there are no pools to be cleared on this
system.

As a result of 'clear license' command

[unsigned int] license pools cleared (Owner execution, license pools other than the
pool still exists).
Owner pool were cleared.

Loading license file [chars]

The license manager is about to open the

named license file to add licenses to the
system.

All licenses from license file [chars] added

successfully

The license manager has installed all the

licenses in the named license file to the
system.

Opening license backup file [chars]

The license manager is about to open the

named license backup file to show license
backup to the user.

License client \[chars]\ failed to respond

A license client program failed to respond.

This may be due to some inter-process
communications problem, or because the
client process is blocked.

Due to a loss of inter-process

An active [chars] license was reclaimed by communications the license manager had
the license manager and moved to
to reclaim a license that was not properly
allocated state on node [chars]
released.

Process initialization failed: ([chars])

Performance Route Processor (PRP)

Bootflash drivers failed to initialize. The
booflash is a storage device that exists on
every PRP. The effect is that PRP storage
will not function. %s - indicates the reason
for the failure.

Unexpected init error: [chars]: [chars]:

[hex]

An unexpected initialization error condition

encountered. System backup utility may
not work properly

Unexpected init warning: [chars]: [chars]:

[hex]

An unexpected initialization problem

condition encountered. It will not affect
system backup but may lose some debug
information.

Can't open device [chars]

Flash device could not be opened

[chars]: invalid option [char]

Bad options

[chars]: Can't Attach Pathname \[chars]\

Could not attach pathname

[chars]: Illegal permission requested ([dec]) Not a valid permission

[chars]: Can not access flash device

Probably the flash card has been removed.

Could not [chars] condition variable : Error

[chars]
Possibly condition variable does not exist

Flash driver unavailable

Flash device driver process is dead.

Flash device initialization failed. Error:

[chars]

Something wen't wrong.

Could not [chars] mutex : Error [chars]

Possibly mutex does not exist

[chars]: Bank Status Error. Shutting down

device

Bad device data

Could not start the thread to wait for driver

after driver crash
Could not start a thread.

[chars]: resmgr_pulse_attach failed: [text]

Could not attach pulse for flash driver

death detection

Could not start the [chars] thread

Could not start a thread.

[chars]: The flash card seems to be

corrupted

Probably the flash card is corrupted

[chars]: can't create channel

Could not create channel for the resource

manager

[chars]: [chars] [chars] Could not open DLL DLL Probably not Loaded

[chars]: [chars] [chars] Can't Resolve

symbol

Proabaly Function not Defined in DLL

[chars]: Hdr Error, ptr=[hex]

A file with a bad header encountered on

flash

[chars]: Bank Status Error. Shutting down

device

Either device is in error or file system

format can not be recognized.

WARNING! [chars] is corrupted. Suggestion:

reformat the device and copy the required The bootflash: is corrupted. Need to reboot files to it.
format it and copy boot files to it.

Could not establish connected to channel

[dec]

Could not create channel for the resource

manager

[chars]

Internal error

Underyling flash card seems to have

changed. Closing file

Probably the driver died or the flash card

has been swapped (OIR). The flash card
has changed. The current access seems to
be for a file which has been opened with
the driver for old card.

event_block failed -[chars]

--

[chars]: can't create channel-[chars]

Could not create channel for the event

manager

can't connect to configuration, [chars]

Flash debugging service register to sysdb

failed.

Flash device could not recover from

interrupted sqeeze. Error: [dec]

Something wen't wrong.

[chars]: unable to export mount point

([chars])

Device will not be accessible from all

nodes.

sysmgr_proc_ready failed - [chars]

Failed to send message to Sysmgr about

init completion.

Could not register a pulse with the driver

Sector [unsigned long int] not erased

We register pulse with the driver so that we

get notification of certain events. For some
reason it did not work.
Bad sector

[chars]: The flash card is write protected

The card is write protected, and a write

operation is attempted

Could not get exclusive access to the

device

Possibly a read or write is still going on in

the background

Unknown pulse received. Code: [dec],

Value [dec]:

An unexpected pulse has been received

[chars]: The flash card has been swapped

(OIR)

The pcmcia flash card has been pulled out

from its slot and re-inserted with a same or
different card

Flash driver [chars] back up

Flash device driver process came back up.

Squeeze is used to recover space

consumed by deleted files in flash file
systems. A deleted file is just marked
deleted and space occupied by it is not
recovered till a squeeze is done. The flash
card has been ejected or router crashed in
Flash device [chars] trying to recover from while performing squeeze. We are trying to
interrupted squeeze. Please wait
recover from that.

Flash device [chars] recovered from

interrupted squeeze

Squeeze is used to recover space

consumed by deleted files in flash file
systems. A deleted file is just marked
deleted and space occupied by it is not
recovered till a squeeze is done. The flash
card has been ejected or router crashed in
while performing squeeze. We are able to
succesfully recover from that and flash is
usable again.

[chars]: Usage -m <mount_point> -d

<device_name>

Arguments for invoking the flash file

system. <mount_point> is the mount
location of the flash file system and
<device_name> is the path name of the
driver to be used by the file system. Wrong
arguments have been used. Please use the
correct ones.

Failed to unregister the debug's

During total cleanup fs_dev_info failed to

unregister the debugs.

[chars], Error: [chars]

Failed in some event management

functions.

[chars], Error: [chars]

Failed to execute some LWM library

functions.

Initialization in main failed, Error: [chars]

One of the functions called during

initialization of the process failed.

Failed in allocating memory, [chars]

Not enough memory available in the

system.

Could not register [chars]

Failed to register Error description DLL.

[chars], Error: [chars]

Some signal related function returned with

an error.

Could not inform sysmgr that process is

ready, Error: [chars]

The main function failed to inform sysmgr

that it is ready.

[chars], Error: [chars]

One of the pthread_* functions returned

with an error.

Invalid parameter [chars]=[dec]

An invalid parameter value was passed to

the named function.

An application is passing an invalid

Invalid application type parameter [dec] in application type parameter to get the
storage media get request
storage media

Unable to read file '[chars]', errno=[dec].

Using default boot device.

The qsm application device file was

unavailable. Default boot device will be
used.

unknown machine

To derive the MODULE TYPE get the

hardware board type ,the module processor
type and revision number of the board and
of the module.
PLATFORM_GET_HW_BOARD_TYPE_REVISIO
N fails when it unable to find the machine
type.

[dec] not supported

GET_PROCESS_MODULE derives the

module type from the Board type. Unable
to get the Board_type, hence unsupported
Board type.

Can't Create Channel

Could not create channel for the resource

manager

Can't Attach Pathname [chars]

Could not attach pathname

%Error: verify @ [hex]-expected [hex], read

[hex]
Verify information due to verbose option

Process initialization failed: ([chars])

MBUS flash drivers failed to initialize. The

MBUS flash is a storage device that exists
on board and is used to store On Board
Failure Logs. The effect is that OBFL
storage will not function. %s - indicates the
reason for the failure.

File '[chars]' is corrupted . Error - [chars]

The specified File is corrupted on Primary

Boot Device.

Media driver is adding the device with

invalid parameter [chars]=0x%zx

An invalid parameter value was passed to

media driver when a media device is
inserted

Media Driver is started with invalid

parameter [chars]=0x%zx

An invalid parameter value was passed to

start the media driver.

Redundancy FS got an invalid parameter

RedFS got an invalid parameter [chars]=0x value when Redundancy FS mirroring was
%zx when enabling REDFS mirroring
being configured

Unable to channel connect to '[chars]',

errno=[dec]:[chars].

The media server channel specified could

not be opened for the specified reason.

File System type ([chars]) is not supported File system type is not supported on the
for '[chars]'
media device.
An invalid parameter value was passed to
Media driver is trying to remove the device the media driver when the media is
with invalid parameter [chars]=0x%zx
removed.

Media driver exits with invalid parameter

[chars]=0x%zx

An invalid parameter value was passed to

the media driver when it exits.

Device partition is requested to be

formatted with an invalid parameter
[chars]=0x%zx

An invalid parameter value was passed to

the driver to format and partition the
media device.

Redundancy FS got an invalid parameter

RedFS got an invalid parameter [chars]=0x value when Redundancy FS mirroring was
%zx when disabling REDFS mirroring
being unconfigured

Redundancy FS got an invalid parameter

RedFS got an invalid parameter [chars]=0x value when RedFS was trying to recover
%zx during REDFS media recovery
from storage media issue

RedFS got an invalid parameter [chars]=0x Redundancy FS got an invalid parameter

%zx when REDFS was partitioning the
value when Redundancy FS was
media for mirroring
partitioning the media for mirroring
Redundancy FS got an invalid parameter
Media redFS got an invalid parameter
value when Redundancy FS was quering
[chars]=0x%zx when querying the storage the media partition information from the
media
device.
Application reported storage device
problem but with invalid parameter
[chars]=0x%zx

Application reported storage device

problem but with invalid parameter shown

Unable to send message to media server,

operation=[dec], errno=[dec]:[chars].

The message sent to the media server

failed for the specified operation number
and failed for the specified reason.

Unexpected init error: [chars]: [chars]:

[hex]

An unexpected init error condition

encountered.

Unexpected sysdb error: [chars]: [chars]:

[hex]

An unexpected sysdb error condition

encountered.

Boot media storage device [chars]

unavailable. Reloading node.

The media storage device specified is the

boot device and is unavailable. The
software will not be able to continue
functioning without the boot device so the
node is reset to failover or recover the
failed device.

File '[chars]' is corrupted . Error - [chars]

The specified File is corrupted on Primary

Boot Device.

Mediasvr Unexpected init error: [chars]:

[chars]: [hex]

Media server is unable to initialize itself.

Media server will exit and retry.

Media storage device [chars] corrupted

beyond repair. Check fsck log at [chars]

The media storage card specified was

corrupted beyond repair. See log file for
specific reason.

Media storage device [chars] failed to exit

properly due to [chars]. Error=[hex]
([chars])

The media storage card specified failed to

exit properly due to the specified reason.
The returned error code is specified.

Media storage device [chars] failed to be

formatted due to [chars]. Error=[hex]
([chars])

The media storage card failed to be

formatted due the specified reason. The
returned error code is specified.

The media storage card specified failed to

Media storage device [chars] failed to
mount due to the specified operation. The
mount due to [chars]. Error=[hex]([chars]) returned error code is specified.
The media storage device specified is
Media storage device [chars] is formatted formatted with a different file system type
as [chars] when software expects it to be
than expected. The running software
formatted as [chars]. Please use device file version expects the device to contain a
system upgrade procedure to fix.
different file system tye.

Mediasvr Unexpected init error: [chars]:

[chars]: [hex]

An unexpected init error condition

encountered when retrieving rommon boot
setup

Mediasvr unable to set up ltrace with error: Media server is unable to initialize the
[chars]: [chars]: [hex]
ltrace buffer for logging.

Mediasvr unexpected media device path

error: [chars]: [chars]: [hex]

An unexpected media device error

condition encountered during booting up
from media

Could not update nvram (Error=[hex]).

The access to the nvram failed, so that

format operation was rejected.

Media storage device [chars] was

The media storage card specified was
formatted due to corruption. Check fsck log corrupted beyond repair and was
at [chars]
formatted. See log file for specific reason.
The media storage card specified is
inconsistent between the partition table
Media storage device [chars] was detected and the file system format. This
as inconsistent. Device will be auto
inconsistency needs to be corrected and
formatted.
the contents formatted correctly.
The media storage card specified has some
Media storage device [chars] was repaired. inconsitencies in the filesystem and was
Check fsck log at [chars]
repaired. See log file for specific reason.
Media storage device [chars] was detected The media storage card specified is
as unformatted. Device will be auto
unformatted. There are problems with the
formatted.
boot sector contents.

Media storage device [chars] will be

(un)partitioned because '[chars]'.

The media storage card specified is going

to be (un)partitioned due to the specified
reason.

Media storage boot device [chars] was

requested to format. Node will reload and
device will be formatted while next boot.

The media storage card specified was

requested to format and will be formatted
through the reload.

Media storage device [chars] was

The media storage card specified was
formatted due to request. Check fsck log at requested to format and was formatted.
[chars]
See log file for specific reason.

Format is requested for [chars]

[chars],filesystem '[chars]'.

The media storage card specified was

requested to format with printed options.

Harddisk mirroring not enabled on this

node. Partition '[chars]' doesnot exist.

The harddisk partition name by provided by

platform does not exist.

[chars] has unknown value '[chars]', it will

be ignored.

The ROMMON variable for format option is

unknown, so that format operation will not
happen.

The ROMMON variable for format option is

[chars] has unsupported value '[chars]' for unsupported, so that format operation will
'[chars]', it will be ignored.
not happen.
nvram is corrupt - textptr: [hex], textsize:
[dec], textbase: [hex], chksum in nvram:
[dec], newchksum: [dec], oldchksum: [dec] nvram corrupt.

Unexpected version of classic configuration

memory ([dec]). Please save contents of
nvram by using classic image, and format
nvram to recover. Please rewrite the config
if need to use classic configs. If not, no
Classic configuration different version than
further action is required.
expected

Couldn't uncompress config ([dec])

Decompress of Compressed Classic Config

Failed

Bad classic configuration memory structure

([chars]:[dec])
Nvptr corrupted

Error while logging nvram activity: [[chars]] Error while logging nvram activity

Previously due to some error, NVRAM dump

file was collected. At the time of collection,
permanent storage was not available so it
was saved at /tmp directory. NVRAM
process tried to move this file out to
permanent storage but it failed. This file
NVRAM dump file was not moved out of
maybe required to identify if there is real
'[chars]' to '[chars]' ([chars]:[dec]:[chars]). issue with NVRAM device. Collect dump file
Please collect file from /tmp before reload from /tmp directory for further inspection.

A write to the nvram was aborted

A Write to nvram was aborted.

NVRAM dump file was moved from [chars]

to [chars]

Previously due to some error, NVRAM dump

file was collected. At the time of collection,
permanent storage was not available so it
was saved at /tmp directory. To avoid the
loss of this file, this file was copied out
from /tmp directory when permanent
storage became available

Warning: NVRAM size is 0

Possible error during sizing nvram, the

NVRAM may not exist

Warning: NVRAM size is 0

Possible error during sizing nvram, the

NVRAM may not exist

Warning: NVRAM size is 0

Possible error during sizing nvram, the

NVRAM may not exist

Could not map nvram - [chars]

Mapping of Nvram Failed

Could not map nvram - [chars]

Mapping of Nvram Failed

Could not map Nvram

Mapping of Nvram Failed. The cause could

be limited physical memory or other
unknown reasons. This does not have any
impact on the router functionalities.

Could not map nvram - [chars]

Mapping of Nvram Failed

ROMMON variable-value pair: [chars],

contains illegal (non-printable)characters

The value of a ROMMON variable contains

illegal character. It is corrupted with
unknown reasons. This does not have any
impact on router functionalities.

NVRAM low battery detected, battery

needs to be replaced

Detect NVRAM low battery state, the data

stored in NVRAM may be destroyed after
power down the board with battery low
state.

NVRAM low battery detected, battery

needs to be replaced

Detect NVRAM low battery state, the data

stored in NVRAM may be lost after power
down the board with battery backup in low
state.

NVRAM low battery detected, battery

needs to be replaced

Detect NVRAM low battery state, the data

stored in NVRAM may be destroyed after
power down the board with battery low
state.

Warning: Failed register NVRAM to platform

manager
pm_fault_register_device() API return error

Warning: Failed register NVRAM to platform

manager
pm_fault_register_device() API return error

Warning: Failed running NVRAM battery

monitor thread

pthread_create() returns error

Warning: Failed running NVRAM battery

monitor thread

pthread_create() returns error

Reading/Writing NVRAM raw: not enough

space on NVRAM raw partition

When reading from or writing to Nvram raw

partition, there is not enough space.

NVRAM is not supported on card type:

[dec].

NVRAM is not currently supported on the

type of cards.

Warning: NVRAM size is 0

Nvram size is found to be zero. This is

usually caused by nvram hardware failure.

ROM: WARNING, nvram structure too big,

user may loose system configuration

Nvram data structure is too big and should

be trimmed. This does not have any impact
on the router functionalities.

Could not map nvram

Mapping of Nvram Failed

Could not map nvram

Mapping of Nvram Failed

Could not map nvram

Mapping of Nvram Failed

Warning: Failed running NVRAM battery

monitor thread

pthread_create() returns error. This error

occurs when mapping of PLD register for
reading NVRAM battery state is failed.

ROMMON variable-value pair: [chars],

contains illegal (non-printable)characters

Could not allocate memory for a DRAM

buffer.

ROMMON variable-value pair: [chars],

contains illegal (non-printable)characters

Could not allocate memory for a DRAM

buffer

ROMMON variable-value pair: [chars],

contains illegal (non-printable)characters

Could not allocate memory for a DRAM

buffer

ROMMON variable-value pair: [chars],

contains illegal (non-printable)characters

Could not allocate memory for a DRAM

buffer

ROMMON variable-value pair: [chars],

contains illegal (non-printable)characters

Could not allocate memory for a DRAM

buffer

ROMMON variable-value pair: [chars],

contains illegal (non-printable)characters

Could not allocate memory for a DRAM

buffer

NVRAM platform board read error

can not read board type. platform_get_hw_board_type_revision()

return err

NVRAM platform board read error

can not read board type. platform_get_hw_board_type_revision()

return err

PM_FAULT_REGISTER_DEVICE registers a
device instance with the fault report API.
This step must be done before the device
driver may report faults. It should be done
at the init phase rather than when an error
occurs. When registration of device
Warning: Failed register NVRAM to platform instance failed, fault reports are not
manager
logged.

Warning: Failed register NVRAM to platform

manager
pm_fault_register_device() API return error

Warning: Failed register NVRAM to platform

manager
pm_fault_register_device() API return error

Warning: NVRAM size is 0

Possible error during sizing nvram, the

NVRAM may not exist

Warning: NVRAM size is 0

Possible error during sizing nvram, the

NVRAM may not exist

NVRAM low battery detected, battery

needs to be replaced

Detect NVRAM low battery state, the data

stored in NVRAM may be destroyed after
power down the board whit battery low
state.

NVRAM low battery detected, battery

needs to be replaced

Detect NVRAM low battery state, the data

stored in NVRAM may be destroyed after
power down the board whit battery low
state.

Could not map nvram

Mapping of Nvram Failed

Could not map nvram

Mapping of Nvram Failed

ROMMON variable-value pair: [chars],

contains illegal (non-printable)characters

Could not allocate memory for a DRAM

buffer

ROMMON variable-value pair: [chars],

contains illegal (non-printable)characters

Could not allocate memory for a DRAM

buffer

Warning: Failed register NVRAM to platform

manager
pm_fault_register_device() API return error

Warning: Failed register NVRAM to platform

manager
pm_fault_register_device() API return error

Warning: Failed running NVRAM battery

monitor thread

pthread_create() returns error

Warning: Failed running NVRAM battery

monitor thread

pthread_create() returns error

Warning: NVRAM size is 0

Possible error during sizing nvram, the

NVRAM may not exist

Warning: NVRAM size is 0

Possible error during sizing nvram, the

NVRAM may not exist

[chars]

Debug init failed

[chars]: Can't connect to configuration,

[chars]

NVRAM debugging service register to sysdb

failed.

Nvram initialization failed due to low

memory conditions.

Could not get enough memory while trying

to initialize nvram.

Nvram initialization failed due to low

memory conditions.

Could not get enough memory while trying

to initialize nvram.

DLL was not loaded after many retries. Will

[chars]: [chars] [chars] Could not open DLL exit to recover.

[chars]: [chars] [chars] Can't Resolve

symbol

Cannot resolve symbols for the interface

function. Probably function not defined in
DLL. Will exit to recover.

[chars]: Undefined Functions in DLL

Some required functions have not been

defined in DLL. Will exit

Corrupt nvram. Format with \erase nvram:

format\

Corrupt nvram detected while trying to do

an operation.

Classic config could not be erased due to

low memory conditions.

Could not get enough memory while trying

to erase classic config.

event_block error in [chars] -- [chars]

Error during event block

Nvram could not be formatted due to low

memory conditions.

Could not get enough memory to format

NVRAM.

[chars]: could not auto format corrupted

NVRAM, error: [chars]

Probably the NVRAM device has gone bad.

[chars]: Nvram Initialization Failed

Error while trying to init, sanitize nvram

during NVRAM initialization.

Nvram initialization failed due to low

memory conditions.

Could not get enough memory while trying

to initialize nvram.

Nvram initialization failed due to low

memory conditions.

Could not get enough memory while trying

to initialize nvram.

Nvram sanitize failed due to low memory

conditions.

Could not get enough memory while trying

to sanitize nvram.

[chars](): Nvram out of space

nvram full

Nvram initialization of raw partition failed

due to low memory conditions.

Could not get enough memory while trying

to initialize nvram.

Nvram initialization of raw partition failed

due to low memory conditions.

Could not get enough memory while trying

to initialize nvram.

[chars]: [chars], please restart nvram

process to attempt recovery
[chars]: [chars]

The NVRAM device corruption recovery

attempt has failed.
The NVRAM device corruption fixed.

Failed during nvram sanitize: Nvram

Initialization Failed

Error while trying to sanitize nvram during

NVRAM initialization.

[chars]: Nvram Initialization Failed

Error while trying to create/open a shared

memory file for nvram backup during
NVRAM initialization.

nvram unmount failed for [chars]

Failed to unmount nvram: file system.

Restart process or reload operation would
trigger possible corruption. If there is no
such symptom, this message can be
ignored.

Nvram sanitize failed due to low memory

conditions.

Could not get enough memory while trying

to sanitize nvram.

Nvram sanitize failed due to low memory

conditions.

Could not get enough memory while trying

to sanitize nvram.

Nvram sanitize failed due to low memory

conditions.

Could not get enough memory while trying

to sanitize nvram.

NVRAM File Corrupted ([chars]). Some of

them May be Lost

Files Overwritten by Another Image, or

Router Crashed

NVRAM dump file was not moved out of

/tmp ([chars]:[dec]:[chars]). Please collect
file from /tmp before reload

Previously due to some error, NVRAM dump

file was collected. At the time of collection,
permanent storage was not available so it
was saved at /tmp directory. NVRAM
process tried to move this file out to
permanent storage but it failed. This file
maybe required to identify if there is real
issue with NVRAM device. Collect dump file
from /tmp directory for further inspection.

nvram classic_rommon_setvar function

failed: ([chars]), ([dec])

PD component returned error for nvram

classic_rommon_setvar function call

[chars]: dump file path: [chars]

Informational message indicating the

nvram dump file path.

[chars]: Open for path [chars] failed, error: Check the state of the device pointed by
[chars], [chars]
path. Device may be inaccessible.
nvram unmount requested due to process
restart or card reload

nvram: file system is unmounted due to

process restart or node reload

nvram upgrade: [chars]

Regular nvram: file system is in upgrading

process

[chars]: Can't Attach Pathname \[chars]\

Could not attach pathname

raw partition resource manager failed:

[chars]

Could not spawn a thread to handle nvram

raw partition request

Could not create event manager for

[chars]: [chars]

Failed to create event manager for the

process

File open failed. file: [chars], reason:

[chars]

File open failed. Reboot history index got

corrupted. When recovering the reboot
history index, file open operation failed.
Please verify the reason why it is failed.

Function write_tlv_in_offset write the TLV

data which is being pointed by region
offset. This function used to for writing
NVRAM TLV from XR. Set the offset position
in the nvram file and write the reboot
history record. Fseek failed for the provided
write_tlv_in_offset: Not able to seek offset: offset for that nvram bin file. Refer the
[dec], reason: [chars]
reason why it is failed.

Write failed: file: [chars], reason: [chars]

Reboot history index got corrupted. When

recovering the reboot history index, file
write operation failed. Please verify the
reason why it is failed.

write_tlv_in_offset: not able to write in

offset: [dec], reason: [chars]

Function write_tlv_in_offset write the TLV

data which is being pointed by region
offset. This function used to for writing
NVRAM TLV from XR. Write the reboot
history record in the offset position.
Operation write failed for the nvram bin
file. Refer the reason why it is failed.

Unable to erase reboot history. Please

erase by 'erase nvram-erase: location
<location>'

Failed when erasing the corrupted reboot

info.

[chars]: Mutex [chars] failed ([chars])

A mutex un/lock failed for the reason cited

in ()'s. If a lock operation fails, subsequent
accesses to nvraw will be aborted. If an
unlock operation fails, the behavior is
dependent on the failure.

[chars]: Reboot history index got

corruppted: [hex]\n Unable to recover the
reboot history. Saving/backuping the reboot
history file and recovering by erase the
reboot history file.\n
Information to collect the logs

[chars]: Reboot cause: [hex]\tReason:

[chars]

printing the reboot reason.

Invalid parameter [chars]=[dec] while

trying to get primary boot device

An invalid parameter value was passed to

the function.

Invalid parameter [chars]=[dec] while

trying to do mirror config verify

An invalid parameter value was passed to

the function.

Invalid device name [chars]=[dec] passed

while trying to get local primary device

An uninitialized argument passed while

trying to get local primary device.

Invalid device name [chars]=[dec] passed

while trying to get local secondary device

An uninitialized argument passed while

trying to get local secondary device.

Invalid argument type [chars]=[dec]

passed to redfs_media_error while
reporting error on a device

An invalid error parameter was passed to

the media_error API.

Invalid parameter [chars]=[dec] while

trying to enable mirroring

An invalid parameter value was passed to

the function.

Invalid parameter [chars]=[dec] while

trying to notify partition is available

An invalid parameter value was passed to

the function.

Invalid parameter [chars]=[dec] while

trying to notify partition is down

An invalid parameter value was passed to

the function.

Invalid parameter [chars]=[dec] while

trying to notify partition is removed

An invalid parameter value was passed to

the function.

Unable to channel connect local to

'[chars]', errno=[dec]:[chars].

The redfs server channel specified could

not be opened for the specified reason.

The message send to the redfs server

Unable to send message to redfs server, op failed for the specified operation number
[dec], errno=[dec]:[chars].
and failed for the specified reason.

Unable to channel connect remote to

'[chars]', errno=[dec]:[chars].

The redfs server channel specified could

not be opened for the specified reason.

[chars] [chars]: [chars]

Syncfs failure

Failed to initialize module [chars] because

[chars] and cannot continue.

Syncfs failed to initialize a module.

Failed to register with [chars] for

notification

Syncfs failed to register with qsm/lrd for

notification

Failed to create link to Standby card:

[chars]

Syncfs failed to create required links to the

standby card. Syncfs unable to mirror any
files to the standby card.

Symbolic Links to Standby root is not

published yet.

Syncfs noticed that required symbolic-links

to the standby card, is not published yet.
Syncfs will get notified when they are
available.

[chars]: [chars]

Failed function call.

Unable to replicate [chars] [chars] to

standby card because [chars]

Syncfs failed to transfer the specified file to

the standby card.

Standby has become AVAILABLE - START

SYNC

The Standby card has been inserted and

sync will be started

Standby has been rendered UNAVAILABLE - The Standby card has been either removed
STOP SYNC
or put down by admin

Standby has become AVAILABLE. LRD

returned partner-node - START SYNC

The Standby card has been inserted and

sync will be started

Failed to lock mutex [chars]

A required mutex lock failed.

Mutex [chars] was found unlocked

A mutex which should have been locked

was tested and found unlocked

Failed to unlock a mutex [chars]

A required mutex unlock failed.

Replication of [chars] [chars] failed: [chars] Syncfs failed to replicate file/dir, it will retry
-- Retry will be attempted.
it again.
Syncfs failed to transfer a file to the
File [chars] lost synchronization to standby standby card. If a card failover occurs,
card
some data may be lost.
Failed to lock mutex for file [chars]
A required mutex lock failed.

Mutex for file [chars] was found unlocked

Failed to unlock mutex for file [chars]

A mutex which should have been locked

was tested and found unlocked
A required mutex unlock failed.

[chars] - [chars]

failed to send accounting record

[chars] - [chars]

Admin exec process failed to send AAA

authorization record.

Event [chars] attach error: [chars]

The call to event_*_attach() failed

Error: [chars]

The call to event_block() failed

Failed to create event manager. Error code:

[dec]
The call to event_manager_create() failed

[chars]: [chars]

'Unable to destroy event manager on exec

exit'

[chars]: [chars]

'lib/ui library API related to getline has

failed'

[chars]

getline_init() failed.

Failed to initialize tracing functionality for

adminexec process([dec]). Shell will
continue but trace messages will not be
generated. Error:[chars]

Initialization of trace functionality for exec

shell failed. This would affect the
debugging of exec shell.

Failure in lwm API call, [chars]. Error:[chars] The LWM api call failed.

Error code:[dec]. [chars]

Unable to create exec's event handling

thread

[chars]. [chars]

An internal software error occurred.

sysdb_register_notification failed with error

messsage:[chars]
An internal software error occurred.

failed to detect hostname displaying

default: [chars]

Unable to bind to sysdb to get hostname

hence displaying default hostname.

Normally a bear has [[dec]] eyes and

[[dec]] legs, can speak Bearish

This is a simple message with

alarm_location set to false

Today the bear has [[dec]] eyes and [[dec]] This is a simple message with
legs, can speak [[chars]]
alarm_location set to true

alarm buffer [chars]: [unsigned int]

event(s) deleted

Some (or all) of the alarms in the alarm

buffer have been deleted as a
consequence of an action initiated by the
user. This message does not require any
action. It informs that a clear logging event
delete command or an alarm buffer resize
operation (or equivalent operation through
another management interface) was
executed.

Invalid argument received for: [chars]

This is an internal error that invalid

parameter is encountered.

Inconsistency in element count in db:

[chars]

The item count in the internal database is

inconsistent.

Nonfatal error: [chars]

This is an error message in the Netflow

manager to indicate anomolies which are
not FATAL. Some of the messages may
indicate a failure to allocate a resource
needed by the application. In many cases
these messages must not keep appearing
after the temperory situation is resolved.

Failure occured in : [chars]

A failure occurred during the initialization

of ENS library or during NRS class creation.
This probably indicates an underlying more
severe problem.Internal failure.

[chars]: memory allocation failed

Failed to allocate dynamic memory.It could

be happen on the route processor or on the
asynchronous transfer mode(ATM) line
card.

Failure occured in : [chars]

A failure occurred during the initialization

of ENS library or during NRS class creation.
This probably indicates an underlying more
severe problem.Internal failure.

Failure occured in : [chars]

A failure occurred during the initialization

of the common VCCCLASS library. This
probably indicates an underlying more
severe problem.

[chars]: failed, consumer tried to add

unknown virtual circuit(vcclass) to its
interface

An ATM VCCLASS consumer has attempted

to attach an unknown vcclass to its
interface.

[chars]: general failures in client(ATM

VCCLASS) API

These are general ATM VCCLASS client API

failures.Internal failure.

[chars]: failure returned by one or more

ENS or NRS functions

One or more ENS or NRS APIs has returned

a failure. The failure happens while the
consumer is calling the ATM VCCLASS
client APIs. Internal failure.

[chars]: invalid fields received in buffer by

consumer

The consumer finds one or more invalid

fields in the buffer received from the
producer.Internal error.

[chars]: failure in external data

manager(EDM) backend

A failure occurred in the ATM VCCLASS EDM

backend. As a result the VCCLASS data will
not be delievered to the front end.

[chars]: failure returned by one or more

ENS or NRS functions

One or more ENS or NRS APIs has returned

a failure. This failure happens on the
producer side.Internal failure.

Failured occured in : [chars]

One or more input arguments to an internal

function is invalid.

[chars]: failed on producer(ATM VCCLASS)

side

A failure occurred in the ATM VCCLASS

producer while preparing the vcclass data
to be sent to ENS.Inernal failure.

[chars]: failed while processing requests

from the consumer

A failure occurred in the ATM VCCLASS

producer handler while processing requests
from the consumer.Internal failure.

A failure occurred related to SysDB or in

[chars]: failure in System database callback one of the verify/apply/notify SysDB
functions
callback functions.

[chars]: virtual circuit class tree is

corrupted

A failure occurred while accessing the ATM

VCCLASS internal data structrure. There
might be an inconsistency between the
SysDB and the vcclass tree or the vcclass
tree is corrupted.

An attempt to save the node configuration

has taken longer than expected. This may
Configuration save request delayed [chars] be due to a high volume of activity within
for [dec] seconds for node [chars].
the configuration management system.

Unable to allocate memory to copy:

'[chars]'

'Memory allocation failure'

Unable to bind to '[chars]': '[chars]'

'Unable to bind to action/gl path' ;

Unable to set value in path '[chars]':

'[chars]'. Probably nothing to clear.
(process to clear is not running)

'Unable to set the value in the specified

path'

sysdb unbind failed: '[chars]'

'Unable to Unbind sysdb bind' ;

Unable to register the aux block ([chars])

The ConAux Identity module has been

unable to register the aux block.

Unable to register the aux TTY ([chars])

The ConAux Identity module has been

unable to register the aux TTY.

Unable to register the console block

([chars])

The ConAux Identity module has been

unable to register the console block.

The ConAux Identity module has been

Unable to register the console TTY ([chars]) unable to register the console TTY.

The call to inet_ntop() failed. Family: [dec]

Internal error

Can't bind to sysdb, aborting operation

Internal error

Error [chars] deleting [chars] from sysdb

Internal error

Error [chars] getting [chars] from sysdb

Internal error

Error [chars] setting [chars] in sysdb

Internal error

Could not start transaction in, [chars] abort operation

Internal error

[chars]

Internal error

Could not lock tuple [chars], in [chars] abort operation

Internal error

Got NULL tuple although sysdb reported

success in, [chars]

Internal error

Error packing tuple received from sysdb in,

[chars]
Internal error

Could not unlock tuple [chars], in [chars],

line [dec] - will time out eventually.

Internal error

Error unpacking tuple received from sysdb

in, [chars]
Internal error

Configuration Manager was unable to

initialize the [chars] module. Error:
'[chars]'. Initialization will be tried again
after 60 seconds.

An error was encountered while initializing

one of the critical modules of the
configuration manager server. Without
proper initialization of this module,
configuration manager can not operate
properly. Initialization will be retried every
60 seconds if required.

Configuration Manager succeeded in

initializing the [chars] module upon retry.

An error was previously encountered while

initializing one of the critical modules of
the configuration manager server.
However, the initialization was retried and
succeeded.

Admin plane configuration inconsistency

alarm has been [chars]

The admin plane configuration

inconsistency alarm has been raised or
cleared.

Could not clean the local CFS before use.

Error: '[chars]'.

Local CFS is non-native and automatic

cleanup of it has failed.

The commit database is not in sync with

the running configuration. Please use the
command 'cfs check' to resynchronize the
commit database. Error: '[chars]'

The chain of configuration changes stored

in commit database is possibly broken.

[chars]

The specified storage device is full or some

files can not be deleted.

An error was occured while retreiving an

event [chars]

An internal error was encountered while

initializing event manager for default
configuration verification thread. This
condition might have been caused by the
failure of the event_block() API.

The OS returned an error while SysDb was

attempting to perform a file save
There was an internal error encountered
operation. Any changes have been rolled
while attempting to save a file during the
back. Error: '[chars]'
user interactive commit operation.

A configuration inconsistency alarm has

been [chars]

The configuration inconsistency alarm has

been raised or cleared.

Error encountered while [chars]

configuration for '[chars]'. Some
configuration may not have been applied
and any missing configuration needs to be
reapplied manually. Error: '[chars]'

An error was encountered during interface

configuration restore/save operation. Some
configuration may not have been applied
or the line card may be in unusable state.

OIR '[chars]' request for interface '[chars]'

could not be processed due to a pending
commit operation or commit database
consolidation operation.

This is an error message to indicate that

the configuration could not be either saved
or restored because of a pending commit
operation or commit database
consolidation operation. A manual reset of
the node after the pending operation has
completed should save or restore the
configuration for the node.

The platform library failed to parse

interface '[chars]'. Error: [chars].

The platform library could not parse the

interface name.

Illegal file read operation of configuration

files by this process.

The process has illegally read configuration

files before configuration manager has
applied configuration. This configuration
read by this process might be inaccurate
after configuration manager completes
applying the configuration.

[chars]

Configuration Manager is displaying an

error message during boot time.

Error encountered while deleting the

configuration lock. Err: '[chars]'

An error was encountered during deletion

of the configuration lock. This configuration
operation (e.g. save/restore configuration,
CLI commit) is successful, but subsequent
configuration operations could be affected
by this error if not corrected.

Could not determine the nativity of the

local CFS; will assume that it is native.
Error: '[chars]'. Problem: '[chars]'.

Could not determine the nativity of the

local CFS. If it is native, this message
should be ignored; if it is non-native, then
automatic cleanup is not done and user
intervention is required.

Configuration manager failed to create the

set of directories comprising the CFS
repository under the cfs root directory. This
renders the system practically unusable.
[chars]. Please check for problems with the The potential problems could range from
boot device.
no space on disk to a flawed disk.

Commit database initialization Failure.

[chars]

An error was encountered during

initialization of the commit database. This
is most likely due to an error in reading the
commitdb info file, which could be due to
disk0: or CFS being corrupted or the file
itself being truncated. The system recovers
from this situation by cleaning up all files in
commitdb if needed and initializing it
empty. This may result in loss of all rollback
points. However, this should not cause loss
of configuration as the system applies the
alternate ASCII file maintained for such
situations. In certain scenarios, changes
made in the last one or two commits may
be lost.

This message indicates that the directory

path specified in the message has incorrect
mode (ie. not a directory). As a corrective
action, the software attempts to
automatically remove the file. A message
of 'No Error' for unlink, for example, would
indicate that it has successfully removed
Path '[chars]'. Mode [hex]. Unlink: '[chars]'. the file.
Some '[chars]' Configuration could not be
restored by Configuration Manager. To view
failed config(s) use the command - '[chars]' None

Configuration Manager was unable to

initialize the [chars] module. Error:
'[chars]'. [chars].

An error was encountered while initializing

one of the modules of configuration
manager server. The failure of this module
initialization is not critical to configuration
manager to be completely operational.

[chars]: interface [[chars]]

The total number of ports could not be

determined for this interface. Configuration
manager will not be able to determine if
there is any more configuration for
remaining ports.

[chars] Error:[chars]

This is a non-fatal error and can happen

when router is low on memory. It should
not affect the functioning of the router, but
trace messages may not be logged.

Version of existing [chars] detected to be

incompatible with the installed software.
[chars]

None

Configuration session ID '[chars]' (started

by user '[chars]' from line '[chars]') was
terminated by user '[chars]' from line
'[chars]'.

This message indicates that the session

specified in the message had been cleared
via CLI 'clear configuration session
<seesion_ID>'.

An error was encountered while accessing

[chars] file.

An error was encountered while stating a

file in commitdb sanity module. This could
be an intermittent software failure and this
will get resolved automatically.

Configuration committed by user '[chars]'.

Use 'show configuration commit changes
An SDR plane configuration change was
[chars]' to view the changes.
made by the specified user.
[chars]. Use 'show configuration commit
changes [chars]' to view the changes.

An administration plane router

configuration change occurred by the
specified user.

Configuration for node '[chars]' has been

restored.

This is message indicates that

configuration for this node has been
restored.

Configuration for removed node '[chars]'

has been saved.

This is message indicates that

configuration for this node has been saved.

Some incompatible configuration was

removed from the running configuration
during this software activation/deactivation
operation and saved in file '[chars]'. To
address the incompatibility issue enter
configuration mode and use the 'load
configuration removed [chars]' and
Some configuration was removed for this
'commit' commands.
software activation /deactivation operation.

[chars]

Configuration Manager is displaying a

message during boot time to indicate an
alternate configuration will be restored
during the router boot operation. The
alternate configuration is specified by the
user by using a boot option or ROMMON
variable setting.

[chars]

An unexpected internal error occurred in

the configuration subsystem.

Failed to announce the completion of

startup configuration. \ [chars] - '[chars]'

Under normal circumstances configuration

manager announces the completion of
startup configuration. If for some reason
config_cli cannot connect to configuration
manager then it should announce the
completion of startup configuration. This is
so that the administrator can perform some
basic tasks like configuring the ethernet
interface, format a disk, kill some
processes, etc., to restore some order to
the system for a subsequent reload.

Failed to execute a AAA operation - [chars]

- [chars]
Failed to execute a AAA function.
Some admin configurations can not be
[dec] admin config(s) failed during [chars]. handled correctly because: - invalid
To view failed config(s) use the command configuration - configuration can not be
- \admin show configuration failed startup\ accepted at this moment

Failed to [chars]: Error: [chars]

Initialization of admin config cli auto-save

commit verifier failed.

Failed to [chars]: Error: [chars]

Initialization of config cli auto-save commit

verifier failed.

[dec] config(s) failed during [chars]. To

view failed config(s) use the command \show configuration failed startup\

Some configurations can not be handled

correctly because: - invalid configuration configuration can not be accepted at this
moment

[chars] process: abnormal termination,

signal number = [dec]

A child process received a signal and

terminated abnormally.

Aborting startup configuration. [chars].

Failed to get the startup config file name.

Event [chars] attach error: [chars]

The call to event_*_attach() failed. Config

CLI library failed to attach events to event
manager. The effect is that config-cli would
not handle any events.

[chars]:Failed to create event manager:

[chars]

Config process is failing to create an event

manager. See error for reason.

config process is failing to create a

[chars]:Failed to create the event handling separate thread for creating and handling
thread:[chars]
edm requests.

[chars] : [chars]: [chars]

config process failed to perform a file

operation due to either filesystem
restart/busy or an internal error.

[chars]: [chars]

'lib/ui library API related to getline has

failed'

Failed to initialize tracing functionality for Initialization of trace functionality for config
config cli library. No trace messages will be failed. This would affect the debugging of
generated. Error:[chars]
config shell.

Failed to initialize tracing functionality for

config process. No trace messages will be
logged. Error:[chars]

Initialisation of trace functionality for config

failed. This would affect the debugging of
config shell.

Failure in lwm API call, [chars]. Error:[chars] The LWM api call failed.

Failed to allocate memory:[chars]

System could not successfully provide the

request memory block.

Unable to get memory info for the current

node:[chars]

Config process failed to get memory state

info from wdsysmon when it came up.

Unable to create piping subproc: [chars]

This condition might result in failure of

communication between two process.

[chars]

Config process bar failed to

creation/deletion

Error associating [chars] stream with file

descriptor : [chars]

Read or Write operation not possible as

there is an error in associating a stream
with a file descriptor.

config process failed to attach event

handler for signal '[chars]':[chars]

Config process is failing to perform event

handling intialisation for a signal. The
operations could cause bad handling of the
signal.

specified source is a ditectory; filename is

expected :[chars]

Failed to open the startup configration file

for the following reason: - CONFIG_FILE is
set to a directory.

[chars]:[chars]:[chars]

Config process is failing to perform a sysdb

operation. The operation and cause of
failure in message.

Config process failed to clear target config

buffer. Configured items will not be cleared
[chars]:Failed to clear target config:[chars] from buffer.

[chars]:Failed to commit target config:

[chars].

Config process failed to commit target

config buffer. Configured items will not be
committed in sysdb.

[chars]:Failed to commit target config:

[chars]

Config process failed to commit target

config buffer. Configured items will not be
committed in sysdb.

[chars]:Failed to create target config:

[chars].

Config process failed to create target config

buffer. Configuration can not proceed.

[chars]:Failed to destroy target config:

[chars]

Config process failed to destroy target

config buffer.

[chars]:Failed to obtain exclusive lock for

this session:[chars]

Config process failed to obtain exclusive

lock for this session. Terminate the other
open sessions and try again.

[chars]:Failed to release the lock held by

session:[chars]

Config process failed to release exclusive

lock held by this session.

failed to detect hostname displaying

default: [chars]: [chars]

Unable to bind to sysdb to get hostname

hence displaying default hostname.

failed to delete failed config file: [chars]:

[chars]

The failed_config file should be deleted

when all the configurations are successfully
reapplied.

failed to spawn: [chars]: [chars]

An executable was not spawned due to the

mentioned error.

failed to open startup file: [chars]: [chars]

Failed to open the startup configration file

for any of the following reasons: - file does
not exist. This may be case when booting
for the first time or when even the default
startup config file does not exist. IGNORE
the message in this case. - CONFIG_FILE is
set to a directory. - the config file doesn't
exist under the current directory. - Illegal
file name. set CONFIG_FILE to a valid file
name an retry. - Other system errors. The
last part of the error message should give a
hint of the system error.

[chars]

Config process is delaying applying

configuration until infrastructure is ready.

Failed to add item to for [chars] - [chars]:

[chars]

'Config library failed to add node to the

given list with the reason mentioned in the
message. This may lead to wrong 'show
config failed' listing.'

'Compiling a regular expression failed with

the reason mentioned in the message. This
Regular expression compilation failed with may lead to wrong 'show config failed'
error '[chars]'.
listing.'

'Regular expression match failed with the

reason mentioned in the message. This
Regular expression match failed with error may lead to wrong 'show config failed'
'[chars]'.
listing.'

Failed to initialise edm for [chars] option [chars]:[chars]

Config library is failing to initialise the edm.

Failed to unregister edm - [chars]:[chars]

Failing to unregister the edm.

Maximum buffer size [[dec]] reached,

deleting correlation ID [[dec]] from
correlation buffer

The alarm correlation buffer is full; the

oldest correlation specified in the message
is dropped from the buffer to make room
for the new correlation.

Virtual appliance configuration cannot

occur: [chars]

The CVAC (Cisco Virtual Appliance

Configuration) subsystem failed at startup
and was unable to run successfully. The
subsystem will attempt to run again after
the next reload of the router.

Errors were encountered while applying

configs from file [chars]. Please inspect
[chars] for details

Automatic configuration from the indicated

file was not fully successful. At least one
error of some sort was encountered.

Could not [chars] file [chars]: [chars]

An error was encountered when CVAC

(Cisco Virtual Appliance Configuration) was
trying to perform the specified operation
on the specified file.

The CVAC (Cisco Virtual Appliance

Configuration) subsystem read and applied
router configuration from the specified file,
which will now be removed from the
system for security. More information can
Configuration was applied from file [chars]. be found in the provided file or CLI
See [chars] for more details.
command.

Configuration file [chars] was ignored:

[chars]

CVAC (Cisco Virtual Appliance

Configuration) ignored a configuration file
and did not apply it to the router. The
specified reason explains why the file was
ignored.

xmlagent process has stopped due to

crypto package deactivation. Unconfigure
xmlagent with 'no xml agent corba'

The crypto pie is deactived or removed

while xmlagent is running in ssl mode.

xmlagent process exits due to crypto

initialization failure. Unconfigure xmlagent The crypto pie is not properly configured
with 'no xml agent corba'
and can't be initailized
xmlagent process detected an anomaly
with pipe due to possible pipe process
restart. xmlagent process is now
terminating and will be restarted
automatically.

The pipe process is probably restarted

which is caught in TCP_Monitor

The xmlagent process is restarting while

xmlagent process is restarting after wait for wait for config operation completion times
configuration completion timeout.
out. Commit database info may lose
xmlagent process detected an anomaly
with underlying transport layer due to
possible TCP process restart. xmlagent
process is now terminating and will be
restarted automatically.

The tcp process is probably restarted which

is caught in TCP_Monitor

[chars]: [chars] - [chars]

failed to send accounting record

[chars]: [chars]

The call to
bag_register_all_outgoing_conn_bag()
failed

Unable to chdir [chars]:[chars]

An internal software error occurred.

[chars]: debug_dll_hook() - ([chars])

An internal software error occurred.

Debug initialization failed: [chars]

'Failed to initialize a debugging event for

the reason listed in' ' the message'

Debug registration failed: [chars]

'Debug registration failed for the reason

listed in the message.'

Event [chars] attach error: [chars]

The call to event_*_attach() failed

Error: [chars]

The call to event_block() failed

[chars]: Error code: [dec]

The call to event_init_event() failed

[chars]: Failed to create event manager.

Error code: [dec]

The call to event_manager_create() failed

[chars]: [chars]: [chars]

'Unable to destroy event manager on exec

exit'

Unable to get path for env var [chars]

An internal software error occurred.

[chars]: [chars]

'lib/ui library API related to getline has

failed'

[chars]: [chars]

getline_init() failed.

[chars]

login() failed

[chars]: Call to login_ecm_conn_sysdb()

failed.

An internal software error occurred.

Failed to initialize tracing functionality for

exec process([dec]). Exec shell will
continue but trace messages will not be
generated. Error:[chars]

Initialization of trace functionality for exec

shell failed. This would affect the
debugging of exec shell.

Failure in lwm API call, [chars]. Error:[chars] The LWM api call failed.

Error code: [dec]. [chars]

Unable to create exec's event handling

thread

[chars]: [chars]

shell_parser_init() failed.

Error code:[dec]. [chars]

Unable to create exec's event handling

thread

[chars]: pthread_mutex_lock failed with

error messsage:[chars]

An internal software error occurred.

[chars]: pthread_mutex_unlock failed with

error messsage:[chars]

An internal software error occurred.

Unable to set [chars]:[chars]

An internal software error occurred.

[chars]: sysdb_bind failed. [chars]

An internal software error occurred.

[chars]: sysdb_item_delete() failed. [chars] An internal software error occurred.

[chars]: sysdb_item_get failed. [chars]

An internal software error occurred.

Exec registers its EDM path for storing

data. This registration of EDM has failed
due to reasons mentioned in the error
message. This failure could cause, exec
session not to start up or could cause
problem in entering configuration
Exec failed to register EDM: [[hex]] [chars] submodes.

[chars]: sysdb_register_notification failed

with error messsage:[chars]

An internal software error occurred.

[chars]: sysdb_unbind failed. [chars]

An internal software error occurred.

Unable to obtain user's taskmap via

([chars]):[chars]

When exec is launched by certain clients

like ssh/Fault-manager the authentication is
bypassed. It is because authentication is
done by clients already. In this case exec
needs to obtain the user's taskmap though.
This is done by calling suitable AAA apis. If
one of the apis fails, then this ios msg is
emitted.

[chars]: tcgetattr call failed with error [dec]

[chars]
An internal software error occurred.

[chars]: tcsetattr call failed with error [dec]

[chars]
An internal software error occurred.

[chars]: [chars]

tty_details_from_device_file() failed

[chars]: [chars]

The call to tty_mgmt_connect() failed

[chars]: [chars]

The call to
tty_mgmt_deregister_tty_options() failed

[chars]: Error:[dec]. [chars]

The call to tty_mgmt_register_tty_subset()

failed

[chars]: [chars]

The call to tty_mgmt_scan() failed

[chars]: [chars]

The call to tuple_pack() failed

[chars]: [chars]

The call to tuple_unpack() failed

[chars]: [chars]

The call to tuple_unpack_mask() failed

[chars]: Error code: [dec]. Description:

[chars]

The call to tty_mgmt_register_tty_options()

failed

Init Error: [chars]

The process nf_gsr_perf encountered a

software error while initializing.

HW Programming Failed: [chars]

A problem is detected in programming the

hardware.

Nonfatal error: [chars]

This is an error message in the nf_gsr_perf

process to indicate anomolies which are
not FATAL.In many cases these messages
must not keep appearing after the
temperory situation is resolved.

[chars]

An AAA operation carried out by the HTTP

CLI Agent returned unexpected results.

[chars]

An AAA operation carried out by the HTTP

CLI Agent returned unexpected results.

An EmWeb function to [chars] returned an

error to the HTTP CLI Agent

The HTTP CLI Agent was unable to carry

out an EmWeb server function. The HTTP
process may no longer be able to function
correctly, and may need restarting if the
errors persist.

An EmWeb function to [chars] returned an

error to the HTTP CLI Agent

The HTTP CLI Agent was unable to carry

out an EmWeb server function. The HTTP
process may no longer be able to function
correctly, and may need restarting if the
errors persist.

[chars], Error: [chars]

The HTTP CLI Agent was unable to carry

out an operation on an internal file. The
HTTP process may no longer be able to
function correctly, and may need restarting
if the errors persist.

[chars], Error: [chars]

The HTTP CLI Agent was unable to carry

out an operation on an internal file. The
HTTP process may no longer be able to
function correctly, and may need restarting
if the errors persist.

[chars]

The HTTP CLI Agent has encountered an

invalid state - this point in the code should
not have been reached. The HTTP process
may need restarting if the errors persist.

[chars]

The HTTP CLI Agent has encountered an

invalid state - this point in the code should
not have been reached. The HTTP process
may need restarting if the errors persist.

The HTTP CLI Agent has passed itself a

NULL pointer when it should not have done
- this point in the code should not have
A NULL pointer was passed by the HTTP CLI been reached. The HTTP process may need
Agent to itself
restarting if the errors persist.

The HTTP CLI Agent has passed itself a

NULL pointer when it should not have done
- this point in the code should not have
A NULL pointer was passed by the HTTP CLI been reached. The HTTP process may need
Agent to itself
restarting if the errors persist.

[chars]

The HTTP CLI Agent has passed itself an

invalid parameter - this point in the code
should not have been reached. The HTTP
process may need restarting if the errors
persist.

[chars]

The HTTP CLI Agent has passed itself an

invalid parameter - this point in the code
should not have been reached. The HTTP
process may need restarting if the errors
persist.

The HTTP CLI Agent was unable to allocate

the required amount of memory, as the
HTTP process has run out of resources. The
HTTP process may no longer be able to
The HTTP CLI Agent was unable to allocate function correctly, and may need restarting
[unsigned int] bytes of memory
if the errors persist.

The HTTP CLI Agent was unable to allocate

the required amount of memory, as the
HTTP process has run out of resources. The
HTTP process may no longer be able to
The HTTP CLI Agent was unable to allocate function correctly, and may need restarting
[unsigned int] bytes of memory
if the errors persist.

[chars]

A Parser operation carried out by the HTTP

CLI Agent returned unexpected results.

[chars]

A Parser operation carried out by the HTTP

CLI Agent returned unexpected results.

[chars] '[chars]'

A SysDB operation carried out by the HTTP

CLI Agent returned unexpected results.

[chars] '[chars]'

A SysDB operation carried out by the HTTP

CLI Agent returned unexpected results.

The HTTP CLI Agent was unable to create a

connection to the SysDB component. It
may be that the communication
infrastructure is faulty, or that the SysDB
component has not yet restarted. If the
The HTTP CLI Agent was unable to create a errors persist, the router may need to be
connection to SysDB
restarted.

The HTTP CLI Agent was unable to create a

connection to the SysDB component. It
may be that the communication
infrastructure is faulty, or that the SysDB
component has not yet restarted. If the
The HTTP CLI Agent was unable to create a errors persist, the router may need to be
connection to SysDB
restarted.

The HTTP CLI Agent was unable to retrieve

The HTTP CLI Agent was unable to retrieve the specified item from the SysDB
the item [chars] from SysDB
component.

The HTTP CLI Agent was unable to retrieve

The HTTP CLI Agent was unable to retrieve the specified item from the SysDB
the item [chars] from SysDB
component.

[chars], Error: [chars]

The HTTP CLI Agent was unable to carry

out an operation on an internal thread. The
HTTP process may no longer be able to
function correctly, and may need restarting
if the errors persist.

[chars], Error: [chars]

The HTTP CLI Agent was unable to carry

out an operation on an internal thread. The
HTTP process may no longer be able to
function correctly, and may need restarting
if the errors persist.

[chars]

No error has occurred, but you should be

aware that an unusual or unwanted
situation may have arisen, and you may
want to take preventation action as
outlined in the warning message.

[chars]

No error has occurred, but you should be

aware that an unusual or unwanted
situation may have arisen, and you may
want to take preventation action as
outlined in the warning message.

[chars]

Authentication related error occured or

returned unexpected results.

[chars]

Authentication related error occured or

returned unexpected results.

The HTTP Server was unable to retrieve the

The HTTP Server was unable to carry out a specified item(s) from the SysDB
backend scan on the SysDB item [chars]
component.

The HTTP Server was unable to retrieve the

The HTTP Server was unable to carry out a specified item(s) from the SysDB
backend scan on the SysDB item [chars]
component.
HTTP server process has exited due to
crypto package deactivation. Please
unconfigure this command via 'no http
server'.

The crypto pie is deactived or removed

while http server is running in ssl mode.

HTTP server process has exited due to

crypto package deactivation. Please
unconfigure this command via 'no http
server'.

The crypto pie is deactived or removed

while http server is running in ssl mode.

An EmWeb function to [chars] returned an

error to the HTTP ENA filesystem handler

The HTTP ENA filesystem handler was

unable to carry out an EmWeb server
function. The HTTP process may no longer
be able to function correctly, and may need
restarting if the errors persist.

An EmWeb function to [chars] returned an

error to the HTTP ENA filesystem handler

The HTTP ENA filesystem handler was

unable to carry out an EmWeb server
function. The HTTP process may no longer
be able to function correctly, and may need
restarting if the errors persist.

[chars], Error: [chars]

An Event Manager operation carried out by

the HTTP ENA filesystem handler returned
unexpected results. The HTTP process may
no longer be able to function correctly, and
may need restarting if the errors persist.

[chars], Error: [chars]

An Event Manager operation carried out by

the HTTP ENA filesystem handler returned
unexpected results. The HTTP process may
no longer be able to function correctly, and
may need restarting if the errors persist.

[chars], Error: [chars]

The HTTP ENA filesystem handler was

unable to carry out an operation on an
internal file. The HTTP process may no
longer be able to function correctly, and
may need restarting if the errors persist.

[chars], Error: [chars]

The HTTP ENA filesystem handler was

unable to carry out an operation on an
internal file. The HTTP process may no
longer be able to function correctly, and
may need restarting if the errors persist.

A NULL pointer was passed by the HTTP

ENA filesystem handler to itself

The HTTP ENA filesystem handler has

passed itself a NULL pointer when it should
not have done - this point in the code
should not have been reached. The HTTP
process may need restarting if the errors
persist.

A NULL pointer was passed by the HTTP

ENA filesystem handler to itself

The HTTP ENA filesystem handler has

passed itself a NULL pointer when it should
not have done - this point in the code
should not have been reached. The HTTP
process may need restarting if the errors
persist.

The HTTP ENA filesystem handler was

unable to allocate [unsigned int] bytes of
memory

The HTTP ENA filesystem handler was

unable to allocate the required amount of
memory, as the HTTP process has run out
of resources. The HTTP process may no
longer be able to function correctly, and
may need restarting if the errors persist.

The HTTP ENA filesystem handler was

unable to allocate [unsigned int] bytes of
memory

The HTTP ENA filesystem handler was

unable to allocate the required amount of
memory, as the HTTP process has run out
of resources. The HTTP process may no
longer be able to function correctly, and
may need restarting if the errors persist.

HTTP SSL init failed\n

The HTTP Server SSL initialization failed

HTTP SSL init failed\n

The HTTP Server SSL initialization failed

[chars] '[chars]'

A SysDB operation carried out by the HTTP

Server returned unexpected results.

[chars] '[chars]'

A SysDB operation carried out by the HTTP

Server returned unexpected results.

The HTTP Server was unable to create a

connection to SysDB

The HTTP Server was unable to create a

connection to the SysDB component. It
may be that the communication
infrastructure is faulty, or that the SysDB
component has not yet restarted. If the
errors persist, the router may need to be
restarted.

The HTTP Server was unable to create a

connection to SysDB

The HTTP Server was unable to create a

connection to the SysDB component. It
may be that the communication
infrastructure is faulty, or that the SysDB
component has not yet restarted. If the
errors persist, the router may need to be
restarted.

HTTP server is restarting since underlying

transport is not available.

TCP accept call failed, the HTTP server

can't function.

HTTP server is restarting since underlying

transport is not available.

TCP accept call failed, the HTTP server

can't function.

HTTP server encountered unexpected TCP

error during accept function call, the errno
is: [dec]. If this message continues to
TCP accept call failed, the HTTP server
appear, try restarting the HTTP server.
can't function.
HTTP server encountered unexpected TCP
error during accept function call, the errno
is: [dec]. If this message continues to
TCP accept call failed, the HTTP server
appear, try restarting the HTTP server.
can't function.

[chars]

The EmWeb code has encountered an error

condition or state. The HTTP process may
no longer be able to function correctly, and
may need restarting if the errors persist.

[chars]

The EmWeb code has encountered an error

condition or state. The HTTP process may
no longer be able to function correctly, and
may need restarting if the errors persist.

HTTP server over ssl would not work

correctly due to crypto package
deactivation. Please unconfigure this
command via 'no http server ssl'.

The crypto pie is deactived or removed

while http server is running in ssl mode.

[chars], Error: [chars]

A Debugging operation carried out by the

HTTP Server returned unexpected results.

[chars], Error: [chars]

A Debugging operation carried out by the

HTTP Server returned unexpected results.

[chars]

The HTTP Server has encountered internal

error conditions or this point in the code
should not have been reached. The HTTP
process may need restarting if the errors
persist.

[chars]

The HTTP Server has encountered internal

error conditions or this point in the code
should not have been reached. The HTTP
process may need restarting if the errors
persist.

Failure during checkpoint initialization:

[chars]: [chars]

A fatal error was encountered during

initialization.

Init failure during gsp registration: [chars]: A fatal error was encountered during
[chars]
initialization.

The statistics infrastructure has received

an update from a stats collector for which
one or more values are erroneously high,
and may cause the datarate calculation to
wrap. This message indicates a bug exists
Counter overrun for one or more deltas for in the relevant stats collector. The
interface [chars], stats type [unsigned int], collector's node and jid will be indicated in
from collector [chars], on node [chars].
the error message. The output of 'show
Overrun counters: [chars]example overrun statsd collector brief' can be used to
value: [unsigned long long int]
determine what process the JID belongs to.

Statsd manager active replication queue

[chars] queue length [unsigned int], queue The replication queue on active stats
size [unsigned int] bytes
manager crossed threshold/max size limits.

Init failure during evm registration: [chars]: A fatal error was encountered during evm
[chars]
initialization.

Init failure: [chars]: [chars]

A fatal error was encountered during

initialization.

Failed to apply load-interval configuration

for [unsigned int] interfaces: [chars]

The statistics infrastructure failed to apply

load-interval configuration for some
interfaces. This means that the data rates
reported for the affected interfaces (in
'show interfaces', for example) may not
cover the time periods specified in the
running load-interval configuration.

Received a stats message which was

[chars] from sender [chars] on node
[chars].

This stats manager handled a message

which didn't meet the expected size
requirements.

An RP switchover occurred before the

standby stats manager (now active) was
able to complete an initial sync with the
previously active stats manager. As such,
some or all statistics data maintained by
this stats manager may have been lost.
Depending on how much data was
transferred prior to the RP switchover,
some or all statistics may be impacted. The
This Stats Manager has gone active prior to 'last discontinuity' timestamp for each item
completion of initial data transfer of interface statistics will indicate whether
statistics for some or all interfaces may
the statistics for that interface have been
have been cleared.
preserved or not.

Failure during SHMWIN operation: [chars]:

[chars]

A fatal error was encountered during

initialization.

The node on which the process is running

has changed state, but the process was not
able to change the mode in which it is
running to reflect this. The most likely
reason for a state change of this type is an
Failed to handle node state change: [chars] RP failover.

Init failure during sysdb related

operation[chars]: [chars]

A fatal error was encountered during

initialization.

Failed to initialize [chars] thread for

statistics collection: [chars]

One of the threads for statistics collection

could not be started.

Stats type ID lookup for feature '[chars]',

item '[chars]' by client with node [hex], job
[unsigned int] failed. Statistics collection
for this process may not operate correctly.
Error: [chars]

The process that is described by the node

ID and job ID in this message sent a
request for a stats type ID that cannot be
handled. This will result in a failure to
register for statistics collection.

Stats type ID update for feature '[chars]',

item '[chars]', ID [unsigned int], by client
with node [hex], job [unsigned int] failed.
Statistics collection for this process may
not operate correctly. Error: [chars]

The process that is described by the node

ID and job ID in this message sent a
request for a stats type ID that cannot be
handled. This will result in a failure to
register for statistics collection.

A stats collector has timed out during a

request: Node [chars], PID [chars]

The stats collector process that is

described by the Node and PID in this
message has timed out during a stats
request. This may result in some stats
being out of date.

Error waiting for event: [chars].

The event loop has received a message of

a type it does not recognize. All events
should be received by handlers. This
message is only a warning and does not
represent a problem in its own right.

Clear counters on [chars]

Counters on one or more interfaces have

been cleared by the user. This message is
for information only.

Interface CI DLL error:[chars] [dec]

Failed to do DLL operation

Interface CI DLL error:[chars]

Failed to do DLL operation

Failed decode [chars] data, Error : [chars]

Failed to decode data retrieved from

database

Path : [chars], Error : [chars]

Failed to bind to system database.

Interface stats retrieval could fail because
of this error

Failure during initialization. Error: [chars].

A failure occured during the initialization of

the process.

Error while processing event ([chars])

An error occurred while processing an

event at the time stamp server event
manager

Failed to initialize [chars]:[chars]

Time stamp server failed to perform

initialization task. The initialization step
where it failed and the exact error are
mentioned in the message.

[chars]

IPSLA modules are failed to allocate

memory due to low memory conditions in
the System.

MPLSLM([dec]) [chars]: [chars]

IPSLA MPLS LSP Monitor module has failed

to perform an operation.

OP:[dec].[chars].[chars]

IPSLA operation module has failed to

perform an operation.

[chars]:[dec]:[chars]

IPSLA module incurred an internal error.

This could happen in various situations.
Such as system low on memory or
communication failures with other
processes.

Op:[unsigned int] Tree trace for target

address [chars] [chars] (retcode: [chars])

Result of the LSP Path Discovery has

changed for the operation. In case of a
failure, the value of the retcode field
indicates the cause of the failure. Refer to
the Textual Convention
RttMplsVpnMonLpdFailureSense at the
CISCO-RTTMON-MIB for possible reported
causes.

LSP Group status has changed for the

operation. This is a result of some/all of the
ECMPs monitored by the operation
changing their status to Up or Down. Refer
to the Textual Convention
RttMplsVpnMonLpdGrpStatus at the CISCOOp:[unsigned int] for target address [chars] RTTMON-MIB for possible reported status
from [chars] to [chars]
values.
Monitor element has reset the threshold
reaction. Op:[unsigned int], TargetAddr:
[chars], MonElem:[chars]([chars])

A threshold condition has cleared for the

operation

Monitor element has exceeded the

threshold condition. Op:[unsigned int],
TargetAddr:[chars], MonElem:[chars]
([chars])

A threshold condition has raised for the

operation

[chars]

Discovered PE targets has exceeded the

maximum number.

[chars]:id(gid:[dec],nid:[dec],pid:[dec]):
[chars]

An operation on agent table is failed. Error

message displays operation:error.

[chars]:[chars]

A sysdb operation failed. See error

message text for details of error. This may
impact some functionality of IPSLA
depending upon where the error occured.

[chars] Error - [chars]

Failure in check_cidr_knob API, input

parameter is a NULL pointer'

[chars]: memory allocation routine failed

'The system has run out of memory'

sysdb_bind: [chars], [chars]

'Unable to bind to sysdb. The error is

displyed in the error message.'

sysdb_item_get: [chars], [chars]

'Unable to get the item from sysdb. The

error is displyed in the error message.'

[chars]: [chars]

'The call to pthread_mutex_lock() was

unsuccessful'

[chars]: [chars]

'The call to pthread_mutex_unlock() was

unsuccessful'

[chars] Error - [chars]

General error in nvgen client library'

Failed to initialize tracing functionality,

error: ([unsigned int]) [chars].

Initialisation of trace functionality for nvgen

failed. This would affect the debugging of
nvgen.

[chars], '[chars]': Error - '[chars]'

Failure in LWM client API.

Error in checking taskid:'[chars]'

'Special taskid string check against user

taskmap failed'

[chars]: Unable to create an entry for

suspended connection: [dec]

'The call to add_session() was unsuccessful'

[chars]: [chars]

'An API failed due to the mentioned error'

Total length of the comment reached its

limit.

The total length of comment permitted for

a command is 1024. Multiple lines of
comments associated for a command is
considered as a single comment for that
command and the total length of all the
comments would be considered as the total
length of the comment associated to that
command. This allowed limit would
approximate to 10 lines of comments of
width 100. Any more lines of comments will
be discarded.

Failed to locate DLL: [chars] specified in

tree '[chars]'

'An error occurred when trying to open the

dll library specified in command tree. This
failure will cause the command tree
unload.'

Failed to locate function: [chars] in DLL

'[chars]'

'An error occurred when trying to locate the

dll function in DLL.'

Timeout reading file. If tftp, try increasing

the timeout value with config CLI 'tftp
client timeout'. Error: [chars]

'Error while reading the file, Aborting the

connection.'

Unknown or wrong Input: [chars]

'Wrong/Unknown Input'

[chars]: memory allocation routine failed

'The system has run out of memory'

[chars]: Parse error

'Parse error'

[chars]: [chars]: [chars]

'Unable to perform a sysdb api call. The

module which is calling this api, the
description of the api and the error is
displyed in the error message.'

sysdb_bind: [chars], [chars]

'Unable to bind to sysdb. The error is

displyed in the error message.'

sysdb_item_conditional_delete of '[chars]': 'sysdb conditional delete operation failed.

[chars]
The error is displyed in the error message.'

Failed to get datalist for '[chars]': [chars]

'The sysdb operation failed. Error text is

displayed in the message'

Failed to get item in data list for '[chars]':

[chars]

'The sysdb operation failed. Error text is

displayed in the message'

sysdb_item_delete of '[chars]': [chars]

'sysdb item delete operation failed. The

error is displyed in the error message.'

sysdb_item_set of [chars] failed: [chars]

'sysdb item set failed. The error is displyed

in the error message.'

[chars]: [chars]

'The call to pthread_cond_wait() was

unsuccessful'

[chars]: [chars]

'The call to pthread_mutex_lock() was

unsuccessful'

[chars]: [chars]

'The call to pthread_mutex_unlock() was

unsuccessful'

The regex operation failed for some reason.

This may lead to parser errors. The possible
causes are a regex compilation failure or a
memory allocation failure. If the failure
Regex operation ([chars]) failed for pattern: shows up during memory allocation ,
[chars]. Error([chars])
please check memory status for router.

Error on file IO '[chars]': '[chars]'

Unable to read/write the file

Error in file '[chars]' of size : '%zu'

Unable to add command defined under the

file

[chars], error: [chars]

'Initialization of interface manager

connection failed. The failure cause is
mentioned in the error message displayed.'

[chars]: Conversion of ip_addr_t to string

failed

'Conversion of ip_addr_t to string failed'

[chars]: Error in compression ipv6 address

'[chars]' with ipv4 address '[chars]' as it's
subset.

'After compression, ipv4 address in ipv6

address should have been converted into' '
two 16 hexs , but this did not happen.'

Failed to initialize tracing functionality,

error: ([unsigned int]) [chars].

Initialisation of trace functionality for

parser failed. This would affect the
debugging of parser.

[chars], '[chars]': Error - '[chars]'

Failure in LWM client API.

[chars]:Reached testpoint callback limit for Failure in adding a new testpoint callback
callback([pointer])
function.

Only support 1000 aliases

'The system has 1000 aliases limitation'

[chars]: [chars]

'Unable to get the sysDB path of an item

from TTY nmspc library'

can not unpack data for

item/entity([chars]): [chars]

'This error will happen if parser can not

unpack interface encap ' 'info from sysdb.
This information is published in sysdb by
ifmgr ' 'As a result parser may not be able
to parse subinterfaces for ' 'interface
mentioned in the error message. Usually
this error could ' 'happen in the low
memory condition. If this happens analyse
the low ' 'memory situation and once
solved, restart parser_server'.

Error in registering with wdsysmon:'[chars]' 'Error in registering with wdsysmon'

debug_event failed: [chars]

'Debug event logic failed. The reporting

function is listed in the message'

sysdb_notification_register_evm of
'[chars]': [chars]

'The sysdb operation failed. Error test is

displayed in the message'

sysdb_notification_unregister of '[chars]':
[chars]

'The sysdb operation failed. Error test is

displayed in the message'

[chars]: fdopen failed: [chars]

'The call to function fdopen failed. The

error message is displayed in the message'

Failed lock operation '[chars]' during

'[chars]'. Error:[chars]

A lock operation for synchronising shared

resource, failed due to the mentioned error.

[chars]: [chars]

Initialization of functionality in getline

library failed for reason mentioned in the
error message. The whitespace completion
behaviour could not be modified.

[MDACon] While aborting a bulk operation

the following error occurred:\n[chars]

An error occurred invoking an MDA

function. The details are in the error string.

[MDACon] While aborting a transaction the An error occurred invoking an MDA

following error occurred:\n[chars]
function. The details are in the error string.
[MDACon] Unable to handle the large
number of elements in data array

The number of elements entered by user in

an array are more than this application is
designed to handle.

[MDACON] Invalid class name - [chars]

An invalid class name was entered either

by itself or as part of a hierarchy string.

[MDACON] Invalid filter name - [chars]

An invalid filter name was entered for the

related class.

[MDACon] Badly formatted [chars]

The command entered is badly formatted.

[MDACON] Invalid hierarchy - [chars]

An invalid hierarchy was entered by the

user.

[MDACon] Invalid option - [chars]

The command option is invalid

[MDACon] Could not bind to the MDA:

[chars]. MDACon cannot carry out any
operations. XML agent (either corba or tty)
needs to be configured to execute MDACon
- try quitting and restarting it after
configuring 'xml agent (corba|tty)'

MDACon was unable to bind to MDA. It is

possible that there is a problem with MDA
or the Schema Server, or the
communication infrastructure.

[MDACon] While committing a transaction

the following error occurred:\n[chars]

An error occurred invoking an MDA

function. The details are in the error string.

[MDACon] While copying object [chars] to

[chars] the following error
occurred:\n[chars]

An error occurred invoking an MDA

function. This could be because the object
to copy does not exist. The details are in
the error string.

An error occurred invoking an MDA

function. This could be because the object
[MDACon] While creating object [chars] the to create already exists. The details are in
following error occurred:\n[chars]
the error string.

[MDACON] Too little or too much [chars]

provided for class [chars]

The number of elements entered for a data

array does not match the expected value.

[MDACON] Invalid [chars] entered for class The datatypes entered in a data array do
[chars]
not match the the expected datatypes.

An error occurred invoking an MDA

function. This could be because the object
[MDACon] While deleting object [chars] the does not exist. The details are in the error
following error occurred:\n[chars]
string.

[MDACon] While ending a bulk operation

the following error occurred:\n[chars]

An error occurred invoking an MDA

function. The details are in the error string.

[MDACon] Not enough memory

MDACon was unable to allocate enough

memory required to process the command

[MDACon] While listing the errors which

occurred in the previous operation the
following error occurred:\n[chars]

An error occurred invoking an MDA

function. The details are in the error string.

[MDACon] While listing the operations

which have been made within the current
bulk operation, the following error
occurred:\n[chars]

An error occurred invoking an MDA

function. The details are in the error string.

[MDACon] Excess tokens in command

string

There were more tokens entered as part of

the command string than are required for
the command.

The file specified for reading instructions

from, or writing output to, when MDACon
was started, cannot be found. The most
[MDACon] The specified file ([chars]) could probable reason is that an incorrect
not be opened for [chars]
incorrect name or path was supplied.

[MDACon] Unable to read from command

file

An error occurred during a read operation

from the instruction file.

[MDACON] While executing the find data or

finddata_next request, the following error An error occurred invoking an MDA
occured:\n[chars]
function. The details are in the error string

An error occurred invoking an MDA

function. This could be because the object
[MDACon] While fetching object [chars] the to fetch does not exist. The details are in
following error occurred:\n[chars]
the error string.

Invalid Arguement. Null paramater passed

[MDACon] Insufficient number of tokens in as part of sysdb path. Please enter a valid
command string
sysdb path.

[MDACon] While executing the list request An error occurred invoking an MDA
the following error occurred:\n[chars]
function. The details are in the error string.

[MDACon] Mismatched quotes or brackets

in command

An unmatched ''' or '{' character was found

part way through a token in a command
string.

The command entered requires a

[MDACon] Missing destination object name destination object name or path and one
or path.
was not supplied.

[MDACon] Missing filter name

The command entered requires a filter

name and one was not supplied.

[MDACon] Missing number

The command entered requires a number

and one was not supplied.

[MDACon] Missing start object naming

information

The command entered requires naming

information of start and one was not
supplied.

[MDACon] Missing object value

The command entered requires an object

value and one was not supplied.

[MDACON] Class [chars] is not a leaf

The entered class name is not a leaf class,

as is expected by the command.

[MDACon] Unable to initialize the command An error occurred while preparing to read
line reader
instructions from the command line.

[MDACon] While setting object [chars] the

following error occurred:\n[chars]

An error occurred invoking an MDA

function. This could be because the object
does not exist or has the wrong type. The
details are in the error string.

[MDACon] While starting a bulk operation

the following error occurred:\n[chars]

An error occurred invoking an MDA

function. The details are in the error string.

[MDACon] While starting a transaction the

following error occurred:\n[chars]

An error occurred invoking an MDA

function. This could be because the
timeout time was not correctly entered.
The details are in the error string.

[MDACon] While determining the MDA

object instance which corresponds to the
SysDB path, the following error
occurred:\n[chars]

An error occurred invoking an MDA

function. The details are in the error string.

[MDACon] While requesting the AAA task

names of a hierarchy point, the following
error occurred:\n[chars]

An error occurred invoking an MDA

function. The details are in the error string.

[MDACon] Verification failed on object

[chars] for the following reason\n[chars]

An error occurred invoking an MDA

function. This could be because the object
does not exist or has the wrong type. Or
because the verifier did not allow the
change. The details are in the error string.

[MDACon] No such command - [chars] Type The first token in a command string was
help or ? for a list of available commands
not a recognised MDACon command.

[MDACon] [chars]%s:\n[chars]

The code has performed an action which

should not be possible.

Could not apply verified config: [chars]

This is an error message in the Netflow

manager to indicate that due to specified
reasons, it was unable to apply the
configuration that it had previously verified
and accepted. This errmsg usually means
that the netflow running config and netflow
operational state are out of sync.

Could not apply configuration: [chars]

This message indicates that a configuration

that was previously verified cannot be
applied due to the reason specified. This
may happen if a configuration that was
applied to a Bundle interface cannot be
applied due to either resources not being
available in the Line Card where the
member resides, or some configuration
mismatch was detected.

This is an informational message to

Cache size of [dec] for monitor [chars] has indicate that the specified flow monitor
been exceeded
map cache size has been exceeded.

Nonfatal error: [chars]

This is an error message in the Netflow

manager to indicate anomolies which are
not FATAL. Some of the messages may
indicate a failure to allocate a resource
needed by the application. In many cases
these messages must not keep appearing
after the temperory situation is resolved.

[chars]: Invalid argument

'Invalid argument has been passed to the

function'

[chars]: basename of: [chars]

'The call to basename failed. The error is

displayed in the message'

[chars]: bgcoption missing ',' after id:

'[chars]'

'The input is invalid. The calling function

and the command are displayed'

[chars]: blank enter tuple template

ptr:0x[pointer] ref 0x[pointer] : [chars]

'The enter tuple is blank. The calling

function and enter tuple are displayed in
the message'

[chars]: new_cmd buffer null

'The command buffer is invalid. The calling

function is displayed in the message'

[chars] [chars]

'Nvgen server could not initialize the CFS'

[chars]: Coption Not Present:'[chars]'

'Coption is missing in the command. The

calling function and the command are
displayed in the message'

Failed to generate '[dec]' configuration

lines for the requested operation.

Nvgen server failed to convert sysdb tuple

into readable config command. This may
result in failure to show some of the
configuration or in in writing configurations
to internal config backup.

[chars]: sysdb_string_decode of '[chars]':

[chars]

'The sysdb decode operation failed. The

error message is displayed in the message'

[chars]: Error on directory '[chars]' during

'[chars]': '[chars]'

Unable to open/create the directory

[chars]: Incomplete endcoption mark for

[hex]: '[chars]', new cmd: '[chars]'

'end option mark is incomplete in the

command. The calling function the coption
id and the commands are are displayed in
the message'

'end option mark is missing a comma in the

command. The calling function the coption
[chars]: Missing comma in endcoption mark id and the command are are displayed in
for [hex]: '[chars]'
the message'

[chars]: No endcoption mark for [hex]:

'[chars]'

'end option mark is missing in the

command. The calling function the coption
id and the command are are displayed in
the message'

[chars]: The call to ovl_setup_env() failed

'Could not update environment variables

due to the error'

Unknown DLL [chars] in tree '[chars]'

'The nvgen try to load an unknow dll in the

specified tree'

Failed to locate function: [chars] in DLL

'[chars]'

'An error occurred when trying to locate the

dll function in DLL.'

[chars]: memory allocation routine failed

'The system has run out of memory'

[[dec]] [chars]: memory allocation routine

failed

'The system has run out of memory'

[chars]: [chars]: [chars]

'Unable to perform a sysdb api call. The

module which is calling this api, the
description of the api and the error is
displyed in the error message.'

sysdb_bind: [chars] [chars]

'Unable to bind to sysdb. The error is

displyed in the error message.'

[chars] while accessing [chars]

'An error occurred while accessing sysdb.

The error is displayed in the error
message.'

sysdb_list of '[chars]': [chars]

'The sysdb operation failed. Error text is

displayed in the message'

Nvgen server failed to set an item in sysdb

database. The item name is part of the
error. This may result in failure to generate
running config properly in show run
command. Or an impact may be seen
Unable to set item in sysdb:[chars]: [chars] during the internal config backup.

[chars]: pthread_cond_wait of: [chars]

'The call to wait on a condition failed. The

error is displayed in the message'

[chars]: pthread_create of : [chars]

'The call to pthread_create failed. The error

text is displayed in the message'

[chars]: pthread_join of: [chars]

'The call to pthread_join failed. The error is

displayed in the message'

[chars]: pthread_mutex_lock of: [chars]

'The call to lock a mutex failed. The error is

displayed in the message'

[chars]: pthread_mutex_unlock of: [chars]

'The call to unlock a mutex failed. The error

is displayed in the message'

[chars]: Failed to attach event handler:

[chars]

'The call to attach nvgen requst handler to

event manager failed. The error is
displayed in the message'

[chars]: event_block failed : [chars]

'The call to event block in parser server

failed. Parser may exit in this case. The
error is displayed in the message'

[chars]: event_manager_create failed :

[chars]

'The call to create parser event manager

failed. The error is displayed in the
message'

[chars]. Pattern: [chars]

'The regcomp function failed for some

reason. This may lead to NVGEN errors.

[chars]: Error on compressing file in

'[chars]': '[chars]'

Unable to compress the file

[chars]: Error on file IO '[chars]' for

'[chars]': '[chars]'

Unable to read/write the file

[chars]: Unable to open file '[chars]' for

'[chars]': '[chars]'

Unable to open the specified file. The error

is mentioned as part of the message. This
could impact the show run functionality or
cause the config loss at upgrade or reload.
If this error has happened at the time of
doing copying configuration to a file, then
copy will not be successful. If this happens
during internal system configuration
backup then certain configuration will not
be updated in the backup. This could result
in the config loss at next reboot. If this
happens during nvgen server process
restart or during initialization after a
pie/package upgrade then either command
files or config order or partition files are not
opened. In which case certain config lines
will be missing in the show run.

[chars]: [chars]

'Nvgen server encountered an error, see

message for more details'

Nvgen server obtained an incorrect cli

template config tuple from system
database. This may result in failure to
generate complete template configuration
in show run command. Or in internal config
Incorrect CLI template tuple:[chars]: [chars] backup.

'The enter string is illegal. The calling

[chars]: Illegal enter string '[chars]' on cmd function and enter string and command are
'[chars]'
displayed in the message'
'The enter tuple is invalid. The calling
[chars]: Illegal enter tuple '[chars]' for cmd function and enter string and command are
'[chars]'
displayed in the message'
[chars]: Call to install_proc_ready failed
with id: [dec] error: [chars]

'nvgen_server got an error return from

calling install_proc_ready'

[chars]: interface name is NULL

'Interface name send for parsing is NULL.'

'interfaces during nvgen are ordered based

on logical intf or slot/' '/port/sub-intf. This
[chars]: display of interfaces may not be in ordering failed due to the mentioned
order. Name: [chars] Error: [chars]
reason'
[chars]: Unable to get information about
interface - [chars]

'Interface Manager API im_is_hw_interface

was not successful.'

[chars]:Invalid nvgen generic ipv4/6 flag.

[dec].

'generic ipv4/6 nvgen flags are incorrect.

Probably error in ' 'dumping the flags.'

[chars]:Invalid flag in ipv6address

template. [dec].

' ipv6 nvgen flags are incorrect. Probably

error in ' 'dumping the flags.'

[chars]: Unknown or unsupported ovl

notification: [dec]

'nvgen_server got an invalid notification

form ovl process'

Incorrect ordering info read from order

table at:[chars]

Nvgen server obtained an incorrect order

list entry from an internal order file. This
may result in the show run output to have
a different ordering than intended.

[chars]: invalid input (no 'B'): '[chars]'

'The input is invalid. The calling function

and the command are displayed'

'The Number output format specification is

not in the number input format
Input format(s) do not match output format specification, so we are writing a number
in: '[chars]'
that we probably cannot read back in'

[chars]: invalid NXCOPTION mark:'[chars]'

'The input is invalid. The calling function

and the command are displayed'

Invalid template file:'[chars]'

'The template in this file is invalid or wrong

version'

nvgen (version: [dec].[dec]) cannot handle

version [dec].[dec] of nvgen template in
component '[chars]'
'The version of this file is too old or wrong'
[chars]: [chars]: [chars]
'The path of the tuple is invalid'

A lock operation on shared resource, called

Failed lock operation '[chars]'. Error:[chars] by nvgen failed due to the mentioned error.
[chars]: Failed to register for ipaddress
mask in prefix format. [chars]

'The call to register the maskformat in

prefix form failed. The error is displayed in
the message'

[chars]: Failed to initialize ipaddress mask

in prefix format.[chars]

'The call to initialize the maskformat in

prefix form failed. The error is displayed in
the message'

The length: [unsigned int] of the message: 'The message length must be greater than
'[chars]' is less than minimum message
minimum message length. The minimum
length
message length varies by request code.'
'The '<' is missing in sysdb string. The
[chars] : [chars]: missing '<' in sysdb string sysdb string and the command are
'[chars]' for command '[chars]'
displayed in the message'

'The equal is missing in sysdb string. The

[chars]: [chars]: missing '=' in sysdb string sysdb string and the command are
'[chars]' for command '[chars]'
displayed in the message'
[chars]: MsgReadv of: [chars]

'The call to MsgReadv failed. The error is

displayed in the message'

Failed a namespace operation ([chars]).

Partition([chars]), Error:[chars]

Nvgen server failed to build config

namespaces from internal namespace
module. This may result in failure to output
the configuration in the intended order in
show run command. Or in internal config
backup.

[chars]: incorrect nested coption:'[chars]'

'The input is invalid. The calling function

and the command are displayed'

The message is not null terminated.

'Parser messages must be null terminated.'

[chars]: [chars]: Unknown object type

[unsigned int] in replace_type

'The object type in the replace_type is

invalid. The objtype is displayed in the
message'

[chars]: open of [chars] failed : [chars]

'The call to open() failed. The error is

displayed in the message'

Could not get partitions names from

cfgmgr: [chars]

'Nvgen server could not get the changed

partition names from cfgmgr'

[chars]: Pattern:'[chars]' not found in

template '[chars]'.

Taskid pattern not found where it was

expected.

[chars]: read failed: [chars]

'The call to function read failed. The error

message is displayed in the message'

[chars]: Failed to register with installmgr

for software change notification : [chars]

'The call to register for notification from

install mgr failed. The error is displayed in
the message'

[chars]: event_resmgr_attach of : [chars]

'The call to attach to parser resource

manager failed. The error is displayed in
the message'

[chars]: rm_init failed

'The call to init rm failed. The error is

displayed in the message'

[chars]: Unable to shrink ipv4_6address:

'[chars]'

Shrinking of expanded ipv4_6address

failed.

[chars]: Failed to register for slot order

display for interfaces. [chars]

'The call to register the slot order display

failed. The error is displayed in the
message'

[chars]: slot order initialization failed :

[chars]

'The call to initialize slot order failed. The

error is displayed in the message'

[chars]: stat of [chars] failed: [chars]

'The call to stat() failed. The error is

displayed in the message'

'The end mark is missing in the submode

[chars]: get_submode_string: no end mark: string. The submode is displayed in the
[chars]
message'
sysdb_operation of [chars] : '[chars]':
[chars]

'The sysdb find data operation failed. The

error is displayed in the message'

[chars]:Failed to create target config:

[chars].

Nvgen client failed to create target config

buffer. Configuration can not proceed.

[chars]:Failed to destroy target config:

[chars]

Nvgen client failed to destroy target config

buffer.

[chars]:Failed to obtain exclusive lock for

this session:[chars]

Nvgen client failed to obtain exclusive lock

for this session. Terminate the other open
sessions and try again.

[chars]:Failed to release the lock held by

session:[chars]

Nvgen client failed to release exclusive lock

held by this session.

[chars]: aaa_compare_tasktable_alt failed! 'nvgen_server got an error from calling

Error: '[chars]'
aaa_compare_tasktable_alt.'

[chars]: Number of taskid in .parser exceed

maximum taskid limit for
Number of taskid found in .parser
template :'[chars]'
exceeded the maximum limit.

[chars]:Taskid found but number of taskid

is 0:'[chars]'

Total number of taskid for the template is

0, but taskid struct is not NULL.

[chars]: Taskid not found, where it is

expected:'[chars]'

Taskid not found, but total number of taskid

is greater than 0.

[chars]: [chars]: Possible loop detected in

command '[chars]'

'The token number is invalid. The

command is displayed in the message'

[chars]: token [dec], old type:[dec], new:

[dec] cmd:'[chars]'

'The token type is invalid. The calling

function, token number and token type is
displayed in the message'

[chars]

'Filter coption index is not zero. There could

be unmatched coptions'

Aborting update of startup configuration.

[chars].

Failed to get the startup config file name or

run out of space on disk or some other
transient error.

Generation of configuration in ASCII format

has failed. During periodic backup
Generation of configuration in ASCII format operation this may lead to internal backup
failed due to internal error. The file '[chars]' files not getting updated with recent config
was not updated
changes

[chars]: [chars]: [chars]

'An API failed due to the mentioned error'

Bogus hook point index [unsigned int]

'Bogus hook point'

Bogus link point index [unsigned int], sub

system:[chars], offset:[hex], mask:[hex]

'Bogus link point'

[chars]

'buffer overflow'

Unable to get card number and module

Parser relies on invmger API to get card
number from nodeid: '[unsigned int]' Error: number and module number. But the API
'[chars]'
had failed.

Failed to create parse thread: [chars]

'pthread_create() API failed due to

mentioned error'

[chars]: The call to ovl_setup_env() failed

'Could not update environment variables

due to the error'

[chars]: [chars]
bag decode error ([chars])

'Parser encountered error, see message for

more details'
'Failure to decode the bag.'

sysdb_item_get of '[chars]': [chars]

'sysdb item get operation failed. The error

is displyed in the error message.'

[chars]

'Sysdb path has string that has special

character without sysdb_encode flag'

[chars]:[dec]:[chars]

Nodeid conversion API has failed.

Extracting rack/slot/module from '[chars]'

failed

Parser unable to get rack/slot/module field

from path.

Unknown or unsupported ovl notification:

[dec]

'parser_server got an invalid notification

form ovl process'

Invalid parser file: [chars]

'Invalid parser file'

Invalid details pointer 0x%zx at offset 0x

%zx tokentype [hex] in tree '[chars]'

'The offset to the token details structure is

bogus'

'The Number output format specification is

not in the number input format
Input format(s) do not match output format specification, so we are writing a number
in: '[chars]'
that we probably cannot read back in'
Invalid offset [hex] from offset [hex] in tree
'[chars]'
'The offset into the parser tree file is bogus'
Invalid [chars] range <[unsigned int],
[unsigned int]> in tree '[chars]'

'The numerical range within the token

details structures is invalid'

parser version is [dec].[dec] cannot handle

version [dec].[dec] of command chain in
component '[chars]'.Please do Jam clean
and build the image.
'The version of this file is too old or wrong'.

Duplicate entries in inventory db for

'[chars]'

Duplicate entries found in inventory

database.

Increasing inventory database size from

'%zd' to '%zd' failed

Inventory database size increase failed.

Can happen only if memory is too low.

Inventory database size is Zero

Inventory database size is zero. Can

happen only if memory is too low.

Description pointer is null

Description string is null.

'[chars]' is NULL

Error in extracting rack/slot/module name

from sysdb path.

'[chars]' is not a number

Rack/slot/module are stored as sysdb path

in inventory DB. They are essentially
numbers. So either rack/slot/module are
not numbers, or the path is incorrect.

Failed lock operation '[chars]' during

'[chars]'. Error:[chars]

A lock operation on shared resource, called

by parser failed due to the mentioned error.

mmap of file '[chars]'

'mmap of file'

Unable to create nodeid for ([dec],[dec],

[dec]): error:'[chars]'

Error in getting rack/slot/module numbers

from system database.

Unable to convert nodeid:'[dec]' to string

Error in conversion routine.

NULL notification path

Parser received notification from NULL

path.

Unable to find the parser object '[dec]'

which is used as range

'The range value was given as a parser

object ,but object could not be found'

'[chars]' overflows ambig_line '[chars]'

'Help string overflows ambig_line'

[chars]:[dec]:[chars]

Nodeid conversion API has failed.

Regex compilation error:[dec] '[chars]'

Regex compilation error has occured. The

command line execution would either fail
or would not show proper result.

Right arg([dec]) type unsupported: [dec]

'The test token has invalid right argument'

[chars]: Can not find submode : [chars]

'The call to parser_submode_find failed to

find submode. The error is displayed in the
message'

[chars]: sysdb_action: [chars]

'Unexpected error in sysdb call. The error is

displayed in the message'

Exceeded '[unsigned int]' of taskids in a

command

'A command can have only

MAX_TASKIDS_PER_COMMAND different
taskids'

An unexpected error caused failure to

increase the maximum limit of
management connections to the device.
This error would affect the user only if he
Failed to increase the maximum limit of
tries to have the number of management
management connections. An unexpected connections above an approximate count
error has occured, error: ([dec]) [chars].
of 25.

'sysdb tuple unmask operation failed. The

sysdb string is displyed in the error
[chars]: tuple_unpack_mask failed: '[chars]' message.'
Unknown token type [hex] at offset [hex] in 'The parser token type is undefined in the
tree '[chars]'
specified tree'

Unresolved hookpoint '[chars]' at chain

'[chars]'

'Unresolved hookpoint'

Failed to resolve linkpoint '[chars]' specified

in chainname '[chars]' in '[chars]' file.
'Unresolved linkpoint'
[chars]: [chars]([dec]) is of unsuppored
type: [dec]

'left/right argument is of unsupported type'

LRd event failed: [chars] Error: '[chars]'

Registration to LRd failed.

[chars] : [chars]

An error has occurred while doing a

checkpointing operation. This may result in
loss of old statistics data during process
restart.

[chars]: [chars]: [chars]

An error has occurred while dumping of the

collected data from the pm collector
process. This error could error due to
various reasons below : a) Local disk is full
or something wrong. b) TFTP server is not
reachable. c) TFTP directory configured
does not have write permissions.

[chars]

The system is running out of memory and

was not able to allocate sufficient memory
to carry out a collection operation.

[chars]:[chars]

Perfmgmt server could not restore

configured memory thresholds. Perfmgmt
server will restore the defaults for memory
limits.

[chars]:[chars]:[chars]

An error has occurred while tftp dumping of

the collected data from the pm collector
process. This error could error due to
various reasons below : a) No tftp server
configure in pm configuration. b) TFTP
Server is not reachable. c) TFTP Directory
configured does not have write
permissions.

[chars]: [chars]
[chars]

An informational alarm upon dumping of

the collected data
This is an informational message.

[chars]:[chars]

An informational alarm upon dumping of

the collected data on to tftp server.

Entity:[chars], Id:[chars] - Attribute:[chars]:

value:'[unsigned long long int]' threshold: The Entity Instance has met a threshold
[chars], threshold-op:[chars]
condition.

[chars] : [chars]

An error has occurred while doing a sysdb

operation. See the message text for error
details.

[chars]: '[dec]' : [chars]

The Collector has detected an internal

error. Reason of the error is in the message
itself. Some of the errors are self
recovering.

[chars]: [hex]: [chars]

A wdsysmon api call returned an error. This

can happen when the state of a node is
transitioning e.g. a line card is restarted or
the node is not booted. The node id is
given by the hexadecimal number after
this message and is followed by a more
specific error description of the cause of
the failure.

Failed to open bootvar file, [chars] ([dec])

Failed to open bootvar file.

Configure sync failed and migration

aborted

If the source device boots from a nondefault disk disk0 check rommon variable
BOOT_DEV_SEQ_OPER on the destination
node correct the setting if necessary and
retry migration If the problem persists refer
to upgrade MOP for more information.

sysmgr_mbi_boot_hold failed, [chars],

([dec])

The function sysmgr_mbi_boot_hold failed.

sysmgr_mbi_boot_unhold failed, [chars]

([dec])

The function sysmgr_mbi_boot_unhold

failed.

Process address space file IO failure for

[chars], [chars], ([dec])

IO failure on process address space. Unable

to detect board type.

SNMP sync failed and migration aborted

If the source device boots from a nondefault disk disk0 check rommon variable
BOOT_DEV_SEQ_OPER on the destination
node correct the setting if necessary and
retry migration If the problem persists refer
to upgrade MOP for more information.

Failed to spawn the 'cp' process Unable to

start copying configuration from active RP
spawn a 'cp' process failed, [chars] ([dec]) to PRP.

Failed to spawn the 'rm' process. Unable to

spawn a 'rm' process failed, [chars] ([dec]) remove existing configuration from PRP.
waitpid for the 'cp' process failed, [chars]
([dec])

waitpid for the 'cp' process failed

Configuration copy thread terminated
incorrectly.

waitpid for the 'rm' process failed, [chars]

([dec])

waitpid for the 'rm' process failed.

Configuration removal thread terminated
incorrectly.

Successfully sync'ed configure files: [chars]

([dec])
Sync successfully completed.
Sync'ing configure files from '[chars]'

Status information while starting config file

sync.

Trying to start unconfigured console

session anyway.

The RS232 DLL tried to apply a template to

the console and failed, but we are
attempting to start a session anyway to try
and ensure that it's possible to log onto the
router from the console. This may mean it's
impossible to gain terminal access any
other way (ie via telnet, ssh, etc).

The RS232 driver encountered an error

retrieving the baud rate for the console;
default to a value of [unsigned int]: [hex]
'[chars]'.

The console baud rate is retrieved from the

configurate register. Problems were
encounted during this operation.

Error in cable monitor thread. '[chars]

([dec])'. Please restart '[chars]' to enable
this functionality.

Failure in cable monitoring function. Since

this functionality is not so important in
console driver, any error in this thread will
be reported through syslog and thread will
retire. Errors are failure in malloc or
pthread operation and if such basic
functions fail, then it might mean system is
in bad shape. So we're not sure restarting
this process will recover the situation. To
avoid worst case -lose console/aux
accessibility-, this process will remain
without cable disconnect function.
Operator might want to restart this process
if this functionality is required in which this
router is physically located, such as
datacenter or co-location house.

The UART driver encountered an framing

error for [chars] port

UART encountered Framing error

The RS232 driver encountered an error

making a kernel call

The RS232 driver has made a kernel call

which is failing; it cannot proceed.

Failed to process Line connect request

because of '[chars]' (category:[dec] port:
[dec] rc:[dec]). Connect the cable tightly

Failed to process connect request.

The UART driver encountered an over run

error for [chars] port

UART encountered over run error

The UART driver encountered an parity

error for [chars] port

UART encountered parity error

Failed to close the existing session because

of '[chars]' (category:[dec] port:[dec] rc:
[dec]). If session should be closed, please
issue 'clear line' command
Failed to close session.
Couldn't acquire mutex to notify [chars]
(category:[dec] port:[dec] rc:[dec]). If
session should be closed, please issue
'clear line' command

Failed to notify line status change.

The TTY is not registered with the TTY

Server

The RS232 DLL tried to perform an

operation on a TTY that isn't registered
with the TTY Server.

Unable to find the desired details in a

loaded DLL

The RS232 DLL was unable find the details

required from a DLL it had loaded.

The RS232 DLL was unable to open a DLL

(error: [chars]([dec]))

The RS232 DLL was unable to open a DLL.

The RS232 DLL was unable map from a TTY The RS232 DLL was unable map from a TTY
ID to a UART port
ID to a UART port

Unable to allocate memory for TTY

structures

The RS232 DLL was unable allocate the

necessary memory it required to hold
details about the TTYs.

Packet mode sessions are not yet

supported on RS232 TTYs

The TTY Server informed the RS232 DLL

about a packet mode session, but we don't
yet support packet mode.

The RS232 DLL was unable to set the

persistant data path

The RS232 DLL has failed to enable the

persistant data path for a TTY.

The RS232 DLL was unable to setup a

session on a TTY

The RS232 DLL has been unable to setup a

session on a TTY

The RS232 DLL encountered an error trying The RS232 DLL tried to apply a template to
to apply a template.
a TTY but failed.

The RS232 DLL encountered an error trying The RS232 DLL tried to deapply a template
to deapply a template.
to a TTY but failed.

Discovered data carrier detect signal

(category:[dec] port:[dec])

The RS232 driver discovered Data Carrier

Detect signal.

Lost data carrier detect signal (category:

[dec] port:[dec]). Existing session will be
closed.

The RS232 driver lost Data Carrier Detect

signal. Process will close existing session.

Unable to map calendar chip

Unable to map calendar chip.

No NMI Info

Unable to get NMI info from platform..

Calendar Chip doesn't exist on this HW

Unable to find calendar chip.

[chars]: mmap'ed. address([hex])

calendar_chip([hex])

Mapping calender chip address to process

address space.

[chars].[dec]\n

Printing value of current time.

[chars]: [char]

Printing option entered in command line.

[chars]: write_chip([chars])
set_system([chars]) calendar([chars])
boottime([chars])

Printing value of write_chip, set_system,

calender and boot time flag set based on
arugment.

[chars] : [chars]

Printing type of time (BCD/Binary).

[chars]: [chars]: tm_sec([hex])

tm_min([hex]) tm_hour([hex])
tm_mday([hex]) tm_mon([hex])
tm_year([hex])

Printing value of time in

sec:min:hour:day:month:year.

***** [chars] *****: READ from [dec].

nmi_enabled [dec]

Reading value of NMI enabled flag from

CMOS.

[chars]: RTC Config Reg([hex])

Reading value of RTC config register.

[chars]: Read from RTC sec([hex])

Reading value of RTC at particular time.

READING FROM [hex]: val [hex]

Reading value of calendar chip at offset.

***** [chars] *****: WRITE to [dec] Val

([hex]). nmi_enabled [dec]

Writing value of NMI enabled flag to CMOS.

[chars]: Writing to RTC: sec([hex]).

reg_b([hex])

Writing current unix date and time to

calender chip.

WRITING TO [hex]: val [hex]

Writing value to calendar chip at offset.

Unable to signal on the status variable

The S2681 UART driver was unable to

signal that that status variable was ready
to be read.

Unable to unmask UART interrupt (error:

[chars]([dec]))

The S2681 UART driver has been unable to

unmask the UART interrupt.

Unable to obtain permission to access

UART (error: [chars]([dec]))

The S2681 UART driver has been unable to

gain the required permissions to access the
UART.

Unable to lock the UART (error: [chars]

([dec]))

The S2681 UART driver has been unable to

lock access to the UART.

Unable to unlock the UART (error: [chars]

([dec]))

The S2681 UART driver has been unable to

unlock access to the UART.

Unable to raise the priority of the interrupt The S2681 UART driver was unable to raise
handler
the priority of the interrupt handler.

Unable to set the parameters for the

interrupt handler

The S2681 UART driver was unable to set

the parameters of the interrupt handler.

Unable to set scheduling policy for the

interrupt handler.

The S2681 UART driver was unable to set

the scheduling policy for the interrupt
handler.

Unable to lock the status variable.

The S2681 UART driver was unable to lock

the status variable for the interrupt thread.

Unable to unlock the status variable.

The S2681 UART driver was unable to

unlock the status variable for the interrupt
thread.

Unable to create the interrupt handler

thread.

The S2681 UART driver was unable to

create a thread for the interrupt handler.

Unable to create statistics file (error:

[chars]([dec])).

The S2681 UART driver was unable to

create a file to store statistics. Show
statistics command would fail. We can still
see the statistics content from core file.

[xml-schema] Unable to handle the large

number of elements in data array

The number of elements entered by user in

an array are more than this application is
designed to handle.

[xml-schema] [chars]%s:\n[chars]

An error occurred invoking an AAA

function. The details are in the error string

[xml-schema] Invalid class name - [chars]

An invalid class name was entered either

by itself or as part of a hierarchy string.

[xml-schema] Badly formatted [chars]

The command entered is badly formatted.

[xml-schema] Invalid hierarchy - [chars]

An invalid hierarchy was entered by the

user.

[xml-schema] Invalid option - [chars]

The command option is invalid

[xml-schema] Could not bind to the MDA:

[chars]. XML schema browser cannot carry
out any operations. XML agent (either
corba or tty) needs to be configured to
execute XML schema browser - try quitting
and restarting it after configuring 'xml
agent (corba|tty)'

XML schema browser was unable to bind to

MDA. It is possible that there is a problem
with MDA or the Schema Server, or the
communication infrastructure.

[xml-schema] Too little or too much [chars] The number of elements entered for a data
provided for class [chars]
array does not match the expected value.

[xml-schema] Invalid [chars] entered for

class [chars]

The datatypes entered in a data array do

not match the the expected datatypes.

[xml-schema] Not enough memory

XML schema browser was unable to

allocate enough memory required to
process the command

[xml-schema] Excess tokens in command

string

There were more tokens entered as part of

the command string than are required for
the command.

[xml-schema] The specified file ([chars])

could not be opened for [chars]

The file specified for reading instructions

from, or writing output to, when XML
schema browser was started, cannot be
found. The most probable reason is that an
incorrect name or path was supplied.

[xml-schema] Unable to read from

command file

An error occurred during a read operation

from the instruction file.

[xml-schema] While executing the walk

data or walkdata_next request, the
following error occured:\n[chars]

An error occurred invoking an MDA

function. The details are in the error string

An error occurred invoking an MDA

function. This could be because the object
[xml-schema] While fetching object [chars] to fetch does not exist. The details are in
the following error occurred:\n[chars]
the error string.

[xml-schema] [chars]%s:\n[chars]

The code has performed an action which

should not be possible.

[xml-schema] While executing the list

request the following error
occurred:\n[chars]

An error occurred invoking an MDA

function. The details are in the error string.

[xml-schema] Mismatched quotes or

brackets in command

An unmatched ''' or '{' character was found

part way through a token in a command
string.

[xml-schema] Class [chars] is not a leaf

The entered class name is not a leaf class,

as is expected by the command.

[xml-schema] Unable to initialize the

command line reader

An error occurred while preparing to read

instructions from the command line.

[xml-schema] No such command - [chars]

Type help or ? for a list of available
commands

The first token in a command string was

not a recognised XML schema browser
command.

A schema version change has occurred due

to the [chars] of schema file '[chars]'. Any
management applications which use the
schema may wish to update to the
appropriate schema version.

The version of some part(s) of the schema

which are running on the router have
changed - this is an informational message
to let any users of the schema know of the
change.

An internal error has occurred in the

schema server or library. Some
The schema infrastructure has encountered management functions may not operate
an error. [chars]
correctly.

[chars] [dec]: [chars]

Restarting the process as it is not in a

recoverable state.

[chars] [dec]: [chars]

Error encountered while Backing up the

ASCII System Configuration.

Reload([dec]) fail to reply to svr Sconbkup

on [chars] [chars]. Error([dec]): [chars].

Error encountered while replying message

during ASCII System Configuration.

Sconbkup([dec]) fail to reply to

Reload([dec]) on [chars] [chars].
Error([dec]): [chars].

Error encountered while replying message

during ASCII System Configuration.

A serial interface error has occured (error:

[chars], details: [chars]).

General error message for the linux serial

interface.

Unable to mask UART interrupt (error:

[chars]([dec]))

The ST16550 UART driver has been unable

to mask the UART interrupt.

Unable to unmask UART interrupt (error:

[chars]([dec]))

The ST16550 UART driver has been unable

to unmask the UART interrupt.

Unable to obtain permission to access

UART (error: [chars]([dec]))

The ST16550 UART driver has been unable

to gain the required permissions to access
the UART.

Too many console line state change

interrupts

The ST16550 UART driver received too

many interrupts within 1 second

Unable to lock the UART (error: [chars]

([dec]))

The ST16550 UART driver has been unable

to lock access to the UART.

Unable to unlock the UART (error: [chars]

([dec]))

The ST16550 UART driver has been unable

to unlock access to the UART.

Unable to raise the priority of the interrupt The ST16550 UART driver was unable to
handler
raise the priority of the interrupt handler.

Unable to set the parameters for the

interrupt handler

The ST16550 UART driver was unable to set

the parameters of the interrupt handler.

Unable to set scheduling policy for the

interrupt handler.

The ST16550 UART driver was unable to set

the scheduling policy for the interrupt
handler.

Unable to perform '[chars]' operation on

semaphore ([chars]).

The ST16550 UART driver was unable to

perform semaphore operation for interrupt
handler.

Unable to lock the status variable.

The ST16550 UART driver was unable to

lock the status variable for the interrupt
thread.

Unable to unlock the status variable.

The ST16550 UART driver was unable to

unlock the status variable for the interrupt
thread.

Unable to create the interrupt handler

thread.

The ST16550 UART driver was unable to

create a thread for the interrupt handler.

Unable to create statistics file (error:

[chars]([dec])).

The ST16550 UART driver was unable to

create a file to store statistics. Show
statistics command would fail. We can still
see the statistics content from core file.

An error occurred while handling an event: The event handling function returned an
[chars]
error which could not be handled

Failed to initialise tracing for Stats library:

[chars]

The infrastructure for tracing returned an

error.

Registration of a stats collector failed [chars]

Registration of a stats collector with stats

server failed.

In certain unlikely scenarios it is possible

that during a process restart the shared
memory region used by the stats
infrastructure can become corrupted. In
most cases this will automatically be
recovered from, however there is a
possibility that the system will not be able
to recover from this - The specific instance
of the message will indicate which of these
cases has arisen. If the system is unable to
restart all necessary processes then
multiple process crashes/blockages may be
Stats shared memory window has become observed. In either case, reported statistics
corrupted. [chars]
may be reset or inaccurate.

Failed to lock shared memory mutex:

[chars]

A failure occurred when attempting to

acquire a shared memory lock

Registration of a statistics collector for

Service Accounting configuration failed.
[chars]

Any updates that are made to the Service

Accounting statistics polling interval
configuration will not be implemented by
this collector. The collector will continue to
use whatever statistics polling interval was
configured at the time this message was
seen.

attempt is made to re-add a node in

[chars]: Attempt to re-add a node to a tree internal data structure.

[chars]: Compare already set for thread :

[dec]

internal data structure state was attempted

to overwrite.

ftruncate of [chars] at failed because

[chars]

The packet subsystem was not able to

initialize memory.

[chars]: Illegal thread for this wavl : [dec]

internal data structure is in inconsistant

state because of an error.

Memory allocation of [dec] bytes failed

from [hex], pool [chars], alignment [dec]

The requested memory allocation is not

available from the specified memory pool.
The current system configuration, network
environment, or possibly a software error
might have exhausted or fragmented the
router's memory.

mmap of [chars] at failed; errno ([dec])

[chars]

The packet subsystem was not able to

initialize memory.

mmap of [chars] at failed, returned address The packet subsystem was not able to
[pointer] is, expected [pointer]
initialize memory.

[chars]: Mutex op [chars] failed on mutex \

[chars]\: [chars]
--

[chars]: failure to delete a node

delete operation failed on system registry.

No memory available for [chars] [dec]

An operation could not be accomplished

because of a low-memory condition.

[chars]: Attempt to remove an unthreaded attempt is made to delete non existing

node from a tree
node from data structure.

[chars]: Received a NULL handle

one of the internal data structure is not

valid.

NULL registry

could not find registry entry.

Unknown registry type ([dec])

could not find registry entry type.

Tried to ascend in descend loop

A find operation in an internal data

structure failed.

Attempt to delink inode with 2 decendents A deletion operation to an internal data

[pointer] ([dec], [hex], [pointer], [pointer]) structure failed.

Node [pointer] ([dec]) has no descendents A deletion operation to an internal data

([hex])
structure failed.

Parent not linked to inode ([pointer],

[pointer], [pointer], [pointer])

A deletion operation to an internal data

structure failed.

Unable to find virtual node parent for

An updation operation to an internal data
[pointer] ([dec], [hex], [pointer], [pointer]) structure failed.

[chars]: Root already set for thread : [dec]

attempt is made to set root of the tree

twice.

[chars]: Attempt to use non-SHMEM API on registry operation is failed because of

SHMEM wavl tree
invalid operation has been tried.

shm_open of [chars] at failed because

[chars]

The packet subsystem was not able to

initialize memory.

[chars]: Thread [dec] does not exist

registry operation is failed because of

corrupted data structure.

[chars]: Attempt to reference an

uninitialized wavl tree

one of the internal data structure is not

initialized.

Configured from [chars] by [chars]

The routers's configuration was changed.

[chars] table [chars] damaged: [chars]

An internal table entry became corrupted.

Error releasing an internal lock ([dec]) process aborting

The TTY Connection library encountered an

unexpected error releasing a lock. To avoid
the potential for deadlock the process is
aborting.

An unexpected internal error occurred

([hex], '[chars]')

The TTY Connection library encountered an

unexpected error during normal operation.

Error acquiring an internal lock ([dec])

The TTY Connection library encountered an

unexpected error occurred acquiring a lock.

Failed to allocate %zd bytes of memory

The TTY Connection library has failed to

acquire the required amount of memory

An error ([dec]) occurred performing the

following messaging operation: [chars]

The TTY Connection library encountered an

unexpected error whilst communicating
with the TTY Server.

The TTY DB library has encountered a

critical error and must restart the process.

A critical internal error has ocurred which

requires the process to restart. For example
if a lock cannot be released then the
process is restarted to avoid deadlock.

Kernel operation failed unexpectedly:

[chars] ([dec])

A system library call failed unexpectedly.

This failure can occur due to any of the
following failures. 1. Failure while obtaining
DB read lock 2. Failure while obtaining DB
write lock 3. Failure while releasing DB
read/write lock 4. Failure while obtaining
TTY lock 5. Failure while releasing TTY lock

Lock busy, Lock operation failed: Requester

([hex]) Owner ([hex]) Lock address
A system call for locking read-write lock
([pointer])
failed because lock is busy.

Lock operation failed: Requester ([hex])

Owner ([hex]) Lock address ([pointer])
Error ([dec]) Reason : [chars]

A system call for locking read-write lock

failed.

STANDBY Console is now available ([chars]) 'Standby Console available during ISSU
[hex], '[chars]'
Load Exec and Load Done Phase'

Fatal condition detected. TTY Server is

restarting

The TTY Server has encountered a fatal

error and must restart in order to continue
operation.

Failed to complete phase 2 initialization:

[hex], '[chars]'

The TTY Server has failed to complete

phase 2 initialization. For this instance of
the server the failure is fatal; without the
services that were being initialized the
code will not be able to function.

The TTY Server previously encountered an

unexpected error while applying access
configuration changes to a TTY. As a result
Access checks for requested connections
it cannot allow future connection requests
cannot proceed. TTY-Server restart required to be authorized.

Unexpected ACL error encountered: [hex],

'[chars]'

The TTY Server has encountered an error

using the IPV4 ACL Library.

Failed to close a file descriptor inheritited

from the spawning process so that the
appropriate device files can be reopened
Failed to close file descriptor [dec]: '[chars]' for exec to read/write.

Failed to set the process' environment:

[hex], '[chars]'

Some instances of exec require the

environment to be set up before exec
initializes. The process which execs 'exec'
has failed to do this.

exec of '[chars]' failed: [unsigned int],

'[chars]'

The Exec launcher failed to exec 'exec'.

This could be due to an error picking up the
load path from install manager.

Failed to obtain the clinfo of the given

server handle: [hex], [hex], '[chars]'

Matching clinfo could not be obtained for

the given server handle.

Unexpected internal error encountered:

[hex], '[chars]'

The TTY Server has either failed on a

function which it expected to succeed, or
has got itself into an inconsistent state.

This is due to either of the following

reasons. First, TTY Server receives an
TTY Invalid pulse recvd! sender:[chars]
invalid pulse code. Or the send process is
([dec]) recvr:[chars] ([dec]) EvPcode: [dec] not tty server. This message added to
DevCtlPcode: [dec] EvPload: [dec] Node
capture maximum debug information to dig
[hex] SerHdl: [hex] [hex], '[chars]'
this issue further.

TTY device control pulse received with

invalid server handle: [hex], '[chars]'

This may be due to corruption in Event

structure.

Failed to register for ISSU on STANDBY

([chars]), [hex], '[chars]'

Failed to register for ISSU Install notification

registration.

Unexpected internal error encountered

'[chars]'

The TTY Server has encountered an

unexpected error while using the system
library.

Failed to allocate %zd bytes of memory

The server has failed to acquire the

required amount of memory

Error getting host's IP address.

The show line command was unable to get

the host IP address.

No attribute provided.

No attrbiute name was provide to the TTY

Management terminal command process.

No feature provided.

No feature name was provide to the TTY

Management terminal command process.

The TTY Management Commands Process

has been supplied with less values on the
Not enough command line values supplied. command line than it was expecting.

Too many command line values supplied.

The TTY Management Commands Process

has been supplied with more values on the
command line than it was expecting.

Error getting TTY details

The show line command was unable to get

details about the mnemonic for the TTY.

Unexpected error: '[chars]'

The TTY Management Commands Process

has encountered an unexpected error

Failed to [chars] device file '[chars]':

'[chars]'

Failed to open or duplicate the device file

that exec requires for read/write
operations.

Unexpected packet error encountered

The TTY Server has encountered an error

using the Packet Library.

Failed to complete phase 2 initialization:

[hex], '[chars]'.

The TTY Server has failed to complete

phase 2 initialization. For this instance of
the server the failure is not fatal; some
services are still available, in particular if
the aux port is running ksh then this should
still be running unimpacted.

Failed to set '[chars]' as the controlling

terminal for the process: '[chars]'

Failed to set the specified device as the

controlling terminal for the process.

System call failed: [chars], [hex], '[chars]'

QNX OS System call failed.

Unexpected SysDB error encountered:

[hex], '[chars]'

The TTY Server has encountered an error

using the SysDB Library.

Error binding to SysDB.

The show line command was unable to

bind to SysDB to retrieve the information
required.

Error un-binding to SysDB.

The show line command was unable to unbind to SysDB

Process exit with error '[chars]', rc=[dec]

tty_verifyd exit with failure. TTY related

configuration might have not applied.

The exec launcher waits on a signal from

An error occured while waiting for a signal: the TTY server before continuing. The
[hex], '[chars]'
signal was not successfully received.
Connection denied by ACL mismatch.
Source Add [chars]. Dest Add [chars].
Source Port [dec]. Dest port [dec]. Acl
[chars].

TTY management denied the requested

connection due to ACL mismatch. Please
check the configuration for applied ACL.

Error encountered while opening fpd lock

file '[chars]'

The TTY Server has encountered an error

while opening FPD lock file. Devc-conaux
has no issue to run, but FPD warning
message will not be printed on AUX port
during FPD upgrade.

Registration for ISSU notification on

STANDBY ([chars]), [hex], '[chars]'
Successful

Register for ISSU Install notification on

standby.

Timeout in phase 2 initialization([chars])

[dec]([chars])

The TTY Server found error in part of phase

2 initialization. Server is set not-to-restart,
so retry. in particular if the aux port is
running ksh then this should still be
running unimpacted.

The TTY Session startup found some error.

Skip detailed routine and proceed([chars]) Error is ignored and console will be
[dec]([chars])
activated.

Unexpected internal error

encountered:'[chars]' [hex], '[chars]'

TTY Server is trying to access Sysdb-mc

and an error [no members in group] is
returned from Sysdb-mc to all the Clients.
This is a generic issue with all the admin
band processes which comes up earlier
than sysdb svrs will have to attempt the
reconnect to sysdb with ECM retry.

Failed to register the TTY error codes:

[hex], '[chars]'

The TTY Server has failed to register the

TTY error codes with the error subsystem.

ISSU Notification received for Load Done

phase ([chars])

'ISSU install notification message for LOAD

DONE Phase received'

ISSU Notification received for Load-Exec (or 'ISSU install notification message for LOAD
Load and EXEC) phase ([chars])
EXEC Phase received'

Failed to update TTY general state in

SysDB: [hex], '[chars]'

The TTY server tried to update the TTY's

state in SysDB and failed to do so.

Couldn't extract TTY attribute

(type=[dec],name=[[chars]])

The show line command was unable to

extract attribute for the TTY.

[chars]

Debug message

Unexpected internal error encountered:

[hex], '[chars]'

The TTY Server unable to access the TTY db

for the given ttyid state.

Critical error - restarting process.

A critical internal error has ocurred which

requires the process to restart. For example
if a lock cannot be released then the
process is restarted to avoid deadlock.

Error performing TTY DB operation

'[chars]': [hex], '[chars]'

An unexpected error occurred whilst the

VTY Device DLL was using the TTY DB
library.

Failed to allocate [dec] bytes of memory for The VTY DLL has failed to acquire the
object '[chars]'
required amount of memory

Unsupported or invalid operation request:

[chars]

The TTY Server has asked the VTY DLL to

perform an unexpected or incorrectly
defined operation.

Error performing vty-pool operation [dec]

([chars]) '[chars]' [chars] will restart to
recover

An unexpected error occurred when

process was trying to apply vty-pool
configuration. Process will abort to take
process core file then restart to recover.

An unexpected error occurred when the

Error performing TTY registration operation VTY Device DLL asked the TTY Server to
'[chars]': [hex], '[chars]'
perform a TTY management operation.

Error performing TTY session operation

'[chars]': [hex], '[chars]'

An unexpected error occurred when the

VTY Device DLL asked the TTY Server to
perform a session operation.

An unexpected error occurred when the

Error performing SysDB operation '[chars]': VTY Device DLL interacted with the SysDB
[hex], '[chars]'
client library.

System library operation failed

unexpectedly: [chars] ([dec])

A system library call failed unexpectedly.

Error performing TTY Management

operation '[chars]': [hex], '[chars]'

An unexpected error occurred when the

VTY Device DLL interacted with the TTY
Management library

Unexpected initialization arguments

Command line arguments were passed to

the VTY Device DLL when it was initialized.
It does not expect to be passed any
arguments.

Couldn't extend SysDB timeout '[chars]'

Couldn't extend timeout value for 'vty-pool'

config.

Error performing device control operation

'[chars]': [hex], '[chars]'

An unexpected error occurred when the

VTY Device DLL asked the TTY Server to
perform a control operation.

Error performing TTY Data Path operation

'[chars]': [hex], '[chars]'

An unexpected error occurred when the

VTY Device DLL asked the TTY Server to
perform a Data Path operation.

Error calling [chars] for '[chars]' sysdb

connection: [hex], '[chars]' ([chars])

An unexpected error occurred when

interacting with SysDB's bulking API.

[chars]. Error : [chars]

There is a problem with the system

infrastructure - perhaps the communication
infrastructure has not yet stabilized.

[chars]

The XML Service Library has detected an

internal error. As a result, the XML
operation that was requested has not been
completely carried out.

[chars]

An internal error has occurred in the XML

TTY Agent. Some XML requests (over TTY)
may not be able to complete correctly.

[chars]

An internal error has occurred in the XML

Dedicated Agent. The logint authentication
(over dedicated) may not be able to
complete correctly.

[chars]

An internal error has occurred in the XML

SSL Agent. SSL library initialization may not
be able to complete correctly.

[chars]

The XML TTY Agent encountered a problem

when interacting with the device file. This
may be due to a problem with the
infrastructure

State has changed

This is a test message for action->bistate

message

Invoking action 'none' message

This is a test message for action->none

message

Invoking action 'peg' message

This is a test message for action->peg

message

Invoking action 'peg' message

This is a test message for action->peg

message

Invoking action 'reset' message

This is a test message for action->reset

message

Invoking action 'restart' message

This is a test message for action->restart

message

Invoking a test message [chars]

This is a test message for ios error

message

[chars] alarm generated [[unsigned int]

[chars] alarms generated so far]: [chars]

Autogenerated alarm

ltrace_init failed with retcode [dec],

([chars])

Ltrace initialization failed.

Failed to [chars] [chars]. Error [dec]

([chars])

The allocator module has either failed to

acquire or release a lock.

Failed to malloc [unsigned int] bytes

The allocator module has failed to acquire

the required amount of memory.

A NULL argument was passed into an

allocator API where a non-NULL value was
expected.

A client passed a NULL value into an

allocator API, or an internal error caused a
NULL value to be unexpectedly passed
through to an internal API.

Mismatch between block size discovered in The block size in the memory passed into
pool memory ([unsigned int]) and block
the allocator module does not match that
size specified by client ([unsigned int])
passed in by the caller on initialisation.

Unexpected init error: [chars]: [chars]:

[hex]

An unexpected init error condition

encountered.

An MBI boot hold has been introduced to

allow the other RP to boot first to give it
the opportunity to become the active RP.
This is because this RP has had multiple
MBI Boot Hold delay of [dec] seconds done ungraceful resets in the last two hours
to allow other RP to become active due to which could be preventing the router from
multiple ungraceful resets on this RP.
being stable.

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error.

[chars]: avpair_add failure on avlist [hex].

avpair_add failed while unpacking the Posix

message into avlist

[chars]: need [dec] bytes, only have [dec]

in buffer, msg dropped.

avpair API fails because the buffer is too

small.

[chars]: Attempt to use uninitialized avlist

[hex].

An illegal attempt to use an uninitialized

avpair list

[chars]: Attempt to re-initialize list [chars]

failed

An illegal attempt to reinitialize an avpair

list

Error code registration failed: [chars]

A software error occurred.

Banner config initialization failed: [chars]

A software error occurred.

Event block dispatch error: [chars]

A software error occurred.

[chars]: event manager creation failed:

[chars]

A software error occurred.

System manager call [chars] failed: [chars] A software error occurred.

Failed to bind to sysdb path [chars]: [chars] Error binding to sysdb path

Failed to register for sysdb path [chars]:

[chars]

A software error occurred.

Failed to unregister for sysdb path [chars]:

[chars]
A software error occurred.

The cardtype [dec] is unknown to us

A software error occurred.

function [chars] failed: [chars]

A call to some system function to initialize

bcdls failed. bcdls process would shut down
when this occurs and will be respawned by
the producer.

Unable to get context in

bcdl_rack_updown_handler

The pointer to the context passed by

bcdl_rack_updown_handler was NULL. This
can affect inconsistency between BCDL
producers and consumers.

A call to function for sending BCDL msg to

consumers failed. This could lead to
Failed to send SEQ_NUM msg. gid: [dec] rc: inconsistency between BCDL producers and
[dec]
consumers.

[chars]

BCLS process has hit some error condition.

bcdl2_tlv_cs_msg_decode failed. gid: [dec]

msg len: [dec] rc: [dec] pid: [dec] nid: [dec] A call to decode a BCDL TLV failed. This
tag: [dec]
could lead to a lost control message.

usage: [chars] -p producer_base_name [-t

r]

Incorrect command line arguments were

given to the module

The plug-in base name: [chars] is longer

than [dec] bytes

The name could not be used.

Could not register dll with error services:

[chars]

The call register the dll using

cerr_register_dll failed.

Unable to initialize debug capabilities:

[chars] failed: [chars]

The program cannot initialize its debug

capabilities.

Unable to initialize debug capabilities:

[chars] failed: [chars]

The program cannot initialize its debug

capabilities.

debug services function [chars] failed

A call to a debug services interface failed.

debug services function [chars] failed

A call to a debug services interface failed.

The plug-in dll: [chars] could not be loaded:

[chars]
The interface library is not availble.
The plug-in dll symbol [chars] could not be
found: [chars]
The interface library is not availble.
Found duplicate agent for BCDL group
[chars]: node [hex], jid [dec]

A BCDL agent for the group is already

running.

event manager function [chars] failed,

error [dec]: [chars]

A call to a event manager interface failed.

event manager function [chars] failed:

[chars]

A call to an event manager interface failed.

function [chars] failed: [chars]

A call to some function interface failed.

function [chars] failed: [chars]

A call to some function interface failed.

group services function [chars] failed for

gid [dec], error [dec]: [chars]

A call to a group services interface failed.

group services function [chars] failed for

gid [dec], error [dec]: [chars]

A call to a group services interface failed.

group_create failed for group [chars], error

[dec]: [chars]
A call to a group services interface failed.

group_create_lwg failed for group [chars],

parent gid [dec], error [dec]: [chars]

A call to a group services interface failed.

Displaying the memberset details of a

Nodeset contains [dec] mbrs: (nid) [chars] failed _nodeset call.

Nodeset call: gid [dec], nid [dec]

Displaying the memberset details of a

failed _nodeset call.

group [chars]: no heartbeats received in

last [dec] seconds

The bcdl client library detected that it

should have received a heartbeat from the
agent, but didn't

An error was returned from install mgr

function [chars]: [chars]

A call to an install manager function failed.

LWM function [chars] failed, error [dec]:

[chars]

A call to a LWM interface failed.

Couldn't malloc %zd bytes: [chars]

The requested memory is not available

Couldn't malloc [dec] bytes: [chars]

The requested memory is not available

Pthread operation [chars] [pointer] failed:

[chars]

The mutex lock/unlock failed

Pthread operation [chars] [pointer] failed:

[chars]

The mutex lock/unlock failed

Unable to use group services function

[chars] for type [dec]: error [dec]: [chars],
grp has [dec] mbrs

A call to a group services rinfo function

failed.

Table id [hex] not found in subgroup [dec]

to merge from subgroup [dec]

Any table has to be part of the subgroup 0.

Bad bytes critical ([dec]) or normal ([dec]), The bcdl_agent_start api was used
using default [dec] and [dec]
incorrectly.
No data reads has been done by
group [chars]: No reads from producers for bcdl_agent from producer on a child
[dec] seconds on subgroup [dec]
subgroup for the specified time.
group [chars]: No data message received
for the last [dec] seconds on the subgroup: The consumer has not received data msg
[dec]
on the child group for sometime.
Group [chars] hit max of [dec] messages
queued - initiating reset of this consumer

The consumer is not servicing the incoming

message queue.

bcdlc_id: [dec], producer: [dec], throttled

([dec] time(s)). [unsigned int] free buffer
previously, [unsigned int] free buffer
currently, threshold is lt:[unsigned int], ht: BCDL consumer is not processing the
[unsigned int]. Please collect the required messages from enqueued by bcdl library,
info a.s.a.p after the message is seen.
causing the CBP buffer state to be critical.

[chars] failed. BCDLC not initialized

BCDL consumer dll hit some error

condition.

[chars]

BCDL consumer dll hit some error

condition.

function [chars] failed: [chars]

BCDL consumer dll hit some error

condition.

A call to function for sending BCDL msg to

consumers failed. This could lead to
Failed to send SEQ_NUM msg. gid: [dec] rc: inconsistency between BCDL producers and
[dec]
consumers.
[chars]

BCDL producer dll encountered an error.

function [chars] failed: [chars]

BCDL producer dll encountered an error.

[chars]

BCLS TLV processing hit some error

condition.

function [chars] failed: [chars]

BCLS TLV processing hit some error

condition.

A BLWM-enabled server failed to send a

reply about batch configuration to the
client. The client might have restarted and
this could be a transient error. Wait for the
Failed to send batch-configuration reply to client to restart and reestablish connection
client, errno [dec]
with the server.

Failed to send a batch of replies to client,

errno [dec]

A BLWM-enabled server encountered a

failure while sending batched replies to the
client. The client might have restarted.
Wait for the client to restart and reconnect
to server to resume the processing.

Pulsed flush of batched requests failed,

Reason: [chars]

A BLWM-enabled client failed to flush the

batched LWM requests. This is most likely
because the server process restarted. Wait
for client to reestablish connection with
server and flush the batched requests
again.

An error ocurred while processing the

batched replies, error: [chars]

A failure occurred while processing the

batched replies received from the server.
This is most likely an internal error.

An error ocurred during restart handling,

error: [chars]

A failure occurred while processing the

requests/replies from the previous life after
a restart. A best-effort attempt is made to
process the requests/replies from the
previous life. if this attempt fails, this error
message is printed and the state is reset
for normal BLWM operation.

Failed to acquire/access shared memory,

error: [chars]

A failure occurred while initializing or

accessing the shared memory buffer used
to assemble the responses. This is most
likely an internal error.

Timed flush of batched requests failed,

Reason: [chars]

A BLWM-enabled client failed to flush the

batched LWM requests. This is most likely
because the server process restarted. Wait
for client to reestablish connection with
server and flush the batched requests
again.

[chars] rc = [dec]

For displaying blwm debugging

information.

[dec]: Consumer has not registered yet,

tag=[hex]

cds lib has got a message to process, but

consumer has not yet registered. please
collect cds consumer ltrace.

Producer is not ready

Failed to connect with the message

channel.

Failed to get hold on client [dec] [chars]

Failed to hold the client.

Failed to release hold on client [dec]

[chars]

Failed to unhold the client.

Connection handles do not match [dec]

[chars]

Comparison of the client failed.

[chars]:[dec] Failed to get file descriptor\n

Failed to get the connection id.

[chars]:Failed to get parent handle\n

Failed to get the the datum for the

message connection.

sysmgr get node state failed [dec], [chars] Failed to get the node state.

Reply Error : [dec] [dec] [dec]

Failed to get the reply.

[chars]:[dec] pthread_mutex_lock: [dec]:

[chars].

Failed to lock the mutex.

[chars]:[dec] pthread_mutex_unlock: [dec]:

[chars].
Failed to unlock the mutex.

Failed to inform System Manager that

process is available [dec] [chars]

System manager process is not available.

Failed to inform System Manager that

initialisation has finished [dec] [chars]

System manager process in not ready.

sysmgr register failed [dec], [chars]

Failed to register the role change with the

system manager.

destroy MRS rwlock [dec]

Failed to destroy read write lock.

Failed to malloc [unsigned int] bytes

The client library has failed to aquire the

required amount of memory.

[chars]: ### failed to send LWM message

ret [dec] error [dec]
--

Incorrect arguments: Usage: [chars]

[svr_threads]

Incorrect command line parameters were

passed to the cds proxy, and so it failed to
start.

Failed to get hold on client [dec] [chars]

Failed to hold the client.

Failed to release hold on client [dec]

[chars]

Failed to unhold the client.

Failed to create event manager

Failed to create the event manager.

sysmgr get node state failed [dec], [chars] Failed to get the node state.

[chars]: rc [hex], [chars]

The server has either failed a function that

expected to succeed, or has got into an
inconsistent state.

Failed to malloc [unsigned int] bytes

The server has failed to acquire the

required amount of memory.

[chars]:[dec] pthread_mutex_lock: [dec]:

[chars].

Failed to lock the mutex.

[chars]:[dec] pthread_mutex_unlock: [dec]:

[chars].
Failed to unlock the mutex.

A NULL pointer was passed as a fn

parameter

A NULL pointer was passed as a fn

parameter

Failed to inform System Manager that

process is available [dec] [chars]

System manager process is not available.

Failed to inform System Manager that

initialisation has finished [dec] [chars]

System manager process in not ready.

sysmgr register failed [dec], [chars]

Failed to register the role change with the

system manager.

destroy MRS rwlock [dec]

Failed to destroy read write lock.

Incorrect arguments: Usage: [chars]

[svr_threads]

Incorrect command line parameters were

passed to the cds proxy, and so it failed to
start.

[chars]: rc [hex], [chars]

The server has either failed a function that

expected to succeed, or has got into an
inconsistent state.

Failed to malloc [unsigned int] bytes

The server has failed to acquire the

required amount of memory.

[chars]:[dec] Failed to initialize trace

[chars]: error: [dec],[chars]

Failed to initialize the ltrace.

[chars]: ring init failed [chars]

Failed to initialize the ring.

Encountered internal error: [chars]: [dec]:

[hex]:[hex]

The CDS module has encountered internal

error.

Invalid argument passed: [chars]: [dec]:

[hex]:[hex]

CDS module was passed invalid arguments.

The infrastructure library detected a

[chars]: corrupted data structured detected corrupt data structure while performing
at line [dec]
internal checks.

[chars]: could not allocate memory ([dec]

bytes requested): [chars]

The infrastructure library was unable to

allocate memory from the system for an
internal data structure.

[chars]: could not create thread key:

[chars]

The infrastructure library was unable to

obtain a thread key for thread private data
storage.

[chars]: could not set threadspecific data

pointer for key [hex]: [chars]

The infrastructure library was unable to set

a threadspecific data pointer for thread
private data storage.

[chars]: shm_open failed for [chars], and

errno was not set. Sending EACCESS as
errno

shm_open failed to open the shared

memory, that is already created. errno was
not set.

Unrecoverable error in event loop. Error:

[chars]

An error (other than EINTR) occured in the

event loop. The process must exit.

Failure during intialization of [chars]. Error: A failure occurred during the initialization
[chars]
of the Cerrno Server process

Error updating Cerrno DLL Lookup table

during Install Event. Error: [chars]

An error has occurred updating the

reference table for cerrno error messages.
Some cerrno messages may be incorrect or
undecodable.

The process was initialized successfully but

Failure communicating readiness to SysMgr. was unable to inform System Manager of
Error: [chars]
the success.

Chunk named \[chars]\ not created

because [chars]

A software error occurred.

Error initializing chunk [chars], mutex error,

[chars]
The chunk's mutex could not be initialized.

Private pool size ([dec]) smaller than

request ([dec])

A software error occurred.

Chunk element size is more than 64k for

[chars]

A software error occurred.

Bad chunk reference count ([dec]), chunk

[pointer] data [pointer].

--

Attempted to exceed freelist chunk bounds,

chunk [pointer], data [pointer]
A software error occurred.

Attempted to destroy chunk with siblings,

chunk [pointer]

A software error occurred.

Attempted to free nonchunk memory,

chunk [pointer], data [pointer]

A software error occurred.

Attempted to free already freed chunk

memory, chunk [pointer], data [pointer]

A software error occurred.

Attempted to lock unlockable chunk data,

chunk [pointer] data [pointer]

--

Negative free counter on chunk [chars]

--

Could not find the sibling to allocate

memory from. Chunk [chars], total free
[dec] inuse [dec].

A software error occurred.

NULL chunk pointer argument

A software error occurred.

Attempted to destroy partially full chunk,

chunk [pointer]

A software error occurred.

Error noticed in the sibling of the chunk

[chars] Chunk index : [dec], Chunk real
max : [dec]

A software error occurred.

copy error

4arg detected a function over-stepping the

bounds of an array it was utilizing.

The debug library was unable to register its

debug specific condition codes. Condition
[chars]: could not register the debug
messages from the debug library are likely
specific structured error messages: [chars] to be degraded.

The debug library was unable to register its

debug specific condition codes. Condition
[chars]: could not register the debug
messages from the debug library are likely
specific structured error messages: [chars] to be degraded.

Deflate cannot access output directory

[chars], [chars]

The compression output directory cannot

not be accessed with the reaaon given by
the error string.

Deflate cannot output to stdout

The multiple file compression output

cannot be directed to stdout

The uncompression output is not a

Deflate cannot process multiple input files directory. The output for multiple files
into a single output file [chars]
uncompression needs to be a directory.

Deflate cannot process the file for

Deflate cannot process the file [chars] due uncompression due to the reason given in
to [chars]
the error message

[chars]: failure in attaching async handler:

[chars]
'Failure in attaching async handler.'

[chars]: bad cancel type [dec]

--

[chars]: bad message type [dec] for group

[chars] gid [dec] client callback handler
[pointer], previous gid [dec] callback
handler [pointer]

'Message type of the GSP message is

corrupted.'

[chars]-I-replying to a non-block sync msg

--

[chars]: Cond op [chars] failed on

conditional variable \[chars]\: [chars]

'Failure of an operation on condition

variable.'

[chars]: failed to connect to [chars], [chars] --

[chars]: failure in connecting to GSP:

[chars]

'Connection to GSP failed.'

Group [chars] gid [dec] got corrupted msg,

component number got [hex] expect [hex]
mtype got [dec] expect [dec] callback
handler [pointer] previous msg type [dec],
restarting to recover
--

[chars]:[dec] [chars]

'Unable to create GSP group.'

[chars]: failure in attaching lib's default

sync handler: [chars]

'Failure in attaching the library's default

sync handler.'

[chars]: async attach call failed: [chars]

'Failure in event async attach call.'

[chars]: event_file_attach call failed:

[chars]

'Failure in event file attach.'

[chars] GSP failure connection lost...

--

Failed to notify node state when [chars]:

[chars]

The internal communication channel

among pctl threads is broken.

[chars]: failure in retrieving msg from GSP:

[chars]
'Failure in retrieving a message from GSP.'

[chars] : [chars] [hex]

'Observed GSP traceback on the console.'

Group [chars] gid [dec] got msg corrupted

by client callback handler [pointer] msg
length [dec], restarting to recover
--

Can not rejoin group [chars], group id

changed from [dec] to [dec], restarting

--

[chars]: Failure in initializing lib memory

manager

Failure in initializing lib memory manager.

[chars]:[dec] malloc failed

'Failure in memory allocation.'

[chars]: msg_chan_disconnect failed

[chars]

--

[chars]: msg_get_conn call failed: [chars]

--

[chars]:[dec] [chars] msg_q mutex failed,

group:[chars] gid:[dec] retrun code:[chars] --

[chars] msg_send failure return code:

[dec]::[chars]

--

[chars]: munmap of size [dec] at addr [hex] 'Memory unmap of a particular chunk
failed. Return code [chars]
failed.'

[chars]: Mutex op [chars] failed on mutex \

[chars]\: [chars]
--

[chars]: no private msg handler

--

[chars] failure in sending SYNC_RESPONSE:

[chars]
--

[chars]: Sequencer channel for [chars] does

not exist.
-[chars][[dec]]-setting lib seq for gid : [dec]
to nidx
Just more information.

[chars] : Previous accesses (line number):

[chars]

--

[chars] -Traceback= [hex] [hex] [hex] [hex]

[hex]
--

[chars] Line:[dec] returned:[chars]

'Failure in function call.'

[chars]: Incorrect CBP access count [dec],

can't be decreased

CBP access count records the number of

threads accessing the CBP. Access count
shall be greater than 0 when it is to be
descreased

The array is filled, no slot found for

inserting [hex] dropping request

A new request for marking segment came,

but the marker reference array is already
filled. Dropping this request.

The given entry [hex] not found, dropping

request

The request for a page to be unmarked

came, but no such marking was found in
the reference array.

Coredump request rate exceeds sanity

threshold - restarting process

The process explicitly configured a

threshold of how many non-invasive
voluntary coredump requests should be
permitted before deeming the process
insane. This has been exceeded, and so the
process is being restarted.

Process [dec] requested voluntary [chars]

dump of itself

A non-invasive voluntary coredump

requested by the process. Process might be
experiancing a condition which needs
investigation. This core file will help
analysing the issue.

Problem with voluntary core dump

requested by [dec] when [chars]: [chars]

A non-invasive voluntary coredump was

requested by the process, and was within
the configured rate-limit, but a problem
occured that prevented the coredump from
being created.

A non-invasive voluntary coredump

requested by the process completed
successfully. Process might be experiancing
Voluntary core dump requested by process a condition which needs investigation. This
[dec] completed
core file will help analysing the issue.

Coredump request would exceed

configured rate-limit

A non-invasive voluntary coredump was

requested by the process, but was declined
since this would exceed the configured
rate-limit.

Too small size [dec] for [chars]

Core dump file resulted in illegally small

size

dll loading [dec] failures: [chars] is [chars]

Dumper startup failed because loading

some of dlls failed. Most likely cause is
memory running low.

Core dump failed for [chars] in getting map Core dump failed because getting map info
info. Error: [chars]
failed.

Core dump for [chars] failed due to process Core dump failed because the process
information not available
information is not available.

platform data file:[chars] doesn't exist

The platform data file doesn't exist.

Core dump for [chars] failed due to lack of Core dump failed because there is no
working dump path choice
working dump path.

platform data file:[chars] scan failed.

Error([dec]): [chars]

An error happened while reading the

platform data file.

Core dump for [chars] failed in selecting

process segments

Core dump failed because selecting

process segments in sparse mode failed.

Failed to set resource limit data. soft limit:

[hex] hard limit: [hex] Error([dec]): [chars] Failed to set resource limit data

Stack size [dec] [chars] at <[chars]:[dec]> Stack size of target process is invalid.

Error in thread pool [chars] and

Error([dec]): [chars]

Thread pool error

Timer [chars] failure. Error: [chars]

Something went wrong with the timer

Wrong file magic number [hex] [hex] [hex] Core dump file compression header is
for [chars]
broken.

Signal code [dec] - BUSADRALN. Invalid

address alignment @ address [hex]

Bus error generated due to invalid address

alignment. Program is trying to read or
write data that does not fit the CPU's
memory alignment rules.

Signal code [dec] - BUSADRERR. Trying to The CPU is instructed by software to read
access non-existent physical address [hex] or write a specific physical memory
at PC [hex]
address that is non-existent
Signal code [dec] - BUSOBJERR. Object
specific hardware error caused accessing
address [hex] at PC [hex]. Error [dec] [chars]

Signal info

Core for pid = [dec] ([chars]) requested by

[chars]@[chars]
Debug core info

[chars] core COPY option enabled but free

memory:[unsigned long int] is not enough
for the next segment:0x[pointer](size
[unsigned long int]) and succeeding ones.
Use 'exception memory-threshold
Not enough free memory to continue COPY
<percentage_in_total_memory>' to change option core dump, which allocate local
the minimum free memory threshold.
memory for each meory segent.

Crashed pid = [dec] ([chars])

Debug crash info

Devctl Code: [dec] failed. Error: [chars]

A devctl failed

Thread which is spawned to collect DLL

information (ID [dec]) is not responding.

Thread to collect DLL info seems to be

blocked. Probably DLL mgr is not
responding.

Memory addr:[hex] not aligned :[chars] at

<[dec]>

Core dump failed because the pending

segment flush failed.

Malloc (size:[dec]) failed :[chars] at

<[dec]>

Memory running low

Pathmgr symlink failed [chars] [chars] .

Error: [chars] errno [hex]

Pathmgr symlink failure

QSM publish dumper path failed [chars]

[chars] . Error: [chars] errno [hex]

QSM publish dumper path failure

Stack Pointer:[hex] is corrupted Base [hex], Core dump failed because the stack pointer
Top [hex]:[chars] at <[dec]>
is corrupted.

Failure in verification apply handler for

[chars]. [chars]

Error in apply handler

[chars]: Unable to bind to [chars]. Error:

[chars]

Could not connect to sysdb

[chars]: Could not get [chars] [chars]

Could not get sysdb item.

Failure in notification handler for [chars].

[chars]

Error in notify handler

Sysdb notifier registration for [chars] failed.

Error: [chars]
Sysdb notifier registration failure

Sysdb verifier registration for [chars] failed.

Error: [chars]
Sysdb verifier registration failure

[chars]: Could not set [chars] [chars]

Could not set sysdb item.

Unable to unbind from [chars]. Error:

[chars]

Could not disconnect to sysdb

Sysmgr LR evt registration failed. Error:

[chars] errno [hex]

Sysmgr LR event registration failure

Sysmgr redundancy state registration

failed. Error: [chars] errno [hex]

Sysmgr redundancy state registration

failure

Signal code [dec] - BUSADRERR. Failed to

map stack @ PC [hex]

Signal info

memory protection for addr:0x[pointer]

size:[hex] mode:[hex] failed. Error: [chars] Probably software bug, or OS bug.
Core dump for process [chars] is aborted as
cause for the crash is hardware specific
error. Check for signal related logs from
Core dump is aborted if the cause for the
dumper for more details
crash is hardware specific error.

Failed to init process options database.

Error([dec]): [chars]

Dumper failed to initialize process core

options database.

show registers call failed

Could not get the registers context for the

process being dumped. This could happen
if a core dump is explicitly requested of a
running or suspended process using
dumpcore command. If not it is a bug.

Thread [dec] received SIGBUS - Bus error

Signal info

Thread [dec] received SIGEMT - Mutex

deadlock signal

Signal info

Thread [dec] received signal SIGFPE Floating point exception caused accessing
address [hex] at PC [hex]. Signal code
[dec] - [chars]

Signal info

Thread [dec] received SIGILL - Illegal

instruction, accessed BadAddr [hex] at PC
[hex]. Signal code [dec] - [chars]

Signal info

Thread [dec] received SIGNAL [dec], si

code [dec], si errno [dec]

Signal info

Core for pid = [dec] ([chars]) as signal

[dec] sent by [chars]@[chars]

Debug core info

Thread [dec] received SIGSEGV Segmentation Fault

Signal info

Accessed BadAddr [hex] at PC [hex]. Signal

code [dec] - [chars]
Signal info

Core for pid = [dec] ([chars]) requested by

Unknown
Debug core info
Core for process [chars] at [chars] on
[chars]

Name of the core file

Transfer of Core file from [chars] to [chars] Status of the core dump transfer to
on [chars] [chars]
persistent location.

Core dump failed: [chars] [chars] [unsigned Could be any number of reasons. Check for
long int]
other error messages.
Core dump success
Core dump succeded

[chars]

Local core dump path is not available

because it is full of files still being
transferred.

Dumper ltrace init failure. Error([dec]):

[chars]

Failed to initialize dumper ltrace buffer

dumper will be restarted due to watchdog

timeout

dumper restarted due to watchdog

timeout.

[chars]

/tmp/dumper is not available because it is

full of files still being transferred.

Choice [dec]([chars]) either not configured

or bad path [chars] at <[dec]>. Trying next Could be any number of reasons. Check for
choice.
other error messages.
Failed to get boot device for local node:
[chars]

Failed to determine the boot device for a

RP

Compress for the file [chars](fd:[dec]) is

disabled. Returned val is [dec]. Error:[dec]
([chars]). The file will become
uncompressed one with \.Z\ suffix.

Compress library initialization for the file

failed. The file will become uncompressed
one with '.Z' suffix.

Core for process [chars] turned off

The core for the process has turned off

delibrately

Could not get core file name for crash

The core dump file name for this crash is

invalid.

Dump to path [chars] fails. Error: [chars]

Could not open a file to dump core.

[chars] [chars] size:[unsigned long int]

md5:[chars]

Keep core file md5 information to identify

later file corruption.

Core dump [chars] is cancelled. Started at

[chars]. Not likely to finish within its max
core dump time, [dec] seconds.

A process core dump has been cancelled as

it is not likely to finish within the indicated
max core dump time. Reasons could be it
has been pending in the process dumper
waiting queue too long, or that the core
dump itself took too much time.

Dumper context information is corrupted,

throwing it away

Looks like the core context infomation

dumper stores is corrupted. The conext is
being reset, all existing context infomation
will be lost.

[chars]

Notify that the default path has been set to

/tmp/dumper

Dumper failed to get process core option

values from the process init/startup file.
Typically because the process doesn't
provide its init/startup file, or rarely
Failed to get process core options from the because dumper shared memory for
process init/startup file. Error([dec]):
keeping process core options are
[chars]. Default options will be used.
corrupted.
Fall back choice: [chars]%s[chars]

Could be any number of reasons. Check for

other error messages.

The fallback choice is on the boot device

for either the local node or the remote
node. This device would be skipped as
Fallback choice is on boot device of local or dump device choice to prevent dumper
remote node.
filling it up with core dumps.

devctl DCMD_PROC_CISCO failed with size:

[dec]. Error: [chars]
A devctl failed

devctl DCMD_PROC_CURTHREAD failed for

[chars] with tid:[dec]. Error: [chars]
A devctl failed

devctl DCMD_PROC_GETGREG failed for

[chars]. Error: [chars]

A devctl failed

devctl DCMD_PROC_TIDSTATUS failed for

[chars]. Error: [chars]

A devctl failed

devctl DCMD_PROC_INFO failed for [chars].

Error: [chars]
A devctl failed
Reply to client is confirmed

Reply to client could have been missing, so

did reply at the end.

No sub processor information found on this

card. Display the local node information
No sub processor information on this card. instead.
Failed to get the local nodes internal node
name

Failed to get the local node name from

platform library.

Failed to get the local nodeid.

Failed to get the local nodeid from platform

library.

Displaying just the context information as

Core for process [chars] turned off

The core for the process has turned off

delibrately

Core dump failed because the pending

Core dump failed in pending segment flush segment flush failed.

Core dump failed in populating filters

Core dump failed because populating filters

for the process mapinfo failed.

Failed to read from text dump file:[chars].

Error:[chars]

Failed to read from the text dump file.

Removing dump [chars] as we can have

only limited number of cores in fallback
path

Memory limitation.

Core dump failed at [dec] in saving

segment info

Core dump failed because the saving

segment info failed.

Core dump failed at [dec] in scanning the

dll data

Core dump failed because scanning the dll

data failed.

Core dump failed in scanning the process

data

Core dump failed because scanning the

process data failed.

Core dump failed in scanning regisers

Core dump failed because scanning

registers for the process failed.

Core dump failed in scanning stack

Core dump failed because scanning stack

for the process failed.

Sparse core dump as [chars]

The core for the process is sparse dump

Timer started last time at [chars] for [dec]

seconds timeout.

This syslog msg is printed out when a

system call blocked too long, and is
unblocked forcibly by internal timeout
mechanism. This msg logs the timestamp
when the timer started last time, and the
timeout value specified for that.

Core dump failed in sparse tree walk

Unlink of [chars] failed. Error: [chars]

Core dump failed because the sparse tree

processing failed.
Could not delete a file

Usage: [chars] [-h]

Usage information.

Too many dump request simultaneously

Too many processes crashes or dump

request simultaneously

Failed to write to text dump file:[chars].

Error:[chars]

Failed to write to the text dump file.

Bad core file size, Expecting: [dec],

Collected: [dec]

Could not collect the entire core file data

<[chars]:[dec]> [chars] failed. Error:

[chars]

Possibly the server died.

[chars] core dump is cancelled. The same

name core is still being transferred from
/tmp

This happens when a process requests

repeating core dump, and the next core
dump is requested while the previous core
was temporary dump'ed to /tmp, and still
being transferred from /tmp.

[chars]

Debug init failed

[chars] [hex] [hex] [hex] [hex] [dec]\n

Dll information for the process being

dumped

DLL path Text addr. Text size Data addr.

Data size Version

Heading for dll info being printed

Dump request with attribute [hex] for

process [chars]

The information message for debug use.

Core dump failed: Could not create core

Could be any number of reasons. Check for

other error messages.

Dump Info [chars] failure. Error: [chars]

Something went wrong with the dump

information storage scheme

Dump request for process [chars]

The information message for debug use.

[chars]: can't create event manager.

[chars]

Failed to create event manager for the

process

event_block error -- [chars]

Error during event block

[chars]: can't attach resmgr funcs '[chars]' Failed to attach pathname to the process

can't attach event msg funcs for [chars].

Error: [chars]

Failed to register event callback functions

Failed call : [chars]. Error [chars]

Unexpected failure for sysdb datalist.

Bad item : [chars]. [chars]

Unexpected or bad item under config for

dumper

Bad item type for [chars]

Unexpected item type in dumper config

[chars]: [chars] failed: [chars]

Could not attribute a thread. Check for

other error messages.

[chars]: [chars] failed: [chars]

Could not cond_wait a thread. Check for

other error messages.

<[chars]:[dec]> [chars]: [chars] failed:

[chars]

Could not create a thread. Check for other

error messages.

thread timed join operation failed: [chars]

A internal timed thread join operation has

failed. This is a bug.

mutex operation [chars] failed for

mutex_destroy mutex: [chars]

A internal mutex operation has failed. This

is a bug.

mutex operation [chars] failed for

mutex_init mutex: [chars]

A internal mutex operation has failed. This

is a bug.

<[chars]:[dec]> mutex operation [chars]

failed for loc_mutex mutex: [chars]

A internal mutex operation has failed. This

is a bug.

<[chars]:[dec]> mutex operation [chars]

failed for unlock_mutex mutex: [chars]

A internal mutex operation has failed. This

is a bug.

[chars]: Unexpected error: [chars]

Encountered an unexpected internal error.

[chars]: Can't connect to configuration,

[chars]

DUMPER debugging service register to

sysdb failed.

Too small size [dec] for [chars]. Expected:

[dec]

A file is found to be too small size than

expected.

file:[chars] size:[dec] has version:[dec]

which is different from expected_version:
[dec]

A file has invalid version than expected.

[chars]: unable to read platform dependent Most probably some problem with the file
filesystem
systems data file

devctl DCMD_PROC_MAPINFO failed, Error:

[chars]
A devctl failed

devctl DCMD_PROC_PAGEDATA failed, Error:

[chars]
A devctl failed
[chars] V [chars][[chars]] [chars] [chars] at
[chars] [chars]
Active installed packages
active installed packages show failed:
[chars]

Install manager might have died

[chars] not a valid path or not supported

most probably tried to configure an

unsupported path e.g. rcp.

Could not map kernel dumper information. Space might not have been allocated for
[chars]
storing kernel dump information

mkdir for path [chars] failed, error:

[chars]\n

Something wrong

<[chars]:[dec]> Map of file descriptor [dec]

for size [dec] Offset [hex] failed: [chars]
Something wrong

Failed to reply to client. Error: [chars]

Could not reply to client

Failed to reply to client. Error: [chars]

Could not reply to client

Unmap for size [dec] at Address 0x[pointer]

failed: [chars]
Something wrong

No space information available\n

Something wrong

No OS debug info available at system

page:[pointer]

OS debug info is not ready yet.

Open of path [chars] failed at [chars]:[dec].

Error: [chars]
Could not open a file

Memory mapping of OS debug info has

Memory map for OS debug info([chars]) at failed. Check the error code for the direct
[hex] failed. Error([dec]): [chars]
cause of the failure.

Fail to open process, pid = [dec]. Error =

[chars]

Could not open the process file system

Process core options shared memory could

be corrupted. Wrong process option index:
[dec] for total options size:[hex] at
<[chars]:[dec]>

An inconsistent process core option index

value is found for the total size. Shared
memory for keeping process core options
could be corrupted by someone. Probably
software bug, or OS bug.

Process options shared memory could be

corrupted. Cksum:[hex] Calculated cksum:
[hex] process option numbers(corrupted?):
[dec]

Shared memory for keeping process core

options is corrupted. Dumper could have
been restarted while it's touching the
shared memory. If not, this could be
software or OS bug.

Process memory pages [dec]

The total memory page number of dumper

target process

No process name information available,

using pid as name instead: [chars]\n

Something wrong

Read of size [dec] to fd [dec] at offset [hex] Most probably some problem with the
failed, read [dec] Error: [chars]
procfs file system

[chars]

This is the register contents at the time of

the crash for the crashed process.

Removing dump [chars] as we are in low

memory condition

Memory running low

lseek to vaddr [hex] with fd [dec] failed.

Error: [chars]

Most probably some problem with the

procfs file system

CPU info is not created as it's requested by

the target process [chars]. Check \'show
exception core-options process
<process_name>\' outputs for the up-todate process core option values.

Skipped CPU info dumping in OS debug

info, as it's requested by the target
process. Down time critical processes
which can't afford extra core dump time
due to CPU info, might request this
skipping.

Failed call : [chars]. Error [chars]

#[dec] [hex]

Unexpected failure for sysmgr call.

Trace back

[chars]

Some error happened in trace back

operation

Stack trace back failed

Could not figure out trace back

Dumper unknown card

Platfrom card type unknown to dumper.

Unlink of [chars] failed. Error: [chars]

Could not delete a file

Write of size [dec] to fd [dec] failed.

Written [dec]. Error: [chars]

Most probably some problem with the file

system

[chars]: attached-message list corrupted -- An Event Manager list of attached

[[dec],[dec]] overlaps [[dec],[dec]]
messages was found to be corrupt.

[chars]: invalid event manager flags -[hex]

An Event Manager call was made with an

invalid flag argument.

[chars]: call to qsm_add_service([chars],

[chars]) failed -- [chars]

A call to the QSM API failed. The server was

not able to advertise itself.

[chars]: unexpected signal [dec] received

The Event Manager signal handler should

never be invoked directly.

An Event Manager blocking call was made

[chars]: timeout call failed, handle [pointer] with an invalid timeout specification.

mutex lock error: ([chars]:[dec])

An Event Manager library function was not

able to lock mutex.

mutex unlock error: ([chars]:[dec])

An Event Manager library function was not

able to unlock mutex.

A server process has registered empty path

name with the path manager without
specifying _RESMGR_FLAG_FTYPEONLY flag.
This may lead to undesired behaviour like
registering empty path name without
receiving requests intended for some other
specifying _RESMGR_FLAG_FTYPEONLY flag, server process (when the other server
flags=[hex]
process is restarted).

[chars]: event_file_attach failure for fd

[dec], cond [dec]: [chars].

An ionotify call to request file-state

notification failed.

[chars] event manager handle -- [pointer]

An Event Manager call was made with an

invalid or corrupted event manager handle.

ionotify failed during reregistration on fd:

[dec], error: [chars], attempt [dec] of [dec],
Server info: nd [hex], pid: [dec], chid:
Event-manager is unable to reregister for
[hex], scoid: [hex]
subsequent notifications with a server.

[chars]: could not allocate memory for

Resource Manager context

The Event Manager could not allocate

memory to construct a Resource Manager
context when delivering an RM message.

The Event Manager signal thread must

[chars]: could not install signal handler for install a signal handler for each signal that
signal [dec] [chars]
it is watching.

The Event Manager signal thread could not

allocate memory needed to deliver a signal
[chars]: could not allocate memory to
message to the Event Manager message
deliver signal [dec] [attempt [dec] of [dec]] channel.

[chars]: could not allocate from heap

An Event Manager library function was not

able to obtain HEAP memory space.

Failed to initialize [chars]: [hex]:[chars].

RedFs failed to setup the mentioned ltrace

buffer.

An attempt to decode a filecopy bag failed.

This may be due to like low memory. You
may need to free some resources from
other processes if the system is running
low on memory - if freeing up resources
does not fix the problem, please contact
your customer support representative and
An attempt to decode a filecopy bag failed file a bug against the infra-filecopy-srv
when [chars]
component.

An attempt to encode a filecopy bag failed.

This may be due to like low memory. You
may need to free some resources from
other processes if the system is running
low on memory - if freeing up resources
does not fix the problem, please contact
your customer support representative and
An attempt to encode a filecopy bag failed file a bug against the infra-filecopy-srv
when [chars]
component.

Insufficient memory to [chars]

No memory to perform bag operations.

Null parameter passed to function when

[chars]

A NULL parameter was passed to a function

expecting non-NULL parameters. This will
result in the operation being performed
failing. If this error occurs, please capture
any contextual information from the CLI,
and email it to your customer support
representative. A bug should be filed
against the infra-filecopy-srv component.

A sysdb operation failed when [chars]

An attempt to retrieve (or set) a sysdb item

or list failed. This could be a transient
problem that may be fixed by restarting the
filecopy_process - note well that restarting
this process could result in loss of data. If
restarting the process does not solve this
problem, please capture any contextual
information from the CLI, contact your
customer support representative and file a
bug against the infra-filecopy-srv
component.

Failed to register filecopy bags during

startup of filecopy_process

The filecopy_process was unable register

its bags during startup. This will result in
the filecopy_process being terminated. The
problem may be due to a transient
condition like low memory. Try restarting
the filecopy_process - you may do this by
creating a new ccCopyEntry row in the
CISCO-CONFIG_COPY-MIB. If the problem
persists after a few tries, please open a
bug and include the release number for the
infra/filecopy/server component, the
logged error message containing the
traceback and a copy of the runningconfiguration at the time of the error.

Could not create event manager for the

filecopy_process

The filecopy_process was unable to create

an event manager. The filecopy_process
will shut down since it cannot receive any
events. Try restarting the process - if the
error continues, contact customer support
with the error message and associated
context.

Insufficient memory to [chars]

No memory to perform edm or bag

operations.

The filecopy_process was unable attach a

handler for a signal. This could affect
cleanup of open connections or allocated
resources during shutdown, which could
affect the filecopy_process' ability to restart
in the future. The filecopy_process will
attempt to shutdown in the hope that this
Could not attach a handler function for the problem is transient, and that a future
signal [chars]
attempt to start it will succeed.

Could not bind with SysDB

The filecopy_process was unable to bind

with sysdb. This means the process will be
unable to communicate with its clients.
Hence the filecopy_process will shut itself
down.

Could not register for debug notifications

The filecopy_process was unable to register

for debug notifications. If you have turned
on debugging for this process, it will have
no effect. However, the rest of the
filecopy_process functionality should still
be available.

Failed to send a filecopy notification [chars]

The filecopy process failed to send a

notification to its clients about a statetransition for a copy request. Users may
find the reported duration of a copy
operation to be quite large as a result,
depending on how long it takes for a client
to poll the filecopy_process to see if a state
change occurred.

Could not unbind with SysDB

The filecopy_process was unable to unbind

from sysdb when shutting down. This may
result in a failure to re-register with sysdb
when the process is restarted later.

The punt flow trap failed to completely

clear the hardware settings for the 'penalty
box' for the above specified interface which
is using more hardware resources (i.e Bad
Actor). Traffic from this source MAC may be
affected. When a flow through any
interface is trapped, it is tagged as a Bad
The platform failed to completely clear the Actor and will be added to 'penalty box',
'penalty policing' for interface [chars],
this box will restrict the traffic through that
[chars].
interface by applying penalty policing.

The punt flow trap failed to completely

clear the hardware settings for the 'penalty
box' for the above specified interface which
is using more hardware resources (i.e Bad
Actor). Traffic from this source MAC may be
affected. When a flow through any
interface is trapped, it is tagged as a Bad
The platform failed to completely clear the Actor and will be added to 'penalty box',
'penalty policing' for source MAC address
this box will restrict the traffic through that
[chars] on interface [chars], [chars].
interface by applying penalty policing.

LPTS Excessive Punt Flow Trap (EPFT)

feature has been disabled, but not all
Penalty policed interfaces on this node
were cleared: [chars]

The LPTS Excessive Punt Flow Trap (EPFT)

feature was disabled by configuration, but
not all existing interfaces which are using
more hardware resource (i.e Bad Actors) on
this node were cleared. This may affect the
creation of new sessions or sub-interfaces.
When a flow through any interface is
trapped, it is tagged as a Bad Actor and will
be added to 'penalty box', this box will
restrict the traffic through that interface by
applying penalty policing.

Failed to initialize [chars], [chars].

Initialization of FLOWTRAP process which is

responsible for EPFT feature is failed to
complete.

Interface [chars] cleared from penaltypolicing by timeout.

An interface that was previously flagged by

the punt flow trap has been removed from
the 'penalty box.'

Interface [chars] deleted: cleared from

penalty-policing.

An interface that was previously flagged by

the punt flow trap has been deleted, and so
the 'penalty box' for it has been cleared.

Excessive [chars] flow detected on

interface [chars]. The interface will be
penalty-policed at [dec] pps for [dec]
minutes.

The punt flow trap sampler detected an

excessive flow on an interface. This could
result in a denial of service to other
interfaces. The interface will be placed in a
'penalty box' and policed at a much lower
rate for a specified time period.

Excessive [chars] flow detected on

interface [chars]. Penalty-policing is
disabled. No action taken.

The punt flow trap sampler detected an

excessive flow on an interface. This could
result in a denial of service to other
interfaces. Penalty-policing has been
disabled by configuration so the interface
will not be placed in the 'penalty box.'

Source MAC [chars] on interface [chars]

cleared from penalty-policing by timeout.

A source MAC address that was previously

flagged by the punt flow trap has been
removed from the 'penalty box.'

Interface [chars] deleted: source MAC

[chars] cleared from penalty-policing.

A source MAC address that was previously

flagged by the punt flow trap has been
removed from the 'penalty box' because
the interface on which it was flagged has
been deleted.

Excessive [chars] flow detected from

source MAC address [chars] on interface
[chars]. Traffic from this MAC address will
be dropped for [dec] minutes.

The punt flow trap sampler detected an

excessive flow from a source MAC address.
This could result in a denial of service to
other interfaces. All traffic from this source
MAC address will be dropped for a specified
time period.

Excessive [chars] flow detected from

source MAC address [chars] on interface
[chars]. Penalty-policing is disabled. No
action taken.

The punt flow trap sampler detected an

excessive flow from a source MAC address.
This could result in a denial of service to
other interfaces. Penalty-policing has been
disabled by configuration so the interface
will not be placed in the 'penalty box.'

[chars]

A SW exception occurred in FSM Library

[chars]

--

Failure to notify node state when [chars]:

[chars]

The internal communication channel is

broken.

[chars]: [dec] members for group [dec]

([chars]) still exists: pid [dec]

'This GSP group can not be deleted since

some of the members still exist within the
group. The remaining members are
required to leave the group before it can be
deleted.'

[chars]:[dec] Issue with client locking of

client id [dec]

'Failed in locking the GSP client. '

[chars]:%zd condvar op [chars] failed

[chars]

'Current operation on the condition variable

has failed.'

'ENS has detected a mismatch in the

handles used by clients. This usually
happens when a client producer registers
[chars]:[dec] detect application issue from with multiple handles and one of the culprit
mid [dec]:[dec]%d and [dec]:[dec]:[dec].
handles invalidate. This results in the
[chars]
mismatch.'

[chars]: File op [chars] failed. : [chars]

'Current operation on the file has failed.'

[chars]:[dec] gs_get_mem or malloc failed

(other [dec])

'Failure in memory allocation.'

Inconsistent node-id received, expect:

[hex], got [hex]:[dec] for group [dec]

'Received a RSI node id for a GSP group

which is different than an expected value.'

Ltrace init for file [chars] failed [chars]

'Initialization of Ltrace failed.'

'GSP client process is either blocked or is

slow to pick up the messages intended for
Process [chars] (pid [dec]) not picking up
itself. This leads in building up of GSP
messages, [dec] msgs dropped. [dec] msgs queue and eventually leads to messages
pending, taking [unsigned int] bytes
being dropped.'

[chars]: Mutex op [chars] failed on mutex

[chars] ([chars]) : [chars]

'Current operation on the mutex has failed.'

Can't insert node [hex] to node state map

'Failure in inserting a node to a node state

map.'

[chars]:[dec] pthread op [chars] failed

[chars]

'Current operation on a pthread failed.'

Couldn't spawn script: [chars] failed, rc:

[chars]

Failed to run a script to collect debug

information.

GSP received spurious node down from rsi

[hex] reason [dec]

GSP process receives notification that the

node it's running on is down.
Communication over GSP will be cutoff
to/from this node.

gsp traceback [chars]

'Observed a GSP traceback on console.'

Can not add node [hex] to group [chars]

(gid [dec]), failure return code [dec]

'Failure in adding a node to a GSP group.'

[chars]: wrong flow zone info

'GSP flow zone information is incorrect.'

GSP Ethernet queue buildup [dec] [chars]

GSP Ethernet queue buildup indicates

underlying transportor hardware issue

GSP fabric queue buildup [dec] [chars]

GSP fabric queue buildup indicates

underlying transportor hardware issue

GSP process memory [chars] in critical

state

If GSP process memory is in critical state it

indicates that one of the internal queues is
building up or there is a memory leak.

[chars].

--

[chars].

--

ENS supports single publisher multiple

consumer model. There can be only one
publisher per class-data handle. If ENS
detects that more than one ENS client is
ENS detected multiple publishers for hdl
trying to become publisher on a given
[hex]:[hex], local-producer gid:[dec]
handle, it prints above message. It shows
rsi_nodeid:[dec] pid:[dec] process name:
both existing producer and new producer.
[chars], new-producer gid:[dec] rsi_nodeid: Triage case need to be logged on producer
[dec] pid:[dec].
process component.

[chars] returned [chars]

--

Process [chars] (pid [dec]) not picking up

messages, [dec] msgs pending, taking
[unsigned int] bytes

--

Received own mcast on gid [dec]

--

[chars] spawn show tech gsp at the request

of [chars]
Start/Complete spawning a script

[chars] returned failure code: [chars] for

node [hex] state [dec] with seq [dec]

'Failed to send a multicast.'

An error condition occurred during LC iMDR

Node will be reloaded due to iMDR aborted operation and the node would be reloading
- [chars]
then.

[chars]

Forwarding through the hardware will

resume now after an upgrade. The
hardware reprogramming needed for the
upgrade has been completed, and
hardware forwarding will now get resumed.

[chars]

Forwarding through hardware will stop now

for an upgrade which is in progress. This is
the stage of NSF stop and will have the
hardware re-programming taking place
now.

An application set the MBI boot hold and it

was not released within the specified
mbi boot hold was not released after [dec] timeout. This could indicate that the node
seconds, resetting node
is having problems and will be reset.

installation still not done after [dec]

seconds, wait continuing

The pakage installation sync did not

complete in time. This could indicate that
the node is hung and may require a reset.

total time [dec].[dec] seconds

The pakage installation software is now

ready. This is not an error.

package install time threshold of [dec]

seconds has been exceeded, continuing

An unexpected condition encountered. This

is not necessarily an error.

total time [dec].[dec] seconds

The MBI processes have all been started.

This is not an error.

MBI bootup exceeded threshold of [dec]

seconds, continuing

An unexpected condition encountered. This

is not necessarily an error.

IOS XRv License Manager unable to start:

[chars], ([dec])

The IOS XRv license manager was unable

to start. This will result in a reload of the
router.

End User License Agreement accepted.

Welcome to the [chars] Version of Cisco IOS The end user has accepted an end user
XRv.
license agreement.

Errors were encountered when starting a

listener thread: [chars]

A component registered for platform mode

notifications and the listener failed.

Error when handling an event: [chars]

An error has occured in attempting to

handle an event sent to the IOS XRv
license manager. The event has been
ignored.

A general allocation failed

An allocation has failed.

Failed to decode a trap event bag: [chars]

([hex])

The agent was unable to decode the bag

representing a trap event.

[chars] : [chars] ([hex])

Initialization failed

Allocation failed for Var OID [chars] ID [dec]

SNMP type [dec] value [hex]
An allocation has failed.

[chars] failed: [chars]

Some error occurred in operations related

to resource allocation. The text of the
message displays the failed operation and
the related error code. The system will try
to re-aquire the resource.

[chars] failed: [chars]

Some error occurred in operations related

to Shared Memory area. The text of the
message displays the failed operation and
the related error code. The traceback can
be used to get the function/line number of
error generating code.

ITAL initialization failed: [chars]

Initialization of ITAL failed. The traceback

can be used to get the function/line
number of error generating code.

ITAL debug init failed: [chars] ([chars])

Initialization of ITAL failed. The traceback

can be used to get the function/line
number of error generating code.

ITAL lib not fully initialized: [chars], error

code [chars]

ITAL Initialization failed. The message

displays the failed operation and the error
code. ITAL connects with various servers to
get required information for process from
which it is invoked. It might lead to
unstable state of the process.

An effort to lock database failed. The

function which tried to lock as well as the
function holding the lock are given in the
An attempt to lock ITAL dbase failed for
message.a The database might not reflect
[chars] dbase, caller [chars] holder [chars] the expected behavior.

An attempt to unlock ITAL dbase failed for

[chars] dbase

An effort to unlock database failed. The

function which tried to unlock is given in
the message. The database might not
reflect the expected behavior.

[chars] : [chars]

Some error occurred in interactions with

debug infrastructure. The text of the
message displays the failed operation and
the related error code. The traceback can
be used to get the function/line number of
error generating code.

Invalid interface notification ([chars])

received: IfName=[chars], IfHandle=[hex]

An invalid interface notification was

received from one of the servers.

Memory allocation (%zu bytes) failed for

[chars]

A memory allocation operation failed.

[chars]

Some client requires unsupported ITAL

functionality.

[chars], Retry Count = [dec]

Retry count exceeded the limit.

[chars]: [chars]

Certain operation failed due to unexpected

error. The message displays the reasons.

[chars], reason: [chars]

Registration operation with a certain server

failed. The message displays the reasons.

Debug event [chars] init failed ([chars])

Initialisation of the specified debug event

failed, the process is unable to start
properly and will exit. The message may
contain details about the failure and the
error code indicates the type of failure.

[chars] ([chars])

A failure was returned from the

infrastructure software, the process is
unable to start properly and will exit. The
message may contain details about the
failure and the error code indicates the
type of failure.

Unable to upload and/or save file [chars]

The kernel dumper file upload and/or save

on local media failed.

Saved truncated file [chars] ([unsigned int] The kernel dumper file saved on local
bytes)
media is truncated.

Unable to open file [chars] for writing on

any available storage media.

The kernel dumper file writing failed on all

available storage media.

[chars] with error ([chars])

A non-fatal condition encountered - a

function call returned an error. The error
code indicates the type of failure.

Read from file [chars] (fd [dec]) failed

([chars])

Reading from the specified file and storage

media failed. The message may contain
details about the failure. This does not
have any other impact on the router
functionality.

Re-opening file [chars] for reading failed

([chars])

Re-opening the specified file and storage

media failed. The associated KD uploaded
file can not be recovered, the KD upload
will fail. The message may contain details
about the failure. This does not have any
other impact on the router functionality.

Write of size [dec] to file [chars] (fd [dec])

failed ([chars])

Writing to the specified file and storage

media failed. The message may contain
details about the failure. This does not
have any other impact on the router
functionality.

[chars]

Intentional exit to restart clean, to keep

things simple.

Successfully wrote [chars] file ([dec] bytes) The kernel dumper file was successfully
received from slot [dec].
saved in the specified location.
[chars]
The kernel dumper message.

Debug event registration failed ([chars])

Registration of the specified debug event

failed, the respective debugging will not be
possible. The message may contain details
about the failure. This does not have any
other impact on the router functionality.

[chars] '[chars]' [chars] [chars]

The activation state of the named virtual

service has changed as notified by Virtmanager.

Virtual Service[chars]

A memory allocation request failed to

allocate a data structure required to
activate the virtual service.

Virtual Service[chars]

The request to commit the resources

required by the named virtual service
failed.

Virtual Service[chars]

The virtual service machine definition file is

requesting more CPU shares than the
system has available for virtual services.

Virtual Service[chars]

Virt-manager and its associated

infrastructure experienced an internal error.

Virtual Service[chars]

The virtual service machine definition file is

requesting more CPU shares than the
system has available for virtual services.

Virtual Service[chars]

The request to create a DB entry for the

named virtual service failed.

Virtual Service[chars]

The final activation processing failed to

successfully defer.

Virtual Service[chars]

The virtual service machine definition file

contains an invalid disk image path for one
of the disk devices. This may be a
Harddisk, CDROM or USB storage device.

Failed to find virtual service with id

[unsigned int] in the Virt-manager DB

The virtual service with the ID named could

not be located in the Virt-manager DB.

Virtual Service[chars]

The named virtual service has triggered

the log. Please interpret the log in the
context of the virtual services.

Virtual Service[chars]

The virtual service machine definition file is

requesting invalid CPU tunes parameter.

Virtual Service[chars]

The virtual service machine definition file is

inconsistent in the specification of required
memory via the <memory> and
<currentMemory> nodes.

Virtual Service[chars]

Inserting the named virtual service into the

virtual service DB tracked by Virt-manager
failed.

Virtual Service[chars]

The installation of the virtual service failed.

VMAN, VM install media still unavailable.

[chars]

The install media was not detected. Waiting

for udev to complete install
media(harddisk) detection.

Successfully [chars] '[chars]'

The installation state of the named virtual

service has changed as notified by Virtmanager.

Virtual Service[chars]

The virtual service activate message was

received, however, the data it contained
could not be interpreted.

The virtual service deactivate message was

Failed to process virtual service deactivate received, however, the data it contained
message
could not be interpreted.

Virtual Service[chars]

The package definition file for the named

virtual service has failed to be validated
and the virtual service will not run.

The virtual service unprovision message

Failed to process virtual service unprovision was received, however, the data it
message
contained could not be interpreted.

Virtual Service[chars]

The named virtual service has an invalid

parameter specified in the .xml file inside
the .ova package.

Virtual Service[chars]

The virtual service cannot be activated as

the machine type specified is not
supported.

Virtual Service[chars]

The virtual service machine definition file is

requesting more memory than the system
has available for virtual services.

The virtual service machine definition file is

Virtual service ([chars])[chars] defines
requesting more memory for the specified
[unsigned int] MB of Memory exceeding the profile, than the system has available for
maximum [unsigned int] MB.
virtual services.

Virtual Service[chars]

The virtual service machine definition file is

requesting more than one CPU tunes
parameter.

Virtual Service[chars]

A network configuration error has been

detected for the named virtual service.

Virtual Service[chars]

The interface list embedded in the activate

request for the named virtual service could
not be processed.

Virtual Service[chars]

The virtual service package for the named

virtual service has failed to be validated
and the virtual service will not run.

Purpose: [chars], URI: [chars], errcode:

[dec]

Persistent Storage Service handling error.

Source URI: [chars], Destination URI:

[chars], errcode: [dec]

Persistent Storage Service snapshot error.

Virtual Service[chars]

Removing the named virtual service from

the virtual service DB tracked by Virtmanager failed.

Description: [chars], errcode: [dec]

Debug infrastructure error.

Failed to set ROM monitor variable

ENABLE_VTX: No space in table

Failed to set ENABLE_VTX ROM monitor

variable due to no space in Monitor
Variable Table.

Failed to set ROM monitor variable

Failed to set ENABLE_VTX rom monitor
ENABLE_VTX: Invalid string format: [chars] variable due to invalid string format.

Virtual Service[chars]

The named virtual service failed to start.

Virtual Service[chars]

The virtual service machine definition file is

requesting invalid VCPU value.

Virtual Service[chars]

The virtual service machine definition file is

requesting more VCPUs than the system
has reserved for virtual services.

Virtual Service[chars]

The virtual service requires Disk Storage in

excess of the Free Disk Storage available to
virtual services.

Virtual Service[chars]

The number of configured virtual port

group interfaces must match the number of
Ethernet Network Interfaces defined in the
machine definition file.

Virtual Service[chars]

The virtual service requires physical

memory in excess of the free memory
available to virtual services.

Virtual service [chars] has no management A management interface is configured but

interface defined but it is configured in CLI. none is defined.

Virtual Service[chars]

The named virtual service has failed. It is

no longer running either because the guest
OS has failed, the guest OS has shut down
the machine or the emulator has failed.

Virtual Service[chars]

The AUX login to a virtual service may

allow the user access to system functions
that may not have been tested or may
interact with the system in unintended
ways. Use with caution.

Unsigned software package [chars] loaded A software package without a code signing
for service container [chars].
certificate has been loaded.

VIRTUAL SERVICE [chars] LOG: [chars]

The named virtual service has triggered

the log. Please interpret the log in the
context of the virtual services.

Process had loaded more than 254 dlls

(pid=[dec]). We exclude dll-text from core
file.

An overflow encountered for the process.

This is not an error.

Given buffer size([dec]) is smaller than

required, possible loss of dll-text segment
in core file.

Buffer given to the devctl routine is smaller

than required. This will cause missing dlltext segment in the core file.

[chars]: [chars](): [chars]

A system call failed. The calling function,

the failed call, and error are displayed.

Unexpected array address: [pointer]:

[pointer]: [pointer]

An unexpected condition encountered. This

is not necessarily an error.

Unexpected magic value: [hex]

An unexpected magic number

encountered. This is not necessarily an
error.

Process had loaded more than 254 dlls

(pid=[dec]), process core file will have
larger size than required. Replace dll-text
info with [hex]-[hex]

An overflow encountered for the process.

This is not an error.

Process had loaded more than 254 dlls

(pid=[dec])

An overflow encountered for the process.

This is not an error.

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error.

API [chars] already been called

The specified API has already been called.

API [chars] already been called

The specified API has already been called.

[chars]: software upgrade error ([dec],

[dec])

Inconsistent file count between given and

in the file list.

[chars]: software upgrade error ([dec],

[dec])

Inconsistent file count between given and

in the file list.

[chars]: sysmgr function [chars]() failed:

[chars]

The client library has failed a sysmgr

function.

[chars]: sysmgr function [chars]() failed:

[chars]

The client library has failed a sysmgr

function.

[chars]: Invalid value [%zd] for argument

[[chars]] passed

An application called the API with invalid

value.

[chars]: Invalid value [%zd] for argument

[[chars]] passed

An application called the API with invalid

value.

[chars]: failed to malloc %zu bytes

The client library has failed to allocate the

required amount of memory.

[chars]: failed to malloc %zu bytes

The client library has failed to allocate the

required amount of memory.

[chars]: parse error: [chars]

An error was encountered whilst parsing

the argument vector for a spawn script
operation.

[chars]: parse error: [chars]

An error was encountered whilst parsing

the argument vector for a spawn script
operation.

[chars]: [chars]() failed: [chars]

The client library has failed a system call.

[chars]: [chars]() failed: [chars]

The client library has failed a system call.

[chars]: Node restart requested by pid

[dec]

Informational only.

[chars]: Node restart requested by pid

[dec]

Informational only.

Script [chars] exceeded allotted time of

[dec] sec and was killed.

Script exceeded allotted time.

Script [chars] exceeded allotted time of

[dec] sec and was killed.

Script exceeded allotted time.

Unsupported API [chars] called by process

[chars]

The call is not supported during MBI boot.

Unsupported API [chars] called by process

[chars]

The call is not supported during MBI boot.

'[chars]: Debug cleanup failed: [chars]'

An error was returned when cleaning up

debug.

'[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]'

An error was returned when initializing

debug.

An error was returned when registering

'[chars]: Debug registration failed: [chars]' debug.

'[chars]: Debug cleanup failed: [chars]'

An error was returned when cleaning up

debug.

'[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]'

An error was returned when initializing

debug.

An error was returned when registering

'[chars]: Debug registration failed: [chars]' debug.

'bad listner tag detected on the packet,

dropping packet'

Unknown lpts packet type; or LPTS packet

with bad listener tag.

'Unable to get packet network start.

Dropping packet'

This failure encountered when the network

start of packet couldnot be obtained.

'[chars]: failed to process ingress buffer

header of packet [hex]: [chars]'

Ingress buffer header of packet failed to

extract.

'[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]'

An error was returned when calling the

debug_init_event() function.

An error was returned when calling

'[chars]: Debug registration failed: [chars]' debug_register() function.

An error was detected when initializing the

'Failure in the PA-FF update module: [chars] event queue between two infrastructure
([chars])'
module.

'[chars]: could not create event manager:

[chars]'

An internal error was detected when

creating Event Manager.

'[chars]: initialization for PA Flow Forwarder An internal error was detected when
I/O thread failed: [chars]'
initializing PA Flow Forwarder I/O thread.

'[chars]: malloc [dec] bytes failed: [chars]' An attempt to allocate meory failed.

'[chars]: initialization(tlvlib_init)in PA Flow

Forwarder I/O thread failed: [chars]'

An internal error was detected when

initializing(tlvlib)in PA Flow Forwarder I/O
thread.

'[chars]: The client structure associated

with this client was not found'

An internal error was detected when trying

find the internal client structure for a given
operation.

'[chars]: failed to block waiting for Event

Manager events: [chars]'

An internal error was detected when block

waiting for Event Manager events.

An internal error was detected when

'[chars]: could not initialize event structure: initializing a sigevent structure using
[chars]'
event_init_event.

An internal error was detected when

'[chars]: could not attach handler for Event attaching a handler for an Event Manager
Manager asynchronous event: [chars]'
asynchronous event.

'[chars]: Can't get my own nodeid: [chars]' A call to platform_get_my_nodeid faild.

'[chars]: error from lrd function [chars]:

[chars]'

An internal error was detected when using

a logical router daemon api

'[chars]: failed to attach handler for Event

Manager synchronous event: [chars]'

An internal error was detected when

attaching a handler for an Event Manager
synchronous event.

'[chars]: msg_clinfo_get_datum failed:

[chars]'

An internal error was detected when

accessing a client info structure.

'[chars]: msg_send_event failed: [chars]'

An internal error was detected when

sending an Event Manager synchronous
event. This is not a critical error message,
on getting the repeated occurrence of this
error log, Copy the error message exactly
as it appears, and report it to your
technical support representative.

'[chars]: could create the timer: [chars]'

An internal error was detected when

creating a timer using timer_create.

'[chars]: Couldn't arm the timer: [chars]'

An internal error was detected when

arming a timer using timer_settime.

[chars]: Debug cleanup failed: [chars]

An error was returned when cleaning up

debug.

[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]

An error was returned when initializing

debug.

[chars]: Debug registration failed: [chars]

An error was returned when registering

debug.

'[chars]: EDM backend function [chars]

failed: [chars]'

An internal EDM backend function failed.

'[chars]: Pre-IFIB datapath control

command [chars] failed: [chars]'

The given Pre-IFIB datapath control

command returns error.

'[chars]: failed to unregister EDM: [chars]'

An internal error was detected when trying

to unregister EDM.

'[chars]: failed to block waiting for Event

Manager events: [chars]'

An internal error was detected when block

waiting for Event Manager events.

'[chars]: could not create event connection: An internal error was detected when trying
[chars]'
to create event connection.

'[chars]: could not set notify handler for

connection open/close/error: [chars]'

An internal error was detected when trying

to set notify handler for connection opens,
closes and errors.

'[chars]: the datapath control function for

the capsulation failed: [chars]'

An internal error was detected when calling

datapath control function for the
capsulation.

'[chars]: Invalid arguments: [chars]'

The given argument is invalid.

'[chars]: failed to publish global directory

channel: [chars]'

An internal error was detected when

publishing a global directory channel.

'[chars]: failed to initialize Pre-IFIB Mgr:

[chars]'

An internal error was detected when trying

to initialize the Pre-IFIB Mgr.

'[chars]: Corrupted reassembly server list

received: num_nodes [dec]'

The list of reassembly servers is incorrect.

'[chars]: Bag function [chars] failed:

[chars]'

An internal bag function failed.

'[chars]: Error [chars] during batching

'[chars]' from hardware pre-ifib'

Hardware pre-ifib returned an error during

a batching operation.

'[chars]: BLC '[chars]' failed for interface

handle: [hex]'

Bundle (vlan) interface update to local

bundle (vlan) database failed

'[chars]: Error [chars] while updating entry

with '[chars]' [hex]'
Error during pre-ifib entry delete or update.

An internal error was detected when trying

'[chars]: could not open all event
to open all event connections of one event
connections of this event manager: [chars]' manager.

'[chars]: could not create event manager:

[chars]'

An internal error was detected when

creating Event Manager.

An internal error was detected when trying

'[chars]: could not set up a managed timer to allocate a managed timer identifier and
identifier: [chars]'
assign to it an event handler.

An internal error was detected when trying

'[chars]: could not create a managed timer to create a managed timer tree leaf for the
tree leaf: [chars]'
event manager.

'[chars]: Error [chars] during hardware retry Hardware pre-ifib returned an error during
to update entry in TCAM'
a update retry operation.

'[chars]: Error [chars] during POS bundle

member query from IIR for ifhandle [hex]'

Hardware pre-ifib returned an error during

a batching operation.

'[chars]: error from lrd function [chars]:

[chars]'

An internal error was detected when using

a logical router daemon api

'[chars]: Not enough memory'

Memory low condition is detected.

'[chars]: Sysdb function [chars] failed:

[chars]'

An internal sysdb function failed.

'[chars]: failed to initialize with tlvlib :

[chars]'

An internal error was detected when trying

to initialize with tlvlib.

'[chars]: VRF '[chars]' failed for VRF id:

[hex]'

VRF update to attached VRFs database on

LC failed

'[chars]: Invalid flowtype [dec]'

The flow type information is not valid.

'Pre-IFIB can't establish connection to NetIO Pre-IFIB process can't establish connection
in %zd:%02zd'
to NetIO.

'Pre-IFIB establish connection to NetIO after Pre-IFIB process established connection to

%zd:%02zd'
NetIO.

'[chars]: failed to connect to the Port

Arbitrator as a Flow Forwarder: [chars]'

An internal error was detected when trying

to connect to the Port Arbitrator as a Flow
Forwarder.

An internal error was detected when trying

'[chars]: Reset of BCDL group in LPTS PA/FF to reset the BCDL group for the LPTS Port
library failed: [chars]'
Arbitrator/Flow Forwarder.

'[chars]: Error [chars] during '[chars]' from

PA'
Update from PA failed.

'[chars]: could not read input flow config

file: [chars]'

An internal error was detected when trying

to parse the input flow configuration file.

'[chars]: failed to notify sysmgr that we are An internal error was detected when trying
ready: [chars]'
to notify sysmgr that we are ready.

'[chars]: Debug cleanup failed: [chars]'

An error was returned when cleaning up

debug.

'[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]'

An error was returned when initializing

debug.

An error was returned when registering

'[chars]: Debug registration failed: [chars]' debug.

'[chars]: Initialization of lightweight tracing

buffer '[chars]' failed: [chars]'
Lightweight tracing initialization failed

'bad listener tag detected on the packet,

dropping packet'

Packet is received with unknown listener

tag, hence dropping it.

'[chars]: SysDB Bag encoding failed:

[chars]'

An internal error was detected when trying

to encode a SysDB Bag.

'[chars]: SysDB Bag registration failed:

[chars]'

An internal error was detected when trying

to register a SysDB Bag definition.

'[chars]: couldn't create event connection

manager: [chars]'

An internal error was detected when trying

to create event connection manager.

'[chars]: couldn't open event connection:

[chars]'

An internal error was detected when trying

to open event connection.

'[chars]: adding datalist as a SysDB EDM

failed: [chars]'

An internal error was detected when trying

to add an item to SysDB data list.

'[chars]: adding datalist as a SysDB EDM

failed: [chars]'

An internal error was detected when trying

to create a SysDB data list.

'[chars]: registering as a SysDB EDM failed: An internal error was detected when trying
[chars]'
to register as a SysDB EDM.

'[chars]: couldn't create event manager:

[chars]'

An internal error was detected when trying

to create event manager.

'[chars]: retrieving data from HSSD failed:

[chars]'

An internal error was detected when trying

to read data from the packet HSSD area.

'[chars]: invalid args'

Detected invalid arguments.

'Unable to get packet network start.

Dropping packet'

This failure encountered when the network

start of packet couldnot be obtained.

'[chars]: Null transport callback'

Detected a NULL transport callback

function.

'[chars]: couldn't establish connection with An internal error was detected when trying
PA: [chars]'
to open a client connection to PA.

'couldn't duplicate packet (deliver failed),

error = [dec]'

Failure in duplicating the packets, hence

packet is dropped.

'datapath control input buffer len error:

length = (%zd)'

Failed to control input buffer length.

'Couldn't set control mapping for lpts

media on fint'

LPTS media registration with FINT failed

'[chars]: [chars] failed'

Failure encountered in packet netio HSSD

register.

'[chars]: [chars] failed'

Failure encountered in IFIB lookup.

'Couldn't allocate platform-specific IFIB

result structure: [chars]'

Failure in allocating platform-specific ifib

result structure as a result packet is
dropped.

'The ltrace init for shmem file [chars]

returned error ([chars])'

An internal error is encountered during

ltrace initialization. The fallout of this could
be the respective show command to view
traces for the transport will not yield any
result.

'NULL fint idb.. dropping packet'

Failed to obtain FINT idb.

'[chars]: couldn't close the client

connection with PA: [chars]'

An internal error was detected when trying

to close the client connection with PA.

'[chars]: pak_netio_mutex_lock() failed:

[chars]'

Failed to aquire mutual lock.

'[chars]: pak_netio_mutex_unlock() failed:

[chars]'

Failed to release mutual lock.

'[chars]: pak_netio_uint8_get() failed:

[chars]'

Failed to identify version of ip packet.

'[chars]: couldn't get my node ID: [chars]'

An internal error was detected when trying

to get the node ID for the node on which
the caller is running.

'punt to [chars] failed, dropping packet:

[chars]'

One of the possible cause for this message

could be denial-of-service attack.

'failed to set platform-specific IFIB result

fields: [chars]'

Failed to set platform-secific IFIB results.

'[chars]: [chars]'

The NETIO encountered a problem of a

generic nature or an information message.

'LPTS tables changed in middle of walk.

Show command incomplete.'

During processing of a show command, the

internal LPTS data structures changed in
such a way as to make completion of the
show command impossible.

'[chars]: malloc failure'

THE NETIO encountered a problem of

memory allocation.

'[chars]: pak_netio_return_buffer() failed:

[chars]'

Failure encountered in drop count of netio

packet.

'[chars]: failed to prepare egress buffer

header of packet [pointer]: [chars]'

Failed to prepare egress buffer header for a

packet.

'[chars]: failed to process ingress buffer

header of packet [pointer]: [chars]'

Failed to process the ingress packet header.

An internal error was detected when trying

'[chars]: converting SysDB connection ID to to convert a SysDB connection ID to a file
file descriptor failed: [chars]'
descriptor.

'[chars]: converting node ID to SysDB

string failed: [chars]'

An internal error was detected when trying

to convert a node ID to a string format that
SysDB expects.

'[chars]: debug register failed: [chars] '

An internal error was detected when trying

to register for changes to debug tuples.

'lpts netio debugging failed to initialize'

An error was encountered when initializing

debug.

<[chars]:[dec]> mutex operation [chars]

A internal mutex operation has failed. This
failed for node config entry mutex: [chars] is a bug.

<[chars]:[dec]> mutex operation [chars]

failed : [chars]

A internal mutex operation has failed.

<[chars]:[dec]> mutex operation [chars]

failed : [chars]

A internal mutex operation has failed.

Failed to unpack tuple data for [chars]

Error([dec]): [chars]

Failed to unpack tuple details

[chars] failed: [chars]

Common external API returned an error

[chars]:Failed to get node name for node

[dec]

Failed to get the local node name from

platform library.

Failed to connect msg chan [chars]

Error([dec]): [chars]

LWM msg channel connect failed

event_conn_create failed. Error([dec]):

Reason: [chars]

Event conn create failure

event_conn_notify failed. Error([dec]):

Reason: [chars]

Event conn notify failure

event_conn_open failed. Error([dec]):

Reason: [chars]

Event Conn Open failure

Failed to extract fields for node [dec]

Malloc failed :[chars] at <[dec]>

Failed to extract rack/slot/instance fields

Memory running low

Failed to validate node [dec]

Failed to validate received nodeid.

qsm dir open failed. Error([dec]): [chars]

Failed to open qsm dir after retrys

Failed to send msg [chars] Error([dec]):

[chars]

LWM msg send failed

Sysdb bind failed. Error([dec]): [chars]

Sysdb bind failure

Sysdb verifier registration failed.

Error([dec]): [chars]

Sysdb verifier registration failure

ltrace initialization failed. Error([dec]):

[chars]

ltrace initialization for ltrace config failed.

Failed to connect msg chan [chars]

Error([dec]): [chars]

LWM msg channel connect failed

event_conn_create failed. Error([dec]):

Reason: [chars]

Event conn create failure

event_conn_notify failed. Error([dec]):

Reason: [chars]

Event conn notify failure

event_conn_open failed. Error([dec]):

Reason: [chars]

Event Conn Open failure

Failed to extract fields for node [dec]

Malloc failed :[chars] at <[dec]>

Failed to extract rack/slot/instance fields

Memory running low

<[chars]:[dec]> mutex destroy for node

[dec] failed : [chars]

A internal mutex destroy operation has

failed.

<[chars]:[dec]> mutex destroy for node

[dec] failed : [chars]

A internal mutex destroy operation has

failed.

<[chars]:[dec]> mutex operation [chars]

A internal mutex operation has failed. This
failed for node config entry mutex: [chars] is a bug.

<[chars]:[dec]> mutex operation [chars]

failed : [chars]

A internal mutex operation has failed.

<[chars]:[dec]> mutex operation [chars]

failed : [chars]

A internal mutex operation has failed.

Failed to validate node [dec]

Failed to validate received nodeid.

qsm dir open failed. Error([dec]): [chars]

Failed to open qsm dir after retrys

Failed to send msg [chars] Error([dec]):

[chars]

LWM msg send failed

Sysdb bind failed. Error([dec]): [chars]

Sysdb bind failure

Sysdb verifier registration failed.

Error([dec]): [chars]

Sysdb verifier registration failure

Failed to unpack tuple data for [chars]

Error([dec]): [chars]

Failed to unpack tuple details

[chars] failed: [chars]

Common external API returned an error

ltrace initialization failed. Error([dec]):

[chars]

ltrace initialization for ltrace config failed.

[chars]:Failed to get node name for node

[dec]

Failed to get the local node name from

platform library.

Extending the trace string data to [dec]

traces ran out of memory

The show decode helper library attempted

to extend its database of decode trace
string data and was unable to do so. Any
trace using this string may not be
printable.

The show decode helper library isolates

string trace data into group keyed by trace
name and nodeid. The library was unable
to obtain memory for one of this group
items. Because of this, the library will not
be able to print out data from the given
Unable to get space for group header data trace name/node grouping.

Unable to decode nodeid because [chars]

The show helper was unable to decode a

text name for the node id a given trace
block containing string data came from. As
a result of this, the given trace will not be
printable.

The show decode helper library breaks up

string data for mesasages into single trace
buffers and reassembles them. There was
not enough memory to create the string
Unable to get string data for trace [dec] of space to hold the data. Any trace using this
length [dec]
string may not be printable.

The show decode helper library breaks up

string data for mesasages into single trace
buffers and reassembles them. While
putting the trace data back together, the
sequence received was not the expected
Sequence of string data on trace [dec] was next sequence. Any trace using this string
[dec] instead of the expected [dec]
may not be printable.

The message decode locate for '[chars]'

failed because:[chars]

The show decode helper library isolates

string and trace data to a given trace name
and node. The attempt to find this in the
lookup tree failed for the above reason.
Any trace using this string may not be
printable.

The message decode insert for '[chars]'

failed because:[chars]

The show decode helper library isolates

string and trace data to a given trace name
and node. The attempt to insert this into
the lookup tree failed for the above reason.
Any trace using this string may not be
printable.

Extending the trace string data to [dec]

traces ran out of memory

The show decode helper library attempted

to extend its database of decode trace
string data and was unable to do so. Any
trace using this string may not be
printable.

The show decode helper library isolates

string trace data into group keyed by trace
name and nodeid. The library was unable
to obtain memory for one of this group
items. Because of this, the library will not
be able to print out data from the given
Unable to get space for group header data trace name/node grouping.

Unable to decode nodeid because [chars]

The show helper was unable to decode a

text name for the node id a given trace
block containing string data came from. As
a result of this, the given trace will not be
printable.

The show decode helper library breaks up

string data for mesasages into single trace
buffers and reassembles them. There was
not enough memory to create the string
Unable to get string data for trace [dec] of space to hold the data. Any trace using this
length [dec]
string may not be printable.

The show decode helper library breaks up

string data for mesasages into single trace
buffers and reassembles them. While
putting the trace data back together, the
sequence received was not the expected
Sequence of string data on trace [dec] was next sequence. Any trace using this string
[dec] instead of the expected [dec]
may not be printable.

The message decode locate for '[chars]'

failed because:[chars]

The show decode helper library isolates

string and trace data to a given trace name
and node. The attempt to find this in the
lookup tree failed for the above reason.
Any trace using this string may not be
printable.

The message decode insert for '[chars]'

failed because:[chars]

The show decode helper library isolates

string and trace data to a given trace name
and node. The attempt to insert this into
the lookup tree failed for the above reason.
Any trace using this string may not be
printable.

The internal message storage space

optimizer failed to lookup the string being
stored. This is not a critical, since the string
will still be stored, however it does possibly
[chars]: The message storage optimization indicate a lower level memory corruption or
failed in btree lookup for '[chars]':[chars]
other problem.

The internal message storage space

optimizer failed to insert the string being
stored. This is not a critical, since the string
will still be stored, however it does possibly
[chars]: The message storage optimization indicate a lower level memory corruption or
failed in btree insert for '[chars]':[chars]
other problem.

The internal message storage space

optimizer failed to lookup the string being
stored. This is not a critical, since the string
will still be stored, however it does possibly
[chars]: The message storage optimization indicate a lower level memory corruption or
failed in btree lookup for '[chars]':[chars]
other problem.

The internal message storage space

optimizer failed to insert the string being
stored. This is not a critical, since the string
will still be stored, however it does possibly
[chars]: The message storage optimization indicate a lower level memory corruption or
failed in btree insert for '[chars]':[chars]
other problem.

[chars]: Failed to init ltrace config thread

Failed to init ltrace config thread after

several retrys.

<[chars]:[dec]> pthread attr set detach

failed [chars]

Failed attr set detach for thread.

<[chars]:[dec]> pthread attr init failed

[chars]

Failed to init pthread attr.

[chars] failed: [chars]

Common external API returned an error

[chars]: Failed to get the local nodes

internal node name

Failed to get the local node name from

platform library.

[chars]: Failed to init ltrace config thread

Failed to init ltrace config thread after

several retrys.

<[chars]:[dec]> pthread attr set detach

failed [chars]

Failed attr set detach for thread.

<[chars]:[dec]> pthread attr init failed

[chars]

Failed to init pthread attr.

[chars] failed: [chars]

Common external API returned an error

[chars]: Failed to get the local nodes

internal node name

Failed to get the local node name from

platform library.

[chars] failed: [chars]

Common external API returned an error

file [chars] has bad magic number [hex],

should be [hex]

The file has wrong magic number.

memory unmapping for [chars] failed. size:

[dec]. Error([dec]): [chars]
Memory unmapping for the file failed.
[chars] failed. Error([dec]): [chars]

Pthread API returned an error

[chars] for [chars] failed. Error([dec]):

[chars]

Read-write lock failed.

The size of file [chars] couldn't be changed

to [dec]. Error([dec]): [chars]
The operation to change the file size failed.
ltrace initialization failed. Error([dec]):
[chars]

ltrace initialization for ltrace

synchronization server failed.

memory mapping for [chars] failed. size:

[dec] protection:[hex] flags:[hex]
fd:0x[dec] off:[dec] Error([dec]): [chars]

Memory mapping for the file failed.

ltrace shmem [chars] failed for [chars].

flags:[hex] mode:%o Error([dec]): [chars]

Shared memory operation failed.

file [chars] is too short. size:[dec] version:

[dec]

The file is read when it's being written, or

version mismatch between the file and the
reader.

file [chars] has wrong version [dec], should

be [dec]
The file has wrong version.
[chars] failed: [chars]

Common external API returned an error

file [chars] has bad magic number [hex],

should be [hex]

The file has wrong magic number.

The size of file [chars] couldn't be changed

to %zd. Error([dec]): [chars]
The operation to change the file size failed.
file [chars] is too short. size:[dec] version:
[dec]

The file is read when it's being written, or

version mismatch between the file and the
reader.

file [chars] has wrong version [dec], should

be [dec]
The file has wrong version.
ltrace initialization failed. Error([dec]):
[chars]

ltrace initialization for ltrace

synchronization server failed.

memory mapping for [chars] failed. size:

[dec] protection:[hex] flags:[hex]
fd:0x[dec] off:[dec] Error([dec]): [chars]

Memory mapping for the file failed.

memory unmapping for [chars] failed. size:

[dec]. Error([dec]): [chars]
Memory unmapping for the file failed.
[chars] failed. Error([dec]): [chars]

Pthread API returned an error

[chars] for [chars] failed. Error([dec]):

[chars]

Read-write lock failed.

ltrace shmem [chars] failed for [chars].

flags:[hex] mode:%o Error([dec]): [chars]

Shared memory operation failed.

[chars] failed: [chars]

Required functionality failed or returned an

error

truncate for [chars] file to a specified

length failed. Failed parameters, index:
[dec] length:[dec] file descriptor:[dec].
Error([hex]): [chars]

ftruncate system call returned an

unexpected error Debug trace buffer
initialization failed.

[chars] Failed parameters, index:[dec]

length:[dec] file descriptor:[dec].
Error([hex]):[chars]

mmap system call returned an unexpected

error Debug trace buffer initialization
failed.

Initializing mutual access exclusion for

[chars] file failed. Error([hex]): [chars]

pthread_mutex_init system call returned an

unexpected error Debug trace buffer
initialization failed.

Opening trace log file [chars] failed,

Error([hex]): [chars]

open system call returned an unexpected

error Debug trace buffer initialization
failed.

Internal debugging message. For

subsequent analysis of magic number
magic number corrupted, filename:[chars], corruption, snapshot of running process
pid:[dec] tid:[dec]
core dump has been taken.
Internal debugging message. For
block header magic number corrupted
subsequent analysis of magic number
([hex] != [hex]), filename:[chars], pid:[dec] corruption, snapshot of running process
tid:[dec]
core dump has been taken.
Internal debugging message. For
subsequent analysis of magic number
control magic number corrupted ([hex] != corruption, snapshot of running process
[hex]), filename:[chars], pid:[dec] tid:[dec] core dump has been taken.
[chars] [chars] [chars]
Internal debugging message.
[chars] [chars] [chars]
Internal debugging message.
[chars] failed: [chars]

Required functionality failed or returned an

error

truncate for [chars] file to a specified

length failed. Failed parameters, index:
[dec] length:%zd file descriptor:[dec].
Error([hex]): [chars]

ftruncate system call returned an

unexpected error Debug trace buffer
initialization failed.

[chars] Failed parameters, index:[dec]

length:%zd file descriptor:[dec].
Error([hex]):[chars]

mmap system call returned an unexpected

error Debug trace buffer initialization
failed.

Initializing mutual access exclusion for

[chars] file failed. Error([hex]): [chars]

pthread_mutex_init system call returned an

unexpected error Debug trace buffer
initialization failed.

Opening trace log file [chars] failed,

Error([hex]): [chars]

open system call returned an unexpected

error Debug trace buffer initialization
failed.

scaling down string buffer [chars] (len:

[dec]) by [dec]

Internal debugging message.

scaling down string buffer [chars] (len:

[dec]) by [dec]

Internal debugging message.

Unlinking trace log file [chars] failed,

Error([hex]): [chars]

unlink() system call returned an

unexpected error Debug trace buffer
initialization failed.

scaling down wrap buffer [chars] (len:[dec])

by [dec]
Internal debugging message.
scaling down wrap buffer [chars] (len:[dec])
by [dec]
Internal debugging message.
[chars]: Corrupted channel list for [chars].
Memory lost, chan=[pointer],
infop=[pointer], connectp=[pointer]
magic=[hex] guard=[hex]

A corrupt memory area was discovered in

an internal data structure

[chars]: Corrupted channel list for [chars].

Memory lost, chan=[pointer],
infop=[pointer], connectp=[pointer]
magic=[hex] guard=[hex]

A corrupt memory area was discovered in

an internal data structure

[chars]: Corrupted channel list for [chars].

Iteration Skipped, chan=[pointer],
infop=[pointer], connectp=[pointer]
magic=[hex] guard=[hex]

A corrupt memory area was discovered in

an internal data structure. A function that
was searching the open connection list was
not able to process all open connections.

[chars]: Corrupted channel list for [chars].

Iteration Skipped, chan=[pointer],
infop=[pointer], connectp=[pointer]
magic=[hex] guard=[hex]

A corrupt memory area was discovered in

an internal data structure. A function that
was searching the open connection list was
not able to process all open connections.

Invalid msg_error errcode: [dec]

The msg_error error codes are limited to

errno values. Any error values with high
bits set (such as -1) are invalid.

Invalid msg_error errcode: [dec]

The msg_error error codes are limited to

errno values. Any error values with high
bits set (such as -1) are invalid.

[chars]: Could not lock conn_list for [chars]: The mutex for the channel connection list
[chars]
could not be held

[chars]: Could not lock conn_list for [chars]: The mutex for the channel connection list
[chars]
could not be held

[chars]: Could not unlock conn_list for

[chars]: [chars]

The mutex for the channel connection list

could not be released

[chars]: Could not unlock conn_list for

[chars]: [chars]

The mutex for the channel connection list

could not be released

Invalid error check value: [hex]

An unexpected value was found in the error

check.

A NULL pointer was passed to free

An attempt was made to free a null pointer

Invalid [chars] value in header: [hex]

An unexpected value was found in the

header. This might indicate a buffer
overflow

Memory allocation failed

A call to malloc failed.

Attempt to use unsupported function:

memalign()

This function is not supported.

Received unknown signal value [unsigned

int]

An unexpected signal value was received.

Attempt to allocate more than 16MB using A process attempted to malloc more than
[chars]()
the maximum size of 16MB

event_block error -- [chars]

Error during event block

Sysdb registration for [chars] failed. Error:

[chars]

Sysdb registration failure

Malloc failed

Memory running low

Unable to bind to [chars]. Error: [chars]

Could not connect to sysdb

[chars] failed: [chars]

An error occurred while processing an

infrastructure service request. This should
happen mostly due to resource exhaustion.

Failed mmap() for process [dec] on [chars] :

[chars], requested addr [pointer], size
[dec], \ returned addr [pointer]
The mmap() failed in mmap_peer_local.
Failed munmap() for process [dec] on
[chars] : [chars]

The munmap() failed in mmap_peer_local.

Failed readlink() on [chars]: [chars]

Failed to get original filedname for the fd.

received msg on domain socket [chars]

with wrong size [dec]

The recv() has unexpected message size.

Failed shm_open() on [chars]: [chars]

The open() failed in mmap_peer_local.

Failed to connect from process [dec] to

[dec]: [chars]

Failed connect() for a domain socket.

Failed to recv [chars] reply for process

[dec] from [dec]: [chars]

Failed recv() for a domain socket.

Failed to send [chars] message from

process [dec] to [dec]: [chars]

Failed send() for a domain socket.

pid [dec], [chars]

For debug only.

Cannot load DLL: [chars]

Cannot load DLL error.

Cannot find symbol [chars] in DLL [chars]

Cannot find DLL symbol error.

[chars] : [chars]

Initialization failed

mpls vpn mib event tracing subsytem

initialization failed

mpls vpn mib could not initialize the

tracing module

NCD Init : [chars]%s

An software error occurred during the

initialization of the NCD process.

Checksum failed on received packet; Pak:

[pointer] Length:%zd Offset:[dec]
Computed Checksum:[unsigned int]

A checksum error was detected for a

packet by NCD.

Checksum failed on received packet;

Pak:0x[pointer] Length:[dec] Offset:[dec]
Computed Checksum:[unsigned int]

A checksum mismatch was detected for a

packet by NCD.

[chars] operation failed on packet;

Pak:0x[pointer] Offset:[dec] Size:[dec]
error:[chars]

The specified operation failed on the

packet.

RP Isolation failed. Err:[chars]. Falling back RP Isolation failed on this node. Node will
to reboot.
take the regular reload path.

Checksum failed on received packet;

Pak:0x[pointer] Length:[dec] Offset:[dec]
Computed Checksum:[unsigned int]

A checksum error was detected for a

packet by NCD.

[chars] operation failed on packet;

Pak:0x[pointer] Offset:[dec] Size:[dec]
error:[chars]

The specified operation failed on the

packet.

RP Isolation is not supported on this

platform/card/config type. Falling back to
reboot.

RP Isolation is not supported either on this

platform, on this card type or it is not
configured. A normal reboot will be done.

[chars]: info [hex]([chars]) error: [hex]

([chars])

--

[chars]-E-[chars]\n

--

Incorrect arguments: Usage: [chars]

[svr_threads]

Incorrect command line parameters were

passed to the nrs server, and so it failed to
start.

checkpoint create failed for attr [dec],

handle [hex], err [hex]

chkpt_create failed while creating an object

in a chkpt table.

checkpoint save failed for attr [hex],

handle [hex], err [hex]

chkpt_save failed while updating an object

in a particular table.

checkpoint create failed for [chars], handle chkpt_create failed while creating an object
[hex], name [chars], err [hex]
in a chkpt table.

saved class [chars], handle [hex] to

checkpoint table

chkpt_iterate_* failed while iterating

through the chkpt list.

checkpoint delete failed for table [chars],

handle [hex], err [hex]

chkpt_delete_bykey failed while deleting

the object present in the chkpt table.

chkpt_iterate_[chars] failed for table 0x

%zx, err [hex]

chkpt_iterate_* failed while iterating

through the chkpt list.

chkpt_iterate_next failed for table 0x%zx,

after [dec] iterations, err [hex]

chkpt_iterate_* failed while iterating

through the chkpt list.

checkpoint register failed for table [dec],

err [hex], [chars]

chkpt_register failed while creating a chkpt

table id.

Failed to restore attr, attr [hex], handle

[hex] from checkpoint table, err [hex],
[chars]

nrs_chm_chkpt_create_attr failed while

restoring the set attributes from chkpt
shared memory after nrs server process
restarts.

nrs_chm_chkpt_create_class failed while

restoring the class handles from the chkpt
Failed to restore class [chars], handle [hex] shared memory after nrs server process
from checkpoint table, err [hex], [chars]
restarts.

nrs_chm_chkpt_create_data failed while

restoring the data handles from the chkpt
Failed to restore data [chars], handle [hex] shared memory after nrs server process
from checkpoint table, err [hex], [chars]
restarts.

restoring from chkpt class [chars], handle

[hex], index [hex] to checkpoint table

chkpt_iterate_* failed while iterating

through the chkpt list.

restored from chkpt class [chars], handle

[hex], index [hex] to checkpoint table

chkpt_iterate_* failed while iterating

through the chkpt list.

Failed to restore set, exp [chars], handle

[hex] from checkpoint table, err [hex],
[chars]

nrs_chm_chkpt_create_set failed while

restoring the set attributes from chkpt
shred memory after nrs server process
restarts.

checkpoint save failed for [chars], handle

[hex], name [chars], err [hex]

chkpt_save failed while updating an object

in a particular table.

checkpoint unregister failed for table

[chars], class [chars], err [hex]

chkpt_unregister failed while unregistering

the chkpt table.

RDS producer calls writer aquire and which

ens_publish call failed [chars] handle([hex]) in turn calls ens_publish. This call may be
len([unsigned int])
failed due to underneath transport issue.

ens_write call failed [chars] handle([hex])

len([unsigned int])

ens_write call has failed. This call may be

failed due to underneath transport issue.

[chars]:[dec] Error: event_message_attach

error [dec]
event_message_attach() failed.

An NRS Server hit an error from which it

NRS Server restarting due to error [hex] in could not recover during initialisation and
intialisation
is restarting to continue normal operation.

[chars]: rc [hex], [chars]

The server has either failed a function that

expected to succeed, or has got into an
inconsistent state.

Failed to [chars] [chars]. Error [dec]

The server has either failed to aquire or

release a lock.

Failed to allocate %zu bytes

The server has failed to acquire the

required amount of memory.

[chars]:[dec] could not reply to the

message

msg_reply() failed to send the reply.

A NULL pointer was passed as a fn

parameter

Invalid arguments are passed to the

function.

regcomp failed - error [hex], regex [chars]

The server has either failed a function that

expected to succeed, or has got into an
inconsistent state.

trying to create or get data [chars] handle

[hex] of class [chars] with previous id [hex]
and new id [hex]
try to register a data with diff id

Failed to send reply to client pid [unsigned The server failed to reply to a client
int] tid [unsigned int]: rc [hex]
request.

NRS Server restarting due to error during

operation. Error [hex], [chars]

An NRS Server hit an error from which it

could not recover and is restarting to
continue normal operation.

[chars]: rc [hex], [chars]

The server's EDM has either failed a

function that expected to succeed, or has
got into an inconsistent state.

Ltrace init for file [chars] failed [chars]

--

[chars]: rc [hex]

The client library has either failed a

function that expected to succeed, or has
got into an inconsistent state.

Failed to malloc [unsigned int] bytes

The nrs common library has failed to aquire

the required amount of memory.

A NULL pointer was passed as a fn

parameter

A NULL pointer was passed as a fn

parameter

Not enough memory available in the

Failed in allocating memory with size:[dec] system.

Fail to get sdd information, file size: [dec]

Fail to get sdd information

Garbage [dec] bytes at the end

File has garbage bytes at the end.

Invalid historical file format. [chars]. field

id: [dec]. Abort printing file contents.

Invalid historical file format.

Invalid record type, type: [dec]

Invalid record type

process's JobID can not be obtained

process's JobID can not be obtained

The string([chars]) is longer than buffer

length([dec]).

The string length is too long.

process(JobID:[dec]) notified symbol:

[chars] but it is not found in dll:[chars].
Error:[chars]

A symbol notified from a process is not

found

Unable to get the nodename of this card,

file name: [chars]

Unable to get the nodename of this card

Failed to execute application

function([chars]: [chars]), client_id:[dec],
descriptor:[dec], error([dec]): [chars]

Failed to execute some application

functions.

Failed to execute application registration

function([chars]), nodeid:[hex],
error([dec]): [chars]

Failed to execute application registration

function.

Invalid client_id [dec] is returned for

feature:[chars] target_node:[hex].

Invalid client_id is created.

process's JobID can not be obtained

process's JobID can not be obtained

Failed to allocate %zd bytes

Not enough memory available in the

system.

Failed to get nodeid for [chars].

Error([dec]): [chars]

Failed to get nodeid.

Cannot set more sensor ID than number of Cannot set more sensor ID than number of
sensors([dec]).
sensors.

Sensor([dec]) is not found

No sensor found

feature [chars] is too long name

Too long feature name is specified

process's JobID can not be obtained

process's JobID can not be obtained

[chars] of nodeid for [chars] failed.

Error([dec]): [chars]

An error happened for a nodeid operation.

device [chars] is too long name

Too long device name is specified

[chars], Error([dec]): [chars]

Failed in some event management

functions.

Invalid record magic number: [hex]. [hex]

is expected. Abort reading the file
contents.

Invalid magic number

Received a bad message. error_val:[dec]

error_info:[chars]

The message received by the server had

inconsistent values.

Failed to allocate %zd bytes at <[chars]:

[dec]>

Not enough memory available in the

system.

platform data file:[chars] doesn't exist

The platform data file doesn't exist.

no destination OBFL manager found

Destination OBFL manager path is not

found.

[chars] of nodeid for [chars] failed.

Error([dec]): [chars]

An error happened for a nodeid operation.

nodeid for [chars] can not be obtained

Self nodeid can not be obtained.

platform data file:[chars] scan failed.

Error([dec]): [chars]

An error happened while reading the

platform data file.

[chars] failed. Error([dec]): [chars] :

<[chars]:[dec]>

Failed in a pthread function.

Too short record size:[dec] for [chars]

record. The file contents might be
corrupted.

A feature record is too short.

Type mismatch for [chars] record.

Record_type:[dec] My_type:[dec].

A feature record has different type with

current software.

Version mismatch for [chars] record.

Record_version:[dec] My_version:[dec].

A feature record has different version

format with current software.

[chars]: [chars]() failed: [chars]

The client library has failed a system call.

Timer Error. [chars]. Error([dec]): [chars] at

<[chars]:[dec]>
Something went wrong with the timer

process's JobID can not be obtained

process's JobID can not be obtained

[chars] [chars]. Error([dec]): [chars]

Failed in re-sending a message after

onboard logging server process resart.

Unsupported API [chars] called by process

[chars]

The call is not supported by OBFL infra.

Received a corrupted message data with

cksum:[hex] Calculated cksum:[hex]
length:[dec] type:[dec]

The message received by an application

had a wrong cksum value. The message
data could be corrupted.

Received a corrupted message header with

cksum:[hex] Calculated cksum:[hex]
The message received by an application
length(corrupted?):[dec] type(corrupted?): had a wrong cksum value. The message
[dec]
data could be corrupted.

Received message has wrong reply

data:0x[pointer] data_len:%zd
actual_data_len:%zd

The message received by an application

had a wrong reply data. The message data
could be corrupted.

process terminated with code:[dec] at

<[chars]:[dec]>

An OBFL process exit.

Garbage [dec] bytes at the end of a buffer

for [chars]
A buffer has garbage bytes at the end.

<[chars]:[dec]> server:[chars]

debug print before msg_chan_connect

<[chars]:[dec]> server:[chars]

debug print before qsm_stat

<[chars]:[dec]> conn:[pointer]
target_node:[pointer]

debug print before msg_sendv

[chars] [chars]. Error([dec]): [chars]

An error happened in a file operation.

Too long record size:[dec] for [chars]

record. The file contents might be
corrupted.

A feature record is too long.

decoding of rack:[hex] and slot:[hex] for

[chars] failed. Error([dec]): [chars]

An error happened for a nodeid decoding.

[chars] [chars] is too long name

Too long name is specified

checksum for [chars] is wrong. Original:

[hex] Calculated:[hex] offset:[dec]. The
contents of [chars] could be corrupted.

A checksum of a record is wrong. The file

could be corrupted. The file should be
saved to other place for later debugging,
and then it should be removed to recover
current situation.

Failed to [chars] env static data record.

Error([dec]): [chars]

An environment record data processing

error.

Failed to create event connection. Error:

[chars]

Failed to create event connection.

Failed to attach a handler for an event

connection. Error: [chars]

Failed to attach a handler for an event

connection.

Failed to open an event connection. Error:

[chars]

Failed to open an event connection.

[chars] [chars]. Error: [chars]

Failed to initialize a timer for an event

manager.

[chars], Error([dec]): [chars]

Failed in some event management

functions.

file size for [chars] can not be obtained

from platform DB

An OBFL file size can not be obtained from

platform DB.

A file's max limit is too small for [chars], or

internal parameters might be corrupted.
A file's max limit is too small, or internal
cur_data_size:%zd file_size_limit:%zd.
parameter might be corrupted.

Too large historical group for [chars], or

internal parameters might be corrupted.
cur_data_size:%zd writing_group_size:[dec] A historical group is too large, or internal
file_size_limit:[dec].
parameter might be corrupted.

[chars], Error([dec]): [chars]

Failed to execute some LWM library

functions.

Msg:[chars] version:[dec] mismatch from

jid:[dec]. Correct version:[dec].

A msg from an application has different

version format with current software.

Mutex reset error. Exit and restart the

process

Failed to reset a corrupted mutex. Restart

the process.

A file [chars] doesn't have its final clear

record after compressed records, or
internal parameters might be corrupted.
cur_data_size:%zd file_size_limit:%zd.

A file don't have its final clear record which

is necessary for coalescing.

A record length:%zd and the LWM

msg_length:%zd doesn't match for [chars] The message received by an application
feature
had inconsistent record length.

Too short record size:%zd for [chars] record

at offset:%zd. The file contents might be
corrupted.
A feature record is too short.

Version mismatch for [chars] record at

offset:%zd. Record_version:[dec]
My_version:[dec].

A feature record has different version

format with current software.

[chars], Error([dec]): [chars]

Failed to init redundancy state.

[chars] [chars] failed. Error([dec]): [chars]

Failure in self management callback

routine.

process(JobID:[dec]) notified symbol:

[chars] for owner:[chars], but it is not
found. Error:[chars]

A dll notified from a client is not found

Sysdb bind failed for [chars] [chars].

Error([dec]): [chars]

Sysdb bind error

Falied edm initialization. Error: [chars]

Falied edm initialization.

sysdb registration edm error. Error: [chars] Registration fail for sysdb edm.

sysdb registration (notification) error,

[chars] [chars], [chars]

Registration fail for sysdb notification

sysdb registration (verification) error,

[chars] [chars], [chars]

Registration fail for sysdb verification

Error in thread pool [chars] and

Error([dec]): [chars]

Thread pool error

previous DLL:[chars] notified from

process(JobID:[dec]) for FEATURE:[chars]
can not be unloaded. Error:[chars]

An old DLL can not be unloaded

Received a bad message with value:[dec]: The message received by the server had
[chars]
inconsistent values.

client_id:[dec] specified from process(JobID:

[dec]) caused an error:[chars]
Specified client ID caused an error.

Failed to get ReloadReason. Return:[dec],

result:[dec].

devctl error.

device:[chars] on node:[chars] is disabled

by user configuration

A device is disabled for logging onboard by

user configuration.

device:[chars](nodeid:[hex]) is deactivated
for onboard logging due to [dec] times
write error to file:[chars]. The last
The device on the node is deactivated for
Error([dec]): [chars]
onboard logging.
device:[chars] on node:[chars] is disabled
by user configuration

A device is disabled for logging onboard by

user configuration.

feature:[chars] on device:[chars](nodeid:
[hex]) failed to get platform information
from [chars], and is deactivated

A feature is deactivated because it couldn't

get platform information from a new
platform library.

file:[chars](fp:[pointer], fd:[dec]) [chars]

failing. [dec] retry so far. Error([dec]):
[chars]

Failed to open/close an OBFL file.

[chars] can not be opened. Error([dec]):

[chars]

File open failure.

Tried to write [dec] bytes to file: [chars]

(total size [dec]). Error([dec]): [chars]

File write failure.

QSM publish obfl config master path failed

for [chars] [chars] with class[hex].
Error([dec]): [chars]
QSM publish obfl config master path failure

queue clear error. elems:%zd first:[pointer]

last:[pointer]
failed to clear internal queue.

sysmgr API [chars] failed. Error([dec]):

[chars]

An error happened for a sysmgr API.

Unsupported FEATURE: [chars] called by a

process(JobID:[dec])

The feature is not supported by OBFL.

ResetReason is not set.

ResetReason is not yet set.

Received a corrupted message for [chars]

with value:[dec]: [chars]

The message received by an application

had inconsistent values.

Received a corrupted message with cksum:

[hex] Calculated cksum:[hex]
The message received by an application
length(corrupted?):[dec] type(corrupted?): had a wrong cksum value. The message
[dec]
data could be corrupted.

device:[chars](nodeid:[hex]) is activated
for onboard logging.

The device on the node is activated for

onboard logging.

device:[chars] on node:[chars] is enabled

by user configuration

A device is enabled for logging onboard by

user configuration.

feature:[chars] on device:[chars](nodeid:
[hex]) is activated

A deactivated feature is activated.

Coalescing failed for feature:[chars] device: Coalescing failed on a device. Records for
[chars](node:[hex]) because [chars].
the device will be discarded.

process(JobID:[dec]) notified coalescer:

[chars] for FEATURE:[chars], but it is not
found

A coalesce function name notified from a

client is not found

device on the node(ID:[hex]) is not active

The device on the node is not active.

no device ready for feature:[chars] from

process(JobID:[dec]). target_node:[hex]
client_id:[dec] device:[pointer].

no device ready yet for notified feature

device:[chars] notified from process(JobID:

[dec]) is not registered
Caller's device is not yet registered

device [chars] on nodeid:[hex] is not

accessible on the filesystem. Error([dec]):
[chars]

A device specified from a driver is not

accessible.

Unknown environment state:[dec] of node: An environment record has an unknown

[hex]
state.

Syslog historical file buffer reached the

limit. Current size:%zd. limit:%zd.
Subsequent syslog historical records will be
discarded.
Syslog historical file reached the limit.

process's JobID can not be obtained

process's JobID can not be obtained

Invalid magic number:[hex] for [chars]

record. [hex] is expected. The file contents A feature record has an invalid magic
might be corrupted.
number.

Failed to write [chars] meta oper record to

the file:[chars]. Error([dec]): [chars]

An OBFL internal record type write failure.

Received a bad message with value:[dec]: The message received by an application

[chars]
had inconsistent values.

Failed to allocate memory with size:[dec] at Not enough memory available in the
<[chars]:[dec]>
system.

decoding of nodeid:[hex] for [chars] failed.

Error([dec]): [chars]
An error happened for a nodeid decoding.

[chars] of nodeid for [chars] failed.

Error([dec]): [chars]

An error happened for a nodeid operation.

The queue:[pointer] for device:[chars]

entry_num:[dec] and the max limit:[dec].
The new request for [chars] will be
discarded.

The destination queue is full. New enqueue

request will be discarded.

decoding of rack:[hex] for [chars] failed.

Error([dec]): [chars]

An error happened for a rackid decoding.

Too long record size:[dec] for [chars]

record. The file contents might be
corrupted.

A feature record is too long.

Unknown record type:[dec] for [chars]

record. The file contents might be
corrupted.

A feature record has an unknown record

type.

logging to node:[hex] is denied because

this node:[hex] is redundancy standby
state.

Node is redundancy standby state, so can't

log to other node.

decoding of rack_type:[hex] and slot:[hex] An error happened for a slot fields

for [chars] failed. Error([dec]): [chars]
decoding.

[chars] sysdb tuple, [chars] at <[chars]:

[dec]>

Invalid sysdb tuple

Unregistered FEATURE:[chars] called by a

process(JobID:[dec])

The specified feature is not yet registered

for OBFL manager.

Too large continuous record, or internal

parameters might be corrupted. length:
[dec].

A continuous record too large, or internal

parameter might be corrupted.

Invalid block_and_task_id:[hex]. The file

contents might be corrupted.

This record has invalid block_and_task_id.

Too large historic uptime record([chars]), or

internal parameters might be corrupted.
A historic uptime record too large, or
length:[dec] offset_ehud:[dec].
internal parameter might be corrupted.

Uptime record([chars]) is not found.

Uptime record is not found

'[chars]: Can't create VRF context

structures. VRF '[chars]' ([hex]) error
[chars] ([unsigned int])'

PA Can't create VFR context structures.

'[chars]: [chars] failed rc=[chars]'

There was a ENA infra call failure resulting

in a failure to provide some infrastructure
service.

'RSI [chars] failed error [chars] ([unsigned

int])'

Failure encoutered when initializing the RSI

for Port Arbitrator.

'Unknown event from RSI event [unsigned

int]'

RSI sent unknown event

'[chars]: [chars] failed: [chars]'

Bag api call failed.

'Error setting linear connection retry

mechanism : [chars]'

Failed to set linear connection retry

mechanism in Port Arbitrator Client

'[chars]: [chars] failed\n[chars]'

Sysdb api call failed.

'[chars]: Assign of slice [chars] to node

[hex] failed. ([chars])'

The PA failed to assign an IFIB slice.

'[chars]: [chars] failed'

Sysdb backend api call failed.

The PA process failed while attempting to

'PA failed to connect to the event manager: connect to an event manager channel for
[chars]'
the indicated subsystem.

'[chars]: [chars] update of slice [chars] to

node [hex] timed out.'

The PA failed to receive a response to an

IFIB table update or an IFIB slice
assignment update message.

'[chars] line [dec]: error: [chars]'

An attempt to lock a mutex failed.

'[chars] line [dec]: error: [chars]'

An attempt to lock a mutex failed.

'[chars]: [chars]'

The PA encountered some problem in

genric nature or plain information.

'[chars]: Pre-IFIB update for slice [chars]

timed out.'

The PA failed to receive a response to a

critical Pre-IFIB update.

[chars] failed: [chars]

[chars] [chars] [chars]

Required functionality failed or returned an

error
Internal debugging message.

lrd call to get dlrsc node id in [chars]:

[chars]: [hex]: [chars]

A placed client API failed in the call to lrd to

get the dlrsc nodeid

platform call in [chars]: [chars]: [hex]:

[chars]

A placed client API failed in the call to

platform api to get its nodeid or node
name. Its an issue with platform call.

[chars]: Failed to connect to lead placed:

[hex]: [chars]

An attempt to connect to the lead placed

server failed with the specified reason. It
may be the case that placed server had
been restarted.

[chars]: Failed to send [chars] message to

placed: [hex]: [chars]

An attempt to send a message to the

placed server failed with the specified
reason. It may be the case that placed
server had been restarted.

System placement policy found in [chars].

Policy should be moved to a .placement
file.

PlaceD discovered system placement policy

specified in an unsupported format; the
policy will not be honored. The system
should continue to function correctly,
though process placement decisions may
be sub-optimal.

Overflow in message vector ([dec] entries

used, [dec] available)

A client was unable to send a message to

PlaceD due to encountering an internal
error condition.

Migration completed. Time taken to

migrate:[dec] seconds

Migration completed in x seconds.

Unable to consume requests from ADR:

[chars]

Unable to consume requests from ADR.

Unable to initialize atomic descriptor ring:

[chars]

Unable to initialize atomic descriptor ring.

Unable to produce:[chars]

Unable to produce requests in ADR.

[chars]:[dec]

PlaceD received an unexpected message.

Failed to obtain card type: [chars]

PlaceD daemon was unable to obtain the

card type. Recovery occurs with automatic
process restart.

Unable to open a CDM table:[chars]

Unable to open a CDM table.

Error on signaling COND variable:[chars]

Error signaling cond variable.

Unable to initialize COND variable:[chars]

Unable to initialize cond variable.

Unable to signal COND variable:[chars]

Unable to signal cond variable.

Unable to turn on debug flag - '[chars]':

[chars]

An error occured whilst PlaceD tried to turn

on debugs.

An error occured whilst PlaceD tried to

Unable to register with debug infra:[chars] register with debug infra.

Failed to create an ECM: [chars]

PlaceD daemaon was unable to create an

ecm. Recovery occurs with automatic
process restart.

Failed to set up ecm notify: [chars]

PlaceD daemaon was unable to set up ecm

notify.

Failed to open ecm: [chars]

PlaceD daemaon was unable to open ecm.

Failed to set retry for ecm: [chars]

PlaceD daemaon was unable to set retry for

ecm. Recovery occurs with automatic
process restart.

Failed to create an event manager for

channel '[chars]': [chars]

PlaceD daemaon was unable to create an

event manager for receiving messages,
and therefore failed to initialize. Recovery
occurs with automatic process restart.

Failed to attach event handler to event

manager: [chars]

PlaceD daemon was unable register an

event handling for processing received
messages, and therefore failed to initialize.
Recovery occurs with automatic process
restart.

evm NULL

Evm null. Recovery occurs with automatic

process restart.

Process [chars] (jid [dec]) exited before

sending EOI

Process failed to send EOI and exited.

Error getting group count:[chars]

Unable to get group count for

PLACEMENT_GSP_GROUP.

Error creating [chars] group:[chars]

Unable to create PLACEMENT_GSP_GROUP.

Error setting up group notify:[chars]

Unable to set group notify for

PLACEMENT_GSP_GROUP.

Error broadcasting msg [chars] to group:

[chars]

Unable to broadcast msg to members of

PLACEMENT_GSP_GROUP.

Received message for incorrect component

:[dec] [dec]
Received unexpected message.

Jid [dec] missing from [chars] table

JID missing from table.

Proc table empty - Unexpected state

Proc table empty.

LR PLANE timer fired. Premature LR

declared. Placement-suboptimal

LR Plane timer fired. Premature declaration

of LR.

[chars]:Failed to malloc: [chars]

Unable to malloc. Recovery occurs with

automatic process restart.

Failed to initialize mutex: [chars]

PlaceD daemon was unable to initialize the

internal state mutex. Recovery occurs with
automatic process restart.

Unable to get my node info:[chars]

An error occured whilst PlaceD tried to

retrieve its node information. Recovery
occurs with automatic process restart.

Node [dec] missing from [chars] table

Node missing from table.

Error querying name for node [dec] from

platform:[chars]

Unable to query name for node from

platform.

Failed to obtain node role: [chars]

PlaceD daemon was unable to obtain the

node role. Recovery occurs with automatic
process restart.

Unable to reg. event_item [chars] with

sysdb:[chars]

Unable to register for event_item with

sysdb.

Error creating node parent timer:[chars]

Unable to create parent for node timer

treee

Error querying partner node from platform: Unable to query partner node from
[chars]
platform.

PI PLANE timer fired. Premature PI

declared. Placement-suboptimal

PI Plane timer fired. Premature declaration

of PI.

Exhausted all instances of placeable

process [chars] possible

Exhausted all instances of placeable

process.

Unable to register with enf for sysmgr proc Unable to register with enf for sysmgr proc
events:[chars]
events.

Failed to create thread: [chars]

PlaceD daemon was unable to create the

thread. Recovery occurs with automatic
process restart.

Failed to detach pthread: [chars]

PlaceD daemon was unable to detach the

thread. Recovery occurs with automatic
process restart.

Unable to bind to sysdb-[pointer]:[chars]

Unable to bind to sysdb.

Unable to add [dec] to startup list:[chars]

Unable to prepare startup list.

Unable to unbind from sysdb-[pointer]:

[chars]

Unable to unbind from sysdb.

Error registering for [chars] with sysmgr:

[chars]

Unable to register with sysmgr.

Error deleting [chars] from [chars] table:

[chars]

Unable to delete object from table.

Multiple objects [chars] found from [chars]

table
Query returned multiple objects.

Table Empty Address: [pointer]

Query returned table empty.

Error finding [chars] from [chars] table:

[chars]

Unable to find object from table.

Unable to initialize [chars] table:[chars]

Unable to initialize table.

Error inserting [chars] into [chars] table:

[chars]

Unable to delete object from table.

Error reading [chars] from [chars] table:

[chars]

Unable to read object from table.

Error creating node leaf timer:[chars]

Unable to create leaf for node timer tree.

Error creating node timer tree:[chars]

Unable to create node related timer tree.

Tuple [chars] missing from [chars] table

Tuple missing from table.

Unknown tuple:[chars]

Unknown tuple.

Received unexpected message:[chars]

Received unexpected message.

Received unexpected request:[dec]

Received unexpected message.

Unknown timer fired type:[dec]

Timer, with unknown timer-id, fired.

Unknown vs notif:[chars] found:[dec]

Unknown vs notif from sysdb.

Unable to reg. item [chars] with sysdb:

[chars]

Unable to register for item with sysdb.

Zero level-started placeable processes

from Proc-table

No level started placeable processes found

in the table.

No singleton processes in the table

Query returned table empty.

Failed to get dLRSC from local lrd: [chars]

PlaceD was unable to get dLRSC from local

lrd.

Error waiting for message - ignoring:

[chars]

An error occured while PlaceD was waiting

for a messages, PlaceD ignored the error
and continued to wait for more messages.

PlaceD was unable to inform SysMgr that it

Failed to signal end of initialization: [chars] had completed its initialization.

Failed init-ing the tlv library : [chars]

PlaceD was unable to initialize the tlv

library for ISSU support

Received unknown EOI req type from [dec]:

type:[dec]
PlaceD received an unknown message.

[chars]: Flow type '[chars]' not configured

Error in IFIB flow handling configuration.

The named flow type was not explicitly
configured and will have default
characteristics applied.

[chars]: Flow type '[chars]' not configured

error in IFIB flow handling configuration.

The named flow type was not explicitly
configured and will have default
characteristics applied.

Syntax error in IFIB flow handling

[chars]: Missing parameter after '[chars]' in configuration. The named flow type may
flow '[chars]'
have default characteristics applied.

Syntax error in IFIB flow handling

[chars]: Missing parameter after '[chars]' in configuration. The named flow type may
flow '[chars]'
have default characteristics applied.

Syntax error in IFIB flow handling

[chars]: Unknown keyword '[chars]' in flow configuration. The named flow type may
'[chars]'
have default characteristics applied.

Syntax error in IFIB flow handling

[chars]: Unknown keyword '[chars]' in flow configuration. The named flow type may
'[chars]'
have default characteristics applied.

Syntax error in IFIB flow handling

[chars]: Unknown parameter '[chars]' after configuration. The named flow type may
'[chars]' in flow '[chars]'
have default characteristics applied.

Syntax error in IFIB flow handling

[chars]: Unknown parameter '[chars]' after configuration. The named flow type may
'[chars]' in flow '[chars]'
have default characteristics applied.

Failed to allocate memory

The system failed to allocate memory. It's

likely that the system is running low in
memory.

[chars]: Missing configuration for IFIB flow

handling

No configuration for IFIB flow handling was

found. Default characteristics will be used
for all packets.

[chars]: Missing configuration for IFIB flow

handling

No configuration for IFIB flow handling was

found. Default characteristics will be used
for all packets.

[chars]: Insufficient memory for IFIB flow

handling configuration

Insufficient memory was available for

storing the IFIB flow handling configuration.
Default characteristics will be used for all
packets.

[chars]: Insufficient memory for IFIB flow

handling configuration

Insufficient memory was available for

storing the IFIB flow handling configuration.
Default characteristics will be used for all
packets.

[chars]: Debug cleanup failed: [chars]

An error was returned when cleaning up

debug. This is not a critical error, and the
process can continue functioning noramlly
despite this failure. Particular undebug will
not be effective though.

[chars]: Debug cleanup failed: [chars]

An error was returned when calling

debug_cleanup() function.

Error msg:[chars]: Error string: [chars]

An error was returned when initializing

debug. The facility to debug the
component may not work.

[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]

An error was returned when initializing

debug. This is not a critical error, and the
process can continue functioning noramlly
despite this failure. Particular debug will
not be effective though.

[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]

An error was returned when calling the

debug_init_event() function.

[chars]: Debug registration failed: [chars]

An error was returned when registering

debug. This is not a critical error, and the
process can continue functioning noramlly
despite this failure. Particular debug will
not be effective though.

[chars]: Debug registration failed: [chars]

An error was returned when calling

debug_register() function.

[chars]: Debug cleanup failed: [chars]

An error was returned when cleaning up

debug.

[chars]: Debug cleanup failed: [chars]

An error was returned when calling

debug_cleanup() function.

[chars]: Debug cleanup failed: [chars]

An error was returned when cleaning up

debug.

[chars]: Debug cleanup failed: [chars]

An error was returned when cleaning up

debug.

[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]

An error was returned when initializing

debug.

[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]

An error was returned when initializing

debug.

[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]

An error was returned when calling the

debug_init_event() function.

[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]

An error was returned when initializing

debug.

[chars]: Debug registration failed: [chars]

An error was returned when registering

debug.

[chars]: Debug registration failed: [chars]

An error was returned when registering

debug.

[chars]: Debug registration failed: [chars]

An error was returned when registering

debug.

[chars]: Debug registration failed: [chars]

An error was returned when calling

debug_register() function.

[chars]: [chars]

An error was returned when initializing

debug. The facility to debug the
component may not work.

[chars]: [chars]

An error was returned when initializing

debug. The facility to debug the
component may not work.

[chars]: EDM backend function [chars]

failed: [chars]

An internal EDM backend function failed.

[chars]: EDM backend function [chars]

failed: [chars]

An internal EDM backend function failed.

[chars]: Bag function [chars] failed: [chars] An internal bag function failed.

[chars]: Bag function [chars] failed: [chars] An internal bag function failed.

[chars]: cgm_init failed: [chars]

An internal cgm_init function failed.

[chars]: cgm_init failed: [chars]

An internal cgm_init function failed.

[chars]: Checkpoint Initialization function

[chars] failed: [chars]

An internal Checkpoint function failed.

[chars]: Checkpoint Initialization function

[chars] failed: [chars]

An internal Checkpoint function failed.

[chars]: Insufficient memory for flow

configuration

There is insufficient memory for the flow

configuration. All flows will be assigned
default characteristics.

[chars]: Insufficient memory for flow

configuration

There is insufficient memory for the flow

configuration. All flows will be assigned
default characteristics.

[chars]: Flow type '[chars]' not configured

error in PIFIB flow handling configuration.

The named flow type was not explicitly
configured and will have default
characteristics applied.

[chars]: Flow type '[chars]' not configured

error in PIFIB flow handling configuration.

The named flow type was not explicitly
configured and will have default
characteristics applied.

Syntax error in PIFIB flow handling

[chars]: Missing parameter after '[chars]' in configuration. The named flow type may
flow '[chars]'
have default characteristics applied.

Syntax error in PIFIB flow handling

[chars]: Missing parameter after '[chars]' in configuration. The named flow type may
flow '[chars]'
have default characteristics applied.

[chars]: Insufficient memory for policer

configuration

There is insufficient memory for the policer

configuration. All flows will be assigned
default characteristics.

[chars]: Insufficient memory for policer

configuration

There is insufficient memory for the policer

configuration. All flows will be assigned
default characteristics.

[chars]: Invalid parameter '[chars]' after

'[chars]' in policer '[dec]' definition

There is an invalid parameter after a

keyword in a policer definition. The policer
may be assigned default characterstics.

[chars]: Invalid parameter '[chars]' after

'[chars]' in policer '[dec]' definition

There is an invalid parameter after a

keyword in a policer definition. The policer
may be assigned default characterstics.

There is a missing required parameter after

a keyword in a policer definition. The
[chars]: Missing parameter after '[chars]' in policer may be assigned default
policer '[dec]' definition
characterstics.

There is a missing required parameter after

a keyword in a policer definition. The
[chars]: Missing parameter after '[chars]' in policer may be assigned default
policer '[dec]' definition
characterstics.

[chars]: Unknown keyword '[chars]' in

policer '[dec]' definition

There is an unknown keyword in a policer

definition. The policer may be assigned
default characterstics.

[chars]: Unknown keyword '[chars]' in

policer '[dec]' definition

There is an unknown keyword in a policer

definition. The policer may be assigned
default characterstics.

An input flow definition references an

[chars]: flow '[chars]' references undefined undefined policer. The flow will be
policer '[dec]'
configured to use policer 0.

An input flow definition references an

[chars]: flow '[chars]' references undefined undefined policer. The flow will be
policer '[dec]'
configured to use policer 0.

Syntax error in PIFIB flow handling

[chars]: Unknown keyword '[chars]' in flow configuration. The named flow type may
'[chars]'
have default characteristics applied.

Syntax error in PIFIB flow handling

[chars]: Unknown keyword '[chars]' in flow configuration. The named flow type may
'[chars]'
have default characteristics applied.

[chars]: Unknown parameter '[chars]' in

flow '[chars]'

Syntax error in PIFIB flow handling

configuration. The named flow type may
have default characteristics applied.

[chars]: Unknown parameter '[chars]' in

flow '[chars]'

Syntax error in PIFIB flow handling

configuration. The named flow type may
have default characteristics applied.

An internal cpp_lpts_ea_register function

[chars]: cpp_lpts_ea_register failed: [chars] failed.

[[chars]]: Gentry get failed

The system failed to get gentry.

[chars]: Failed to get node type for nodeid

[hex]

The system failed to get node type.

Failed to find uidb index for interface

handle [hex]

Failed to find uidb index for an given

interface handle. It is likely to be caused by
a programming bug or a programming
problem happened in the past.

[chars] Invalid shadow entry state [dec]

Invalid shadow entry state.

Failed to allocate memory

The system failed to allocate memory. It's

likely that the system is running low in
memory.

The queue for notifications from [chars] is

full

Too many notifications have been sent to

the component. The queue to hold the
notification has overflowed.

[chars] : [chars]

proc nodeid error.

Failed to program BFD Discriminator Table : The system failed to program BFD
[chars]
discriminator table on the linecard.

The system failed to program static punt

Failed to program Static Punt Table : [chars] table on the linecard.

[chars]: >2 Rack cluster unsupported!

more then 2 Rack cluster not supported.

[chars]: [chars] errno [hex]

sysdb return error.

RZ: tcam is not ready

TCAM is not ready.

[chars]:FATAL ERROR Error([hex]): [chars]

TCAM ods delete error.

[chars]: prm_tcam_ods_destroy FATAL

ERROR on reg type [dec] with pifib rc [hex]
and tcam rc [hex]
TCAM ods destroy error.

[chars]:FATAL ERROR Error([hex]): [chars]

TCAM ods get free error.

[chars]:FATAL ERROR Error([hex]): [chars]

TCAM ods insert error.

[chars]: prm_tcam_ods_invalidate
encountered FATAL ERROR on reg type
[dec] with tcam errno [hex]

TCAM ods invalidate encountered FATAL

ERROR.

[chars]: prm_tcam_ods_rd_ids FATAL ERROR

on reg type 0 with pifib rc [hex] and tcam
rc [hex]
TCAM ods destroy error.

[chars]: prm_tcam_ods_write failed on reg

type [dec] with pifib error [hex] and tcam
error [hex]

TCAM ods write error.

[chars]: [chars] encountered FATAL ERROR

with tcam errno [hex]
TCAM ods write encountered error.

[chars]: [chars] encountered FATAL ERROR

with tcam errno [hex] prot_id [dec]
TCAM ods write encountered error.

[chars]: prm_tcam_ods_write_with_fmt
encountered FATAL ERROR on reg type
[dec] with tcam errno [hex] base_idx [dec],
num_tm_entries [dec], op [dec], dev_id
[dec], vmr_id [dec], lt_id [dec], index [dec],
nr_ent [dec], key_size [dec], result_size
[dec], app_id [dec]
TCAM ods write with fmt error.

[chars]: could not create event connection: An internal error was detected when trying
[chars]
to create event connection.

[chars]: could not create event connection: An internal error was detected when trying
[chars]
to create event connection.

[chars]: could not open event connection:

[chars]

An internal error was detected when trying

to open event connection.

[chars]: could not open event connection:

[chars]

An internal error was detected when trying

to open event connection.

Failed to establish evm connection

[chars]:;error code:[chars]

An internal error was detected when trying

to set up event connection. When this issue
happens, it will trigger an automatic restart
of the pifibm_server_lc process.

An internal error was detected when trying

to allocate a timer object.When this issue
Could not set up a timer object;error code: happens, it will trigger an automatic restart
[chars]
of pifibm_server_lc process..

Could not create a timer tree leaf

objct.Error code: [chars]

An internal error was detected when trying

to create a timer tree leaf object.When this
issue happens, it will trigger an automatic
restart of pifibm_server_lc process.

[chars]: fm add feat to group failed for ISIS An internal fm add feature to group
[chars]
function failed.

[chars]: fm add feat to group failed for ISIS An internal fm add feature to group
[chars]
function failed.

[chars]: fm add ifh to group failed for ISIS

[chars]

An internal fm add ifh to group function

failed.

[chars]: fm add ifh to group failed for ISIS

[chars]

An internal fm add ifh to group function

failed.

[chars]: fm create group failed: [chars]

An internal fm create group function failed.

[chars]: fm create group failed: [chars]

An internal fm create group function failed.

[chars]: fm feature registration failed:

[chars]

An internal fm feature registration function

failed.

[chars]: fm feature registration failed:

[chars]

An internal fm feature registration function

failed.

[chars]: fm_register failed: [chars]

An internal fm_register function failed.

[chars]: fm_register failed: [chars]

An internal fm_register function failed.

[chars]: Failed to get node type for nodeid

[hex]\n

Getting the node type failed.

[chars]: [chars]

An internal
cpp_ha_platform_wait_for_platform_state
function still waiting for HA redy state.

[chars]: [chars]

An internal
cpp_ha_platform_wait_for_platform_state
function still waiting for HA ready state.

[chars]: hfa_register failed: [chars]

An internal hfa_register function failed.

[chars]: hfa_register failed: [chars]

An internal hfa_register function failed for

pifib.

Failed to find uidb index for interface

handle [hex]

It is likely to be caused by a programming

bug or a programming problem happened
in the past. The message frequency
depends on the protocol for which
programming takes place.

Failed to perform IPV6 compress, tcam

error code = [hex], prefix_len = [hex]

IPV6 compression has failed due to some

error.So,lpts entry for that IPV6 address will
not be programmed.Automatic process
restart of pifibm_server_lc will happen.It
will impact traffic only for that specific IPV6
address.

IPV6 compression has failed due to some

error. So,lpts entry for that IPV6 address
will not be programmed. Automatic process
Failed to perform IPV6 compress, tcam mgr restart will happen. It will impact traffic
error code = [hex], prefix_len = [hex]
only for that specific IPV6 address.

[chars]: ltrace_init2 failed: [chars]

An internal ltrace_init2 function failed.

[chars]: ltrace_init2 failed: [chars]

An internal ltrace_init2 function failed.

Failed to allocate memory

It's likely that the system is running low in

memory.When this issue happens, it will
trigger an automatic restart of
pifibm_server_lc process.

[chars]: Event Mgr function [chars] failed:

[chars]

An internal Event Manager function failed.

[chars]: Event Mgr function [chars] failed:

[chars]

An internal Event Manager function failed.

No configuration for PIFIB flow handling

[chars]: Missing configuration for PIFIB flow was found. Default characteristics will be
handling
used for all packets.

No configuration for PIFIB flow handling

[chars]: Missing configuration for PIFIB flow was found. Default characteristics will be
handling
used for all packets.

The queue for notifications from [chars] is

full

Too many notifications have been sent to

the component. The queue to hold the
notification has overflowed. System will
recover by itself. When this issue happens,
it will trigger an automatic restart of
pifibm_server_lc process.

[chars]: platform pre-IFIB shared memory

init failed: ([chars]) [chars]

An internal shared memory function failed.

[chars]: platform pre-IFIB shared memory

init failed: ([chars]) [chars]

An internal shared memory function failed.

[chars]: Cleanup for EDM failed: [chars]

Cleanup for EDM failed.

[chars]: Cleanup for EDM failed: [chars]

Cleanup for EDM failed.

[chars]: Initialization for show EDM failed:

[chars]

Initialization for show EDM failed.

[chars]: Initialization for show EDM failed:

[chars]

Initialization for show EDM failed.

[chars]: Sysdb function [chars] failed:

[chars]

An internal sysdb function failed.

[chars]: Sysdb function [chars] failed:

[chars]

An internal sysdb function failed.

[chars]:
vmr_builder_program_tcam_fmt_from_hfa_ An tcam format to hfa mapping function
map failed: [chars]
failed.

[chars]:
vmr_builder_program_tcam_fmt_from_hfa_ An tcam format to hfa mapping function
map failed: [chars]
failed.

: [chars]: Out of range uidb index for

ifhandle [hex]: [int]

An internal API to retrieve hardware details

failed for an interface. LPTS may not be
functioning properly on the interface.

Failed to connect to platform component:

[chars];error string :[chars]

An internal error was detected when trying

to connect to the respective
component.When this issue happens, it will
trigger an automatic restart of
pifibm_server_lc.

[chars] [chars]

acl string is non-effective. Acl string

provided is not mapped to any access-list
mentioned for ipv4, so its not effective.

[chars]

security ttl feature is not effective. As OPSF

protocol entries being optimized in TCAM,
enabling this feature on selective OSPF
neighbors is not permitted

Failed to initialize the flow policer [dec]:

[chars]

It failed to program a flow policer during

initialization.When this issue happens, it
will trigger an automatic restart.

Failed to initialize with Metro IPC Server:

[chars]

An internal error was detected when trying

to initialize with Metro IPC server.

Failed to acknowledge a MIPC notification:

[chars]

It is an internal error which the system

failed to acknowledge a MIPC Server
notification.When this issue happens, it will
trigger an automatic restart of
pifibm_server_lc process.

Failed to initialize stats table: [chars]

An internal error was detected when trying

to initialize a statistic counter table.

An internal error was detected when trying

to handle a notification from the respective
component.When this issue happens, it will
trigger an automatic restart of
Failed to handle [chars] notification: [chars] pifibm_server_lc process

Failed to reprogram the flow policer [dec]:

[chars]

An internal error was detected when trying

to program the flow policer.When this issue
happens, it will trigger an automatic
restart.

Failed to program the flow policer [dec]:

[chars]

It failed to reprogram a flow policer when it

had received a request to reprogram all
flow policers to HW.When this issue
happens, it will trigger an automatic
restart.

Sysdb datalist function failed to create an

object handle: [chars]

An internal sysdb function failed. When this

issue happens, it will trigger an automatic
restart of pifibm_server_lc process.

Failed to initialize TCAM regions: [chars]

An internal error was detected when trying

to initialize TCAM regions.

Failed to allocate HW counters.

It failed to allocate HW counters. It may be

because of running out of HW counters or
encountering internal error.

Found the Pre-IFIB region with

unrecognized name: [chars]

A Pre-IFIB region with unrecognized name

is found in the TCAM. It is likely caused by
a programming bug or a programming
problem happened in the past.

Does not have enough space for the PreIFIB entry in TCAM region [chars]

TCAM space is not enough for all Pre-IFIB

entries in the particular TCAM region. All
control packets which do not have
matching Pre-IFIB entries in TCAM will use
SW path to forward to destinations.

Failed to have IPv6 prefix compressed

IPv6 prefix compression failed because the

line card has run out of internal resources
for compressing a preifx. It shouldn't have
any major impact on the system service.
The in-bound (destined to the system)
packets can still reach destinations through
SW path.

Failed to allocate HW counters.

It failed to allocate HW counters. It may be

because of running out of HW counters or
encountering internal error.

Found the Pre-IFIB region with

unrecognized name: [chars]

A Pre-IFIB region with unrecognized name

is found in the TCAM.

Does not have enough space for the PreIFIB entry in TCAM region [chars]

TCAM space is not enough for all Pre-IFIB

entries in the particular TCAM region. All
control packets which do not have
matching Pre-IFIB entries in TCAM will use
SW path to forward to destinations.

Failed to have IPv6 prefix compressed

IPv6 prefix compression failed because the

line card has run out of internal resources
for compressing a preifx. It shouldn't have
any major impact on the system service.
The in-bound (destined to the system)
packets can still reach destinations through
SW path.

[chars]: TOS config is not supported in E3

TOS Config is not supported in E3.

[chars]: Debug cleanup failed: [chars]

An error was returned when cleaning up

debug.

[chars]: Debug cleanup failed: [chars]

An error was returned when cleaning up

debug.

[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]

An error was returned when initializing

debug.

[chars]: Debug initialization for the lpts/

[chars] event failed: [chars]

An error was returned when initializing

debug.

[chars]: Debug registration failed: [chars]

An error was returned when registering

debug.

[chars]: Debug registration failed: [chars]

An error was returned when registering

debug.

Failed to connect to [chars]: [chars]

An internal error was detected when trying

to connect to the respective component.

[chars]: [chars]

An error was returned when initializing

debug. The facility to debug the
component may not work.

[chars]: [chars]

An error was returned when initializing

debug. The facility to debug the
component may not work.

[chars]: [chars]

An error was returned when initializing

debug. The facility to debug the
component may not work.

[chars]: [chars]

An internal error was detected when trying

to set up event connection.

Could not set up a timer object: [chars]

An internal error was detected when trying

to allocate a timer object.

Could not create a timer tree leaf objct:

[chars]

An internal error was detected when trying

to create a timer tree leaf object.

Failed to initialize the flow policer [dec]:

[chars]

It failed to program a flow policer during

initialization.

Failed to initialize the ltrace buffer

An internal error was detected when trying

to initalize a ltrace buffer.

Failed to initialize with Metro IPC Server:

[chars]

An internal error was detected when trying

to initialize with Metro IPC server.

Failed to acknowledge a MIPC notification:

[chars]

It is an internal error which the system

failed to acknowledge a MIPC Server
notification.

[chars] was asked to do neither Overwrite

nor Update

function called to do neither Overwrite nor

Update.

An internal error was detected when trying

to handle a notification from the respective
Failed to handle [chars] notification: [chars] component.

Failed to initialize stats table: [chars]

An internal error was detected when trying

to initialize a statistic counter table.

Failed to reprogram the flow policer [dec]:

[chars]

An internal error was detected when trying

to program the flow policer.

Failed to program the flow policer [dec]:

[chars]

It failed to reprogram a flow policer when it

had received a request to reprogram all
flow policers to HW.

Warning: shadow write limit exceeded

shadow write limit exceeded.

Sysdb datalist function failed to create an

object handle: [chars]

An internal sysdb function failed.

Failed to initialize TCAM regions: [chars]

An internal error was detected when trying

to initialize TCAM regions.

Usage: [chars] : [chars]

usage error.

Failed to initialize the ltrace buffer

An internal error was detected when trying

to initalize a ltrace buffer.

PM HA Client DLL failed to initialize

debugging services, reason [chars]

The Platform Manager HA DLL encountered

an internal software error. The debugging
services could not be initialized. This
problem should rarely happen. Restarting
the Platform Manager HA process might
recover the problem

[chars]

The Platform Manager HA Driver DLL was

unable to add any new fault record due to
lack of memory. This condition will cause
the DLL to exit.

[chars]

The Platform Manager HA Driver DLL was

unable to add one new fault record due to
lack of memory, but it is still running.

[chars], reason [chars]

The Platform Manager HA Driver DLL

encountered an internal software error. The
debugging services could not be initialized.
This problem should rarely happen.
Restarting the Platform Manager HA
process might recover the problem

[chars], reason: [chars]

The Platform Manager HA Driver DLL was

unable to initialize due to internal software
resource issues.

Running on unknown nodetype, assuming

it is a linecard

Procfind was did not recognise the node

type on which it was running, and therefore
assumed it was a linecard.

Error waiting for message - ignoring:

[chars]

An error occured whilst Procfind was

waiting for messages, Procfind ignored the
error and continued to wait for more
messages.

Failed to retrieve info for process [dec]:

[chars]

Procfind was unable to read the information

for the specified process, and will therefore
return incomplete results.

Failed to open process [dec]: [chars]

Procfind was unable to open the specified

process, and will therefore return
incomplete results.

Failed to signal end of initialization to

SysMgr: [chars]

Procfind was unable to inform System

Manager that it has finished initializing and
is ready to service request. Procfind
ignored the error and continued normally.

Procfind was unable to create an event

manager for receiving messages, and
Failed to create an event manager: [chars] therefore failed to initialize.

Failed to allocate memory for [chars]

Insufficient resources were available to

allocate memory for the specified item.
Procfind may not be able to continue
running.

Failed to get node ID of current node:

[chars]

Procfind was unable to determine the ID of

the node on which it was running, and
therefore failed to initialize.

Procfind was unable to bind to the SysDB

Failed to bind to SysDB at '[chars]': [chars] server, and therefore failed to initialize.

Failed to initialize SysDB EDM functions

handle: [chars]

Procfind was unable to initialize its SysDB

EDM functions handle, and therefore failed
to initialize.

Procfind was unable to register with the

Failed to register with SysDB as an EDM at SysDB server for as an EDM, and therefore
'[chars]': [chars]
failed to initialize.

Problem processing incoming multicast

message: [chars]

An incoming multicast message was

received, supposedly containing data that
should be persisted to non-volatile storage
on the receiving location, but this
persisting operation could not complete
because of a problem.

Operation [chars] failed : [chars]

The specified operation failed

Operation [chars] failed : [chars], rc [hex],

[chars]

Shared memory access operations like

init,open or bind might have failed.

Condition [chars] : [chars]

The specified condition has occurred

Operation [chars] failed : [chars]

The specified operation failed

Operation [chars] , rc [hex], [chars]

Shared memory access operations like

init,open or bind might have failed.

Operation [chars] failed : [chars]

The specified operation failed

Shared memory access operations like

Operation [chars] [chars] ,rc [hex], [chars] init,open or bind might have failed.

Operation [chars] ,[chars] \n

Sysmgr proc ready operation failed.

Operation [chars] ([chars])

event manager operations failed for some

reason.

[chars]:[dec]:[chars]: Invalid attempt to

build chain (type [dec])

qnetbase_builder_func() called with bad

chain type.

[chars]:[dec]:[chars]: Base Control function

erroneously called!
qnetbase_control_func() wrongly called.

[chars]:[dec]:[chars]: Invalid attempt to

build chain (type [dec])

qnetcaps_builder_func() called with wrong

chain type.

[chars]:[dec]:[chars]: Caps Control function qnetcaps_control_func() has been called,

erroneously called!
which should never happen.

[chars]: Cannot duplicate BMA packet

(rc=[dec] dropping Qnet packet.\n

pak_netio_duplicate() failed.

[chars]:[dec]:[chars]: Qnet encapsulation

node erroneously called!

qnetcaps_encaps() has been called, which

should never happen.

Lost connection to Qnet process; dropping

packets.

netio_dll_packet_input_NEW() to Qnet failed

and Qnet connection is closed.

[chars]:[dec]:[chars]: packet_input returned netio_dll_packet_input_NEW() to Qnet

non-zero result code ([dec])
failed.

[chars]:[dec] failed to get destination slot.

error [dec]

pak_netio_uint32_get() failed.

[chars]

An EMERGENCY level message was emitted

by QNET.

[chars]

An ALERT level message was emitted by

QNET.

[chars]

A CRITICAL level message was emitted by

QNET.

prp3fabric packet stream creation failed,

rc: [dec]

During device initialization, creating packet

stream for QNET application is failed.
Results, unknown callback function for
incoming QNET packets.

QNET encountered an error when waiting

for events with error [dec]([chars])

QNET process had encountered a problem

when waiting inside its event waiting loop.
Process will exit and respawn.

QNET problem in creating debug event

handling thread with error [dec]([chars])

QNET process tried to create event debug

pthread for the process but encountered an
error The process will exit and respawn
again

QNET had problem attach a disconnect

handler fd=[dec] to the process during
[chars] with error [dec]([chars])

QNET process tried to attach a disconnect

handler for the process but encountered
error. The QNET process may not exit or
restart properly.

[chars]

An ERROR level message was emitted by

QNET.

QNET process tried to create a thread for

QNET problem in creating EVM thread with handling events but encountered error. The
error [dec]([chars])
process will exit and retry again

QNET process had encountered a problem

QNET had problem in its EVM thread during in its EVM thread while wating for event.
[chars] with error [dec]([chars])
The thread will exit and retry again

packet client unscramble header failed:

[chars]

During qnet packet transmission, Packet

header validation failed.

QNET problem in setting rlimit with error

[dec]([chars]), exiting

QNET process tried to set the rlimit for the

process but encountered error The process
will exit and retry again

QNET problem in creating debug event

manager with error [dec]([chars])

QNET process tried to create debug evm

but encountered error specified The
process may not be able to handle debug
events

Process [dec] requested voluntary [chars]

dump of itself

A non-invasive voluntary coredump

requested by the process. Process might be
experiancing a condition which needs
investigation. This core file will help
analysing the issue.

Problem with voluntary core dump

requested by [dec] when [chars]: [chars]

A non-invasive voluntary coredump was

requested by the process, but a problem
occured that prevented the coredump from
being created.

[chars]

A WARNING level message was emitted by

QNET.

[chars]

A NOTICE level message was emitted by

QNET.

A non-invasive voluntary coredump

requested by the process completed
successfully. Process might be experiancing
Voluntary core dump requested by process a condition which needs investigation. This
[dec] completed
core file will help analysing the issue.
[chars]

An INFO level message was emitted by

QNET.

[chars]

A DEBUG level message was emitted by

QNET.

q_produce for QNET tx failed, rc = [dec]\n

could not send pkt to fabric driver.

A error occured while processing a QSM

configuration file. This could be due to a
problem with the installed media or file
system damage. QSM will continue startupup, but some system functionality may be
Unable to add directory link [chars]: [chars] impared.

A error occured while processing a QSM

configuration file. This could be due to a
problem with the installed media or file
system damage. QSM will continue startupup, but some system functionality may be
Unable to add link [chars]->[chars]: [chars] impared.

An database dump message from another

node could not be processed ([chars]):
[chars]

The indicated error occured while

processing a dbdump from another node.

An unexpected message from another

An invalid message type was received from
node could not be processed ([chars]): %zd another node.

An update message from another node

could not be processed ([chars]): [chars]

The indicated error occured while

processing an update from another node.

The QSM error number/messages table

could not be registered with the cerrno
Unable to register the QSM error messages: system. Error translations will not be
[chars]
available.

Unable to open QSM checkpoint file

[chars]: [chars]

The checkpoint file could not be opened. A

restart of QSM is likely to have incomplete
data.

Unable to re-load QSM link [chars]>[chars]: [chars]

A link found in the checkpoint file could not

be created in the QSM database.

Unable to re-load QSM notification for

[chars]: [chars]

A link found in the checkpoint file could not

be created in the QSM database.

Unable to rename checkpoint file [chars]>[chars]: [chars]

The checkpoint temporary file could not be

renamed. A restart of QSM is likely to have
incomplete data.

Unable to seek to the end of the QSM

checkpoint file [chars]: [chars]

The checkpoint file could not be appended

to. A restart of QSM is likely to have
incomplete data.

Unable to truncate QSM checkpoint file

[chars]: [chars]

The QSM checkpoint file could not be

truncated -- prior to being overwritten with
updated data. A restart of QSM is likely to
have incomplete data.

Unable to write to QSM checkpoint file

[chars]: [chars]

A link could not be written to the QSM

checkpoint file. A restart of QSM is likely to
have incomplete data.

Insufficient buffer size to format QSM

checkpoint record. Have %zd, need %zd

A QSM checkpoint record could not be

placed in the checkpoint file due to
insufficient buffer space.

Checkpoint lock failure: [chars]

The lock that protects the QSM checkpoint

database could not be taken. The
checkpoint database could become
corrupted -- causing a restart of QSM to
have incomplete data.

A QSM checkpoint record could not be

Unable to allocate space for the checkpoint placed in the checkpoint file due to
buffer
insufficient heap space.

Unable to initialize [chars]: [chars]

The QSM process wasn't able to startup up

due the indicated failure during
initialization. A restart of the process will be
attempted. If the process can not be
sucessfully started after several attempts,
the board will probably be unusable.

Platform_get_type returned an unknown

node type: [dec]

The QSM process wasn't able to startup up

due the indicated failure during
initialization. A restart of the process will be
attempted. If the process can not be
sucessfully started after several attempts,
the board will probably be unusable.

Invalid line in symlinks file: [chars]

A startup configuration file for QSM

contained an invalid line. This could be due
to a problem with the installed media or file
system damage. QSM will continue startupup, but some system functionality may be
impared.

A Link database entry had an unexpected

mode: 0o%o

The mode data (MOG) for a link entry had

an unexpected value. This could indicate a
memory corruption problem.

Unable to create link database entry

'[chars]' ([chars]): [chars]

An entry could not be placed in the links

database. The full error message should
indicate where the failure occured and why.

A link could not be deleted from the links

database. This could indicate either a code
Unable to delete link database entry: [dec] problem or a memory corruption problem.

Unable to delete link database entry:

[chars]

An entry could not be deleted from the

links database. The full error message
should indicate where the failure occured
and why.

The QSM links database was requested to

free a inode with a zero inumber

A internal error occured. A small amount of

memory has been lost. QSM can be
restarted to recover the lost memory.

Invalid cur index in [chars]. CUR: [dec],

path: [chars], inum: [dec]

A internal error has occured. The QSM

directory scrub routine has been aborted.
This should not cause any instability unless
this message is repeated many times.

An expected database lock was not held.

A lock failure occured in the links database This could indicate a memory corruption
([chars]():[chars]): [chars]
problem.
link delete returned wrong link entry. path
[chars], result: [hex], delete_result: [hex]

This is a debug message that is not

compiled into a customer version of the
code.

Unable to locate symlinks file at etcpath

[chars]: [chars]

An expected startup configuration file for

QSM could not be found. This could be due
to an install problem or due to data being
deleted from the installation file system.
QSM will continue startup-up, but some
system functionality may be impared.

A lock failure occured ([chars]): [chars]

The indicated error occurred while

attempting to hold or release a lock.

[chars]: [dec]. A lock failure occured

([chars]): [chars]

The indicated error occurred while

attempting to hold or release a lock.

Unable to obtain %zd bytes of memory

while: [chars]

QSM could not obtain system meory while

performing the indicated operation.

(transition message) Detected NON admin

plane add for [chars]. class: [hex], svctype:
[hex], msgflags: [hex]
Development debug message

A lock failure occured in the notification

database ([chars]): [chars]

An expected database lock was not held.

This could indicate a memory corruption
problem.

A notification record could not be written to

the QSM notification checkpoint file. A
Notification checkpoint record could not be restart of QSM is likely to have incomplete
written: [chars]
data.

Unable to open symlinks file [chars]:

[chars]

An expected startup configuration file for

QSM could not be opened. This could be
due to a problem with the installed media
or file system damage. QSM will continue
startup-up, but some system functionality
may be impared.

Unable to send a database message

([chars]): [chars]

A database update or dump mesage could

not be sent to the other nodes.

(transition message) Detected admin plane This is a debug message that is not
add for [chars]. class: [hex], svctype: [hex], compiled into a customer version of the
msgflags: [hex]
code.
An error was received while processing a
request from a local process. There could
be a version mis-match or corruption in the
Bad LWM Message received from pid [dec]. client process. The error message should
([chars]): [chars]
provide some clue to the problem.
An error was received while processing a
request from a local process. There could
A QSM message was received, but it had
be a version mis-match or corruption in the
the wrong version number. Received: [hex], client process. The error message should
Expected: [hex].
provide some clue to the problem.
Could not create key. rc: [dec],
qsm_lock_key: [dec]

This is a debug message that is not

compiled into a customer version of the
code.

Could not alloc space for thread specific

lock data: [chars]

This is a debug message that is not

compiled into a customer version of the
code.

This is a debug message that is not

Could not set thread specific for lock data: compiled into a customer version of the
[chars]
code.
A link was not threaded correctly in the
links database ([chars]). thread: [dec].
inum: [dec]

This is a debug message that is not

compiled into a customer version of the
code.

A link was not threaded correctly in the

links database ([chars]). thread: [dec].
path: [chars]

This is a debug message that is not

compiled into a customer version of the
code.

An empty directory was to be deleted but

inode [dec] could not be found: [chars]

An empty directory was to be automatically

purged from the QSM database. When the
directory was searched for, it could not be
found.

This is a debug message that is not

Unexpected lock held at [chars]: [dec]. Last compiled into a customer version of the
taken at [chars]: [dec]
code.
A lock list did not have an expected lock at
[chars]: [dec]
The lock list was corrupted.
A lock list had an incorrect count at [chars]:
[dec]. ([dec] vs [dec])
The lock list was corrupted.
A lock ordering failure occured ([chars]) at
[chars]:[dec]. ([dec] vs [dec]).
A lock was taken in an invalid sequence.
A lock upgrade (read to write) attempt was
made at [chars]:[dec]. The lock was first
taken at [chars]:[dec]
An invalid upgrade was made of a lock.

A node was only partially deleted. thread

[dec], node: [chars]

Internal memory corruption occured in the

QSM nodes database.

A node could not be found in the QSM

nodes database: [chars]

An attempt to use a QSM link was made -but the remote node that exported the link
to the local node was not in the local nodes
database. This could be a harmless timing
condition.

A QSM message was received from a nonlocal process

A process on another node contacted the

local QSM server. The local server refused
the request.

notification register of [chars] failed:

[chars]

A application requested database

notification could not be placed in the QSM
notification database. An error will be
returned to the client process.

A application requested database unnotification could not be removed from the

QSM notification database. An error will be
notification register of [dec] failed: [chars] returned to the client process.

Bad [chars] of [pointer] in queue [pointer]

The router is running short on memory.

[chars] didn't find [pointer] in queue

[pointer]

An internal software error occurred.

Bad [chars] [pointer] count [dec]

An internal software error occurred.

IDT for replica [chars] (all handles) FAILED

IDT for the specified replica has totally

failed and the process will do a voluntary
dump to recover.

couldnt alloc for [chars], len=[dec],

errno=[dec]

This is a generic error msg for memory

allocation failure. The RDS library tried to
allocate a memory and it wasn't succesful.
Can happen when system is running low in
memory

rds hit an internal assert. An unexpected

[chars].[dec]: hit assert condition. 'val1=0x error condition has been seen due to which
%zx' expected to be [chars] 'val2=0x%zx' RDS hit assert.

ens_[chars] returned len=[dec] for

DH_ENTRY: [hex], expected>=[dec]

RDS library uses ENS/GSP services to

read/write data. While using ens_read API
to read, it returned failure. ens_read
returned bad len. Underlying GSP/ENS
might have some problem

UNEXPECTED rdr_dh_seqnum=[dec] >

rhdr.seq_num=[dec] for DH=[hex],
dlen=[dec], rdr_data=[pointer]

RDS library uses ENS/GSP services to

read/write data. While using ens_read API
to read, it returned failure. The Ens read
has returned a sequence number which
was not expected.

An internal Lock/Unlock operation has

failed in the RDS library. While trying to
acquire/free a lock in RDS Library , an error
RDS library lock-[chars] failed, errno=[dec] condition was returned.

[chars]: handle=[hex] memory

ptr=0x[pointer]

RDS Library hit an internal error. The

internal error may be due to invalid
memory access or corrupt memory.

RDS library uses ENS/GSP services to

read/write data. While using ens API , it
returned failure. RDS write has not been
able to write successfully and has timed
rds_write DHDL=[hex]([chars]), req=[dec], out.This may be due to message size or
resp=[dec], #wtrs=[dec]: [chars],
underlying problems in transport.RDS will
errno=[dec], retries=[dec]
retry to write again.

TID=%zd: Unexpected error=[dec] from

pthread_cond_timedwait cmd=[dec]

In RDS library we tried to wait using the

pthread_cond_timedwait but the
pthread_cond_timedwait failed.

Lookup of identifier=[hex] index=[hex] in

RING=[pointer] failed

When RDS library tried to search for an

identifier in the atomic tag ring, it returned
failure.

TID=%zd: [dec]: Wrong replica type

passed, expected=[dec]..

replica ID used to invoke the RDS API is

wrong.

TID=%zd: [dec]: Duplicate Tick Notif

(Dropping it) rp=[pointer] tick=[hex]
curr=[dec] hi=[dec] currturn=[hex]
next=[hex] TickCurr=[dec] TickHi=[dec]
state=[hex]

When the single writer mode is set, RDS

library allowes to create a ticket. Got a
ticket notification, for an already active
ticket.

[dec]: ens_bulk_register failed, rc=[hex],

errno=[dec]

RDS library uses ENS/GSP services to

read/write data. While using ens API , it
returned failure. ens_bulk_register API
failed.

RDS library uses ENS/GSP services to

read/write data. While using ens API , it
ens_producer_release for DH=[hex] failed, returned failure. ens_producer_release
errno=[dec]
failed.

[chars]: ens_publish for DH=[hex] failed,

errno=[dec]

RDS library uses ENS/GSP services to

read/write data. While using ens API , it
returned failure. ens_publish failed.

[chars]: ens_register_class for

replica_name=[chars] ch=[hex] failed,
rc=[hex], errno=[dec]

RDS library uses ENS/GSP services to

read/write data. While using ens API to bulk
register, it returned failure.
ens_bulk_register failed.

[chars][dec]

This is a generic error msg.

[dec]: No entry for Datahandle=[hex],

rp=[pointer] vec=[pointer] errno=[dec]\n

Could find datahandle entry in the vector

for replica The datahandle might have not
been added or may have been deleted.

[dec]: [chars] for CH=[hex], errno=[dec],

rds_type=[dec]

The Rds library couldnt get the replica

entry when it queried for it. The entry
might not have been updated.

group_create for [chars]/[chars] failed,

errno=[dec]

When RDS tried to create rds group, it

failed.

[chars]: group_send_rinfo failed GID=[hex],

errno=[dec], rc=[dec], #resp=[dec],
When RDS library invoked GSP api
pattern=[chars]\n
group_send_rinfo , it failed.

When RDS library invoked GSP api

group_send_memberset , it failed. The
errno returned can help in understanding
GSM for [chars] Failed for Handle=[hex], to the problem. The transport GSP layer
(g:[hex]/n:[hex]/p:[dec]), errno=[dec]
returned an failure to RDS.

[dec]: invalid args passed

A function was invoked with invalid

arguments This is a generic error message
and happens when the calling function
invokes the caller function with invalid
arguments

[dec]: invalid rhdr=[pointer] passed

a function was invoked with invalid rhdr

msg

[chars].[dec]: [chars] rp=[pointer]

nptr=[pointer] from sender=g:[dec]/n:
[dec]/p:[dec]

Couldnt find pending request entry in the

pending list. The response which came
couldn't find the corresponding pending
request in the list.

[chars]: nrs_create_class for [chars] failed, RDS library uses NRS API to create nrs
errno=[dec]
classes . nrs_create_class API failed.

[chars], Datahandle=[hex], errno=[dec]

An internal NRS function failed when

invoked from RDS library. The NRS library
returned a failure when we queried on a
handle.

[chars]: nrs_register_bulk for CH=[hex]

failed, rc=[dec] errno=[dec]

RDS library uses NRS API to bulk register

class. nrs_register_bulk API in nrs library
failed.

[chars]: nrs_search for [chars] failed,

rc=[dec] errno=[dec]

RDS library uses NRS API to search nrs

class nrs_search API in NRS library failed.

[chars]: couldnt create pending msg for

CH=[hex], DH=[hex], errno=[dec]

couldnt create pending msg for the

incoming write/publish.

TID=%zd Couldnt cmd=[dec] for

GID=[hex] CHDL=[hex]([hex])
#to_resp=[dec] req=[dec] got=[dec]
state=[hex], expstate=[hex] preq_id=[dec]
rds_type=[dec]
Ticket request timed out.

RDS library uses ENS/GSP services to

read/write data. While using ens_read API
[chars] DH_ENTRY=[hex] for exp_len=[dec] to read, it returned failure. Underlying
got=[dec] rc=[dec] errno=[dec]
GSP/ENS might have some problem

[chars]:[dec] nrs_search for replica_name

[chars] returned NULL after 50 retries

nrs_search for the specified replica did not

yield any data handles.

TID=%zd: gs_sync_create failed for tag

[hex], err [dec]

When the single writer mode is set, RDS

library allowes to create a ticket. When we
tried to create ticket, we failed.

TID=%zd: Ticket Release failed

rp=[pointer] tick=[hex] curr=[dec]
hi=[dec] currturn=[hex] next=[hex]
waitcnt=[dec] rc=[dec] errno=[dec]

When the single writer mode is set, RDS

library allowes to create a ticket. Ticket
request timed out.

TID=%zd: Ticket Request failed for ticket

[hex], rp [pointer], err [dec]

When the single writer mode is set, RDS

library allowes to create a ticket. When
Ticket request was queried, it failed.

TID=%zd: Tick Req Timed out rp=[pointer]

tick=[hex] curr=[dec] hi=[dec]
currturn=[hex] next=[hex] waitcnt=[dec]
rc=[dec] errno=[dec], RETRYING...

When the single writer mode is set, RDS

library allowes to create a ticket. RDS
library got a timed out when it requested
for a ticket.

TID=%zd: Tick Req unknown failure,

rp=[pointer] tick=[hex] curr=[dec]
hi=[dec] currturn=[hex] next=[hex]
waitcnt=[dec] rc=[dec] errno=[dec]

When the single writer mode is set, RDS

library allowes to create a ticket. Ticket
request failed with unknown error.

RDS library uses ENS/GSP services to

read/write data. While using ens API , it
returned failure. ens_bulk_register API
[dec]: Wrong plane [dec] for [chars] failed.. failed.
Bad Replica detected: Condition-[chars]
Path-[chars] Error-[chars].

The current instance of RDSFS encountered

an error so that it is no longer a replica.

PID:TID=[dec]:[dec] [chars] [chars] Error[chars]

RDSFS failure.

RDSFS encountered an internal error within

There was an internal error with the RDSFS it's EDM, which is a non vital component for
EDM: [chars], [hex] ([chars]).
normal operation.

[chars] [chars] Error-[chars]

RDSFS encounterd internal error. Error

could be either transient or persistent error.

Failed to initialize [chars] because [chars].

RDSFS failed to initialize a module.

Unexpected init error: [chars]: [chars]:

[hex]

An unexpected init error condition

encountered.

Unexpected sysdb error: [chars]: [chars]:

[hex]

An unexpected sysdb error condition

encountered.

File '[chars]' is corrupted on both primary

and secondary device, need recovery
action such as 'install verify packages
repair location <>'.

The specified file is found to be corrupted

during sync operation. There is no backup
copy on the node hence no recovery was
attempted.

File '[chars]' is corrupted. Error - [chars]

([chars])

The specified File is corrupted on Primary

Boot Device.

Recovery for Corrupted File '[chars]

The specified File is corrupted on Primary
(backup:[chars])' is failed because [chars] . Boot Device. Recovery was attempted but
Error - [chars] ([chars])
failed.

Mirroring disabled because [chars].

RedFs disabled mirroring because of the

specified reason.

Corrupted File '[chars]' on Primary Boot

Device has been recoverd.

The specified File on Primary Boot Device

has been recoverd.

Failed to preload [chars].

RedFs failed to load its dependent DLL.

Mirroring unable to start because harddisk RedFs indicates that mirror sync process
device [chars] is not ready due to reason
cannot start because the specfied harddisk
'[chars]'.
device is not ready for the given reason.
Harddisk Mirroring will now be disabled
while in sync state '[chars]' due to local
mirroring

RedFs indicates that harddisk mirror will

stop and local disk mirroring will start.

Failed to initialize [chars]: [hex]:[chars].

RedFs failed to initialize a module.

Mirror [chars] error on [chars]/[chars].

Error-[dec]:[chars].

RedFs indicates that mirroring error

occured on the operation and file specified
with the specified error.

RedFs indicates that mirroring state is no

Mirroring is not redundant because [chars]. longer redundant and is only using the
Only using device [chars] now.
specified device.

RedFs indicates that mirror sync process

Mirroring unable to start because
cannot start because the specfied
secondary device [chars] is not partitioned. secondary device is not partitoned. It must
Please format partition it.
be partitioned to start mirroring.

Mirroring has been paused. Please do

'mirror resume' to restart mirroring.

RedFs indicates that mirroring has been

paused.

RedFs indicates that mirror sync process

Mirror sync failed on [chars]/[chars]. Error- has failed on the specified file and is not
[dec]:[chars].
able to make disks redundant.

Copy file '[chars]' from [chars] to [chars]

(pri:([chars])[dec], sec:([chars])[dec])

The specified file is copied to recover.

File '[chars]' is corrupted and will be

recovered.

The specified file is found to be corrupted

during sync operation. System has backup
copy of this file, so file will be restored.

Mirroring has been enabled with configured RedFs indicates that mirroring has been
devices of [chars] and [chars].
enabled with the specified devices.
Mirroring is now fully redundant for devices RedFs indicates that mirroring state is now
[chars] and [chars].
fully redundant for the specified devices.
Mirroring has been resumed after being
paused.

RedFs indicates that mirroring has been

resumed after being paused.

Mirroring is partitioning device [chars] as

part of upgrade procedure.

RedFs indicates that it is partitioning the

specified device as part of the mirroring
upgrade procedure.

% Out of memory

system is running out of memory.

% Out of memory

*NONE*

% Internal error

an internal error occured while regular

expression matching.

% Internal error

*NONE*

% invalid regexp: [chars]

invalid regular expression matching has

been tried.

% invalid regexp: [chars]

*NONE*

% [chars]

a corrupted regular expression is been tried

to match.

% [chars]

*NONE*

Failed to create required '[chars]' object

'[chars]', id=[hex]: [chars]

Failed to internally create an object

required to provide service.

An important resource '[chars]' required to An important resource required to perform

operate was unavailable: [chars]
an operation was unavailable.

'[chars]' had a value of '[chars]', which did A software bug when an internal data
not match the expected value '[chars]'.
consistency check failed.

Consistency Check for Locally requested

Tables failing for Client '[chars]'. Expected
Local Table count=[dec], Actual Local Table A software bug when an internal data
count=[dec]
consistency check failed.

'[chars]' failed: [chars]

Some requested operation failed. The text

of the message displays the failed
operation with error code.

Initialization of a required module failed.

'[chars]' failed during initialization: [chars] The process was unable to continue.
Unexpected interface name:handle
mapping change from [chars]:[hex] to
[chars]:[hex].

An interface handle was received which

does not match the interface handle
already in the database.

Client has passed a wrong table as a

dependency. No action is being taken. This
Client id [hex] has passed a wrong table as is likely caused by a race condition in the
a dependency tblid=[hex]
code.

Client '[chars]' has not processed an

update [dec] seconds after being notified.
Forcing reconnect. PID=[dec],

RSI is forcing the specified client to

reconnect, as the client has not processed
a notification after a substantial timeout
period.

Based on the card configuration/type, the

AFI IPv[dec] role of the card has changed
from [chars] to [chars]

Based on the card configuration the role of

this card has changed. The text of the
message displays more informationi about
the change. 'show svd role' would provide a
summary of AFI specific card roles.

Callback from ENS on incorrect thread,

actual/expected = [dec]/[dec]

Detected single-threaded RSI Master code

running on an unknown thread. This
concurrency can result in corruption. %d/
%d indicate actual tid/expected tid.

Insufficient memory for '[chars]', [unsigned RSI Master terminated due to lack of
int] bytes, terminating
memory for a critical operation.

'[chars]' failed: [chars]

Some requested operation failed. The text

of the message displays the failed
operation with error code.

[chars]

Some requested operation failed. The text

of the message displays the failed
operation.

[chars]

There are restrictions to enable and disable

Selective VRF Download. The text of the
message displays more information.

Values from [chars] are invalid. data=\

[chars]\. start=[dec], end=[dec].

Reserve Physmem encountered a severe

error and is not able to recover from the
error. Details are provided with the error
message. Call support with this error
message text.

Did not set return values correctly. start=

%zu, size=%zu, base_addr=%zu,
mem_size=%zu,
mem_physical_start=[pointer],
mem_physical_size=%zu.

Reserve Physmem encountered a severe

error and is not able to recover from the
error. Details are provided with the error
message. Call support with this error
message text.

Invalid parameters passed to function.

[chars] is NULL

Reserve Physmem encountered a severe

error and is not able to recover from the
error. Details are provided with the error
message. Call support with this error
message text.

memutil_find_reserved_mem returned
invalid memory reservation mem_physical_start=[pointer],
mem_physical_size=%zd.

Reserve Physmem encountered a severe

error and is not able to recover from the
error. Details are provided with the error
message. Call support with this error
message text.

Open of [chars] failed. Error [chars]

Reserve Physmem encountered a severe

error and is not able to recover from the
error. Details are provided with the error
message. Call support with this error
message text.

sscanf function failed to match required

number of parameters. Matched [dec],
error: [chars]. data=\[chars]\.

Reserve Physmem encountered a severe

error and is not able to recover from the
error. Details are provided with the error
message. Call support with this error
message text.

Failed to find any line in [chars] for infrastructure : [chars]

Unable to read reserved physical memory

for a given memory infra-structure. There
can be a case when there is no support for
that infra-structure on platform. Details are
provided with the error message. Call
support with this error message text.

Could not register dll with error services:

[chars]

The call register the dll using

cerr_register_dll failed.

debug services function [chars] failed

A call to a debug services interface failed.

event manager function [chars] failed:

[chars]

A call to an event manager interface failed.

rt_check library error in [chars]: [chars]

A generic error occured in the rt_check

library.

mgd timer function [chars] failed

A call to a mgd timer interface failed.

Pthread operation [chars] [pointer] failed:

[chars]

A pthread operation failed

[chars]

A call to a sysdb interface failed.

[chars]: error connecting with Group

Services: [chars]

A call to group_join() failed. There could be

a problem connecting to underlying gsp
server or transport between RP and LCs. If
this is seen for a long time, there might be
a real issue.

[chars]: error group lookup with Group

Services: [chars]

A call to group_lookup() failed. There could

be a problem connecting to underlying gsp
server or transport between RP and LCs. If
this is seen for a long time, there might be
a real issue.

[chars]: error group set notify with Group

Services: [chars]

A call to group_set_notify() failed. There

could be a problem connecting to
underlying gsp server or transport between
RP and LCs. If this is seen for a long time,
there might be a real issue.

A call to group_send() failed. There could

be a problem connecting to underlying gsp
server or transport between RP and LCs. If
[chars]: error sending with Group Services: this is seen for a long time, there might be
[chars]
a real issue.

[chars] msg chan connect failed: [chars],

error [dec]: [chars]

A call to a LWM API failed.

debug services function [chars] failed

A call to a debug services interface failed.

Failed to add an external data manager

datalist for [chars]

A process has requested information

through SysDB, probably as the result of
executing a show command. The attempt
to add an item to an external data
manager datalist has failed.

Failed to create external data manager

datalist for [chars]

A process has requested information

through SysDB, probably as the result of
executing a show command. The creation
of the external data manager datalist has
failed.

Failed to encode [chars] data in external

data manager

A process has requested information

through SysDB, probably as the result of
executing a show command. The data
requested could not be encoded.

Failed to add to an external data manager

list for [chars]

A process has requested information

through SysDB, probably as the result of
executing a show command. The attempt
to add an item to an external data
manager list has failed.

A process has requested information

through SysDB, probably as the result of
executing a show command. The creation
Failed to create external data manager list of the external data manager list has
for [chars]
failed.

Failed to register its external data

manager: [chars]

The process failed when attempting to

register its external data manager with
SysDB.

event manager function [chars] failed:

[chars]

A call to an event manager interface failed.

group services function [chars] failed, error

[dec]: [chars]
A call to a group services interface failed.

[chars] detected inconsistency with [dec]

entries for scan-id [dec]

RCC or LCC detected an inconsistency

during verification of the route/label
information between RIB/LSD and the FIBs.
Please collect the inconsistency data and
analyze the results.

Memory allocation error.

Malloc or calloc returned a null pointer. This

indicates an out of memory condition. The
rt_check process will exit or return.

mgd timer function [chars] failed

A call to a mgd timer interface failed.

Producer [chars] request failure, error

[dec]: [chars]

A call to a BCDL interface failed.

pthread function [chars] failed

A call to a pthread interface failed.

Pthread operation [chars] [pointer] failed:

[chars]

The mutex lock/unlock failed

Failed to initialize RSI client library: [chars] Failed to initialize RSI global client library

Failed to get RSI tbl id from vrf name:

[chars]

The RSI failed to translate a vrf name into a

tbl id.

Failed to get RSI vrf name from tbl id:

[chars]

The RSI failed to translate a tbl id to a vrf

name.

[chars]

A call to a sysdb interface failed.

SYSMGR for fucntion: [chars], gave [chars]

error
SYSMGR failed to reply.

timer init failed

A call to the rt_check timer init routine

failed.

usage: [chars] [-m] [-u] [-M] [-U]

Incorrect command line arguments were

given to the module

[chars] detected node(s) did not reply to

background scan id [dec]

RCC or LCC detected a node that did not

reply to statistics request during a
background scan. It is possible that the
node is just busy with processing updates
and could not reply to the statistics. It is
also quite probable that the node in
question is blocked and is not no longer
working properly.

The process failed while attempting to

Failed to register its external data manager register its external data manager data
data blocks: [chars]
blocks with SysDB.

SEIPC INVALID OBJECT [chars]: [chars]

Encountered an error in debug module.

This error should not impact the major
functionality of the module. Here is a list of
possible reasons for this message (not allinclusive). - Invalid objects. This condition
indicates a problem where the object being
processed by the software is invalid.

SEIPC OPERATION FAILURE [chars]: [chars]

Encountered an error in debug module.

This error should not impact the major
functionality of the module. Here is a list of
possible reasons for this message (not allinclusive). - Failed to initialize modules.
Typically, this occurs when the software
tries to initialize the modules. - Failed to
shutdown modules. Typically, this occurs
when the software tries to shutdown the
modules.

SEIPC OPERATION FAILURE STR [chars]:

[chars], [chars]

A critical error during the initialization of

Service Engine IPC. The cause of the error
will be mentioned in the message
displayed. Here is a list of possible reasons
for this message (not all-inclusive). - Failed
to handle ip addr. This condition indicates a
problem with the software on the card.
Typically, this occurs when the software
tries handle ip address.

The size of receive buffer is less than the

required size. This will cause degraded
perforamce in SEIPC calls. Here is a list of
possible reasons for this message (not allinclusive). - Failed to receive buffer. This
condition indicates a problem with receive
[chars]: Limited size of receive buffer [dec] buffer size.

Server [chars], Error: [chars]

Failed to initialize the event manager

during IMDR due to the reason shown

Server [chars], Error: [chars]

Failed to initialize the event manager due

to the reason shown

Shmwin mutex lock global shared mutex

failed ([dec], [chars])

Global mutex lock/unlock failure has

occurred for shmwins open/close operation.

Shmwin server detected invalid window ID

Invalid window ID or group ID ([dec], [dec]) or group ID in shmwin meta data.

Failed to execute to retrieve incoming LWM

Shmwin server unable to retrieve incoming message for the reason shown in the
message due to [chars], Error: [chars]
message.

Initialization in shmwin server main failed

[chars], Error: [chars]

Shmwin server initialization failed when

setting up some resource in shmwin server
main.

Failed to mmap [chars] during MDR

mmap of the shared memory required to

store servers tree nodes failed during
IMDR.

Failed to mmap shmwin alloc memory at

[chars]

mmap of the shared memory required to

store servers tree nodes failed.

Failed to mmap shmwin statistic file at

[chars]

mmap of the shared memory required to

store shmwin statistic failed.

Received a bad message, [chars]

The message received by the server had

invalid values as indicated.

Failed in allocating memory

Not enough memory available in the

system.

Exhausted virtual memory, top [dec]

consumer, [chars]: [unsigned int] KBytes

Not enough memory available for shared

memory window in the system. Top shared
memory window users will be display on
the console.

Problem opening/reading from the platform

Server failed to open [chars], Error: [chars] shmwin file.

Failed to publish QSM namespace, [chars]

The server failed in advertising its

namespace through QSM

An error has occurred when shmwin was

trying to remap the memory. Shmwin
server needs the memory to operate.
Server remap shared memory failed due to Process will exit when it has encountered
[chars]
the error

Shmwin server failed to [chars], Error:

[chars]

There was a problem to initialize shared

memory file allocation.

Shmwin server failed to [chars], path

[chars], Error: [chars]

Shmwin server failed to map shmwin share

memory.

Shmwin server failed to create pool of

elements, Error: [chars]

Shmwin server failed to create pool of

elements

[chars] area's size %zd is smaller than

%zd(shmwin header size)

Opened shmwin size is smaller the shmwin

header size.

shmwin server [chars] window failed,

window:[chars] ([dec], [chars])

Mutex lock/unlock failure has occurred for a

shmwin open/close operation.

Shmwin server failed get shmwin list, path Shmwin server failed to retrieve shmwin
[chars], Error: [chars]
window list information.

Shmwin server failed logging [chars]

[chars], Error: [chars]

Shmwin server failed to retrieve shmwin

logging information.

Server unable to handle shmwin show

request due to [chars], error : [chars]

An error has occurred when server was

trying to handle a shmwin show request.

The shmwin control mutex was revived by

shmwin_svr

A participant process crashed or exited

while holding the shared shmwin control
mutex and the shmwin_svr revived the
mutex.

SHMWIN: Error encountered: [chars]

SHMWIN hit an error, which is described by

the description printed. This error indicates
that the shared memory window library
detected a service internal error condition.
This does not mean a service impacting
condition.

SHMWIN: Shared page related error

encountered: [chars] : failed with [chars]

SHMWIN hit an error related to the shared

page. This error indicates that the shared
memory window library detected a service
internal error condition. This does not
mean a service impacting condition.

SHMWIN: Failed to allocate new arena from SHMWIN failed to allocate the arena's
the server : [chars]
virtual range from the server.

SHMWIN: DATA translation error: wid [dec], SHMWIN encountered a data translation
[chars] [pointer], error [hex] ([chars])
error. Client data is not updated.

SHMWIN: Failed to free VM at address

[pointer] back to the server : [chars]

SHMWIN failed to free the arena's virtual

range back to the server. This is possibily
an indication of shmwin memory corruption

SHMWIN: fstat call for [chars] failed, error: SHMWIN encountered an error condition, a
[chars][[dec]]
fstat call failed.

SHMWIN: [chars]: ftruncate for [chars] to

size %zd failed, error: [chars][[dec]]

SHMWIN encountered an error condition,

the ftruncate failed.

SHMWIN: List node check failed, b:

[pointer], lnp: [pointer], nbpe: [dec],
d_usize: [dec]

SHMWIN encountered an error condition,

list node check failed

SHMWIN: [chars]: pid [dec], %zu, %zu

SHMWIN encountered an error condition,

the abort mmapping.

SHMWIN: [chars]: mmap at pid [dec]

address [pointer] size [dec] failed, error:
[chars][[dec]]

SHMWIN encountered an error when mmap

memory.

SHMWIN: [chars]: mmap peer at pid [dec]

address [pointer] size [dec] failed, error:
[chars][[dec]]

SHMWIN encountered an error when mmap

to a peer process.

SHMWIN: [chars]: munmap at pid [dec]

address [pointer] size [dec] failed, error:
[chars][[dec]]

SHMWIN encountered an error condition,

the munmap failed.

SHMWIN: [chars]: peer at pid [dec] address

[pointer] size [dec] failed, error: [chars]
SHMWIN encountered an error when
[[dec]]
munmap a peer process.

SHMWIN mutex operation : [chars], error:

[chars][[dec]]

SHMWIN encountered an error condition, a

mutex operation failed.

SHMWIN: shm open for [chars] failed, error: SHMWIN encountered an error condition,
[chars][[dec]]
the shm open failed.

SHMWIN global mutex [chars], error:

[chars][[dec]]

SHMWIN encountered an error condition

with the shmwin global lock, the a mutex
operation failed.

SHMWIN: [chars]: shmem unlink failed for

[chars] to size %zd failed, error: [chars]
[[dec]]

SHMWIN encountered an error condition,

the ftruncate failed.

SHMWIN: window [dec] mutex [chars],

error: [chars][[dec]]

SHMWIN encountered an error condition, a

mutex operation failed.

SHMWIN: [chars]: shmwin found file [chars]

of size %zd existing when not expecting,
SHMWIN encountered an error condition,
trying to continue
the file was existing already.

Copying the OVA artifacts to standby failed.

VM installation of '[chars]' will not happen
after failover
Artifacts copy failed description

Syncing the OVA artifacts to standby failed.

VM installations will not work after failover Artifacts sync failed description

[chars]: could not create event manager:

[chars]

An internal error was detected when

creating Event Manager.

Remote path '[chars]' should not start with

a '/'. Remove the '/' and try again
OVA path invalid

[chars]:[dec] malloc failed

--

Sending async pulse to Channel [chars]

(CJ-FIXME)SM process tried to send a pulse
failed, name=[chars], id=[dec], pid=[dec], to the clients channel using MsgSendPulse
coid=[dec].
api and encountered a failure.

service VM '[chars]' [chars] failed

VM activate/deactivate failure description.

VM ([chars]) [chars] Status: ([chars]), Error: VM install/upgrade/unistall failure

([chars])
description.

VM ([chars]) Licensing Failed with error:

([chars])

VM Licensing failed.

[chars]: Service Provisioing Manager config

failed, error: [chars]
Service Enablement config failed(CJ-FIXME).

OVA ([chars]) is copied to ([chars]).

Installation will begin now.

OVA copy done

OVA ([chars]) is getting copied to ([chars]).

When the copy is done, you will get the
notification.
OVA copy start

Service VM '[chars]' is '[chars]' successfully VM activate/deactivate status.

'[chars]' of service VM '[chars]' [chars]

VM install/upgrade/unistall status.

[chars]: [chars](): [chars]

A system call failed. The calling function,

the failed call, and error are displayed.

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error.

[chars]:[dec]:[chars]: Invalid attempt to

build chain (type [dec])

qnetbase_builder_func() called with bad

chain type.

[chars]:[dec]:[chars]: Base Control function

erroneously called!
qnetbase_control_func() wrongly called.

[chars]:[dec]:[chars]: Invalid attempt to

build chain (type [dec])

qnetcaps_builder_func() called with wrong

chain type.

[chars]:[dec] spaipc-base to register debug. debug_register() failed.

[chars]:[dec]:[chars]: Qnet encapsulation

node erroneously called!

qnetcaps_encaps() has been called, which

should never happen.

[chars]:[dec]:[chars]: packet_input returned netio_dll_packet_input_NEW() to Qnet

non-zero result code ([dec])
failed.

[chars]:[dec] failed to get destination slot.

error [dec]

pak_netio_uint32_get() failed.

Process (pid1=[dec]) didn't finish task for

[dec] seconds. Overseved by [chars]
(pid2=[dec]). Please raise a bug against
infra-lwmsg. attach_process -p <pid1> and
<pid2> are required to fix the issue.
Meantime, please try to restart process
with pid1 to temporary fix this issue.
Process may have been blocking in library

[chars] [[dec]:[chars]]

Critical error message from library

Couldn't register mutex revival service

([chars])

New service can't be registered due to

other infrastructure issue.

Maximum number of [dec] service entries

exceeded. No more service entry for
monitoring [[chars]] service.

New service can't be registered due to

memory exhaustion. Need to fix source
code to accept more services.

String length is %zd where limited to %zd

([chars])

Given string is longer than expected. There

is mismatch in source code.

Library misuse [[chars]] (pid=[dec],

function=[chars])

There is miuse of library.

Invalid ID is given ([dec]) (pid=[dec],

function=[chars])

There is miuse of library.

Error from [chars] ([dec]:[chars]),

(pid=[dec],id=[dec])

Error in other library

Process (pid=[dec]) didn't finish task for

[dec] seconds. Overseved by [chars]
(pid=[dec]).

Process is experiencing delay in library

MSG1[[chars]] ID[[dec]] MSG2[[chars]]

Debug message

ConnectAttach to Channel [chars] failed,

name=[chars], id=[dec], pid=[dec],
coid=[dec], err=[chars].

SSM process tried to connect to the clients

channel using ConnectAttach api and
encountered a failure.

ConnectDetach to Channel [chars] failed,

name=[chars], id=[dec], pid=[dec],
coid=[dec], retval=[dec], err=[chars].

SSM process tried to detach to the clients

channel using ConnectDetach api and
encountered a failure.

[chars]: could not create event manager:

[chars]

An internal error was detected when

creating Event Manager.

[chars]:[dec] malloc failed

Malloc failed for ssm process. Check if node

is in low memory condition.

SSM process tried to recover service by

calling sysmgr_start_mdr and and
encountered an error. Collect sysmgr traces
sysmgr_start_mdr failed for service [chars], and check state of the process specified by
pid=[dec], err=[chars]
pid.

Sending async pulse to Channel [chars]

SSM process tried to send a pulse to the
failed, name=[chars], id=[dec], pid=[dec], clients channel using MsgSendPulse api
coid=[dec].
and encountered a failure.

Connection to Channel [chars] is stuck,

name=[chars], id=[dec], pid=[dec], A
detail information is stored on
/tmp/ssm_restart_[dec].log, ssm process
will restart.

SSM process sends a pulse to the

monitored process over a lwm channel.
This error is reported when it tries to open
a connection to the channel and is stuck.

SSM process tried to restart the process

using the kill command and encountered
Failed to send [chars] to [chars], pid=[dec], an error. Check state of the process
err=[chars]
specified by pid.

[chars]:ssm_shm_open failed with err:

[chars]

SSM tried to create shared memory region

but failed. It will exit with failure status.

SSM process detects sysdb is not available.

Sysdb service is not available, ssm process It will restart and configuration will be
is restarting([chars]:[dec]).
ignored until sysdb comes back.

[chars]: ssm_config_init failed, error:

[chars]

ssm_config_init failed due to sysdb

intialization problem.

mdr recovery specified on RP for service

[chars], pid=[dec]

Recovery action specified (MDR) for the

failing service is unsupported on RP.

Card Reloading to recover failing service

[chars], pid=[dec]

SSM Process is taking recovery action for

the failing service. Cold reload is the
specifed recovery action for this service.

Service [chars], id=[dec] reports alarm

transition from [chars] to [chars]

Service alarm changes. They are not

necessarily critical errors but need
investigation by DE

Nodal service state changes from [chars] to Service state changed to

[chars]
available/unavailable.

Recovery unsuccessful for service [chars],

pid=[dec]

SSM Process took a recovery action, but

service is not responding

Service [chars], id=[dec] is down,

fail_count=[dec], callback_max=[dec],
proc_exited=[dec], recovery=[chars]

Service state has become unavailable. SSM

process will try a recovery action. They are
not necessarily critical errors but need
investigation by DE.

Service [chars], id=[dec] transitions from

[chars] to [chars]

Service state changes. They are not

necessarily critical errors but need
investigation by DE

Sysdb service becomes available, update

configuration.

SSM process detects sysdb becomes

available. It will register with sysdb to read
new configurations.

Wait for sysdb service becomes available.

SSM process is waiting for sysdb service(s)

become available.

Sysdb service [[chars]] is not available.

SSM process detects sysdb service is not

available.

System call failure :: [chars]: [chars]():

[chars]

A system call failed. The calling function,

the failed call, and error are displayed.

Unexpected: [chars]: [chars]: [hex]

An unexpected condition encountered. This

is not necessarily an error.

[chars]

An Emergency message logged.

[chars]

An emergency owner plane message

logged.

[chars]

An Error message logged.

[chars]

An alert owner plane message logged.

[chars]

A Critical message logged.

[chars]

A critical owner plane message logged.

[chars]

An Error message logged.

[chars]

An error owner plane message logged.

[chars]

A warning message logged.

[chars]

A warning owner plane message logged.

[chars]

A Notice message logged.

[chars]

A notice owner plane message logged.

[chars]

An Info message logged.

[chars]

An info owner plane message logged.

Could not create event manager: [chars]

The syslog_dev process has failed to create

an Event Manager.This can happen when
the process is (re)starting. The process
recovers by restarting itself.

An error occurred while waiting for an

event: [chars]

The event infrastructure will ignore this

error and continue to wait for the next
event. If this error is seen repeatedly, the
process may not be able to function and
will need to be restarted.

[chars]

A debug message logged.

[chars]

A debug owner plane message logged.

[chars] ([chars])

An unexpected error occurred. This can

happen when the process is (re)starting.
The process recovers by restarting itself.

Could not attach resource manager

funtions to event manager: [chars]

The syslog_dev process has failed to attach

a Resource Manager to an Event Manager.

Could not create a Posix thread

The pthread_create function reported an

error.

[chars]

The system is unusable.

[chars]

The system is unusable. Possible resource

shortage or coding error.

Attempt to Warm Reload the card has

failed. The syslog events logged
preceeding this event would indicate the
Aborting Warm Reload. Cold-restarting the reason for the failure to warm reload the
card ([chars]:[dec])
card.
Attempt to Warm Reload the card has
failed. The syslog events logged
preceeding this event would indicate the
Aborting Warm Reload. Cold-restarting the reason for the failure to warm reload the
card ([chars]:[dec])
card.
[chars]

Action must be taken immediately.

[chars]

Action must be taken immediately. Possible

resource shortage or coding error.

[chars]

Critical conditions are present. Possible

resource shortage or coding error.

[chars]

Critical conditions are present.

reboot to be managed by process ([chars]) A critical process ran into trouble and will
reason ([chars])
reboot the node.
reboot to be managed by process ([chars]) A critical process ran into trouble and will
reason ([chars])
reboot the node.
reboot required, process ([chars]) reason
([chars])

A critical process ran into trouble.

reboot required, process ([chars]) reason

([chars])

A critical process ran into trouble.

[chars]

A function call returned an unexpcted error.

Possible resource shortage or coding error.
Monitor CPU,memory conditions and
process crashes in that timing window.

[chars]

A function call returned an unexpcted error

[chars]: call to [chars] failed: [chars]

A function call returned an unexpcted error

[chars]: call to [chars] failed: [chars]

A function call returned an unexpcted error

[chars]: sysmgr_msg_sendv
SYSMGR_GET_PLACEMENT_LIST failed:
[chars]\n

Sysmgr prints this when a request for

placement list comes to a wrong node like
SC.

[chars]: sysmgr_msg_sendv
SYSMGR_GET_PLACEMENT_LIST failed:
[chars]\n

Sysmgr prints this when a request for

placement list comes to a wrong node like
SC.

[chars]

A function call returned an unexpcted error

[chars]

A function call returned an unexpected

error. Possible resource shortage or coding
error.

mandatory state off for all processes by

request

Check specified log for important

information

mandatory state off for all processes by

request

Check specified log for important

information

mandatory state on for all processes by

request

Check specified log for important

information

mandatory state on for all processes by

request

Check specified log for important

information

mandatory reboot aborted by request

Check specified log for important

information

mandatory reboot aborted by request

Check specified log for important

information

mandatory reboot option enabled by

request

Check specified log for important

information

mandatory reboot option enabled by

request

Check specified log for important

information

mandatory reboot option overridden by

request

Check specified log for important

information

mandatory reboot option overridden by

request

Check specified log for important

information

For high availability demonstration,

User [chars] ([chars]) requested a crash of processes may be intentionally crashed by
process with jobid [dec] at [chars]
sending them a fatal signal.
For high availability demonstration,
User [chars] ([chars]) requested a crash of processes may be intentionally crashed by
process with jobid [dec] at [chars]
sending them a fatal signal.
For high availability demonstration,
User [chars] ([chars]) requested a crash of processes may be intentionally crashed by
process [chars] at [chars]
sending them a fatal signal.
For high availability demonstration,
User [chars] ([chars]) requested a crash of processes may be intentionally crashed by
process [chars] at [chars]
sending them a fatal signal.
For high availability demonstration,
User [chars] ([chars]) requested a restart of processes may be intentionally restarted
process with jobid [dec] at [chars]
by users.
For high availability demonstration,
User [chars] ([chars]) requested a restart of processes may be intentionally restarted
process with jobid [dec] at [chars]
by users.
For high availability demonstration,
User [chars] ([chars]) requested a restart of processes may be intentionally restarted
process [chars] at [chars]
by users.

For high availability demonstration,

User [chars] ([chars]) requested a restart of processes may be intentionally restarted
process [chars] at [chars]
by users.
User [chars] ([chars]) requested a
shutdown of process with jobid [dec] at
[chars]

For high availability demonstration,

processes may be intentionally shut down
by users.

User [chars] ([chars]) requested a

shutdown of process with jobid [dec] at
[chars]

For high availability demonstration,

processes may be intentionally shut down
by users.

User [chars] ([chars]) requested a

shutdown of process [chars] at [chars]

For high availability demonstration,

processes may be intentionally shut down
by users.

User [chars] ([chars]) requested a

shutdown of process [chars] at [chars]

For high availability demonstration,

processes may be intentionally shut down
by users.

User [chars] ([chars]) requested a start of

process with jobid [dec] at [chars]

Processes may be started by users. This log

maintains a record of process starts

User [chars] ([chars]) requested a start of

process with jobid [dec] at [chars]

Processes may be started by users. This log

maintains a record of process starts

User [chars] ([chars]) requested a start of

process [chars] at [chars]

Processes may be started by users. This log

maintains a record of process starts

User [chars] ([chars]) requested a start of

process [chars] at [chars]

Processes may be started by users. This log

maintains a record of process starts

[chars] Unable to delete logfile [chars],

because device was busy. Please delete
this file manually after making a copy.

Check specified log for important

information

[chars] Unable to delete logfile [chars],

because device was busy. Please delete
this file manually after making a copy.

Check specified log for important

information

[chars]

Warning conditions are present.

[chars]

Warning conditions are present. Possible

resource shortage or coding error.

[chars]

A normal but significant event has

occurred.

[chars]
[chars]
[chars]

A normal but significant event has

occurred.
An informational message only
An informational message only

[chars]

Check specified log for important

information

[chars]
[chars]
[chars]

System event occured requiring that

specified log to be checked for important
information
An informational message only
An informational message only

[chars]: [chars] [chars] failed: [chars]

A function call returned an unexpcted error

[chars]: [chars] [chars] failed: [chars]

software installation is finished
software installation is finished

A function call returned an unexpcted error

software installation has finished.
software installation has finished.

A notification to begin processing a

notification of software installation received software installation has been received.
A notification to begin processing a
notification of software installation received software installation has been received.

[chars]%s, timer = [pointer]

A software or hardware error occurred.

Parent has no child, this may be a

freed/stopped parent

All parents in a managed timer tree should

have at least one child.

Cannot start timer ([pointer]) with negative

offset ([dec]).
An internal error occured in timer api.

A timer wheel has been created with a

timeslice less than 100ms and cannot
accurately be supported. The timeslice
specified was [dec]ms.

The kernel will override a request to create

a repetitive timer of less than 100ms on a
priority 10 thread and internally use
100ms. This could cause software using
this timer wheel to behave extremely
badly.

Couldn't allocate a chunk for timer wheel

There wasn't enough resources to allocate

a chunk in timer wheels.

Couldn't free chunk for timer wheel

Resources were not able to be deallocated

in timer wheels.

EVM error [dec] in timer wheels.

EVM failed.

Error acquiring mutex for timer wheel;

[chars]

A software error occurred acquiring a

mutex.

Error releasing mutex for timer wheel;

[chars]

A software error occurred releasing a

mutex.

Couldn't allocate memory for timer wheel

Not enough resources to allocate a system

structure in timer wheels.

OS error [dec] in timer wheels.

OS call failed.

Timer wheels Couldn't allocate OS timer for

timer wheel ([dec])
Could get access to OS timer resources.

OS timer error [dec] in timer wheels

Couldn't manipulate OS timer.

[chars]: [chars]

Serious problem occured.

[chars]: [chars]

Serious problem occured.

LRd error: [chars]

Unable to query LR status

LRd error: [chars]

Unable to query LR status

Unable to find timezone config string field

when checking persistent file [chars]: the
PUF file doesn't have valid format.

This indicate a format error in timezone

configuration file.

Unable to find timezone config string field

when checking persistent file [chars]: the
PUF file doesn't have valid format.

This indicate a format error in timezone

configuration file.

Invalid PUF token type of [dec] for token ID

[dec] (expected token type = [dec]) in
This indicate invalid token type detected in
[chars]
timezone configuration file.

Invalid PUF token type of [dec] for token ID

[dec] (expected token type = [dec]) in
This indicate invalid token type detected in
[chars]
timezone configuration file.

The persistent file ([chars]) has invalid

magic number of [hex] (expected [hex]) file doesn't have valid format.

This indicate a format error in timezone

configuration file.

The persistent file ([chars]) has invalid

magic number of [hex] (expected [hex]) file doesn't have valid format.

This indicate a format error in timezone

configuration file.

Unable to find magic number field when

checking persistent file [chars]: the PUF file This indicate a format error in timezone
doesn't have a valid format.
configuration file.

Unable to find magic number field when

checking persistent file [chars]: the PUF file This indicate a format error in timezone
doesn't have a valid format.
configuration file.

Can't access storage media '[chars]':

[chars]

There indicated media cannot be ccessed

to read/write timezone configuration file.

Can't access storage media '[chars]':

[chars]

There indicated media cannot be ccessed

to read/write timezone configuration file.

Unable to open file when reading persistent This indicate a failure attempt to open
file [chars]: [chars] ([chars])
timezone configuration file.

Unable to open file when reading persistent This indicate a failure attempt to open
file [chars]: [chars] ([chars])
timezone configuration file.

Unable to [chars] when writing persistent

file [chars]: [chars] ([chars])

This indicate a failure to create the

timezone configuration file.

Unable to [chars] when writing persistent

file [chars]: [chars] ([chars])

This indicate a failure to create the

timezone configuration file.

[chars]: [chars]

One of the sysdb APIs failed.

[chars]: [chars]

One of the sysdb APIs failed.

The timezone '[chars]' string was not

configured - [chars] ([hex])

This indicate error when setting timezone

string.

The timezone '[chars]' string was not

configured - [chars] ([hex])

This indicate error when setting timezone

string.

BFD PD encountered an error and is not

able recover from the error. A reason text
bfd pd : error encountered, reason=[chars] will be supplied call support with this text.

bfd pd : Could not find symbol.. init

0x[pointer] open 0x[pointer] close
0x[pointer] tx 0x[pointer]

BFD PD encountered an error and is not

able recover from the error. A reason text
will be supplied call support with this text.

bfm: locking error encountered,

reason=[chars], errno=[dec]

bfm encountered an error and is not able to

recover from the error. A reason text will be
supplied call support with this text. An
integer errno will also be printed.

BFM: memory allocation error for <[dec]>

bytes

BFM encountered an memory allocation

error

BFM: ptcl type [chars] is not as expected

type is [chars]

BFM encountered a warning condition

bfm: general debug,<[chars]>

The BFM's debug message.

an unknown platform type.

platform_get_type returned an unknown

platform type.

BFM: event msg type [dec] bradcast for

client jid [dec] error [chars]

BFM encountered an message event send

error

BFM: edm error [chars] due to [chars]

BFM encountered edm error

bfm: internal error encountered,

reason=[chars], error=[chars]

bfm encountered an error and is not able to

recover from the error. A reason text will be
supplied call support with this text.

bfm encountered an error and is not able to

bfm: an error encountered, reason=[chars], recover from the error. A reason text will be
error=[chars]
supplied call support with this text.

bfm: internal error encountered,

reason=[chars], error=[chars]

bfm encountered an error and is not able to

recover from the error. A reason text will be
supplied call support with this text.

BFM: an memory allocation error for

<[dec]> bytes

BFM encountered an memory allocation

error

BFM: message reply error for client [dec]

msg type [dec]

BFM encountered message reply error

Pool config failed: reason:[chars] error:

[dec]

BFM encountered pool state error

A Pool with ID [dec] in region ID [dec] found

to be in *unknown* state
BFM encountered an pool state error

bfm: registration failed, reason=[chars]

iq manager encountered an error and is not

able recover from the error. A reason text
will be supplied call support with this text.

bfm: internal error encountered,

reason=[chars], error=[chars]

bfm encountered an error and is not able to

recover from the error. A reason text will be
supplied call support with this text.

bfm encountered an error and is not able to

recover from the error. A reason text will be
bfm: an error encountered, reason=[chars], supplied call support with this text. An
errno=[dec]
integer errno will also be printed.

bfm: init failed, reason=[chars]

iq manager encountered an error and is not

able recover from the error. A reason text
will be supplied call support with this text.

bfm encountered an error and is not able to

recover from the error. A reason text will be
bfm: an error encountered, reason=[chars], supplied call support with this text. An
errno=[dec]
integer errno will also be printed.

iq manager encountered an error and is not

able recover from the error. A reason text
will be supplied call support with this text.
bfm: An error encountered, reason=[chars], Some of the functionality may not work
error=[chars]
until this error is removed.

bfm: init error encountered,

reason=[chars], attempt=[dec],
error=[chars]

bfm encountered a error and is not able to

recover from the error trying again. A
reason text will be supplied call support
with this text.

[chars][dec]

An error occured in the forwarder netio

client dll (possible the plim driver)

Dropped a statistics notification for CFM

An error was encountered while attempting

to deliver statistics to the Connectivity
Fault Management (CFM) protocol. This is a
transient problem from which the system
should recover, but CFM statistics may be
incorrect until it does. This may indicate
the system is under unusuallay high traffic
load.

Dropped a timeout notification for CFM

An error was encountered while attempting

to deliver a notification of a timeout event
to the Connectivity Fault Management
(CFM) protocol. This is a transient problem
from which the system should recover, but
CFM may take longer to identify
connectivity errors until it does. This may
indicate the system is under unusuallay
high traffic load.

[chars]

An error occurred during initialization.

eint: netio idb attach failed for plim

interface: [hex].

EINT was not able to attach to plim

interface .

eint: received bad command result for

buffer request: [hex]

EINT received a bad command result for

BMA free buffer request.

eint: BMA buffer request/response

sequence number mismatch - received
[dec], expected [dec]

EINT received an out of sequence BMA

buffer request response

eint: fatal error encountered,

reason=[chars]

Null Driver partner encountered a fatal

error and is not able recover from the error.
A reason text will be supplied call support
with this text.

eint: fatal error encountered,

reason=[chars], errno=[dec]

eint encountered a fatal error and is not

able to recover from the error. A reason
text will be supplied call support with this
text. An integer errno will also be printed.

Failed to get idb ctx for port [dec], error ([dec])

EINT driver got a packet but couldn't map a

port to an idb context

EINT idb context for port [hex] is NULL!

While processing an ingress packet, the

eint driver failed to find idb context

eint: looking for plim interface: [hex], netio EINT was supplied with a plim interface
gave us: [hex].
that does not have an idb yet.

eint: service degrading error, reason =

[chars]

The eint encountered an error that would

lead to degraded service.

eint: invalid plim port <[dec]> for plim

interface: [hex]

EINT was supplied with a plim port that

exceeds the limit of num ports.

eint: fatal memory allocation error for

<[dec]> bytes

EINT encountered a fatal memory

allocation error

eint: plim interface: [hex] does not have a

netio idb.

EINT was supplied with a plim interface

that does not have an idb yet.

[chars]: Mutex [chars] operation failed on

[chars]; reason [chars]

The packet subsystem failed to get mutex.

netio idb for interface [hex] not found,

dropping packet 0x[pointer]

While processing an ingress packet, the

eint driver failed to find netio idb

EINT received a BMA interrupt indicating a

eint: received BMA buffer request response response to a BMA buffer request but there
with no outstanding request
was no request made

eint: this function <[chars]> is not yet

implemented

EINT, a function was not implemented.

Packet dropped: reason [chars], packet

contents: [chars]

The packet was dropped due to the

specified reason.

Failed to find netio egress qad queue,

dropping packet 0x[pointer]

While transmitting a packet down to the

fabric, couldn't find the egress queue

Failed to populate netio egress queue, error EINT driver failed to populate qad netio
- [chars]
egress queue

Failed to create eint qad rx thread, error [chars]

EINT driver failed to create qad rx thread

Failed to set input interface handle [hex] on While processing an ingress packet, the
packet
eint driver failed to set input interface

Fatal error: [chars]: Err=[dec]

A fatal error occurred in L2 Encap String RM

which involves exiting the process. Shared
memory operation from L2 Encap RM s
unsuccesful.

encap_rm: msg: [dec], retried: [dec]

time(s), failed to send, errno: [chars]

Unable to send a message to the L2 Encap

String resource-manager server.

Nonfatal error: [chars]: Err=[dec]

This is a error message in the L2 Encap

String RM to indicate anomalies which are
not FATAL. Some of the messages may
indicate a failure to allocate resources
needed by applications. In many cases
these messages must not keep appearing
after the temporary situation is resolved.

A request to insert a L2 encapsulation

Failed to insert L2 encapsulation string. Out string into the encapsulation table has
of resource condition reached.
failed due to out of resource condition.
Info: [chars]

This is an informational message in the L2

Encap String RM.

Auto-recovery failed on interface

<<CH[hex]>>: [chars]

Auto-recovery failed to restart on the given

interface. This interface will remain in ErrorDisable state until manually cleared.

The Verification Daemon Debug failed to

initialize: [chars]

This is a fatal error which would stop the

process from debugging. The process will
restart in an attempt to clear the error.

Failed to begin processing events: [chars]

The Verification Daemon failed to start

processing events. This is a fatal error.

The owner library has received

configuration that should have been
rejected by the verification daemon. The
owner has not acted on the invalid
Invalid configuration has been received by configuration, but the system is now in an
the owner library: [chars]
inconsistent state.

Failed to shut down process correctly:

[chars]

The Verification Daemon failed to inform

SysManager of it shutting down due to
removal of configuration. This is not a fatal
error but should be investigated all the
same as it may cause the process to restart
when no configuration is present.

Auto-recovery failed on an interface and

Auto-recovery failed on interface [hex]
will not be retried due to the auto-recovery
which has since had auto-recovery disabled configuration being deleted.

This is a fatal error for the standby

verification daemon process. Unless this is
resolved, the standby process will not be
informed when the node goes active
Verification Daemon failed to block on
following a failover event. The process will
sysmgr for the node to to go active: [chars] restart in an attempt to clear the error.

The Verification Daemon failed to cleanup

the config module: [chars]

The Verification Daemon failed to cleanup

its configuration registrations, this may
leave stale state within SysDB. The process
is exiting anyway, but subsequent process
restarts may hit errors within SysDB during
initialization.

Verification Daemon failed to initialize the

config module: [chars]

This is a fatal error which would stop the

process from verifying and applying
configuration. The process will restart in an
attempt to clear the error.

The Verification Daemon failed to cleanup

the debug module: [chars]

The Verification Daemon failed to cleanup

its debug registrations, this may leave stale
state in the debug infrastructure. The
process is exiting anyway, but subsequent
process restarts may hit errors within the
debug infrastructure during initialization.

Failed to cleanup debug module: [chars]

Could not cleanup the debug module, this

message should be harmless as the
process is exiting anyway, but it may leave
stale state causing a future restart to fail.

The Verification Daemon failed to destroy

The Verification Daemon failed to shutdown its event manager. The process is exiting
the event manager: [chars]
anyway which should clear the condition.

Verification Daemon failed to initialize the

event manager: [chars]

This is a fatal error. The verification

daemon will be unable to process any
events. The process will restart in an
attempt to clear the error condition.

Verification Daemon failed to inform

SysMgr that the process is ready: [chars]

This is a fatal error which will slow down

system intialization following boot or a
failover event. The process will restart in an
attempt to clear the error.

<<CH[hex]>>: Error disabling due to

reason: [chars]

The interface is being error disabled. This

has occurred due to the reason given in the
log.

[chars] error. region [chars] direction

[chars] ([chars])

After a process restart, an error was

encountered while recovering checkpoint
memory/database. The runningconfiguration and hardware programming
may be inconsistent. Problems may be
encountered with future configuration
changes as well.

MSTATS [chars] region: [chars]

Feature EA DLL failed to allocate statistics

entry for ACL. Number of ACL entries
requiring statistics entries has exceeded
statistics entries reserved for security ACLs
on this line card. As a result, per ACE
hardware accouting for the failed ACL
entries is not available. There is no impact
on ability to apply security ACLs in
hardware.

MSTATS [chars] error: [chars]

Feature EA DLL encountered error on

initializing interface with hardware
statistics API. Process will be restarted
automatically. On restart, Feature EA DLL
will initialize interface with hardware
statistics API and no action needs to be
taken.

PRM INIT [chars] error: [chars]

Feature EA DLL encountered error in

completing PRM init operation. This can
lead to malfunction or restart of pfilter ea
process.

PRM SSH [chars] error: [chars]

Feature EA DLL encountered error in

completing PRM SSH operation. This can
lead to failure of configuration.

Errored during scrub reprogramming

[chars] : [chars]

TCAM entries are reprogrammed every 24

hours to ensure accuracy of hardware
entries programmed earlier on user
configuration or system changes. This
message lists the ACL for which errors have
occured during reprogramming.

Errored during scrub reprogramming

[chars] : [chars]

TCAM entries are reprogrammed every 24

hours to ensure accuracy of hardware
entries programmed earlier on user
configuration or system changes. This
message lists the ACL for which errors have
occured during reprogramming.

STATS [chars] region: [chars]

Feature EA DLL failed to allocate statistics

entry for ACL. Number of ACL entries
requiring statistics entries has exceeded
statistics entries reserved for security ACLs
on this line card. As a result, per ACE
hardware accouting for the failed ACL
entries is not available. There is no impact
on ability to apply security ACLs in
hardware.

STATS [chars] error: [chars]

Feature EA DLL encountered error on

interacting with PRM Stats APIs. Error
encountered during performing ace counter
related operations e.g., allocation of
counter, clearing the counter etc.

TCAM [chars] error: [chars]

Feature EA DLL encountered error in

completing TCAM operation. This can lead
to mismatch between hardware and
software configuration.

TCAM [chars] limit exceeded

This message will typically occur when

permissible single region size is exceeded
or total number of entries allowed in TCAM
for a given application is exceeded.

UIDB [chars] error: [chars] : [chars]

UIDB stores the reference to ACL entries

programmed in TCAM for the interface,
protocol and direction. This error message
is due to one of the following reasons: 1.
Initialization failure of Feature EA DLL and
UIDB manager interface. 2. Failure to set
reference of hardware entries programmed
or removed for security ACL in UIDB on
configuration or system changes. This
failure can lead to mismatch between
hardware and software configuration.

UIDB [chars] error: [chars] : [chars]

UIDB stores the reference to ACL entries

programmed in TCAM for the interface,
protocol and direction. This error message
is due to one of the following reasons: 1.
Initialization failure of Feature EA DLL and
UIDB manager interface. 2. Failure to set
reference of hardware entries programmed
or removed for security ACL in UIDB on
configuration or system changes. This
failure can lead to mismatch between
hardware and software configuration.

TCAM [chars] error: [chars]

Feature EA DLL encountered error in

completing TCAM operation. This can lead
to mismatch between hardware and
software configuration.

Deny action is not supported and will be

ignored in [chars] ACL: [chars], ACE: [dec]

'Deny' action for an ACE is not supported

and will be ignored. The behavior will be
the same as with Permit action.

The following match criteria specified in an

Unsupported match field: [chars], in [chars] ACL are not supported as part of a QoS
ACL: [chars], ACE: [dec].
policy: Packet Length, TTL, TCP Flags.

MSTATS [chars] region: [chars]

Feature Manager failed to allocate statistics

entry for ACL. Number of ACL entries
requiring statistics entries has exceeded
statistics entries reserved for security ACLs
on this line card. As a result, per ACE
hardware accouting for the failed ACL
entries is not available. There is no impact
on ability to apply security ACLs in
hardware.

MSTATS [chars] error: [chars]

Feature Manager encountered error on

initializing interface with hardware
statistics API. Process will be restarted
automatically. On restart, Feature Manager
will initialize interface with hardware
statistics API and no action needs to be
taken.

Errored in reprogramming policy-map

[chars] used by ACL [chars]: [chars]

When an ACL definition is changed which is

used by a some class-map as a match
criteria, it result in reprogramming of all
the polices which are using this class-map
and are already applied to some interfaces.
This message lists the policy-map and ACL
for which errors have occured during
reprogramming.

TCAM [chars] limit exceeded

This message will typically occur when

permissible single region size is exceeded
or total number of entries allowed in TCAM
for a given application is exceeded.

UIDB [chars] error: [chars] : [chars]

UIDB stores the reference to ACL entries

programmed in TCAM for the interface,
protocol and direction. This error message
is due to one of the following reasons: 1.
Initialization failure of Feature Manager and
UIDB manager interface. 2. Failure to set
reference of hardware entries programmed
or removed for security ACL in UIDB on
configuration or system changes. This
failure can lead to mismatch between
hardware and software configuration.

TCAM [chars] error: [chars]

Feature Manager encountered error in

completing TCAM operation. This can lead
to mismatch between hardware and
software configuration.

FINT n2n protocol dll could not set certain

internal protocol mapping. This should not
affect the functionality of any other
control set mapping for capsulation [chars] protocol traffic, but might affect n2n
protocol [dec] ([chars]) failed: [chars]
protocol traffic only.
Description: [chars] Group: [chars] FID:
[chars]([unsigned long long int]) EID:
[chars]

Autogenerated alarm

'[chars]: [chars] failed rc=[chars]'

There was a IOS-XR infra call failure while

attempting to provide some infrastructure
service. These typically could be some IPC
services or debug infrastructure, etc.

Description: [chars] Group: [chars] FID:

[chars]([unsigned long long int]) EID:
[chars]

Autogenerated alarm

'FM EDM initialization failed: [chars]'

The FM process failed to initialize its edm

manager.

An internal error was detected when trying

'[chars]: could not create event connection: to create event connection for FM with
[chars]'
netio or sysdb.

'[chars]: could not open all event

An internal error was detected when trying
connections attached to an Event Manager: to open all event connections attached to
[chars]'
an Event Manager.

FID:[chars]([unsigned long long int]) EID:

[chars] opaque: [chars]

Fault Detected

'[chars]: [chars] failed'

Interface Manager client api call failed

Process initialization failed: ([chars]%s)

The feature manager (feat_mgr) process

failed to initialize. This process programs
packet classification hardware for features
which require an action to be performed
based on the packet classification. If the
feat_mgr process fails to initialize, the
access control list cannot be programmed
into the hardware. %s - indicates the
reason for the initialization failure. %s - is
the decoded error reason.

'Cannot allocate memory in function

[chars]()'

Internal error. System is out of memory malloc failed.

Description: [chars] Group: [chars] FID:

[chars]([unsigned long long int]) EID:
[chars]

Autogenerated alarm

'Failed to call the backend parser to handle

all datalist requests : [chars]'
backend_edm_datalist() call failed.

'Failed to call the backend parser to handle

all get requests : [chars]'
backend_edm_get() call failed.

'[chars]: [chars] failed: [chars]'

This failure encountered when registering

or encoding or decoding of FM bags are
failed.

'[chars]: could not set notify handler for

connection open/close/error: [chars]'

An internal error was detected when trying

to set notify handler for connection opens,
closes and errors.

'[chars]: Invalid Params'

Internal error. Function was passed an

Invalid Parameter.

'[chars]: [chars] failed\n[chars]'

Sysdb api call failed.

'[chars]: im_caps_datapath_control failed

err [[chars]]'
[chars] [chars]

im_caps_datapath_control to LPTS netio

caps dll failed
Information message.

FID:[chars]([unsigned long long int]) EID:

[chars] opaque: [chars]

Information message.

'[chars]: [chars]'

The FM encountered a problem of a generic

nature or an informational message.

Deny action is not supported and will be

ignored in [chars] ACL: [chars], ACE: [dec]

'Deny' action for an ACE is not supported

and will be ignored. The behavior will be
the same as with Permit action.

Deny action is not supported and will be

ignored in [chars] ACL: [chars], ACE: [dec]

'Deny' action for an ACE is not supported

and will be ignored. The behavior will be
the same as with Permit action.

Only the following match types specified in

an ACL are supported as part of an AFmon
policy: Source/ Destination IP address,
Source/ Destination Port values. An ACE
Match on [chars] is not supported in AFmon containing any other match types will be
policy. ACE [dec] in [chars] ACL [chars] on ignored i.e. it will not be programmed in
interface [chars] will be ignored.
hardware.

The following match criteria specified in an

ACL are not supported as part of a QoS
policy: Packet Length, TTL, TCP Flags. An
Unsupported match field: [chars], in [chars] ACE containing any of these match fields
ACL: [chars], ACE: [dec]. ACE will be
will be ignored i.e. it will not be
ignored
programmed.

The following match criteria specified in an

ACL are not supported as part of a QoS
policy: Packet Length, TTL, TCP Flags. An
Unsupported match field: [chars], in [chars] ACE containing any of these match fields
ACL: [chars], ACE: [dec]. ACE will be
will be ignored i.e. it will not be
ignored
programmed.

[chars]

A message from Platform Manager

containing set/unset notifications for subinterface VLAN IDs was too large and had
to be dropped because enough memory
could not be allocated. As a result, for a
'set' notification, QoS was not enabled for
the reported VLANs. For an unset
notification, QoS was not disabled for the
reported VLANs.

Only rules matching UDP packets are

supported in AFmon policy. ACE [dec] in
[chars] ACL [chars] on interface [chars] will
be ignored.

AFmon policy only allows matching on UDP

flows. Other types of match rules will be
ignored i.e. they will not be programmed in
hardware.

[chars] (error = [chars])

Request to TCAM Manager for programming

QoS match rules into TCAM failed. Feature
manager sends this request to TCAM
manager when a policy is
attached/removed to/from an interface (or
fabric), when there is a change in bundle
membership or when an ACL which is used
in a QoS policy is modified. The most likely
cause of this error is not enough space
remaining in TCAM.

[chars] (error = [chars])

Request to TCAM Manager for allocating a

QOS Policy ID for a policy attached to an
interface failed. The most likely cause of
this error is not enough ACL IDs remaining
in TCAM manager. QOS policy on this
interface will not take effect since TCAM
entries are not programmed.

Encountered error while compressing IPv6

src address (error = [chars])

Request to TCAM Manager for IPv6 src

prefix compression failed. QOS policy on
this interface will not take effect since
TCAM entries are not programmed.

Feature Mgr failed to program UIDB for

QoS. (reason: [chars])

Feature Mgr failed to program the correct

QoS related information in UIDB (interface
data structure in hardware) when
enabling/disabling QoS on the interface.
The most likely cause of this message is
deletion of a vlan sub-interface when there
is a qos policy attached on the parent
physical interface. In this case, the
message is harmless and can be ignored.
The reason this happens is because, the
feature_mgr process tries to reset QoS
related flags in the UIDB, but by that time
the UIDB entry has already been deleted. It
is possible, though very unlikely, for this
message to appear in the following cases:
1) A QoS policy is attached on an interface.
2) QoS policy is removed from an interface.
3) Vlan-id is configured for a sub-interface
and a QoS policy exists on the associated
physical interface. 4) Vlan-id is unconfigured on a sub-interface and a QoS
policy exists on the associated physical
interface. 5) When all members of a bundle
go 'down'. In such cases, the warning
message indicates that there could be a
problem in enabling/disabling QoS on the
interface.

[chars] (error: [chars]). Feature Mgr

initialization failed!

Feature Mgr process failed to initialize

correctly. In this case process will restart.

Unable to get heap memory during

upgrade: [chars]

Fwd basecaps dll was not able to get heap

memory.

Unexpected saved data length during

upgrade for DLL. Expected len [unsigned
int], got [unsigned int]

FINT DLL saves data across DLL upgrades.

It expects the length of saved data to be
same before and after upgrade, else it
would cause netio to take default action (to
restart) for upgrade to take effect.

FINT DLL does not support DLL upgrade

DLL upgrade with change in major version across major version changes. This will
number is not supported. Expected version cause netio to take default action to restart
[dec], got [dec]
for upgrade to take effect.

netio idb attach failed for plim interface:

[hex].

FWD was not able to attach to plim

interface .

fwd: netio idb attach failed for plim

interface: [hex].

FWD was not able to attach to plim

interface .

fwd: received bad command result for

buffer request: [hex]

FWD received a bad command result for

BMA free buffer request

fwd: BMA buffer request/response

sequence number mismatch - received
[dec], expected [dec]

FWD received an out of sequence BMA

buffer request response

egressq queue creation failed, q: [dec], rx: FWD was not able to create one of the
[dec], client: [dec], dev: [dec], rc = [dec]
egressq queues.

FWD encountered a memory allocation

Memory allocation error for <[dec]> bytes failure error

Forwarder netio dll error encountered,

reason=[chars]

Null Driver partner encountered a error and

is not able recover from the error. A reason
text will be supplied call support with this
text.

fabricq queue creation failed, q: [dec], rx:

[dec], client: [dec], dev: [dec], rc = [dec]

FWD was not able to create one of the

fabricq queues.

fwd: fatal error encountered,

reason=[chars]

Null Driver partner encountered a fatal

error and is not able recover from the error.
A reason text will be supplied call support
with this text.

fwd: fatal error encountered,

reason=[chars], errno=[dec]

fwd encountered a fatal error and is not

able to recover from the error. A reason
text will be supplied call support with this
text. An integer errno will also be printed.

Failed to get idb ctx for port [dec], error ([dec])

FWD driver got a packet but couldn't map a

port to an idb context

FWD idb context for port [hex] is NULL!

While processing an ingress packet, the

fwd driver failed to find idb context

looking for plim interface: [hex], netio gave FWD was supplied with a plim interface
us: [hex].
that does not have an idb yet.

fwd: looking for plim interface: [hex], netio FWD was supplied with a plim interface
gave us: [hex].
that does not have an idb yet.

fwd: service degrading error, reason =

[chars]

The fwd encountered an error that would

lead to degraded service.

ingressq queue creation failed, q: [dec], rx: FWD was not able to create one of the
[dec], client: [dec], dev: [dec], rc = [dec]
ingressq queues.

fwd: invalid plim port <[dec]> for plim

interface: [hex]

FWD was supplied with a plim port that

exceeds the limit of num ports.

invalid plim port <[dec]> for plim

interface: [hex]

FWD was supplied with a plim port or uidb

index that exceeds the limit of num ports.

fwd: fatal memory allocation error for

<[dec]> bytes

FWD encountered a fatal memory

allocation error

fwd: plim interface: [hex] does not have a

netio idb.

FWD was supplied with a plim interface

that does not have an idb yet.

[chars]: Mutex [chars] operation failed on

[chars]; reason [chars]

The packet subsystem failed to get mutex.

netio idb for interface [hex] not found,

dropping packet 0x[pointer]

While processing an ingress packet, the

fwd driver failed to find netio idb

FWD received a BMA interrupt indicating a

fwd: received BMA buffer request response response to a BMA buffer request but there
with no outstanding request
was no request made

fwd: this function <[chars]> is not yet

implemented

FWD, a function was not implemented.

Error retrieving buff_hdr parameters,

[chars] : [chars], pak = [hex], rc = [hex]\n

There was an packet processing error.

Possible causes 1) Unable to retrieve fabric
dest addr from inside the pkt 2) Error
setting/getting input ifh from pkt

Failed to find netio egress qad queue.

dropping packet 0x[pointer]

While transmitting a packet down to the

fabric, couldn't find the egress queue

Failed to populate netio egress queue, error FWD driver failed to populate qad netio
- [chars]
egress queue

Failed to create forwarder qad rx thread,

error - [chars]

FWD driver failed to create qad rx thread

Failed to set input interface handle [hex] on While processing an ingress packet, the
packet
fwd driver failed to set input interface

Unexpected packet has been received by

PRP3 Netio Forward Driver. Type: [dec]

An unexpected packet type was sent to the

PRP3 Fabric. This will not impact
functionality or performance. It is being
reported for informational purposes only.
Type: %d is the type of the packet that the
driver rejected.

txm locp info: magic:[hex]([dec])

copy_prec:([hex])[dec] prec_value:([hex])
[dec] \n

Information exchanged between Txm node

of netio chainwalker thread and bypass
thread during bypass init. These pointers
should be valid memmap pointers.

netio idb attach failed for plim interface:

[hex].

FWD was not able to attach to plim

interface .

egressq queue creation failed, q: [dec], rx: FWD was not able to create one of the
[dec], client: [dec], dev: [dec], rc = [dec]
egressq queues.

FWD encountered a memory allocation

Memory allocation error for <[dec]> bytes failure error

Forwarder netio dll error encountered,

reason=[chars]

Null Driver partner encountered a error and

is not able recover from the error. A reason
text will be supplied call support with this
text.

fabricq queue creation failed, q: [dec], rx:

[dec], client: [dec], dev: [dec], rc = [dec]

FWD was not able to create one of the

fabricq queues.

looking for plim interface: [hex], netio gave FWD was supplied with a plim interface
us: [hex].
that does not have an idb yet.

ingressq queue creation failed, q: [dec], rx: FWD was not able to create one of the
[dec], client: [dec], dev: [dec], rc = [dec]
ingressq queues.

invalid plim port <[dec]> for plim

interface: [hex]

FWD was supplied with a plim port or uidb

index that exceeds the limit of num ports.

Error retrieving buff_hdr parameters,

[chars] : [chars], pak = [hex], rc = [hex]\n

There was an packet processing error.

Possible causes 1) Unable to retrieve fabric
dest addr from inside the pkt 2) Error
setting/getting input ifh from pkt

Teleport Netio DLL failed initialization or

registration with the debugging subsystem.
Failed to [chars] [chars] with the debugging This resulted in the restart of NetIO
subsystem: '[chars]'
process.

Failed to get event manager handle to

register with the debugging subsystem:
'[chars]'

Teleport Netio DLL failed to get the event

manager handle from netio to register with
debug system. This resulted in the restart
of NetIO process.

Failed to cleanup registration with

debugging subsystem: '[chars]'

Teleport Netio DLL failed to cleanup the

registration with the debugging subsystem.
This may result in error when fwd DLL is reregistering with the debug system. If such
an error is not noticed, no further action is
needed.

Failed to add encapsulation [dec] protocol

[dec] to interface <<CH[hex]>> ([hex]):
[chars]

Forwarder was not able to add this

encapsulation to the forwarder interface.
This will effect the traffic of this protocol
type going to/from fabric.

Error checkpointing data. This will not

affect present service but forwarding of
CPU bound traffic from this interface may
be affected on fwd_driver_partner process
restart. Ifh = [hex], port num = [dec], error
= [chars]

FWD encountered an error while

checkpointing interface info. While this will
not affect present service, it will affect CPU
bound fwding if partner process restarts.

fwd: fatal error encountered,

reason=[chars], error=[chars]

FWD Driver partner encountered a fatal

error and is not able to recover from the
error.

fwd: invalid option <[chars]> passed to

fwd server

Startup option supplied to FWD is not valid.

fwd: this function <[chars]> is not yet

implemented

FWD, a function was not implemented.

Response to IM Notfn [chars] failed for

interface <<CH[hex]>> ([hex]), caps
[dec], proto [dec] with error [chars]

Forwarder was not able to reply to IFMGR

notification. Based on the type of
notification the traffic flowing through
forwarder interface might or might not be
affected.

All retries now complete. Forwarder and

NetIO are in sync.

All queued retries from forwarder to its

NetIO DLL have been completed
successfully. The two are now in sync and
all slow-path forwarding should be
operational.

[unsigned int] failures encountered (first

error: [chars]) sending specify plim
interface information to Forwarder NetIO
DLL. Enqueuing retries

The forwarder NetIO DLL returned errors

when sent a bulk of specify plim interface
information, most likely because the
interface is not yet in NetIO. A retry has
been enqueued.

Batched config restore failed on node

[chars] due to error: [chars].

Configuration could not be restored on

some interfaces after they were created.

Config restore failed on interface [chars] on Configuration could not be restored on this
node [chars] due to error: [chars].
interface after the interface was created.

Config save failed on node [chars] due to

error: [chars].

Configuration for a batch of interfaces

could not be saved prior to the interfaces
being deleted.

Config save failed on interface [chars] on

node [chars] due to error: [chars].

Configuration could not be saved for this

interface prior to the interface being
deleted.

Already exists error received from IM for

interface [hex]

A caps add or interface create was

attempted for a resource that already
exists.

Infra error [chars] ([chars])

This error is an internal infra error and

when critical is handled accordingly in the
code. The context of the error is provided
in the actual code where this error is used.
Some of the error conditions that are
encountered under this is bind failure, attr
query failure, set/get failures, etc. If this
error is seen persistently initiate the
recommended action.

ftruncate failed([chars])

Platform PFI was unable to truncate the file.

The returned err code should indicate the
reason for the failure of the api. This is
likely due to a transient condition on the
system. The client calling this api could
retry it or handle it accordingly. If the issue
is seen persistently, initiate the
recommended action.

mmap failed([chars])

Memory map api failure in Platform PFI api.

The returned error code should indicate the
reason for the failure of the api. This is a
transient error in the system likely due to
low mem condition etc. The impact to
system is minimal except that some global
counters are not set. The client calling this
api could retry it or handle it accordingly. If
the issue is seen persistently, initiate the
recommended action.

shm_open failed([chars])

Platform PFI was unable to setup shared

memory due to failure in shared mem
open. The returned err code should
indicate the reason for the failure of the
api. This is a transient error in the system
likely due to low mem condition etc. The
impact to system is minimal except that a
few counters dont get set. The client
logging this error should retry the api
and/or handle this error accordingly. If this
error is seen persistently, Initiate the
recommended action.

Failed fabric type check in <<CH[hex]>>.

L2 Fabric may fail: [chars]

Whilst attempting to determine whether an

interface is configured as L2 Fabric, an
unexpected error was encountered. If the
interface is configured as L2 Fabric, it may
not operate correctly in some networks.

Invalid SDACP message received on

interface <<CH[hex]>>.

A SDACP discovery message was received

on the interface, but was malformed and
could not be decoded.

There has been a mis-wiring or

misbehaving satellite connected over the
specified interface - the MAC from which
the Satellite is reciving SDACP discovery
Uni-directional link detected to satellite
packets is not the MAC address on which
[unsigned int] on interface <<CH[hex]>>. this host is sending them.

Corrupt checkpoint data found. Deleting

and restarting.

Corrupt persistent data was encountered

during a process restart. The data will be
deleted and the process restarted
automatically.

An authentication failure occurred on

satellite [unsigned int] because [chars].

The information provided by the satellite

does not match the configured information.
Examine the error message for the specific
error.

Failed authentication attempt on satellite

[dec] from \'[chars]\'

This indicates that a user has attempted to

log into the specified satellite and failed
authentication.

Satellite [dec] failed to set the specified

password: '[chars]'

The satellite failed to set the password

requested. This may result in inability to
connect to the satellite via telnet.

Satellite [unsigned int] [chars]

The satellite has not been discovered on

one or more links, or the control session to
the satellite has never been established.

Control session to satellite disconnected

while image transfer was in progress. Run
Satellite [unsigned int] disconnected while 'show nv satellite protocol control' for more
transferring an image.
information.
Satellite [unsigned int] is running
incompatible software version. Starting
auto-upgrade (operation: [unsigned int]).

This satellite is running an incompatible

software version.

Image install completed on Satellite

[unsigned int]

Image install requested on this satellite has

completed. Run 'show nv satellite status'
for more information.

Satellite [dec] successfully authenticated

user from \'[chars]\'

This indicates that a user has successfully

logged into the specified satellite.

Image transfer completed on Satellite

[unsigned int]

Image transfer requested on this satellite

has completed. Run 'show nv satellite
status' for more information.

Satellite [unsigned int] is running

incompatible software and cannot be autoupgraded due to an existing install
operation in progress. Please perform a
This satellite is running an incompatible
manual install once this has completed
software version.
Satellite [unsigned int] is running a
software version which is not current

This satellite is running a software version

which is compatible, but not current.

The satellite with the specified ID has

Satellite [unsigned int] Rejected the
rejected the crosslink configuration applied
crosslink configuration on interface [chars] to the specified ICL.
The configuration conflict status for a
Satellite Interface [chars] [chars] on [chars] satellite access port interface has changed.

An ICCP redundancy group which is being

used for satellite multi-chassis redundancy
Redundancy-group [unsigned int] could not could not be synchronized due to the error
be synchronized: [chars].
stated.
Redundancy-group [unsigned int] has been An ICCP redundancy group which is being
given multiple members: [unsigned int]
used for satellite multi-chassis redundancy
and [unsigned int].
has been given multiple members.

Encap change for [chars] [chars] [chars]

failed(error [chars])

The code has hit an error situation while

applying/removing encapsulation config.
This may be caused by lack of memory,
sysdb error, invalid arguments or some
internal error for which there is no current
handling, therefore the system may now be
out of sync.

Process initialization failed while applying

encapsulation config, for which there is no
Process initialization failed. [chars] : [chars] current handling, therefore the system may
([hex])
now be out of sync.

Event Manager creation failed while

applying encapsulation config. This could
Process initialization failed. Failed to create be due to memory allocation failure or
Event Manager: [chars] ([hex])
message channel creation failure.

Process failed to creat a connection to

Interface Manager while applying
encapsulation config. This could be due to
invalid or corrupt arguments being passed
or memory allocation failure for which
Process initialization failed. Failed to create there is no current handling, therefore the
a connection to ifmgr: [chars] ([hex])
system may now be out of sync.

Process failed to connect to Interface

Manager while applying encapsulation
config. This could be due to invalid
connection context for which there is no
Process initialization failed. Failed to open a current handling, therefore the system may
connection to ifmgr: [chars] ([hex])
now be out of sync.

Process initialization failed. Memory

allocation error: [chars] ([hex])

Memory allocation failed while applying

encapsulation config. This failure is due to
exhaustion of system memory resources.

Process failed to bind to SysDB while

applying encapsulation config. This could
be due to invalid arguments, invalid path
or an internal error for which there is no
Process initialization failed. Failed to bind to current handling, therefore the system may
SysDB: [chars] ([hex])
now be out of sync.

Process initialization failed. Failed to

register for SysDB verification: [chars]
([hex])

Process failed to register for SysDB

verification while applying encapsulation
config. This could be due to the invalid
arguments or memory allocation failure for
which there is no current handling,
therefore system may now be out of sync.

The code failed to create sysdb item while

applying encapsulation config. This may be
caused due to invalid arguments for which
there is no current handling for the same,
Unpack for sysdb CREATE_SET event failed therefore the system may now be out of
for [chars] (error [chars])
sync.

Unpack for sysdb DELETE event failed for

[chars] (error [chars])

The code failed to delete sysdb item while

removing encapsulation config. This may
be caused due to invalid arguments for
which there is no current handling for the
same, therefore the system may now be
out of sync.

Sysdb [chars] for [chars] failed(error

[chars])

The code has hit a sysdb error situation

while applying encapsulation config, for
which there is no current handling,
therefore the system may now be out of
sync.

Unpack for sysdb SET event failed for

[chars] (error [chars])

The code failed to set a sysdb item while

applying encapsulation config. This may be
caused due to invalid arguments for which
there is no current handling for the same,
therefore the system may now be out of
sync.

Implicit remove: Intf [hex] ([chars]) caps

[unsigned int], proto [unsigned int] (views
[hex])

IM has implicitly removed some caps nodes

as part of an interface delete. These caps
nodes should have been removed prior to
the interface delete.

Process initialisation failed. [chars]: [chars] There was a software error during process
([hex])
startup.

Ifmgr unintentionally converted a larger

type into a smaller one

IM converted a type of size_t into either a

uint32_t and uint16_t, when it expected the
value in the size_t variable to be small
enough to fit into the new variable type.
However, the conversion caused the value
to change, indicating that some data was
lost. This is likely to leave the system in an
inconsistent state.

Failed to find [chars] rule for ID [unsigned

int]

IM is unable to create an interface/caps

due to static information about the
resource type being missing. The system
may be in an inconsistent state.

The ma-feature or ea-feature property was

set twice within a rule. This property may
have been set implicitly by the feature or
owner-string properties. feature and ownerstring are synonyms which set both the
Error: Feature string already set in rules file ma-feature and ea-feature properties.
[chars]
Please check the rules file.

Error: Duplicate ID [dec] found in rules file

[chars]

Multiple rules with the same static id were

found in rules files. Every rule should have
exactly one static id assigned to it.

Error: ID not found in the rules file [chars]

A rule with no static id is found in rules file.

Every rule should have a static id assigned
to it.

Error: The rules file [chars] could not be

parsed. First error on line [dec]

The rules file cold not be parsed. Please

check the rules file.

[chars] caps is not allowed on interface

type [unsigned int] (allowed caps =
[chars]) ([chars])

The current operation failed because the

capsulation is not allowed on this interface.

[chars]: [chars]

An IM client has used the IM API in an

unexpected way, usually implying a bug in
the client code.

Dropping message from node [chars]

([hex]) due to '[chars]'. Message version is
[hex], whilst expected version is [hex].
[unsigned int] messages dropped in total
for this reason.

A message received from the Interface

Manager on a different node has been
dropped. This is due to incompatible
versions of the software communicating
with each other and will result in interfaces
not working correctly.

Unexpected error received in reply: code:

[hex] (msgno = [unsigned int], sparts =
[unsigned int] rparts = [unsigned int])

This is a temporary ios_msg to identify

when an unexpected error is returned when
communicating with the IM server.

Maximum packet size out of range for

interface <<CH[hex]>>. Maximum MTU
[unsigned int], requested maximum
packet-size [unsigned int].

The maximum packet size requested on an

interface is outside its operational range.
This may result in traffic loss on the
interface.

MTU out of range for interface

<<CH[hex]>>, protocol [unsigned int],
encapsulation [unsigned int]. Minimum
MTU [unsigned int], maximum MTU
[unsigned int], actual MTU [unsigned int].

The MTU on an interface or encapsulation

is outside its operational range. This may
result in traffic loss on the interface.

An IM notification failed to be delivered to

one of its clients. The most likely reason for
[chars] notification failed to be delivered to this is an out-of-memory condition. This will
client: [chars]
have left that client out-of-sync with IM.
Implicit download of [unsigned int]
interfaces has completed

A previously stuck or failing implicit

download has now successfully completed.

After [unsigned int] minutes of retries,

implicit download of [unsigned int]
interfaces is still failing (first intf
<<CH[hex]>>, error: [chars])

An error was repeatedly encountered while

attempting to replicate the dataplane of an
interface to a node to which it implicitly
required replication (e.g. due to wildcard
replication being used, and a new node
coming up later). This may cause
forwarding on this interface (via this node)
to be broken.

After [unsigned int] minutes, implicit

download of [unsigned int] interfaces has
still not completed

An attempt to replicate the dataplane of an

interface to a node to which it implicitly
required replication (e.g. due to wildcard
replication being used, and a new node
coming up later) has taken an
exceptionally long time. This may cause
forwarding on this interface (via this node)
to be broken.

Ignoring unexpected pulse with code

[unsigned int], value [hex]

This error message indicates that a pulse

has been delivered to the event manager
in the IM client library which was intended
for someone else. This is almost certainly
harmless in this case since IM has detected
and ignored the event.

Failure registering for mutex revival

IM was unable to perform a system

operation that it expects to succeed. IM will
exit and restart in an effort to help clear
the condition.

IM was unable to allocate the memory it

needed - indicating the system is in a very
low-memory condition, which should be
Ifmgr was unable to allocate memory for an recovered by wdsysmon automatically. IM
operation. Ifmgr will exit and restart to
will exit and restart in an effort to help
attempt to clear this condition
clear the low memory condition

[chars] operation from callback [hex]

received for interface <<CH[hex]>> that
has not been created.

A client performed an operation on an

interface that is in the progress of being
created. In general, the interface handle for
the interface being created is not published
until the interface create has completed.
The most likely reason for this log is that
the client is using a stale interface handle
(for example, from before a linecard OIR).
An IM_ERROR_NOTFOUND error is returned
to the client.

Ifmgr encountered an unexpected error

calling '[chars]': [chars] ([dec]). [chars]

IM was unable to perform a system

operation that it expects to succeed. IM
may exit and restart in an effort to help
clear the condition.

IFO EA PD Interface create function called

for [unsigned int] interfaces

PD Stub DLL called

IFO EA PD Interface delete function called

for [unsigned int] interfaces

PD Stub DLL called

IFO EA PD Interface update function called

for [unsigned int] interfaces. First intf has
changed flags [hex]
PD Stub DLL called

The IFO EA platform DLL returned an error

handling a interface update for an
underlying interface removal operation on
interface <<CH[hex]>>([hex]): [chars].
This interface may no longer correctly
operate.

During the handling of a bundle member

update notification, the platform returned
an error which cannot be handled. The
interface may continue trying to send
traffic over an interface which it should no
longer be using, resulting in traffic drops.

[chars]: could not create connection

structure for the connection to [chars]:
[chars]

Internal error

[chars]: could not set notify handler for

connection opens and errors to [chars] :
[chars]

Internal error

[chars]: opening all connections of Event

Manager failed: [chars]

Internal error

[chars]: Internal error: [chars]: [chars]

An internal software error occurred.

[chars]: sysmgr_proc_ready failed: [chars]

Internal error

[chars]: Timer creation failed: [chars]

Internal error

[chars]: bag register error is detected;

[chars].

Internal error

[chars]: Debug initialization for the

im/imaedm/[chars] event failed: [chars]

An error was returned when the IM

Attribute EDM server called the
debug_init_event() function.

An error was returned when the IM

[chars]: Debug registration for IM Attribute Attribute EDM server called the
EDM server failed: [chars]
debug_register() function.

[chars]: Failed to open EDM connections

(retries [unsigned int][chars]). Turn on
debug imaedm errors to diagnose failure.

The opening of EDM connections has failed

repeatedly.

[chars]: event_manager_create failed;

[chars]

The event_manager_create function

reported an error trying to initialize the
event manager.

Received duplicate successful replies for

interface [hex], attribute type [chars]

The attribute client has received duplicate

successful responses for this attribute on
this interface. This would suggest that
multiple attribute owners have been
configured for this (interface, attribute)
pair.

A bulked notification message failed to be

sent: [chars]

The attribute owner library has failed to

send a bulk notification message to the
attribute clients. However, the attribute
owner that produced these notifications is
not aware that they failed to be sent. This
could result in the attribute clients being
out of sync with this owner.

The attribute owner library has failed to

reply to the client to inform it that a set or
clear operation has succeeded. This could
At least 1 item in a bulk set/clear operation result in the client being out of sync with
succeeded, but the client cannot be
the owner. This may be caused by a
informed due to an error: [chars]
transport drop.

Received an asynchronous message from

an unknown source which has been
dropped (pulse code [hex], request
0x[pointer])

The attribute client or owner has received a

pulse which is not expected, and cannot be
handled. This message has been dropped.
If no other problems are seen then the
error can be considered harmless.

Initialisation Failed. Task: '[chars]' Error:

'[chars]'

The process failed to initialise and will exit.

Line protocol on Interface [chars],

dampening state changed to [chars]

The interface line protocol dampening state

changed. When the state is 'suppressed'
the interface will be held down. In
'unsuppressed' state, link state changes
are allowed to occur as normal.

Line protocol on Interface [chars], changed The data link level line protocol changed
state to [chars]
state.

The interface hardware went either up or

Interface [chars], changed state to [chars] down.
[chars] is administratively down
[chars] is not running BERT

Unable to start BERT because controller in

admin down state
Trying to stop BERT when not running

[chars] is already running BERT

[chars] could not start BERT
[chars] [chars]

Restarting a running BERT is not allowed

BERT could not be started
The bert status of the link

Interface [chars], changed state to [chars] The interface has changed state.

Interface [chars], dampening state

changed to [chars]

The interface dampening state changed.

When the state is 'suppressed' the
interface will be held down. In
'unsuppressed' state, link state changes
are allowed to occur as normal.

Unrecoverable error in FGID resource

managing infrastructure : [chars]

A internal error was detected while using

Fabric Multicast Group Indentifier(FGID)
resource managing infrastructure APIs.

NetIO debugging partner initialization

failed: [chars] (Err=[chars])

The NetIO debugging partner process

initialization failed. This could happen due
to errors in various server processes. The
error code and its text in the message will
reveal the source of the error.

Couldn't install the default handler for

async messages, err: [chars]

The NetIO debugging partner process

couldn't install the default event handler
for async messages.

Couldn't block while waiting for events:

[chars]

The NetIO debugging partner process failed

to wait for events to be delivered.

This error indicates that a code sanity

check has failed. This indicates the size of
the global HSSD area defined in Pakman
'[chars]' HSSD area size [unsigned int] not does not match the size that NetIO is
equal to expected size [unsigned int]
expecting.

Global HSSD area '[chars]' not known to

NetIO

This error indicates that a code sanity

check has failed. This indicates a new
global HSSD area was added to Pakman
without adding the appropriate endian
transform code to NetIO.

NetIO DLL attempted to use a bad chain

A NetIO feature DLL has attempted to pass
node (magic number [hex]) in packet punt a bad chain node to a NetIO packet punt
to [chars]
API. The packet has been dropped.

Error: NetIO received a request to delete

the Forwarder Interface

Interface Manager has requested NetIO to

delete the Forwarder Interface. This should
not occur - the system assumes the
Forwarder Interface is never deleted.

Failed to load DLL for caps [chars]

([unsigned int]), error: [chars]

An error occurred while auto-loading a caps

DLL. If this message is repeatedly seen
then the software packet path on this node
may be broken.

[chars], [chars], [pointer]

ARP netio error.

[chars] : Failed to initialize ipv4 proto for

[chars] with error ([chars])

netio initialization error.

[chars] : Failed for ipv4 proto to [chars]

([chars])

netio media register or callback error.

ltrace_init failed for '[chars]': [chars]

Netio ltrace facility failed to initlize one of

the trace buffers. The Netio trace
information will not be available.

A NetIO DLL invoked API '[chars]' before

callbacks table initialized

A statically linked NetIO DLL has invoked a

NetIO API before the callbacks table has
been initialized

[chars] : Failed to acquire pak netio mutex

lock ([chars])
ARP netio error.

An error occurred while processing a resync

An error occurred during a synchronization from Interface Manager. If this message is
with Interface Manager: Failed to [chars],
repeatedly seen then the software packet
error: [chars]
path on this node may be broken.

Cannot allocate memory in <[chars]>

Internal error. System is out of memory malloc failed.

netio script failed: <[chars]>

An error occurred during netio script

processing. Please check the error
message for more details.

NetIO was attempting a hitless upgrade of

a DLL that was part of a SMU/PIE. A step
during this operation encountered this
error. Netio may or may not be able to
[chars] failed during self managed upgrade perform the DLL upgrade successfully
of DLL/SMU, Error: [chars]
when this error is encountered.

Shared memory initialization for stats failed IP Netio library encountered failure while
- [chars]
operating on the shm stats information.

NetIO received a packet with no data

particle in it, packet: 0x[pointer], packet
PID: [dec]

NetIO received a bad packet from the

driver (or from an application) that had no
particle data in it. NetIO drops these
packets. If too many such packets
belonging to a routing protocol are
received and dropped, we have a potential
possibility of an adjancency flap.

Failed to input the packet for [chars]

([chars])

This message indicates that the ARP packet

queue is filling up faster than ARP can
process the packets. It could be due to
many addresses needing to be resolved on
initial bring up. In this case packet drops
are not a problem. Addresses will resolved
as quick as possible and the condition will
clear. If seen for a while then could imply
some potential problem.

script [chars]([dec]): [chars]

An internal syntax error was detected in

the script file. The current line was skipped
and the execution of the script continued.

NetIO gets restarted if a NetIO DLL fails to

process an install event. This should not
NetIO DLL registration '[chars]' failed to
cause any problems to the router and
handle install event for DLL '[chars]'. NetIO NetIO should come back up fine after
will be restarted
restart.

NetIO DLL < [chars] > is being upgraded.

NetIO will be restarted

NetIO gets restarted whenever we upgrade

a DLL that does not support NetIO DLL
upgrade. This should not cause any
problems to the router and NetIO should
come back up fine after restart.

NetIO is upgrading([chars]) the dll [chars]

Netio is upgrading this dll. This is here only

for informational purpose only. No further
action is recommended/needed.

packet mutex [chars] failed : [chars]

NetIO was unable lock/unlock the packet

mutex. This could lead to certain cases
when the same packet is used

create idb error: interface ifhandle [hex]

already in datastore with name [chars],
new name [chars]

Netio already has this IDB in its datastore.

It is getting a request for create for the
same interface handle but with a different
name. This could possibly cause issues
with this interface in NetIO.

delete idb: interface (ifhandle = [hex],

name [chars]) has [unsigned int]
subinterfaces associated with it and cannot
be deleted. Error: [chars]

NetIO cannot delete a interface which still

have subinterfaces under it. This could
potentially cause issues with recreate of
any interface, if the same interface handle
is reused.

delete idb: interface (ifhandle = [hex],

name [chars]) having subinterfaces
(demux index: [dec], ifh [hex], name
[chars]) cannot be deleted. Error: [chars]

NetIO cannot delete a interface which still

have subinterfaces under it. This could
potentially cause issues with recreate of
any interface, if the same interface handle
is reused.

[chars] Failed, Error: [chars]

NetIO process has problem initializing its

database and attempts to restart in an
attempt to recover from the error.

A packet was dropped in hardware due to

bad programming or a hardware error. This
packet dropped in hw due to programming is a raw dump of the packet to aid in
error: pkt type [hex] pkt: [chars]
debugging.

[chars]

An error occurred during packet debug

events initilization. Refer to the error
message for the particular cause.

Attempt to lock packet mutex from

disallowed thread

An attempt was made to lock the packet

mutex from a thread where mutex locking
is disallowed

Client with pid [dec] tried to access packet

[pointer] owned by process with jid [dec]
The identified client attempted to access a
(pid [dec])
packet that does not belong to it.

Client with pid [dec] tried to access freed

packet [pointer] (pak pid [dec])

The identified client attempted to access a

freed packet.

Client with pid [dec] tried to access packet

[pointer] owned by queue with id [hex]
The identified client attempted to access a
(pak pid [dec])
packet that does not belong to it.

When getting packet header, particle list

on returned packet non-NULL ([pointer]).
Packet last owned by [unsigned int]

A packet header on the free list had a nonNULL particle list.

packet exception, reason: [chars], data:

0x[pointer]

An software exception had occurred in the

packet manager library. The client process
terminated with exit code -1. The reason is
that the client passed an invalid packet to
packet manager library and led to the
exception.

Failed to get node name

The Packet manager library was unable to

retrieve the nodename for the
node/linecard.

__spp_trymap: [chars]

The vector packet path API bind routine has

failed.

Connect to the packet server failed. Reason The platform driver was not able to connect
: [chars]
to the packet server.

The platform driver attempted to define a

Platform attempted to define a packet
packet memory region larger than is
region that was too large: Start:0x[pointer] currently supported. This will be
Size:%zd
automatically reduced to a supported size.

Send data to the packet server failed.

Reason : [chars]

The platform driver was not able to send

data to the packet manager. This could
happen when the platform driver is trying
to send the initilization information to the
packet manager.

Failed to revive the packet mutex, reason:

[chars]

The packet subsystem failed to revive the

packet mutex.

Corruption detected in the [chars] at

[pointer] owned by packet [pointer]
belonging to process [dec]

Consistency check detected corruption in

the specified area of the specified packet.
This will cause packet manager to restart.
Please report the message and value to
your technical support representative.

Packet server: line [dec], fatal

misalignment.

Packet server internal structures are

misaligned. This is a fatal programming
error. The value is a marker for tracking
down the misalignment. Please report the
message and value to your technical
support representative.

Packet server initialization failed. Reason :

[chars]

The packet subsystem was not able to

initialize properly. It will be restarted by
sysmgr and should recover.

Memory allocation failed in process [dec] at Packet server failed to allocate more
[chars]
memory.
Confirmation of the number of corrupt
[unsigned int] corrupt packets successfully packets cleared when 'clear packet corrupt'
reclaimed from the corrupt queue.
was executed.

[chars]: [chars]

Particle body corruption is detected. This

message follows a BADPAK message and
dumps the first few bytes of the particle
body and the last few bytes of the one
before.

Packet server failed to send a broadcast

message to the client. This will result in the
Failed to send broadcast message [dec] to client being unaware of an event that
client [dec], error: [chars]
occurred in the packet server.

Failed to create a channel and event

manager, error: [chars]

Packet server failed to create an event

manager and channel. Clients will be
unable to connect to packet server, and
packet server will be unable to send and
receive messages.

[chars]: [chars] check point operation

failed, reason : [chars]

A check point operation failed in packet

manager.

Chunk creation for packet headers failed

Could not allocate a chunk of memory for

the packet headers.

Conditional wait operation on [chars] in

[chars] failed; reason [chars]

The packet subsystem failed to perform a

conditional wait. This usually indicates a
programming error.

Packet server debug initialization: [chars]

failed, error [chars]

The debug support initalization failed in the

packet server. It will be restarted by sysmgr
and should recover.

Failed to remove client [dec] from clients

list at [chars]

Packet server failed to remove the

specified client from the client list queue.
This may cause the client fail to reconnect
to packet server.

Fail to insert client [dec] into the list of

clients at [chars]

Packet Server failed to insert a client into

client list queue. This will prevent the client
from connecting to packet server.

Failed to attach event handler.

The packet subsystem encountered an

error when attaching a handler for
synchronous or asynchronous events.

[chars]: fsv_register for name=[chars]

failed, error : [dec]

An automatic register for one of the FSVs

failed.

msg_chan_get_rendezvous failure: [chars]. msg_chan_get_rendezvous failed.

Failed to get client's pid at [chars]

Packet Server failed to get the client's pid.

This will prevent the client from connecting
to packet server.

[chars]: hssd_register for

name=[chars],size=[dec] failed, error :
[dec]

An automatic register for one of the HSSDs

failed.

Memory mapping for [chars] failed, reason: Memory maping for the specified area
[chars]
failed and packet server will restart.

Failed to reply to client [dec] message

[dec] at [chars]

Packet server failed to reply to a client's

request. This will result in the client getting
blocked on packet server.

Failed to initialize packet mutex, reason:

[chars]

The packet subsystem failed to initialize

the packet mutex.

Packet server registration for mutex

monitoring (revival) failed, error [chars]

Packet server failed to register for the

mutex revival and will exit. It will be
restarted by sysmgr.

Mutex [chars] operation on [chars] in

[chars] failed; reason [chars]

The packet subsystem failed to perform the

specified operation on the specified mutex.
This usually indicates a programming error.

Broadcast to clients from packet server

failed

Packet server failed to broadcast to

message to its clients that it is about to
restart.

Particle initialization failed.

Packet server was not able to initialize the

particles correctly and will restart.

qsm_add_service failure: [chars].

qsm_add_service failed.

An unexpected signal SIGALRM was

Received SIGALRM unexpectedly, ignored. received.

signal: [chars].

The packet subsystem encountered an

error while performing a signal operation.

Failed to get node state from Sysmgr:

[chars].

Packet server failed to get node state from

sysmgr.

[chars]: Failed to set thread attributes

Packet server unable to set the thread's

attributes.

Failed to create the [chars] thread

Packet server was unable to create the

specified thread.

Packet server was unable to detach from a

[chars]: Failed to detach from a new thread new thread.

[chars]: timer: [chars].

The packet subsystem encountered an

error while operating/handling a timer.

Depletion level [dec] percent for resource

[chars]

The depletion level of the specified packet

resource is catastrophic. At this level of
depletion, all services and protocols on the
specified node are not able to allocate
packets and node may not be able to
function properly unless the depletion
levels improve.

Depletion level [dec] percent for resource

[chars]

The depletion level of the specified packet

resource is critical. At this level of
depletion, routing protocols on the
impacted node are not able to allocate
packets and the software packet path will
be impacted. Critical services on the node
may not be able to allocate packets and
thus could be impacted.

An attempt has been made to free a packet

buffer that is already freed or that a buffer
that is not owned by the calling process.
This usually indicates the process using the
packet has used it after it has been
Double free detected for pak [pointer], pak returned or after it has been sent to
pid [dec], client pid [dec]
another process.

An attempt has been made to free a packet

buffer that is already freed. This usually
Particle [pointer] with [dec] refcount being indicates the process using the particle has
freed
used it after it has been returned.

Depletion level [dec] percent for resource

[chars]

The depletion level of the specified packet

resource has reached warning level. If the
depletion level does not improve then
routing protocols on the impacted node will
not be able to allocate packets and the
software packet path will be impacted. At
warning depletion level, critical services on
the node should still be able to allocate
packets and thus shouldn't be impacted.

Fragmenting pak [pointer] pak pid [dec],

client pid [dec], with header length
[unsigned int] > allocated particle size
[unsigned int], Dumping pkt: [chars]

An attempt has been made to fragment a

packet buffer with a header length that is
higher than allocated particle max size.
This usually indicates the process using
fragment apis might have miscalculated
the header length that does not fit into a
particle

Depletion level [dec] percent for resource

[chars]

Information about the current depletion

level of the specified resource. At this level
of depletion functionality should not be
impacted.

[chars] free list NULL when count shows

[unsigned int] headers free

The particle/header free list and

particle/header free count are out of sync;
probable corruption of packet memory.

[chars] [dec] [dec]

The resource depletion information in the

following format: PROCESS_NAME PID
COUNT

[hex] [dec]

The resource depletion information in the

following format: PROGRAM_COUNTER
COUNT

[chars] [chars] [chars]

The header for resource depletion

information that follows this message. It is
of the format: PROCESS_NAME PID COUNT

[chars] [chars]

The header for resource depletion

information that follows this message. It is
of the format: PROGRAM_COUNTER COUNT

Top [dec] netio DLL addresses using [chars] The info about the top netio DLL addresses
(netio PID [dec]):
using the specified resource.

Only [dec] netio DLL locations found using The info about the total number of users of
[chars].
the specified resource.
[chars]

The traceback info about caller

Top [dec] users of [chars]:

The info about the top users of the

specified resource.

Only [dec] users found using [chars].

The info about the total number of users of

the specified resource.

The FINT idb is not yet created in netio.

Failed to obtain netio idb for FINT interface This could be a transient condition.

Failed to obtain my node id [chars]

Unable to determine my node id using

platform api.

[chars] ([chars])

Platform PFI was unable to set globals

bacause of some shared memory issues.

The FINT idb is not yet created in netio.

Failed to obtain netio idb for FINT interface This could be a transient condition.

Failed to obtain my node id [chars]

Unable to determine my node id using

platform api.

Lookup for ppindex([dec]), pp_proto([dec]), Unable to get the adjacency and next hop
failed due to [chars]
information from given ppindex.

Failed to get the logical port for the

specified interface from the Platform Mgr.
Failed to get logical port for ifhandle=[hex], This will cause the interface to not get
[chars]
created properly.

[chars], [chars]

An error was encountered. A reason text

will be supplied in the message

The FINT idb is not yet created in netio.

Failed to obtain netio idb for FINT interface This could be a transient condition.

Failed to obtain my node id [chars]

Unable to determine my node id using

platform api.

Could not map handle [hex] to slot

The interface handle cannot be mapped to

a slot on the card.

Failed to initialise [chars]

An error occured when a module was going

to be initialised. This may cause the
process to terminate.

The FINT idb is not yet created in netio.

Failed to obtain netio idb for FINT interface This could be a transient condition.

Failed to obtain my node id [chars]

Unable to determine my node id using

platform api.

Taildrop on [chars] queue [dec] owned by

[chars] ([chars]=[dec])

A producer process was unable to produce

into a software queue because the queue
was full. This typically means that the
owning process is blocked or CPU is under
heavy stress.

Build-up detected on [chars] queue [dec]

owned by [chars] ([chars]=[dec])

The amount of work queued into a software

queue has crossed the high threshold
(three-fourths of the queue size). This
typically means that the owning process is
blocked or CPU is under heavy stress and,
hence, the owner process is unable to
process the queued work items.

Build-up cleared on [chars] queue [dec]

owned by [chars] ([chars]=[dec])

Informational message to indicate that a

queue build-up has cleared up. This
message coupled with the corresponding
queue build-up message can give an
indication of how long the queue build-up
condition lasted.

Internal error: [chars]

An internal error occurred in IPv6 Prefix

Compression library involves exiting the
process. After the associated process
restarts, the error should have been
cleared. *DDTS*

IPv6 compression anchor prefixes are

changed. A linecard reload is needed to
make this change effective Existing anchor
prefix length [dec] [dec] [dec] [dec] [dec]
[dec] [dec] [dec] [dec] [dec] [dec] [dec]
[dec] [dec] [dec] [dec] [dec] [dec] [dec]
[dec]. Pending anchor prefix length [dec]
[dec] [dec] [dec] [dec] [dec] [dec] [dec]
[dec] [dec] [dec] [dec] [dec] [dec] [dec]
[dec] [dec] [dec] [dec] [dec]

The IPv6 compression anchor prefixes are

changed. The linecard needs to be reloaed
to make the changes effective. This is not
an error message or condition.

V6 source prefix compression failed due to

lack of extended path. This failure indicates
that a particular v6 prefix indicated in the
message will not be compressed. There are
3 workarounds of this problem. 1) do not
use this entry. 2) change the prefix length.
3) change the prefix value. For example if
an entry failed. 4) use the compression
anchor prefix cli controller sse tcam
location R/S/I compression ipv6 anchorprefix to configure the common IPv6 prefix
lengths during an ACL programming then
try removing that ACE indicated in the
message and apply the configuration
v6 source prefix compression failed: [chars] again. *DDTS*

PFI Protect debugging initialization failed:

[chars] (Err=[chars])

The PFI Protect debugging initialization

failed. The error code and its text in the
message will reveal the source of the error.

Trigger Handle [unsigned int] :[hex]

The PFI Protect infrastructure is dumping

handles for debug purposes.

Client jid:[dec] nodeid:[hex]

The PFI Protect infrasturcture is dumping

handles for the client and node given.

Dumping handles...

The PFI Protect infrastructure is about to

output a list of handles for debug purposes.

The Prescision Time Protocol (PTP) received

a packet with an unknown protocol
encapsulation and dropped it. This may
have been an incorrectly encapsulated PTP
packet, in which case PTP may operate
incorrectly, or a misdirected packet for
Dropped a packet for an unknown protocol. another protocol, in which case other
Supported protocols are [chars]
protocols may operate incorrectly.

Dropped a statistics notification for PTP

An error was encountered while attempting

to deliver statistics to the Prescision Time
Protocol (PTP) protocol. This is a transient
problem from which the system should
recover, but some PTP statistics may be
incorrect. This may indicate the system is
under unusuallay high traffic load.

[chars]

An emergency error has been detected.

[chars]

An alert error has been detected.

An error was enountered when attempting

to alert a packet- processing client of
packets that have been delivered to it for
Failed to notify packet-processing client
processing, and repeated retries have not
(PID [dec]) of received packets, and unable resolved the problem. No further retries will
to recover after repeated retries
be attempted.

[chars]

A critical error has been detected.

Failed to allocate block in SPP shared

memory window. Error [chars]

SPP or one of its clients was unable to

allocate a block in the SPP shared memory
window. This indicates that either system
resources are low, or that there is an
internal problem with SPP or the shared
memory infrastructure. It is likely that both
ingress and egress packets will be dropped.

Packet-processing client failed to perform

[chars] operation.

An error was encountered while trying to

perform an operation on a lock. The
process will continue without retrying the
operation. In most cases, no further
adverse behaviour should be observed.

Failed to notify packet-processing client

(PID [dec]) of received packets

An error was enountered when attempting

to alert a packet- processing client of
packets that have been delivered to it for
processing. The system will retry to
attempt to recover.

[chars]

An error has been detected.

An interrupt pulse was received by SPP

from the OS, but no handler was registered
to take appropriate action. This indicates a
problem in an SPP plug-in, which has
registered for receiving the interrupt, but
has not registered a corresponding handler.
No handler registered for interrupt [dec], ID It is likely that ingress packets will be
[dec]
dropped.

A pulse was received by SPP from the OS or

another process, but no handler was
registered to take appropriate action. This
indicates a problem with SPP if the pulse
Unexpected pulse [dec] received by thread was received from the OS, or another
[dec] with value [hex]
process which sent the unexpected pulse.

Failed to initialize [chars]: [chars]%s

An error was encountered while the

specified process was initializing. The error
message contains details about the source
of the error.

Failed to register to monitor shared

memory [chars] mutex. Error: [chars]

SPP or one of its clients was unable to

register to monitor a shared memory
mutex. This indicates that either system
resources are low, or that there is an
internal problem with SPP or the shared
memory infrastructure. Restarting SPP or
its client processes may result in memory
leaks.

A packet client was unable to allocate the

required number of packets for
transmission because no more packets are
available. This may be a transient issue, if
the system is under unusually heavy load,
Failed to allocate [unsigned int] packets for or if the situation persists it may indicate a
sending
packet client problem.

Failed to load packet processing driver

[chars]

An error was encountered while trying to

load an SPP plugin library. The plugin will
not be used. Packets may not be sent or
received correctly for the affected location.

SPP failed to initialize its periodic 1Hz

timer, which is used to ensure that rollover
Failed to initialize 1Hz timer used to handle of the system timestamp is handled
rollover of the system timestamp clock.
correctly. It is likely that times reported by
Some SPP show commands may show
the following show commands will be
incorrect timings. Error: [chars]
incorrect as a result: - show spp node

[chars]

A warning codition has been detected.

[chars]

A condition worthy of note has been

detected.

[chars]

An informational message.

[chars]

An informational message.

[chars]

A debug message.

Either the active or standby Service State

Controller for the location given in the
message provided the Adjacency Manager
with corrupt data. This most likely indicates
The SVI Adjacency Manager was provided a bug in the Service State Controller logic.
with corrupt adjacency data for [chars] SSC No adjacencies will be installed for the
belonging to service [chars] on location
named service, so no traffic will be
[chars]
forwarded to or from it.

The SVI Adjacency Manager was provided

with conflicting settings for installing
adjacencies for interface [hex]

Conflicting 'follow standby' instructions

were supplied to the Adjacency Manager
for an interface. 'Follow standby' is
specified for an interface by a Service State
Controller if it believes that traffic should
be directed towards the standby, rather
than active, service instance. This message
indicates that the active and standby
Service State Controllers gave conflicting
information about where traffic to be
directed to. This indicates an inconsistency
between the system state as viewed by the
Service State Controllers that are
responsible for the service to which the
interface belongs. Restarting those
processes may help, after allowing any
other problems that could lead to
inconsistencies being resolved. No
adjacencies will be installed for the
interface, and all traffic to it will be
dropped.

Initialization failed, module: [chars],

operation: [chars], error: [chars]

The SVI Adjacency Manager Library's

initialization has failed. The process will
exit and automatically restart.

An error occurred while setting up

adjacencies for service '[chars]': [chars]

The SVII Adjacency Manager encountered

an error while preparing to set up
adjacencies for the specified service. It is
likely that packets will not be forwarded to
interfaces for that service. This may be
caused by a lack of resources or other
system problems. Restarting the
'svi_adj_mgr' process on the affected node
(after any other problems have been
cleared up) will restore adjacencies for the
affected service.

An inconsistency has been found in the

adjacency manager interface database.
The adjacency manager will automatically
An inconsistency has been found in the
recover from this; nevertheless it may
interface database (interface handle [hex]) indicate a software error.

An error occurred while requesting

adjacency refresh for service '[chars]':
[chars]

The SVII Adjacency Manager encountered

an error while resynchronising its
adjacencies. The adjacencies for the
specified service may not be correctly set
up on the specified card, meaning that
traffic for that service arriving at that card
may not be forwarded correctly.

An error occurred while trying to restart

cleanly: [chars]

The SVII Adjacency Manager encountered

an error while preparing to restart itself. It
will restart itself anyway, but there may be
other errors.

The Service Director process/library sent an

invalid message to the SVII Adjacency
Manager. This indicates a problem with the
The Service Director library passed invalid Service Director. It is likely that packets will
parameters to the SVII Adjacency Manager not be correctly forwarded to some Service
process.
Virtual Interfaces.

A Service owner tried to revoke a request

for adjacencies to be managed by the SVI
Adjacency Manager. It is likely that the
originally published request has not been
The SVI Adjacency Manager 'publish' library cleaned up correctly. This should not have
encountered an error when trying to clean any adverse effects, other than the use of
up after a service unregistered. Error
some additional resouces, but probably
[chars]
indicates some kind of programming error.

An error occurred while trying to program

an adjacency: [chars] (interface
handle=[hex])

The SVII Adjacency Manager encountered

an error while programming an adjacency.
Packets may not be forwarded to the
affected service interface. The name of the
interface can be retrieved with 'show im
chains ifhandle 0xabc', where '0xabc' is the
interface handle shown in the message.

An error occurred while trying to recover

from a previous failure: [chars]

The SVII Adjacency Manager encountered

an error while calling AIB. Normally, it
would recover from this error. However, a
secondary failure has occurred while
invoking the recovery mechanism. After
this error, packets may not be forwarded
correctly for some service virtual
interfaces.

Initialization failed, module: [chars],

operation: [chars], error: [chars]

The SVI Adjacency Manager's initialization

has failed. The process will exit and
automatically restart.

Event Loop failed, error: [chars]

The SVII Adjacency Manager encountered

an error while waiting for an event. This
should not ordinarily happen, but may
indicate a temporary glitch that will
automatically recover. If it occurs very
frequently it may be necessary to restart
the SVII Adjacency Manager process.

An error occurred whilst processing a

'[chars]' message from a client, during
operation [chars]: [chars]

The process encountered an error while

trying to handle a message from a Service
on a line card. If this happens frequently,
then restarting the process that caused the
error may fix the problem. It may indicate
that the card is low on memory.

The process was initialized successfully but

Failure communicating readiness to System was unable to inform System Manager of
Manager. Error: [chars]
the success.

A failure occured while re-syncing state

with AIB after a restart: [chars]

After a restart, the adjacency manager

attempts to re-sync its state with AIB. A
failure occurred during this process. This
could result in adjacencies being
erroneously deleted in AIB, and hence
forwarding could be interrupted.

Error registration failed ([chars]) - some

messages may not be displayed correctly

The SVI Adjacency Manager encountered

an error while registering its error
messages. Some error messages may be
displayed numerically rather than with full
messages. No other problems will be
caused by this failure.

Protocols may not operate correctly

An error was encountered while attempting

to set up protocol sessions. Affected
protocols may operate incorrectly or not at
all.

Internal error: [chars]

An internal error occurred in TCAM Manager

which involves exiting the process. After
the TCAM Manager process restarts, the
error should have been cleared. *DDTS*

V6 source prefix compression failed due to

lack of extended path. This failure indicates
that a particular v6 prefix indicated in the
message will not be compressed. There are
3 workarounds of this problem. 1) do not
use this entry. 2) change the prefix length.
3) change the prefix value. For example if
an entry failed. 4) use the compression
anchor prefix cli controller pse tcam
location R/S/I compression ipv6 anchorprefix to configure the common IPv6 prefix
lengths during an ACL programming then
try removing that ACE indicated in the
message and apply the configuration
v6 source prefix compression failed: [chars] again. *DDTS*

TCAM Manager re-initializes its internal

data. Process [chars], Number of respawn
[dec]

'Typically this indicates an error condition, '

'such as tcam mgr crashes while internal
dats are updated. ' 'and leave the internal
data in an inconsistent state ' 'To recover
from the error, ' 'TCAM Manager has to
reset its internal data.'

Internal error: [chars]: [chars]

An internal error occurred in TCAM Manager

which involves exiting the process. After
the TCAM Manager process restarts, the
error should have been cleared.

IPv6 compression anchor prefixes are

changed. A linecard reload is needed to
make this change effective Existing anchor
prefix length [dec] [dec] [dec] [dec] [dec]
[dec] [dec] [dec] [dec] [dec] [dec] [dec]
[dec] [dec] [dec] [dec] [dec] [dec] [dec]
[dec]. Pending anchor prefix length [dec]
[dec] [dec] [dec] [dec] [dec] [dec] [dec]
[dec] [dec] [dec] [dec] [dec] [dec] [dec]
[dec] [dec] [dec] [dec] [dec]

The IPv6 compression anchor prefixes are

changed. The linecard needs to be
reloaded to make the changes effective.
This is not an error message or condition.

Infra error [chars] ([chars])

This error is an internal infra error and

when critical is handled accordingly in the
code. The context of the error is provided
in the actual code where this error is used.
Some of the error conditions that are
encountered under this is bind failure, attr
query failure, set/get failures, etc. If this
error is seen persistently initiate the
recommended action.

ftruncate failed([chars])

Platform PFI was unable to truncate the file.

The returned err code should indicate the
reason for the failure of the api. This is
likely due to a transient condition on the
system. The client calling this api could
retry it or handle it accordingly. If the issue
is seen persistently, initiate the
recommended action.

mmap failed([chars])

Memory map api failure in Platform PFI api.

The returned error code should indicate the
reason for the failure of the api. This is a
transient error in the system likely due to
low mem condition etc. The impact to
system is minimal except that some global
counters are not set. The client calling this
api could retry it or handle it accordingly. If
the issue is seen persistently, initiate the
recommended action.

shm_open failed([chars])

Platform PFI was unable to setup shared

memory due to failure in shared mem
open. The returned err code should
indicate the reason for the failure of the
api. This is a transient error in the system
likely due to low mem condition etc. The
impact to system is minimal except that a
few counters don't get set. The client
logging this error should retry the api
and/or handle this error accordingly. If this
error is seen persistently, Initiate the
recommended action.

[chars] encounterted the error [chars], for

interface [chars] handle [hex]

This is typically an internal error in the

software. The software failed in the
interface accounting on the engine..

tunnel ea debug_init failed [chars]

This is an Internal error in tunnel ea. The

failure here is while tunnel_ea is trying to
initialize/register debug flags. The
tunnel_ea process exits when there is a
failure to register these flags. Possible
reason for failure here could be due to lack
of memory. The tunnel_ea process gets
respawned by the sysmgr. If the system
does not recover on its own initiate the
below recommended action.

debug_init failed [chars]

This is an internal initialization error.

tunnel ea event_block failed [chars]

This is an Internal error in tunnel ea. An

invalid event handler or messaging api
failure (while tunnel ea is waiting for
events) is the reason for this error. If this is
seen consistently, initiate the
recommended action.

event_block failed [chars]

This is typically an internal error in the

software. The software failed to initialize
the code that handles/processes events
related to tunnel_ea.

This is an internal error in tunnel ea. The

failure is while tunnel_ea is creating an
event manager. The actual cause of the
tunnel ea error [chars] while creating event failure could be due to memfail/invalidargs
manager
etc.

Error [chars] creating event manager

This is typically an internal error in the

software. The software failed to initialize a
communication channel in the card where
the error is seen.

tunnel ea imp_init failed [chars]

This is an Internal error in tunnel ea. The

failure is while tunnel_ea is initializing its
event connection(to im). The process exits
here on failure. Possible cause of failure
could be due to lack of memory. The
tunnel_ea process gets respawned by the
sysmgr. If the system does not recover on
its own initiate the below recommended
action.

imp_init failed [chars]

This is typically an internal error in the

software. The software failed to initialize a
connection to another process in the card
where the error is seen.

This is an internal error in tunnel ea. The

Platform Manger returned the error [chars], error here is due to platform manager
for interface [chars] handle [hex]
returning interface creation failure.

This is typically an internal error in the

Platform Manger returned the error [chars], software. The software failed to create the
for interface [chars] handle [hex]
interface on the engine..

(Sysmgr_proc_ready failed [hex]) [chars]

sysmgr had difficulty in processing the

READY notification for tunnel_ea.

(Sysmgr_proc_ready failed [hex]) [chars]

This is typically an internal error in the

software. The software is not signalled to
start accepting events associated with it.

tunnel ea stats collecton init failed [chars]

This is an internal error in tunnel ea. The

failure here is while initializing the stats
collector. Possible cause of failure could be
due to invalid args/lack of memory. The
tunnel_ea process exits on failure and gets
respawned. If the system does not recover
on its own, initiate the below
recommended action.

stats collecton init failed [chars]

This is typically an internal error in the

software. The software failed to initialize
statistics infrastructure on the card where
the error is seen.

[chars]: [chars] - error ([hex]): [chars]

The specified API returned the specified

error.

[chars]: [chars] - error: [chars]

The specified API returned the specified

error

Invalid chain type ([dec])

An invalid chain type was received by the

chain builder. This is an internal error

tunnel config rescan failed: item [chars]:

[chars]

An unexpected error occured.

Current maximum [dec] exceeds absolute

maximum [dec]

New current maximum is larger than the

absolute max.

New current max [dec] is lower than the

number of tunnels currently configured
[dec].

New current max is lower than the current

tunnel count.

tunnel-[chars]: Current Maximum # of

configured tunnels reached [dec]

Tunnel Count has reached the current

maximum limit.

Eventmgr API to [chars] returned error:

[chars]

An internal error has occurred.

[chars]

None

Interface manager API failed [chars], error:

[chars]
An internal error has occurred.

Tunnel process infra error: [chars] error:

[chars]

An internal error has occurred.

Tunnel process initialization failed to

[chars]: error: [chars]

The tunnel process responsible for the

creation of tunnel interfaces failed during
initialization. The process will exit and as a
result, no tunnel interfaces can be
configured.

tunnel-[chars]: current tunnel count

became negative, restarting

Tunnel count has been decremented till it

became negative. process tunnel_infra will
restart to recover from the situation.

Interface [chars] does not exist to delete

A request to delete a non-existent interface

has been received. This is relatively a
harmless error, unless it is too frequent, in
which case the reason for the error must be
investigated, starting with the name of the
interface printed in the error message.

NULL DPC received

The EA received a datapath control with

NULL input data.

Sysdb API to [chars] returned error: [chars] An internal error has occurred.

pthreads api to [chars]; error: [chars]

An internal error has occurred.

IDB for interface [hex] not found

The EA received a datapath control

indication for an unknown interface handle

Received unexpected message opcode

[dec] in Interface Manager handler

An unexpected message was received by

this process. This is relatively a harmless
error and should not have any immediate
impact on the operation of tunnel
interfaces. It must still be reported and
looked into.

Invalid value [dec] for debug

An invalid value was received for the

debug flag.

Packet received on tunnel whose interface A packet was received on a tunnel whose
is not up
interface status is not up.

[chars]

An unexpected event occured in the

process specified, and so a running core
dump has been taken. This is not expected
to have any functional impact, but should
any problems be seen then this core will
aid debugging.

Failure during ISSU operation. [chars].

Error: [chars].

A failure occurred during the special

handling that takes place during an ISSU
operation.

Virtual Interface config replication failed.

[chars]. Error: [chars].

A failure occurred during the replication of

an item of virtual interface configuration to
one or more of the backup RPs.

VICR REPLICA received an incorrectly

formatted message while processing entry
[dec]: [chars]. [dec] bytes out of [dec]
read. VICR is registered on NRS class:
[hex]. VICR class name corresponds to
class handle: [hex].

VICR replica received a message that was

not in the expected format. This message
is to replicate virtual interface
configuration to the standby RP in case of
failover.

Unrecoverable error in event loop. Error:

[chars]

An unhandled error occured while waiting

for an event.

A failure occurred during the initialization

Failed to initialize config replicator. [chars]. of the Virtual Interface Config Replicator
Error: [chars]
process.

Performance traffic monitoring has cleared

an out-of-resource condition. Performance
traffic monitoring process on the linecard
Performance Traffic Monitoring: [chars] flow has detected that the number of flows
count on LC no longer at maximum
being monitored on an LC is no longer at
capacity
maximum.

Performance traffic monitoring has

encountered an out-of-resource condition.
Performance traffic monitoring process on
the linecard has detected that the number
Performance Traffic Monitoring: [chars] flow of flows being monitored on a LC has
count reached maximum ([unsigned int])
reached maximum capacity. New flows will
on LC
no longer be learnt

Performance traffic monitoring has cleared

an out-of-resource condition. Performance
traffic monitoring process on the linecard
Performance Traffic Monitoring: [chars] flow has detected that the number of flows
count on NP [unsigned int] no longer at
being monitored on a NP is no longer at
maximum capacity
maximum.

Performance Traffic Monitoring: Monitored

flows on LC [unsigned int] no longer at
maximum capacity

Performance traffic monitoring has cleared

an out-of-resource condition. Performance
traffic monitoring process on the linecard
has detected that the number of flows
being monitored on a LC is no longer at
maximum.

Performance traffic monitoring has

encountered an out-of-resource condition.
Performance traffic monitoring process on
the linecard has detected that the number
Performance Traffic Monitoring: [chars] flow of flows being monitored on a NP has
count reached maximum ([unsigned int])
reached maximum capacity. New flows will
on NP [unsigned int]
no longer be learnt

Performance Traffic Monitoring: Maximum

monitored flows ([unsigned int]) reached
on LC [unsigned int]

Performance traffic monitoring has

encountered an out-of-resource condition.
Performance traffic monitoring process on
the linecard has detected that the number
of flows being monitored on a LC has
reached maximum capacity. New flows will
no longer be learnt

Performance traffic service policy

verification failed, error [chars]: [chars]

Peformance traffic service policy

verification encountered the specified error

Performance traffic service policy

verification failed, error [chars]: [chars]

Peformance traffic service policy

verification encountered the specified error

During restart, corruption was detected in

the AVL tree. Tree is reinitialized as part of
recovery, some interval history during this
Corruption detected in AVL tree for [chars] time could be lost for the flow

Failed to initialise debug infra within AFMon Debug initialization failed within EA.
EA. Error: [chars]
Debugs may not be printed
Failed to initialise ltrace infra within AFMon Ltrace initialization failed within EA. Ltraces
EA. Error [chars]
may not be printed
AFMon EA encountered an error during
rollback phase of policy modification on an
Error encountered during Rollback phase of interface. In this condition, h/w
policy modification on interface: [chars]
programming of the policy may not be in
(ifh: [hex]), Error: [chars]
sync with policy configuration.

Failed to attach event to event manager:

[chars]

Failed to attach event to event manager.

Failed to initialize event manager event:

[chars]

Failed to initialize event manager event.

Failed to setup event manager

Failed to setup event manager.

FAM connection failed - [chars]

Connection to FAM process failed during

AFMon EA process init. This would lead to
an inablility of AFMon EA to receive flow
updates from the hardware

Server connection failed - [chars]. Error

code - [chars]

Connection to IM server failed during

AFMon EA process init. This would lead to
an inablility of AFMon EA to process CAPS
from AFMon MA and to a potential
disconnect between the hardware/software
views of the configured afmon policies on
the system.

LC has reached maximum limit for flows,

current [dec] maximum allowed [dec]

Software enforces a limit of 1.5 times the

maximum number of flows permitted on a
LC. When this limit is reached, no more
new flows can be added unless the current
flow count comes under the limit

Unrecoverable error in event loop. Error:

[chars]

An error (other than EINTR) occured in the

event loop. The process has exited and
restarted.

HD0 device not responding

SATA HD0 device not responding

HD1 device not responding

SATA HD1 device not responding

'bind: error aipc_debug_em_init failed:

[dec]'

Debug initialization failed within EM.

Debugs may not be printed

AIPC fabric media is disabled in this mode

'AIPC:fabric media is disabled in this mode' and Ethernet media is enabled.

Process Initialization Failed: ([chars]%s)

The alphadisplay process failed to initialize.

The alphadisplay process controls the 8
characters alphanumeric LEDs on the
bottom of all 12000 series line and route
processor cards (excluding SIP cards). It
provides for the configuration of custom
messages as well as the reading of the
current output both through CLI and XML.
%s - indicates the reason for the failure.
There are 2 types of possible failures, these
include: - Event Manager Creation Failure SYSDB Initialization Failure %s - is the
decoded error reason

Alpha display on node [chars] changed to

[chars] in state [chars]

Message to indicate that alpha-display was

updated with new string or state.

Alpha display on node [chars] changed to

[chars] in state [chars]\n

Message to indicate that alpha-display was

updated with new string or state.

Alpha display on node [chars] changed to

[chars] in state [chars]\n

Message to indicate that alpha-display was

updated with new string or state.

Event Failure: ([chars])

The alphadisplay process received a bad

event. The alphadisplay process controls
the 8 characters alphanumeric LEDs on the
bottom of all 12000 series line and route
processor cards (excluding SIP cards). It
provides for the configuration of custom
messages as well as the reading of the
current output both through CLI and XML.
%s - is the decoded error reason

APIV show_ltrace failed : [chars]

The message indicates failure in initializing

the tracing module.

APIV module [chars] is incompatible

APIV module version negotiation failed.

[chars]

An internal software error has occurred for

the specified APIV module

Message [dec] in APIV module [chars] is

incompatible (reason: [chars])

The APIV module message version

negotiation failed.

[chars] -ErrStr[chars]

This message indicates an error condition

in client library api while communicating
with the server process. It may be caused
due to invalid api arguments by client
process or a transient condition while the
server process is initializing the ASIC

[chars] -ErrStr[chars] [dec]

This message indicates an error condition

in client library api while communicating
with the server process. It may be caused
due to invalid api arguments by client
process or a transient condition while the
server process is initializing the ASIC

[chars] -ErrStr[chars] [chars]

This message indicates an error condition

in client library api while communicating
with the server process. It may be caused
due to invalid api arguments by client
process or a transient condition while the
server process is initializing the ASIC

Initialization Error: [chars] Reason: [chars]. Arbiter driver encountered a fatal error and
Exiting.
is not able recover from the error.

Arbiter driver encountered a fatal error and

is not able recover from the error. A reason
Initialization Error: [chars] Reason: [chars]. text will be supplied call support with this
Exiting.
text.

Error Allocating <[dec]> bytes of memory

Arbiter driver encountered a fatal memory

allocation error

Error Allocating <[dec]> bytes of memory

Arbiter driver encountered a fatal memory

allocation error

Continuing execution: [chars]: Caused by

[chars]

This message indicates an error occurred

beyond which execution of the arbiter
driver may continue, attempting to effect
recovery or work-around internally,
minimizing loss of information/functionality.

Continuing execution: [chars]: Caused by

[chars]

This message indicates an error occurred

beyond which execution of the arbiter
driver may continue, attempting to effect
recovery or work-around internally,
minimizing loss of information/functionality.

Event Manager create failed for [chars].

Reason: [chars]

Arbiter driver Event Manager create error

Event Manager create failed for [chars].

Reason: [chars]

Arbiter driver Event Manager create error

Event Manager notify failed for [chars].

Reason: [chars]

Arbiter driver Event Manager notify error

Event Manager notify failed for [chars].

Reason: [chars]

Arbiter driver Event Manager notify error

Exit on error: [chars]: Caused by [chars]

An error occurred in arbiter driver which

requires exiting (and, hence, restarting) the
process.

Exit on error: [chars]: Caused by [chars]

An error occurred in arbiter driver which

requires exiting (and, hence, restarting) the
process.

LWM Event Manager event block failed.

Reason: [chars]

Arbiter driver Event Manager event block

error

LWM Event Manager event block failed.

Reason: [chars]

Arbiter driver Event Manager event block

error

An error occurred during LWM message

reply. Reason: [chars]

Arbiter driver LWM reply error

An error occurred during LWM message

reply. Reason: [chars]

Arbiter driver LWM reply error

When a hardware fault occurs and the

device driver cannot correct it, the Platform
Manager is required to reset the ASICs. This
error indicates that the Platform Manager
failed to reset the ASICs and the hardware
on the PRP may not be in an operational
The fault recovery procedure for the
state. This condition affects the
FromFab component of the fabric driver has functionality of the entire router. %s is the
failed. The root fault was: [chars]
Interrupt Source.

A software error occurred in the FrFab

driver component during initialization:
[chars]

The fabricq_prp_driver process which

controls the FromFab driver on the route
processor has failed to initalize and cannot
recover automatically. This is a software
fault. The FromFab driver controls the
hardware that receives data from the
fabric. It runs in the fabricq_prp_driver
process. An unrecoverable failure of the
fabricq_prp_driver process may prevent
this route processor card from
communicating with other cards on the
chassis. %s indicates the type failure

Assembler detected a bad descriptor in the

free queue. The hex number indicates the
Assembler detected a bad descriptor error: error cause register value. This usually
Data [hex]
indicates a hardware problem on the RP.

assembler dll: block: [chars], entity: [chars] PII block got a packet from the entity
had CRC error, count: [dec]
mentioned above with a CRC error.

FFQ: device halted, sub-block: [chars],

halted entity: [chars]

FFQ, ASIC got halted. The halted block and

its parent block are provided

assembler dll: fatal error encountered,

reason=[chars]

iqm, assembler dll manager encountered a

fatal error and is not able recover from the
error. A reason text will be supplied call
support with this text.

assembler dll: fatal error encountered,

reason=[chars], errno=[dec]

assembler encountered a fatal error and is

not able to recover from the error. A reason
text will be supplied call support with this
text. An integer errno will also be printed.

Assembler detected a FIA interface error:

Data [hex]

Assembler detected an error with the fia

interface. The hex number indicates the
error cause register value. This usually
indicates a hardware problem on the RP.

A parity error has been detected on the

assembler to fia interface. The hex number
indicates the error cause register value.
Assembler detected a FIA parity error: Data This usually indicates a hardware problem
[hex]
on the RP.

Assembler detected a free queue empty

error: Data [hex]

Assembler detected a that the free queue

is empty. The hex number indicates the
error cause register value.

Assembler detected that a free queue is

empty

The assembler component has detected

that one of the free queues used to buffer
packets coming from the fabric into the
route processor is empty.

assembler dll: general

information,<[chars]>

The ASM's informational message.

assembler dll: hardware initialization not

complete

hardware init is not complete.

assembler dll: service degrading error,

reason = [chars]

The assembler encountered an error that

would lead to degraded service.

assembler dll: intr enable at addr: [hex]

mask: [hex] failed.

hardware state is not correct.

assembler dll: intr status get failed for:

[chars]@[hex], rc=[dec]

Hardware register read failed.

assembler dll: fatal memory allocation error ASM encountered a fatal memory allocation
for <[dec]> bytes
error

assembler dll: asic is not available

hardware state is not correct.

assembler dll: asic is not operational, state:

[dec]
hardware state is not correct.

assembler dll: this function <[chars]> is

not yet implemented

FFQ, assembler dll , a function is not

implemented.

Assembler is being reset because of too

many errors.

Assembler software driver is seeing too

many errors that indicated a problem with
the hardware. Some of the error logs prior
to this message should indicate the errors
that lead to this reset.

Assembler detected a bad descriptor.

Assembler detected a bad descriptor in the

free queue. The system will usually recover
from this error automatically. If the
frequency of this alert increases noticeably
it could indicate a hardware problem on the
route processor card.

assembler dll: halt not handled, parent:

[chars], child: [chars], intr: [dec]

Hardware halt is not handled.

assembler dll: intr not handled, parent:

[chars], child: [chars], group id: [dec], intr: Hardware interrupt is not handled in the
[dec]
code, need to implement.

PLATFORM-IFLX: [chars]

Only 10/100M IFLX front port sharing mode

is supported. No explicit blocking

Asr9k pagent process exiting because

[chars], func:[chars] , line [dec], error code The pagent process exited due to the
[chars]\n
reason mentioned in the message.

[chars],Info - [chars]\n

Informational condition and/or failure. The

process can continue functioning as
expected despite the failure.

[chars] in func: [chars]\n

This is a programmed diagnostic debug

message.

Failed to [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

Timeout ([dec] seconds) waiting for APIV

modules registration.

The registration of APIV modules has not

completed. The specified timeout period
has reached and is this event will be
considered as a failure that will trigger a
reload of the affected card.

The [chars] APIV module (module ID =

[dec]) was not registered in time to receive This event will cause the module to fail in
version negotiation event notification.
APIV versioning negotiation operation.
Node: [chars]: [chars] will be used for
storing control ethernet logs. Current logs
are under [chars] directory.

This is an informational message to

indicate the location of for es_persist,
bcm.log, stp.log and stp_shim.log are.

This is an informational message to

indicate that copying a log file to the
storage device indicated has failed. This
could be because the device was being
Copying of log file to [chars] failed. err =
formatted. The process will restart to
[dec], status = [dec]. Restarting to recover. recover.

[chars] directory not found.

This is an informational message to

indicate that a log directory in the storage
device is not found. This could be because
the device was being formatted. The
process will restart to recover.

Copying of control-ethernet log files to

persistent storage is suspended because
no persistent storage device
(harddisk/PCMCIA disk) found

The service that copies /tmp/bcm.log,

stp.log, es_persist to persistent storage, did
not find any of harddisk, disk0, disk1
available

Spanning Tree Port [chars] state changed

to ADMIN_DOWN

Spanning Tree Port's state change by

manual intervention.

Spanning Tree Port [chars] state changed

to [chars]

Spanning Tree Port's state change

indication.

Control Ethernet Intra-rack Switch [dec]

detected MMU error

The switch encountered a MMU error. MMU

errors can affect traffic forwarding in the
switch.

PCI fatal error seen on switch [dec] DMA

channel [dec] type [chars]

The switch encountered a PCI error during

a DMA transaction.

Hardware fault declared on Switch port

[dec] after maximum recovery attempt.

Software declared hardware fault on the

specified port after the number of autorecovery attempt exceeded the threshold.
The port will be set to UDLD err-disable
state until manually cleared. The fault
could be hardware issues or connection
problem.

Control Ethernet Intra-rack Switch [dec]

detected Memory full condition

The switch encountered a memory full

condition. Normally this error is not
expected. As per the spec, this situation
should fix itself. The ports will drop packets
in ingress if the situation persists.

[chars] [dec] [chars] [chars]

Unable to get shared memory window info

[chars]

BFD HW offload not supported on this

node, disabled it

[chars]

bfd hw offload mode changed, config will

be activated only after a line card reset

[chars] [dec] [chars]

LC level scale limit has been reached.

[chars] [dec] [chars] [chars] [dec] [dec]

LC level scale limit for this timer has been

reached.

[chars] [dec] [chars] [chars] [dec] [dec]

NP level scale limit has been reached.

[chars] [dec] [chars] [chars] [dec] [dec]

NP level scale limit for this timer has been

reached.

Exceeded bundle scale limit ([dec]) for

Trident based LC. Might experience
unpredictable traffic loss behaviour.
Remove excess bundle and reload LC.

The limit to maximum number of bundles

per LC is exceeded.

Unable to mmap DMA device memory for

burst access of SMDC

Unable to mmap the DMA memory for

accessing the SMDC.

IPC mmap failed in the card

Need to memory map the PCI memory in

order to do IPC, but unable to mmap the
PCI memory of the SMDC.

Unable to mmap PCI device memory of

SMDC

Need to memory map the PCI memory in

order to do communicate, but unable to
mmap the PCI memory of the SMDC.

Mmap failed in PCI library, rc = [dec]

Need to memory map the PCI memory in

order to do IPC, but unable to mmap the
PCI memory of the SMDC.

Failed to create/ftruncate shared memory

Failed to create/ftruncate shared memory

for the pci library initialization.

Card shutdown failed

Tried to shut the SMDC, but there is a

problem in shutting the card.

Card is shutdown

The SMDC is shut down by the sysldr

process as requested.

SMDC - Get uboot status failed

Failure in getting the SMDC - uboot status.

The uboot status is read from the hummer
register of the PRP3.

Powered down SMDC

For displaying SMDC's informational

events.

Malloc failed for the config: [chars]

Failed to allocate memory for the

configuration to be applied.

[chars]: Received NULL request/response

from PI

When trying to apply the config to SMDC

via CLI, it received null request and/or
response from the PI/parser.

Failed to allocate memory for msgbuf

SMDC fault manager: Failed to allocate

memory for msgbuf.

Failed to create event channel

SMDC fault manager: Failed to create event

channel.

Failed to create SMDC event handling

thread

SMDC event handler thread. This thread is

only used for events related to booster
shutdown functionality. And it is failing

Couldn't create EVM

Trying to create and initialize Event

Manager structures, but the Event
manager creation is failed.

Failed to create event channel

Failed to create event channel, Internal

failures.

Service card is powered, SMDC License is

not installed

Service card is powered, but the SMDC

License is not installed.

Message handler attach failed with errcode Event message handler attach to sysldr
= [dec]
failed

c12k service pie is deactivated please

execute install commit immediately to
disable SMDC service

The c12k service pie is deactivated. Error

faced in getting the path/file name of the
bin/pkg file from the image

c12k-service pie is deactivated

The c12k service pie is deactivated.

Shut failed

Tried to shut the SMDC, but there is a

problem in shutting the card.

Card is shut down, hence sleeping

SMDC card is shutting down hence

sleeping.

Shutting down the card

The SMDC is shut down by the sysldr

process as requested.

Failed to block on sysmgr until card active

Sysmgr block is failed until this card is

becoming ACTIVE.

Failed to update c12k-service pie, install

status is [chars]

The c12k-service pie install status update

is failed. This status is updated by sysldr
process when c12k-service pie install
status is changed.

[chars]

For displaying SMDC's informational

events.

SMDC shut config :[dec]

SMDC shut configuration detail

This RP detected more than 2 RPs

(active/standby) inserted in the chassis.

When more than 2 RPs (active/standby) are

used in the same chassis, one must be
elected as the dSC, the master of the
chassis. In order to select which RP will
become the dSC, insert only the RPs that
will be part of the Owner Logical Router
(maximum of 2 RPs). Once these RPs are
fully booted, you may insert other RPs as
required and assign them to manage
logical routers. At this point, chassis
mastership has been determined and
subsequent power-cycle of the chassis will
support multiple RPs with no problem.

This process needs to know if it runs on the

DSC or standby DSC. An error occured
while trying to get the information from the
Failed to learn if we are running on the DSC DSC process. The process will voluntary
([chars])
exit, and should be restarted.

Backplane NVRAM contains MAC address

info field [hex] which is invalid. Please
rectify this problem to ensure quality
operation of your router

There is a MAC address block field in the

backplane NVRAM. If the MAC address
block field is invalid, there is the possibility
of corrupted backplane NVRAM or
incompatibility with the software

Backplane NVRAM contains Backplane

Version number [dec] which is invalid.
Please rectify this problem to ensure
quality operation of your router

There is a Backplane Version field in the

backplane NVRAM. If the Backplane Version
field is invalid, there is the possibility of
corrupted backplane NVRAM or
incompatibility with the software

Backplane NVRAM contains chassis model

number [dec] which is invalid. Please
rectify this problem to ensure quality
operation of your router

Backplane NVRAM contains the chassis

model number which the software relies on
for chassis identification. This is a
complaint about an invalid chassis model
number is stored in backplane NVRAM.
Software will try its best to use the CSC
card in the chassis to determine the
chassis model.

Local request for backplane nvram [chars] Backplane NVRAM request received locally
rejected. Address is outside valid range of is invalid. Range mentioned in request is
nvram (offset=[dec], len=[dec])
outside valid range.

Backplane nvram could not be read

Reading Backplane NVRAM failed([chars]). successfully.

Request for backplane nvram [chars] from

slot=[dec] rejected. Address is outside
valid range of nvram (offset=[dec],
len=[dec])

Backplane NVRAM request received from

mentioned slot through MBUS is invalid.
Range mentioned in request is outside
valid range.

[chars].[dec]: cdi_bind to [chars] failed\n

An error occurred in i2c driver due to cdi

bind function call failed.

An error occurred in i2c driver due to cdi

[chars].[dec]: cdi_bind on rack [dec] failed, bind function call failed in th particular
last path triedi:[chars]\n
rack.

[chars]: cdi_unbind failed for rack [dec]\n

An error occurred in i2c driver due to cdi

unbind function call failed in the particular
rack.

[chars], ErrStr:[chars]([hex])

An error occurred in BPE Driver which

requires exiting (and, hence, restarting) the
process.

BPE Driver encountered a fatal error and is

not able to recover. The supplied text string
Initialization Error: [chars] Reason: [chars]. will explain the reason. Call support with
Exiting.
this text.

Error Allocating <[dec]> bytes of memory

BPE encountered a fatal memory allocation

error

Continuing execution: [chars]: Caused by

[chars]

This message indicates an error occurred

beyond which execution of the bpe_driver
may continue, attempting to effect
recovery or work-around internally,
minimizing loss of information/functionality.

[chars]

This message logs an informational

message.

Continuing execution: [chars]

This message indicates an condition

occurred beyond which execution of the
bpe_driver may continue

Event Manager create failed for [chars].

Reason: [chars]

BPE Event Manager create error

Event Manager notify failed for [chars].

Reason: [chars]

BPE Event Manager notify error

Exit on error: [chars]: Caused by [chars]

An error occurred in BPE Driver which

requires exiting (and, hence, restarting) the
process.

LWM Event Manager event block failed.

Reason: [chars]

BPE Event Manager event block error

An error occurred during LWM message

reply. Reason: [chars]

bpe LWM reply error

DDR bus data bit stuck-0

DDR bus databit stuck on bridge instance0.

DDR bus data bit stuck-1

DDR bus databit stuck on bridge instance1.

DDR bus data bit stuck-2

DDR bus databit stuck on bridge instance2.

DDR bus data bit stuck-3

DDR bus databit stuck on bridge instance3.

DDR interface loss of sync-0

Loss of sync on DDR interface on bridge

instance-0.

DDR interface loss of sync-1

Loss of sync on DDR interface on bridge

instance-1.

DDR interface loss of sync-2

Loss of sync on DDR interface on bridge

instance-2.

DDR interface loss of sync-3

Loss of sync on DDR interface on bridge

instance-3.

FIFO-0 FIA to bridge-0 overflow

FIFO-0 FIA to bridge instance-0 overflow.

FIFO-0 FIA to bridge-1 overflow

FIFO-0 FIA to bridge instance-1 overflow.

FIFO-0 FIA to bridge-2 overflow

FIFO-0 FIA to bridge instance-2 overflow.

FIFO-0 FIA to bridge-3 overflow

FIFO-0 FIA to bridge instance-3 overflow.

FIFO-0 NPU to bridge-0 overflow

FIFO-0 NPU to bridge instance-0 overflow.

FIFO-0 NPU to bridge-1 overflow

FIFO-0 NPU to bridge instance-1 overflow.

FIFO-0 NPU to bridge-2 overflow

FIFO-0 NPU to bridge instance-2 overflow.

FIFO-0 NPU to bridge-3 overflow

FIFO-0 NPU to bridge instance-3 overflow.

FIFO-1 FIA to bridge-0 overflow

FIFO-1 FIA to bridge instance-0 overflow.

FIFO-1 FIA to bridge-1 overflow

FIFO-1 FIA to bridge instance-1 overflow.

FIFO-1 FIA to bridge-2 overflow

FIFO-1 FIA to bridge instance-2 overflow.

FIFO-1 FIA to bridge-3 overflow

FIFO-1 FIA to bridge instance-3 overflow.

FIFO-1 NPU to bridge-0 overflow

FIFO-1 NPU to bridge instance-0 overflow.

FIFO-1 NPU to bridge-1 overflow

FIFO-1 NPU to bridge instance-1 overflow.

FIFO-1 NPU to bridge-2 overflow

FIFO-1 NPU to bridge instance-2 overflow.

FIFO-1 NPU to bridge-3 overflow

FIFO-1 NPU to bridge instance-3 overflow.

MAC on NPU-0 transmit fifo overflow - 0

MAC on NPU-0 had transmit fifo overflow on

bridge instance-0.

MAC on NPU-0 transmit fifo overflow - 1

MAC on NPU-0 had transmit fifo overflow on

bridge instance-1.

MAC on NPU-0 transmit fifo overflow - 2

MAC on NPU-0 had transmit fifo overflow on

bridge instance-2.

MAC on NPU-0 transmit fifo overflow - 3

MAC on NPU-0 had transmit fifo overflow on

bridge instance-3.

MAC on NPU-1 transmit fifo overflow - 0

MAC on NPU-1 had transmit fifo overflow on

bridge instance-0.

MAC on NPU-1 transmit fifo overflow - 1

MAC on NPU-1 had transmit fifo overflow on

bridge instance-1.

MAC on NPU-1 transmit fifo overflow - 2

MAC on NPU-1 had transmit fifo overflow on

bridge instance-2.

MAC on NPU-1 transmit fifo overflow - 3

MAC on NPU-1 had transmit fifo overflow on

bridge instance-3.

NPU-0 egress queue error - 0

Egress queue error on NPU-0 interface on

bridge instance-0.

NPU-0 egress queue error - 1

Egress queue error on NPU-0 interface on

bridge instance-1.

NPU-0 egress queue error - 2

Egress queue error on NPU-0 interface on

bridge instance-2.

NPU-0 egress queue error - 3

Egress queue error on NPU-0 interface on

bridge instance-3.

NPU-0 interface loss of sync-0

Loss of sync on NPU-0 interface on bridge

instance-0.

NPU-0 interface loss of sync-1

Loss of sync on NPU-0 interface on bridge

instance-1.

NPU-0 interface loss of sync-2

Loss of sync on NPU-0 interface on bridge

instance-2.

NPU-0 interface loss of sync-3

Loss of sync on NPU-0 interface on bridge

instance-3.

NPU-0 scheduler mem parity error - 0

Scheduler Hang, Sram or egress mid-fifo

parity error on NPU-0 interface on bridge
instance-0.

NPU-0 scheduler mem parity error - 1

Scheduler Hang, Sram or egress mid-fifo

parity error on NPU-0 interface on bridge
instance-1.

NPU-0 scheduler mem parity error - 2

Scheduler Hang, Sram or egress mid-fifo

parity error on NPU-0 interface on bridge
instance-2.

NPU-0 scheduler mem parity error - 3

Scheduler Hang, Sram or egress mid-fifo

parity error on NPU-0 interface on bridge
instance-3.

NPU-0 XAUI PLL not locked on bridge - 0

NPU-0 XAUI PLL not locked on bridge

instance-0.

NPU-0 XAUI PLL not locked on bridge - 1

NPU-0 XAUI PLL not locked on bridge

instance-1.

NPU-0 XAUI PLL not locked on bridge - 2

NPU-0 XAUI PLL not locked on bridge

instance-2.

NPU-0 XAUI PLL not locked on bridge - 3

NPU-0 XAUI PLL not locked on bridge

instance-3.

NPU-0 XAUI not ready on bridge - 0

NPU-0 XAUI not ready on bridge instance-0.

NPU-0 XAUI not ready on bridge - 1

NPU-0 XAUI not ready on bridge instance-1.

NPU-0 XAUI not ready on bridge - 2

NPU-0 XAUI not ready on bridge instance-2.

NPU-0 XAUI not ready on bridge - 3

NPU-0 XAUI not ready on bridge instance-3.

NPU-1 egress queue error - 0

Egress queue error on NPU-1 interface on

bridge instance-0.

NPU-1 egress queue error - 1

Egress queue error on NPU-1 interface on

bridge instance-1.

NPU-1 egress queue error - 2

Egress queue error on NPU-1 interface on

bridge instance-2.

NPU-1 egress queue error - 3

Egress queue error on NPU-1 interface on

bridge instance-3.

NPU-1 interface loss of sync-0

Loss of sync on NPU-1 interface on bridge

instance-0.

NPU-1 interface loss of sync-1

Loss of sync on NPU-1 interface on bridge

instance-1.

NPU-1 interface loss of sync-2

Loss of sync on NPU-1 interface on bridge

instance-2.

NPU-1 interface loss of sync-3

Loss of sync on NPU-1 interface on bridge

instance-3.

NPU-1 scheduler mem parity error - 0

Scheduler Hang, Sram or egress mid-fifo

parity error on NPU-1 interface on bridge
instance-0.

NPU-1 scheduler mem parity error - 1

Scheduler Hang, Sram or egress mid-fifo

parity error on NPU-1 interface on bridge
instance-1.

NPU-1 scheduler mem parity error - 2

Scheduler Hang, Sram or egress mid-fifo

parity error on NPU-1 interface on bridge
instance-2.

NPU-1 scheduler mem parity error - 3

Scheduler Hang, Sram or egress mid-fifo

parity error on NPU-1 interface on bridge
instance-3.

NPU-1 XAUI PLL not locked on bridge - 0

NPU-1 XAUI PLL not locked on bridge

instance-0.

NPU-1 XAUI PLL not locked on bridge - 1

NPU-1 XAUI PLL not locked on bridge

instance-1.

NPU-1 XAUI PLL not locked on bridge - 2

NPU-1 XAUI PLL not locked on bridge

instance-2.

NPU-1 XAUI PLL not locked on bridge - 3

NPU-1 XAUI PLL not locked on bridge

instance-3.

NPU-1 XAUI not ready on bridge - 0

NPU-1 XAUI not ready on bridge instance-0.

NPU-1 XAUI not ready on bridge - 1

NPU-1 XAUI not ready on bridge instance-1.

NPU-1 XAUI not ready on bridge - 2

NPU-1 XAUI not ready on bridge instance-2.

NPU-1 XAUI not ready on bridge - 3

NPU-1 XAUI not ready on bridge instance-3.

QDR memory data bit stuck-0

QDR memory databit stuck on bridge

instance-0.

QDR memory data bit stuck-1

QDR memory databit stuck on bridge

instance-1.

QDR memory data bit stuck-2

QDR memory databit stuck on bridge

instance-2.

QDR memory data bit stuck-3

QDR memory databit stuck on bridge

instance-3.

Multicast free pages empty - 0

Multicast free pages empty on bridge

instance-0.

Multicast free pages empty - 1

Multicast free pages empty on bridge

instance-1.

Multicast free pages empty - 2

Multicast free pages empty on bridge

instance-2.

Multicast free pages empty - 3

Multicast free pages empty on bridge

instance-3.

QDR memory ECC failure on bridge-0

QDR memory ECC failure on bridge

instance-0.

QDR memory ECC failure on bridge-1

QDR memory ECC failure on bridge

instance-1.

QDR memory ECC failure on bridge-2

QDR memory ECC failure on bridge

instance-2.

QDR memory ECC failure on bridge-3

QDR memory ECC failure on bridge

instance-3.

QDR memory self test failure on bridge-0

QDR memory self test failure on bridge

instance-0.

QDR memory self test failure on bridge-1

QDR memory self test failure on bridge

instance-1.

QDR memory self test failure on bridge-2

QDR memory self test failure on bridge

instance-2.

QDR memory self test failure on bridge-3

QDR memory self test failure on bridge

instance-3.

Register access failure on bridge-0

Register access failure on bridge instance0.

Register access failure on bridge-1

Register access failure on bridge instance1.

Register access failure on bridge-2

Register access failure on bridge instance2.

Register access failure on bridge-3

Register access failure on bridge instance3.

State machine-0 error-1 on bridge-0

State machine - 0 ran into error-1 on bridge

instance-0.

State machine-0 error-1 on bridge-1

State machine - 0 ran into error-1 on bridge

instance-1.

State machine-0 error-1 on bridge-2

State machine - 0 ran into error-1 on bridge

instance-2.

State machine-0 error-1 on bridge-3

State machine - 0 ran into error-1 on bridge

instance-3.

State machine-0 error-2 on bridge-0

State machine - 0 ran into error-2 on bridge

instance-0.

State machine-0 error-2 on bridge-1

State machine - 0 ran into error-2 on bridge

instance-1.

State machine-0 error-2 on bridge-2

State machine - 0 ran into error-2 on bridge

instance-2.

State machine-0 error-2 on bridge-3

State machine - 0 ran into error-2 on bridge

instance-3.

State machine-0 error-3 on bridge-0

State machine - 0 ran into error-3 on bridge

instance-0.

State machine-0 error-3 on bridge-1

State machine - 0 ran into error-3 on bridge

instance-1.

State machine-0 error-3 on bridge-2

State machine - 0 ran into error-3 on bridge

instance-2.

State machine-0 error-3 on bridge-3

State machine - 0 ran into error-3 on bridge

instance-3.

State machine-1 error-1 on bridge-0

State machine - 1 ran into error-1 on bridge

instance-0.

State machine-1 error-1 on bridge-1

State machine - 1 ran into error-1 on bridge

instance-1.

State machine-1 error-1 on bridge-2

State machine - 1 ran into error-1 on bridge

instance-2.

State machine-1 error-1 on bridge-3

State machine - 1 ran into error-1 on bridge

instance-3.

State machine-1 error-2 on bridge-0

State machine - 1 ran into error-2 on bridge

instance-0.

State machine-1 error-2 on bridge-1

State machine - 1 ran into error-2 on bridge

instance-1.

State machine-1 error-2 on bridge-2

State machine - 1 ran into error-2 on bridge

instance-2.

State machine-1 error-2 on bridge-3

State machine - 1 ran into error-2 on bridge

instance-3.

State machine-1 error-3 on bridge-0

State machine - 1 ran into error-3 on bridge

instance-0.

State machine-1 error-3 on bridge-1

State machine - 1 ran into error-3 on bridge

instance-1.

State machine-1 error-3 on bridge-2

State machine - 1 ran into error-3 on bridge

instance-2.

State machine-1 error-3 on bridge-3

State machine - 1 ran into error-3 on bridge

instance-3.

XAUI to NPU-0 chan sync error on bridge

XAUI to NPU-0 chan sync error on bridge-0 instance-0.

XAUI to NPU-0 chan sync error on bridge

XAUI to NPU-0 chan sync error on bridge-1 instance-1.

XAUI to NPU-0 chan sync error on bridge

XAUI to NPU-0 chan sync error on bridge-2 instance-2.

XAUI to NPU-0 chan sync error on bridge

XAUI to NPU-0 chan sync error on bridge-3 instance-3.

XAUI to NPU-0 char alignment error on

bridge-0

XAUI to NPU-0 char alignment error on

bridge instance-0.

XAUI to NPU-0 char alignment error on

bridge-1

XAUI to NPU-0 char alignment error on

bridge instance-1.

XAUI to NPU-0 char alignment error on

bridge-2

XAUI to NPU-0 char alignment error on

bridge instance-2.

XAUI to NPU-0 char alignment error on

bridge-3

XAUI to NPU-0 char alignment error on

bridge instance-3.

XAUI to NPU-0 MGT code violation on

bridge-0

XAUI to NPU-0 MGT code violation on

bridge instance-0.

XAUI to NPU-0 MGT code violation on

bridge-1

XAUI to NPU-0 MGT code violation on

bridge instance-1.

XAUI to NPU-0 MGT code violation on

bridge-2

XAUI to NPU-0 MGT code violation on

bridge instance-2.

XAUI to NPU-0 MGT code violation on

bridge-3

XAUI to NPU-0 MGT code violation on

bridge instance-3.

XAUI to NPU-0 Rx alignment loss - 0

Rx alignment loss on XAUI to NPU-0

interface on bridge instance-0.

XAUI to NPU-0 Rx alignment loss - 1

Rx alignment loss on XAUI to NPU-0

interface on bridge instance-1.

XAUI to NPU-0 Rx alignment loss - 2

Rx alignment loss on XAUI to NPU-0

interface on bridge instance-2.

XAUI to NPU-0 Rx alignment loss - 3

Rx alignment loss on XAUI to NPU-0

interface on bridge instance-3.

XAUI to NPU-0 state error on bridge-0

XAUI to NPU-0 state error on bridge

instance-0.

XAUI to NPU-0 state error on bridge-1

XAUI to NPU-0 state error on bridge

instance-1.

XAUI to NPU-0 state error on bridge-2

XAUI to NPU-0 state error on bridge

instance-2.

XAUI to NPU-0 state error on bridge-3

XAUI to NPU-0 state error on bridge

instance-3.

XAUI to NPU-0 tx fifo overflow - 0

XAUI interface to NPU-0 reported tx fifo

overflow on bridge instance - 0.

XAUI to NPU-0 tx fifo overflow - 1

XAUI interface to NPU-0 reported tx fifo

overflow on bridge instance - 1.

XAUI to NPU-0 tx fifo overflow - 2

XAUI interface to NPU-0 reported tx fifo

overflow on bridge instance - 2.

XAUI to NPU-0 tx fifo overflow - 3

XAUI interface to NPU-0 reported tx fifo

overflow on bridge instance - 3.

XAUI to NPU-1 chan sync error on bridge

XAUI to NPU-1 chan sync error on bridge-0 instance-0.

XAUI to NPU-1 chan sync error on bridge

XAUI to NPU-1 chan sync error on bridge-1 instance-1.

XAUI to NPU-1 chan sync error on bridge

XAUI to NPU-1 chan sync error on bridge-2 instance-2.

XAUI to NPU-1 chan sync error on bridge

XAUI to NPU-1 chan sync error on bridge-3 instance-3.

XAUI to NPU-1 char alignment error on

bridge-0

XAUI to NPU-1 char alignment error on

bridge instance-0.

XAUI to NPU-1 char alignment error on

bridge-1

XAUI to NPU-1 char alignment error on

bridge instance-1.

XAUI to NPU-1 char alignment error on

bridge-2

XAUI to NPU-1 char alignment error on

bridge instance-2.

XAUI to NPU-1 char alignment error on

bridge-3

XAUI to NPU-1 char alignment error on

bridge instance-3.

XAUI to NPU-1 MGT code violation on

bridge-0

XAUI to NPU-1 MGT code violation on

bridge instance-0.

XAUI to NPU-1 MGT code violation on

bridge-1

XAUI to NPU-1 MGT code violation on

bridge instance-1.

XAUI to NPU-1 MGT code violation on

bridge-2

XAUI to NPU-1 MGT code violation on

bridge instance-2.

XAUI to NPU-1 MGT code violation on

bridge-3

XAUI to NPU-1 MGT code violation on

bridge instance-3.

XAUI to NPU-1 Rx alignment loss - 0

Rx alignment loss on XAUI to NPU-1

interface on bridge instance-0.

XAUI to NPU-1 Rx alignment loss - 1

Rx alignment loss on XAUI to NPU-1

interface on bridge instance-1.

XAUI to NPU-1 Rx alignment loss - 2

Rx alignment loss on XAUI to NPU-1

interface on bridge instance-2.

XAUI to NPU-1 Rx alignment loss - 3

Rx alignment loss on XAUI to NPU-1

interface on bridge instance-3.

XAUI to NPU-1 state error on bridge-0

XAUI to NPU-1 state error on bridge

instance-0.

XAUI to NPU-1 state error on bridge-1

XAUI to NPU-1 state error on bridge

instance-1.

XAUI to NPU-1 state error on bridge-2

XAUI to NPU-1 state error on bridge

instance-2.

XAUI to NPU-1 state error on bridge-3

XAUI to NPU-1 state error on bridge

instance-3.

XAUI to NPU-1 tx fifo overflow - 0

XAUI interface to NPU-1 reported tx fifo

overflow on bridge instance - 0.

XAUI to NPU-1 tx fifo overflow - 1

XAUI interface to NPU-1 reported tx fifo

overflow on bridge instance - 1.

XAUI to NPU-1 tx fifo overflow - 2

XAUI interface to NPU-1 reported tx fifo

overflow on bridge instance - 2.

XAUI to NPU-1 tx fifo overflow - 3

XAUI interface to NPU-1 reported tx fifo

overflow on bridge instance - 3.

XAUI-A databus stuck-0

XAUI-A databus stuck on bridge instance-0.

XAUI-A databus stuck-1

XAUI-A databus stuck on bridge instance-1.

XAUI-A databus stuck-2

XAUI-A databus stuck on bridge instance-2.

XAUI-A databus stuck-3

XAUI-A databus stuck on bridge instance-3.

Decoder A CRC Error - 0

Decoder A CRC error on bridge instance-0.

Decoder A CRC Error - 1

Decoder A CRC error on bridge instance-1.

Decoder A Framing Error - 0

Decoder A framing error on bridge

instance-0.

Decoder A Framing Error - 1

Decoder A framing error on bridge

instance-1.

Decoder A Packet Length Error - 0

Packet with invalid length encountered by

decoder A on bridge instance-0.

Decoder A Packet Length Error - 1

Packet with invalid length encountered by

decoder A on bridge instance-1.

Decoder A PWM Error - 0

PWM bit level decoder error on decoder A

on bridge instance-0.

Decoder A PWM Error - 1

PWM bit level decoder error on decoder A

on bridge instance-1.

Decode A Type Disabled - 0

Pkt received for timestamp type disabled

on Decoder A on bridge instance-0.

Decode A Type Disabled - 1

Pkt received for timestamp type disabled

on Decoder A on bridge instance-1.

Egress long packet detected - 0,0

Egress long packet detected on xaui-0

bridge instance-0.

Egress long packet detected - 0,1

Egress long packet detected on xaui-0

bridge instance-1.

Egress long packet detected - 1,0

Egress long packet detected on xaui-1

bridge instance-0.

Egress long packet detected - 1,1

Egress long packet detected on xaui-1

bridge instance-1.

Egress invalid length detected - 0,0

Invalid egress NPH length detected on

xaui-0 bridge instance-0.

Egress invalid length detected - 0,1

Invalid egress NPH length detected on

xaui-0 bridge instance-1.

Egress invalid length detected - 1,0

Invalid egress NPH length detected on

xaui-1 bridge instance-0.

Egress invalid length detected - 1,1

Invalid egress NPH length detected on

xaui-1 bridge instance-1.

Egress seg data fifo overflow - 0,0

Egress seg data fifo overflow on xaui-0

bridge instance-0.

Egress seg data fifo overflow - 0,1

Egress seg data fifo overflow on xaui-0

bridge instance-1.

Egress seg data fifo overflow - 1,0

Egress seg data fifo overflow on xaui-1

bridge instance-0.

Egress seg data fifo overflow - 1,1

Egress seg data fifo overflow on xaui-1

bridge instance-1.

Egress seg hdr ext fifo overflow - 0,0

Egress seg hdr ext fifo overflow on xaui-0

bridge instance-0.

Egress seg hdr ext fifo overflow - 0,1

Egress seg hdr ext fifo overflow on xaui-0

bridge instance-1.

Egress seg hdr ext fifo overflow - 1,0

Egress seg hdr ext fifo overflow on xaui-1

bridge instance-0.

Egress seg hdr ext fifo overflow - 1,1

Egress seg hdr ext fifo overflow on xaui-1

bridge instance-1.

Egress seg hdr fifo overflow - 0,0

Egress seg hdr fifo overflow on xaui-0

bridge instance-0.

Egress seg hdr fifo overflow - 0,1

Egress seg hdr fifo overflow on xaui-0

bridge instance-1.

Egress seg hdr fifo overflow - 1,0

Egress seg hdr fifo overflow on xaui-1

bridge instance-0.

Egress seg hdr fifo overflow - 1,1

Egress seg hdr fifo overflow on xaui-1

bridge instance-1.

Egress sgt fifo overflow - 0,0

Egress sgt fifo overflow on xaui-0 bridge

instance-0.

Egress sgt fifo overflow - 0,1

Egress sgt fifo overflow on xaui-0 bridge

instance-1.

Egress sgt fifo overflow - 1,0

Egress sgt fifo overflow on xaui-1 bridge

instance-0.

Egress sgt fifo overflow - 1,1

Egress sgt fifo overflow on xaui-1 bridge

instance-1.

Egress sgt hdr ext fifo overflow - 0,0

Egress sgt hdr ext fifo overflow on xaui-0

bridge instance-0.

Egress sgt hdr ext fifo overflow - 0,1

Egress sgt hdr ext fifo overflow on xaui-0

bridge instance-1.

Egress sgt hdr ext fifo overflow - 1,0

Egress sgt hdr ext fifo overflow on xaui-1

bridge instance-0.

Egress sgt hdr ext fifo overflow - 1,1

Egress sgt hdr ext fifo overflow on xaui-1

bridge instance-1.

Egress sgt2 fifo overflow - 0,0

Egress sgt2 fifo overflow on xaui-0 bridge

instance-0.

Egress sgt2 fifo overflow - 0,1

Egress sgt2 fifo overflow on xaui-0 bridge

instance-1.

Egress sgt2 fifo overflow - 1,0

Egress sgt2 fifo overflow on xaui-1 bridge

instance-0.

Egress sgt2 fifo overflow - 1,1

Egress sgt2 fifo overflow on xaui-1 bridge

instance-1.

Non-zero seg profile detected - 0,0

Non-zero seg profile detected on xaui-0

bridge instance-0.

Non-zero seg profile detected - 0,1

Non-zero seg profile detected on xaui-0

bridge instance-1.

Non-zero seg profile detected - 1,0

Non-zero seg profile detected on xaui-1

bridge instance-0.

Non-zero seg profile detected - 1,1

Non-zero seg profile detected on xaui-1

bridge instance-1.

GST jump error - 0

GST jump error on bridge instance-0.

GST jump error - 1

GST jump error on bridge instance-1.

GST PWM timeout - 0

GST PWM not received within 1 ms on

bridge instance-0.

GST PWM timeout - 1

GST PWM not received within 1 ms on

bridge instance-1.

GST SYNC ERR - 0

GST Sync error on bridge instance-0.

GST SYNC ERR - 1

GST Sync error on bridge instance-1.

Ingress invalid length detected - 0

Invalid ingress NPH length detected on

bridge instance-0.

Ingress invalid length detected - 1

Invalid ingress NPH length detected on

bridge instance-1.

Ingress L4 array overflow - 0

L4 array overflow on bridge instance-0.

Ingress L4 array overflow - 1

L4 array overflow on bridge instance-1.

Ingress L4 array underflow - 0

L4 array underflow on bridge instance-0.

Ingress L4 array underflow - 1

L4 array underflow on bridge instance-1.

MAC on NPU-0 receive frame error - 0

MAC on NPU-0 received an errored frame

interface on bridge instance-0.

MAC on NPU-0 receive frame error - 1

MAC on NPU-0 received an errored frame

interface on bridge instance-1.

MAC on NPU-0 receive frame error - 2

MAC on NPU-0 received an errored frame

interface on bridge instance-2.

MAC on NPU-0 receive frame error - 3

MAC on NPU-0 received an errored frame

interface on bridge instance-3.

MAC on NPU-1 receive frame error - 0

MAC on NPU-1 received an errored frame

interface on bridge instance-0.

MAC on NPU-1 receive frame error - 1

MAC on NPU-1 received an errored frame

interface on bridge instance-1.

MAC on NPU-1 receive frame error - 2

MAC on NPU-1 received an errored frame

interface on bridge instance-2.

MAC on NPU-1 receive frame error - 3

MAC on NPU-1 received an errored frame

interface on bridge instance-3.

Multicast page error on bridge-0

Multicast page error on bridge instance-0.

Multicast page error on bridge-1

Multicast page error on bridge instance-1.

Multicast page error on bridge-2

Multicast page error on bridge instance-2.

Multicast page error on bridge-3

Multicast page error on bridge instance-3.

NPU-0 egress flow control DIP2 parity error Egress flow control DIP2 parity error on
-0
NPU-0 interface on bridge instance-0.

NPU-0 egress flow control DIP2 parity error Egress flow control DIP2 parity error on
-1
NPU-0 interface on bridge instance-1.

NPU-0 egress flow control DIP2 parity error Egress flow control DIP2 parity error on
-2
NPU-0 interface on bridge instance-2.

NPU-0 egress flow control DIP2 parity error Egress flow control DIP2 parity error on
-3
NPU-0 interface on bridge instance-3.

NPU-0 egress flow control out-of-sync - 0

Egress flow control out-of-sync on NPU-0

interface on bridge instance-0.

NPU-0 egress flow control out-of-sync - 1

Egress flow control out-of-sync on NPU-0

interface on bridge instance-1.

NPU-0 egress flow control out-of-sync - 2

Egress flow control out-of-sync on NPU-0

interface on bridge instance-2.

NPU-0 egress flow control out-of-sync - 3

Egress flow control out-of-sync on NPU-0

interface on bridge instance-3.

NPU-0 scheduler 0 hang - 0

Scheduler 0 Hang on NPU-0 interface on

bridge instance-0.

NPU-0 timestamp update error - 0

Timestamp update error on NPU-0 interface

on bridge instance-0.

NPU-0 timestamp update error - 1

Timestamp update error on NPU-0 interface

on bridge instance-1.

NPU-1 egress flow control DIP2 parity error Egress flow control DIP2 parity error on
-0
NPU-1 interface on bridge instance-0.

NPU-1 egress flow control DIP2 parity error Egress flow control DIP2 parity error on
-1
NPU-1 interface on bridge instance-1.

NPU-1 egress flow control DIP2 parity error Egress flow control DIP2 parity error on
-2
NPU-1 interface on bridge instance-2.

NPU-1 egress flow control DIP2 parity error Egress flow control DIP2 parity error on
-3
NPU-1 interface on bridge instance-3.

NPU-1 egress flow control out-of-sync - 0

Egress flow control out-of-sync on NPU-1

interface on bridge instance-0.

NPU-1 egress flow control out-of-sync - 1

Egress flow control out-of-sync on NPU-1

interface on bridge instance-1.

NPU-1 egress flow control out-of-sync - 2

Egress flow control out-of-sync on NPU-1

interface on bridge instance-2.

NPU-1 egress flow control out-of-sync - 3

Egress flow control out-of-sync on NPU-1

interface on bridge instance-3.

NPU-1 timestamp update error - 0

Timestamp update error on NPU-1 interface

on bridge instance-0.

NPU-1 timestamp update error - 1

Timestamp update error on NPU-1 interface

on bridge instance-1.

Multi bit mem parity error - 0

Multi bit mem parity error on bridge

instance-0.

Multi bit mem parity error - 1

Multi bit mem parity error on bridge

instance-1.

Single bit mem parity error - 0

Single bit mem parity error on bridge

instance-0.

Single bit mem parity error - 1

Single bit mem parity error on bridge

instance-1.

Multicast write when free page fifo empty - Multicast write when free page fifo empty
0
on bridge instance-0.

Multicast write when free page fifo empty - Multicast write when free page fifo empty
1
on bridge instance-1.

Multicast write when free page fifo empty - Multicast write when free page fifo empty
2
on bridge instance-2.

Multicast write when free page fifo empty - Multicast write when free page fifo empty
3
on bridge instance-3.

Scheduler 0 hang - 0

Scheduler 0 Hang on bridge instance-0.

NPU-0 scheduler 0 hang - 1

Scheduler 0 Hang on bridge instance-1.

Scheduler 1 hang - 0

Scheduler 1 Hang on bridge instance-0.

Scheduler 1 hang - 1

Scheduler 1 Hang on bridge instance-1.

XAUI 0 High Queue full error - 0

Queue full error on XAUI 0 HQ on bridge

instance-0.

XAUI 0 High Queue full error - 1

Queue full error on XAUI 0 HQ on bridge

instance-1.

XAUI 0 High Queue overflow error - 0

Queue overflow error on XAUI 0 HQ on

bridge instance-0.

XAUI 0 High Queue overflow error - 1

Queue overflow error on XAUI 0 HQ on

bridge instance-1.

XAUI 0 High Queue packet length error - 0

Queue packet length error on XAUI 0 HQ on

bridge instance-0.

XAUI 0 High Queue packet length error - 1

Queue packet length error on XAUI 0 HQ on

bridge instance-1.

XAUI 0 High Queue sequence error - 0

Queue sequence error on XAUI 0 HQ on

bridge instance-0.

XAUI 0 High Queue sequence error - 1

Queue sequence error on XAUI 0 HQ on

bridge instance-1.

XAUI 0 Low Queue full error - 0

Queue full error on XAUI 0 LQ on bridge

instance-0.

XAUI 0 Low Queue full error - 1

Queue full error on XAUI 0 LQ on bridge

instance-1.

XAUI 0 Low Queue overflow error - 0

Queue overflow error on XAUI 0 LQ on

bridge instance-0.

XAUI 0 Low Queue overflow error - 1

Queue overflow error on XAUI 0 LQ on

bridge instance-1.

XAUI 0 Low Queue packet length error - 0

Queue packet length error on XAUI 0 LQ on

bridge instance-0.

XAUI 0 Low Queue packet length error - 1

Queue packet length error on XAUI 0 LQ on

bridge instance-1.

XAUI 0 Low Queue sequence error - 0

Queue sequence error on XAUI 0 LQ on

bridge instance-0.

XAUI 0 Low Queue sequence error - 1

Queue sequence error on XAUI 0 LQ on

bridge instance-1.

XAUI 0 Mgmt Queue full error - 0

Queue full error on XAUI 0 MQ on bridge

instance-0.

XAUI 0 Mgmt Queue full error - 1

Queue full error on XAUI 0 MQ on bridge

instance-1.

XAUI 0 Mgmt Queue overflow error - 0

Queue overflow error on XAUI 0 MQ on

bridge instance-0.

XAUI 0 Mgmt Queue overflow error - 1

Queue overflow error on XAUI 0 MQ on

bridge instance-1.

Queue packet length error on XAUI 0 MQ on

XAUI 0 Mgmt Queue packet length error - 0 bridge instance-0.

Queue packet length error on XAUI 0 MQ on

XAUI 0 Mgmt Queue packet length error - 1 bridge instance-1.

XAUI 0 Mgmt Queue sequence error - 0

Queue sequence error on XAUI 0 MQ on

bridge instance-0.

XAUI 0 Mgmt Queue sequence error - 1

Queue sequence error on XAUI 0 MQ on

bridge instance-1.

XAUI 1 High Queue full error - 0

Queue full error on XAUI 1 HQ on bridge

instance-0.

XAUI 1 High Queue full error - 1

Queue full error on XAUI 1 HQ on bridge

instance-1.

XAUI 1 High Queue overflow error - 0

Queue overflow error on XAUI 1 HQ on

bridge instance-0.

XAUI 1 High Queue overflow error - 1

Queue overflow error on XAUI 1 HQ on

bridge instance-1.

XAUI 1 High Queue packet length error - 0

Queue packet length error on XAUI 1 HQ on

bridge instance-0.

XAUI 1 High Queue packet length error - 1

Queue packet length error on XAUI 1 HQ on

bridge instance-1.

XAUI 1 High Queue sequence error - 0

Queue sequence error on XAUI 1 HQ on

bridge instance-0.

XAUI 1 High Queue sequence error - 1

Queue sequence error on XAUI 1 HQ on

bridge instance-1.

XAUI 1 Low Queue full error - 0

Queue full error on XAUI 1 LQ on bridge

instance-0.

XAUI 1 Low Queue full error - 1

Queue full error on XAUI 1 LQ on bridge

instance-1.

XAUI 1 Low Queue overflow error - 0

Queue overflow error on XAUI 1 LQ on

bridge instance-0.

XAUI 1 Low Queue overflow error - 1

Queue overflow error on XAUI 1 LQ on

bridge instance-1.

XAUI 1 Low Queue packet length error - 0

Queue packet length error on XAUI 1 LQ on

bridge instance-0.

XAUI 1 Low Queue packet length error - 1

Queue packet length error on XAUI 1 LQ on

bridge instance-1.

XAUI 1 Low Queue sequence error - 0

Queue sequence error on XAUI 1 LQ on

bridge instance-0.

XAUI 1 Low Queue sequence error - 1

Queue sequence error on XAUI 1 LQ on

bridge instance-1.

XAUI 1 Mgmt Queue full error - 0

Queue full error on XAUI 1 MQ on bridge

instance-0.

XAUI 1 Mgmt Queue full error - 1

Queue full error on XAUI 1 MQ on bridge

instance-1.

XAUI 1 Mgmt Queue overflow error - 0

Queue overflow error on XAUI 1 MQ on

bridge instance-0.

XAUI 1 Mgmt Queue overflow error - 1

Queue overflow error on XAUI 1 MQ on

bridge instance-1.

Queue packet length error on XAUI 1 MQ on

XAUI 1 Mgmt Queue packet length error - 0 bridge instance-0.

Queue packet length error on XAUI 1 MQ on

XAUI 1 Mgmt Queue packet length error - 1 bridge instance-1.

XAUI 1 Mgmt Queue sequence error - 0

Queue sequence error on XAUI 1 MQ on

bridge instance-0.

XAUI 1 Mgmt Queue sequence error - 1

Queue sequence error on XAUI 1 MQ on

bridge instance-1.

Checksum error - 0 from FIA on bridge-0

Checksum error - 0 from FIA on bridge

instance-0.

Checksum error - 0 from FIA on bridge-1

Checksum error - 0 from FIA on bridge

instance-1.

Checksum error - 0 from FIA on bridge-2

Checksum error - 0 from FIA on bridge

instance-2.

Checksum error - 0 from FIA on bridge-3

Checksum error - 0 from FIA on bridge

instance-3.

Checksum error - 1 from FIA on bridge-0

Checksum error - 1 from FIA on bridge

instance-0.

Checksum error - 1 from FIA on bridge-1

Checksum error - 1 from FIA on bridge

instance-1.

Checksum error - 1 from FIA on bridge-2

Checksum error - 1 from FIA on bridge

instance-2.

Checksum error - 1 from FIA on bridge-3

Checksum error - 1 from FIA on bridge

instance-3.

CRC error - 0 from FIA on bridge-0

CRC error - 0 from FIA on bridge instance-0.

CRC error - 0 from FIA on bridge-1

CRC error - 0 from FIA on bridge instance-1.

CRC error - 0 from FIA on bridge-2

CRC error - 0 from FIA on bridge instance-2.

CRC error - 0 from FIA on bridge-3

CRC error - 0 from FIA on bridge instance-3.

CRC error from NPU-0 on bridge-0

CRC error from NPU-0 on bridge instance-0.

CRC error from NPU-0 on bridge-1

CRC error from NPU-0 on bridge instance-1.

CRC error from NPU-0 on bridge-2

CRC error from NPU-0 on bridge instance-2.

CRC error from NPU-0 on bridge-3

CRC error from NPU-0 on bridge instance-3.

CRC error - 1 from FIA on bridge-0

CRC error - 1 from FIA on bridge instance-1.

CRC error - 1 from FIA on bridge-1

CRC error - 1 from FIA on bridge instance-1.

CRC error - 1 from FIA on bridge-2

CRC error - 1 from FIA on bridge instance-2.

CRC error - 1 from FIA on bridge-3

CRC error - 1 from FIA on bridge instance-3.

CRC error from NPU-1 on bridge-0

CRC error from NPU-1 on bridge instance-0.

CRC error from NPU-1 on bridge-1

CRC error from NPU-1 on bridge instance-1.

CRC error from NPU-1 on bridge-2

CRC error from NPU-1 on bridge instance-2.

CRC error from NPU-1 on bridge-3

CRC error from NPU-1 on bridge instance-3.

FIA to NPU-0 packet maximum length error Packet maximum length error on FIA to
-0
NPU-0 interface on bridge instance-0.

FIA to NPU-0 packet maximum length error Packet maximum length error on FIA to
-1
NPU-0 interface on bridge instance-1.

FIA to NPU-0 packet maximum length error Packet maximum length error on FIA to
-2
NPU-0 interface on bridge instance-2.

FIA to NPU-0 packet maximum length error Packet maximum length error on FIA to
-3
NPU-0 interface on bridge instance-3.

FIA to NPU-0 packet minimum length error - Packet minimum length error on FIA to
0
NPU-0 interface on bridge instance-0.

FIA to NPU-0 packet minimum length error - Packet minimum length error on FIA to
1
NPU-0 interface on bridge instance-1.

FIA to NPU-0 packet minimum length error - Packet minimum length error on FIA to
2
NPU-0 interface on bridge instance-2.

FIA to NPU-0 packet minimum length error - Packet minimum length error on FIA to
3
NPU-0 interface on bridge instance-3.

FIA to NPU-1 packet maximum length error Packet maximum length error on FIA to
-0
NPU-1 interface on bridge instance-0.

FIA to NPU-1 packet maximum length error Packet maximum length error on FIA to
-1
NPU-1 interface on bridge instance-1.

FIA to NPU-1 packet maximum length error Packet maximum length error on FIA to
-2
NPU-1 interface on bridge instance-2.

FIA to NPU-1 packet maximum length error Packet maximum length error on FIA to
-3
NPU-1 interface on bridge instance-3.

FIA to NPU-1 packet minimum length error - Packet minimum length error on FIA to
0
NPU-1 interface on bridge instance-0.

FIA to NPU-1 packet minimum length error - Packet minimum length error on FIA to
1
NPU-1 interface on bridge instance-1.

FIA to NPU-1 packet minimum length error - Packet minimum length error on FIA to
2
NPU-1 interface on bridge instance-2.

FIA to NPU-1 packet minimum length error - Packet minimum length error on FIA to
3
NPU-1 interface on bridge instance-3.

Missing EOP-0 from FIA DDR on bridge-0

Missing EOP-0 from FIA DDR on bridge

instance-0.

Missing EOP-0 from FIA DDR on bridge-1

Missing EOP-0 from FIA DDR on bridge

instance-1.

Missing EOP-0 from FIA DDR on bridge-2

Missing EOP-0 from FIA DDR on bridge

instance-2.

Missing EOP-0 from FIA DDR on bridge-3

Missing EOP-0 from FIA DDR on bridge

instance-3.

Missing EOP-0 from XAUI on bridge-0

Missing EOP-0 from XAUI on bridge

instance-0.

Missing EOP-0 from XAUI on bridge-1

Missing EOP-0 from XAUI on bridge

instance-1.

Missing EOP-0 from XAUI on bridge-2

Missing EOP-0 from XAUI on bridge

instance-2.

Missing EOP-0 from XAUI on bridge-3

Missing EOP-0 from XAUI on bridge

instance-3.

Missing EOP-1 from FIA DDR on bridge-0

Missing EOP-1 from FIA DDR on bridge

instance-0.

Missing EOP-1 from FIA DDR on bridge-1

Missing EOP-1 from FIA DDR on bridge

instance-1.

Missing EOP-1 from FIA DDR on bridge-2

Missing EOP-1 from FIA DDR on bridge

instance-2.

Missing EOP-1 from FIA DDR on bridge-3

Missing EOP-1 from FIA DDR on bridge

instance-3.

Missing EOP-1 from XAUI on bridge-0

Missing EOP-1 from XAUI on bridge

instance-0.

Missing EOP-1 from XAUI on bridge-1

Missing EOP-1 from XAUI on bridge

instance-1.

Missing EOP-1 from XAUI on bridge-2

Missing EOP-1 from XAUI on bridge

instance-2.

Missing EOP-1 from XAUI on bridge-3

Missing EOP-1 from XAUI on bridge

instance-3.

NPU-0 is constantly backpressuring bridge

NPU-0 constantly backpressuring bridge - 0 instance-0.

NPU-0 is constantly backpressuring bridge

NPU-0 constantly backpressuring bridge - 1 instance-1.

NPU-0 is constantly backpressuring bridge

NPU-0 constantly backpressuring bridge - 2 instance-2.

NPU-0 is constantly backpressuring bridge

NPU-0 constantly backpressuring bridge - 3 instance-3.

NPU-0 packet maximum length error - 0

Packet maximum length error on NPU-0

interface on bridge instance-0.

NPU-0 packet maximum length error - 1

Packet maximum length error on NPU-0

interface on bridge instance-1.

NPU-0 packet maximum length error - 2

Packet maximum length error on NPU-0

interface on bridge instance-2.

NPU-0 packet maximum length error - 3

Packet maximum length error on NPU-0

interface on bridge instance-3.

NPU-0 packet minimum length error - 0

Packet minimum length error on NPU-0

interface on bridge instance-0.

NPU-0 packet minimum length error - 1

Packet minimum length error on NPU-0

interface on bridge instance-1.

NPU-0 packet minimum length error - 2

Packet minimum length error on NPU-0

interface on bridge instance-2.

NPU-0 packet minimum length error - 3

Packet minimum length error on NPU-0

interface on bridge instance-3.

NPU-0 timestamp core error on bridge - 0

NPU-0 timestamp core error on bridge

instance-0.

NPU-0 timestamp core error on bridge - 1

NPU-0 timestamp core error on bridge

instance-1.

NPU-0 timestamp core error on bridge - 2

NPU-0 timestamp core error on bridge

instance-2.

NPU-0 timestamp core error on bridge - 3

NPU-0 timestamp core error on bridge

instance-3.

NPU-1 is constantly backpressuring bridge

NPU-1 constantly backpressuring bridge - 0 instance-0.

NPU-1 is constantly backpressuring bridge

NPU-1 constantly backpressuring bridge - 1 instance-1.

NPU-1 is constantly backpressuring bridge

NPU-1 constantly backpressuring bridge - 2 instance-2.

NPU-1 is constantly backpressuring bridge

NPU-1 constantly backpressuring bridge - 3 instance-3.

NPU-1 packet maximum length error - 0

Packet maximum length error on NPU-1

interface on bridge instance-0.

NPU-1 packet maximum length error - 1

Packet maximum length error on NPU-1

interface on bridge instance-1.

NPU-1 packet maximum length error - 2

Packet maximum length error on NPU-1

interface on bridge instance-2.

NPU-1 packet maximum length error - 3

Packet maximum length error on NPU-1

interface on bridge instance-3.

NPU-1 packet minimum length error - 0

Packet minimum length error on NPU-1

interface on bridge instance-0.

NPU-1 packet minimum length error - 1

Packet minimum length error on NPU-1

interface on bridge instance-1.

NPU-1 packet minimum length error - 2

Packet minimum length error on NPU-1

interface on bridge instance-2.

NPU-1 packet minimum length error - 3

Packet minimum length error on NPU-1

interface on bridge instance-3.

NPU-1 timestamp core error on bridge - 0

NPU-1 timestamp core error on bridge

instance-0.

NPU-1 timestamp core error on bridge - 1

NPU-1 timestamp core error on bridge

instance-1.

NPU-1 timestamp core error on bridge - 2

NPU-1 timestamp core error on bridge

instance-2.

NPU-1 timestamp core error on bridge - 3

NPU-1 timestamp core error on bridge

instance-3.

Packet length error from FIA for NPU-0 on

bridge-0

Packet length error from FIA for NPU-0 on

bridge instance-0.

Packet length error from FIA for NPU-0 on

bridge-1

Packet length error from FIA for NPU-0 on

bridge instance-1.

Packet length error from FIA for NPU-0 on

bridge-2

Packet length error from FIA for NPU-0 on

bridge instance-2.

Packet length error from FIA for NPU-0 on

bridge-3

Packet length error from FIA for NPU-0 on

bridge instance-3.

Packet length error - 0 from XAUI on bridge- Packet length error - 0 from XAUI on bridge
0
instance-0.

Packet length error - 0 from XAUI on bridge- Packet length error - 0 from XAUI on bridge
1
instance-1.

Packet length error - 0 from XAUI on bridge- Packet length error - 0 from XAUI on bridge
2
instance-2.

Packet length error - 0 from XAUI on bridge- Packet length error - 0 from XAUI on bridge
3
instance-3.

Packet length error from FIA for NPU-1 on

bridge-0

Packet length error from FIA for NPU-1 on

bridge instance-0.

Packet length error from FIA for NPU-1 on

bridge-1

Packet length error from FIA for NPU-1 on

bridge instance-1.

Packet length error from FIA for NPU-1 on

bridge-2

Packet length error from FIA for NPU-1 on

bridge instance-2.

Packet length error from FIA for NPU-1 on

Packet length error - 1 from FIA on bridge-3 bridge instance-3.

Packet length error - 1 from XAUI on bridge- Packet length error - 1 from XAUI on bridge
0
instance-0.

Packet length error - 1 from XAUI on bridge- Packet length error - 1 from XAUI on bridge
1
instance-1.

Packet length error - 1 from XAUI on bridge- Packet length error - 1 from XAUI on bridge
2
instance-2.

Packet length error - 1 from XAUI on bridge- Packet length error - 1 from XAUI on bridge
3
instance-3.

XAUI to NPU-0 fragment error - 0

XAUI interface to NPU-0 reported

fragmentation error on TX side on bridge
instance - 0.

XAUI to NPU-0 fragment error - 1

XAUI interface to NPU-0 reported

fragmentation error on TX side on bridge
instance - 1.

XAUI to NPU-0 fragment error - 2

XAUI interface to NPU-0 reported

fragmentation error on TX side on bridge
instance - 2.

XAUI to NPU-0 fragment error - 3

XAUI interface to NPU-0 reported

fragmentation error on TX side on bridge
instance - 3.

XAUI to NPU-1 fragment error - 0

XAUI interface to NPU-1 reported

fragmentation error on TX side on bridge
instance - 0.

XAUI to NPU-1 fragment error - 1

XAUI interface to NPU-1 reported

fragmentation error on TX side on bridge
instance - 1.

XAUI to NPU-1 fragment error - 2

XAUI interface to NPU-1 reported

fragmentation error on TX side on bridge
instance - 2.

XAUI to NPU-1 fragment error - 3

XAUI interface to NPU-1 reported

fragmentation error on TX side on bridge
instance - 3.

C2C IIF [chars] asic instance [dec] failed on

initialzation.
Hardware initialization failure

C2C IIF encountered an software error:

[chars]

The C2C IIF library encountered an error

which it cannot resolve.

C2C PIF [chars] asic instance [dec] failed

on initialzation.

Hardware initialization failure

C2C PIF encountered an software error:

[chars]

The C2C PIF library encountered an error

which it cannot resolve.

[chars] asic instance [dec] bist block

[chars] ch [dec] failed on BIST[[hex]].

BIST failure

[chars] asic instance [dec] bist block

[chars] ch [dec] failed on BIST[[hex]].

BIST failure

[chars]

provide BIST failure info

[chars] asic instance [dec] bist block

[chars] BIST timedout.

BIST failure

[chars] asic instance [dec] bist block

[chars] BIST timedout.

BIST failure

[chars].

software initialization error

[chars].

software initialization error

Clear alarm from CBC[chars] in slot [chars], Alarm cleared received from CBC, condition
alarm code [chars]\n
has alleviated.

Alarm indication received from CBC. This

may be a serious failure (example: power
sequencer failure), however process may
Raise alarm from CBC[chars] in slot [chars], continue functioning as expected (or
alarm code [chars]\n
successfully retry) despite the failure.

*****Could not open CBC UART device. file

desc = [dec]\n
Informational log only

*****Could not open CBC UART1 device. file

desc = [dec]\n
Informational log only

Canbus-server process exiting in [chars].

[dec], error code [chars]\n

The CAN Bus Server process exited due to

the reason mentioned in the message.

IDPROM cache write overflow detected at

[chars].[dec] on
This is an error message related to the
tx_request_array[[dec]].tx_base_ptr, a retry Canbus Controller processing the received
will be scheduled\n
UART message.

Invalid slot id:[dec] detected at [chars].

[dec] \n

This is an error message related to the

Canbus Controller processing the received
message.

Invalid slot id:[dec] on bus:[dec] detected

at [chars].[dec] \n

This is an error message related to the

Canbus Controller processing the received
message.

Memory corruption detected at [chars].

This is an error message related to the
[dec] on tx_request_array[[dec]],
Canbus Controller processing the received
magic_num expected: [hex], actual [hex]\n UART message.

A message was received and did not match

any outstanding requests and also is not a
standalone message. This is not a critical
Unexpected CBC[chars] message received failure, the process can continue
from slot [chars] [ver [dec].[dec]] for msg functioning as expected despite the
type [dec], id [dec], len [dec]\n
message arrival, message is discarded.
OBFL cache write overflow detected at
[chars].[dec] on
This is an error message related to the
tx_request_array[[dec]].tx_base_ptr, a retry Canbus Controller processing the received
will be scheduled\n
UART message.

The particular operation mentioned in the

message failed due to some reason. This
may be a serious failure, however process
may continue functioning as expected (or
Failed in [chars].[dec], error code [chars]\n successfully retry) despite the failure.

CRC error in Rx message from CBC and

recover by retransmit, throttled count =
[dec]\n

The message received from Canbus

Controller has CRC error computed. This is
indicative of a low level serial device
transmission error. In most cases, the
message is fully recoverable automatically.

Informational condition and/or failure. The

[chars].[dec], CBC Maj Version (Part-A:[dec] process can continue functioning as
Part-B:[dec]) Illegal for node [chars] \n
expected despite the failure.

[chars].[dec], Info - [chars]\n

Informational condition and/or failure. The

process can continue functioning as
expected despite the failure.

[chars] is in RP isolation\n

This is an informational message indicating

that target RP has transitioned into RP
isolation.

CPU reset request ignored for [chars]\n

This is an informational message indicating

that RP Isolation is in force, CPU reset
request for the target slot is ignored.

CBC upgrade completed on [chars]\n

This is an informational message indicating

that Canbus Controller firmware upgrade is
completed on the specified location.

CBC upgrade in progress on [chars], Page

[dec] of range [dec]-[dec]\n

This is an informational message indicating

that Canbus Controller firmware upgrade is
in progress on the specified location. The
page that is being presently upgraded is
mentioned in the message. This page
number would be in the specified range,
corresponding to the Canbus Controller
partition that is being upgraded.

CBC upgrade on [chars]: [chars]\n

This is an informational message related to

the Canbus Controller upgrade process on
the specified location.

Starting CBC upgrade on [chars] with

image [chars]

This is an informational message indicating

that the Canbus Controller firmware on the
specified loation is going to be upgraded
with the image at the specified path.

Node [chars] [chars], [chars] ([hex][hex]

%02x[hex])\n

Informational log only

Node [chars] [chars], [chars] ([hex][hex]

%02x[hex])\n

Informational log only

Debug [chars].[dec], [dec], [dec], error

code [chars]\n

This is a programmed diagnostic debug

message.

ClkCtrl detected an overcurrent condition

on card [chars]

ClkCtrl driver detected a card overcurrent

condition

could not get CS revision info!

Could not get CS revision info

chdir to [chars] failed: [chars]

Chdir failed

module [chars] not available

Module was unavailable to be accessed.

no cards defined

No card information is defined in the

PCMCIA device

no device drivers defined

No device driver is found for the device.

Malloc failure

System is running out of memory. This

message will be for debug only. The out of
memory situation will have other bad
effects upon the router.

no sockets found!

No sockets

PCMCIA initialization error at: \[chars]\

PCMCIA initialization error

select (): [chars]

Select failure

Unsupported card in socket [dec]

product info: [chars]
socket [dec]: [chars]

Unsupported card is found. Only Cisco

approved card can be used
Product info
Socket info

could not adjust resource: [chars]: [chars]

Could not adjust resource

could not open [chars]: [chars]

Open of file failed

bind '[chars]' to socket [dec] failed: [chars] Bind failed

bind MTD '[chars]' to region at [hex] failed:

[chars]
Bind mtd region failed

bind MTD '[chars]' to socket [dec] failed:

[chars]

Bind mtd to socket failed

error parsing CIS([hex]) on socket [dec]:

[chars]

CIS data parsing error

error reading CIS data on socket [dec]:

[chars]

CIS data read error

could not replace CIS: [chars]

CIS replace error

Card Services release does not match

Release mismatch

get device info on socket [dec] failed:

[chars]

Device info failed

open_sock(socket [dec]) failed: [chars]

Open of socket failed

read ([dec]): [chars]

Read failed

Thread create failed: [chars]

Thread create failed

unbind '[chars]' from socket [dec] failed:

[chars]

Unbind failed

unbind MTD '[chars]' from socket [dec]

failed: [chars]

Unbind MTD failed

Event Manager create failed for [chars].

Reason: [chars]

CATAPULT Event Manager create error

Exit on error: [chars]: Caused by [chars]

An error occurred in CATAPULT Driver which

requires exiting (and, hence, restarting) the
process.

CATAPULT Driver encountered a fatal error

and is not able to recover. The supplied
Initialization Error: [chars] Reason: [chars]. text string will explain the reason. Call
Exiting.
support with this text.

Continuing execution: [chars]: Caused by

[chars]

This message indicates an error occurred

beyond which execution of the
catapult_driver may continue, attempting
to effect recovery or work-around
internally, minimizing loss of
information/functionality.

Canbus A and B have failed

CBC detected both CANBUS A and CANBUS

B have failed. This may be a serious
hardware failure.

CBC power sequence failed

The CBC alarm indicating that the power up

sequence has failed. The proper
functioning of the board requires that a
successful application of power be applied
to the board in the proper sequence.

CBC A failed

CBC detected CANBUS A failure. This may

be a serious failure, however the system
may continue functioning as expected
despite the failure.

CBC B failed

CBC detected CANBUS B failure. This may

be a serious failure, however the system
may continue functioning as expected
despite the failure.

CBC inrush fantray has failed

CBC has detected that the inrush fantray

has failed. This will result in the LCs getting
overheated. Please turn off power to the
system.

CBC power fuse has failed

CBC has detected power fuse failure. The

proper functioning of the board requies
that the current drawn be within the rating
of the boards power fuse.

CBC slot id changed

CBC detected unexpected slot id change.

The system can no longer manage/monitor
the card's environment conditions.
Normally this means some HW issue on slot
id pins, there are 6 pins per board to
indicate a valid slot, if any of the pin has
noise which get changed during card
operation, we will see this alert

CBC major version error on node [chars].

Expected=[dec], Actual=[dec]

The CBC on the slot has an incorrect

firmware type programmed. The firmware
major version does not match the card
type.

[chars]: [dec] [chars]

CCI HAL SATORI Packet transmit error.

The cpuctrl (sstar) driver detected an error

CPUCtrl (SSTAR) Initialization failed: [chars] during initialization.

Failed to create event manager

The Fabric driver was unable to create an

event manager for processing messages
and hence failed to initialize. The System
Manager process (sysmgr) will
automatically respawn this (sfe_drvr)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

[chars] priority interrupt thread failed.

Exiting.

The cpuctrl (sstar) driver detected a critical

failure in the interrupt thread initialization.
Abort and exit the thread.

Envmon process exiting because [chars],

error code [chars]\n

The Chassis Control driver process exited

due to the reason mentioned in the
message.

Failed to [chars], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

Unable to powerup card(for node:[chars])

rc: [chars]\n

The hardware powerup was unsuccessful

due to the mentioned reason.

Unable to shutdown card(for node: [chars]) The shutdown of the card was unsuccessful
rc: [chars]\n
due to the mentioned reason.

Unable to shutdown chassis because

[chars]\n

The shutdown of the chassis was

unsuccessful due to the mentioned reason.

Fabric PLD [chars] interrupt detected

instance [dec] Channel [dec] [chars]
register: [hex]\n

The Fabric PLD power fault alarm was

encountered

Fabric PLD [chars] interrupt detected

instance [dec] [chars] register [hex]\n

The Fabric PLD power fault alarm was

encountered

Fan tray mismatch [chars]. Please check

[chars] fan tray.\n

The CRS-8-LCC-B chassis is runing with

different types of fan trays. Please check
the fan tray and make sure both are of
same type.

Voltage validation failed, motherboard did

not power up. Shutting down card.

The voltage validation and power status

check for the card failed. This might be a
power issue to the card or a faulty card.

[chars] Alarm detected on MSC-400G

node([dec]) register: [hex]\n

An LC power alarm was encountered.

[chars] Alarm detected on MSC-400G

node([dec]) register: [hex]\n

An LC temperature alarm was encountered.

Unable to reset SP node([chars]) rc:

[chars]\n

The hard reset of sp was unsuccessful due

to the mentioned reason.

Unable to shutdown the standby node as

part of chassis shutdown\n

The shutdown of the standby SC/RP node

failed during the chassis shutdown process.

[chars] Alarm detected on Taiko

node([dec]) register: [hex]\n

The taiko power alarm was encountered

[chars] Alarm detected on Taiko

node([dec]) register: [hex]\n

The taiko temperature alarm was

encountered

Voltage fix on VP4 could not be activated

for Barbarian SPA in slot [dec]\n

VP4 rail on the SPA could not be margined

to nominal voltage due to some failure.

Envmon process exiting because [chars],

error code [chars]\n

The Chassis Control driver process exited

due to the reason mentioned in the
message.

An I2C failure occurred while trying to clear An I2C failure occurred while trying to clear
the alarm LED(s).\n
one or more of the alarm card LEDs.
Unable to recover from I2C bus hang for
sensor [chars].\n

An I2C bus hang was encountered when

attempting to access a sensor.

An I2C error was encountered when

An I2C failure occurred while trying to clear attempting to clear the fault / alarm
the fault status of Power Module id: [dec].\n information of a Power Module.
An I2C failure occurred while checking the
fault status of Power Module id: [dec].\n

An I2C error was encountered when

attempting to access the fault / alarm
information of a Power Module.

An I2C failure occurred while trying to set

the Power Module presence LED(s).\n

An I2C failure occurred while trying to set

or clear the LEDs of a Power Module in a
power shelf.

This I2C failure indicates that there was a

fault when checking the presence
information for the Power Modules in a
An I2C failure occurred while checking for power shelf. The shelf might have been
the presence of Power Modules in [chars].\n removed or is not inserted correctly.
An I2C error was encountered when
An I2C failure occurred when reading
attempting to read a sensor on a Power
sensor [chars] for Power Module id: [dec].\n Module.
An I2C failure occurred while trying to set
the alarm LED(s).\n

An I2C failure occurred while trying to set

one or more of the alarm card LEDs.

An I2C failure occurred while checking the

zone breaker status in [chars].\n

This I2C failure indicates that a fault

occurred when checking the circuit breaker
status on the shelf.

Exiting because not able to [chars]

mastership\n

The Chassis Control driver process exited

as it was not able to grab mastership or
unable to release it.

Unable to detect power shelf type.

Assuming AC shelf and continuing for now.
Please check EEPROM programming on
power shelf backplane.\n

We are unable to read the power shelf

backplane EEPROM for some reason. Need
to check the programming of the
backplane.

Unknown Controller/Platform type [hex]

read from EEPROM.\n

The value read from the EEPROM does not

match any of the known Controller/platform
type values.

Voltage fix on VP4 active for Barbarian SPA VP4 rail on the SPA is margined to nominal
in slot [dec]\n
voltage due to SAR chip errata.

Power Sequencer [inst: [dec] channel: [dec]

sensor_type: [chars]] detected alarm
The fabric power sequencer detected a
[chars] value: [dec] threshold: [dec]
temperature or power alarm.

Fabric PLD [chars] interrupt detected

instance [dec] Channel [dec] [chars]
register: [hex]\n

The Fabric PLD power alert was

encountered

Unknown shelf ID [hex] read from power

shelf backplane EEPROM - please check
EEPROM programming.\n

The value read from the power shelf

backplane does not match any of the
known shelf ID values. Please check the
EEPROM programming.

[chars]\n

The particular operation mentioned in the

message succeeded.

[chars] alarm occured for [chars] sensor at

temperature [dec] deg C, against
Informational msg indicating temperature
configured threshold of [dec] deg C\n
at which alarm occured.
Invalid temp value read for [chars]
sensor.\n

Informational msg indicating invalid

temperature read

[chars]

During power failures on the card, power

failure interrupts are generated. In
response to this power failure interrupt, the
CCTL module will try to collect the debug
dumps and then move the card to
IN_RESET state. This iosmsg is added to
inform the status of the log collection.

Failed to [chars], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

Switch process failed to register with

deadline monitor, error [chars]

ce-switch process failed to register with

deadline monitor

Intra-rack switch port [dec] state changed

to ADMIN_DOWN

The intra-rack switch port was

administratively shut down.

Intra-rack switch port [dec] state changed

to [chars]

When the process starts, port state

oscillate between up and down and finally
the port state will become up. While
configuring also port link state change
message information displayed. Except the
above two scenarious, if port state change
occurs please contact TAC support.

Hardware fault declared on Switch port

[dec] after maximum recovery attempt.

Software declared hardware fault on the

specified port after the number of autorecovery attempt exceeded the threshold.
The port will be set to UDLD err-disable
state until manually cleared. The fault
could be hardware issues or connection
problem.

Hardware fault declared on Switch port

[dec] after maximum recovery attempt.

Software declared hardware fault on the

specified port after the number of autorecovery attempt exceeded the threshold.
The port will be set to UDLD err-disable
state until manually cleared. The fault
could be hardware issues or connection
problem.

Broadcom switch stacking link down

The driver was unable to successfully

initialise the stacking link

CE_SWITCH DMAC link interface ([dec]) is

down

The internal link interface for the specified

port is down.

Intra-rack switch port [dec] state changed

to ADMIN_DOWN

The intra-rack switch port was

administratively shut down.

Front panel nV Edge Control Port [dec] has

unsupported SFP plugged in.\n Port is
disabled, please plug in Cisco support 1Gig nV Edge Control ports needs Cisco
SFP for port to be enabled
supported SFPs.
\nFront Panel port [dec] error disabled
because of UDLD \nuni directional
forwarding. There will be automatic
\nretries to try and bring up the port
periodically

Front panel SFP port is UDLD UniDirectional, check sfp/fiber for errors

Interface [dec] ([chars]) is [chars]

A link to the RSP control plane switch has

change state.

[chars] : [chars]

An unexpected critical error condition

encountered.

'CE SFP monitor init failed with invalid

board type [hex]'

An unexpected failure occurs in register

notification. If the mentioned board type
does not matches, then failure occurs.

CE SFP monitor init failed with invalid board An unexpected failure in register
type [hex]
notification failed.

[chars] : [chars]

An unexpected condition encountered.

'CE register noification failed ltrace buffer

init : [chars]'

Ltrace initialization failed within INV.

Ltraces may not be printed.

'Control-ethernet external gigabit sfp

[chars] - [chars]'

The control-ethernet external gigabit

ethernet sfp state changed

Control-ethernet external gigabit sfp

[chars] - [chars]

The control-eth ext ge sfp state changed

Ltrace failure in [chars] : [chars]

An unexpected condition encountered.

'[chars]: cemgbl inv trace buffer init failed: Ltrace initialization failed within INV.
[chars]'
Ltraces may not be printed.

[chars] : [chars]

An unexpected error condition

encountered.

'CE register notification failed with cb :

[hex] intf : [hex] num_elements : [hex]'

An unexpected failure occurs in register

notification.

CE register notification failed with cb :

[hex] intf : [hex] num_elements : [hex]

An unexpected failure in register

notification failed.

Hardware error on control-ethernet port

[chars]

Hardware error on CPU control ethernet

port.

The rate of link errors on the control

ethernet port has exceeded the threshold.
High rate of errors on control ethernet port The link should be fixed to avoid disruption
[chars]
in router services.

RP does not have GE connectivity

RP does not have GE connectivity.

Reload/failovers may cause problems.

Statistics: [chars]

Packet tx/rx statistics on CPU control

ethernet port.

There has been a change (toggle) in

'bundle-offload' configuration. Process
cfm process restart required on active RSP restart of cfm is required on active RSP for
for configuration change to take effect
the changes to take effect.

CFP Module for port [dec] is not Cisco

compliant

A compliance error was detected during

CFP initialization. A compliance error is due
to checksum error, EEPROM CRC error,
vendor data error, or decryption error. The
CFP is the pluggable optics on the line
cards. CFP initialization may happen when
linecard boots up, CFP OIR and line card
process restart. The optics will not be
enabled if an CFP compliance error is
detected.

A CFP Module not supported for the port

error was detected during CFP initialization.
A CFP Module not supported for the port
error is reported when Optics is not
supported on the port. The CFP is the
pluggable optics on the line cards. CFP
initialization may happen when linecard
boots up, CFP OIR and line card process
restart. Traffic will not be impacted by this
CFP Module for port [dec] is not supported error.

CFP Module for port [dec] is not a

supported Product ID (PID)

A PID not supported error was detected

during CFP initialization. A PID not support
error is reported when either the PID can
not be read it not supported on the
platform. The CFP is the pluggable optics
on the line cards. CFP initialization may
happen when linecard boots up, CFP OIR
and line card process restart. Traffic will not
be impacted by this error.

CFP Module for port [dec] is not a

supported module type

A supported error was detected during CFP

initialization. A support error is reported
when the CFP type can not be determined
or it is not supported on the platform. The
CFP is the pluggable optics on the line
cards. CFP initialization may happen when
linecard boots up, CFP OIR and line card
process restart. The optics will not be
enabled if an CFP supported error is
detected.

CFP Case High Bias Alarm

Environmental monitoring has detected a

CFP bias greater than or equal to the high
bias alarm threshold. The CFP is the
pluggable optics on the line cards. The bias
threshold values are read from the CFP.

CFP Case High Temperature Alarm

Environmental monitoring has detected a

CFP temperature greater than or equal to
the high temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Case High Voltage Alarm

Environmental monitoring has detected an

CFP voltage greater than or equal to the
high voltage alarm threshold. The CFP is
the pluggable optics on the line cards. The
voltage threshold values are read from the
CFP.

CFP Lane 0 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 0 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 0 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 0 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 0 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 0 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 0 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 0 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 1 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 1 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 1 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 1 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 1 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 1 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 1 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 1 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 10 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 10 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 10 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 10 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 10 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 10 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 10 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 10 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 11 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 11 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 11 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 11 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 11 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 11 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 11 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 11 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 12 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 12 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 12 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 12 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 12 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 12 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 12 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 12 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 13 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 13 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 13 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 13 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 13 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 13 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 13 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 13 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 14 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 14 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 14 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 14 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 14 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 14 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 14 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 14 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 15 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 15 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 15 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 15 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 15 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 15 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 15 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 15 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 2 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 2 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 2 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 2 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 2 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 2 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 2 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 2 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 3 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 3 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 3 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 3 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 3 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 3 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 3 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 3 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 4 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 4 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 4 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 4 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 4 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 4 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 4 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 4 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 5 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 5 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 5 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 5 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 5 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 5 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 5 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 5 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 6 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 6 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 6 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 6 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 6 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 6 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 6 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 6 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 7 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 7 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 7 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 7 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 7 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 7 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 7 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 7 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 8 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 8 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 8 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 8 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 8 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 8 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 8 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 8 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 9 High Bias Alarm

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias alarm threshold. The CFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 9 High Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the CFP.

CFP Lane 9 High Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature alarm
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 9 High Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power alarm threshold. The CFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the CFP.

CFP Lane 9 Low Bias Alarm

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 9 Low Rx Power Alarm

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 9 Low Temperature Alarm

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature alarm threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 9 Low Tx Power Alarm

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power alarm threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Case Low Bias Alarm

Environmental monitoring has detected a

CFP bias less than or equal to the low laser
bias alarm threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Case Low Temperature Alarm

Environmental monitoring has detected an

CFP temperature less than or equal to the
low temperature alarm threshold. The CFP
is the pluggable optics on the line cards.
The temperature threshold values are read
from the CFP.

CFP Case Low Voltage Alarm

Environmental monitoring has detected a

CFP voltage less than or equal to the low
voltage alarm threshold. The CFP is the
pluggable optics on the line cards. The
voltage threshold values are read from the
CFP.

CFP Case High Bias Warning

Environmental monitoring has detected a

CFP bias greater than or equal to the high
bias warning threshold. The CFP is the
pluggable optics on the line cards. The bias
threshold values are read from the CFP.

CFP Case High Temperature Warning

Environmental monitoring has detected a

CFP temperature greater than or equal to
the high temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Case High Voltage Warning

Environmental monitoring has detected a

CFP voltage greater than or equal to the
high voltage warning threshold. The CFP is
the pluggable optics on the line cards. The
voltage threshold values are read from the
CFP.

CFP Lane 0 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 0 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 0 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 0 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 0 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 0 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 0 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 0 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 1 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 1 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 1 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 1 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 1 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 1 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 1 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 1 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 10 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 10 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 10 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 10 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 10 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 10 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 10 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 10 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 11 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 11 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 11 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 11 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 11 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 11 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 11 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 11 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 12 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 12 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 12 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 12 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 12 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 12 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 12 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 12 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 13 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 13 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 13 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 13 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 13 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 13 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 13 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 13 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 14 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 14 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 14 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 14 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 14 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 14 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 14 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 14 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 15 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 15 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 15 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 15 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 15 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 15 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 15 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 15 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 2 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 2 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 2 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 2 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 2 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 2 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 2 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 2 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 3 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 3 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 3 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 3 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 3 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 3 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 3 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 3 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 4 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 4 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 4 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 4 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 4 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 4 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 4 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 4 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 5 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 5 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 5 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 5 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 5 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 5 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 5 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 5 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 6 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 6 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 6 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 6 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 6 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 6 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 6 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 6 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 7 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 7 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 7 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 7 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 7 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 7 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 7 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 7 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 8 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 8 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 8 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 8 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 8 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 8 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 8 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 8 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Lane 9 High Bias Warning

Environmental monitoring has detected a

CFP laser bias greater than or equal to the
high laser bias warning threshold. The CFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the CFP.

CFP Lane 9 High Rx Power Warning

Environmental monitoring has detected a

CFP Rx power greater than or equal to the
high Rx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the CFP.

CFP Lane 9 High Temperature Warning

Environmental monitoring has detected a

CFP laser temperature greater than or
equal to the high temperature warning
threshold. The CFP is the pluggable optics
on the line cards. The temperature
threshold values are read from the CFP.

CFP Lane 9 High Tx Power Warning

Environmental monitoring has detected a

CFP Tx power greater than or equal to the
high Tx power warning threshold. The CFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the CFP.

CFP Lane 9 Low Laser Bias Warning

Environmental monitoring has detected a

CFP laser bias less than or equal to the low
laser bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Lane 9 Low Rx Power Warning

Environmental monitoring has detected a

CFP Rx power less than or equal to the low
Rx power warning threshold. The CFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
CFP.

CFP Lane 9 Low Temperature Warning

Environmental monitoring has detected a

CFP laser temperature less than or equal to
the low temperature warning threshold.
The CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Lane 9 Low Tx Power Warning

Environmental monitoring has detected a

CFP Tx power less than or equal to the low
Tx power warning threshold. The CFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
CFP.

CFP Low Laser Bias Warning

Environmental monitoring has detected a

CFP bias less than or equal to the low laser
bias warning threshold. The CFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the CFP.

CFP Case Low Temperature Warning

Environmental monitoring has detected an

CFP temperature less than or equal to the
low temperature warning threshold. The
CFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the CFP.

CFP Case Low Voltage Warning

Environmental monitoring has detected a

CFP voltage less than or equal to the low
voltage warning threshold. The CFP is the
pluggable optics on the line cards. The
voltage threshold values are read from the
CFP.

[chars] [hex]

An error occurred in initialization of CGV6

Services . If this occurred during process
startup or RP Switchover, then the process
may be restarted.

[chars]

An error occurred in initialization of CGV6

Services . If this occurred during process
startup or RP Switchover, then the process
may be restarted.

The message indicates, the supplied ltrace

pathname is not a valid one. This error
should not impact any major functionality.
The message will indicate the cause of the
cgv6_services_show_ltrace: [chars] [chars] error.

[chars]: [chars]: [hex]

A fatal error occurred in the cgv6 services

process which involves exiting the process.

cgv6_services error: [chars]

An error occurred in the cgv6 services

process during process initialization or
process communication.

[chars]

This is a debug message in the CGV6

SERVICE PROCESS to indicate anomolies
which are not FATAL. Some of the messages
may indicate a failure to allocate resources
needed by applications. In many cases
these messages must not keep appearing
after the temperory situation is resolved.

[chars]: [chars] errno [dec]

This is a debug message in the CGV6

SERVICES PROCESS to indicate anomolies
which are not FATAL. Some of the messages
may indicate a failure to allocate resources
needed by applications. In many cases
these messages must not keep appearing
after the temperory situation is resolved.

[chars] [hex]

A generic error occurred in Services CGV6

SERVICE. Cause of the error will be
mentioned in the message displayed.

Info: [chars]

The message is used to report generic info

about Services CGV6 SERVICES.

When a hardware fault occurs and the

device driver cannot correct it, the Platform
Manager is required to reset the ASICs. This
error indicates that the Platform Manager
failed to reset the ASICs and the hardware
on the PRP may not be in an operational
The fault recovery procedure for the ToFab state. This condition affects the
component of the fabric driver has failed. functionality of the entire router. %s is the
The root fault was: [chars]
Interrupt Source.

chopper dll: block: [chars], entity: [chars]

had CRC error, count: [dec]

PII block got a packet from the entity

mentioned above with a CRC error.

TFQ: device halted, sub-block: [chars],

halted entity: [chars]

TFQ, ASIC got halted. The halted block and

its parent block are provided

This message indicates that the Chopper

hardware found a DMA problem. The
hexadecimal data indicates the error
register value when the problem is
detected. This usually indicates a hardware
Chopper detected a DMA error: Data [hex] error.

chopper dll: fatal error encountered,

reason=[chars]

iqm, chopper dll manager encountered a

fatal error and is not able recover from the
error. A reason text will be supplied call
support with this text.

chopper dll: fatal error encountered,

reason=[chars], errno=[dec]

chopper encountered a fatal error and is

not able to recover from the error. A reason
text will be supplied call support with this
text. An integer errno will also be printed.

Chopper detected a Fusilli parity error:

Data [hex]

A parity error has been detected on the

Chopper to Fusilli interface. The hex
number indicates the error cause register
value. This usually indicates a hardware
problem on the RP. RP may be reset.

chopper dll: general information,<[chars]> The CHP's informational message.

chopper dll: hardware initialization not

complete

hardware init is not complete.

chopper dll: service degrading error, reason The chopper encountered an error that
= [chars]
would lead to degraded service.

chopper dll: intr enable at addr: [hex]

mask: [hex] failed.

hardware state is not correct.

chopper dll: intr status get failed for:

[chars]@[hex], rc=[dec]

Hardware register read failed.

chopper dll: fatal memory allocation error

for <[dec]> bytes

CHP encountered a fatal memory allocation

error

chopper dll: asic is not available

hardware state is not correct.

chopper dll: asic is not operational, state:

[dec]

hardware state is not correct.

chopper dll: this function <[chars]> is not

yet implemented

TFQ, chopper dll , a function is not

implemented.

Chopper detected a PCI error: Data [hex]

A PCI error has been detected by the

Chopper PCI interface. The hex number
indicates the error cause register value.
This usually indicates a hardware problem
on the RP. RP may be reset.

Chopper detected a SRAM parity error:

Data [hex]

A parity error has been detected on the

Chopper to SRAM interface. The hex
number indicates the error cause register
value. This usually indicates a hardware
problem on the RP. RP may be reset.

chopper dll: halt not handled, parent:

[chars], child: [chars], intr: [dec]

Hardware halt is not handled.

chopper dll: intr not handled, parent:

[chars], child: [chars], group id: [dec], intr: Hardware interrupt is not handled in the
[dec]
code, need to implement.
[chars][[dec]]: reload board due to too
many reset

Mulitple reset occurred, need to reload

board

[chars][[dec]]: reload board due to too

many reset

Mulitple reset occurred, need to reload

board

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need to

reload system

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and need to

reload system

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need to

reload system

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need to

reload system

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need to

reload system

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and need to

reload system

[chars][[dec]]: Reset threshold is crossed

Mulitple reset occurred, threshold exceeds

[chars][[dec]]: Reset threshold is crossed

Mulitple reset occurred, threshold exceeds

[chars][[dec]]: Reset threshold is crossed

Mulitple reset occurred, threshold exceeds

[chars][[dec]]: Reset threshold is crossed

Mulitple reset occurred, threshold exceeds

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and board need

shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and board need

shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and board need

shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and board need

shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and board need

shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and board need

shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need a hard

reset.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need a hard

reset.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and need a hard

reset.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need a hard

reset.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need a hard

reset.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and need a hard

reset.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and need a

power on reset.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need a

power on reset.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need a

power on reset.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need a

power on reset.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need a

power on reset.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and need a

power on reset.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need

reprogram resource.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need

reprogram resource.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need

reprogram resource.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and need

reprogram resource.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need

reprogram resource.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and need

reprogram resource.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors need to reprogram resource

have happened, such errors has crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors need to reprogram resource

have happened, such errors has crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors need to reprogram resource

have happened, such errors has crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

ASIC errors need to reprogram resource

have happened, such errors has crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors need to reprogram resource

have happened, such errors has crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

ASIC errors need to reprogram resource

have happened, such errors has crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause

retrain link.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause

retrain link.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause

retrain link.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause

retrain link.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause

retrain link.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause

retrain link.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and need

memory scrubbing, such errors have
crossed threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and need

memory scrubbing, such errors have
crossed threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

ASIC errors have occured and need

memory scrubbing, such errors have
crossed threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and need

memory scrubbing, such errors have
crossed threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and need

memory scrubbing, such errors have
crossed threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

ASIC errors have occured and need

memory scrubbing, such errors have
crossed threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause fabric

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause fabric

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause fabric

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause fabric

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause fabric

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause fabric

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause ilte

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause ilte

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause ilte

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause ilte

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause ilte

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause ilte

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and been

handled. Such errors have crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

ASIC errors have occured and been

handled. Such errors have crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and been

handled. Such errors have crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and been

handled. Such errors have crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and been

handled. Such errors have crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

ASIC errors have occured and been

handled. Such errors have crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error threshold was crossed.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error threshold was crossed.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error threshold was crossed.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error threshold was crossed.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error threshold was crossed.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error threshold was crossed.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need to

reload board

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need to

reload board

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and need to

reload board

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need to

reload board

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need to

reload board

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and need to

reload board

[chars][[dec]]: device is not recovered from An ASIC error has occured and cause board
fault - and reload is requested.
reload.
[chars][[dec]]: device is not recovered from An ASIC error has occured and cause board
fault - and reload is requested.
reload.
[chars][[dec]]: device is not recovered from An ASIC error has occured and cause board
fault - and reload is requested.
reload.
[chars][[dec]]: device is not recovered from An ASIC error has occured and cause board
fault - and reload is requested.
reload.
[chars][[dec]]: device is not recovered from An ASIC error has occured and cause board
fault - and reload is requested.
reload.
[chars][[dec]]: device is not recovered from An ASIC error has occured and cause board
fault - and reload is requested.
reload.
[chars][[dec]]: [chars] error has
occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause ilte

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause ilte

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause ilte

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause ilte

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause ilte

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause ilte

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and hard reset is

needed.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and hard reset is

needed.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and hard reset is

needed.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and hard reset is

needed.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and hard reset is

needed.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and hard reset is

needed.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and power on

reset is needed

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and power on

reset is needed

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and power on

reset is needed

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and power on

reset is needed

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and power on

reset is needed

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and power on

reset is needed

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause fabric

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause fabric

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause fabric

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause fabric

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause fabric

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause fabric

link shutdown.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

ASIC errors have occured and been

handled. Such error have crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and been

handled. Such error have crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and been

handled. Such error have crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and been

handled. Such error have crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and been

handled. Such error have crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

ASIC errors have occured and been

handled. Such error have crossed
threshold.

[chars]

The CIH library encountered an error

related to memory or data value.

[chars]

The CIH library encountered an error

related to memory or data value.

[chars]

The CIH library encountered an error

related to memory or data value.

[chars]

The CIH library encountered an error

related to memory or data value.

[chars]

The CIH library encountered an error

related to memory or data value.

[chars]

The CIH library encountered an error

related to memory or data value.

Leaf node [chars] do not have mem info

Missing mem_info while processing error

interrupt.

Leaf node [chars] do not have mem info

Missing mem_info while processing error

interrupt.

Leaf node [chars] do not have mem info

Missing mem_info while processing error

interrupt.

Leaf node [chars] do not have mem info

Missing mem_info while processing error

interrupt.

Leaf node [chars] do not have mem info

Missing mem_info while processing error

interrupt.

Leaf node [chars] do not have mem info

Missing mem_info while processing error

interrupt.

[chars][[dec]]: multiple stuck

bits([unsigned int]) failure in memory
'[chars]'.

Multiple stuck bit is detected in DRAM.

[chars][[dec]]: multiple stuck

bits([unsigned int]) failure in memory
'[chars]'.

Multiple stuck bit is detected in DRAM.

[chars][[dec]]: multiple stuck

bits([unsigned int]) failure in memory
'[chars]'.

Multiple stuck bit is detected in DRAM.

[chars][[dec]]: multiple stuck

bits([unsigned int]) failure in memory
'[chars]'.

Multiple stuck bit is detected in DRAM.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and been

handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and been

handled.

ASIC SCAN is needed due to ASIC error

[hex] with instance [dec]

An ASIC error which requires ASIC SCAN

has occured, the ASIC SCAN will be
triggered.

ASIC SCAN is needed due to ASIC error

[hex] with instance [dec]

An ASIC error which requires ASIC SCAN

has occured, the ASIC SCAN will be
triggered.

ASIC SCAN is needed due to ASIC error

[hex] with instance [dec]

An ASIC error which requires ASIC SCAN

has occured, the ASIC SCAN will be
triggered.

ASIC SCAN is needed due to ASIC error

[hex] with instance [dec]

An ASIC error which requires ASIC SCAN

has occured, the ASIC SCAN will be
triggered.

ASIC SCAN is needed due to ASIC error

[hex] with instance [dec]

An ASIC error which requires ASIC SCAN

has occured, the ASIC SCAN will be
triggered.

ASIC SCAN is needed due to ASIC error

[hex] with instance [dec]

An ASIC error which requires ASIC SCAN

has occured, the ASIC SCAN will be
triggered.

[chars][[dec]]: HARD_RESET needed [hex]

An ASIC error has occured and need to hard

reset, this marks the beginning of it.

[chars][[dec]]: HARD_RESET needed [hex]

An ASIC error has occured and need to hard

reset, this marks the beginning of it.

[chars][[dec]]: HARD_RESET needed [hex]

An ASIC error has occured and need to hard

reset, this marks the beginning of it.

[chars][[dec]]: HARD_RESET needed [hex]

An ASIC error has occured and need to hard

reset, this marks the beginning of it.

[chars][[dec]]: HARD_RESET needed [hex]

An ASIC error has occured and need to hard

reset, this marks the beginning of it.

[chars][[dec]]: HARD_RESET needed [hex]

An ASIC error has occured and need to hard

reset, this marks the beginning of it.

[chars][[dec]]: PON_RESET needed [hex]

An ASIC error has occured and need power

on reset, this mark the beginning of it.

[chars][[dec]]: PON_RESET needed [hex]

An ASIC error has occured and need power

on reset, this mark the beginning of it.

[chars][[dec]]: PON_RESET needed [hex]

An ASIC error has occured and need power

on reset, this mark the beginning of it.

[chars][[dec]]: PON_RESET needed [hex]

An ASIC error has occured and need power

on reset, this mark the beginning of it.

[chars][[dec]]: PON_RESET needed [hex]

An ASIC error has occured and need power

on reset, this mark the beginning of it.

[chars][[dec]]: PON_RESET needed [hex]

An ASIC error has occured and need power

on reset, this mark the beginning of it.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause

reprogram resource, such error has crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause

reprogram resource, such error has crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause

reprogram resource, such error has crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause

reprogram resource, such error has crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause

reprogram resource, such error has crossed
threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause

reprogram resource, such error has crossed
threshold.

[chars][[dec]]: notification of exceeded

reset threshold is sent to the driver

Multiple reset occurred, threshold exceeds,

notification is sent to driver for proper
action

[chars][[dec]]: notification of exceeded

reset threshold is sent to the driver

Multiple reset occurred, threshold exceeds,

notification is sent to driver for proper
action

[chars][[dec]]: notification of exceeded

reset threshold is sent to the driver

Multiple reset occurred, threshold exceeds,

notification is sent to driver for proper
action

[chars][[dec]]: notification of exceeded

reset threshold is sent to the driver

Multiple reset occurred, threshold exceeds,

notification is sent to driver for proper
action

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause

retrain link.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause

retrain link.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause

retrain link.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and cause

retrain link.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause

retrain link.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and cause

retrain link.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

ASIC errors have occured and need

memory scrubbing, such errors have
crossed threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and need

memory scrubbing, such errors have
crossed threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and need

memory scrubbing, such errors have
crossed threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and need

memory scrubbing, such errors have
crossed threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have occured and need

memory scrubbing, such errors have
crossed threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

ASIC errors have occured and need

memory scrubbing, such errors have
crossed threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error that need special handling

has occured and been handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error that need special handling

has occured and been handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error that need special handling

has occured and been handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error that need special handling

has occured and been handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error that need special handling

has occured and been handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error that need special handling

has occured and been handled.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have exceed the threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have exceed the threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have exceed the threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

ASIC errors have exceed the threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

ASIC errors have exceed the threshold.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

ASIC errors have exceed the threshold.

[chars][[dec]]: single stuck bit failure in

[chars].

A stuck bit is detected in DRAM.

[chars][[dec]]: single stuck bit failure in

[chars].

A stuck bit is detected in DRAM.

[chars][[dec]]: single stuck bit failure in

[chars].

A stuck bit is detected in DRAM.

[chars][[dec]]: single stuck bit failure in

[chars].

A stuck bit is detected in DRAM.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and need to

reprogram resource.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need to

reprogram resource.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need to

reprogram resource.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need to

reprogram resource.

[chars][[dec]]: [chars] error has

occurred[chars]%s [chars] [chars] [chars]

An ASIC error has occured and need to

reprogram resource.

[chars][[dec]]: [chars] error has

occurred[chars]%s [hex] [chars] [chars]

An ASIC error has occured and need to

reprogram resource.

Timing driver version is not compatible

with the hardware FPGA version. S/W ver:
[dec]:[dec] H/W ver: [dec]:[dec]

Timing driver software version is not

compatible with the hardware FPGA
version.

ClkCtrl detected an EEPROM overcurrent

condition

ClkCtrl detected an EEPROM overcurrent

condition

Timing software detected a parity error

address=[dec] data=[dec]

Timing software detected a parity error

from interrupt controller

The 64k composite clock signal has been

Invalid signal received for Rx mode [chars] invalidated possibly due to loss-of-signal
on \ sync [dec] clock-interface
condition or AMI violations.

The 64k composite clock signal has been

Invalid signal received for Rx mode [chars] invalidated possibly due to loss-of-signal
on \ sync [dec] clock-interface
condition or AMI violations.
The clock-control T0 PLL (reference clock
for all interfaces) \ is [chars] FREERUN
mode.

No external reference frequency is

available for synchronization, so the T0 PLL
output is free-running.

The clock-control T0 PLL (reference clock

for all interfaces) \ is [chars] HOLDOVER
mode.

No external reference frequency is

available for synchronization, so the T0 PLL
output is in holdover, maintaining the
most-recent frequency to which it was
locked.

The clock-control T4 PLL (reference clock

for Sync 0 and \ Sync 1 ports) is [chars]
FREERUN mode.

No external reference frequency is

available for synchronization, so the T4 PLL
output is free-running.

The BITS receiver has detected AIS defect

for incoming signal. AIS is usually an
unframed all-ones signal. For T1 mode AIS
is declared when the BITS receiver detects
four or fewer zeroes in a 3ms period. For E1
Alarm indication signal condition observed mode AIS is declared when the BITS
for Rx mode [chars] on \ sync [dec] clock- receiver detects fewer than three zeroes in
interface
two E1 frames.

The BITS receiver has detected AIS defect

for incoming signal. AIS is usually an
unframed all-ones signal. For T1 mode AIS
is declared when the BITS receiver detects
four or fewer zeroes in a 3ms period. For E1
Alarm indication signal condition observed mode AIS is declared when the BITS
for Rx mode [chars] on \ sync [dec] clock- receiver detects fewer than three zeroes in
interface
two E1 frames.

Frame error rate exceeded condition

observed for \ Rx mode [chars] on sync
[dec] clock-interface

For UTI mode alarm is raised if frame error

rate exceeds 2%.

Frame error rate exceeded condition

observed for \ Rx mode [chars] on sync
[dec] clock-interface

For UTI mode alarm is raised if frame error

rate exceeds 2%.

Invalid 10MHz input clock observed for Rx

mode [chars] on \ sync [dec] clockinterface

The 10MHz UTC clock signal has been

invalidated possibly due to loss-of-signal
condition, offset out of range or phase lock
issue.

Loss of frame condition observed for Rx

mode [chars] on sync [dec] \ clockinterface

The BITS receiver has detected OOF defect

for incoming signal. For T1 mode OOF is
declared when out of every four frame bits
two or more frame bits are received in
error. For E1 mode OOF is declared when
three consecutive incorrect FAS is received.
Also for E1 mode(CRC-4 framing) OOF can
be declared when 915 or more CRC blocks
out of 1000 are received in error.
Additionally for E1 mode(CAS signalling)
OOF can be declared when two consecutive
multiframe alignment words are received in
error or, for a period of one multiframe, all
bits in timeslot 16 are zero.

Loss of frame condition observed for Rx

mode [chars] on sync [dec] \ clockinterface

The BITS receiver has detected OOF defect

for incoming signal. For T1 mode OOF is
declared when out of every four frame bits
two or more frame bits are received in
error. For E1 mode OOF is declared when
three consecutive incorrect FAS is received.
Also for E1 mode(CRC-4 framing) OOF can
be declared when 915 or more CRC blocks
out of 1000 are received in error.
Additionally for E1 mode(CAS signalling)
OOF can be declared when two consecutive
multiframe alignment words are received in
error or, for a period of one multiframe, all
bits in timeslot 16 are zero.

Loss of signal condition observed for Rx

mode [chars] on sync [dec] \ clockinterface

For T1 mode LOS is declared (as detected

by BITS receiver) when no pulses are
detected in a window of 192 consecutive
pulse intervals. In E1 and 2048kHz modes
LOS is declared when no pulses are
detected in a window of 255 consecutive
pulse intervals. For UTI mode, LOS is
detected by hardware as per J.211
specifications.

Loss of signal condition observed for Rx

mode [chars] on sync [dec] \ clockinterface

For T1 mode LOS is declared (as detected

by BITS receiver) when no pulses are
detected in a window of 192 consecutive
pulse intervals. In E1 and 2048kHz modes
LOS is declared when no pulses are
detected in a window of 255 consecutive
pulse intervals. For UTI mode, LOS is
detected by hardware as per J.211
specifications.

The specified [chars] TOD message

received at input port indicates no \
satellite availability for sync [dec] clockinterface

The received and parsed GPS TOD

message frame from external equipment
indicates no satellite availablity, which
could possibly indicate that the time-of-day
received is not synchronized to a UTC/TAI
timescale.

No TOD messages in the specified [chars]

format are received on \ sync [dec] clockinterface

No TOD messages are being detected on

the GPS port UART receiver.

Remote alarm indication condition

observed for Rx mode [chars] on \ sync
[dec] clock-interface

The BITS receiver has detected RAI defect

for incoming signal. Receiving remote
alarm indication(RAI) means the far-end
equipment over the T1/E1 line has a
problem with the signal it is receiving from
the upstream equipment.

Remote alarm indication condition

observed for Rx mode [chars] on \ sync
[dec] clock-interface

The BITS receiver has detected RAI defect

for incoming signal. Receiving remote
alarm indication(RAI) means the far-end
equipment over the T1/E1 line has a
problem with the signal it is receiving from
the upstream equipment.

Transmit open circuit condition observed

for Tx mode [chars] on \ sync [dec] clockinterface

BITS transmitter has detected an open

circuit condition.

Transmit open circuit condition observed

for Tx mode [chars] on \ sync [dec] clockinterface

BITS transmitter has detected an open

circuit condition.

Transmit short circuit condition observed

for Tx mode [chars] on \ sync [dec] clockinterface

Condition raised by BITS transmitter when

internal short-circuit resistance is approx
25 ohms or less.

Transmit short circuit condition observed

for Tx mode [chars] on \ sync [dec] clockinterface

Condition raised by BITS transmitter when

internal short-circuit resistance is approx
25 ohms or less.

Incorrect frame alignment condition

observed for Tx mode \ [chars] on sync
[dec] clock-interface.

Condition raised possibly due to incorrect

internal BITS transmitter configuration.

Incorrect frame alignment condition

observed for Tx mode \ [chars] on sync
[dec] clock-interface.

Condition raised possibly due to incorrect

internal BITS transmitter configuration.

Incorrect multi-frame alignment condition

observed for Tx mode \ [chars] on sync
[dec] clock-interface.

Condition raised possibly due to incorrect

internal BITS transmitter configuration.

Incorrect multi-frame alignment condition

observed for Tx mode \ [chars] on sync
[dec] clock-interface.

Condition raised possibly due to incorrect

internal BITS transmitter configuration.

Transmit pulse density violation condition

observed for Tx mode \ [chars] on sync
[dec] clock-interface

In T1 mode TPDV alarm is raised when the

transmit data stream does not meet ANSI
T1.403 requirements for transmit pulse
density.

Transmit pulse density violation condition

observed for Tx mode \ [chars] on sync
[dec] clock-interface

In T1 mode TPDV alarm is raised when the

transmit data stream does not meet ANSI
T1.403 requirements for transmit pulse
density.

ClkCtrl Driver encountered an initialization

error and may not operate correctly. The
Initialization Error: [chars] Reason: [chars]. supplied text string will explain the reason.
Exiting.
Call support with this text.

ClkCtrl Driver initialization failed: [chars]

Reason: [chars].

ClkCtrl Driver encountered an initialization

error.

Error Allocating <[dec]> bytes of memory

ClkCtrl encountered a fatal memory

allocation error

Alarm [chars]. Invalid 10MHz input clock

received for Rx mode [chars] on \ sync
[dec] clock-interface

The 10MHz UTC clock signal has been

invalidated possibly due to loss-of-signal
condition, offset out of range or phase lock
issue.

Alarm [chars]. Invalid 10MHz input clock

received for Rx mode [chars] on \ sync
[dec] clock-interface

The 10MHz UTC clock signal has been

invalidated possibly due to loss-of-signal
condition, offset out of range or phase lock
issue.

Invalid signal [chars] for Rx mode [chars]

on \ sync [dec] clock-interface

The 64k composite clock signal has been

invalidated possibly due to loss-of-signal
condition or AMI violations.

Invalid signal [chars] for Rx mode [chars]

on \ sync [dec] clock-interface

The 64k composite clock signal has been

invalidated possibly due to loss-of-signal
condition or AMI violations.

Invalid signal [chars] for Rx mode [chars]

on \ sync [dec] clock-interface

The 64k composite clock signal has been

invalidated possibly due to loss-of-signal
condition or AMI violations.

Alarm [chars]. The specified [chars] TOD

message received at input port inidicates
no \ satellite availability for sync [dec]
clock-interface

The received and parsed GPS TOD

message frame from external equipment
indicates no satellite availablity, which
could possibly indicate that the time-of-day
received is not synchronized to a UTC/TAI
timescale.

Alarm [chars]. The specified [chars] TOD

message received at input port inidicates
no \ satellite availability for sync [dec]
clock-interface

The received and parsed GPS TOD

message frame from external equipment
indicates no satellite availablity, which
could possibly indicate that the time-of-day
received is not synchronized to a UTC/TAI
timescale.

Alarm [chars]. No TOD messages in the

specified [chars] format are received on \
sync [dec] clock-interface

No TOD messages are being detected on

the GPS port UART receiver.

Alarm [chars]. No TOD messages in the

specified [chars] format are received on \
sync [dec] clock-interface

No TOD messages are being detected on

the GPS port UART receiver.

The BITS receiver has detected AIS defect

for incoming signal. AIS is usually an
unframed all-ones signal. For T1 mode AIS
is declared when the BITS receiver detects
four or fewer zeroes in a 3ms period. For E1
Alarm indication signal condition [chars] for mode AIS is declared when the BITS
Rx mode [chars] on \ sync [dec] clockreceiver detects fewer than three zeroes in
interface
two E1 frames.

The BITS receiver has detected AIS defect

for incoming signal. AIS is usually an
unframed all-ones signal. For T1 mode AIS
is declared when the BITS receiver detects
four or fewer zeroes in a 3ms period. For E1
Alarm indication signal condition [chars] for mode AIS is declared when the BITS
Rx mode [chars] on \ sync [dec] clockreceiver detects fewer than three zeroes in
interface
two E1 frames.

The BITS receiver has detected AIS defect

for incoming signal. AIS is usually an
unframed all-ones signal. For T1 mode AIS
is declared when the BITS receiver detects
four or fewer zeroes in a 3ms period. For E1
Alarm indication signal condition [chars] for mode AIS is declared when the BITS
Rx mode [chars] on \ sync [dec] clockreceiver detects fewer than three zeroes in
interface
two E1 frames.
Frame error rate exceeded condition
[chars] for \ Rx mode [chars] on sync [dec] For UTI mode alarm is raised if frame error
clock-interface
rate exceeds 2%.
Frame error rate exceeded condition
[chars] for \ Rx mode [chars] on sync [dec] For UTI mode alarm is raised if frame error
clock-interface
rate exceeds 2%.
Frame error rate exceeded condition
[chars] for \ Rx mode [chars] on sync [dec] For UTI mode alarm is raised if frame error
clock-interface
rate exceeds 2%.

The BITS receiver has detected OOF defect

for incoming signal. For T1 mode OOF is
declared when out of every four frame bits
two or more frame bits are received in
error. For E1 mode OOF is declared when
three consecutive incorrect FAS is received.
Also for E1 mode(CRC-4 framing) OOF can
be declared when 915 or more CRC blocks
out of 1000 are received in error.
Additionally for E1 mode(CAS signalling)
OOF can be declared when two consecutive
multiframe alignment words are received in
Loss of frame condition [chars] for Rx mode error or, for a period of one multiframe, all
[chars] on sync [dec] \ clock-interface
bits in timeslot 16 are zero.

The BITS receiver has detected OOF defect

for incoming signal. For T1 mode OOF is
declared when out of every four frame bits
two or more frame bits are received in
error. For E1 mode OOF is declared when
three consecutive incorrect FAS is received.
Also for E1 mode(CRC-4 framing) OOF can
be declared when 915 or more CRC blocks
out of 1000 are received in error.
Additionally for E1 mode(CAS signalling)
OOF can be declared when two consecutive
multiframe alignment words are received in
Loss of frame condition [chars] for Rx mode error or, for a period of one multiframe, all
[chars] on sync [dec] \ clock-interface
bits in timeslot 16 are zero.

The BITS receiver has detected OOF defect

for incoming signal. For T1 mode OOF is
declared when out of every four frame bits
two or more frame bits are received in
error. For E1 mode OOF is declared when
three consecutive incorrect FAS is received.
Also for E1 mode(CRC-4 framing) OOF can
be declared when 915 or more CRC blocks
out of 1000 are received in error.
Additionally for E1 mode(CAS signalling)
OOF can be declared when two consecutive
multiframe alignment words are received in
Loss of frame condition [chars] for Rx mode error or, for a period of one multiframe, all
[chars] on sync [dec] \ clock-interface
bits in timeslot 16 are zero.

For T1 mode LOS is declared (as detected

by BITS receiver) when no pulses are
detected in a window of 192 consecutive
pulse intervals. In E1 and 2048kHz modes
LOS is declared when no pulses are
detected in a window of 255 consecutive
pulse intervals. For UTI mode, LOS is
Loss of signal condition [chars] for Rx mode detected by hardware as per J.211
[chars] on sync [dec] \ clock-interface
specifications.

For T1 mode LOS is declared (as detected

by BITS receiver) when no pulses are
detected in a window of 192 consecutive
pulse intervals. In E1 and 2048kHz modes
LOS is declared when no pulses are
detected in a window of 255 consecutive
pulse intervals. For UTI mode, LOS is
Loss of signal condition [chars] for Rx mode detected by hardware as per J.211
[chars] on sync [dec] \ clock-interface
specifications.

For T1 mode LOS is declared (as detected

by BITS receiver) when no pulses are
detected in a window of 192 consecutive
pulse intervals. In E1 and 2048kHz modes
LOS is declared when no pulses are
detected in a window of 255 consecutive
pulse intervals. For UTI mode, LOS is
Loss of signal condition [chars] for Rx mode detected by hardware as per J.211
[chars] on sync [dec] \ clock-interface
specifications.

Remote alarm indication condition [chars]

for Rx mode [chars] on \ sync [dec] clockinterface

The BITS receiver has detected RAI defect

for incoming signal. Receiving remote
alarm indication(RAI) means the far-end
equipment over the T1/E1 line has a
problem with the signal it is receiving from
the upstream equipment.

Remote alarm indication condition [chars]

for Rx mode [chars] on \ sync [dec] clockinterface

The BITS receiver has detected RAI defect

for incoming signal. Receiving remote
alarm indication(RAI) means the far-end
equipment over the T1/E1 line has a
problem with the signal it is receiving from
the upstream equipment.

Remote alarm indication condition [chars]

for Rx mode [chars] on \ sync [dec] clockinterface

The BITS receiver has detected RAI defect

for incoming signal. Receiving remote
alarm indication(RAI) means the far-end
equipment over the T1/E1 line has a
problem with the signal it is receiving from
the upstream equipment.

Transmit open circuit condition [chars] for

Tx mode [chars] on \ sync [dec] clockinterface

BITS transmitter has detected an open

circuit condition.

Transmit open circuit condition [chars] for

Tx mode [chars] on \ sync [dec] clockinterface

BITS transmitter has detected an open

circuit condition.

Transmit open circuit condition [chars] for

Tx mode [chars] on \ sync [dec] clockinterface

BITS transmitter has detected an open

circuit condition.

Transmit short circuit condition [chars] for

Tx mode [chars] on \ sync [dec] clockinterface

Condition raised by BITS transmitter when

internal short-circuit resistance is approx
25 ohms or less.

Transmit short circuit condition [chars] for

Tx mode [chars] on \ sync [dec] clockinterface

Condition raised by BITS transmitter when

internal short-circuit resistance is approx
25 ohms or less.

Transmit short circuit condition [chars] for

Tx mode [chars] on \ sync [dec] clockinterface

Condition raised by BITS transmitter when

internal short-circuit resistance is approx
25 ohms or less.

Incorrect frame alignment condition [chars]

for Tx mode \ [chars] on sync [dec] clock- Condition raised possibly due to incorrect
interface.
internal BITS transmitter configuration.

Incorrect frame alignment condition [chars]

for Tx mode \ [chars] on sync [dec] clock- Condition raised possibly due to incorrect
interface.
internal BITS transmitter configuration.

Incorrect frame alignment condition [chars]

for Tx mode \ [chars] on sync [dec] clock- Condition raised possibly due to incorrect
interface.
internal BITS transmitter configuration.

Incorrect multi-frame alignment condition

[chars] for Tx mode \ [chars] on sync [dec] Condition raised possibly due to incorrect
clock-interface.
internal BITS transmitter configuration.

Incorrect multi-frame alignment condition

[chars] for Tx mode \ [chars] on sync [dec] Condition raised possibly due to incorrect
clock-interface.
internal BITS transmitter configuration.

Incorrect multi-frame alignment condition

[chars] for Tx mode \ [chars] on sync [dec] Condition raised possibly due to incorrect
clock-interface.
internal BITS transmitter configuration.

In T1 mode TPDV alarm is raised when the

Transmit pulse density violation condition transmit data stream does not meet ANSI
[chars] for Tx mode \ [chars] on sync [dec] T1.403 requirements for transmit pulse
clock-interface
density.

In T1 mode TPDV alarm is raised when the

Transmit pulse density violation condition transmit data stream does not meet ANSI
[chars] for Tx mode \ [chars] on sync [dec] T1.403 requirements for transmit pulse
clock-interface
density.

In T1 mode TPDV alarm is raised when the

Transmit pulse density violation condition transmit data stream does not meet ANSI
[chars] for Tx mode \ [chars] on sync [dec] T1.403 requirements for transmit pulse
clock-interface
density.

Continuing execution: [chars]: Caused by

[chars]

This message indicates an error occurred

beyond which execution of the
ClkCtrl_driver may continue, attempting to
effect recovery or work-around internally,
minimizing loss of information/functionality.

Continuing execution: [chars]: Caused by

[chars]

This message indicates an error occurred

beyond which execution of the
ClkCtrl_driver may continue, attempting to
effect recovery or work-around internally,
minimizing loss of information/functionality.

Continuing execution: [chars]: Caused by

[chars]

This message indicates an error occurred

beyond which execution of the
ClkCtrl_driver may continue, attempting to
effect recovery or work-around internally,
minimizing loss of information/functionality.

The clock-control T0 PLL (reference clock

for all interfaces) \ is [chars] FREERUN
mode.

No external reference frequency is

available for synchronization, so the T0 PLL
output is free-running.

The clock-control T0 PLL (reference clock

for all interfaces) \ is [chars] FREERUN
mode.

No external reference frequency is

available for synchronization, so the T0 PLL
output is free-running.

The clock-control T0 PLL (reference clock

for all interfaces) \ is [chars] FREERUN
mode.

No external reference frequency is

available for synchronization, so the T0 PLL
output is free-running.

The clock-control T0 PLL (reference clock

for all interfaces) \ is [chars] HOLDOVER
mode.

No external reference frequency is

available for synchronization, so the T0 PLL
output is in holdover, maintaining the
most-recent frequency to which it was
locked.

The clock-control T0 PLL (reference clock

for all interfaces) \ is [chars] HOLDOVER
mode.

No external reference frequency is

available for synchronization, so the T0 PLL
output is in holdover, maintaining the
most-recent frequency to which it was
locked.

The clock-control T0 PLL (reference clock

for all interfaces) \ is [chars] HOLDOVER
mode.

No external reference frequency is

available for synchronization, so the T0 PLL
output is in holdover, maintaining the
most-recent frequency to which it was
locked.

The clock-control T4 PLL (reference clock

for Sync 0 and \ Sync 1 ports) is [chars]
FREERUN mode.

No external reference frequency is

available for synchronization, so the T4 PLL
output is free-running.

The clock-control T4 PLL (reference clock

for Sync 0 and \ Sync 1 ports) is [chars]
FREERUN mode.

No external reference frequency is

available for synchronization, so the T4 PLL
output is free-running.

The clock-control T4 PLL (reference clock

for Sync 0 and \ Sync 1 ports) is [chars]
FREERUN mode.

No external reference frequency is

available for synchronization, so the T4 PLL
output is free-running.

Event Manager create failed for [chars].

Reason: [chars]

ClkCtrl Event Manager create error

Event Manager notify failed for [chars].

Reason: [chars]

ClkCtrl Event Manager notify error

Exit on error: [chars]: Caused by [chars]

An error occurred in ClkCtrl Driver which

requires exiting (and, hence, restarting) the
process.

Exit on error: [chars]: Caused by [chars]

An error occurred in ClkCtrl Driver which

requires exiting (and, hence, restarting) the
process.

Exit on error: [chars]: Caused by [chars]

An error occurred in ClkCtrl Driver which

requires exiting (and, hence, restarting) the
process.

LWM Event Manager event block failed.

Reason: [chars]

ClkCtrl Event Manager event block error

An error occurred during LWM message

reply. Reason: [chars]

ClkCtrl LWM reply error

Interface [dec] ([chars]) is [chars]

A link to the RSP control plane switch has

change state.

[chars]

This is an informational message from the

Cluster Upgrade Engine

Headless RSP Detected: No HB requests

from the active RSP.

This LC has timed out waiting for Heartbeat

requests from the active RSP.

Headless RSP Detected: No HB requests

from the active RSP.

This RSP has timed out waiting for

Heartbeat requests from the active RSP.

CONCERTO Driver encountered a fatal error

and is not able to recover. The supplied
Initialization Error: [chars] Reason: [chars]. text string will explain the reason. Call
Exiting.
support with this text.

Error Allocating <[dec]> bytes of memory

CONCERTO encountered a fatal memory

allocation error

Continuing execution: [chars]: Caused by

[chars]

This message indicates an error occurred

beyond which execution of the
concerto_driver may continue, attempting
to effect recovery or work-around
internally, minimizing loss of
information/functionality.

Event Manager create failed for [chars].

Reason: [chars]

CONCERTO Event Manager create error

Event Manager notify failed for [chars].

Reason: [chars]

CONCERTO Event Manager notify error

Exit on error: [chars]: Caused by [chars]

An error occurred in CONCERTO Driver

which requires exiting (and, hence,
restarting) the process.

LWM Event Manager event block failed.

Reason: [chars]

CONCERTO Event Manager event block

error

An error occurred during LWM message

reply. Reason: [chars]

concerto LWM reply error

[chars] - [chars]

Error in CPU Control FPGA operation.

[chars] - [chars] [dec]

Error in CPU Control FPGA operation.

[chars] - [chars] [chars]

Error in CPU Control FPGA operation.

[chars] - [chars] [hex] [hex]

CPU Control FPGA operation information.

[chars] - [dec]: [chars]

Error in CPU Control FPGA operation.

[chars] - [dec]: [chars] (rc = [hex])

Error in CPU Control FPGA operation.

[chars] - [chars]

Error in CPU Control FPGA operation.

i2c ack error on SFP+ port [dec].\n

The system has encountered an error while

refreshing SFP port.

i2c ack error on SFP+ port [dec].\n

The system has encountered an error while

refreshing SFP port.

[chars] loaded from backup partition\n

The FPGA has loaded from backup

partition.

[chars]: calloc failed for size: [dec]\n

An error occurred in CPUCtrl driver due to

memory allocation

ErrStr:[chars]\n

An error occurred in CPUCtrl driver which

requires exiting the function call.

CPUCtrl Driver encountered an initialization

error and may not operate correctly. The
Initialization Error: [chars] Reason: [chars]. supplied text string will explain the reason.
Exiting.
Call support with this text.

[chars]: msg send problem to client:

[chars]: Error:[chars]\n

An error occurred in CPUCtrl driver due to

client which tried to send message
failed.The error string updates the client
name reason for the message send failure.

[chars]: msg send problem: [chars]\n

An error occurred in CPUCtrl driver due to

message send failure which requires
exiting the function call.The error string
updates the reason for the message send
failure

[chars] - [chars]

Error in CPU Control FPGA operation.

[chars] - [chars] [hex]

Error in CPU Control FPGA operation.

[chars] programming error.\n

The system has encountered an error while

loading FPGA.

i2c timeout error on SFP+ port [dec].\n

The system has encountered an error while

refreshing SFP port.

i2c timeout error on SFP+ port [dec].\n

The system has encountered an error while

refreshing SFP port.

USB Over Current condition encountered.\n The front panel usb port is disabled.

[chars] - [chars]

CPU Control FPGA operation information.

[chars] - [chars]

Error in CPU Control FPGA operation.

The CPU Control, Dynamic Link Library

(DLL) failed to initialize. The effect is that
the line card may not function or may not
function appropriately. The CPU Control DLL
provides low level services to other
components on the SIP 700 Line Card (LC).
These include, among other things,
interrupt services and watch dog time out
services. If CPU Control services are not
available then those mandatory processes
that use these services will exit, respawn
and retry the initialization. If these services
remain unavailable then the LC will not
properly boot and will reset itself. This error
is generally indicative of a larger LC-wide
problem. %s - description of the specific
CPU Control, DLL initialization error, [chars] failure encountered %s - error detail, if
%s
appropriate

CPU Control, DLL cleanup error, [chars]%s

The CPU Control, Dynamic Link Library

(DLL) failed to cleanup. The effect is
relatively minimal and should not be of
concern in and of itself. Some minor
resource may or may not have been
properly returned to a system resource
pool. %s - description of the specific failure
encountered %s - error detail, if
appropriate

CPU Control, DLL trace error, [chars]%s

The CPU Control, Dynamic Link Library

(DLL) failed to initialize the LTrace facility.
The effect is that the CPU Control debug
trace facility is not functional. This means
that trace information used by Cisco
support to help isolate CPU Control device
issues may not be available. This does not
impact normal CPU Control device
operations. Note that it is unlikely that this
failure would occur by itself. This failure is
generally indicative of a larger LC-wide
problem. %s - description of the specific
failure encountered %s - error detail, if
appropriate

CPU Control driver, event manager setup

error, [chars]%s

The CPU Control driver failed to initialize

the event manager. The effect is that the
line card may not function or may not
function appropriately. The CPU Control
driver provides low level services on the
SIP 700 Line Card (LC). These include,
among other things, access timeout
interrupt services and bus parity error
interrupt services. The CPU Control driver
relies on an event manager to
communicate with other components on
the SIP 700 LC. If event manager services
are not available then the driver process is
exited, respawned and the initialization
retried. The CPU Control driver is a
mandatory process. If the initialization
continues to fail after several retries the LC
will not properly boot and will reset itself.
This error is generally indicative of a larger
LC-wide problem. %s - description of the
specific failure encountered %s - error
detail, if appropriate

CPU Control driver, main setup error,

[chars]%s

The CPU Control driver failed to initialize.

The effect is that the line card may not
function or may not function appropriately.
The CPU Control driver provides low level
services on the SIP 700 Line Card (LC).
These include, among other things, access
timeout interrupt services and bus parity
error interrupt services. If these services
are not available then the driver process is
exited, respawned and the initialization
retried. The CPU Control driver is a
mandatory process. If the initialization
continues to fail after several retries the LC
will not properly boot and will reset itself.
This error is generally indicative of a larger
LC-wide problem. %s - description of the
specific failure encountered %s - error
detail, if appropriate

CPU Control driver, interrupt setup error,

[chars]%s

The CPU Control driver failed to initialize

interrupt processing. The effect is that the
line card may not function or may not
function appropriately. The CPU Control
driver provides low level services on the
SIP 700 Line Card (LC). These include,
among other things, access timeout
interrupt services and bus parity error
interrupt services. If these services are not
available then the driver process is exited,
respawned and the initialization retried.
The CPU Control driver is a mandatory
process. If the initialization continues to fail
after several retries the LC will not properly
boot and will reset itself. This error is
generally indicative of a larger LC-wide
problem. %s - description of the specific
failure encountered %s - error detail, if
appropriate

CPU Control driver, ASIC Peek/Poke setup

error, continuing

The CPU Control driver failed to initialize

the ASIC Peek/Poke facility. The effect is
that the CPU Control driver debug
Peek/Poke facility is not functional. This
means that CPU Control Peek/Poke
commands used exclusively by Cisco
support may not be available. This does
not impact normal CPU Control device
operations. Note that it is unlikely that this
failure would occur by itself. This failure is
generally indicative of a larger LC-wide
problem.

The CPU Control driver failed to initialize

External Data Manager (EDM) processing.
The effect is that the CPU Control driver
show commands are not functional. This
means that display information used by
customers and Cisco support to monitor
the CPU Control device may not be
available. This does not impact normal CPU
Control device operations. In particular,
this failure would impact the 'show
controllers CPUCtrl a9k-sip-700'
commands. %s - description of the specific
CPU Control driver, External Data Manager failure encountered %s - error detail, if
setup error, [chars]%s
appropriate

CPU Controller: FPD agent failure, [chars]

(Return code [chars])

The CPU Controller FPGA FPD agent failed

to initialize. If this error is encountered the
CPU Controller FPGA could not be
upgraded. The failure should not have an
adverse effect on the card's normal
operation. %s - description of the specific
failure encountered %s - error detail, if
appropriate

CPU Control driver, trace setup error,

continuing

The CPU Control driver failed to initialize

the LTrace facility. The effect is that the CPU
Control driver debug trace facility is not
functional. This means that trace
information used by Cisco support to help
isolate CPU Control device issues may not
be available. This does not impact normal
CPU Control device operations. Note that it
is unlikely that this failure would occur by
itself. This failure is generally indicative of
a larger LC-wide problem.

Cpuctrl could not find [chars]

While booting up, CPUCTRL could not find

the required ASICs. %s - detail description
of which asic can not be found

While trying to bring up ASIC links, Cpuctrl

Cpuctrl could not reset board ASICs. [chars] manager could not reset MSC and PLIM
Error.
board ASICs port.

Cpuctrl HW detected SBE in [chars] RAM.

Key: [hex]\n[chars]

Indicates a correctable single-bit error

occurred on this internal SRAM. The error is
corrected transparently. The location will be
written automatically before being read
again. %s - name of ram that error
occurred %x - key of error node recorded
%s - error data

Indicates an uncorrectable parity error

occurred on this internal SRAM. %s - name
Cpuctrl HW detected parity in [chars] RAM. of ram that error occurred %x - key of error
Key: [hex]\n[chars]
node recorded %s - error data

Cpuctrl HW detected MBE in [chars] RAM.

Key: [hex]\n[chars]

Indicates an uncorrectable multi-bit error

occurred on this internal SRAM. %s - name
of ram that error occurred %x - key of error
node recorded %s - error data

TX PDMA Ring Stalled, port = [dec]

([chars]), queue = [dec] ([chars]), cur_ind
= [dec], tx_ind = [dec].

CPUCTRL TX PDMA ring remained full over

non-transient period. Packets which could
not be sent were discarded. The
downstream ASIC may be stalled. Asic error
logged with queue details. %d - port
number %s - device name %d - queue
number %s - client name %d - current
descriptor index %d - current refill
descriptor index

Event Manager create failed for [chars].

Reason: [chars]

Cpuctrl Event Manager create error

Event Manager notify failed for [chars].

Reason: [chars]

Cpuctrl Event Manager notify error

[chars], Reason: [chars]. Exiting.

Cpuctrl manager encountered a fatal error

and is not able to recover from the error. A
reason text will be supplied; please provide
this text when calling Cisco support. %s error description %s - error code
description

[chars]

The cpuctrl driver HW error interrupt

handler was invoked and found valid PCI
ISN register from a Cpuctrl Internal Access
failure.

[chars]

The cpuctrl driver HW error interrupt

handler was invoked and found a port with
valid link error registers.

[chars]

The cpuctrl driver HW error interrupt

handler was invoked and found valid PCI
PM error registers.

[chars]

The cpuctrl driver HW error interrupt

handler was invoked and found valid PCI
SN error registers.

[chars]

The cpuctrl driver HW error interrupt

handler was invoked and found valid PCIX
error registers.

[chars]

The cpuctrl driver HW error interrupt

handler was invoked and found a port with
valid isn error registers.

Bus error when attempting User requested The user may have entered an invalid
GASPP Read, Address = [hex]\n
address, or else there is a HW problem.
Cpuctrl HW detected error on GASPP write, The user may have entered an invalid
Address = [hex]\n
address that is not writable.

The IMDR procedure was aborted by this

process. Error [dec] Reason [chars]

The CPUCTRL process aborted the IMDR

upgrade process. Check prior log messages
for possible process crahses or errors.

A failure occurred when interacting with

IMDRs. An IMDR operation in progress may
A error occurred [chars] process imdr. Error be aborted or may not complete
[dec] Reason [chars].
sucessfuully.

Cpuctrl HW detected SBE in [chars] Mask

RAM. Key: [hex]\n[chars]

Indicates a correctable single-bit error

occurred on this internal SRAM. This
memory is considered 'persistent' and
requires special handling as described in
the 'Data_corrected' row of Table 1.2. %s name of ram that sbe occurred %x - key of
error node recorded %s - error data

Cpuctrl HW detected SBE in [chars] RAM.

Key: [hex]\n[chars]

Indicates a correctable single-bit error

occurred on this internal SRAM. The error is
corrected transparently. The location will be
written automatically before being read
again. %s - name of ram that sbe occurred
%x - key of error node recorded %s - error
data

Cpuctrl HW detected MBE in [chars] RAM.

Key: [hex]\n[chars]

Indicates an uncorrectable multi-bit error

occurred on this internal SRAM. %s - name
of ram that error occurred %x - key of error
node recorded %s - error data

[chars] receiving queue [dec] ([chars])

stopped to process incoming packets

Indicated device stop process the incoming

packets in the receiving queue, while there
is still packets in the pdma queue. %s:
device name %d: queue number %s: client
name

Cpuctrl HW detected SBE in [chars] RAM.

Key: [hex]\n[chars]

Indicates a correctable single-bit error

occurred on this internal SRAM. The error is
corrected transparently. The location will be
written automatically before being read
again. %s - name of ram that error
occurred %x - key of error node recorded
%s - error data

Indicates an uncorrectable parity error

occurred on this internal SRAM. %s - name
Cpuctrl HW detected parity in [chars] RAM. of ram that error occurred %x - key of error
Key: [hex]\n[chars]
node recorded %s - error data

Cpuctrl HW detected MBE in [chars] RAM.

Key: [hex]\n[chars]

Indicates an uncorrectable multi-bit error

occurred on this internal SRAM. %s - name
of ram that error occurred %x - key of error
node recorded %s - error data

Cpuctrl port [dec] link is out of frame with

persistent CRC errors.

Cpuctrl manager could not bring up the

ASIC link on the specified port. This
indicates a hardware failure on the MSC or
PLIM board.

Bag register failed for rules. Reason:

[chars]

EDM Bags are used to share information

between components using sysdb. This
Error indicates that bag registration failed.

Dll Initialization for [chars] failed. Reason:

[chars]

Cpuctrl driver tried to register for a dll but

it encountered an error. The driver might
lose some of its functionality.

LWM Event Manager event block failed.

Reason: [chars]

Cpuctrl Event Manager event block error

Sysdb Register EDM failed. Reason: [chars] Cpuctrl Sysdb Register EDM error

CDMA to port 0 channel = [dec], queue =

[dec] ([chars]). ASIC address [[hex],[hex]]

The cpuctrl driver detected an attempt to

DMA to port 0. The request was discarded
and not performed. %d - channel number
%d - queue number %s - client name %x address high 32bit %x - address low 32bit

TX PDMA to EgressQ queue 0, port = [dec], The cpuctrl driver detected an attempt to
queue = [dec] ([chars]). Buffer Header:
DMA a packet to egressq queue 0. The
[hex]. Initial packet data(hex): [chars]
packet was discarded and not sent.

[chars], [dec], port = [dec] ([chars]), queue The cpuctrl driver detected an error during
= [dec] ([chars])
packet DMA.
The indicated rx pdma queue has a drop
device [dec] PDMA rx queue [dec]([chars]) error occurred %d - device id %d - queue
drop error
number %s - client name

This error indicates that a packet sent to

the squidlib code by the client was
truncated while the squidlib code was
[chars] , Pak Particle count = [dec],
trying to send the packet. The squidlib has
datagram_size = [dec], port = [dec] ,queue aborted the tx operation as the packet
= [dec]([chars])
doesn't have any particles to send

HW set the error bit in a CDMA descriptor\n

\tCDMA engine = [dec], queue = [dec]
([chars]), index = [dec]\n \terror reg_lo =
[hex], error_reg_hi = [hex]
CDMA ended in error.

HW set the error bit in a RX PDMA

The cpuctrl driver detected a buffer
descriptor\n \tport = [dec] ([chars]), queue marked with an error, possibly a CRC
= [dec] ([chars]), index = [dec]\n
check. The buffer is discarded.
Restarting cpuctrl client [dec] ([chars]) on
port [dec] for devid [dec] ([chars]) on
unrecovered PIO error notification

A PIO error was detected and the

responsible client was notified but did not
mark the error as recovered. Restarting the
client.

The cpuctrllib ASIC Interrupt wrapper has

detected that an ASIC driver has not
cleared its interrupts at the source for 1000
consecutive times. This is possibly an error
in the Driver ISR, that does not process and
clear all possible interrupts, or
malfunctioning HW. The Interrupt is
disabled to prevent the ISR from hogging
Excess Spurious interrupt on device [chars] the CPU.

Port [dec] ([chars]) could not clear Link

errors during init\n \tlink_error_reg = [hex],
crc_reg = [hex]
Port will not operate reliably

Attempt to access Port [dec] which was not

discovered\n \tDevice ID_reg = [hex], devid
= [hex]
Port will not operate reliably

Port [dec] ([chars]) would not sync on

reframe attempt

Port will not operate reliably

Port [dec] ([chars]) Device chipid mismatch

during reframe\n \tid_reg read after
reframe = [hex], id_reg during HW
discovery = [hex]
Port will not operate reliably

RX PDMA Ring out of buf, Port [dec]

([chars]), Q [dec] ([chars]), cur_ind = [dec], CPUCTRL RX PDMA ring could not replace
tx_ind = [dec], retry [dec]
the buffers, possible low buffer condition.

Crossbar unicast FPOE DB correctable ECC Crossbar driver detected unicast FPOE
error on [chars] link 0
correctable ECC error on link 0

Crossbar unicast FPOE DB correctable ECC Crossbar driver detected unicast FPOE
error on [chars] link 1
correctable ECC error on link 1

Crossbar unicast FPOE DB uncorrectable

ECC error on [chars] link 0

Crossbar driver detected unicast FPOE

uncorrectable ECC error on link 0

Crossbar unicast FPOE DB uncorrectable

ECC error on [chars] link 1

Crossbar driver detected unicast FPOE

uncorrectable ECC error on link 1

Crossbar unicast input memory detected

correctable ECC error on [chars] link 0

Crossbar driver detected unicast input

memory correctable ECC error on link 0

Crossbar unicast input memory detected

correctable ECC error on [chars] link 1

Crossbar driver detected unicast input

memory correctable ECC error on link 1

Crossbar unicast input memory detected

uncorrectable ECC error on [chars] link 0

Crossbar driver detected unicast input

memory uncorrectable ECC error on link 0

Crossbar unicast input memory detected

uncorrectable ECC error on [chars] link 1

Crossbar driver detected unicast input

memory uncorrectable ECC error on link 1

Crossbar unicast output memory detected

correctable ECC error on [chars] link 0

Crossbar driver detected unicast output

memory correctable ECC error on link 0

Crossbar unicast output memory detected

correctable ECC error on [chars] link 1

Crossbar driver detected unicast output

memory correctable ECC error on link 1

Crossbar unicast output memory detected

uncorrectable ECC error on [chars] link 0

Crossbar driver detected unicast output

memory uncorrectable ECC error on link 0

Crossbar unicast output memory detected

uncorrectable ECC error on [chars] link 1

Crossbar driver detected unicast output

memory uncorrectable ECC error on link 1

Excessive Crossbar input buffer CRC error

on [chars] link 0

Crossbar driver detected excessive input

buffer CRC error on link 0

Excessive Crossbar input buffer CRC error

on [chars] link 1

Crossbar driver detected excessive input

buffer CRC error on link 1

Crossbar driver input memory error on

[chars] link 0

Crossbar driver detected an input memory

error on link 0

Crossbar driver input memory error on

[chars] link 1

Crossbar driver detected an input memory

error on link 1

Crossbar multicast FPOE DB correctable

ECC error on [chars] link 0

Crossbar driver detected multicast FPOE

correctable ECC error on link 0

Crossbar multicast FPOE DB correctable

ECC error on [chars] link 1

Crossbar driver detected multicast FPOE

correctable ECC error on link 1

Crossbar multicast FPOE DB uncorrectable Crossbar driver detected multicast FPOE

ECC error on [chars] link 0
uncorrectable ECC error on link 0

Crossbar multicast FPOE DB uncorrectable Crossbar driver detected multicast FPOE

ECC error on [chars] link 1
uncorrectable ECC error on link 1

Crossbar multicast input memory detected Crossbar driver detected multicast input
correctable ECC error on [chars] link 0
memory correctable ECC error on link 0

Crossbar multicast input memory detected Crossbar driver detected multicast input
correctable ECC error on [chars] link 1
memory correctable ECC error on link 1

Crossbar multicast input memory detected Crossbar driver detected multicast input
uncorrectable ECC error on [chars] link 0
memory uncorrectable ECC error on link 0

Crossbar multicast input memory detected Crossbar driver detected multicast input
uncorrectable ECC error on [chars] link 1
memory uncorrectable ECC error on link 1

Crossbar multicast output memory

detected correctable ECC error on [chars]
link 0

Crossbar driver detected multicast output

memory correctable ECC error on link 0

Crossbar multicast output memory

detected correctable ECC error on [chars]
link 1

Crossbar driver detected multicast output

memory correctable ECC error on link 1

Crossbar multicast output memory

detected uncorrectable ECC error on
[chars] link 0

Crossbar driver detected multicast output

memory uncorrectable ECC error on link 0

Crossbar multicast output memory

detected uncorrectable ECC error on
[chars] link 1

Crossbar driver detected multicast output

memory uncorrectable ECC error on link 1

Crossbar driver output memory error on

[chars] link 0

Crossbar driver detected an output

memory error on link 0

Crossbar driver output memory error on

[chars] link 1

Crossbar driver detected an output

memory error on link 1

Crossbar driver serdes error on [chars] link Crossbar driver detected a serdes error on
0
link 0.

Crossbar driver serdes error on [chars] link Crossbar driver detected a serdes error on
1
link 1.

Crossbar driver detected crossbar timeout

error on [chars] link 0

Crossbar driver detected an crossbar

timeout error on link 0

Crossbar driver detected crossbar timeout

error on [chars] link 1

Crossbar driver detected an crossbar

timeout error on link 1

Crossbar ASIC access failed [chars]

Crossbar driver detected an issue with ASIC

access.

Crossbar ASIC BIST failed [chars]

Crossbar driver detected ASIC BIST failure.

Crossbar ASIC current temperature [chars] Crossbar driver detected that the current
is over threshold
ASIC temperature is over threshold.

Crossbar multicast queue utilization

crossed threshold, [chars]

Crossbar driver detected multicast queue

utilization is over configured threshold.

Crossbar multicast queue utilization

crossed threshold, [chars]

Crossbar driver detected multicast queue

utilization is over configured threshold.

LINK FAIL port=[dec]

Data Path switch link has failed.

ENS init failed

A critical error occured while getting the

state of booster state info from dll

Card initialisation failed :[chars] with rc

[hex]

A critical error occured during the

initialization of DC_SERVICE_SRVR process
which involves exiting the process. The
DC_SERVICE_SRVR will restart and unless
the same error occurs on the next attempt
the DC_SERVICE_SRVR will function
normally. If the error is persistent, it
indicates the system error or HW error
which needs further investigation. The
cause of the error will be mentioned in the
message displayed.

Server initialisation failed :[chars] with rc

[hex]

A critical error occured during the

initialization of DC_SERVICE_SRVR process
which involves exiting the process. The
DC_SERVICE_SRVR will restart and unless
the same error occurs on the next attempt
the DC_SERVICE_SRVR will function
normally. If the error is persistent, it
indicates the system error or HW error
which needs further investigation. The
cause of the error will be mentioned in the
message displayed.

Failed to initialize debug module:[chars]

Encountered an error in debug module.

This error should not impact the major
functionality of the module.

Error encountered tracing for [chars]:

[chars]

Encountered an error in tracing module.

This error should not impact the major
functionality of the module.

NP loopback failure count crossed

threshold, [chars]

This line card has detected a problem with

the packet punt and injection path between
this line card CPU and some network
processor(s), and the consecutive failure
count has reached or crossed the failure
threshold.

NP loopback failure count crossed

threshold, [chars]

This line card has detected a problem with

the packet punt and injection path between
this line card CPU and some network
processor(s), and the consecutive failure
count has reached or crossed the failure
threshold.

NP loopback failure count crossed

threshold, [chars]

This line card has detected a problem with

the packet punt and injection path between
this line card CPU and some network
processor(s), and the consecutive failure
count has reached or crossed the failure
threshold.

Excessive ECC Single-bit errors

The number of single-bit ECC errors has

crossed the error threshold.

Fabric multicast loopback (SC0) failure

count crossed threshold.

A problem is detected by loopback test to

the first Crossbar chip (chip#0) on this RSP.

Fabric multicast loopback (SC1) failure

count crossed threshold.

A problem is detected by loopback test to

the second Crossbar chip (chip#1) on this
RSP.

Fabric unicast loopback failure count

crossed threshold.

A problem is detected by loopback test to

the Crossbar chips on this RSP.

FPD image integrity check failed,

An FPD image in non-volatile memory is

corrupted or missing. Each FPD has 2
images stored in non-volatile memory, one
is field upgradable version; the 'B' version.
The other is the backup version; the 'A'
version. If a B version FPD image has gone
bad, it can be recovered by following the
recommended_action. If the A version has
gone bad, the board must be replaced.

Device identity readback value is incorrect Device identity readback value is incorrect

LC lost EOBC heartbeat to both RSPs.

This line card has lost EOBC heartbeat to

both RSPs

EOBC Heartbeat failure count for RSP0

([chars]) crossed threshold.

This line card has lost EOBC heartbeat to

RSP0.

EOBC Heartbeat failure count for RSP1

([chars]) crossed threshold.

This line card has lost EOBC heartbeat to

RSP1.

This line card has lost EOBC heartbeat to

LC lost EOBC heartbeat to the Standby RSP. the standby RSP.
No RSP is up, LC EOBC heartbeat skipped.
[chars]

This line card found there is no RSP present

in the system.

Failed to send a heartbeat to RSP [chars]

This line card has failed to transmit a

heartbeat to a RSP over EOBC.

System punt, fabric and data path failure

count crossed threshold, [chars]

A problem is detected on the system punt,

fabric or data path between this RSP CPU
to one or more of the network processor(s)
on some line card(s).

Device scratch register test has failed

The CPU at the failed location has failed to

access the named device scratch register.

Standby RSP has detected an error with the

active eobc link between this standby RSP
Heartbeat failed over active EOBC, [chars] and one or more line card)(s)

Failed to broadcast heartbeat over active

EOBC.

Standby RSP failed to transmit heartbeat to

all nodes via active EOBC links.

Heartbeat failed over Standby EOBC,

[chars]

Standby RSP has detected an error with the

standby eobc link between this standby
RSP and one or more line card)(s)

Failed to broadcast heartbeat over standby Standby RSP failed to transmit heartbeat to
EOBC.
all nodes via standby EOBC links.

ASIC-ERR: [chars]

System Controller asic detected a critical

error that will bring the node down. A
reason text will be supplied.

Failed to mmap to Kernel dumper

information in syspage, error: [chars].

Failed to mmap to Kernel dumper

information in syspages.

Failed to mmap to Kernel dumper

information in syspage, error: [chars].

Failed to mmap to Kernel dumper

information in syspages.

Failed to set reboot cause into syspage,

error: [chars].

The failure on setting reboot cause to

syspage before performing Kernel Dump.

Failed to set reboot cause into syspage,

error: [chars].

The failure on setting reboot cause to

syspage before performing Kernel Dump.

ASIC-ERR: RAM error #[dec]: Name =

[chars] #[dec]: Description = [chars]

Two or more bit ECC error (Uncorrectable)

found in a RAM Access.

ASIC-ERR: RAM error #[dec]: Name =

[chars] #[dec]: Description = [chars]

Two or more bit ECC error (Uncorrectable)

found in a RAM Access.

ASIC-ERR: CPU error #[dec]: Name =

[chars] #[dec]: Description = [chars] (info
latched and follows)

Errors observed on the system controller

CPU module. A reason text will be supplied.

ASIC-ERR: CPU error #[dec]: Name =

[chars] #[dec]: Description = [chars] (info
lost)

Errors observed on the system controller

CPU module for which information may be
lost due to other errors. A reason text will
be supplied.

ASIC-ERR: DEV error #[dec]: Name =

[chars] #[dec]: Description = [chars] (info
latched and follows)

Errors seen on the device bus. A reason

text will be supplied.

ASIC-ERR: DEV error #[dec]: Name =

[chars] #[dec]: Description = [chars] (info
lost)

Errors seen on the device bus for which

information was lost due to other errors or
some other condition.

ASIC-ERR: PCI[dec] error #[dec]: Name =

[chars] #[dec]: Description = [chars] (info
latched and follows)

Error was observed on the system PCI bus.

Error description is provided.

ASIC-ERR: PCI[dec] error #[dec]: Name =

[chars] #[dec]: Description = [chars] (info
lost)

Error was observed on the system PCI bus

for which detailed infromation was lost due
to more errors or some other reason.

ASIC-ERR: RAM error #[dec]: Name =

[chars] #[dec]: Description = [chars]

Threshhold reached for single bit ECC

(Corrected) errors.

ASIC-ERR: RAM error #[dec]: Name =

[chars] #[dec]: Description = [chars]

Threshhold reached for single bit ECC

(Corrected) errors.

ASIC-ERR: SRAM error #[dec]: Description

= [chars]

Parity Error detected in SRAM.

ASIC-ERR: Addr High [hex] Addr Low [hex]

Err Attribute [hex], Cause [hex], Command Details about the error observed on the PCI
[hex]
bus with Atlantis system controller.
ASIC-ERR: PCI[dec] error #[dec]:
Command: [chars], Error Address: [hex]
[hex], Error Attribute: [hex]

Details about the error observed on the PCI

bus with Atlantis system controller.

ASIC-ERR: CPU error #[dec]: Error Address:

[hex], Address Parity Bits: [hex], Error Data: Details about the error seen in CPU
[hex] [hex], Data Parity Bits: [hex] [hex]
module.
ASIC-ERR: DEV error #[dec]: Error Address:
[hex]
Details on the device bus error.

ASIC-ERR: [chars], [dec]

Information message from Discovery driver

on software error condition.

ASIC-ERR: [chars], [dec]

Information message from Discovery driver

on software error condition.

ASIC-ERR: PCI[dec] error #[dec]:

Command: [chars], Byte Enables: [hex]
[hex], Error Address: [hex] [hex], Error
Data: [hex] [hex], Parity Bits: [hex] [hex]

Details about the error observed on the PCI

bus.

ASIC-ERR: RAM error #[dec]: Error Address:

[hex], Error Data: [hex] [hex], Recorded
Details about the ECC error happenned
ECC Bits: [hex], Calculated ECC Bits: [hex] before.
ASIC-ERR: RAM error #[dec]: Error Address:
[hex], Error Data: [hex] [hex], Recorded
Details about the ECC error happenned
ECC Bits: [hex], Calculated ECC Bits: [hex] before.
ASIC-ERR: RAM error #[dec]: Error Address:
[hex] [hex], Error Data: [hex] [hex], Parity
Bits: [hex]
Details on SRAM parity error.

Unable to allocate timer id

ATA device might report these errors when

it unable to allocate event timer id.

Unable to allocate timer leaf

ATA device might report these errors when

it unable to allocate event timer leaf.

Unable to create evm [chars]

ATA device might report these errors when

it unable to create ATA_EVM.

Unable to create thread. rc = [chars]\n

pthread_create() returns error. If this occurs

, event related operations will not occur.

Unable to open file [chars] reason: [chars]

Failed to open file to log debugs. If this

failure occurs, debugs wont be logged.

ATA warning. Too many nested calls. Error

code = [hex]

ATA device might report these errors if it

has not been shutdown properly before the
RP reload. The device generally recovers of
it's own.

Unable to pass through, CERR Handler.

[chars]

Media device shutdown operation failed to

pass through.

DMAC DAO link interface is down

The internal link interface for the specified

port is down.

Un-recoverable ECC error was detected in

DMAC device [dec]

The DMAC device encountered an

unrecoverable ECC error condition. This
would require a reset of the device to
recover.

Dmac device [dec] encountered fatal PCIe

error : [dec]

PCIe interface encountered fatal error.

Dmac device [dec] PCIe link down

PCIe interface encountered fatal error.

Temperature alarm on DMAC device [dec]

The thermal sensor trip point was crossed

on DMAC.

Dmac device [dec] XAUI link down for

extended duration

DMAC XAUI link went down and stayed

down for an extended duration which
would affect CE/Fabric connectivity of the
RP.

DMAC CE_SWITCH link interface is down

The internal link interface for the specified

port is down.

PCI errors were detected in DMAC device

[dec]

The DMAC device encountered PCI errors.

Unexpected PCIe link state for DMAC [dec]: DMAC came up with a degraded PCIe
[dec] lanes Gen [dec], expected [dec] lanes configuration. Number of lanes and Link
Gen [dec]
speed does not match what is expected.

DMAC dev [dec] link state changed to

[chars]

The DMAC link state changed.

Some packets are dropped due to receive

buffer overflow in DMAC device. The CLI
above will show which queue dropped the
packet. This would in general indicate an
Packets dropped due to buffer overflow on unexpected CPU busy condition wherein
device [dec]
the software is slow in processing packets.

[chars], reason: [chars]

This message indicates that during

dra_pairing dll attach, either debugging or
ltrace services cannot be initialized.

[chars], reason: [chars]

This message indicates that during

dra_pairing dll attach, either debugging or
ltrace services cannot be initialized.

Config manager connect failed. [chars]

drp_pairing process connection with config

manager got failed. Software will
automatically do recovery by restarting the
drp_pairing process.

Drp pairing checkpointing application

initialization failed: [chars].

Check pointing of drp_pairing application

initialisation got failed. Software will
automatically do recovery by restarting the
drp_pairing process.

Unable to determine the dSC nodeid

Got invalid DSC node while searching to

run the DRP pairing process on DSC node.
Software will automatically do recovery by
restarting the drp_pairing process.

Event manager create failed. [chars]

Event manager creation got failed.Software

will automatically do recovery by restarting
the drp_paring process.

Failed to get my own nodeid. [chars]

drp-pairing process should run on the dSC

rack's active RP. Unable to get the nodeid
information from platform. Software will
automatically do recovery by restarting the
drp_pairing process.

Unable to initialize drp_pairing server.

[chars]

Error in intialising DRP pairing server

process. Software will automatically do
recovery by restarting the drp_pairing
process.

The specified SysDB operation failed.

SysDB operation [chars] failed. Error code: Software will automatically do recovery by
[chars]
restarting the drp_paring process.

Unable to create a LWM thread. [chars]

Creation of LWM thread failed. Software will

automatically do recovery by restarting the
drp_pairing process.

Drp_pairing process readiness update to

config manager connect failed. [chars]

Drp_pairing process failed to notify cfgmgr

that it is now ready to accept admin config

Failed to register with CERR Handler.

[chars]

Error in registering with CERR handler.

WARNING: A node with unknown type or a

non DRP node [chars] is used for drp
pairing configuration

DRP_PAIRING process will output this

informational message during drp pairing
configuration commit time only if one or
both of the node(s) used to form the drp
pair is not a DRP node. Please note that if
the node is not in IOX-RUN state, it's node
type will not be determined.

WARNING: A node with unknown type or a

non DRP node [chars] is used for drp
pairing configuration

DRP_PAIRING process will output this

informational message during drp pairing
configuration commit time only if one or
both of the node(s) used to form the drp
pair is not a DRP node. Please note that if
the node is not in IOX-RUN state, it's node
type will not be determined.

DRP pairing is not supported on CRS-4-CH

Because CRS-DRP is not supported in CRS

Series 4 Slots Line Card system, therefore,
drp pairing configuration will be disabled
also.

DRP pairing is not supported on CRS-4-CH

Because CRS-DRP is not supported in CRS1 Series 4 Slots Line Card system,
therefore, drp pairing configuration will be
disabled also.

We are not on Active RP so blocking Drp

pairing process until active stanby RP role
change. [chars]

Drp pairing process will be blocked until

active RP comes up.

[chars] [hex] [chars]

This message indicates that a failure has

occured in DSC-CTRL process.

Multiple nodes within the system have

declared the Primary DSC role. This can
lead to severe system instability and traffic
loss as the multiple primary nodes conflict.
In order to resolve the conflict, the system
Primary DSC state declared by [dec] nodes: will reload RSP nodes until only a single
[chars]. Local state is [chars]
Primary node remains.

No Primary DSC has been declared after

[dec] retries. Redundancy State is [chars].
DSC Role is [chars]

After numerous retries, the system has

been unable to elect an RSP node to act as
the primary DSC node. Without this
election complete, the system is
inoperable.

Current rack number '[dec]' does not

match serial '[chars]' number in admin
config. Correcting and reloading ..

The rack number in rommon does not

match the rack number in admin config.
Fixing the rommon rack number to that in
admin config. This will cause a reload of
the system.

Rack reloading due to control link failure.

The system has detected that the control

links connecting the Primary and Backup
racks of the Clustered system are not
functional. Since XR cannot operate
without the Primary DSC node, and a new
one cannot be declared, this rack must be
reloaded.

[chars]

This is an informational message from DSCCTRL process.

Node reloading due to ISSU upgrade.

An ISSU upgrade is in progress and this

node requires a reload. When the upgrade
is complete, this node will be restarted.

Rack [dec] is now [chars]

One rack of the cluster system has entered

or exited the cluster. Up state is normal for
a rack in the cluster. Down could indicate a
rack level reboot, or a connectivity issue
between the racks.

Lost Connection to all Fabric Racks

This node has lost connectivity with all

fabric racks before the fabric planes came
up. This could be a control ethernet
problem or the fabrics have reloaded.

[chars] - error : [chars] , exiting...

The dsc process failed in initialization. This

indicates that there was a software error
during initialization.

[chars] - error : [chars] , exiting...

The dsc process failed in initialization. This

indicates that there was a software error
during initialization.

[chars] - nodeid : [hex]

Priority given for the node is not applicable.

[chars] - error : [chars], exiting...

An internal software error occured as

indicated in the message.

Could not initialize [chars] trace buffer,

error [hex] ([chars])

ltrace initialization failed

Failed to allocate [dec] bytes, exiting...

The dsc process could not allocate memory.

This indicates some problem with the
system wide memory.

Failed to allocate [dec] bytes, exiting...

The dsc process could not allocate memory.

This indicates some problem with the
system wide memory.

WARNING ! WARNING ! Received request

with zeroed serial number. Assigning rack
num [dec] and allowing it to pass, till
CSCeg63482 is fixed. If this is multichassis, please upgrade ALL RP/SC
ROMMONs in this setup to 1.22 !

Once ROMMON 1.22 is rolled out, all multichassis testbeds should upgrade to it to
avoid problems of more than one RP
getting the same rack number assigned.
This msg warns the operator that an RP
was detected that had older ROMMON and
should be upgraded ASAP.

Lost connectivity with rack [chars]

This indicates that either the rack is

powerdown/shutdown or there is some
problem with control ethernet cables or
switches between the racks.

[chars] - error: [chars]

The dsc process could not notify RMF about

the backup dsc.

[chars] - error: [chars]

The dsc process could not open connection

with sysdb. Hence the show commands will
fail. However, the system will continue to
function normally.

Primary transport connection not ok to

node [chars], alternate transport
connectivity ok

CRS: This indicates that there is a problem

with control ethernet cables or switches to
that node. C12k: This indicates that there is
a problem with MBUS communication to
that node.

Lost connectivity to the rack: [dec]

Connectivity to the given rack is lost. We

are expected to reload in case if the lost
rack is the DSC rack or the last fabric rack.

We lost connectivity to a rack while the

user initiated system reload is in progress.
As the entire system is undergoing a
Lost rack [dec] during user initiated system reload, it is expected to see the racks going
reload.
down.

Not creating reload thread for cause code

[[dec]] since system reload already in
progress with cause [[dec]].

Since the reload is already in progress,

there is no need to create a reload thread
again in case if the connectivity to DSC
rack or the last fabric rack is lost.

System reload status: [[dec]]

Shows the system reload status - whether a

user initiate system reload is in progress or
not.

Missed [dec] consecutive heartbeats from

node [chars]. Please check transport
connectivity to node

Heartbeats over control-ethernet from the

node in question are being missed. This
usually indicates a CE transport issue.
Please check control ethernet connections
to and from the node in question. Note,
these messages are expected if node in
question is going down due to a user
trigger such as OIR, failover

ROMMON RACK_NUM (=[dec]) set

inconsistent.

ROMMON RACK_NUM variable setting is

different from the node_id rack field
setting.

ROMMON RACK_NUM set to 0.

ROMMON RACK_NUM variable set to 0.

Table entry present flag: [dec] for node

([hex]) on rack [dec].

None.

Setting myself as DSC

Informational message notifying current

DSC in system

Node ([hex]) came up first on rack

[dec].Notify the clients now.

None.

[dec] min elapsed,still waiting.

Informational message notifying current

DSC in system.

Install operation - reload in progress

dSC process is not reloading node since a

reload install operation is in progress.
Install will reload node after install
complete. Heartbeat loss messages are
expected during this time.

Missed heartbeat from node [chars]

Heartbeats over control-ethernet from the

node in question are being missed.
Continous meesages usually indicate a CE
transport issue. Please check control
ethernet connections to and from the node
in question

[chars]. rack = [dec], [chars]

An internal software error occured and this

rack could not be removed.

Config cleanup failed following rack [dec]

removal - [chars]. error: [chars]\n

Not able to save configuration for this rack.

No Response received from configuration

manager server.

No response received from configuration

manager server.

Could not store reboot information for node Chassis APIs that write to non volatile
[hex], [chars]
memory failed.

Waiting for result of active/standby

arbitration...keep trying

The redundancy information is needed as

an input for the DSC election. Only active
cards may become DSC. The information is
still unavailable at this time. The DSC
election is on hold, waiting for the
information to become available. This will
prevent proper system operation.

[chars]; rc = [chars]

DSC could not read back plane EEPROM.

This might affect the booting up of the
standby. If the standby does not boot then
the work around is to set the rack number
to backplane eeprom association using the
following cli. (admin-config)#dsc serial
<serial-id> rack <rack-num>

[chars] ; rc = [chars]

DSC Media DLL has encounered the

annunciated Event Manager error. The
System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

[chars]; rc = [chars]

DSC Media DLL failed to get the nodeid.

The System Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

[chars]

DSC Media DLL has encounered the

annunciated transport error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Error from dsc media dll: [chars]

The dsc media dll encountered an internal

software error. Details of the internal
software error is reported as part of the
error log.

Error from dsc media dll: [chars],

errno=[dec] ([chars])

The dsc media dll encountered an internal

software error. Details of the internal
software error is reported as part of the
error log.

Unable to [chars] when parsing persistent

file [chars]: [chars] ([chars])

The dsc process attempted to read dcs

election information from non-volatile
storage, but encountered a problem. This
may cause the wrong RP card to get
elected as DSC.

Unable to [chars] when writing persistent

file [chars]: [chars] ([chars])

The dsc process attempted to store dcs

election information to non-volatile
storage, but encountered a problem. This
may cause the wrong RP card to get
elected as DSC on the next chassis cold
boot.

[chars] ; rc = [chars]

DSC media DLL encountered an error while

locking a mutex. The operation related to
the resource may be affected while the
system continues to run normally.

[chars]; rc = [chars]

DSC media DLL encountered an error while

un-locking a mutex. The operation related
to the resource may be affected while the
system continues to run normally.

Unable to [chars] [chars] when fetching

initial copy from DSC: [chars] ([chars])

The process is unable to get an initial copy

of the dsc info file from the dsc card. This
may cause the wrong RP card to get
elected as DSC on the next chassis cold
boot.

Unable to listen for multicast messages:

[chars] ([chars])

The process is unable to register to receive

multicast messages. This means that the
card will not be able to update local nonvolatile data with the latest dsc election
information coming from remote nodes.
This may cause the wrong RP card to get
elected as DSC on the next chassis cold
boot.

Serial Numbers of the Fabric Cards (slots 16

and 17) are used to help determine chassis
nativity for the Logical Routers feature.
Chassis nativity is part of the algorithm to
ensure that on a cold boot, the right RP is
elected as the DSC and provides Logical
Router boundaries to other RP cards. The
lack of CSC serial numbers may cause the
wrong RP to be elected DSC when RP cards
Could not read Serial Numbers of the Fabric are shuffled from one chassis to another
Cards slot 16 & 17; errno=[dec] ([chars])
and a cold boot is performed.

Warning from dsc media dll: [chars]

The dsc media dll encountered an internal

software warning.

Warning from dsc media dll: [chars],

errno=[dec] ([chars])
This node is now [chars]

The dsc media dll encountered an internal

software warning.
A new dSC has been elected.

EIO library failed to send message; rc =

[chars], exiting...

The EIO Library encountered LWM error,

therefore failed to send pulse. The System
Manager process (sysmgr) will
automatically respawn the annunciated
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger MSC
reload. After a certain number of MSC
reloads, the shelf manager will
permanently shutdown the MSC.

[chars]; rc = [chars], exiting...

The EIO Library encountered ECM error,

therefore failed to send pulse. The System
Manager process (sysmgr) will
automatically respawn the annunciated
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger MSC
reload. After a certain number of MSC
reloads, the shelf manager will
permanently shutdown the MSC.

[chars]; rc = [chars]

The EIO library was unable to register with

sysdb as an EDM. The System should still
continue to function as normal, with the
exception that the 'show' commands for
EIO will not be available.

[chars]; [chars]

The Chip-to-Chip connecting link

encountered the annunciated link training
error. This link connects the two adjacent
ASIC and its required to be in trained state
for the ASIC's to commuincate control and
data reliably over this channel. In general
this is a recoverable error as the ASIC
driver's will re-train the link on seeing this
error.

EIO library failed to allocate [dec] bytes

The EIO library was unable to allocate

memory.

[chars]; rc = [chars]

The EIO library encountered the

annunciated register access error. This
could result in inconsistent behavior of the
device/system.

[chars]; rc = [chars]

The EIO library encountered the

annunciated register access error. This
could result in inconsistent behavior of the
device/system.

Egress Mux FPGA has encountered

uncorrectable error. Reloading LC to
recover

Egress Mux FPGA has encountered

uncorrectable error. Reloading LC to
recover.

Egress MUX detected loss of sync error on

interlaken interface

Loss of sync on interlaken interface on

egress mux and fia 0

Loss of sync

Loss of sync on interlaken interface on

egress mux and fia 0

Loss of sync

Loss of sync on interlaken interface on

egress mux and fia 1

Loss of sync

Loss of sync on interlaken interface on

egress mux and fia 1

Multicast high priority fifo multi-bit ECC

error

Multicast high priority fifo multi-bit ECC

error

Multicast high priority fifo overflow error

Multicast high priority fifo overflow error

Multicast high priority fifo Single bit ECC

error

Multicast high priority fifo single bit ECC

error

Multicast low priority fifo multi-bit ECC

error

Multicast low priority fifo multi-bit ECC

error

Multicast low priority fifo overflow error

Multicast low priority fifo overflow error

Multicast low priority fifo Single bit ECC

error

Multicast low priority fifo single bit ECC

error

Unicast high priority fifo multi-bit ECC error Unicast high priority fifo multi-bit ECC error

Unicast high priority fifo overflow error

Unicast high priority fifo overflow error

Unicast high priority fifo Single bit ECC

error

Unicast high priority fifo single bit ECC

error

Unicast low priority fifo multi-bit ECC error Unicast low priority fifo multi-bit ECC error

Unicast low priority fifo overflow error

Unicast low priority fifo overflow error

Unicast low priority fifo Single bit ECC error Unicast low priority fifo single bit ECC error

FIA00 burst FIFO multi-bit ECC error

FIA00 burst FIFO multi-bit error.

FIA01 burst FIFO multi-bit ECC error

FIA01 burst FIFO multi-bit error.

FIA10 burst FIFO multi-bit ECC error

FIA10 burst FIFO multi-bit error.

FIA11 burst FIFO multi-bit ECC error

FIA11 burst FIFO multi-bit error.

FIA00 burst FIFO overflow error

FIA00 burst FIFO overflow error.

FIA01 burst FIFO overflow error

FIA01 burst FIFO overflow error.

FIA10 burst FIFO overflow error

FIA10 burst FIFO overflow error.

FIA11 burst FIFO overflow error

FIA11 burst FIFO overflow error.

FIA00 burst FIFO single bit ECC error

FIA00 burst FIFO single bit error.

FIA01 burst FIFO single bit ECC error

FIA01 burst FIFO single bit error.

FIA10 burst FIFO single bit ECC error

FIA10 burst FIFO single bit error.

FIA11 burst FIFO single bit ECC error

FIA11 burst FIFO single bit error.

FIA00 packet header checksum error

FIA00 packet header checksum error.

FIA01 packet header checksum error

FIA01 packet header checksum error.

FIA10 packet header checksum error

FIA10 packet header checksum error.

FIA11 packet header checksum error

FIA11 packet header checksum error.

FIA00 packet maximum length error

Packet maximum length error FIA 00

interface.

FIA01 packet maximum length error

Packet maximum length error FIA 01

interface.

FIA10 packet maximum length error

Packet maximum length error FIA 10

interface.

FIA11 packet maximum length error

Packet maximum length error FIA 11

interface.

FIA00 packet minimum length error

Packet minimum length error FIA 00

interface.

FIA01 packet minimum length error

Packet minimum length error FIA 01

interface.

FIA10 packet minimum length error

Packet minimum length error FIA 10

interface.

FIA11 packet minimum length error

Packet minimum length error FIA 11

interface.

FIA00 packet length error

Packet length error FIA 00 interface.

FIA01 packet length error

Packet length error FIA 01 interface.

FIA10 packet length error

Packet length error FIA 10 interface.

FIA11 packet length error

Packet length error FIA 11 interface.

SEM critical error

Egress MUX detected SEM correctable

error.

Egress Mux FPGA has encountered critical

correctable error.

Egress Mux FPGA has encountered critical

correctable error.

Over Temperature error

Over temperature error

VCC int error

Vccaux out of range..

VCC int error

Vccint out of range..

[chars], port [dec], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

[chars], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

Envmon process has been [chars] to read

temperature from various nodes\n

Two possibilities to this message 1) The

envmon_mon process has been unable to
read the temperature from various nodes
for the last 5 iterations. This is most likely
due to a communications error with remote
nodes. Due to this, envmon_mon has no
visibility into whether the chassis is being
cooled properly or not. So the fans are
being set to maximum speed to cover for
any potential thermal issues during this
time. Once the temperatures are readable,
the fan speed will automatically be
adjusted as per the ambient temperature.
Setting fan speed to maximum to prevent
chassis from heating up. 2) The
envmon_mon process which has previously
not been able to read the temperature
from various nodes, is now able to read the
temperature from atleast one node.
Subsequently, the fan speed will be
adjusted as per the mean_temp
calculation. Setting fan speed as per
ambient temperature.

Card temperature has risen at or over

Slot [chars] temperature [dec].[dec]C at or shutdown threshold. Card shutdown
above STT [dec].[dec]C
commencing.
Chassis ambient temperature has risen at
Chassis ambient temperature [dec].[dec]C or over shutdown temperature threshold
at or over shutdown STT threshold [dec].
(STT). Entire chassis shutdown
[dec]C
commencing.

Environmental Monitor was unable to

shutdown slot [dec]: [chars]

Envmon attempted to shutdown the

specified slot due to severely out-of-range
conditions, but was unable to do so. The
request to sysldr to shut the card, failed.

The environmental condition on slot [dec]

is because of power failure in [chars]

Powershelf failure environmental conditions

exist on the specified slot. If left untended,
they could result in loss of service or even
hardware damage.

The environmental condition on slot [dec]

is because of power fault

Powershelf fault environmental conditions

exist on the specified slot. If left untended,
they could result in loss of service or even
hardware damage.

Fan blower removed from slot [dec]

The fan blower module specified was

detected as removed.

[chars] removed from slot [dec]

The power entry module specified was

detected as removed.

Environmental Monitor initiated shutdown

on slot [dec]

An environmental sensor has remained in a

dangerous operating range, and sysldr is
requested to shutdown card to avoid
possible damage.

Environmental Monitor was unable to

shutdown slot [dec] bay [dec]: [chars]

Envmon attempted to shutdown the

specified spa due to severely out-of-range
conditions, but was unable to do so.

Environmental Monitor initiated shutdown

on slot [dec] bay [dec]

An environmental sensor on the spa has

remained in a critical operating range, and
is being shutdown to avoid possible
damage.

The power calculated in use by the chassis

exceeds that available by the powershelf.
Power consumption has exceeded additive This condition could result in an outage of
supply mode limit by [dec]W; results
the chassis if action is not immediately
unpredictable
taken.

There are no fan trays plugged into the

chassis, chassis cooling is non-operational,
and chassis ambient temperature and card
No fan trays present in the chassis, chassis temperatures may rise to over temperature
cooling non-operational
conditions.

One or more fan trays now plugged in,

chassis cooling operational

One or more fan trays plugged into the

chassis, chassis cooling is now in operation.
One fan tray runs at full speed by SW
default and provides partial chassis
cooling, two fan trays run at computed
speed based on ambient temperature.

Slot [chars] temperature [dec].[dec]C at or Card hotspot temperature has risen at or

above rising T4 threshold [dec].[dec]C
over critical threshold.
Slot [chars] temperature [dec].[dec]C
returned below falling T4 threshold [dec].
[dec]C

Card temperature has returned to

operating range.

Chassis ambient temperature is over

critical threshold. Ambient temperature is
Card [dec] sensor [dec] temperature [dec] the average of the temperature inlet
at or above STT [dec]
sensor for all RSP plugged in the chassis.

Chassis ambient temperature is over

critical threshold. Ambient temperature is
Chassis ambient temperature [dec].[dec]C the average of the temperature inlet
at or above rising T3 threshold [dec].[dec]C sensor for all RSP plugged in the chassis.
Chassis ambient temperature has returned
Chassis ambient temperature [dec].[dec]C to operating range. Ambient temperature is
returned below falling T3 threshold [dec]. the average of the temperature inlet
[dec]C
sensor for all RSP plugged in the chassis.

Slot [chars] sensor [chars] temperature

[dec].[dec]C [chars] threshold [dec].0C

LC on die temperature sensor is risen

above or fallen below critical threshold.LC
or Port will be shutdown in 24 Hrs

Outstanding environmental condition

[chars] in the chassis

One or more environmental conditions

exits in the chassis. If left unattended, they
can result in loss of service or physical
equipment damage.

An environmental condition on slot [dec]

[chars]

Two possibilities to this message: 1) One or

more environmental conditions exist on the
specified slot; 2) All environmental
conditions on the specified slot have
cleared. If env conditions exist and are left
untended, they could result in loss of
service or even hardware damage.

The environmental condition on slot [dec]

has cleared because the slot is no longer
monitorable

All environmental conditions on the

specified slot have cleared due to the fact
that the card was either removed from the
slot or was powered down.

The environmental condition on slot [dec]

bay [dec] has cleared because the SPA is
no longer monitorable

All environmental conditions on the

specified spa have cleared due to the fact
that the spa was either removed from the
card or was shut down.

The fan array specified has reached a

warning or critical level and is approaching
The fan array ([chars]) has reached [chars] or approached a condition that is outside
level.
the acceptable range.
Fan failure cleared on slot [chars], fan
[dec], RPM [dec]

The indicated fan has measured RPM

returning to operating level.

Fan failure on slot [chars], fan [dec], RPM

[dec]

The indicated fan has measured RPM below

operating level.

[chars] FAILED.

The fan array's specified parameter FAILED.

Fan tray failure cleared on slot [chars]

All fans on indicated fan tray returned

RPMs to operating level.

Fan tray communication failure cleared on

slot [chars]

System SW communication with fan tray

re-established.

Fan tray communication failure on slot

[chars]

System SW has lost communication with

fan tray. Fan tray LED may not be
consistent, (admin)# show env fan may no
longer be consistent. Fans do continue to
run, just no longer under system SW
control.

Fan tray failure on slot [chars]

One or more fans on indicated fan tray

measured RPM below operating level.
Remaining fans in operation on this fan
tray running at full speed.

[chars] ,[dec] error code [chars]\n

Message sending failed between envmon

component and Envmon Event Detector of
the Embedded Event Manager.

Slot [chars] Port_[dec] is [chars]

Port is disabled if the port temparture is

over the critical threshold for more than
24hrs. And re-enabled if, the temperature
drops.

Power consumption is back within [chars]

supply mode limits

The power calculated in use by the chassis

has returned to a value that is within the
power supplied by the powershelf.

[chars] current has reached [chars] level at The current supply specified has reached a
[dec] A (scan# = [unsigned int])
critical level and is now out of specification.

[chars] is Non-Operational

The power supply specified has become

non-operational.

[chars] voltage has reached [chars] level at The voltage supply specified has reached a
[dec] V (scan# [unsigned int])
critical level and is now out of specification.

Power consumption has exceeded

redundant supply mode limit by [dec]W;
power redundancy lost

The power calculated in use by the chassis

exceeds that for which power supply
redundancy is available. The chassis now
function in additive mode.

The CPT 50 Panel Battery Failure A

(SAT_BAT_FAIL_A) alarm is raised when the
battery A fails. This could be because the
Battery Failure A - [chars] on Satellite [dec] battery is removed or is not operational.
The CPT 50 Panel Battery Failure A
(SAT_BAT_FAIL_A) alarm is raised when the
battery A fails. This could be because the
Battery Failure A - [chars] on Satellite [dec] battery is removed or is not operational.
The CPT 50 Shelf Battery Failure B alarm
occurs when battery B is down or not
detected. This could be because the
Battery Failure B - [chars] on Satellite [dec] battery is removed or is not operational.
The CPT 50 Shelf Battery Failure B alarm
occurs when battery B is down or not
detected. This could be because the
Battery Failure B - [chars] on Satellite [dec] battery is removed or is not operational.

Chassis temperature is [chars] the [chars]

threshold on Satellite [dec]

The CPT 50 Chassis temperature threshold

crossing (SAT_CHASSIS_TEMP_ALARM)
alarm is raised when the chassis
temperature crosses minimum/maximum
threshold.

Fan failure - [chars] on Satellite [dec]

The CPT 50 Panel Fan Failure

(SAT_FAN_FAIL) alarm is raised when there
is a faulty fan-tray assembly.

Fan failure - [chars] on Satellite [dec]

The CPT 50 Panel Fan Failure

(SAT_FAN_FAIL) alarm is raised when there
is a faulty fan-tray assembly.

Fan MFGMEM failure - [chars] on Satellite

[dec]

The CPT 50 Panel Fan Manufacturing Data

Memory (EEPROM) Failure
(SAT_FAN_MFGMEM) alarm is raised when
the fan-tray assembly manufacturing data
memory (or EEPROM) fails.

Fan MFGMEM failure - [chars] on Satellite

[dec]

The CPT 50 Panel Fan Manufacturing Data

Memory (EEPROM) Failure
(SAT_FAN_MFGMEM) alarm is raised when
the fan-tray assembly manufacturing data
memory (or EEPROM) fails.

The CPT 50 Panel Fan Unit is Missing

(SAT_FAN_MISSING) alarm is raised when
the fan-tray assembly is not present in the
Fan unit missing - [chars] on Satellite [dec] CPT 50 panel.
The CPT 50 Panel Fan Unit is Missing
(SAT_FAN_MISSING) alarm is raised when
the fan-tray assembly is not present in the
Fan unit missing - [chars] on Satellite [dec] CPT 50 panel.
The CPT 50 Panel Fan Unit RPM threshold
crossing (SAT_FAN_RPM_ALARM) alarm is
Fan rpm is [chars] the [chars] threshold on raised when the fan RPM crosses
Satellite [dec]
minimum/maximum threshold.

PM failure - [chars] on Satellite [dec]

Satellite PM Failure (SAT_PM_FAIL) alarm is

raised when there is a faulty power-supply
assembly.

[Satellite [dec]]: [chars] alarm occurred for The sensor in the satellite module reported
[chars] sensor at [dec] deg C, \ against a
a critical hi/lo sensor value against the
configured threshold of [dec] deg C
configured threshold value.

slot [dec] bay [dec] temperature [dec].

[dec]C [chars] threshold [dec].0C

SPA temperature has risen over shutdown

threshold. SPA shutdown commencing.

[chars] temperature has reached [chars]

level at [dec](C)

The temperature sensor specified has

reached a critical level and is approaching
or approached a condition that is outside
the acceptable range.

Indicates that a voltage sensor contains

Voltage sensor [chars] contains value [dec] value that is out side of expected +-10%
which is out side of +-10% valid range.
range. The card will be shutdown to
Card will be shutdown!
prevent damage to other components

Card shutdown through RP failed. rc =

[dec], reason = [chars]. Initiating selfshutdown

Indicates that shelfmgr failed to shutdown

the card either because of communication
failure or because the shelfmgr rejected
the shutdown request

[chars] voltage has reached [chars] level at The voltage supply specified has reached a
[dec] mV
critical level and is now out of specification.

Voltage [chars] = [dec] not within

thresholds\n

Software periodically reads voltages on

fabric cards. If the voltage read is out side
of +-10% valid range, this message will be
displayed.

slot:[dec] Cannot determine if E5 [chars]

supports 12V rail. Assuming legacy E5
card.

The envmon component needs to to know

the E5's hardware type and power
controller firmware version in order to
determine if the card supports the new
daughterboard 12V SPA voltage rail.
However, we could not determine one of
these components, and so the software is
taking the conservative stance of assuming
that the E5 does not support the 12V rail.
This error should always be preceeded by
another envmon E5 related error about the
hardware or firmware check failing.

Card type [dec] in slot [dec] is not

supported by environmental monitoring.
The card will not be monitored

The card inserted in the specified slot

cannot be monitored.

Slot [chars] sensor [chars] temperature

[dec].[dec]C shutdown in ([dec]) hours

LC or port shutdown is schedulded if the

temperature value stays above the critical
thresold for 24 hrs or more

Card type [dec] in slot [dec] needs

hardware rework and is not supported by
The E5 card inserted in the specified slot
environmental monitoring. The card will not cannot be monitored since it needs
be monitored
hardware rework.

Envmon process exiting in [chars].[dec],

error code [chars]\n

The Envmon process exited due to the

reason mentioned in the message.

An attempt to read from MBus to determine

whether the chassis is AC or DC powered
failed. This will result in the supply type
Failed mbus read when determining AC/DC reporting as the default of AC.

Fan tray alarm on slot [chars]

One or more fans on indicated fan tray

operating below 30% of the set RPM. This
is not a critical condition. If it is below 30%,
the remaining fans in operation on this fan
tray run at full speed.

Fan tray alarm cleared on slot [chars]

All fans on indicated fan tray operating at

the set RPM.

Unknown margin code [hex]

An unknown margin mode was received by

the erroring function. Consequently it did
not know what to do and has aborted the
current action.

Power Supply [chars] is non Cisco

compliant, powering off.

Should a non-Cisco power supply be

installed into the Cisco QQ chassis, upon
detection as non-compliant, IT WILL BE
SHUTDOWN. Please note that using nonCisco power supplies MAY RESULT IN
COMPLETE CHASSIS SHUTDOWN due to
insufficient power

Failed in [chars],[dec] error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This
may be a serious failure, however process
may continue functioning as expected (or
successfully retry) despite the failure.

The particular operation mentioned in the

message failed due to some reason. This
may be a serious failure, however process
may continue functioning as expected (or
Failed in [chars].[dec], error code [chars]\n successfully retry) despite the failure.

[chars] slot insertion current counter

exceeds TB [dec] - [chars]

Backplane slot connector has card

insertions exceed threshold B per current
counter statistics.

[chars]: Invalid slot [dec]

Invalid slot number.

Unexpected PRP type [hex] in slot [dec].

Assuming PRP-2

The envmon component received an

unexpected PRP type.

slot:[dec] Cannot determine E5 power

controller firmware version. errno=[hex]:
[chars]

The envmon component could not

determine the E5's power controller FW
version.

slot:[dec] Cannot determine E5 hardware

type.

The envmon component could not

determine the E5 type.

Unknown PEM[dec] of type [chars]%s,

chassis type [dec]

The envmon component could not

determine the type of Power Entry Module.
This will result in this PEM reporting as a
0W PEM and the power calculations will be
inaccurate.

Cannot determine PRP type in slot [dec],

assuming PRP-2.

The envmon component could not

determine the PRP type. The envmon
component will treat this PRP as if it was a
PRP-2. If this is really a PRP-1 then the
show environmental voltage command will
list two extra sensors: PLIM_V7_HDD_5V
and PLIM_V6_1.5V, and these sensors will
have incorrect voltage and margin states,
because they do not really exist. Moreover,
the PRP1's PLIM_V4_1.6V volt sensor will be
instead listed as PLIM_V4_1.3V. There is no
negative impact to the card.

[chars] alarm [chars] by [chars]

Some possibilities to this message 1) An

alarm has occured. If this is a PEM INPUT1
or INPUT2 failure alarm, then it means that
low voltage (40V +/- 1V) or no voltage is
present on the input. Due to limitations in
the hardware, the 'show environment
power' CLI command is inaccurate at that
low voltage level and may show 0V and 0A
for the readings, even though the input
voltage is non-zero. In such a condition, a
high amperage may also be present.
Please measure the voltage/current on all
failed PEMs with an oHm meter before
performing any maintenance on the power
supplies. 2) A previously occured alarm has
been cleared. If this is 'power shelf circuit
breaker error' alarm, there might be an
internal wiring failure. The power shelf
circuit breaker trip wire might be touching
the chassis or ground. 3) Software failed to
access temperature, voltage, and/or power
supply alarm sensor(s) which are critical to
the operation of environmental monitoring.

Resetting the blower life cycle weekly

count for slot [dec] after 5 year of expiry

The blower life cycle weekly count is

supported for 5 years. After 5 year expiry
restart the life cycle count.

Voltage sensor alarm slot [chars], sensor

[chars] measured [dec] mV and out of
operational range [dec] - [dec] mV

The card voltage sensor has been

monitored below or above it's operational
range. If the voltage continues to fall or
rise, the HW power sequencer may reset
the board.

Voltage sensor alarm cleared slot [chars],

sensor [chars] measured [dec] mV and
returned to operational range

The card voltage sensor has returned to

operational range.

[chars] alarm [chars] by [chars]

Two possibilities to this message 1) An

alarm has occured. 2) A previously occured
alarm has been cleared. power shelf circuit
breaker alarm, there might be an internal
wiring failure. The power shelf circuit
breaker trip wire might be touching the
chassis or ground. Or circuit breaker on/off
triggered.

Watchdog stats are collected on active RP.If

CBC on node [chars] has not seen
watchdog toggle is not seen for long time,
watchdog toggle in at least [dec] seconds\n the message will be displayed.

Slot [chars] sensor [chars] temperature

[dec].[dec]C [chars] threshold [dec].0C

LC on die temperature sensor is risen

above or fallen below major threshold.

Fan tray RPM warning on slot [chars]

One or more fans on indicated fan tray

operating above 30% of the set RPM. This
is not a critical condition.

Fan tray RPM warning cleared on slot

[chars]

All fans on indicated fan tray operating at

the set RPM.

Fan tray version mismatch warning on slot Fantray version is different from the
[chars]
existing one. This is not a critical condition.
Fan tray version mismatch warning cleared
on slot [chars]
All fantrays are same version.

The envmon component has detected that

the E5 in the specified slot has HW
capability to support margining and
monitoring of the Daughterboard's 12V SPA
slot:[dec] E5 has downrev power controller rail, but the FW does not. The minimum
firmware.
power controller firmware needed is 0.95.

Port [chars]: [chars]. Reason: [chars]\n

The particular operation mentioned in the

message occured due to some reason. This
may be a serious failure, however process
may continue functioning as expected (or
successfully retry) despite the failure.

[chars], error code [chars]\n

The particular operation mentioned in the

message occured due to some reason. This
may be a serious failure, however process
may continue functioning as expected (or
successfully retry) despite the failure.

[chars] temperature has reached [chars]

level

The temperature sensor specified has

reached a warning level and is approaching
or approached a condition that is outside
the acceptable range.

[chars] alarm [chars] by [chars]

Two possibilities to this message 1) An

alarm has occured. 2) A previously occured
alarm has been cleared. power supply not
present.

[Satellite [dec]]: Fan RPM is at [dec],

running [chars] threshold of [dec]

The FAN RPM of the satellite is currently

running above/below the operating level.

Speed / duplex degrade - on port [dec] of

Satellite [dec]

This is a notification to user that the

speed / duplex parameters of a particular
port set to auto negotiate has degraded
post negotiation from its maximum
capability due to either lower capability of
the peer or the the peer not able to engage
in auto negotiation.

Speed / duplex degrade - on port [dec] of

Satellite [dec]

This is a notification to user that the

speed / duplex parameters of a particular
port set to auto negotiate has degraded
post negotiation from its maximum
capability due to either lower capability of
the peer or the the peer not able to engage
in auto negotiation.

Speed / duplex upgrade - on port [dec] of

Satellite [dec]

This is a notification to user that the

speed / duplex parameters of a particular
port set to auto negotiate has upgraded
post negotiation from its minimum
capability due to either higher capability of
the peer or the the peer not able to engage
in auto negotiation.

[chars] slot insertion current counter

exceeds TA [dec] - [chars]

Backplane slot connector has card

insertions exceed threshold A per current
counter statistics.

slot [dec] bay [dec] temperature [dec].

[dec]C [chars] threshold [dec].0C

SPA temperature is risen above or fallen

below major threshold.

slot [dec]: Unable to read mbus eeprom

contents for PCA

For displaying notification of mbus

nonresponsiveness to get eeprom contents.

slot [dec] bay [dec] temperature [dec].

[dec]C [chars] threshold [dec].0C

SPA temperature is risen above or fallen

below minor threshold.

The environmental condition (Power

Failure) on slot [dec] is cleared in [chars]

Power failure environmental conditions on

the specified slot have cleared.

The environmental condition (Power Fault) Power fault environmental conditions on

on slot [dec] is cleared
the specified slot have cleared.

The fan array ([chars]) has returned to a

normal level.

The fan sensor/array has returned to a

level that is within the acceptable range.

Fan blower inserted into slot [dec]

The fan blower module specified was

detected as inserted.

[chars] is spinning slow - speed is [dec]RPM Informational msg indicating that the fan is
(register value = [hex])\n
spinning very slow.
[chars] override has been set!

Override condition has been triggered.

[chars] temperature has returned to a

normal level

The temperature sensor specified has

returned to a level that is within the
acceptable range.

[chars] inserted into slot [dec]

The power entry module specified was

detected as inserted.

[chars] current has returned to a normal

level at [dec] A (scan# = [unsigned int])

The voltage supply specified has returned

to a level that is within the acceptable
range.

[chars] has become operational

The power supply specified has returned to

an operational state.

[chars] voltage has returned to a normal

level at [dec] V (scan# = [unsigned int])

The voltage supply specified has returned

to a level that is within the acceptable
range.

Unable to power off non compliant Power

Supply [chars]

Indicates that a non Cisco compliant power

supply was detected. The attemp to
shutdown this power supply has failed for
number of tries.

The Unqualified PPM Inserted condition

occurs when a PPM with a nonqualified
product ID is plugged into the card's port;
that is, the PPM passes the security code
check as a Cisco PPM but is not qualified
Unqualified PPM - [chars] on Satellite [dec] for use on the particular card.

The Unqualified PPM Inserted condition

occurs when a PPM with a nonqualified
product ID is plugged into the card's port;
that is, the PPM passes the security code
check as a Cisco PPM but is not qualified
Unqualified PPM - [chars] on Satellite [dec] for use on the particular card.
Failed to send pulse to shelfmgr to notify
[chars]

Failure to send pulse to shelfmgr to notify

the particular alarm condition.

[chars] temperature has returned to a

normal level at [dec](C)

The temperature sensor specified has

returned to a level that is within the
acceptable range.

[chars] voltage has returned to a normal

level at [dec] mV

The voltage supply specified has returned

to a level that is within the acceptable
range.

Bag decode on [chars] failed. Error: [chars] Could not decode bag

Cache size ([dec]) is to small for sensor id

([dec]) from SPA in slot:[dec] bay:[dec]

This is a coding defect caught by sanity

checks. The envmon subsystem maintains
a short term cache for a SPA's voltage
margin values. However, the specified SPA
is using sensor ids that are too large for our
cache. Consequently we will not be able to
store or report the voltage margin value for
these offending sensors.

Assertion failure due to [chars]

A fatal internal software error has occurred.

Checkpointing error, [chars] : [chars]

Envmon encountered an error in data

checkpointing.

Could not create checkpoint entry (key

[hex]): [chars]

Envmon encountered an error in data

checkpointing.

Could not delete checkpoint entry (objid

[hex]): [chars]

Envmon encountered an error in data

checkpointing.

[chars]: [chars]

Envmon encountered an error in data

checkpointing.

A corrupted checkpoint was detected: key

= [hex], datakey = [hex]. Entry deleted.

Envmon encountered an error in data

checkpointing.

Could not save checkpoint entry (key [hex], Envmon encountered an error in data
objid [hex]): [chars]
checkpointing.

Debug registration failed ([chars]).

An internal registration call returned an

error. Debug commands for the LIB device
may not be effective. Normal operation is
not affected.

Could not contact the dSC: [chars]

Environmental monitoring couldn't contact

the dSC

Could not determine relationship to dSC:

[chars]

Environmental monitoring couldn't

determine if it is running on the dSC or not.

Error initializing envmon EDM ([chars]):

[chars]

An error occurred while setting up the

envmon EDM.

Unknown error code [hex]

One of the look up routines for the

ENV_EDM_ERRS_E enumeration received
an unexpected error code. Most likely
caused by a new enumerated type being
added but the table was not updated, or
the look up routines are being passed a
value that really isn't a ENV_EDM_ERRS_E
value.

Event Manager's event_async_attach

function failed. Error: [chars]

Could not attach an event_handler to

handle async messages.

Event Manager create failed. Error: [chars] The Event Manager could not be created.
[chars]: [chars]
Miscellaneous software error.
The Light-Weight Messaging msg_recieve
LWM Message Receive failed. Error: [chars] function failed.
LWM Message Reply failed. Error: [chars]

The Light-Weight Messaging msg_reply

function failed.

[chars]: Error reading mbus register [hex]

on slot [dec]: [chars]

An error occurred reading an MBus register.

[chars]: Error receiving MBus message for

slot [dec], type [dec]: [chars]

An error occurred reading an MBus register.

nodeid_create for slot [dec] failed. Error:

[chars]

Platform function return error on invocation

[chars]: pthread manipulation error: [chars] A proccess thread call failed.

[chars] nodeid_extract_fields for nodeid
[dec] failed. Error: [chars]

Platform function return error on invocation

SysDB bind to [chars] failed. Error: [chars]

Could not bind to SysDB

SysDB register for notification on [chars]

failed. Error: [chars]

Could not register for notification in Sysdb

[chars]:[dec] SysDB register configuration

verifiers failed. Error: [chars]

Could not register for configuration

verification in Sysdb

Could not create thread. Error: [chars]

A thread could not be created.

Error generating Envmon trap notification

[chars]: [chars]

An error occurred while generating trap

notification to SNMP

Error, [chars]

Envmon encountered an software error.

Event Manager could not block. Error:

[chars]

Could not block on receiving events from

sysdb via event manager

[chars]: Error reading mbus cec register

[hex] on slot [dec] bay [dec]. Status:[hex], An error occurred reading an MBus CEC
Errno:[hex], ErrStr:'[chars]'
register.
Environmental monitoring will only run on
the dSC

Environmental monitoring only runs on the

dSC

Debug [chars]. ([dec],[dec],[dec],[dec],

[dec]): error code [chars]

This is a programmed diagnostic debug.

Debug [chars]. ([dec],[dec],[dec]): error

code [chars]

This is a programmed diagnostic debug.

System Manager's proccess ready failed.

Error: [chars]

A sysmgr process ready API failed.

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC0
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC1
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC10
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC11
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC12
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC13
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC14
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC15
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC16
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC17
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC18
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC19
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC2
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC3
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC4
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC5
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC6
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC7
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC8
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to LC9
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
local RSP to switch
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
peer RSP to switch
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to SFP+ port 0
errors on link

Packet errors detected on [chars] link from Switch MAC detected excessive packet
switch to SFP+ port 1
errors on link

eth_server_retrieve_clean: client[[dec]]:
orphan_count mismatch on RX,
bfm_rx_hdl[[hex]] oc[[dec]] loc[[dec]]\n

A partial retrievel of buffers happened for

the current process that restarted due to
retrieved orphan_count less than actual
orphan_count.

eth_server api free: non-fatal in_use[0]

case ignoring, src client[[dec]] dst
client[[dec]] mem_score[[dec]]\n

A double-free condition has been avoided

Self test detected that control ethernet

transmit functionality has stalled.
RestartingDMA to recover.

Ethernet server is performing a periodic

self test to ensure that transmit has not
stalled for any reason. This error msg
means that the test failed and transmit has
stalled. Eth server will correct the condition
by restarting itself and operator needs to
do nothing.

Self test detected that control ethernet

transmit functionality has stalled.
Restarting to recover.

Ethernet server is performing a periodic

self test to ensure that transmit has not
stalled for any reason. This error msg
means that the test failed and transmit has
stalled. Eth server will correct the condition
by restarting itself and operator needs to
do nothing.

ethernet driver received an unknown for us Ethernet driver received an unknown for us
packet. Cmd = [dec]
packet.

ethernet driver received an unknown for us Ethernet driver received an unknown for us
packet. Cmd = [dec]
packet.

[chars], error = [dec] ([chars])

An error occurred during initialization from

which eth server cannot recover. The
process will restart on its own to attempt a
recovery.

[chars], error = [dec] ([chars])

An error occurred during initialization from

which eth server cannot recover. The
process will restart on its own to attempt a
recovery.

ethernet server received an Isolate

message, all EOBC traffic disabled [chars]

Ethernet server received an ioslate

message to disable all EOBC traffic.

[chars], pcds at 0x[pointer] value = [hex]

An error occurred inside PCDS data

structure. Process continues to run but
PCDS data may not be logged properly

ethernet driver received a poison pill for us Ethernet driver received a poison pill for us
packet. Cmd = [dec]
packet.

[chars], buffer = [pointer]

Application tried to handle a buffer not part

of queue. Use the CLI 'show controllers
backplane ethernet trace buffstat location
<node>*' to determine if there is a queue
leak.

A bad or incomplete frame was received on

the node given in the msg. If the messages
are not persistent the condition is harmless
and no action is required. If the messages
RECV_FSM: Type: [chars] Fragments: [dec] are constantly seen, contact tech support
src: [chars] dest [chars] size: [dec] [chars] with the output of the given command.

A bad or incomplete frame was received on

the node given in the msg. If the messages
are not persistent the condition is harmless
and no action is required. If the messages
RECV_FSM: Type: [chars] Fragments: [dec] are constantly seen, contact tech support
src: [chars] dest [chars] size: [dec] [chars] with the output of the given command.

Packet corruption detected in eth_server

transmit complete

Ethernet driver got a corrupted packet in

its transmit complete, possibly because its
client (EES) has zeroed out the packet
contents before eth_server is done with the
packet.

Failed to [chars], port [dec], error code

[chars]\n

A runtime failure occurred in Ether-ctrl

process. Typically, this is an internal error.
The message string indicates the reason
for the failure. This message also provides
an error code. The process can continue
functioning as expected despite the failure.

Stats overflow port [dec]\n

Error in SERVICE-EC operation

Exiting because [chars], error code

[chars]\n

The SI Ether-Ctrl process exited due to the

reason mentioned in the message.

'Driver init fail: [chars]'

Some initialization failure while loading the

driver.

[chars], port [dec], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

[chars], port [dec], error code [chars]\n

A runtime failure occurred in Ether-Ctrl

process. Typically, this is an internal error.
The message string indicates the reason
for the failure. This message also provides
an error code and a string interpretation of
the error code.

[chars], port [dec], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

'Shared Memory Create/Open Failed:

[chars]: [chars] [dec]'

Error encountered while creating the

shared memory or accessing the shared
memory.

[chars], port [dec], error code [chars]\n

A runtime failure occurred in Ether-CtrlMgmt process. Typically, this is an internal

error. The message string indicates the
reason for the failure. This message also
provides an error code and a string
interpretation of the error code.

[chars], port [dec], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

[chars], [dec] error code [chars]\n

A runtime failure occurred in Ether-Ctrl

process. Typically, this is an internal error.
The message string indicates the reason
for the failure. This message also provides
an error code and a string interpretation of
the error code.

[chars], [dec] error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

[chars], error code [chars]\n

A runtime failure occurred in Ether-Ctrl

process. Typically, this is an internal error.
The message string indicates the reason
for the failure. This message also provides
an error code and a string interpretation of
the error code.

[chars], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

Port index ([dec]) is out of range, error

code [chars]\n

A runtime failure occurred in Ether-Ctrl

process. Typically, this is an internal error.
The message string indicates the reason
for the failure. This message also provides
an error code and a string interpretation of
the error code.

Port index ([dec]) is out of range, error

code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

Unknown code ([dec]) is out of range at

[chars]\n

A runtime failure occurred in Ether-CtrlMgmt process. Typically, this is an internal

error. The message string indicates the
reason for the failure. This message also
provides an error code and a string
interpretation of the error code.

Unknown code ([dec]) is out of range at

[chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

A runtime failure occurred in Ether-Ctrl

process. Typically, this is an internal error.
The message string indicates the reason
for the failure. This message also provides
an error code and a string interpretation of
[chars], port [dec], counter number [dec]\n the error code.

The particular scenario mentioned in the

message was detected for an unknown
reason. This is not a critical failure, the
process can continue functioning as
[chars], port [dec], counter number [dec]\n expected despite the event.
This message provides information about
the pluggable tranceiver. Possible causes
[chars] for port [dec] is disabled - [chars]\n are not supported speed, autoneg.
The particular operation mentioned in the
message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
[chars] for port [dec] is disabled - [chars]\n the failure.

[chars]\n

This message provides information about

the kind of events happening in the
software at the location where the error is
seen. This is not an error message.
Typically, following events are logged in
this message type. - End of successfull
initialization of the software. - Start and
end of a processing of new object that
needs to programmed to the hardware. Configuration is not applicable to the port.

'Details: [chars]'

Print the static/decode data information.

[chars]: [chars] ([chars]) (rc: [hex])

Failed to initialize debug in the platform

Ethernet loopback component

[chars]: [chars] (rc: [hex])

Failed to initialize error messaages in the

platform Ethernet loopback component

[chars]: [chars] (rc: [hex])

Failed to initialize IM connection in the

platform Ethernet loopback component

[chars]: [chars] (rc: [hex])

Failed to initialize PRM connection in the

platform Ethernet loopback component

[chars]: [chars] (rc: [hex])

Failed to initialize shared memory in the

platform Ethernet loopback component

[chars]: [chars] ([chars]) (rc: [hex])

Failed to initialize trace in the platform

Ethernet loopback component

[chars]: [chars] (rc: [hex])

Failed to initialize UIDB connection in the

platform Ethernet loopback component

The card is inactive due to front panel

ejector switch being pressed.

Crossbar driver detected that the front

panel ejector switches on the fabric card
were pressed/released to de-activate the
card but the card was not removed from
chassis.

Unable to access crossbar. Idx:[dec]

Crossbar driver detected an issue with ASIC

read and write access. A persistent ASIC
access error indicates an issue with the
hardware.

[chars]

Unable to get rackid.

[chars]

fpoe: ltrace_init2 for errors trace failed.

Fabric arbiter driver bkr module error on

[chars]

Fabric arbiter driver detected a bkr module

error

Fabric arbiter driver bkt module error on

[chars]

Fabric arbiter driver detected a bkt module

error

Fabric arbiter driver carb crm error on

[chars]

Fabric arbiter driver detected a carb crm

error

Fabric arbiter driver carb enqdeq error on

[chars]

Fabric arbiter driver detected a carb

enqdeq error

Fabric arbiter driver carb filter error on

[chars]

Fabric arbiter driver detected a carb filter

error

Fabric arbiter detected RX Msg Parity/CRC

error [chars]

Fabric arbiter detected RX Msg Parity/CRC

error

Fabric arbiter detected RX Link error

[chars]

Fabric arbiter detected RX Link error

Fabric arbiter driver serdes error on [chars] Fabric arbiter driver detected a serdes error

Fabric arbiter detected Sync error [chars]

Fabric arbiter detected link sync error

Fabric arbiter detected SCSM MBE [chars]

Fabric arbiter detected SCSM multi-bit error

Fabric arbiter driver acess non-exist

address location error

Fabric arbiter driver detected an access

non-exist address location error

Fabric arbiter driver cpu parity error

Fabric arbiter driver detected a parity error

from the CPU

Fabric arbiter driver protocol error

Fabric arbiter driver detected a protocol

error from the CPU

Fabric arbiter detected QCR FMT ERR

[chars]

Fabric arbiter detected QCR FMT Error

Fabric arbiter detected error in QCR Head

memory [chars]

Fabric arbiter detected QCR Head memory

module

Fabric arbiter detected QCR MEM0 ERR

[chars]

Fabric arbiter detected QCR MEM0 Error

Fabric arbiter detected QCR MEM1 ERR

[chars]

Fabric arbiter detected QCR MEM1 Error

Fabric arbiter detected QCR MEM2 ERR

[chars]

Fabric arbiter detected QCR MEM2 Error

Fabric arbiter detected QCR MEM3 ERR

[chars]

Fabric arbiter detected QCR MEM3 Error

Fabric arbiter detected PGAR Current

memory error [chars]

Fabric arbiter detected PGAR Current

memory error

Fabric arbiter detected QCR PGAR MAX

MEM ERR [chars]

Fabric arbiter detected QCR PGAR MAX

MEM ERR

Fabric arbiter detected error in QCR Tail

memory [chars]

Fabric arbiter detected QCR Tail memory

error

Fabric arbiter detected temperature fault

[chars]

Fabric arbiter detected temperature fault

Fabric arbiter detected XIF counter memory Fabric arbiter detected XIF counter memory
multi-bit error [chars]
multi-bit error

Fabric arbiter detected XIF GTFF0 memory

multi-bit error [chars]

Fabric arbiter detected XIF GTFF0 memory

multi-bit error

Fabric arbiter detected XIF GTFF1 memory

multi-bit error [chars]

Fabric arbiter detected XIF GTFF1 memory

multi-bit error

Fabric arbiter detected XIF GTFF2 memory

multi-bit error [chars]

Fabric arbiter detected XIF GTFF2 memory

multi-bit error

Fabric arbiter detected XIF RQFF memory

multi-bit error [chars]

Fabric arbiter detected XIF RQFF memory

multi-bit error

Fabric arbiter detected XIF VQI table multi- Fabric arbiter detected XIF VQI table multibit error [chars]
bit error

Still trying to create pdma queue on dev

[dec] after [dec] seconds

Cannot create pdma queue required. Likely

a asic driver does not come up properly %d
- 0 ingressq; 1 egressq; 2 fabricq 0; 3
fabricq 1 %d - number of seconds elapsed

An error was encountered while calling the

CCI (cpuctrl) cleanup function prior to
restarting the process as part of an IMDR
operation. The parenthesis contain the
CCI cleanup failed during the IMDR process error code and the corresponding string
restart ([hex]: [chars])
description for it.

One of the arguments required for the

process' signal handler to successfully
CCI cleanup failed during the IMDR process perform its CCI (cpuctrl) cleanup was
restart due to an invalid argument ([hex], invalid. The two pointer values are listed
[hex])
inside of the parenthesis.

[chars], with code([dec]) [chars]

Encounter problem during process

initialization. '%s' contains the explanation
of the problem. %s - error description %d error code %s - error code description

Failed to do registration with IPSLA Pak Fsv

area. Err: [chars]([dec])
Internal Error

Failed to find the qad queue for egress

packets. This could causes applications
using this qad queue not sending out
Failed to find necessary egress QAD queues packet %s - QAD queue name %s - thread
[chars] ([chars])
name

Failed to get depth of qad queue

0x[pointer]

Failed to get the qad queue depth(number

of packets in queue). This should be
because of some issues with the indicated
qad queue %p - QAD queue id

QAD transition notification failed

0x[pointer]

Failed to get the qad notification of queue

depth above or below watermark. This
normally indicates there is some issues
with the qad queue %p - QAD queue id

Failed to set [chars] for qad queue

0x[pointer]

Failed to set the watermark of the indicated

qad queue. This should be because of
some issues with the qad queue %s - high
or low watermark %p - QAD queue id

Still trying to connect to pak netio after

[dec] seconds

Cannot connect to netio pak server.

NULL parameters passed for thread

Failed to create thread due to internal error.

Error during IPSLA Time Stamping. Size:

[dec], error_type: [dec]

Internal Error

[chars], [hex], [dec], rc is [hex]

Cannot send packet to pdma queue %s error description %x - QAD queue id %d - 0

ingressq; 1 egressq; 2 fabricq 0; 3 fabricq 1
%x - error code

[chars], [dec], [dec], rc is [hex]

Cannot send packet to qad queue, likely

the qad queue is full and application does
not drain the qad queue fast enough %s error description %d - 0 ingressq; 1
egressq; 2 fabricq 0; 3 fabricq 1 %d queue number %x - error code

Still trying to create pdma queue on dev

[dec] after [dec] seconds

Cannot create pdma queue required. Likely

a asic driver does not come up properly %d
- 0 ingressq; 1 egressq; 2 fabricq 0; 3
fabricq 1 %d - number of seconds elapsed

[chars], with code([dec]) [chars]

Encounter problem during process

initialization. '%s' contains the explanation
of the problem. %s - error description %d error code %s - error code description

Failed to do registration with IPSLA Pak Fsv

area. Err: [chars]([dec])
Internal Error

Failed to find the qad queue for egress

packets. This could causes applications
using this qad queue not sending out
Failed to find necessary egress QAD queues packet %s - QAD queue name %s - thread
[chars] ([chars])
name

Failed to get depth of qad queue

0x[pointer]

Failed to get the qad queue depth(number

of packets in queue). This should be
because of some issues with the indicated
qad queue %p - QAD queue id

QAD transition notification failed

0x[pointer]

Failed to get the qad notification of queue

depth above or below watermark. This
normally indicates there is some issues
with the qad queue %p - QAD queue id

Failed to set [chars] for qad queue

0x[pointer]

Failed to set the watermark of the indicated

qad queue. This should be because of
some issues with the qad queue %s - high
or low watermark %p - QAD queue id

Still trying to connect to pak netio after

[dec] seconds

Cannot connect to netio pak server.

NULL parameters passed for thread

Failed to create thread due to internal error.

Error during IPSLA Time Stamping. Size:

[dec], error_type: [dec]

Internal Error

[chars], [hex], [dec], rc is [hex]

Cannot send packet to pdma queue %s error description %x - QAD queue id %d - 0

ingressq; 1 egressq; 2 fabricq 0; 3 fabricq 1
%x - error code

[chars], [dec], [dec], rc is [hex]

Cannot send packet to qad queue, likely

the qad queue is full and application does
not drain the qad queue fast enough %s error description %d - 0 ingressq; 1
egressq; 2 fabricq 0; 3 fabricq 1 %d queue number %x - error code

Still trying to create pdma queue on dev

[dec] after [dec] seconds

Cannot create pdma queue required. Likely

a asic driver does not come up properly %d
- 0 ingressq; 1 egressq; 2 fabricq 0; 3
fabricq 1 %d - number of seconds elapsed

An error was encountered while calling the

CCI cleanup function prior to restarting the
process as part of an IMDR operation. The
CCI cleanup failed during the IMDR process parenthesis contain the error code and the
restart ([hex]: [chars])
corresponding string description for it.

One of the arguments required for the

process' signal handler to successfully
CCI cleanup failed during the IMDR process perform its CCI cleanup was invalid. The
restart due to an invalid argument ([hex], two pointer values are listed inside of the
[hex])
parenthesis.

[chars], with code([dec]) [chars]

Encounter problem during process

initialization. '%s' contains the explanation
of the problem. %s - error description %d error code %s - error code description

Failed to do registration with IPSLA Pak Fsv

area. Err: [chars]([dec])
Internal Error

Failed to find the qad queue for egress

packets. This could causes applications
using this qad queue not sending out
Failed to find necessary egress QAD queues packet %s - QAD queue name %s - thread
[chars] ([chars])
name

Failed to get depth of qad queue

0x[pointer]

Failed to get the qad queue depth(number

of packets in queue). This should be
because of some issues with the indicated
qad queue %p - QAD queue id

QAD transition notification failed

0x[pointer]

Failed to get the qad notification of queue

depth above or below watermark. This
normally indicates there is some issues
with the qad queue %p - QAD queue id

Failed to set [chars] for qad queue

0x[pointer]

Failed to set the watermark of the indicated

qad queue. This should be because of
some issues with the qad queue %s - high
or low watermark %p - QAD queue id

Still trying to connect to pak netio after

[dec] seconds

Cannot connect to netio pak server.

NULL parameters passed for thread

Failed to create thread due to internal error.

Error during IPSLA Time Stamping. Size:

[dec], error_type: [dec]

Internal Error

[chars], [hex], [dec], rc is [hex]

Cannot send packet to pdma queue %s error description %x - QAD queue id %d - 0

ingressq; 1 egressq; 2 fabricq 0; 3 fabricq 1
%x - error code

[chars], [dec], [dec], rc is [hex]

Cannot send packet to qad queue, likely

the qad queue is full and application does
not drain the qad queue fast enough %s error description %d - 0 ingressq; 1
egressq; 2 fabricq 0; 3 fabricq 1 %d queue number %x - error code

[chars]

Fabric encountered fatal fault and is

isolating fabric plane to recover from the
fault. If this fault occurs on active RSP, it
would trigger chassis reload/switchover.

[chars]

Fabric encountered fatal fault and is

isolating fabric plane to recover from the
fault. If this fault occurs on active RSP, it
would trigger chassis reload/switchover.

Slot [dec]: Failure in Arbiter Serdes Links

Persistent failure in serdes link.

Persistent failure in serdes links to all

Slot [dec]: XBAR-MASK-[hex] may be faulty connected linecards.

Slot [dec]: Persistent failure in Serdes Links Persistent failure in serdes link.

[chars]

Number of active spine cards is less than

required. This could result in reduced fabric
bandwidth.

[chars]

Fabric encountered multiple fabric link

faults and is unable to recover.

[chars] [dec] [chars]

Fabric encountered fatal internal arb fabric

link fault and has reloaded linecard to
recover from this fault.

[chars] (slot [dec]) [chars]

Fabric encountered internal fabric link fault

and is bringing interfaces down to isolate
fabric slice.

[chars] (slot [dec]) [chars]

Fabric encountered multiple fabric link

faults toward single spine card. Spine card
is getting reloaded to recover from the
fault.

[chars]

Fabric encountered fatal fault and is

isolating spine card to recover from the
fault.

Fabric crossbars disabled from peer RSP

Peer RSP has disabled fabric crossbars.

[chars] [dec]

Fabric encountered transient fabric link

fault and has successfully recovered from
this error.

Encountered error when waiting for the

active/standby role of the RP. rc=[hex]

This message indicates that the fctl

process encounter an error when waiting
for the active RP notification. Process exits
and respawns.

card state [chars], [hex]

This message indicates that the fctl

process tries to set the state of an
unknown card.

Fabric control failed to initialize for data

checkpointing, errno = [hex]

This message indicates that the fctl

process encountered a problem when
trying to initialize data checkpointing.
Process will abort.

Fabric control failed to register for data

checkpointing, errno = [hex]

This message indicates that the fctl

encountered a problem when trying to
registering data for checkpointing. Process
will abort.

[chars]

This message indicates that the system did

not have enough memory available. [chars]
is the operation for which there was
insufficient memory. System may be in an
unstable state.

[chars]

This message indicates that the system did

not have enough memory available. [chars]
is the operation for which there was
insufficient memory. System may be in an
unstable state.

This message indicates that the fctl

Process event loop exited due to unknown process encounter an error in its event
errors. Abort
dispatcher.

No memory avaliable for [chars]

This message indicates that the system did

not have enough memory for initializing
the internal data structure.

Error detected in the fabric hardware :

[chars]

This message indicates the fctl process

detected a fabric hardware error.

Slot [dec] does not see fabric clock from

[chars]

The card in a particular slot failed to

synchronize clocks with the Master clock. If
this condition persists, the slot is unusable.
%d - indicates the slot number the card.

Failed to reset fabric card, slot=[dec] in

software

This message indicates the fctl process

trying to reset the fabric card on slot
number got failed. Slot number is marked
as malfunction and is shutdown.

Failed to send new fabric configuration to

slot [dec] after [dec] retries

The linecard on slot number failed to

receive the latest fabric configuration data.
Line card will be disconnected from the
fabric.

Failed sending slot bandwidth info to slot

[dec] after [dec] retries

The linecard on slot number failed to

receive the latest fabric bandwidth. Line
card will be disconnected from the fabric.

Failed to sync RP (slot=[dec]) to [chars]

(slot=[dec])

RP on a particular slot failed to synchronize

its clock with the Master clock. If this
condition presists, the RP on slot number is
unusable . If RP is the primary RP, then the
router is unusable. %d - indicates the slot
number the RP.

Could not sync primary RP (slot=[dec]) to

both CSC1 and CSC0

The primary RP failed to synchronize its

clock with either CSC.

Failed to sync [chars] (slot [dec]) to itself

The primary CSC failed to synchronize its

clock with itself.

LOS detected on fabric card in slot [dec],

shutting down the fabric card.

This indicates the fctl process got event

which is persistent LOS detected on one of
the fabric planes. The fabric card having
the issue will be shutdown.

Persistent LOS detected on [dec] fabric

planes.

LOS errors are seen multi fabric planes,this

could be issue with active node. This could
result in bringdown the system.

Unable to send MBUS msg. Error = [dec]

([chars])

This message indicates that an error

occurred when the card tries to
communicate with remote on fabric and
chassis management via MBUS. Chassis,
LCs and fabric is in a bad state.

new chassis bandwidth, [dec], cannot be

sent to clients. Error: [chars]

This message indicates the fctl process got

event which is that chassis bandwidth has
changed but fctl process cannot send the
info to its clients.

Encountered critical problem in

initialization of [chars]

This message indicates that the system

cannot initialize the fctl process.

This message indicates that fabric card has

a wrong or unsupported version of FPGA.
Fabric Card type [hex] has an unsupported Software cannot monitor the fabric card
FPGA version. Card will be shutdown
and it is shutdown.

Failure detected on fabric cards [chars] in

connecting LC/RPs [chars].

Thiere is a failure in connecting LC/RPs

from fabric due to one of the following
reasons either temporary/permanent. 1.
There has been a problem in
communication over the MBUS. 2. The
fabric cards indicated in mask have
hardware problem. 3. A LC/RP with bad
hardware impacting the MBUS
communication is is inserted.

Failure detected on fabric cards [chars] in

diconnecting LC/RPs [chars].

There is a failure in disconnecting LC/RPs

from fabric due to one of the following
reasons either temporary/permanent. 1.
There has been a problem in
communication over the MBUS. 2. The
fabric cards indicated in mask have
hardware problem. recommended_action:
Safely ignore the message if it's one time
and no impact on the system. Ensure that
all the firmware on fabric cards are upto
date. Replace the fabric card indicated in
the message if the problem persists. If
problem is reported on multiple fabric
cards, *SUPPORT*.

Failed to determine card type of slot [dec]

in [dec] retries

This message indicates that the Fabric

Controller Software on the active RP has
failed to determine the card type for card
in slot <slot> through <retries> attempts
from the mbus agent.

This message indicates that an error

RP Communication fails with remote node : occurred in fctl process when RP tries to
[chars], errno=[hex], [chars]
communicate with remote node via MBUS.

Error in initializing the fabric debugs:

[chars]

The fctl process Unable to initialize the

debugging facility of fabric MIB. Other
fabric MIB capabilities are not disturbed.

Encountered error restoring checkpointed

data

This message indicates that the system

cannot restore checkpointed data of the
fctl process.

Unable to create thread to detect card

insertion/removal for register [dec] :
rc=[hex], [chars]

There is a critical problem when fctl

process trying to creating a thread to
detect lincard insertion and removal.
Linecards, fabric cards, and RP insertion
and removal may not be handled correctly.

The fctl process got an event which

indicates the software installed on the
system does not recognize the chassis
type. The Backplane Server has not
The chassis type is not known from reading provided the chassis model. Software
the backplane
cannot monitor the chassis and will abort.

Unknown msg from slot [dec] with msg

type [hex]

This message indicates that the fctl

process received an unknown msg from
remote node. The message can be ignored.

Chassis type [dec] not supported

This message indicates that the software

installed on the system does not recognize
the chassis type. Software cannot monitor
the chassis fabric. Fabric cards are
shutdown.

This logs will be thrown when we are trying

add/remove a configuration in non root LR.
In a MLR configured chassis, all
I am on non root LR, configuration allowed configuration has to be carried out from the
only from ROOT
ROOT LR.

Fabric card [chars] unavailable

Fabric cards (CSC/SFC) are unvailable or

properly not seated in slot. Note: CSCs
should be in slot 16 or 17 and SFCs should
be in slot 18-22. recommended_action: Use
the 'show platform' command check the
availability of fabric cards.If fabric cards are
not detected then try following corrective
action in order (1)Reseat the undetected
fabric cards (2) swap the active RP (3) try
one alarm card at a time (4) power cyle the
chasis *RECUR*

multicast-priority config has no effect on

this chassis type

This message indicates that hw-module

fabric multicast-priority was configured but
this configuration has no effect on this
chassis. It only applies to non-Sphere
124xx chassis. The chassis type is an
internal type value.

sysdb operation [chars] failed (reason:

[chars])

This message indicates fctl process lock

the sysdb resource and at the same time
show api process is trying to acess got fail.
%s - Failed operation. %s - Failure reason.

Fabric card [chars] inserted in slot [dec]

The fabric card on slot number is inserted

into the chassis. The fabric control software
takes care of its insertion automatically.
The chassis fabric and card's Fabric
Interface ASIC are re-configured
accordingly.

The fabric card on slot number is removed

from the chassis. The fabric control
software takes care of its removal
automatically. The chassis fabric and card's
Fabric Interface ASIC are re-configured
Fabric card [chars] removed from slot [dec] accordingly.

ClkCtrl detected an overcurrent condition

on Fan [chars], please replace the fantray
immediately

ClkCtrl detected an overcurrent condition

on Fan

[chars]%s

This message indicates fault manager

client on the LC is unable to send messge
to server. Fault manager client will try to
connect to LWM channel for sending fault
indication to the server. If the channel
connect or message send fails error details
will be displayed. Subsequent LWM
messges for clint will succed.*RECUR* %s Error details %s - why the error occured

ERROR while ([chars]%s)

This error indicates failure in fault manager

client for E3/E5 Linecard. This is a non
service impacting message. %s - indicates
where the error occured %s - why the error
occured

[chars]

This is a informational message from E7

fault manager. This indicates that fault
manager has received a fault message. %s
- Message to be displayed

[chars]

This is a informational message %s message that needs to be displayed to the

user

Max errors of [dec] will be tolerated in

[dec] sec\n

This informational message tells the timer

wheel configuration %d - max_errors %d max_timer

Process Initialization Failed: ([chars]%s)

The fault-mgr process failed to initialize.

This process controls all ASIC resets on all
LC's for either internal ASIC problems or
larger system issues (ie, fabric control). %s
- indicates the reason for the failure. There
are 3 types of possible failures, these
include: - Checkpointing
initialization/creation/restore - Server
initialization - Client initialization %s - is the
decoded error reason

ERROR while ([chars]%s)

This error indicates failure in fault manager

client for E7 Linecard. This is a non service
impacting message. %s - why the error
occured

ERROR while ([chars]%s)

This ios_msg can be used for all kinds of

error %s - indicates where the error
occured %s - why the error occured

Error occured in:[chars], rate

exceeded.So,send MBUS msg\n

Print the device name in which the error

occured.

Reset LC [dec]: Reason - [chars]

PRP Platform Manager process received an

mbus message from the LC fault-mgr
process saying the LC will be reloaded. The
platform-mgr process is only reporting this
message, via mbus, for the LC fault-mgr
process - as some HW devices have failed
and the slow-path will be down. %d - is the
slot number of the LC that will be reloaded.
%s - Contains the reason for the LC reload.

LC [dec]: Reset Device - [chars]

PRP Platform Manager process received an

mbus message from the LC fault-mgr
process saying HW devices will be reset.
The platform-mgr process is only reporting
this message, via mbus, for the LC faultmgr process - as HW devices are being
reset and the slow-path will be down. There
will be traffic loss on the LC. %d - is the slot
number of the LC with the faulty device.
%s - is the Device and Instance of the fault
being addressed.

Device driver for mac detected SEU

uncorrectable error

Device driver detected a Multi Bit Error or

CRC or uncorrectable Single Bit Error for
this device

Device driver for device '[chars]' detected

clock reference failure / DPLL unlock
indicator on '[chars]'. GPIO reporting the
problem is [dec].

Device driver detected a clock failure on

some bus/port

PHY controller driver version is not

compatible with the hardware version.
[chars]

PHY controller driver version is not

compatible with PHY controller hardware
version.

PHY controller driver detected a parity

PHY controller driver detected parity errors error.

PHY controller driver version is not

compatible with the hardware version.
[chars]

PHY controller driver version is not

compatible with PHY controller hardware
version.

PHY controller driver detected a parity

PHY controller driver detected parity errors error.

Port controller version is not compatible

with the hardware version. [chars]

Port controller driver version is not

compatible with the hardware version.

Port controller driver detected parity errors Port controller driver detected a parity error

Port controller version is not compatible

with the hardware version. [chars]

Port controller driver version is not

compatible with the hardware version.

Port controller driver detected parity errors Port controller driver detected a parity error

Port controller driver version is not

compatible with the hardware version.
[chars]

Port controller driver version is not

compatible with the hardware version.

Port controller driver detected parity errors Port controller driver detected a parity error

Device driver for device '[chars]' detected

invalid address error on '[chars]'. Error
address [hex]. Error access type [hex].

Device driver detected invalid address

error on some bus

PHY controller driver version is not

compatible with the hardware version.
[chars]

PHY controller driver version is not

compatible with the hardware version.

PHY controller driver detected a parity

PHY controller driver detected parity errors error.

[chars] Link TX fault error on port [dec]

Port controller driver detected a TX fault on

the transceiver port.

Device driver version is not compatible

with the hardware version. [chars]

Device driver version is not compatible

with the hardware version.

Device driver detected parity errors.

[chars]

Device driver detected a parity error for

this device (FPGA/CPLD/ASIC)

Device driver for mac detected SEU

correctable error

Device driver detected a Single Bit Error for

this device which is correctable

Device driver for device '[chars]' detected

the error '[chars]'

Device driver detected an error

Device driver for device '[chars]' detected

sequence error on '[chars]'. Error status
Device driver detected sequence error on
[hex]. Error address [hex]. Error data [hex]. some bus, this could be software error

SFP I2C PHY Ack error

Port controller driver detected I2C access

error on PHY SFP port.

Port controller driver detected I2C timeout

I2C PHY operation got either aborted/failed error on PHY SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 0
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 1
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 10
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 11
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 12
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 13
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 14
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 15
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 16
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 17
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 18
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 19
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 2
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 20
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 21
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 22
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 23
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 24
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 25
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 26
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 27
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 28
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 29
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 3
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 30
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 31
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 32
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 33
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 34
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 35
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 36
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 37
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 38
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 39
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 4
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 5
the SFP port.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 6
the SFP port 6.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 7
the SFP port 7.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 8
the SFP port 8.

Port controller driver detected a TX fault on Port controller driver detected a TX fault on
the SFP port 9
the SFP port 9.

Port controller version is not compatible

with the hardware version. [chars]

Port controller driver version is not

compatible with the hardware version.

PortCtrl controller driver detected parity

errors

Port controller driver detected a parity

error.

Device driver for device '[chars]' detected

parity errors in Tx/Rx on '[chars]'. Error
status [hex]. Error address [hex]. Error data Device driver detected a parity error for
[hex].
this device

Device driver for device '[chars]' detected

IO timeout on '[chars]'. Timeout address
[hex]. Timeout access [hex].

Device driver detected a timeout on some

bus

PHY controller driver version is not

compatible with the hardware version.
[chars]

PHY controller driver version is not

compatible with PHY controller hardware
version.

PHY controller driver detected a parity

PHY controller driver detected parity errors error.

Port controller driver detected I2C access

error on XFP port

Port controller driver detected I2C access

error on XFP port.

XFP Link TX fault error on port 0

Port controller driver detected a TX fault on

the XFP port.

XFP Link TX fault error on port 1

Port controller driver detected a TX fault on

the XFP port.

XFP Link TX fault error on port 2

Port controller driver detected a TX fault on

the XFP port.

XFP Link TX fault error on port 3

Port controller driver detected a TX fault on

the XFP port.

XFP Link TX fault error on port 4

Port controller driver detected a TX fault on

the XFP port.

XFP Link TX fault error on port 5

Port controller driver detected a TX fault on

the XFP port.

XFP Link TX fault error on port 6

Port controller driver detected a TX fault on

the XFP port.

XFP Link TX fault error on port 7

Port controller driver detected a TX fault on

the XFP port.

Port controller driver detected I2C access

error on SFP port

Port controller driver detected I2C access

error on SFP port.

Port controller driver detected I2C timeout Port controller driver detected I2C timeout
error on SFP port
error on SFP port.

After completing Field Diags, the EEPROM

update was requested, but there was a
read failure during the process. Internal
error: Contact Cisco's TAC. This error could
be a software problem or could be related
to failing hardware. Please report this to
failure reading EEPROM ([chars]) values
TAC along with other supportive log
during Field Diag EEPROM update: EEPROM information to determine the best course of
not updated
action for this UUT.

failure writing EEPROM @ offset of [hex]

during Field Diag EEPROM update: This
byte not updated

After completing Field Diags, the EEPROM

update was requested, but there was a
write failure during the process. Internal
error: Contact Cisco's TAC. This error could
be a software problem or could be related
to failing hardware. Please report this to
TAC along with other supportive log
information to determine the best course of
action for this UUT.

Unable to kill this existing Field Diag

process: rc from kill was [dec]

Could not kill that job ID for Field Diags

Internal error: Contact Cisco's TAC. This
error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

The current IOS-XR field diagnostics

command failed because the software
The [chars] buffer is too small - need [dec]; found that an internally configured buffer
have [dec].
was not large enough.

Cannot determin Job ID for Field Diags

process

Error getting JID Internal error: Contact

Cisco's TAC. This error could be a software
problem or could be related to failing
hardware. Please report this to TAC along
with other supportive log information to
determine the best course of action for this
UUT.

cannot send mbus messages: errno [dec]:

[chars]()

Unable to complete sending mbus error

message Internal error: Contact Cisco's
TAC. This error could be a software problem
or could be related to failing hardware.
Please report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

Fabric card MBUS Ram Agent not loaded

prior to beginning Field Diags Fabric tests

After launching Fabric Field Diagnostics, the

fabric card appear not have MBUS Ram
Agent loaded within the appropriate time.
Internal error: Contact Cisco's TAC. This
error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

Problems occurred while trying to

disconnect slot [dec] from the fabric.
RC=[hex]

Field diagnostics encountered a failure

while trying to restore the fabric for the slot
that was just tested. Field diagnostics uses
a FCTL API to disconnect the slot under test
from the fabric when it is done. This API
failed, returning the specified return value.

Field diagnostics encountered a failure

while trying to restore the fabric for the slot
that was just tested. Other software errors
Problems occurred while trying to clear the should have been logged before this to
fabric.
provide details about what failed.

Failed to fork Field Diags process: [chars]

Call to fork process for Field Diags failed for

given reason Internal error: Contact Cisco's
TAC. This error could be a software problem
or could be related to failing hardware.
Please report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

Cannot read jid data from file

Could not read that job ID for Field Diags

from the file Internal error: Contact Cisco's
TAC. This error could be a software problem
or could be related to failing hardware.
Please report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

[chars]() could not determine the idle cell

generation address.

Field diagnostics was not able to determine

the idle cell generation address for the
router's fabric.

Error opening halt request file. Internal

error: Contact Cisco's TAC. This error could
be a software problem or could be related
to failing hardware. Please report this to
TAC along with other supportive log
Unable to open Field Diags halt request file information to determine the best course of
[chars]: [chars]
action for this UUT.

Unable to write Field Diags halt request to

file [chars]: [chars]

Error writing HALT request file Internal

error: Contact Cisco's TAC. This error could
be a software problem or could be related
to failing hardware. Please report this to
TAC along with other supportive log
information to determine the best course of
action for this UUT.

Unable to open Field Diags state file

[chars]: [chars]

Error opening JID file Internal error: Contact

Cisco's TAC. This error could be a software
problem or could be related to failing
hardware. Please report this to TAC along
with other supportive log information to
determine the best course of action for this
UUT.

Unable to read Field Diags state from file

[chars]: [chars]

Error reading JID file Internal error: Contact

Cisco's TAC. This error could be a software
problem or could be related to failing
hardware. Please report this to TAC along
with other supportive log information to
determine the best course of action for this
UUT.

Unable to write Field Diags state to file

[chars]: [chars]

Error writing JID file Internal error: Contact

Cisco's TAC. This error could be a software
problem or could be related to failing
hardware. Please report this to TAC along
with other supportive log information to
determine the best course of action for this
UUT.

Failed to Connect to sysloader initially

Internal error: Contact Cisco's TAC. This
error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
could not connect to LWM [chars] in [chars] supportive log information to determine
()
the best course of action for this UUT.

could not send LWM in [chars]()

Failed to Connect to sysloader initially

Internal error: Contact Cisco's TAC. This
error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

could not LWM disconnect from [chars] in

[chars]()

Failed to Connect to sysloader initially

Internal error: Contact Cisco's TAC. This
error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

UUT launch failed ([chars]). Exiting.

Failed to Connect to sysloader initially

Internal error: Contact Cisco's TAC. This
error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

No response from UUT in ~[dec] minutes

([dec] seconds). exiting

No communication from the UUT in a while.

UUT likely became inoperable. Internal
error: Contact Cisco's TAC. This error could
be a software problem or could be related
to failing hardware. Please report this to
TAC along with other supportive log
information to determine the best course of
action for this UUT.

Unable to open Field Diags state file

[chars]: [chars]

Error opening JID file Internal error: Contact

Cisco's TAC. This error could be a software
problem or could be related to failing
hardware. Please report this to TAC along
with other supportive log information to
determine the best course of action for this
UUT.

internal (FSM) state change ILLEGAL: was

[chars], attempted [dec]

Bad internal state change Internal error:

Contact Cisco's TAC. This error could be a
software problem or could be related to
failing hardware. Please report this to TAC
along with other supportive log information
to determine the best course of action for
this UUT.

40G fabric is not supported on 12x04

chassis

Field diagnostics has been asked to do a

40G operation on a 12x04 chassis, which is
not a supported fabric chassis combination.
Field diagnostics is proceeding with the
action as if this where not a 40G fabric.

Field diagnostics validated a slot value

before using it and found that it was
invalid. Consequently this event was
raised. Other field diagnostics errors will be
raised to further explain the impact of this
[chars]() encountered an invalid slot ([dec]) problem.

[chars]. Failing path is ([chars])

The field diagnostics proxy on the standby

RP has received an install path from the
install infrastructure, but it is not formatted
as expected. Consequently field
diagnostics is not able to execute on the
standby RP.

Could create nodeid for slot [dec]: [chars]

in [chars]()

Failed to create a node identifier. Internal

error: Contact Cisco's TAC. This error could
be a software problem or could be related
to failing hardware. Please report this to
TAC along with other supportive log
information to determine the best course of
action for this UUT.

misc svcs: [chars]: could not read primary

clock

Failed to read Primary Clock from fctl

Internal error: Contact Cisco's TAC. This
error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

Failed to read a slot-specific register via an

mbus-access Internal error: Contact Cisco's
TAC. This error could be a software problem
or could be related to failing hardware.
Please report this to TAC along with other
Failed to read register [hex] from slot [dec]. supportive log information to determine
Errval=[hex].
the best course of action for this UUT.

misc svcs: [chars]: Undefined

MBUS_MISC_SVCS message received:
Ignored: msg [hex]

Misc services server received an

unrecognized message Internal error:
Contact Cisco's TAC. This error could be a
software problem or could be related to
failing hardware. Please report this to TAC
along with other supportive log information
to determine the best course of action for
this UUT.

Failed to write [hex] to register [hex] on

slot [dec]. Errval=[hex].

Failed to write a slot-specific register via an

mbus-access Internal error: Contact Cisco's
TAC. Collect syslogs, verbose run log and
show diags detail.

Failed to read xbar map from fctl Internal

error: Contact Cisco's TAC. This error could
be a software problem or could be related
to failing hardware. Please report this to
TAC along with other supportive log
information to determine the best course of
misc svcs: [chars]: could not read xbar map action for this UUT.

Cannot determine which CSC is the

primary. RC:[dec]-[dec]

Field diagnostics needs to know which CSC

is the primary before it can run on the
fabric cards. However, it was not able to
determine which CSC was the primary. The
field diagnostics run stops.

no time of day

Time of Day unavailable internally

Failed to extract node id from var: line

[dec]

One of the calls to a node ID extraction

function returned an error Internal error:
Contact Cisco's TAC. This error could be a
software problem or could be related to
failing hardware. Please report this to TAC
along with other supportive log information
to determine the best course of action for
this UUT.

Unexpected message received during

\UUT_ON\ state: sub-msg [hex] from slot
[dec]

Field Diags was not expecting this type of

message at this time. If this problem
persists and diags does not complete,
Contact Cisco's TAC. This error could be a
software problem or could be related to
failing hardware. Please report this to TAC
along with other supportive log information
to determine the best course of action for
this UUT.

Failed to validate field diagnostic request.

Unexpected return code: [dec]

There is some problem with field diagnostic

software since a function has returned an
unexpected value. Internal error: Contact
Cisco's TAC. This error could be a software
problem. Please report this to TAC along
with other supportive log information to
determine the best course of action for this
UUT.

Failed to write a value to the register in the

specified slot or broadcast group. Internal
Failed [chars] write [hex] to register [hex] error: Contact Cisco's TAC. Collect syslogs,
on slot/broadcast group [dec]. Errval=[hex] verbose run log and show diags detail.

This card requires a special version of

mbus Ram Agent for compatibility with
diags for C2W requests for SPA
communication Internal error: Contact
Cisco's TAC. This error could be a software
problem or could be related to failing
hardware. Please report this to TAC along
with other supportive log information to
determine the best course of action for this
FAILURE re-loading default mbus ram agent UUT.

Unable to obtain file path for RP field

diagnostics image. Fail code: [hex]

The field diagnostics proxy on the standby

RP was not able to determine the file path
for the RP's field diagnostics binary. An
infrastructure function failed, returning the
fail code displayed. Consequently, field
diagnostics is not able to execute on the
standby RP.

Unable to obtain install path for RP field

diagnostics image. Fail code: [hex]

The field diagnostics proxy on the standby

RP was not able to determine the install
path for the RP's field diagnostics binary.
An infrastructure function failed, returning
the fail code displayed. Consequently, field
diagnostics is not able to execute on the
standby RP.

Unable to identify SPA's inserted in slot

[dec]

The field diags processs was unable to

determine which SPAs where inserted in
the SIP. Internal error: Contact Cisco's TAC.
This error could be a software problem or
could be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

Requested instance ([dec]) (bay) not

supported by this UUT (min=[dec],
max=[dec])

Spa bay requested not supported

Download of LC Ram Agent

diag_mbus_ram.ucode failed

Download of diag_mbus_ram.ucode failed

Internal error: Contact Cisco's TAC. This
error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

Cannot connect to the system data base.

Field diagnostics cannot be run.

Cannot bind to path /admin/oper/instmgredm/gl in the system data base. This path
is used to get the current setting of the
config-register on the standby RP. Internal
error: Contact Cisco's TAC. This error could
be a software problem. Please report this to
TAC along with other supportive log
information to determine the best course of
action for this UUT.

Coding violation: Sysldr code returns

unexpected cause. Internal error: Contact
Cisco's TAC. This error could be a software
problem or could be related to failing
hardware. Please report this to TAC along
with other supportive log information to
Result code from sysloader ([dec]) exceeds determine the best course of action for this
list of known messages
UUT.

Sysldr reporting error - Field Diags will not

commence testing

Sysldr reporting error - time to quit Field

Diags Internal error: Contact Cisco's TAC.
This error could be a software problem or
could be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

time of day conversion error

Internal error: Contact Cisco's TAC. This

error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.
Internal Time Of Day conversion error

Card type ([dec]) is NOT recognized

This card type is not recognized in this

version

Card type not supported

This card type is not supported in this

version

Unable to get variable '[chars]'. Fail code:

[hex]

The field diagnostics proxy on the standby

RP was not able to obtain the specified
environment variable. Consequently it was
not able to adjust the environment to run
the field diagnostics application on the
standby RP.

Unable to set variable '[chars]'. Fail code:

[hex]

The field diagnostics proxy on the standby

RP was not able to modify the specified
environment variable. Consequently it was
not able to adjust the environment to run
the field diagnostics application on the
standby RP.

BOOT variable is already set.

The field diagnostics proxy on the standby

RP was attempting to modify the standby's
environment variables in order to run the
field diagnostics binary. However, it found
that the BOOT variable was already set.
This is unexpected, but should not be
harmful. The application continued with its
attempt to load and run the field
diagnostics application on the standby RP.

Unexpected return value from reporting

results to sysldr: [chars]

Resulting response from sysldr after

reporting final results indicates a nonhappy sysldr. Reason in string from sysldr
Internal error: Contact Cisco's TAC. This
error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

There is a problem with the standby RP

state. Field diagnostics cannot be run

The standby RP does not respond to a

configuration query from the active RP. The
system data base (sysdb) get of the
tuple /admin/oper/instmgr-edm/gl/configregister has failed for the standby RP.
Internal error: Contact Cisco's TAC. This
error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

Unexpected Misc Services message

subtype [dec] received from slot [dec]

An unexpected MBUS_FDIAG MISC Services

message was received from UUT. Possibly a
mal-formed or unfinished software
enhancement. Internal error: Contact
Cisco's TAC. This error could be a software
problem or could be related to failing
hardware. Please report this to TAC along
with other supportive log information to
determine the best course of action for this
UUT.

Unexpected message subtype [dec]

received from slot [dec]

An unexpected MBUS_FDIAG message was

received from UUT. Possibly a mal-formed
or unfinished software enhancement.
Internal error: Contact Cisco's TAC. This
error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

IOS-XR Field diagnostics is not currently

supported on the specified RP
Field diagnostics cannot be run on [chars]. configuration.

WARNING: Field diagnostics cannot be run

with the current config-register setting

The router must be configured to auto boot

the standby RP from disk if the user wants
to run field diagnostics on the standby RP.
The config-register setting may have been
changed manually to the wrong setting by
the user.

Deleted orphaned Field Diags jid file

A file from a previous instance of Field

Diags was left. We have now deleted it.

Field Diagnostics can only be invoked when The field diagnostics can only be invoked
PRP is in IOX Running state.
when the PRP is in IOX Running state.

Field Diags download completed on slot

[dec]. Status: [chars]

This is a notice field diags has been

downloaded to the specified slot. The next
step is that field diags will start running on
the specified slot.

Field Diags downloading to slot [dec]

This is a notice that field diags has started

to download to the specified slot.

Field Diags completed for slot [dec]

This is a notice that field diags has

completed on the specified slot. This is the
last field diags related message for this
slot.

A halt request is present: Shutting down

Field Diags process (FSM)

FSM has detected that a halt is to be

initiated

Longest time inactivity ([dec] secs)(~[dec] The longest time difference message
minutes) just after [[chars]]
preceding this

Can not open /dev/console to write, fdiag

quits

Cannot open console for output. Internal

error: Contact Cisco's TAC. This error could
be a software problem or could be related
to failing hardware. Please report this to
TAC along with other supportive log
information to determine the best course of
action for this UUT.

Successfully terminated Field Diags

(jid=[dec], Field Diags state file [chars])

Success in terminating Field Diags instance

on a particular slot

Total Test Time: ~[dec] minutes ([dec]

seconds)

Ho long this set of tests ran for

Now restoring default ram agent ([chars])

This card had the diags ram agent loaded

for the test, but will now restore the system
one Internal error: Contact Cisco's TAC. This
error could be a software problem or could
be related to failing hardware. Please
report this to TAC along with other
supportive log information to determine
the best course of action for this UUT.

Linecard type requires

diags_mbus_ram.ucode - downloading

This card requires a special version of

mbus Ram Agent for compatibility with
diags for C2W requests for SPA
communication Internal error: Contact
Cisco's TAC. This error could be a software
problem or could be related to failing
hardware. Please report this to TAC along
with other supportive log information to
determine the best course of action for this
UUT.

Field Diags starting on slot [dec]

This is a notice that a user has started field

diags on the specified slot.

Sysldr notified of completion: params sl:

[dec] wait:[hex] diag_stats:[hex] roe_flag:
[hex]

Just finishing diag command and telling

sysldr to handle finished diags state on the
same slot

Field diagnostics has completed, where the

message identifies the final status, the
Field Diags COMPLETE on UUT ([chars])
card's numeric and string type as well as
[chars], card type [dec], [chars] s/n [chars] its serial number.

[chars]

Non error-specific redirected output from

diag process to syslog. This may be test
names, progress messages, or failure
information generated by the UUT.

Field Diags COMPLETE on UUT ([chars])

[chars] card type [dec] [[chars]] s/n
[chars]\n

Field Diagnostics final results

UUT [chars]: [chars]

Text output from UUT (Cisco use only) Non

error-specific redirected output from diag
process to syslog. This may be test names,
progress messages, or failure information
generated by the UUT.

UUT (init) [chars]: [chars]

Text output from UUT during init state

(Cisco use only) Non error-specific
redirected output from diag process to
syslog. This may be test names, progress
messages, or failure information generated
by the UUT.

Forcing into FSM mode, even though sysldr Internal use - ignoring sysldr error,
load UUT returned error
continuing to Field Diags FSM

During Init state, unexpected mbus submessage [hex] received from slot [dec]

Field Diags was not expecting this type of

message at this time. If this problem
persists and diags does not complete,
Contact Cisco's TAC. This error could be a
software problem or could be related to
failing hardware. Please report this to TAC
along with other supportive log information
to determine the best course of action for
this UUT.

A software error occurred in the FromFab

driver component during initialization:
[chars]

The fabricq_prp_driver process which

controls the FromFab driver on the route
processor has failed to initalize and cannot
recover automatically. This is a software
fault. The FromFab driver controls the
hardware that receives data from the
fabric. It runs in the fabricq_prp_driver
process. An unrecoverable failure of the
fabricq_prp_driver process may prevent
this route processor card from
communicating with other cards on the
chassis. %s indicates the type failure

This message indicates that a buffer was

Corrupted packet, start_offset [hex], length received from the fabric with a corrupted
[unsigned int], slot [unsigned int]
buffer header.

Assembler packet pointer corrupt: pkt

[hex], dgram [hex], oq [hex]

This message indicates that the

reassembly buffer pointer used by
assembler is incorrect.

ffq manager encountered a fatal error and

is not able recover from the error. A reason
text will be supplied call support with this
ffq: fatal error encountered, reason=[chars] text.

ffq: fatal error encountered,

reason=[chars], errno=[dec]

ffq encountered a fatal error and is not able

to recover from the error. A reason text will
be supplied call support with this text. An
integer errno will also be printed.

ffq: general information,<[chars]>

The FFQ's informational message.

ffq: service degrading error, reason =

[chars]

The ffq encountered an error that would

lead to degraded service.

FFQ: queue [dec] alloc [dec] bytes error for FFQ encountered a fatal memory allocation
ptr [hex] of max [hex]\n
error

This message indicates that Assembler

driver is not able to allocate memory for
No memory available for Assembler queues the Queues and other use. This usually
in [chars]
indicates a memory problem.

No buffers available for Assembler error

[unsigned int]

This message indicates that there are too

many messages coming from the GSR Line
Card. There are no more buffers on the RP
to handle these messages. Try shutting
down debugs on Line Card or reloading it.

ffq: this function <[chars]> is not yet

implemented

FFQ, a function was not implemented.

The fabric driver has failed to return a

packet buffer received from the fabric to
the free list. If this error keeps recurring it
could result in the depletion of buffer for
packet received on the route processor
The fabric driver failed to return a buffer to from the fabric. %s is the entity processing
the free list from: [chars]
the packet.

Invalid packet type [dec]

FFQ has received an invalid packet type

from the fabric.

No timer interval for [chars]

An internal data structure was missing a

field.

No timer wheel for [chars]

An internal data structure was missing a

field.

Call to [chars] failed, cerrno=[hex]

The library call failed.

ffq: invalid option <[chars]> passed to ffq

server

Startup option supplied to FFQ is not valid.

FFQ has received an invalid packet type

from the fabric. This error will not affect the
Invalid packet type received from fabric on functionality or stability of the system. %d
route processor: [dec]
packet type received

[chars]

PLATFORM FIB, error

[chars] [chars] [chars] [dec]

PLATFORM FIB, error information

[chars] [chars] [chars] [dec]

An internal error occurred in FIB engine

layer for collecting traces. The message
string indicates the reason for the failure.
This message also provides an error code.
Additionally, it provides a more verbose
information of the error.

[chars] [chars] [chars] [dec]

An internal error occurred in FIB engine

layer for collecting traces. The message
string indicates the reason for the failure.
This message also provides an error code.
Additionally, it provides a more verbose
information of the error.

[chars] [chars] [chars] [dec]

An internal error occurred in FIB engine

layer for collecting traces. The message
string indicates the reason for the failure.
This message also provides an error code.
Additionally, it provides a more verbose
information of the error.

[chars]: [chars] ([unsigned int])

PLATFORM FIB, error information

[chars]: [chars] ([unsigned int])

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]: [chars] ([unsigned int])

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]

PLATFORM FIB, error

[chars]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars] [dec] [chars] [chars] [dec]

PLATFORM FIB, error information

[chars] [dec] [chars] [chars] [dec]

An internal error occurred in FIB engine

layer for collecting traces. The message
string indicates the reason for the failure.
This message also provides an error code.
Additionally, it provides a more verbose
information of the error.

[chars] [dec] [chars] [chars] [dec]

An internal error occurred in FIB engine

layer for collecting traces. The message
string indicates the reason for the failure.
This message also provides an error code.
Additionally, it provides a more verbose
information of the error.

[chars] [dec] [chars] [chars] [dec]

Bad command option: [chars] [chars]

An internal error occurred in FIB engine

layer for collecting traces. The message
string indicates the reason for the failure.
This message also provides an error code.
Additionally, it provides a more verbose
information of the error.
Bad coammand option.

[chars]: [chars] in function [chars] at line

[dec]

Error occured with file operations.

Failed in allocating memory in function

[chars] at line [dec]
[chars] [chars]

No enough memory.
Output progress to RP console.

[chars] version [dec].[dec] is not supported

for this board.
Invalid FPD version to RP console.

fpd-err: [chars] [chars]

This is an error message from FPD

operation. It indicates error condition was
encountered in FPD operation.

fpd-init-err: [chars] [chars]

This is an error message during initializing

one of FPD processes.

FPD-WARN: [chars]

This is a warning message from FPD

operation.

fpd-info: [chars] [dec] [chars]

This is a info message from FPD operation.

fpd-debug: [chars]

This is a debug message from FPD

operation.

MAC[dec] FPGA PLL failed to lock.

val=[hex]\n

This message indicates an error occurred

due to fpga PLL lock failure.The PLL lock
has reached the maximum retry.

Failed to retrieve RP FPGA base address ,

type [dec], processid [dec]\n

This message indicates an error occurred

due to wrong FPGA RP type.The base
address of the FPGA can not be retrieved
due to wrong FPGA type as input.

Node reset initiated by PID: [dec]

The FPGA Manager api for resetting the

board via a control register has been called
by the process with the specified PID.

Node reset initiated by PID: [dec]

The FPGA Manager api for resetting the

board via a control register has been called
by the process with the specified PID.

Error initializing PD lib [dec]

An error occurred when loading the PD

library for a specific platform's dll for
device access, causing the process to
return unexpectedly.

FPGAMGR:[chars]

The FPGA Manager, interrupt handling

thread, failed to spawn. %s-Error
Description.

Could not init ltrace buffer

Due to an error in the ltrace initialization

routines, the init failed. This may be due to
other problems on the system (is ltrace
running?).

The process was unable to map and

configure a shared memory window,
Error while mapping and configuring shared causing the process to return unexpectedly.
memory [dec]
Debugs will provide more info
FPGAMGR:[chars]

The FPGA Manager, init completed. %sMessage Description.

Checkpoint library could not allocate

memory for Sync Controller check-point
data.

Checkpointing is a mechanism to update

the redundant RSP with the current
configuration and status of the system to
help takeover in case of a failover. The
checkpoint mechanism needs to be
initialized for Sync-controller to update the
standby RSP with current frequency
syncronization status. This failure could be
because of memory allocation failure.

Sync-controller is the software component

which controls the synchronization devices
in the system. Checkpointing is a
mechanism to update the redundant RSP
with the current configuration and status of
the system to help takeover in case of a
failover. The checkpoint mechanism needs
to be initialized for Sync-controller to
update the standby RSP with current
frequency syncronization status. This
The Sync Controller check-point data is not failure could be because of memory
initialized.
allocation failure.

[chars]

Checkpointing is a mechanism to update

the redundant RSP with the current
configuration and status of the system to
help takeover in case of a failover. The
checkpoint mechanism needs to be
initialized for Sync-controller to update the
standby RSP with current frequency
syncronization status. This failure could be
because of memory allocation failure.

[chars]

Sync-controller is the software component

which controls the synchronization devices
in the system. Checkpointing is a
mechanism to update the redundant RSP
with the current configuration and status of
the system to help takeover in case of a
failover. The checkpoint mechanism needs
to be initialized for Sync-controller to
update the standby RSP with current
frequency syncronization status. This
failure could be because of memory
allocation failure.

Due to limitations in ASR9000 RSP

frequency synchronization hardware,
certain combinations of clock-interface
config are not supported. If one clockinterface (sync 0 or sync 1) is configured in
any of these modes: clock-mode bits-input
t1 clock-mode bits-output t1 clock-mode
bits-output 6m-output-only then the
following configurations for the other clockinterface are prohibited: clock-mode bitsinput e1 clock-mode bits-input 2m clockmode bits-output e1 clock-mode bitsoutput 2m Note that 'clock-mode uti' is
The configuration for two synchronization compatible with all other modes; that is, if
ports, [chars] and [chars], is incompatible one clock-interface is configured 'clockwith the hardware. When sync port
mode uti' then the other clock-interface
#[unsigned int] is in [chars] mode,
can have any clock-mode ... including 'uti'.
hardware will not support port #[unsigned Likewise, 'clock-mode bits-input 64k-inputint] in [chars] mode.
only' is compatible with all other modes.

Due to limitations in ASR9000 RSP

frequency synchronization hardware,
certain combinations of clock-interface
config are not supported. If one clockinterface (sync 0 or sync 1) is configured in
any of these modes: clock-mode bits-input
t1 clock-mode bits-output t1 clock-mode
bits-output 6m-output-only then the
following configurations for the other clockinterface are prohibited: clock-mode bitsinput e1 clock-mode bits-input 2m clockmode bits-output e1 clock-mode bitsoutput 2m Note that 'clock-mode dti' is
The configuration for two synchronization compatible with all other modes; that is, if
ports, [chars] and [chars], is incompatible one clock-interface is configured 'clockwith the hardware. When sync port
mode dti' then the other clock-interface
#[unsigned int] is in [chars] mode,
can have any clock-mode ... including 'dti'.
hardware will not support port #[unsigned Likewise, 'clock-mode bits-input 64k-inputint] in [chars] mode.
only' is compatible with all other modes.
The synchronization ports 0/1 do not
The configuration for the synchronization
support gps-tod-input. Likewise the
port #[unsigned int] in [chars] mode is not synchronization port 2 does not support
supported in hardware.
bits-input, bits-output and DTI modes.

Connection to [chars] failed. Error: [chars]

Connection to a shared database sotware

component failed. This could be an
intermittent issue. This can be ignored
unless this message is seen frequently.

Connection to [chars] failed. Error: [chars]

Connection to a shared database sotware

component failed. This could be an
intermittent issue. This can be ignored
unless this message is seen frequently.

SyncAgent Server function not

implemented: [chars]()

Somebody called a SyncAgent API function

that has yet to be implemented.

[chars] [chars]

Checkpointing is a mechanism to update

the redundant RSP with the current
configuration and status of the system to
help takeover in case of a failover. The
checkpoint mechanism needs to be
initialized for Sync-controller to update the
standby RSP with current frequency
syncronization status.

[chars] [chars]

Checkpointing is a mechanism to update

the redundant RSP with the current
configuration and status of the system to
help takeover in case of a failover. The
checkpoint mechanism needs to be
initialized for Sync-controller to update the
standby RSP with current frequency
syncronization status.

Quality ITU-T Option does not support

current framing mode. Option 1 should use
SDH, Option 2 for SONET: Alarm [chars],
Current mode is [chars]. Transmitting
[chars] from controller interface instance
Quality ITU-T Option 1 does not support
[chars]
SONET framing, only SDH framing.
SyncAgent Client API version mismatch
detected by process [dec]: Expected
[chars]([unsigned int]=[hex]), received
[unsigned int]=[hex].

SyncAgent has detected incompatible

versions between its Client API and the
currently-running server.

SyncAgent [chars] failed to [chars] during

initialization: [chars]

An error was encountered while the

specified process was initializing. The error
message contains details about the source
of the error. Frequency synchronization on
this line card is disabled.

When no external clock source is available,

this status propagates to BITS output ports
[chars]: Disabling [chars] output on clock- in 2MHz and 6.312MHz modes. When an
interface sync 0 location [chars] due to loss external source is qualified, this alarm will
of external synchronization signal.
be cleared.
When no external clock source is available,
this status propagates to BITS output ports
[chars]: Sending [chars] AIS on clockin T1 and E1 modes. When an external
interface sync 0 location [chars] due to loss source is qualified, this alarm will be
of external synchronization signal.
cleared.

[chars]: [chars] Transmitter disabled on

clock-interface sync 0 location [chars]
standby RSP.

On the standby RSP, BITS outputs are

disabled. This prevents the sync 0
transmitters on RSP0 and RSP1 from
interfering with one another when a Y-cable
is installed.

When no external clock source is available,

this status propagates to BITS output ports
[chars]: Disabling [chars] output on clock- in 2MHz and 6.312MHz modes. When an
interface sync 1 location [chars] due to loss external source is qualified, this alarm will
of external synchronization signal.
be cleared.
When no external clock source is available,
this status propagates to BITS output ports
[chars]: Sending [chars] AIS on clockin T1 and E1 modes. When an external
interface sync 1 location [chars] due to loss source is qualified, this alarm will be
of external synchronization signal.
cleared.

[chars]: [chars] Transmitter disabled on

clock-interface sync 1 location [chars]
standby RSP.

On the standby RSP, BITS outputs are

disabled. This prevents the sync 1
transmitters on RSP0 and RSP1 from
interfering with one another when a Y-cable
is installed.

When no external clock source is available,

this status propagates to BITS output ports
[chars]: Disabling [chars] output on clock- in 2MHz and 6.312MHz modes. When an
interface sync 0 location [chars] due to loss external source is qualified, this alarm will
of external synchronization signal.
be cleared.
When no external clock source is available,
this status propagates to BITS output ports
[chars]: Sending [chars] AIS on clockin T1 and E1 modes. When an external
interface sync 0 location [chars] due to loss source is qualified, this alarm will be
of external synchronization signal.
cleared.

[chars]: [chars] Transmitter disabled on

clock-interface sync 0 location [chars]
standby RSP.

On the standby RSP, BITS outputs are

disabled. This prevents the sync 0
transmitters on RSP0 and RSP1 from
interfering with one another when a Y-cable
is installed.

When no external clock source is available,

this status propagates to BITS output ports
[chars]: Disabling [chars] output on clock- in 2MHz and 6.312MHz modes. When an
interface sync 1 location [chars] due to loss external source is qualified, this alarm will
of external synchronization signal.
be cleared.
When no external clock source is available,
this status propagates to BITS output ports
[chars]: Sending [chars] AIS on clockin T1 and E1 modes. When an external
interface sync 1 location [chars] due to loss source is qualified, this alarm will be
of external synchronization signal.
cleared.

[chars]: [chars] Transmitter disabled on

clock-interface sync 1 location [chars]
standby RSP.

On the standby RSP, BITS outputs are

disabled. This prevents the sync 1
transmitters on RSP0 and RSP1 from
interfering with one another when a Y-cable
is installed.

SyncAgent [chars] [chars] during

initialization: [chars]

This message is informational; it doesn't

indicate a failure, only that some out-ofthe-ordinary event has been encountered.
The message contains details about the
source of the event. Frequency
synchronization functionality will not be
impacted by this event; however, history
('show sync-agent ...') and/or debugging
support may be unavailable.

This line card does not have hardware

Frequency Synchronization is not supported support for Synchronous Ethernet
on this line card.
operation.
Frequency Synchronization feature does
not recognize hardware board type [hex]

This line card does is not known to work

with the frequency synchronizatoin feature.

Failed to initialize the shared memory for

[chars]: shmwin_init() failed shmwinid [dec] NH.

hal_shm_alloc: shmwin_malloc() failed

shmwinid [dec]

Failed to allocate the shared memory for

NH.

[chars]: shmwin_pool_create_v2() failed,

return: cerr: [dec]

Failed to create the memory pool for

shared memory.

G_PLIM_QOS SysDB Error. Reason: [chars]

%s - Sysdb error message

G_PLIM_QOS IM controller creation error.

Reason: [chars]

%s - IM controller creation error message

GE_DMAC MLAN link interface ([dec]) is

down

The internal link interface for the specified

port is down.

[chars], error code [chars]\n

A runtime failure occurred in GE-DMAC

process. Typically, this is an internal error.
The message string indicates the reason
for the failure. This message also provides
an error code and a string interpretation of
the error code.

[chars], error code [chars]\n

A runtime failure occurred in GE-DMAC

process. Typically, this is an internal error.
The message string indicates the reason
for the failure. This message also provides
an error code and a string interpretation of
the error code.

Interface [dec] ([chars]) is [chars]

A link in the RSP control plane MAC has

change state.

Interface [dec] ([chars]) is [chars]

A link in the RSP control plane MAC has

change state.

'bind: error gsp_debug_em_init failed:

[dec]'

Debug initialization failed within EM.

Debugs may not be printed

GSP fabric media is disabled in this mode

'GSP:fabric media is disabled in this mode' and Ethernet media is enabled.

An packet corruption occurred during

transport of aipc packets. This DLL controls
transport of aipc packets over the fabric on
crc error on rx, dropping aipc packet : drop c1200 platform. %d - indicates number of
count = [dec]
packets dropped so far.

[chars], error [dec] ([chars])

Failed to perform the action specified in the

error message.

[chars], error [chars]

This is an error message in the c12000

platform specific code software to indicate
anomolies that are not FATAL. This error is
most likely caused by a temporary
situation, so is unlikely to re-occur. %s indicates the reason for the failure. %s - is
the decoded error reason.

[chars], error [chars]

This is an error message in the c12000

platform specific code software to indicate
anomolies that are not FATAL. This error is
most likely caused by a temporary
situation, so is unlikely to re-occur. %s indicates the reason for the failure. %s - is
the decoded error reason.

shared memory free error [chars]

This error occurs because we are not able

to free the shared memory.

shared memory allocation error [chars]

This error occurs because we are not able

to allocate the shared memory.

Cannot get platform specific info for shared This error occurs because we are not able
mem [dec]: [chars]\n
to get the platform specific info.

System run out of [chars], no pages left

A error occurred in GSR external memory

manager resulting in a failure to provide
some system service as indicated in the
message text.

A error condition occured during init of the

LC external memory manager. Connection
to sysdb from LC external memory
manager failed. The LC external memory
manager could not complete proper
exmem: error encountered, reason=[chars] operation.

exmem: fatal error encountered,

reason=[chars]

A fatal error condition is encountered in LC

external memory manager. The LC external
memory manager could not complete
proper operation.

Unable to get thread priority [chars], Will

result in longer boot time\n

This error occurs because we are not able

to get thread priority.

Unable to lower thread priority [chars], Will This error occurs because we are not able
result in longer boot time\n
to get thread priority.

[chars]

This is an informational message from

SRAM external memory when it's utilization
has reached 95%.

LC Reset: Reason - [chars]

Platform manager client API received an

error from one of the linecard software
driver processes that crashed due to a
software problem and the LC must be
reloaded. The platform-mgr process
controls linecard resets for the software
driver processes. If a linecard software
driver crashes due to a software problem, it
can get into a very bad and may be
unrecoverable. This action is taken to
reload the linecard immediately. %s Contains the process and reason for the
linecard reload.

LC Reset: Reason - [chars]

Platform manager Error Handling received

an error from one of the LC devices. The LC
MUST be reset.

Process connection failed: ([chars]%s)

The linecard platform-mgr process failed to

connect its process to the route processor
processes during process initialization. The
platform-mgr process runs on the linecard
and handles interface information between
the route processor and the linecard
hardware drivers. It also stores all local
linecard information for every interface
configured on the linecard. If the platformmgr fails to connect, no linecard interfaces
can be created or deleted. The platformmgr show commands will also not be
available. %s - indicates the reason for the
failure. %s - is the decoded error reason.

gsr_lc_pm: [chars] [hex]

gsr_lc_pm encountered an error and is not

able to recover from the error. A reason
text will be supplied. call support with this
text.

GSR_LC_PM: Fatal Error, reason = [chars]

Platform manager encountered a fatal error

and is not able recover from the error. A
reason text will be supplied call support
with this text.

gsr_lc_pm: fatal error encountered,

reason=[chars], errno=[dec]

gsr_lc_pm encountered a fatal error and is

not able to recover from the error. A reason
text will be supplied call support with this
text. An integer errno will also be printed.

[chars]: imc_control_server_bind failed,rc:

[chars]

Interface manager client control server

binding failed

Process initialization failed: ([chars]%s)

The linecard platform-mgr process failed to

initialize. The platform-mgr process runs on
the linecard and handles interface
information between the route processor
and the linecard hardware drivers. It also
stores all local linecard information for
every interface configured on the linecard.
If the platform-mgr fails to initialize, no
linecard interfaces can be created or
deleted. %s - indicates the reason for the
failure. %s - is the decoded error reason.

[chars]: found [hex] instead of

PSARB_COMM_MAGIC ([hex])

This error indicates that the value found is

not the magic value.

Event manager failure: ([chars]%s)

An error occurred in the system data-base

(SysDB) event manager GSR platform
library DLL. This DLL controls thread
creation, deletion and connections between
all other processes and DLL's. If there is a
failure in this DLL, a connection will be lost
somewhere on the system and failures will
occur. %s - indicates the reason for the
failure. %s - is the decoded error reason.

[chars] ([chars])

For displaying error conditions with

traceback and an error string.

[chars]: fopen of [chars] failed err=[dec]\n Failed to open the file.

[chars]: fread from [chars] failed

err=[dec]\n

Failed to read the file.

[chars]: fstat [dec] failed err=[dec]

Failed to get the stat of the file descriptor.

get_partner failed [dec]

Failed to get the active and standby info.

Logical router failure: ([chars]%s)

An error occurred during a card state

change. This DLL controls the node
information during a card state change for
logical routers. If there is a failure here, the
logical router will lose its nodeid
information and will get out of sync with
the system. %s - indicates the reason for
the failure. %s - is the decoded error
reason.

[chars]: mmap [chars] failed err=[dec]

Failed to memory map.

[chars]: mmap to Interrupt Mask Register

failed err=[dec]\n

Failed to memroy the interuppt mask

register.

[chars](): error, Inconsitent content of

psarb shared memory primery rp=[dec]
standby rp=[dec] partner slot of
primary=[dec] partner slot of
standby=[dec]

This error indicates that the shared

memory contains inconsistent data.

[chars]: shm_open [chars] failed err=[dec] Failed to open the shared memory area.

create thread for mgmt interface disable

failed. [chars]

Failed to create the thread.

failed to detach mgmt disabling thread.

[chars]

Failed to detach the thread.

failed to unmount [chars]/[chars]

This error indicates that there is an error in

unmounting the device.

Failed fm_add_feature [dec] ifh [hex] rc:

[dec], [chars]

Failed to add the feature.

[chars], error [chars]

Failed to perform the action specified in the

error message.

Critical severity error: Device: [chars]

PRP Platform Manager process received a

critical severity hardware error from one of
the PRP hardware devices. In the case of
the ASIC drivers, PRP-PM receives error
reports from the drivers and takes action
based on its knowledge of the required
ASIC reset sequence. If error reports
exceed a threshold then a PRP fail-over is
initiated by PRP-PM. A traffic loss on the
PRP will occur and an PRP failover may
occur to recover. %s - is the Device of the
fault being addressed.

High severity error: Device: [chars]

PRP Platform Manager process received a

high severity hardware error from one of
the PRP hardware devices. In the case of
the ASIC drivers, PRP-PM receives error
reports from the drivers and takes action
based on its knowledge of the required
ASIC reset sequence. If error reports
exceed a threshold then a PRP fail-over is
initiated by PRP-PM. A slight traffic loss on
the PRP will occur. %s - is the Device of the
fault being addressed.

Process initialization failed: ([chars]%s)

The PRP platform-mgr process failed to

initialize. The PRP Platform Manager
process provides fault management
services for ASIC drivers and PRP fail-over
initiation for Fabric Control (FCTL) If the
platform-mgr fails to initialize, the system
will be unable to recover due to an asic
fault or PRP failover. %s - indicates the
reason for the failure. %s - is the decoded
error reason.

Low severity error: Device: [chars]

PRP Platform Manager process received a

low severity hardware error from one of the
PRP hardware devices. In the case of the
ASIC drivers, PRP-PM receives error reports
from the drivers and takes action based on
its knowledge of the required ASIC reset
sequence. %s - is the Device of the fault
being addressed.

Detected i2c bus hang with Backplane

EEPROM\n

As shown in the message.

[chars]

Error detected when starting the i2c driver

Detected i2c bus hang with lower fantray\n As shown in the message.

Detected i2c bus hang with onboard

device\n

As shown in the message.

Detected old PLD version = [hex] on this

board. Please upgrade the PLD to atleast
[hex], and check for i2c rework\n

Detected that the board has old PLD

version. Because of this, we will not be able
to detect or correct an i2c bus hang.

Detected i2c bus hang from which sw is

unable to recover.\n

As shown in the message.

Detected i2c bus hang with upper fantray\n As shown in the message.

Detected i2c bus hang, attempting to

unhang the bus......\n

Detected i2c bus hang.

Successfully unhung the i2c bus\n

As shown in the message.

[chars] [dec]

An internal error occurred in FIB engine

layer for collecting traces. The message
string indicates the reason for the failure.
This message also provides an error code.
Additionally, it provides a more verbose
information of the error.

Users initiated a heartbeat loss

User ran a heartbeat test utility to create

heartbeat loss.

Fatal error occurred. HB agent [chars].

Process is exiting. Errinfo:[chars]

This message indicates that HBA agent

encountered Fatal internal error. Embedded
String will provide details of error
encountered.

This error means that hbagent was not able

WARNING! The hbagent process failed to
to notify mbi-hello that mbi-hello on this
notify the mbi-hello process. rc [dec], errno node should now terminate. Please collect
[dec]
console logging.

HB agent was unable to [chars]. ErrInfo:

[chars]

An infrastructure component has returned

an error to the MBI infrastructure, so it may
not be able to continue with the current
operation.

This may be a problem with lack of

resources. The MBI infrastructure will be
unable to carry out all of its expected
Failed to create a thread for [chars]: [chars] functionality.

Failed to attach a reconnect handler to

ethernet server coid. If ethernet server
restarts, heartbeat agent may not be able
to receive/write messages [chars]

Failed to attach a reconnect handler to

ethernet server coid. If ethernet server
restarts, heartbeat agent may not be able
to receive/write messages.

The process will continue with it's business,

however, cause of why hbagent was not
able to initialize tracing should be tracked
Failed to initialize hbagent tracing: ([dec] : down. As result of this error, hbagent will
[chars])
not have any tracings.
Unable to set the heartbeat pulse of this
node to high priority. Proceeding with
default priority, however in a high CPU
Unable to set the heartbeat pulse through consumption, this node's heartbeat pulse
ethernet server to high priority. Proceeding may get lost, causing this node to get
with normal priority: [chars]
reloaded.

Unable to set the thread priority to high.

Proceeding with normal priority: [chars]

Unable to set the heartbeat pulse of this

node to high priority. Proceeding with
default priority, however in a high CPU
consumption, this node's heartbeat pulse
may get lost, causing this node to get
reloaded.

Reload notification received. Reloading in

[dec] secs

Message indicating that the node has

received a reload notification and the node
is going to reload soon.

There is already an instance of heatbeat

loss log collection in progress. Ignoring
current heatbeat loss log collection
request.

The current request to collect heatbeat loss

log is being ignored because of another
instance of heatbeat loss log collection that
is still in progress.

The node received a test reload notification

just to check functionality. The notification
Received a test reload notification, ignore. is ignored.

Hard disk device error

Hard disk encountered media errors

Hard disk restarted

HFR IP-EA: Critical error: [chars]
HFR IP-EA: Error: [chars] [dec]
HFR IP-EA: Error: [chars]
HFR IP-EA: Debug info: [chars]
HFR IP-EA: Critical error: [chars]
HFR IP-EA: Error: [chars] [dec]
HFR IP-EA: Error: [chars]
HFR IP-EA: Debug info: [chars]

Hard disk restart is taking excess time.

HFR IP-EA, Critical error
HFR IP-EA, error
HFR IP-EA, error
HFR IP-EA, Debug information
HFR IP-EA, Critical error
HFR IP-EA, error
HFR IP-EA, error
HFR IP-EA, Debug information

HFR_L2FIB_METRO_SHOW: [chars] ,Err_Str: HFR_L2FIB_METRO_SHOW has encountered

[chars]
an init or a sysdb error.

Invalid option passed to

hfr_l2fib_metro_show command: [chars]

Startup option supplied to l2fib metro show

command is not valid.

HFR_PM_SHOW: [chars] , [chars]

HFR_PM_SHOW encountered an error

hfr_pm_show: invalid option passed to

hfr_pm_show command. [chars]
PLATFORM MPLS-EA: [chars]

Startup option supplied to HFR_PM_SHOW

is not valid.
CRS MPLS-EA, error

PLATFORM MPLS-EA: [chars] Error: [chars]

([dec])
PLATFORM MPLS-EA: [chars]: [chars]

CRS MPLS-EA, error

CRS MPLS-EA, Debug information

Platform Manager Info: [chars]

The Platform Manager info for some action

taken.

HFR_PM_SHOW: [chars] , [chars]

HFR_PM_SHOW encountered an error

hfr_pm_show: invalid option passed to

hfr_pm_show command. [chars]

Startup option supplied to HFR_PM_SHOW

is not valid.

hfr_pm_test: fatal error encountered,

reason=[chars]

hfr_pm test encountered a fatal error and is

not able recover from the error. A reason
text will be supplied call support with this
text.

hfr_pm_test: fatal error encountered,

reason=[chars], errno=[dec]

hfr_pm_test encountered a fatal error and

is not able to recover from the error. A
reason text will be supplied call support
with this text. An integer errno will also be
printed.

[chars], svr_ctx=0x[pointer],
expected_ctx=0x[pointer]

The Platform Manager detected a software

error where the received library server
context does not match the expected
value.

The specified device has a fault that affects

the card functionality. The card node will be
reset and ideally or waiting to be debugged
if the card node is in NMON mode. When
Device [chars] #[dec] has a fault=[chars]. action is reset, the problem will not happen
action: [chars]
again when it comes back up.

hfr_pm encountered a fatal error and is not

able to recover from the error. A text
hfr_pm: error encountered, reason=[chars], reason and error number will be supplied to
errno=[dec]
describe the error.

Platform Manager encountered an

initialization error A reason text will be
hfr_pm: error encountered, reason=[chars] supplied to describe the error.

fatal memory allocation error for <[dec]>

bytes

Platform Manager encountered a fatal

memory allocation error

If configuring policing granularity via CLI,

note that it is effective \ only for the future
service-policy configurations. In order for
qos \ granularity to take effect, reapply the
service-policy to the interfaces \ requiring The LC needs to be reloaded, or the policy
granularity change or reload the line-card has to be reapplied for the configured qos
[chars]
police granularity to be effective.
WARNING: PLEASE RELOAD THE NODE
[chars], FOR GRANULARITY TO TAKE
EFFECT

The LC needs to be reloaded for the

configured qos shaping granularity to be
applied.

Platform Manager warning: [chars]

The Platform Manager encountered an

provisioning warning.

Platform Manager warning: [chars]

The Platform Manager encountered an

internal software warning. The software will
reattempt to fix the cause of this warning.

Platform Manager error, reason=[chars],

errno=[dec]

The Platform Manager encountered an

internal software error.

Platform Manager error, reason=[chars]

The Platform Manager encountered an

internal software initialization error.

[chars]: [chars]

HFR SPP Initialization Error message.

Error Allocating <[dec]> bytes of memory

HFR SPP Memory Allocation Error message.

[chars]: client_id = [dec], client_name =

[chars], index = [dec], elsize = [dec]

HFR SPP Invalid Queue Element Size Error

message.

[chars]: [chars]

HFR SPP Thread Error message.

[chars], error [chars]

This is an error message in the CRS

platform specific code software to indicate
anomolies that are not FATAL. This error is
most likely caused by a temporary
situation, so is unlikely to re-occur. %s indicates the reason for the failure. %s - is
the decoded error reason.

[chars], param1 = [unsigned int], param2

= [unsigned int]

This is an error message in the CRS

platform specific code software to indicate
some problem with the code. %s - indicates
the reason for the failure.

[chars]

This is an error message in the CRS

platform specific code software to indicate
some problem with the code. %s - indicates
the reason for the failure.

[chars] ([hex])

This is an error message in the CRS

platform specific code software to indicate
some problem with the code. %s - indicates
the reason for the failure.

[chars] ([hex]) [chars] ([hex])

This is an error message in the CRS

platform specific code software to indicate
some problem with the code. %s - indicates
the reason for the failure.

[chars] - [dec]: [chars]

Error in HORSE operation.

[chars] - [dec]: [chars] (rc = [hex])

Error in HORSE operation.

TX PDMA Ring Stalled, queue = [[chars]],

cur_ind = [dec], tx_ind = [dec].

CPUCTRL TX PDMA ring remained full over

non-transient period. Packets which could
not be sent were discarded. The
downstream ASIC may be stalled. Asic error
logged with queue details.

TX PDMA Ring Stalled, queue = [[chars]],

cur_ind = [dec], tx_ind = [dec].

CPUCTRL TX PDMA ring remained full over

non-transient period. Packets which could
not be sent were discarded. The
downstream ASIC may be stalled. Asic error
logged with queue details.

PIO access to [hex] with width [dec]B.

PIO access to address with an different

access width. It is possible to cause access
failure.

RX PDMA Ring out of buf, queue =

[[chars]], cur_ind = [dec], tx_ind = [dec],
retry [dec]

CPUCTRL RX PDMA ring could not replace

the buffers. possible low buffer condition.

RX PDMA Ring out of buf, queue =

[[chars]], cur_ind = [dec], tx_ind = [dec],
retry [dec]

CPUCTRL RX PDMA ring could not replace

the buffers. possible low buffer condition.

The reason of Failure: [chars] . Value

Associated with the Failure =[dec]

A driver internal failure occurred which

involves exiting the process.

Info: [chars] [hex]

This is a Informational message in the

QFPCPUBridge driver %s - indicates the
informational message. %d - indicates any
additiona data.

Unable to recover the I2C bus

The attempted I2C bus hang recovery was

not successful.

Unable to recover the I2C bus

The attempted I2C bus hang recovery was

not successful.

Successfully recovered the i2c bus

The I2C bus hang has been cleared

successfully. I2C communication is restored
on the bus.

Successfully recovered the i2c bus

The I2C bus hang has been cleared

successfully. I2C communication is restored
on the bus.

SCL hang detected on I2C bus (ctrl-reg

[hex]). Attempting recovery

An I2C bus hang has been detected.

Recovery is automatically attempted.
Should the recovery be successful, a
BUS_UNHANG_SUCCESS message is issued;
otherwise, an UNRECOVERABLE_BUS_HANG
is issued.

SCL hang detected on I2C bus (ctrl-reg

[hex]). Attempting recovery

An I2C bus hang has been detected.

Recovery is automatically attempted.
Should the recovery be successful, a
BUS_UNHANG_SUCCESS message is issued;
otherwise, an UNRECOVERABLE_BUS_HANG
is issued.

An I2C bus hang has been detected.

Recovery is automatically attempted.
Should the recovery be successful, a
BUS_UNHANG_SUCCESS message is issued;
SDA hang detected on I2C bus (read [hex], otherwise, an UNRECOVERABLE_BUS_HANG
expected [hex]). Attempting recovery
is issued.

An I2C bus hang has been detected.

Recovery is automatically attempted.
Should the recovery be successful, a
BUS_UNHANG_SUCCESS message is issued;
SDA hang detected on I2C bus (read [hex], otherwise, an UNRECOVERABLE_BUS_HANG
expected [hex]). Attempting recovery
is issued.

Lock Unavailable. Possible Reason: Other

RP trying to boot up in Normal mode.

Failed to grab lock in DR mode as the lock

is unavailable. Possible reason: Other RP
booted up in Normal mode and
permanantly grabbed the lock.

Lock Unavailable. Possible Reason: Other

RP trying to boot up in Normal mode.

Failed to grab lock in DR mode as the lock

is unavailable. Possible reason: Other RP
booted up in Normal mode and
permanantly grabbed the lock.

ASICS PLL LOCK failed [hex]

This message indicates that ASICS(except

beluga) PLL LOCK failed.

ASICS (except beluga) not out of reset

[hex]

ASICS not out of reset.

crs-x fabric card (board-type = [hex])

power good register bits are low,
power_up_status value = [hex] \n

As soon as power is asserted on fabric

card, s/w will read power good reister for
crs-x fabric cards. If power good register
bits are low, it indicates that the crs-x
fabric card is not having a good power .

Powering up MSC-400G line card failed!

MSC-400G board power up failed.

LC power not ready. power status [hex] ctrl

register [hex]
LC power not ready.

Card stays in power disabled state, cannot

be recovered even after LC turn OFF, power
control register value = [hex], overtemp
register value = [hex]
Card stays in power disabled state

Board cannot be recovered from power

disabled state, powering down the board
since the power ON failed

Board powering down due to power

disabled state

Warning: PLIM power up has been

bypassed

PLIM bypass jumper is installed on the

MSC. PLIM power up will be bypassed, only
MSC will be powered up.

PLIM DCEN jumper installed. PLIM will

Warning: PLIM power is enabled externally power up, but will not be fully operational.

Invalid PLIM present. ctrl register [hex]

This message indicates that this is invalid

PLIM and this PLIM is not suitable with
present MSC.

PLIM NOT present detected ctrl register

[hex]

PLIM is not detected by lc fpga.

PLIM did not complte initialization [hex]

PLIM is not ready.

POGO tcams not out of reset [hex]

POGO tcams not out of reset

The i2c server proxy process ECM failed

i2c proxy process ECM function [chars] call due to the reason mentioned in the
failed err_str [chars]\n
message.

Superstar fabric card (board-type = [hex])

power good register bits are low,
power_up_status value = [hex] \n

As soon as power is asserted on S2 card,

s/w will read power good reister for
superstar fabric cards. If power good
register bits are low, it indicates that the
superstar fabric card is not having a good
power and the i2c power ON is possibly
failed.

Voltage sensor [chars] contains value [dec]

which is out side of +-10% valid range.
If voltage validation failed, the card will be
Card will be shutdown!
power down by Shelfmgr.

Voltages on this board are not within valid

ranges, shutdown requested.

Voltage validation failed and the client is

requesting us to shutdown the card.

Voltage [chars] = [dec] not within

thresholds\n

As soon as power is asserted on S2 cards,

s/w will read voltage sensors on the host
board. If for any reason reading voltages
failed or voltage read are not within +-10%
range, then this message will be displayed.
It will also list which device and value read.

Error while setting PLD resgister to

enable/disable access to backplane: unable Error while trying to grab or release the
to [chars] mastership
lock.

I2C operation failed because the EMPTY bit

is still set after multiple retries. I2C server
I2C server process restarting due to
process will automatically restart to recover
unrecoverable EMPTY Bit Not Cleared errors from this error condition.

The i2c server process cannot continue due

to error condition mentioned in the
i2c server process exiting, reason: [chars]\n message.

LC power-up failed because - [chars] on

[chars] is bad - as indicated by power good
registers: Register [chars] ([hex]): Value
This message indicates that LC power-up
[hex]\n
failed.

LC power-up failed because - [chars] - as

indicated by power status registers:
Register [chars] ([hex]): Value [hex]\n

This error message indicates that there is a

failure to power up LC card.

Disabling I2C mux in preparation for card

reload failed\n

This error message indicates the i2c mux is

not disabled properly before card reload.

Shutting down card for reload.

I2C Server has parked the I2C bus since the

card is going down for reload. For LC, the
LC will be shutdown as well.

Line card FPGA software revision [hex] does The line card FPGA is reporting a different
not match XR FPGA driver version [hex]
software revision.
Voltages on [chars] are within valid ranges voltage validation succeeded
[chars]
None
Board not powered up (DC_DC_en not
asserted) after max timeout of [dec]
seconds

None

Board not powered up (DC_DC_en not

asserted) after [dec] seconds, resending
pulse to shelfmgr to powerup this board

None

Putting the I2C mux in default state in

preparation for card reload: [chars]

This debug message indicates the start/end

of I2C bus parking. Since shelfmgr powercycles this card immediately after this
parking, this message might not show up
on the RP console. But if there is any delay
during msg_chan_connect or I2C bus park
steps, then this message will help to
findout which step caused the delay.

This debug message indicates the start/end

of SPC power down. Since shelfmgr powercycles this card immediately after this
parking, this message might not show up
on the RP console. But if there is any delay
during msg_chan_connect or power down
Powering down the SPC to handle reload of steps, then this message will help to
the card: [chars]
findout which step caused the delay.
Unable to check LC power status registers
because [chars]\n

None

Plim is not powered up. PLIM_VDD [hex]

None

Failed to send pulse because [chars] failed None

Failed to send a pulse to [chars]: [chars]

The IPC message from i2c server to

shelfmgr failed due to the reason listed in
the msg.

I/O Communications Failure with Device

[chars]

I/O Communications Failure with a Device

on the I2C Bus

Bus Mastership Denied for Device [chars]

SMBus Mastership Denied by Bus-Master

Mux

Bus Stuck Low for Device [chars]

A Device on the I2C bus is stuck, holding

the bus low

An SMBus Transaction Interrupted by

Transaction Interrupted with Device [chars] Another Master

[chars]

The CAI C2C I-lite library encountered an

error related to memory or data value.

Invalid slot type in [chars],slot type=[dec],

slotnum=[dec] \n
Invalid Slot Type.
failed in [chars], return code=[hex]
[chars]\n
[chars] \n

The particular operation mentioned in the

message failed due to some reason.
For notification purpose only.

Ingress MUX FPGA encountered

uncorrectable error. Reloading LC to
recover

Ingress MUX FPGA encountered

uncorrectable error. Reloading LC to
recover

Loss of sync on NPU-IMUX interface

Ingress MUX FPGA encountered Loss of

sync on interlaken interface.

Ingress MUX encountered Rx burst short or Ingress MUX encountered Rx burst short or
burst length error.
burst length error.

Ingress MUX FPGA encountered interlaken

Rx burst max exceeded error.

Ingress MUX FPGA encountered interlaken

Rx burst max exceeded error.

Ingress MUX FPGA encountered interlaken

Rx missing EOP error.

Ingress MUX FPGA encountered interlaken

Rx missing EOP error.

Ingress MUX encountered Rx interlaken

core error.

Ingress MUX encountered Rx interlaken

core error.

Ingress MUX encountered Rx serdes lane

metaframe length error

Ingress MUX encountered Rx serdes lane

metaframe length error.

Ingress MUX encountered Rx serdes lane

metaframe repeat error.

Ingress MUX encountered Rx serdes lane

metaframe repeat error.

Ingress MUX encountered Rx serdes lane

metaframe sync error.

Ingress MUX encountered Rx serdes lane

metaframe sync error.

Ingress MUX FPGA encountered interlaken

Rx serdes lane metaframe type error.

Ingress MUX FPGA encountered interlaken

Rx serdes lane metaframe type error.

Ingress MUX FPGA encountered interlaken

fifo overflow error.

Ingress MUX FPGA encountered interlaken

fifo overflow error.

Ingress MUX FPGA encountered interlaken

Rx missing SOP error.

Ingress MUX FPGA encountered interlaken

Rx missing SOP error.

Ingress MUX FPGA encountered FIA00

channel FIFO multi-bit ECC error

Ingress MUX FPGA encountered FIA00

channel FIFO multi-bit error.

Ingress MUX FPGA encountered FIA01

channel FIFO multi-bit ECC error

Ingress MUX FPGA encountered FIA01

channel FIFO multi-bit error.

Ingress MUX FPGA encountered FIA10

channel FIFO multi-bit ECC error

Ingress MUX FPGA encountered FIA10

channel FIFO multi-bit error.

Ingress MUX FPGA encountered FIA11

channel FIFO multi-bit ECC error

Ingress MUX FPGA encountered FIA11

channel FIFO multi-bit error.

Ingress MUX FPGA encountered FIA00

channel FIFO overflow error

Ingress MUX FPGA encountered FIA00

channel FIFO overflow error.

Ingress MUX FPGA encountered FIA01

channel FIFO overflow error

Ingress MUX FPGA encountered FIA01

channel FIFO overflow error.

Ingress MUX FPGA encountered FIA10

channel FIFO overflow error

Ingress MUX FPGA encountered FIA10

channel FIFO overflow error.

Ingress MUX FPGA encountered FIA11

channel FIFO overflow error

Ingress MUX FPGA encountered FIA11

channel FIFO overflow error.

Ingress MUX FPGA encountered FIA00

channel FIFO single bit ECC error

Ingress MUX FPGA encountered FIA00

channel FIFO single bit error.

Ingress MUX FPGA encountered FIA01

channel FIFO single bit ECC error

Ingress MUX FPGA encountered FIA01

channel FIFO single bit error.

Ingress MUX FPGA encountered FIA10

channel FIFO single bit ECC error

Ingress MUX FPGA encountered FIA10

channel FIFO single bit error.

Ingress MUX FPGA encountered FIA11

channel FIFO single bit ECC error

Ingress MUX FPGA encountered FIA11

channel FIFO single bit error.

Ingress MUX FPGA encountered critical

correctable error.

Ingress MUX FPGA encountered critical

correctable error.

Over Temperature error

Ingress MUX encountered over-temperature

error.

Ingress MUX FPGA encountered FIA00 Tx

burst short error

Ingress MUX FPGA encountered FIA00 Tx

burst short error.

Ingress MUX FPGA encountered FIA01 Tx

burst short error

Ingress MUX FPGA encountered FIA01 Tx

burst short error.

Ingress MUX FPGA encountered FIA10 Tx

burst short error

Ingress MUX FPGA encountered FIA10 Tx

burst short error.

Ingress MUX FPGA encountered FIA11 Tx

burst short error

Ingress MUX FPGA encountered FIA11 Tx

burst short error.

Ingress MUX FPGA encountered FIA00 Tx

burst FIFO overflow error

Ingress MUX FPGA encountered FIA00 Tx

burst FIFO overflow error.

Ingress MUX FPGA encountered FIA01 Tx

burst FIFO overflow error

Ingress MUX FPGA encountered FIA01 Tx

burst FIFO overflow error.

Ingress MUX FPGA encountered FIA10 Tx

burst FIFO overflow error

Ingress MUX FPGA encountered FIA10 Tx

burst FIFO overflow error.

Ingress MUX FPGA encountered FIA11 Tx

burst FIFO overflow error

Ingress MUX FPGA encountered FIA11 Tx

burst FIFO overflow error.

Ingress MUX FPGA encountered FIA00 Tx

overflow error

Ingress MUX FPGA encountered FIA00 Tx

overflow error.

Ingress MUX FPGA encountered FIA01 Tx

overflow error

Ingress MUX FPGA encountered FIA01 Tx

overflow error.

Ingress MUX FPGA encountered FIA10 Tx

overflow error

Ingress MUX FPGA encountered FIA10 Tx

overflow error.

Ingress MUX FPGA encountered FIA11 Tx

overflow error

Ingress MUX FPGA encountered FIA11 Tx

overflow error.

Ingress MUX FPGA encountered FIA00 Tx

underflow error

Ingress MUX FPGA encountered FIA00 Tx

underflow error.

Ingress MUX FPGA encountered FIA01 Tx

underflow error

Ingress MUX FPGA encountered FIA01 Tx

underflow error.

Ingress MUX FPGA encountered FIA10 Tx

underflow error

Ingress MUX FPGA encountered FIA10 Tx

underflow error.

Ingress MUX FPGA encountered FIA11 Tx

underflow error

Ingress MUX FPGA encountered FIA11 Tx

underflow error.

Vccint out of range

VCCint out of range

Interrupt controller driver fab arbiter ready Interrupt controller driver detected a fab
error
arbiter ready error (ack not received).

Interrupt controller driver crossbar fabric

arbiter receive parity error

Crossbar fabric arbiter reported to Interrupt

controller that the data it received had
parity error

Interrupt controller driver crossbar fabric

arbiter transmit parity error

Interrupt controller FPGA reported that data

it received from crossbar fabric arbiter had
parity error

Interrupt controller driver Timing and CPI

controller data ack error

Interrupt controller driver detected an data

ack error from Timing and CPI controller
FPGA

Interrupt controller driver Timing and CPI

controller parity error on receive interface

Timing and CPI controller FPGA reported

that the data it received had parity error

Interrupt controller FPGA reported that data

Interrupt controller driver Timing and CPI
it received from Timing and CPI controller
controller parity error on transmit interface FPGA had parity error

Interrupt controller driver cpu address

parity error

Interrupt controller driver detected an

address parity error from the cpu

Interrupt controller driver cpu data parity

error

Interrupt controller driver detected a data

parity error from the cpu

Interrupt controller driver version is not

compatible with the hardware version.
[chars]

Interrupt controller driver version is not

compatible with the hardware version.

Interrupt controller driver crossbar fabric

interface ready error

Interrupt controller driver detected a

crossbar fabric interface ready error (ack
not received).

Crossbar fabric interface reported to

Interrupt controller driver FIA receive parity interrupt controller that the data it received
error
had parity error

Interrupt controller driver crossbar fabric

interface transmit parity error

Interrupt controller FPGA reported that data

it received from crossbar fabric interface
had parity error

Interrupt controller driver detected a PUNT

Interrupt controller driver PUNT ready error ready error (ack not received).

Interrupt controller driver PUNT receive

parity error

PUNT FPGA reported to Interrupt controller

that the data it received had parity error

Interrupt controller driver PUNT transmit

parity error

Interrupt controller FPGA reported that data

it received from crossbar fabric arbiter had
parity error

Interrupt controller driver Thermal Alarm

Interrupt controller driver detected a

thermal error.

Interrupt controller driver Thermal Over

Temperature

Interrupt controller driver detected a

thermal over temperature

Initialization Error: [chars] Reason: [chars]. Interrupt controller Driver encountered a

Exiting.
fatal error and is not able to recover.

[chars]: Ltrace Initialization for [chars]

failed. rc.[chars]\n

Interrupt controller Driver Ltrace

initialization failed.

Error Allocating <[dec]> bytes of memory

Interrupt controller encountered a fatal

memory allocation error

Continuing execution: [chars]: Caused by

[chars]

This message indicates an error occurred

beyond which execution of the Interrupt
controller_driver may continue, attempting
to effect recovery or work-around
internally, minimizing loss of
information/functionality.

Event Manager create failed for [chars].

Reason: [chars]

Interrupt controller Event Manager create

error

Event Manager notify failed for [chars].

Reason: [chars]

Interrupt controller Event Manager notify

error

Exit on error: [chars]: Caused by [chars]

An error occurred in Interrupt controller

Driver which requires exiting (and, hence,
restarting) the process.

LWM Event Manager event block failed.

Reason: [chars]

Interrupt controller Event Manager event

block error

An error occurred during LWM message

reply. Reason: [chars]

Interrupt controller LWM reply error

Inter-rack switch port [dec] state changed

to [chars]

When the process starts, port state

oscillate between up and down and finally
the port state will become up. While
configuring also port link state change
message information displayed. Except the
above two scenarious, if port state change
occurs please contact TAC support.

Inter-rack switch port [dec] state changed

to ADMIN_DOWN

The inter-rack switch port was

administratively shut down.

INTF_EA_SHOW: [chars] , [chars]

INTF_EA_SHOW encountered an error

intf_ea_show: invalid option passed to

intf_ea_show command. [chars]

Startup option supplied to HFR_PM_SHOW

is not valid.

[chars], svr_ctx=0x[pointer],
expected_ctx=0x[pointer]

The Interface EA detected a software error

where the received library server context
does not match the expected value.

intf_ea encountered a fatal error and is not

able to recover from the error. A text
intf_ea: error encountered, reason=[chars], reason and error number will be supplied to
errno=[dec]
describe the error.

Interface EA encountered an initialization

error A reason text will be supplied to
intf_ea: error encountered, reason=[chars] describe the error.
Granularity is effective for future servicepolicy configurations only. \ Please reapply
the service-policy for all the existing
The LC needs to be reloaded, or the policy
interfaces that \ require granularity change has to be reapplied for the configured qos
or reload the line-card [chars]
police granularity to be effective.

WARNING: PLEASE RELOAD THE NODE

[chars], FOR GRANULARITY TO TAKE
EFFECT

The LC needs to be reloaded for the

configured qos shaping granularity to be
applied.

Interface EA warning: [chars]

The Interface EA encountered an

provisioning warning.

Exiting because [chars], error code

[chars]\n

The process exited due to the reason

mentioned in the message.

Failed to [chars], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

SFP or XFP or CFP or QSFP enity is inserted

xFP OIR: [chars]%s/[dec] is inserted, state: into the line card inv_agent collects the
[dec]\n
port data whenever it is presented.
SFP or XFP or CFP or QSFP enity is removed
xFP OIR: [chars]%s/[dec] is removed, state: from the line card inv_agent removes the
[dec]\n
port data ehne

[chars]\n

The particular operation mentioned in the

message occured due to some reason. This
is not a critical failure, the process can
continue functioning as expected despite
the failure.

[chars] Error code [hex] Reason [chars]

This message indicates that there is a

failure in the invmgr process which creates
a thread pool to handle items in the queue.
The failure may be in event
creation/queuing or handling in the thread.

OIR: Card [chars] inserted\n

Entity specified in the messages is inserted

into the chassis and inventory manager is
updated. This message is used by CWI/CTM
to determine when the entity-related
information (read from the EEPROM) is
available in inventory database.

Compact Flash is inserted on Node:

[chars]\n

Compact Flash entity is inserted into the

RSP invmgr_agent collects the CF data
whenever it is inserted.

Compact Flash is removed on Node:

[chars]\n

Compact Flash entity is removed from the

RSP invmgr_agent deletes the CF data
whenever it is removed.

xFP OIR: [chars] port_num: [dec] is

inserted, state: [dec]\n

SFP or XFP or CFP or QSFP entity is inserted

into the line card.

xFP OIR: [chars] port_num: [dec] is

removed, state: [dec]\n

SFP or XFP or CFP or QSFP entity is

removed from the line card.

Node: [chars], state: [chars]

Inventory Manager output this

informational message whenever there is a
card state change. This message will
indicate the current card state.

Node: [chars], state: [chars]

Inventory Manager output this

informational message whenever there is a
card state change. This message will
indicate the current card state.

OIR: Node [chars] inserted\n

Entity specified in the messages is inserted

into the chassis and inventory manager is
updated. This message is used by CWI/CTM
to determine when the entity-related
information (read from the EEPROM) is
available in inventory database.

OIR: Node [chars] removed\n

Entity specified in the messages is

removed from the chassis and inventory
manager is updated.

Optic Interface Module [chars] for [chars]

port [dec] on satellite [dec]

The Optic Interface Module (XFP) for the

specified port has either been inserted or
removed.

[chars]

This message indicates a generic failure in

the invmgr w.r.t the cards in the inventory.
This can be a any failure that occurs
commonly either during bootup or in RUN
state

[chars]

Failure in Inventory Manager resulting in

error condition %s - indicates the reason of
the failure.

[chars], reason: [chars]

Failure in Inventory Manager dllmain

function call %s - indicates the reason of
the failure. reason: %s - is the decoded
error reason.

Unable to register for invmgr edm event

notification

Failure in Inventory Manager event creation

Unable to start invmgr edm communication Failure in Inventory Manager event connect
channel
open

Unable to allocate memory

Failure in Inventory Manager memory

allocation error occurred

Inventory Creation of RACK failed.

The RACK entry is a must in inventory

management

[chars], Problem in loading DLL : [chars]

Failure to load the DLL in Inventory

Manager dllmain function call

Unable to register for invmgr edm event

notification. error: [chars]

Inventory Manager is not able to create a

EDM connection with the event manager to
populate the inventory details in to the
SYSDB database. As a reason it is not able
to resgiter for notification/verification from
SYSDB.

Unable to create/start invmgr edm

communication channel. error: [chars]

Inventory Manager is not able to open a

EDM connection channel with the event
manager to read/write the inventory details
from the SYSDB database.

Unable to allocate memory

Failure in Inventory Manager memory

allocation. No sufficient memory

Inventory Creation of RACK failed.

The RACK entry is a must in inventory

management. This is the first element in
the invntory sysdb hierachy. If the rack is
not created we are not proceeding further
to create slots.

[chars], reason: [chars]

Sysdb api call failed %s - indicates the

reason of the failure. reason: %s - is the
decoded error reason.

EEPROM/NVRAM read failed for a chassis,

card, or SPA. Inventory information would
be incomplete. This would affect
information provided to CLI 'show
inventory', inventory schema, and the
entity related MIBs. %s - indicates the
EEPROM/NVRAM read failed. Error - [chars], internal error string %d - indicates the
[dec]
internal error code

EEPROM/NVRAM read failed for a chassis,

card, or SPA. Inventory information would
be incomplete. This would affect
information provided to CLI 'show
inventory', inventory schema, and the
entity related MIBs. %s - indicates the
EEPROM/NVRAM read failed. Error - [chars], internal error string %d - indicates the
[dec]
internal error code

EEPROM/NVRAM read failed for a chassis,

card, or SPA. Inventory information would
be incomplete. This would affect
information provided to CLI 'show
inventory', inventory schema, and the
entity related MIBs. %s - indicates the
EEPROM/NVRAM read failed. Error - [chars], internal error string %d - indicates the
[dec]
internal error code

Initialization failed. [chars]. [chars]

This message indicates that process

invmgr failed to initialize and exited.
Inventory information would not be
available. This would affect CLI 'show
inventory', inventory schema, and the
entity related MIBs. Some reasons are: 1)
System manager process ready notification
failed 2) Error waiting for secondary RP to
go active 3) Internal API error %s indicates the internal message. %s indicates the internal error reason.

Initialization failed. [chars]. [chars]

This message indicates that process

invmgr failed to initialize and exited.
Inventory information would not be
available. This would affect CLI 'show
inventory', inventory schema, and the
entity related MIBs. Some reasons are: 1)
System manager process ready notification
failed 2) Error waiting for secondary RP to
go active 3) Internal API error %s indicates the internal message. %s indicates the internal error reason.

[chars], slot [dec]

This message indicates memory allocation

failure. Inventory information for the
specified slot would be incomplete. This
would affect information provided to CLI
'show inventory', inventory schema, and
the entity related MIBs for the specified
slot. %s indicates the internal data
structure that failed allocation for.

[chars], slot [dec]

This message indicates memory allocation

failure. Inventory information for the
specified slot would be incomplete. This
would affect information provided to CLI
'show inventory', inventory schema, and
the entity related MIBs for the specified
slot. %s indicates the internal data
structure that failed allocation for.

Node ID of slot [dec]. Error - [chars]

This message indicates a failure in creating

the node ID of the specified slot. Inventory
information for the specified slot would be
incomplete. This would affect information
provided to CLI 'show inventory', inventory
schema, and the entity related MIBs for the
specified slot. %s - indicates the internal
error reason.

Node ID of slot [dec]. Error - [chars]

This message indicates a failure in creating

the node ID of the specified slot. Inventory
information for the specified slot would be
incomplete. This would affect information
provided to CLI 'show inventory', inventory
schema, and the entity related MIBs for the
specified slot. %s - indicates the internal
error reason.

Slot [dec]. Error - [chars]

This message indicates a failure in creating

the object for the specified slot. The entry
is not added to the inventory. %s indicates an internal message

Slot [dec]. Error - [chars]

This message indicates a failure in creating

the object for the specified slot. The entry
is not added to the inventory. %s indicates an internal message

This message indicates a failure in creating

the sensor object for the specified slot and
sensor. The sensor entry is not added to
Slot [dec] sensor [dec] object create failed the inventory.

This message indicates a failure in creating

the sensor object for the specified slot and
sensor. The sensor entry is not added to
Slot [dec] sensor [dec] object create failed the inventory.

This message indicates bind to the

specified path failed. Inventory information
would be incomplete. This would affect
information provided to CLI 'show
inventory', inventory schema, and the
entity related MIBs. %s - indicates the
SysDB bind to [chars] failed. Error - [chars] internal error reason.

This message indicates bind to the

specified path failed. Inventory information
would be incomplete. This would affect
information provided to CLI 'show
inventory', inventory schema, and the
entity related MIBs. %s - indicates the
SysDB bind to [chars] failed. Error - [chars] internal error reason.

SysDB registration for notification on

[chars] failed. Error - [chars]

This message indicates that registration for

notification failed for the tuple specified.
%s - tuple %s - indicates the internal error
message

SysDB registration for notification on

[chars] failed. Error - [chars]

This message indicates that registration for

notification failed for the tuple specified.
%s - tuple %s - indicates the internal error
message

[chars] [hex] [chars]

This message indicates that a failure has

occured in Inventory Manager.

Initialization failed. [chars]. [chars]

This message indicates that process

invmgr failed to initialize and exited.
Inventory information would not be
available. This would affect CLI 'show
inventory', inventory schema, and the
entity related MIBs. Some reasons are: 1)
System manager process ready notification
failed 2) Error waiting for secondary RP to
go active 3) Internal API error %s indicates the internal message. %s indicates the internal error reason.

This message indicates memory allocation

failure. Inventory information for the
specified slot would be incomplete. This
would affect information provided to CLI
'show inventory', inventory schema, and
the entity related MIBs for the specified
slot. %s indicates the internal data
[chars] memory allocation failed, slot [dec] structure that failed allocation for.

Extract fields from node ID [dec] failed.

Error - [chars]

This message indicates a failure in

extracting fields from the node ID.
Inventory information for the specified
node ID(if valid), would be incomplete. This
would affect information provided to CLI
'show inventory', inventory schema, and
the entity related MIBs for the specified
node. %s - indicates the internal error.

Node ID Create for slot [dec] failed. Error [chars]

This message indicates a failure in creating

the node ID of the specified slot. Inventory
information for the specified slot would be
incomplete. This would affect information
provided to CLI 'show inventory', inventory
schema, and the entity related MIBs for the
specified slot. %s - indicates the internal
error reason.

Slot [dec] object create failed. Error [chars]

This message indicates a failure in creating

the object for the specified slot. The entry
is not added to the inventory. %s indicates an internal message

This message indicates a failure in creating

the sensor object for the specified slot and
sensor. The sensor entry is not added to
Slot [dec] sensor [dec] object create failed the inventory.

This message indicates bind to the

specified path failed. Inventory information
would be incomplete. This would affect
information provided to CLI 'show
inventory', inventory schema, and the
entity related MIBs. %s - indicates the
SysDB bind to [chars] failed. Error - [chars] internal error reason.

SysDB registration for notification on

[chars] failed. Error - [chars]

This message indicates that registration for

notification failed for the tuple specified.
%s - tuple %s - indicates the internal error
message

[chars]

This message indicates that setting up

system database for any data
changes/retrieval failed. The failure may
occur when we read/write/delete tuples
from/to sysdb. This would affect
information provided to CLI 'show
inventory', inventory schema, and the
entity related MIBs. %s - indicates the
failure.

OIR: Node [chars] inserted\n

Entity specified in the messages is inserted

into the chassis and inventory manager is
updated.

OIR: Node [chars] inserted\n

Entity specified in the messages is inserted

into the chassis and inventory manager is
updated.

OIR: Node [chars] inserted\n

Entity specified in the messages is inserted

into the chassis and inventory manager is
updated.

OIR: Node [chars] removed\n

Entity specified in the messages is

removed from the chassis.

OIR: Node [chars] removed\n

Entity specified in the messages is

removed from the chassis.

OIR: Node [chars] removed\n

[chars]

Entity specified in the messages is

removed from the chassis.
Info message

Node: [chars], state: [chars]\n

This message indicates the node state (eg.

IOS XR RUN, MBI_RUNNING). A node being
a card, SPA, etc. %s - indicates the
node/location in
<rack>/<slot>/<instance> format %s indicates the state

Node: [chars], state: [chars]\n

This message indicates the node state (eg.

IOS XR RUN, MBI_RUNNING). A node being
a card, SPA, etc. %s - indicates the
node/location in
<rack>/<slot>/<instance> format %s indicates the state

Node: [chars], state: [chars]\n

This message indicates the node state (eg.

IOS XR RUN, MBI_RUNNING). A node being
a card, SPA, etc. %s - indicates the
node/location in
<rack>/<slot>/<instance> format %s indicates the state

[chars]

Failure in Inventory Manager resulting in

error condition

[chars] failed for slot [dec]. Error [dec]

The sensor entry will not be added in

inventory. This would affect information
provided to CLI 'show inventory', inventory
schema, and the entity related MIBs.

[chars] failed for slot [dec]

The sensor entry will not be added in

inventory

[chars] failed for slot [dec]

The sensor entry will not be added in

inventory

Extract fields from node ID [dec] failed.

Error - [chars]

This message indicates a failure in

extracting fields from the node ID.
Inventory information for the specified
node ID, if valid, would be incomplete. This
would affect information provided to CLI
'show inventory', inventory schema, and
the entity related MIBs for the specified
node. %s - indicates the internal error.

Extract fields from node ID [dec] failed.

Error - [chars]

This message indicates a failure in

extracting fields from the node ID.
Inventory information for the specified
node ID, if valid, would be incomplete. This
would affect information provided to CLI
'show inventory', inventory schema, and
the entity related MIBs for the specified
node. %s - indicates the internal error.

[chars]

This message indicates a failure in

inventory manager. This is an internal
debug message. %s - indicates the failure.

[chars]

This message indicates a failure in

inventory manager. This is an internal
debug message. %s - indicates the failure.

[chars]

This message indicates a failure in

inventory manager. This is an internal
debug message. %s - indicates the failure.

IPCP Error: [chars]

The error occurs due to the failure in

initialization or creation of the event
manager.

IPCP Server process initialization failed [chars]: [chars]

A fatal software error encountered during

IPCP Server process initialization. The
specific error and cause are appended to
the error message. Process will be
terminated. Node can't function properly
and will be reset.

IPCP Server process initialization failed [chars]: [chars]

A fatal software error encountered during

IPCP Server process initialization. The
specific error and cause are appended to
the error message. Process will be
terminated. Node can't function properly
and will be reset.

IPCP has been restarted. Node [chars] is

going down for reboot.

IPCP server has been restarted. The node

will be reloaded. This is not an error.

IPCP has been restarted. Node [chars] is

going down for reboot.

IPCP server has been restarted. The node

will be reloaded. This is not an error.

JBI-Err: [chars]

This is an error message from the altera

JTAG player, it indicates that something has
gone wrong with FPGA programming.

JBI-Info: [chars]

This is an informational message from the

altera JTAG player

JBI-Debug: [chars]

This is a debuging message from the altera

JTAG player

open of [chars] failed with errno=[dec]

([chars])

This message indicates that the file open

failed on storage device.

[chars]

Procmgr encountered an error during

initialization resulting in restarting the
Procmgr process. This may be a program
level error. The failure will cause the
Procmgr process to restart.

[chars]

Ltrace initialization failed. This may be a

program level error. The failure will cause
the Procmgr process to restart.

[chars]

pcie attach has failed and process will

respawn

[chars]

Pearl LC Kensho-GL CPU Subsystem DLL

warning message. No system functional
impact.

[chars]

Informational Pearl LC Kensho-GL CPU

Subsystem DLL message.

Bridge MAC table has reached max limit.

No more MACs can be learned or manually The maximum number of MAC addresses
added.
have been learned to a physical limit

Maximum number of ACs allocated on a

bridge on a single NP. Resource exceeded.

Exceeded maximum number of ACs on a

bridge on a single NP.

Bridge member table on one or more NP

has reached max limit. No more bridge
ports can be added on the NP.

Exceeded maximum number of bridge

ports allocated on a single NP

Storm control policer allocation failure

Storm control policer allocation has failed

on at least one bridge port.

Lamp test aborted. [chars]

Lamp Test has been aborted due to an

internal error.

Lamp test is now complete.

Test of all system LEDs has now finished.

Lamp test has been initiated.

Test of all system LEDs is now in progress.

Lamp Test attempt rejected because a

lamp test is already in progress.

Lamp Test cannot be executed because

another lamp test operation is already in
progress.

[chars]:[dec], [chars], error - [chars]

A run time error occurred while initializing

the lc idb on the linecard. The reason for
the error is dispalyed. Please call Cisco
Support with the error information

[chars]:[dec], [chars], error - [chars]

A run time error occurred while initializing

the lc idb on the linecard. The reason for
the error is dispalyed. Please call Cisco
Support with the error information

[chars]:[dec], [chars], error - [chars]

A run time error occurred during the lc idb

operation on the linecard. The reason for
the error is dispalyed. Please call Cisco
Support with the error information

[chars]:[dec], [chars], error - [chars]

A run time warning occurred during the

pidb operation on the linecard. The reason
for the error is dispalyed. Please call Cisco
Support with the error information

[chars]:[dec], [chars], error - [chars]

Informational message. No action needed

[chars]:[dec], [chars], error - [chars]

A run time error occurred while initializing

the lc idb on the linecard. The reason for
the error is dispalyed. Please call Cisco
Support with the error information

[chars]:[dec], [chars], error - [chars]

A run time error occurred while initializing

the lc idb on the linecard. The reason for
the error is dispalyed. Please call Cisco
Support with the error information

[chars]:[dec], [chars], error - [chars]

A run time error occurred during the lc idb

operation on the linecard. The reason for
the error is dispalyed. Please call Cisco
Support with the error information

[chars]:[dec], [chars], error - [chars]

A run time warning occurred during the

pidb operation on the linecard. The reason
for the error is dispalyed. Please call Cisco
Support with the error information

[chars]:[dec], [chars], error - [chars]

Informational message. No action needed

LC CPU controller driver detected no active LC CPU controller driver detected no active
RSP in the system
RSP in the system.

LC CPU controller driver has detected no

RSP in the system

LC is unable to detect any RSPs in the

chassis.

LC CPU controller driver detected

inconsistency in active arbiter signals

LC CPU controller driver detected

inconsistency between raw and decoded
active arbiter signals.

LC CPU controller driver detected

inconsistency in active RSP signal

LC CPU controller driver detected

inconsistency between raw and decoded
active RSP signals.

LC CPU controller driver detected board

revision mismatch

LC CPU controller driver version is not

compatible with the current Board.

LC CPU controller driver detected board

revision parity error

LC CPU controller driver detected a board

revision parity error.

LC CPU controller driver version is not

compatible with the hardware version.
[chars]

LC CPU controller driver version is not

compatable with the hardware version.

LC CPU controller driver detected no active LC CPU controller driver detected no active
fabric in the system.
arbiter in the system.

LC CPU controller driver no active fabric in LC CPU controller driver detected no active
the system
fabric in the system.

LC CPU controller driver detected fabric

parity from RSP

LC CPU controller driver detected fabric

parity from RSP.

LC CPU controller driver detected Tx/Rx

parity error

LC CPU controller driver detected a parity

error on Tx/Rx

This board is running in hardware

debugging mode. Some features such as
FPGA image failover mechanisms,
watchdogs, and envmon shutdowns are
disabled in this mode. It is intended for
HARDWARE DEBUG use only. It should
The board is running in hardware
NEVER be running XR in this mode for any
debugging mode. Some features on the
other purpose. Unpredictable behaviours
card are disabled and it should not be used and unexpected errors may occur while
except for hardware debugging.
running in hardware debugging mode.

[chars]:[dec], [chars], error - [chars]

A run time error occurred while initializing

the pidb on the linecard. The reason for the
error is dispalyed. Please call Cisco Support
with the error information

Initialization error at [chars]:[dec] suberror: [chars], error-str: [chars]

Above run time error occurred while

initializing the pidb on the linecard.

[chars]:[dec], [chars], error - [chars]

A run time error occurred while initializing

the pidb on the linecard. The reason for the
error is dispalyed. Please call Cisco Support
with the error information

[chars]:[dec], [chars], error - [chars]

A run time error occurred during the pidb

operation on the linecard. The reason for
the error is dispalyed. Please call Cisco
Support with the error information

Run-time error occured at [chars]:[dec],

sub-error: [chars], error-str: [chars]

A run time error occurred during the pidb

operation on the linecard. The reason for
the error is dispalyed.

File operation failed at [chars]:[dec], suberror: [chars], error-str: [chars]

Failed to open a above mentioned file on

the linecard. The reason for the error is
dispalyed.

[chars]:[dec], [chars], error - [chars]

A run time warning occurred during the

pidb operation on the linecard. The reason
for the error is dispalyed. Please call Cisco
Support with the error information

[chars]:[dec], [chars], error - [chars]

Informational message. No action needed

Discovered board revision not compatible

with expected board revision

CPU controller board revision (MB.DB)

mismatch. MB = Mother Board, DB =
Daughter Board.

Board revision parity error encountered

CPU controller board revision parity error

encountered on either mother board or
daughter board

CPU A/D bus parity error detected on data

receive

CPU controller FPGA detected a parity error

on the CPU A/D bus during data reception
from the CPU.

Discovered device ID not equal to expected

device ID
Unexpected CPU controller device ID.

SW version is not compatible with HW

version

The CPU controller driver software is not

compatable with the CPU controller
hardware version.

SPAQFPBridgeCtrl0 ERP bus parity error

detected on data receive

CPU controller FPGA detected a parity error

on the SPAQFPBridgeCtrl0 ERP bus during
data reception from SPAQFPBridgeCtrl0.

SPAQFPBridgeCtrl1 ERP bus parity error

detected on data receive

CPU controller FPGA detected a parity error

on the SPAQFPBridgeCtrl1 ERP bus during
data reception from SPAQFPBridgeCtrl1.

Interrupt parity errors exceeded fatal

threshold

CPU controller FPGA detected repeated

parity errors on the A/D CPU bus or one of
the SPAQFPBridgeCtrl ERP buses.

Module identification test skipped. Modules

on the line card are not certified for live
Hardware in the specified location could
network operation.
not be verified as a genuine Cisco product.

Unable to initialize the daughter controller. The line card daugher board control
[#[hex]#]
initialization failed.

Failed to initialize [chars] ([hex] - [chars])

An attempt to initialize a component failed.

The error message describes the error,
provides an error code and a string
interpretation of the error code.

Unable to initialize MPA in bay: [dec],

[chars] ([hex] - [chars])

Unable to initialize MPA due to an internal

software error. The error message
describes the error.

Unable to initialize MPA in bay [dec] ([hex] Unable to initialize the MPA due to failure in
- [chars]) [#[hex]#]
starting internal software process (vic).

[chars] MPA PHY initialization failed:

bay=[dec] phy=[dec] rc=0[hex]

MPA PHY initialization failed.

Unable to power on MPA in bay:[dec].

Reason:[chars] ([hex]-[chars])

Unable to power on the MPA during

initialization. The software attempts to
recover from this error. This message also
provides an error code and a string
interpretation of the error code.

MPA failure in bay: [dec], [chars] ([hex] [chars])

Unable to use MPA due to an internal

software error. The error message
describes the error.

Failed to initialize PHY ([hex] - [chars])

An attempt to initialize PHY failed. The

error message describes the error, provides
an error code and a string interpretation of
the error code.

Failed to initialize shared memory for

[chars] ([hex] - [chars])

An attempt to initialize shared memory

failed. The error message describes the
error, provides an error code and a string
interpretation of the error code.

Failed to initialize [chars] ([hex] - [chars])

An attempt to initialize a component failed.

The error message describes the error,
provides an error code and a string
interpretation of the error code.

1588 timing configuration failure : [chars]

([hex] - [chars])

An attempt to initialize or configure timing

failed. 1588 Timing functionality may be
impacted if it is configured. The error
message describes the error, provides an
error code and a string interpretation of the
error code.

LDA trace logging init failed for [chars]

([hex] - [chars])

This message indicates that LDA failed to

initialize the internal debug tracing. While
this doesn't affect router functionality, it
does limit the ability to debug failures in
the LDA and LC driver subsystem.

Failed to map the MPA's shared memory.

Failed to map MPA shared memory ([hex] - The error message describes the Software
[chars]) [#[hex]#]
warning.

In Slot [dec], BAD MPA IDPROM, ([hex] [chars]) [#[hex]#]

Unable to initialize MPA due to IDPROM

read error.

MPA Information not present ([hex] [chars])

Unable to initialize MPA as IDPROM info is

not available.

Unable to shutdown MPA in bay [dec] as

corresponding NP cleanup failed

This message indicates MPA showdown

failed as corresponding NP cleanup failed

OIR operation was performed on MPA in

bay:[dec] while the system is initializing.
Recommend waiting for two minutes after
EP initialized.

The OIR operation was performed quickly.

Recommendation is to wait for two minutes
before doing next MPA OIR.

During MPA shutdown unable to clean up

the software for bay [dec], ep_type [hex]

During MPA shutdown unable to clean up

the vic process software corresponding to
the bay.

[chars] ([hex] - [chars])

A warning about a unexpected event that

occurred. The warning message describes
the event. The event does not impact any
critical system functionality, but may affect
some auxiliary function such as internal
debugging or may activate some recovery
path.

[chars]

An informational message about an

expected event as described by the
message.

This message indicates that a client of the

LDA server requested an operation that is
not implemented for this card type. The
message may provide informational value,
Opcode: [chars]{[dec]} is not found ([hex] if there are other unexpected behaviors
- [chars]) [#[hex]#]
observed.

[chars], error: [chars]\n

This message indicates that the requested

node isolation action failed due to the
specified error. The sysmgr will as a result
not proceed with the isolation action prior
to card reset and simply reset the card to
recover.

[chars], error: [chars]

This message indicates that the requested

node isolation action failed due to the
specified error. The sysmgr will as a result
not proceed with the isolation action prior
to card reset and simply reset the card to
recover.

[chars]: [chars]

This message is for information related to

node isolation.

[chars] completed successfully\n

This message indicates that the requested

node isolation action completed
successfully.

[chars] completed successfully

This message indicates that the requested

node isolation action completed
successfully.

[chars]: The flash card has been removed

Probably the flash card has been removed.

[chars]: The flash card has been inserted

The pcmcia flash card has been inserted.

pcmciad spawn of process [chars] failed.

Disk media might be unavailable to access,
or OIR would fail. Please restart pcmciad
process to recover.

pcmciad spawns filesystem process and

cardmgrd. One of them died and its
respawn failed. After this, disk media might
be unavailable or OIR would fail.

pcmciad child \[chars]\ died. Being

restarted

pcmciad spawns filesystem process and

cardmgrd. One of them died and hence
being restarted

pcmciad failed to reopen standard output

file descriptor. It continues to spawn new
process without standard output.

pcmciad will spawn filesystem process and

cardmgrd without standard output. This
would result in no debug messages from
those processes.

[chars]() failed: [chars]

The function specified failed

Malloc failed: [chars]

Low in memory

pcmciad spawn of process [dec] failed,

since no information available

pcmciad stores the pids of its children in

/tmp. For some reason the file might have
got corrupted

Open of file [chars] failed: [chars]

Open of file failed.

sleepon_lock failed: [chars]

deadlock error.

UDI information for the chassis could not

be retrieved.

Issue in initialization of platform library and

recevie the UDI information for license
management ,Possible reason for the issue
are a. Unknown platform/Card type and
installation of more that two RP's in the
system . b. Data in back plane nvram
cache is corrupt . To resolve we need to
intiate dSC re-election which will update
the required licensing udi data.

Failed to retrieve chassis UDI -- [chars]\n

Can not retrieve licensing udi data from

backplane or the udi string retrieved is
invalid or mismatch.

[chars]\n

The particular operation mentioned in the

message occured due to some reason. This
is not a failure, the process can continue
functioning as expected.

Could not create event manager for udi

process. Error: [chars]
[chars]: [chars]
[chars]: [chars]
Malloc for -[dec] bytes failed

A event manager create failed.

Miscellaneous software error.
Miscellaneous software error.
Memory allocation failed.

Sysdb registration for notification on path [chars] failed

Application failed to register for notification

[chars]:ErrStr-[chars]\n

An error occurred in mace driver due to

memory mapping failure.

MANS Dorf init failure : [chars] [hex]

A initialization failure occurred in

MANSDORF layer. The message string
indicates the reason for the failure. Here is
a list of possible reasons for this message
(not all-inclusive). - Failed in init lteace.
This condition indicates a problem with the
software when ltrace init failed.

MANSDORF No Intreeupt Handler Error:

[chars] [hex]

A critical condition occurred in MANSDORF

layer. The message string indicates the
reason for the failure. Here is a list of
possible reasons for this message (not allinclusive). - No interrupt handler. This
condition indicates a problem with the
software when there is no interrupt handler
for MANS.

A critical condition occurred in MANSDORF

layer. The message string indicates the
reason for the failure. Here is a list of
possible reasons for this message (not allinclusive). - Failed in squid_dma_req. This
condition indicates a problem with the
MANSDORF Squid DMA Req failure : [chars] software when squid_dma_req returned
[hex]
critical error.

MANS Event: [chars]

A generic event logs in MANSDORF layer.

MANS Event failure : [chars]

A generic event failure logs in MANSDORF

layer.

Users initiated a heartbeat loss

User ran a heartbeat test utility to create

heartbeat loss.

[chars]

The card could not send a heartbeat reply

to the RSP because the ethernet server
connection is down. The card will continue
to attempt to respond to the heartbeat
requests from the RSP. If the RSP continues
to not receive these messages due to this
particular or any other failure, it will issue a
command to reset this card.

[chars] error: [chars], exiting

Failed to register for getting messages from

ethernet server, therefore exiting the
process. The system will attempt automatic
error recovery by restarting the mbi-hello
process several times. If the error does not
correct itself, this card will then be
rebooted.

Fatal error: [chars] [chars], exiting

Fatal internal error occurs, the process will

be exited and this will recover
automatically by restarting the mbi-hello
process by software.

Shelfmgr detected partial heartbeat loss

for this node. Debug logs are collected on
Collecting logs as shelfmgr detected partial the bootflash locally to help identify the the
heartbeat loss
root cause of the heartbeat loss.

[chars]: error [chars]

This card has stopped receiving heartbeat

messages from the RSP. It will therefore
reset itself as it can not communicate
properly with the RSP.

[chars]: error [chars]

At process startup, the card could not set

up its audit timer for detecting a loss of
heartbeat communication with the RSP. The
system will attempt automatic error
recovery by restarting the mbi-hello
process several times. If the error does not
correct itself, this card will then be
rebooted.

Initialization time failure: [chars] [chars],

exiting

The initialization of a needed resource

failed at process startup, therefore exiting
the process. The system will attempt
automatic error recovery by restarting the
mbi-hello process several times. If the error
does not correct itself, this card will then
be rebooted.

Reload notification received. Reloading in

[dec] secs

Message indicating that the node has

received a reload notification and the node
is going to reload soon.

Reload notification received. Reloading

card in [dec] secs

Message indicating that the mbi-hello on

the card has received a reload notification
from sysldr for powering off the card and
the card is going to reload soon. Card state
is MBI_RUNNING

Node delay time over, reloading now

Message indicating that the node has

received a reload notification from the
sysldr and the node is going to reload as
the delay is over. This message is logged
after the delay over since the
NODE_RELOAD message is logged.

Unable to [chars], error: [chars]

An infrastructure component has returned

an error to the MBI infrastructure, so it may
not be able to continue with the current
operation.

Failed to run heartbeat loss log collection

script - [chars]

This may be a problem with lack of

resources. The heartbeat loss log won't get
collected.

Clock operation failed ([chars]): [chars]

A clock operation failed. This should have

only cosmetic effect on the MBI
infrastructure.

Invalid hb seq number received: [dec]

The heart beat request message from the

RSP has an invalid seq number in it. If this
error persists, the card could be reset by
the RSP.

The MBI infrastructure was unable to

connect to the Ethernet Server error:
[chars].

A communication problem occurred

between the MBI client and Ethernet
server. The MBI operation in progress will
not be carried out.

[chars] returned error [chars]

The MBI hello process could not read or

write a message via the ether server
message delivery system.

The MBI infrastructure was unable to send

a message to the Ethernet Server, error:
[chars].

A communication problem occurred

between the MBI client and Ethernet
server. The MBI operation in progress will
not be carried out.

Failure returned by heartbeat loss log

collection script (error code [dec])

The execution of the heartbeat loss log

collection script has failed, and the error
code is indicated in the error message.

[chars]: error [chars]

The specified timer operation required to

detect a potential loss of heartbeat
communication with the RSP failed. This
means that in the event that this card
stops receiving heartbeat messages from
the RSP, it might not be able to detect this
and do the necessary self-reset accordingly.

Error in fping util init ([chars])

Failed in the initialization. The process will

exit as an attempt to recover and will be
restarted.

Failed to allocate [unsigned int] bytes of

memory

The requested operation could not be

accomplished because of a low memory
condition.

The MBI infrastructure was unable to send

a message to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server. The MBI
operation in progress will not be carried
out.

Failed to request netmgr mountpoint

Failed to request netmgr mountpoint.

The MBI infrastructure was unable to

connect to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server, perhaps
because the communications infrastructure
is not yet up. The MBI operation in progress
will not be carried out.

Failed to allocate shared memory. Error:

[chars]

mbi-hello is not able to allocate shared

memory to share information with other
processes.

This may be a problem with lack of

resources. The MBI infrastructure will be
unable to carry out all of its expected
Failed to create a thread for [chars]: [chars] functionality.

Failed to create a thread for handling

[chars]: error [chars]

This may be a problem with lack of

resources. The MBI infrastructure will be
unable to carry out any requests to reset
the card from other software components.
These requests normally come during the
installation or upgrade process and also
when the user issues a '(admin)#reload
location all' CLI command. The MBI Hello
process will reboot the card via alternate
means.

Timer timed out from server : [chars]

Timer timed out from hbagent server or

MBI server.

Failed to attach a reconnect handler to

ethernet server coid. If ethernet server
restarts, heartbeat agent may not be able
to receive/write messages: [chars]

Failed to attach a reconnect handler to

ethernet server coid.

Failed to attach a reconnect handler to

ethernet server. If the ethernet server
Failed to attach a reconnect handler to the restarts, heartbeat agent may not be able
ethernet server. If the ethernet server
to receive/write messages, which could
restarts, the MBI hello process may not be eventually lead to this node being reset by
able to receive/write messages: [chars]
the RSP heartbeat monitoring code.

Card memory size too large to be sent to

dSC

While sending the MBI Hello Response

packets we check for the memory size. If
the obtained memory size of the platform
is more than the available scaled limit of
the RAM we reset the size to Zero. The Max
available Scale Value is 255 as there are
only 8 bits in the Hw_version field of the
data structure sent to the DSC.

The process will continue with it's business,

however, cause of why mbi-hello was not
able to initialize tracing should be tracked
Failed to initialize mbi_hello tracing: ([dec] : down. As result of this error, mbi-hello will
[chars])
not have any tracings.

Failed to set priority for [chars] ([chars])

Error while setting the Priority for the

Process The error is described in the
message log itself.

Error waiting on receive fabric queue.

([chars])

fping thread handles fabric pings. This

thread runs on an infinte loop and monitors
the fabric diag queue and replies to ping
when they come.There is some error
received while waiting on the Fabric ingress
ping queue.

Unable to set the heartbeat pulse of this

node to high priority. Proceeding with
default priority, however in a high CPU
Unable to set the heartbeat pulse through consumption, this node's heartbeat pulse
ethernet server to high priority. Proceeding may get lost, causing this node to get
with normal priority: [chars]
reloaded.

Unable to set the heartbeat pulse through

ethernet server to high priority. Proceeding
with default priority. However in the event
of a high CPU consumption scenario
occurring, this node's heartbeat messages
Unable to set the heartbeat pulse through might start not getting through to the RSP
ethernet server to high priority. Proceeding and if this condition persists, this node
with normal priority: [chars]
could get reloaded.

Unable to set the thread priority to high.

Proceeding with normal priority: [chars]

Unable to set the heartbeat pulse of this

node to high priority. Proceeding with
default priority, however in a high CPU
consumption, this node's heartbeat pulse
may get lost, causing this node to get
reloaded.

Unable to set the heart beat thread priority

to high. Proceeding with default priority.
However in the event of a high CPU
consumption scenario occurring, this
node's heartbeat messages might start not
Unable to set the heartbeat thread priority getting through to the RSP and if this
to high. Proceeding with normal priority:
condition persists, this node could get
[chars]
reloaded.
Sending IMDR complete message to
shelfmgr

The MBI hello process is notifying shelfmgr

that IMDR has completed.

Sending IMDR has started message to

shelfmgr

The MBI hello process is notifying shelfmgr

that IMDR has started.

Received the IMDR state of [dec] from

sysmgr

The MBI hello process received the

indicated IMDR state from the sysmgr
process. This state change will be
communicated to the shelfmgr.

The process will continue with it's business,

however, as result of this error, mbi-hello
Could not initialize mbi_hello tracing: ([dec] will not be able to collect any trace debug
: [chars])
information of its operation.

Failed to initialize ltrace buffer in [chars].

Error: [chars]

Ltrace buffer will not be available.

Debuggability will be reduced because of
lacking of ltrace buffer.

Power Cycle Request Received. Power

Cycling now !

Message indicating that the node has

received a power down request and the
node is going to power down.

Power Down Request Received. Powering

down now !

Message indicating that the node has

received a power down request and the
node is going to power down.

Message indicating that the node has

Reload request received. Reloading in [dec] received a reload request and the node is
secs
going to reload soon.
The MBI infrastructure was unable to send
a message to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server. The MBI
operation in progress will not be carried
out.

Failed to request QNX net manager

mountpoint

Failed to request netmgr mountpoint. The

debug ping to mbi-hello process could not
be accomplished.

The MBI infrastructure was unable to

connect to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server, perhaps
because the communications infrastructure
is not set up. The MBI operation in progress
will not be carried out.

Mbi-hello was restarted, but detected that

hbagent is up and functioning already.
Proceeding with passive mode

Mbi-hello process was restarted. However,

it detected that the hbagent process is
already functioning. Hence mbi-hello is
going into passive mode by design.

Partial heartbeat loss log collection

completed

Collection of heatbeat loss log has been

completed.

There is already an instance of heatbeat

loss log collection in progress. Ignoring
current heatbeat loss log collection
request.

The current request to collect heatbeat loss

log is being ignored because of another
instance of heatbeat loss log collection that
is still in progress.

MBI-Hello: Successful creation of [chars].

Attempt number [dec]\n

Successful creation of mbi-hello LWM

channel for communication.

Failed to allocate [unsigned int] bytes of

memory

The debug ping to mbi-hello process could

not be accomplished because of a low
memory condition.

The node received a test reload notification

just to check functionality. The notification
Received a test reload notification, ignore. is ignored.
The node received a test reload notification
just to check functionality. The notification
Received a test reload notification, ignore. is ignored and has no impact.
Timer timed out between the MBI client
and server, perhaps because the
communications infrastructure is not set
The MBI infrastructure timer timed out from up. The MBI operation in progress will not
server : [chars]
be carried out.

[chars]

Error in thread creation for mbi-hello

process. The error reason is described in
the message log itself.

The MBI infrastructure was unable to send

a message to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server. The MBI
operation in progress will not be carried
out.

The MBI infrastructure was unable to send

a message to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server. The MBI
operation in progress will not be carried
out. However, the MBI client will continue
trying to send the message to the server. In
the event that the operation continues
failing, then the card could be rebooted by
the RSP.

The MBI infrastructure was unable to

connect to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server, perhaps
because the communications infrastructure
is not yet up. The MBI operation in progress
will not be carried out.

The MBI infrastructure was unable to

connect to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server, perhaps
because the communications infrastructure
is not yet up. The MBI operation in progress
will not be carried out. However, the MBI
client will continue trying to connect to the
server. In the event that the operation
continues failing, then the card could be
rebooted by the RSP.

The MBI infrastructure was unable to send

a message to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server. The MBI
operation in progress will not be carried
out.

The MBI infrastructure was unable to

connect to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server, perhaps
because the communications infrastructure
is not set up. The MBI operation in progress
will not be carried out.

The MBI infrastructure was unable to send

a message to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server. The MBI
operation in progress will not be carried
out.

The MBI infrastructure was unable to send

a message to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server. The MBI
operation in progress will not be carried
out. %s - indicates the error message.

The MBI infrastructure was unable to send

a message to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server. The MBI
operation in progress will not be carried
out.

The MBI infrastructure was unable to

connect to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server, perhaps
because the communications infrastructure
is not yet up. The MBI operation in progress
will not be carried out. %s - indicates the
error message.

The MBI infrastructure was unable to

connect to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server, perhaps
because the communications infrastructure
is not yet up. The MBI operation in progress
will not be carried out.

The MBI infrastructure was unable to

connect to the MBI Hello server, error:
[chars].

A communication problem occurred

between the MBI client and server, perhaps
because the communications infrastructure
is not yet up. The MBI operation in progress
will not be carried out.

The MBI infrastructure was unable to

determine the time, error: [chars]

The infrastructure is behaving incorrectly.

This will not affect the operation of the MBI
infrastructure, but messages and logs may
not contain timestamps.

The MBI infrastructure was unable to

determine the time, error: [chars]

The infrastructure is behaving incorrectly.

This will not affect the operation of the MBI
infrastructure, but messages and logs may
not contain timestamps.

The MBI file name is possibly too large or

The MBI infrastructure was unable to copy invalid. The MBI operation in progress may
the MBI file name for location [chars], error: fail. %s - indicates the location of the error.
[chars].
%s - indicates the error itself.

The MBI file name is possibly too large or

[chars]The MBI infrastructure was unable to invalid. The MBI operation in progress may
copy the MBI file name, error: [chars].
not be carried out.

[chars]The MBI infrastructure failed to

The default MBI is either unknown or
obtain the default MBI for card class [hex], missing. The MBI operation in progress may
error: [chars].
not be carried out.

Can't able to get the boot image in the load

path, The default MBI is either unknown or
missing. The MBI operation in progress may
not be carried out. %s - indicates the node
[chars] The MBI infrastructure failed to
on which the error occurred. 0x%llx obtain the default MBI for card class [hex], indicates the class of the failing node. %s error: [chars].
gives the error message.

[chars]Failed to calculate MD5 value from

path ([chars]): [chars]

Either the path is invalid, or the

infrastructure is behaving incorrectly. The
MBI operation in progress may not be
carried out.

Failed to calculate MD5 value for location

[chars] from path ([chars]): [chars]

Either the path is invalid, or the

infrastructure is behaving incorrectly. The
MBI operation in progress may not be
carried out. %s - indicates the node on
which the error occurred. %s - gives the
path to the MBI that can't be MD5ed. %s gives the error message.

[chars]The MBI infrastructure failed to

compare MD5 values between the boot
request MBI ([chars]) and the MBI stored in
dSC ([chars]), error: [chars]. Using the MBI
([chars]) from dSC.

Either the MD5 values are invalid, or the

infrastructure is behaving incorrectly. The
MBI operation in progress may not be
carried out.

Finding out if the local MBI in dSC and the

boot requestMBI MD5 values matches or
not got failed. Either the MD5 values are
invalid, or the infrastructure is behaving
incorrectly. The MBI operation in progress
may not be carried out. %s - indicates the
The MBI infrastructure failed to compare
node on which the error occurred. %s MD5 values between the boot request MBI gives the MBI path we're comparing. %s ([chars]) and the MBI stored in dSC
gives the MBI path we're comparing
([chars]) for location [chars], error: [chars]. against. %s - gives the error message. %s Using the MBI ([chars]) from dSC.
gives the MBI path we're comparing.

The MBI passed was not in the expected

[chars]The MBI infrastructure detected an form. The MBI infrastructure will ignore this
abnormality with the MBI passed ([chars]). MBI and most likely new MBI will be
Ignoring this MBI. Error: [chars].
downloaded from dSC as result.

The MBI passed was not in the expected

form. The MBI infrastructure will ignore this
MBI and most likely new MBI will be
The MBI infrastructure detected an
downloaded from dSC as result. %s - gives
abnormality with the MBI passed ([chars]) the MBI path we're ignoring. %s - indicates
for location [chars]. Ignoring this MBI. Error: the node on which the error occurred. %s [chars].
gives the error message.

[chars]An invalid argument was passed to

the MBI infrastructure.

An internal error has occurred in an

application that has caused it to pass
invalid data to the MBI infrastructure. The
MBI operation in progress may not be
carried out.

An invalid node [chars] was passed to the

MBI infrastructure.

An internal error has occurred in an

application that has caused it to pass
invalid data to the MBI infrastructure. The
MBI operation in progress may not be
carried out. %s - indicates the location of
the error.

[chars]Unable to allocate [unsigned int]

bytes of memory.

The requested operation could not be

accomplished because of a low memory
condition. %s - indicates the location of the
error.

[chars]Unable to allocate [unsigned int]

bytes of memory

The requested operation could not be

accomplished because of a low memory
condition.

Either an invalid location is being queried,

[chars]The infrastructure failed to extract or the infrastructure is behaving incorrectly.
the R/S/I elements of node [dec] for for the The MBI operation in progress may not be
MBI infrastructure, error: [chars].
carried out.

Extracting R/S/I from the node id got failed.

Either an invalid location is being queried,
or the infrastructure is behaving incorrectly.
The MBI operation in progress may not be
The infrastructure was unable to return the carried out. %d - gives the id of the node
IP address of a node ([dec]) to the MBI
on which the error occurred. %s - indicates
infrastructure for location [chars], error:
the location of the error. %s - indicates the
[chars].
error message.

Getting a node id to find out the mbimgr is

running on that node or not got failed.
Either an invalid location is being queried,
or the infrastructure is behaving incorrectly.
The infrastructure failed to inform the MBI The MBI operation in progress may not be
infrastructure of the location [chars] where carried out. %s - indicates the location of
it is running, error: [chars].
the error. %s - indicates the error message.

Either an invalid location is being queried,

[chars]The infrastructure failed to inform
or the infrastructure is behaving incorrectly.
the MBI infrastructure of the location where The MBI operation in progress may not be
it is running, error: [chars].
carried out.

[chars]The infrastructure was unable to

return the IP address of a node ([dec]) to
the MBI infrastructure, error: [chars].

Either an invalid location is being queried,

or the infrastructure is behaving incorrectly.
The MBI operation in progress may not be
carried out.

Cant able to convert my nodeid to ip

address, Either an invalid location is being
queried, or the infrastructure is behaving
incorrectly. The MBI operation in progress
The infrastructure was unable to return the may not be carried out. %d - gives the id of
IP address of a node ([dec]) to the MBI
the node on which the error occurred. %s infrastructure for location [chars], error:
indicates the location of the error. %s [chars].
indicates the error message.

The infrastructure was unable to create an

external representation of a location ([dec])
for the MBI, error: [chars]. Error messages Either an invalid location is being queried,
from the MBI infrastructure will not contain or the infrastructure is behaving incorrectly.
the prefix-string that represents the remote The MBI operation in progress may not be
location being processed.
carried out.

The infrastructure was unable to create an

external representation of a location ([dec]) Either an invalid location is being queried,
for the MBI, error: [chars]. Error messages or the infrastructure is behaving incorrectly.
from the MBI infrastructure will not contain The MBI operation in progress might not be
the prefix-string that represents the remote carried out. %d - indicates the location of
location being processed.
the error. %s - indicates the error message.

Unexpected NULL pointer passed to the

MBI infrastructure by a client

An internal error has occurred in an

application that has caused it to pass
invalid data to the MBI infrastructure. The
current request or operation may not be
carried out.

Unexpected NULL pointer passed to the

MBI infrastructure by a client

An internal error has occurred in an

application that has caused it to pass
invalid data to the MBI infrastructure. The
current request or operation may not be
carried out.

The MBI infrastructure failed to create a

message string for a remote location
([dec]), error: [chars]. Error messages from
the MBI infrastructure will not contain the
prefix-string that represents the remote
location being processed.

Either an invalid location is being queried,

or the infrastructure is behaving incorrectly.
The MBI operation in progress may not be
carried out. %d - indicates the location of
the error. %s - indicates the error message.

[chars]The MBI infrastructure failed to

populate the TFTP information, error:
[chars].

The TFTP information is unavailable. The

MBI operation in progress may not be
carried out.

The MBI infrastructure failed to populate

the TFTP information for location [chars],
error: [chars].

The TFTP information is unavailable. The

MBI operation in progress may not be
carried out. %s - indicates the node on
which the error occurred. %s - gives the
error message.

[chars]An unknown boardtype ([dec]) was

passed to the MBI infrastructure.

Either an invalid boardtype is being

queried, or the infrastructure is behaving
incorrectly. The MBI operation in progress
may not be carried out.

Either an invalid boardtype is being

queried, or the infrastructure is behaving
incorrectly. The MBI operation in progress
may not be carried out. %s - indicates the
[chars] An unknown boardtype ([hex]) was location of the error. 0x%llx - gives the
passed to the MBI infrastructure.
boardtype.

The MBI infrastructure failed to create a

message string for a remote location
([dec]), error: [chars]. Error messages from
the MBI infrastructure will not contain the
prefix-string that represents the remote
location being processed.

Either an invalid location is being queried,

or the infrastructure is behaving incorrectly.
The MBI operation in progress may not be
carried out.

MBIMGR: [chars] ([dec])

MBIMGR: [chars] ([dec])

MBI Mgr general info, where one part of the

specifiable info is a string, the other a digit.
MBI Mgr general info

MBIMGR: [chars] ([chars])

MBIMGR: [chars] ([chars])

MBI Mgr general info, where both parts of

the specifiable info are strings.
MBI Mgr general info

[chars]MBI [chars] validated

A message to indicate which MBI was

validated for which location.

[chars]: MBI [chars] validated

A message to indicate which MBI was

validated for which location.

[chars]Invalid MBI spec passed in ([chars]): A problem was found in the MBI spec that
[chars]
was passed in.

[chars]Invalid MBI spec passed in ([chars]): A problem was found in the MBI spec that
[chars]
was passed in.

The version of Mbus agent ROM on slot is

not current. %d - is the slot number of the
card in question. %d - is the major version
of the agent currently in ROM %d - is the
slot [dec]: mbus rom agent is down-rev
minor version of the agent currently in
(V[dec].[dec]), suggest upgrade to current ROM %d - is the major version of the agent
(V[dec].[dec]). Use the \upgrade mbus\ CLI that is recommeneded %d - is the minor
in admin mode.
version of the agent that is recommeneded

The version of Mbus agent ROM on slot is

not current. %d - is the slot number of the
card in question. %d - is the major version
of the agent currently in ROM %d - is the
slot [dec]: mbus rom agent is down-rev
minor version of the agent currently in
(V[dec].[dec]), suggest upgrade to current ROM %d - is the major version of the agent
(V[dec].[dec]). Use the \upgrade mbus\ CLI that is recommeneded %d - is the minor
in admin mode.
version of the agent that is recommeneded

The version of Mbus agent ROM on slot is

not current. %d - is the slot number of the
card in question. %d - is the major version
of the agent currently in ROM %d - is the
slot [dec]: mbus rom agent is down-rev
minor version of the agent currently in
(V[dec].[dec]), suggest upgrade to current ROM %d - is the major version of the agent
(V[dec].[dec]). Use the \upgrade mbus\ CLI that is recommeneded %d - is the minor
in admin mode.
version of the agent that is recommeneded

mbus: zero length packet with type [dec]

from slot [dec]

mbus debug information %d - mbus

message type. %d - slot where packet
originated

mbus: zero length packet with type [dec]

from slot [dec]

mbus debug information %d - mbus

message type. %d - slot where packet
originated

mbus: zero length packet with type [dec]

from slot [dec]

mbus debug information %d - mbus

message type. %d - slot where packet
originated

[chars] ([hex])

mbus API debugging information. The error

message and the return code indicate the
type of error.

download failed ([chars]).

mbus debug info %s - a string containing

the slot number.

Failed to perform [chars] on file \[chars]\.

mbus API debug information indicating the

file and the operation on the file that failed

[chars]

mbus debug information %s - debug

message

[chars]

Displaying mbus API debug information.

The argument indicates information
message to be displayed

invalid slot [dec].

[chars]

mbus debug information indicating the

invalid slot number
mbus debug information

[chars]

mbus debugging information. %s - debug

message

[chars] ([hex])
[chars]

mbus debug info %s - attach error

information. %X - error return code
mbus debug info %s - attach statistics

[chars]

mbus debug information %s - describes the

function that failed

[chars]

mbus debug information. %s - is the

information being displayed for debug
purposes

[chars]

mbus debug information. %s - is the

information being displayed for debug
purposes

mbus: local agent check failed ([chars]).

mbus debug information %s - is a string

outlining the action that the system will
take to attempt to recover (e.g. forcing
RAM download).

mbus: local agent check failed ([chars]).

mbus debug information %s - is a string

outlining the action that the system will
take to attempt to recover (e.g. forcing
RAM download).

mbus: local agent check failed ([chars]).

mbus debug information %s - is a string

outlining the action that the system will
take to attempt to recover (e.g. forcing
RAM download).

[chars] ([hex])

mbus debug information. %s - is the debug

message

[chars] ([hex])

mbus debug information. %s - is the debug

message

[chars] ([hex])

mbus debug information. %s - is the debug

message

mbus: EOF unexpected on file \[chars]\.

mbus debug information. %s - is the file

name in question.

mbus: EOF unexpected on file \[chars]\.

mbus debug information. %s - is the file

name in question.

mbus: EOF unexpected on file \[chars]\.

mbus debug information. %s - is the file

name in question.

mbus: Failed to perform [chars] on file \

[chars]\.

mbus debug information. %s - indicates the

type of file operations (e.g. open, close) %s
- is the file name in question.

mbus: Failed to perform [chars] on file \

[chars]\.

mbus debug information. %s - indicates the

type of file operations (e.g. open, close) %s
- is the file name in question.

mbus: Failed to perform [chars] on file \

[chars]\.

mbus debug information. %s - indicates the

type of file operations (e.g. open, close) %s
- is the file name in question.

[chars]

mbus debug information being displayed

for debug purpose.

[chars]

mbus debug information being displayed

for debug purposes

[chars]

mbus debug information being displayed

for debug purposes

mbus: invalid stream [dec].

mbus debug information %d - is the stream

identifier.

mbus: invalid stream [dec].

mbus debug information %d - is the stream

identifier.

mbus: invalid stream [dec].

mbus debug information %d - is the stream

identifier.

L2 CACHE ERROR

The message is displayed whenever there

is a L2 cache error in CPU.

FPGA and MCU failed to synchronize

The FPGA and the MCU failed to exchange

the configuration information about the
board. The user will not be able to start a
console tunneling session to this node.

The SP FPGA version is too old (minimal

version required is [dec].[dec])

If the SP FPGA version is below the minimal

version, the feature to check if the FPGA
and the MCU are synchronized is not
working correctly. To prevent any
unexpected behavior, the application that
is reporting the out of synchronization will
be disabled.

Failed to [chars], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

Version translation from [unsigned int] to

[unsigned int] failed for table [unsigned
int]: [chars]

Version upgrade from one version to

another failed. Traffic loss is expected till
database is rebuilt.

MGID Server: Total allocated MGIDs have

reached system limit. No more allocations
allowed until total allocated MGIDs goes
below critical threshold

Total number of allocated MGIDs has

reached system capacity. No more MGID
allocations will be allowed until some
MGIDs have been freed so that the total
allocation falls below the critical threshold.

MGID Server: Total allocated MGIDs have

Total number of MGIDs (Multicast Group ID)
crossed [dec], MGIDs will now be allocated allocated in the system is above the pre
from the extended MGID range
4.2 release system threshold.

MGID Server: Total allocated MGIDs is

below critical threshold ([unsigned int])

Total number of MGIDs (Multicast Group ID)

allocated in the system is below the system
critical threshold. New MGID allocations will
be allowed from this point onwards.

MGID Server: Total allocated MGIDs have

reached system limit ([unsigned int]). No
more allocations allowed until total
allocated MGIDs goes below critical
threshold ([unsigned int])

Total number of allocated MGIDs has

reached system capacity. No more MGID
allocations will be allowed until some
MGIDs have been freed so that the total
allocation falls below the critical threshold.

ACL used by the optimized-fabric-multicast

MGID Server: ACL ([chars]) used in the hw- feature has been unconfigured without
module optimized-fabric-multicast
removing the optimized-fabric-multicast
configuration has been removed without
configration, this can cause unexpected
de-attaching it first
system behaviour.

MGID Server: Total high bandwidth MGIDs

have reached configured limit ([unsigned
int]). High bandwidth flows will now be
allocated MGIDs from the general pool.

The max flow count configured in the cli hw-module optimized-fabric-miulticast... has been reached. There are no more high
bandwidth MGIDs available for high
bandwidth flows that match the ACL
provided in the - hw-module ... - CLI. High
bandwidth flows will now be allocated
MGIDs from the general pool

MGID Server: Optimized fabric multicast

CLI change detected, multicast flows
resync process complete.

User has previously changed the ACL or the

MAX FLOW COUNT which is part of the hwmodule optimized-fabric-multicast CLI
which triggered a resync operation. The
operation is now complete and multicast
traffic should be restored to affected
multicast flows.

MGID Server: Optimized fabric multicast

CLI change detected, multicast flows will
now undergo a resync process, traffic loss
is expected for affected multicast flows.

User changed the ACL or the MAX FLOW

COUNT which is part of the hw-module
optimized-fabric-multicast CLI. Multicast
flows will be resynced to update the high
bandwidth and low bandwidth
identification. Momemtary traffic loss is
expected until the process is complete

[chars] busy flag failed to clear, error

[chars]\n

The busy flag for this particular operation

mentioned in the message failed to clear
for some reason. The MLAN switch was
reset. This is not a critical failure, the
process can continue functioning as
expected despite the failure.

Failed to [chars] for port [dec], error

[chars].\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

[chars] [chars]\n

The particular operation mentioned in the

message failed due to some reason. This
might be a critical failure, the process can
continue functioning as expected despite
the failure.

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
Failed to [chars], port [dec], error [chars]\n the failure.

MLAN switch reset failed, error [chars]\n

The reset of the switch failed for some

reason. This is not a critical failure, the
process can continue functioning as
expected despite the failure.

[chars], for port [dec]. Status/Value is

[dec].\n

The particular operation mentioned in the

message gave a informative message. This
is not a failure.

[chars]\n

The particular operation mentioned in the

message gave a informative message. This
is not a failure.

[chars], for port [dec]. Status/Value is

[dec].\n

The particular operation mentioned in the

message gave an informative message.
This is not a failure.

[chars] traceback for port [dec].\n

The particular operation mentioned in the

message gave a trace message. This is not
a failure.

LR is going to ROOT role

This logical router(LR) is going to be root

role, this can happen when an LR initially
boots up, it can take the root role if no
other root LR is present. Also when current
root goes down either due to root failure or
reloading the root LR could cause the
backup root change the state to root. This
message displayed when an LR is going
root.

MLR configuration has changed for the LR

mentioned in the message,this is an
expected behaviour. We will see this
message in following cases. 1.Any new Slot
Addition to the MLR Group 2.Deletion of
MLR Config changed for LR - [chars],hence slot from the LR Group 3.Slot Additions or
it will be reloaded
removal between LR Groups.

Controller [dec]: [chars]

There are some PCI errors reported as

shown. Those errors are non-fatal. %d - the
PCIe controller id %s - indicates the reason
for the failure.

Controller [dec]: [chars]

MPC8641 PCI Controller encounters a fatal

error. %d - MPC8641 PCI Controller id. %s is the error reason.

[chars] failed ([chars])

[chars], [chars], err = [hex]

There are S/W errors to setup the interrupt

handling for MPC8641's PCI controller's
interrupts.
Failure in Multishelf Manager.

Exceeding max [chars]

This message indicates that the

configuration is exceeding the maximum
Sampling Rate of 4 or the maximum Flow
Sampler limit of 16 in a given direction.

[chars]

Netflow punt rate is more than policer rate,

it informs the user when such an event
occurs

[chars]

Netflow punt rate is more than policer rate,

it informs the user when such an event
occurs

[chars]

Netflow punt rate is more than policer rate,

it informs the user when such an event
occurs

[chars]

During initialization, an internal error

occurred in Netflow which involves exiting
the process.

[chars]

During initialization, an internal error

occurred in Netflow which involves exiting
the process.

[chars]

During initialization, an internal error

occurred in Netflow which involves exiting
the process.

Addition of flow exporter([chars]) resulted

in crossing the limit of the number of
supported exporters in flow monitormap([chars]). Maximum is [dec] per flow
monitor-map. Please remove the extra
exporter configuration from the monitormap.

The number of flow exporter support in

hardware is limited. The config has resulted
in exceeding this limit.

Satori 8 base board did not power up fully:

powerfail_reg:[hex]
The Satori-8 RP did not power up fully.

NP DOUBLE ECC ERROR, NP=[dec],

memId=[dec], subMemId=[hex]

NP detects double ECC ERROR and

reported through interrupts

[chars]

Network Processor Initialization

encountered a critical error that renders
the system unusable.

[chars]

A critical errror has been encountered that

renders the system unusable.

A non-recoverable soft error has been

detected on NP[dec]. The linecard will be
rebooted.

PRM has detected a non-recoverable soft

error on NP %d. The linecard will be
rebooted.

Persistent Initialization Failure.

NP Persistent Initialization failure Indicates

a problem with the Network processor on
the LineCard.

Unrecoverable out of resources error

NP system resources have been exhausted

and cannot be recovered

Pex parity error

A parity error interrupt at data phase of the

PEX WR transaction

TCAM excessive correctable parity error.

np[dec] saw >[dec] per hour

TCAM correctable parity errors have

occurred more often than expected.

TM cluster parity interrupt. Indicates an

internal SRAM problem in TM cluster,
NP=[dec]

A parity error interrupt

TM control memory cluster parity interrupt.

Indicates an internal SRAM problem in TM
control memory, NP=[dec] memId=[dec],
mask=[hex], PMask=[hex]
SRAMLine=[dec] Rec=[dec] Rewr=[dec]
A parity error interrupt

TMa cluster parity interrupt. Indicates an

internal SRAM problem in TMa cluster,
NP=[dec] memId=[dec], mask=[hex],
PMask=[hex] SRAMLine=[dec] Rec=[dec]
Rewr=[dec]

A parity error interrupt

TMb cluster parity interrupt. Indicates an

internal SRAM problem in TMb cluster,
NP=[dec] memId=[dec], mask=[hex],
PMask=[hex] SRAMLine=[dec] Rec=[dec]
Rewr=[dec]

A parity error interrupt

TMc cluster parity interrupt. Indicates an

internal SRAM problem in TMc cluster,
NP=[dec] memId=[dec], mask=[hex],
PMask=[hex] SRAMLine=[dec] Rec=[dec]
Rewr=[dec]

A parity error interrupt

Central cluster parity interrupt. Indicates

an internal SRAM problem in the
TOPModify/PEX/General block, NP=[dec]
memId=[dec], mask=[hex], PMask=[hex]
SRAMLine=[dec] Rec=[dec] Rewr=[dec]

A parity error interrupt

fatal interrupt case and unable to handle,

chip=[dec], memId=[dec]

Unable to handle the interrupt. Too many

errors.

NP SINGLE ECC ERROR, NP=[dec],

memId=[dec], subMemId=[hex]

NP detects single ECC ERROR and reported

through interrupts

Matrix cluster parity interrupt. Indicates an

internal SRAM problem in the Shared block.
NP=[dec] memId=[dec], mask=[hex],
PMask=[hex] SRAMLine=[dec] Rec=[dec]
Rewr=[dec]
A parity error interrupt

Failed to retrieve the configured memory

resource profile from SysDB. Default profile
will be activated. In order to instate the
configured profile this line card must be
reloaded.

Attempt to retrieve configured memory

resource profile from SysDB failed,
resulting in activation of the default
memory resource profile.

NP diagnostics warning on NP[dec].

Self diagnostics has detected NP packet

processing problem. Automatic recovery
action will be attempted. Further alarm will
be raised if automatic recovery attempts
fail.

TopParse cluster parity interrupt. Indicates

an interanl SRAM problem in the TopParse.
NP=[dec] memId=[dec], mask=[hex],
PMask=[hex] SRAMLine=[dec] Rec=[dec]
Rewr=[dec]
A parity error interrupt

TOPresolve cluster parity interrupt.

Indicates an internal SRAM problem in the
TOPResolve block, NP=[dec] memId=[dec],
mask=[hex], PMask=[hex]
SRAMLine=[dec] Rec=[dec] Rewr=[dec]
A parity error interrupt

[chars]

TCAM programming encounters error and

rollback fails. This is a double fault
condition. Traffic mis-classification or loss
may occur.

TOPsearch I cluster parity interrupt.

Indicates an interanl SRAM problem in the
TOPsearch I block, NP=[dec] memId=[dec],
mask=[hex], PMask=[hex]
SRAMLine=[dec] Rec=[dec] Rewr=[dec]
A parity error interrupt

tcam fatal interrupt case and unable to

handle, chip=[dec]

Unable to handle the interrupt. too many

tcam parity errors.

TCAM write parity error. chip=[dec]

A parity error interrupt

The buffers used by all TMs

(TMa+TMb+TMc) exceeds the configured
threshold

NP detects BIQ_EMPTY and reported

through interrupts

[chars]

The Network Processor experienced a self

diagnostic error in operation. The error is
automatically recovered via self healing NP
fast reset. Minor loss of traffic is expected
during recovery.

[chars]

The Network Processor experienced a bit

error in NP memory. This may be a parity
error, a single bit ECC, or a double bit ECC.

The side B (TMb+TMc) Frame buffers pool

is empty

NP detects EG_FBU_POOL_EMPTY and

reported through interrupts

The FBU3 low resource interrupt

NP detects FBU3_LOW_RESOURCE and

reported through interrupts

The buffers used by frames destined for

NP detects HOST_SLAVE_QUEUE_FULL and
Host PCI exceeds the configured threshold reported through interrupts

The TMa destination host slave queue not

empty

NP detects
HOST_SLAVE_QUEUE_NOT_EMPTY and
reported through interrupts

OQ structure is full. System cannot write

additional OQ entries into the queue

NP detects OQ_FULL and reported through

interrupts

The number of buffers in the Rx Pointer

Table reaches zero

NP detects RX_RFD_EMPTY and reported

through interrupts

TFD structure is full. System cannot write

additional TFD entries into the queue

NP detects OQ_FULL and reported through

interrupts

The number of buffers in the Tx Pointer

Table reaches zero

NP detects TX_RFD_EMPTY and reported

through interrupts

[chars]

The swappable interface on the network

processor failed the OIR event.

The TMa frame buffers pool is empty

NP detects ING_FBU_POOL_EMPTY and

reported through interrupts

[chars]

Network Processor Provisioning

experienced an Out-of-resource condition
that could not be reported back to
provisioning agent for recovery/back-off
Loss of configuration and data could occur.

The buffers used by destination TMa

exceeds the configured threshold

NP detects TMA_FULL and reported through

interrupts

The buffers used by destination Side B

(TMb+TMc) exceeds the configured
threshold

NP detects TMB_FULL and reported through

interrupts

[chars]

The Network Processor experienced an

unexpected error condition. Loss of
configuration could have occurred.

[chars]

Initialization cannot be completed because

sysdb is not ready to accept registrations.

[chars]

config will be activated only after a line

card reset

[chars]

Network Processor Experienced a Fault

condition that has been self-recovered
from. If this condition persists or occurs
frequently, line card is deemed unhealthy.

[chars]

A memory resource profile has been

configured for the system using '(adminconfig)#hw-module profile <>'. However,
this profile has not been activated on the
line card that originated the warning
message. Use '#show hw-module profile
<> location X/Y/cpu0' to see what profiles
are currently active on the line card.

[chars]

There is some configuration on the line

card that originated the warning message
that is not supported by the active memory
resource profiles. Consult the warning
message for details.

[chars]

The NP has recovered from a diagnostic

error and is now back to normal operation.

TX PDMA Ring Stalled, queue = [[chars]],

cur_ind = [dec], tx_ind = [dec].

CPUCTRL TX PDMA ring remained full over

non-transient period. Packets which could
not be sent were discarded. The
downstream ASIC may be stalled. Asic error
logged with queue details.

RX PDMA Ring out of buf, queue =

[[chars]], cur_ind = [dec], tx_ind = [dec],
retry [dec]

CPUCTRL RX PDMA ring could not replace

the buffers. possible low buffer condition.

IBS from CPP packet Async FIFO full

IBS from CPP packet Async FIFO full.

IBS from CPP packet Async FIFO multiple

bits error

IBS from CPP packet Async FIFO multiple

bits error.

IBS from CPP packet length FIFO full

IBS from CPP packet length FIFO full.

IBS from CPP packet length FIFO multiple

bits error

IBS from CPP packet length FIFO multiple

bits error.

IBS from CPP packet FIFO 0 full

IBS from CPP packet FIFO 0 full.

IBS from CPP packet FIFO 0 multiple bits

error

IBS from CPP packet FIFO 0 multiple bits

error.

IBS from CPP packet FIFO 1 full

IBS from CPP packet FIFO 1 full.

IBS from CPP packet FIFO 1 multiple bits

error

IBS from CPP packet FIFO 1 multiple bits

error.

IBS from CPP packet FIFO 2 full

IBS from CPP packet FIFO 2 full.

IBS from CPP packet FIFO 2 multiple bits

error

IBS from CPP packet FIFO 2 multiple bits

error.

IBS from CPP packet FIFO 3 full

IBS from CPP packet FIFO 3 full.

IBS from CPP packet FIFO 3 multiple bits

error

IBS from CPP packet FIFO 3 multiple bits

error.

IBS from CPP to Tx DDR FIFO full

IBS from CPP to Tx DDR FIFO full.

IBS from CPP to Tx DDR FIFO parity error

IBS from CPP to Tx DDR FIFO parity error.

IBS from CPU async FIFO full

IBS from CPU async FIFO full.

IBS from CPU async FIFO multiple bits error IBS from CPU async FIFO multiple bits error.
IBS from CPP packet parity error

IBS from CPP packet parity error.

IBS from CPU packet length FIFO full

IBS from CPU packet length FIFO full.

IBS from CPU packet length FIFO multiple

bits error

IBS from CPU packet length FIFO multiple

bits error.

IBS from CPU packet FIFO 0 full

IBS from CPU packet FIFO 0 full.

IBS from CPU packet FIFO 0 multiple bits

error

IBS from CPU packet FIFO 0 multiple bits

error.

IBS from CPU packet FIFO 1 full

IBS from CPU packet FIFO 1 full.

IBS from CPU packet FIFO 1 multiple bits

error

IBS from CPU packet FIFO 1 multiple bits

error.

IBS from CPU packet FIFO 2 full

IBS from CPU packet FIFO 2 full.

IBS from CPU packet FIFO 2 multiple bits

error

IBS from CPU packet FIFO 2 multiple bits

error.

IBS from CPU packet FIFO 3 full

IBS from CPU packet FIFO 3 full.

IBS from CPU packet FIFO 3 multiple bits

error

IBS from CPU packet FIFO 3 multiple bits

error.

EBS To CPP HP FIFO full

Egress Buffer and Scheduling to CPP high

priority FIFO full.

EBS To CPP HP tail drop

Egress Buffer and Scheduling to CPP high

priority tail drop.

EBS To CPP LP FIFO full

Egress Buffer and Scheduling to CPP low

priority FIFO full.

EBS To CPP LP tail drop

Egress Buffer and Scheduling to CPP low

priority tail drop.

EBS RGMII FIFO full

EBS RGMII FIFO full.

EBS RGMII parity error

Fatal error: [chars]

EBS RGMII parity error.

NPUXBAR bridge has a fatal error.

No Active RSP detected in the system.

NPU Crossbar bridge FPGA detected that

there is no active RSP in the system,
linecard will reset itself.

CIB PCIe core error overrun

CIB PCIe core error overrun

CIB PCIe response FIFO multiple bits error.

PCIe response FIFO multiple bits error.

CIB PCIe Tx FIFO multiple bits error

CIB PCIe Tx FIFO multiple bits error.

CIB PCIe Tx interface FIFO multiple bits

error

CIB PCIe Tx interface FIFO multiple bits

error.

RxDDR 1875 to 200 FIFO 0 full

RxDDR 1875 to 200 FIFO 0 full.

RxDDR 1875 to 200 FIFO 0 parity error

RxDDR 1875 to 200 FIFO 0 parity error.

RxDDR 1875 to 200 FIFO 1 full

RxDDR 1875 to 200 FIFO 1 full.

RxDDR 1875 to 200 FIFO 1 parity error

RxDDR 1875 to 200 FIFO 1 parity error.

RxSPI align 16B module control bits

mismatch

RxSPI align 16B module control bits

mismatch.

RxSPI align 16B memory overflow

RxSPI align 16B memory overflow.

TxDDR 200 to 1875 FIFO 0 full

TxDDR 200 to 1875 FIFO 0 full.

TxDDR 200 to 1875 FIFO 0 parity error

TxDDR 200 to 1875 FIFO 0 parity error.

TxDDR 200 to 1875 FIFO 1 full

TxDDR 200 to 1875 FIFO 1 full.

TxDDR 200 to 1875 FIFO 1 parity error

TxDDR 200 to 1875 FIFO 1 parity error.

TxSPI async FIFO overflow

TxSPI async FIFO overflow.

IBS from CPP packet SPI error

IBS from CPP packet SPI error.

IBS from CPP packet SPI protocol error

IBS from CPP packet SPI protocol error.

IBS from CPP packet CRC error

IBS from CPP packet CRC error.

IBS from CPP packet length mismatch

IBS from CPP packet length mismatch.

EBS to CPP packet data multiple bits error

EBS to CPP packet data multiple bits error.

EBS to CPP high priority FIFO multiple bits

error

EBS to CPP high priority FIFO multiple bits

error.

EBS to CPP low priority FIFO multiple bits

error

EBS to CPP low priority FIFO multiple bits

error.

EBS to CPU packet data multiple bits error

EBS to CPU packet data multiple bits error.

EBS to CPU FIFO multiple bits error

EBS to CPU FIFO multiple bits error.

EBS To CPU FIFO full

Egress Buffer and Scheduling to CPU FIFO

full.

EBS from FIA CRC error

EBS from FIA CRC error.

EBS from FIA delm error

EBS from FIA delm error.

EBS from FIA header checksum error

EBS from FIA header checksum error.

EBS from FIA header error

EBS from FIA header error.

Local Bus parity error

Local Bus PARITY error.

Local Bus read operation timeout error

Local Bus read operation timeout error.

Local Bus write operation timeout error

Local Bus write operation timeout error.

CIB PCIe bad write address

Local Bus RSP0 parity error

CIB PCIe bad write address

Local Bus RSP0 parity error.

Local Bus RSP 1 parity error

Local Bus RSP 1 parity error.

RxSPI Calendar ECC multiple bits error

RxSPI DIP4 error

RxSPI Calendar ECC multiple bits error.

RxSPI DIP4 error.

RxSPI out of frame

RxSPI out of frame.

RxSPI Phy lost sync

RxSPI Phy lost sync.

RxSPI protocol burst error

RxSPI protocol burst error.

RxSPI protocol packet gap error

RxSPI protocol packet gap error.

RxSPI protocol sequence error

RxSPI protocol sequence error.

RxSPI protocol reserved control word error

RxSPI protocol reserved control word error.

TSP decoder A CRC error

TSP decoder A CRC error.

TSP decoder A frame error

TSP decoder A frame error.

TSP decoder A length error

TSP decoder A length error.

TSP decoder B CRC error

TSP decoder B CRC error.

TSP decoder B frame error

TSP decoder B frame error.

TSP decoder B length error

TSP decoder B length error.

TxSPI async FIFO high 72bits data multiple TxSPI async FIFO high 72bits data multiple
bits ECC error
bits ECC error.
TxSPI async FIFO low 72bits data multiple
bits ECC error

TxSPI async FIFO low 72bits data multiple

bits ECC error.

TxSPI staus bus frame error

TxSPI staus bus frame error.

TxSPI Calendar ECC multiple bits error

TxSPI staus bus DIP2 error

TxSPI Calendar ECC multiple bits error.

TxSPI staus bus DIP2 error.

TxSPI out of frame error

TxSPI out of frame error.

IBS from CPP packet Async FIFO single bit

error

IBS from CPP packet Async FIFO single bit

error.

IBS from CPP packet length FIFO single bit

error

IBS from CPP packet length FIFO single bit

error.

IBS from CPP packet FIFO 0 single bit error IBS from CPP packet FIFO 0 single bit error.
IBS from CPP packet FIFO 1 single bit error IBS from CPP packet FIFO 1 single bit error.
IBS from CPP packet FIFO 2 single bit error IBS from CPP packet FIFO 2 single bit error.
IBS from CPP packet FIFO 3 single bit error IBS from CPP packet FIFO 3 single bit error.
IBS from CPP packet too long error

IBS from CPP packet too long error.

IBS from CPP packet too short error

IBS from CPP packet too short error.

IBS from CPU async FIFO single bit error

IBS from CPU async FIFO single bit error.

IBS from CPU packet length FIFO single bit IBS from CPU packet length FIFO single bit
error
error.
IBS from CPU packet FIFO 0 single bit error IBS from CPU packet FIFO 0 single bit error.
IBS from CPU packet FIFO 1 single bit error IBS from CPU packet FIFO 1 single bit error.
IBS from CPU packet FIFO 2 single bit error IBS from CPU packet FIFO 2 single bit error.
IBS from CPU packet FIFO 3 single bit error IBS from CPU packet FIFO 3 single bit error.
IBS from CPP packet too long error

IBS from CPP packet too long error.

IBS from CPP packet too short error

Critical error: [chars]

IBS from CPP packet too short error.

NPUXBAR bridge has a critical error.

EBS to CPP packet data single bit error

EBS to CPP packet data single bit error.

EBS to CPP high priority FIFO single bit

error

EBS to CPP high priority FIFO single bit

error.

EBS to CPP low priority FIFO single bit error EBS to CPP low priority FIFO single bit error.
EBS to CPU packet data single bit error

EBS to CPU packet data single bit error.

EBS to CPU FIFO single bit error

EBS to CPU FIFO single bit error.

EBS To CPU HP tail drop

Egress Buffer and Scheduling to CPU high

priority tail drop.

EBS from FIA packet length mismatch error EBS from FIA packet length mismatch error.

EBS from FIA packet too long error

EBS from FIA packet too long error.

EBS from FIA packet too short error

EBS from FIA packet too short error.

CIB PCIe bad read address

CIB PCIe bad read address

CIB PCIe response FIFO single bit error

PCIe response FIFO single bit error

CIB PCIe Tx FIFO single bit error

CIB PCIe Tx FIFO single bit error.

CIB PCIe Tx interface FIFO single bit error

CIB PCIe Tx interface FIFO single bit error.

RxSPI Calendar ECC single bit error

RxSPI Calendar ECC single bit error.

TxSPI async FIFO high 72bits data single bit TxSPI async FIFO high 72bits data single bit
ECC error
ECC error.
TxSPI async FIFO low 72bits data single bit TxSPI async FIFO low 72bits data single bit
ECC error
ECC error.
TxSPI Calendar ECC single bit error

TxSPI Calendar ECC single bit error.

EBS To CPU LP tail drop

Minor error: [chars]

Egress Buffer and Scheduling to CPU low

priority tail drop.
NPUXBAR bridge has a minor error.

RxSPI protocol unexpected control word

error

RxSPI protocol unexpected control word

error.

RxSPI protocol end of packet abort

RxSPI protocol end of packet abort.

TSP decoder A disabled but packet

received

TSP decoder A disabled but packet

received.

TSP decoder A PWM error

TSP decoder A PWM error.

TSP decoder B disabled but packet

received

TSP decoder B disabled but packet

received.

TSP decoder B PWM error

TSP decoder B PWM error.

TSP GST timeout

TSP GST timeout.

TSP GST timer jump

TSP GST timer jump.

TSP TxDDR timeout

TSP TxDDR timeout.

TSP Tx DDR timer jump

TSP Tx DDR timer jump.

nV Edge data module: Shared mem corrupt

[hex] / [hex]\n Proceeding anyways
([dec])\n, recommended LC reload
Critical error, recommended LC reload

Interface [hex] has been uni directional

for\n 10 seconds, this might be a transient
condition if\n a card bootup / oir etc.. is
happening and will get\n corrected
automatically without any action. If its a\n
real error, then the IRL will not be available
fo\n forwarding inter-rack data and will be
missing in the\n output of show nv edge
This can be a transient condition or an
data forwarding cli
error.
INFO: More than [dec] IRLs configured, only
[dec] active IRLS will be used for
forwarding
Recommendation for better IRL resiliency
[dec] Inter Rack Links configured all on one
slot.\n Recommended to spread across at
least two slots\n for better resiliency\n
Recommendation for better IRL resiliency
[dec] Inter Rack Links configured on [dec]
slots.\n Recommended to spread across
maximum 5 slots\n for better
manageability and troubleshooting\n

Recommendation for better IRL resiliency

Only one Inter Rack Link is configured.\n

For Inter Rack Link resiliency,
recommendation is\n to have at least two
links spread across at least\n two slots\n

Recommendation for better IRL resiliency

OBFL PD diver error message: [chars]

An error happened during OBFL initilization

Format [chars] failed

This debug message indicates that format

device failed.

OBFL PD diver informational message:

[chars]

None

[chars]

Failure to create an OBFL record. This may

indicate a problem with the OBFL storage
device.

Could not create event manager for obfl

process. Error: [chars]
[chars]: [chars]
Malloc for -[dec] bytes failed

A event manager crreate failed.

Miscellaneous software error.
Memory allocation failed.

Sysdb registration for notification on path [chars] failed

Application faile to register for notification
Could not create thread. Error: [chars]

A thread could not be created.

Error, [chars]
[chars]: [chars]

Envmon encountered a software error.

software trace.

OIR: Node [chars] inserted\n

Detected a card is inserted into the

chassis.

OIR: Node [chars] removed\n

Detected a card is removed from the

chassis.

Failed to attach handler for async events:

[chars]

Failed to attach handler for async events.

Received unexpected message: [dec]

Received unexpected async message type.

Failed to perform checkpoint services:

[chars]

Failed to perform checkpoint service

functions.

Failed to create event manager: [chars]

Failed to create event manager.

Failed to map OIR registers to process

space

Failed to mmap OIR registers.

Failed to attach handler for sync events:

[chars]

Failed to attach handler for sync events.

Failed to connect to message channel:

[chars]

Failed to attach handler for sync messages.

Received unexpected message : [chars]

Received unexpected message.

Failed to create thread [chars]

Failed to create threads.

Failed to create timer: [chars]

Failed to create timer.

Failed to init timer events: [chars]

Failed to init timer events.

Unexpected: [chars]: [chars]

An unexpected condition encountered. This

is not necessarily an error, but may help
with debugging other problems elsewhere!

P40X0 DPAA fatal error: reason=[chars],

errno=[dec]

P40X0 datapath encountered a fatal error

and is not able to recover from the error. A
text reason and error number will be
supplied to describe the error.

P40X0 DPAA init error: reason=[chars]

P40X0 datapath encountered an

initialization error A reason text will be
supplied to describe the error.

P40X0 DPAA warning: [chars]

P40X0 datapath encountered an

provisioning warning.

Failed due to [chars] error [chars]

Initialization of fwdlib has failed.

[chars]: [chars]

PANINI SPP Initialization Error message.

Error Allocating <[dec]> bytes of memory

PANINI SPP Memory Allocation Error

message.

[chars]: [chars]

PANINI SPP Thread Error message.

[chars]: [hex]

PANINI SPP Pakman Abort message

received.

Performance Traffic Monitoring: Monitored

flows on NP [unsigned int] no longer at
maximum capacity

Performance traffic monitoring has cleared

an out-of-resource condition. Performance
traffic monitoring process on the linecard
has detected that the number of flows
being monitored on a NP is no longer at
maximum.

Performance Traffic Monitoring: Maximum

monitored flows ([unsigned int]) reached
on NP [unsigned int]

Performance traffic monitoring has

encountered an out-of-resource condition.
Performance traffic monitoring process on
the linecard has detected that the number
of flows being monitored on a NP has
reached maximum capacity. New flows will
no longer be learnt

Performance traffic service policy

verification failed, error [chars]: [chars]

Peformance traffic service policy

verification encountered the specified error

Failed to initialize the PCI/PCIe API TRACE

buffer: rc=[hex] ([chars])

The PCI/PCIe client was not able to initialize

the trace buffer. The message has more
details.

PCI Device : bus/device/function [dec]/

[dec]/[dec] - Link reset without release for
double fault

An access error happenned on Squirt or

PEX8114 while checking for errors.

An error has occurred on the switch port.

The message has the port identification,
PCIe Switch ([chars]): port [dec] - [chars] - the error register, and and the error
[chars]
description.

An error has occurred on the switch port.

The message has the port identification,
PCIe Switch ([chars]): port [dec] - [chars] - the error register, and and the error
[chars]
description.

A PCIe bus error has occurred. The

PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.

A PCIe bus error has occurred. The

PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.
A device has been detecting a PCIe bus
error and it is exceeding threshold. The
PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.

A device has been detecting a PCIe bus

error and it is exceeding threshold. The
PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.

The PCIe server has encountered an

additonal error on this device during error
PCI/PCIe Device: bus/device/function [dec]/ handling. The message contains the device
[dec]/[dec] - [chars]
identification and the error reason.

[chars] - [chars]

Critical Error in PCIE Operation

There was an error during PCIe server

Failed to initialize PCIe server: [chars] Error initialization phase. The error message has
code [hex] ([chars]).
detailed information.

A PCI bus error has occurred. The message

PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.

A PCI bus error has occurred. The message

PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.
A device has been detecting a PCI bus error
and it is exceeding threshold. The message
PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.

A device has been detecting a PCI bus error

and it is exceeding threshold. The message
PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.

Fabric Card [dec] PCIE enumeration error

detected.

A PCIE enumeration error was detected for

this Fabric Card. The error prevents this
card to do traffic switching thereby making
it unusable

A PCIe bus error has occurred. The

PCI/PCIe Device: bus/device/function [dec]/ message has the root device identification,
[dec]/[dec] - [chars]
error severity, and error type.
A root device has been detecting a PCIe
bus error and it is exceeding threshold. The
PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.

A PCIe bus error has occurred. The

PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.

A PCIe bus error has occurred. The

PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.
A device has been detecting a PCIe bus
error and it is exceeding threshold. The
PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.
A device has been detecting a PCIe bus
error and it is exceeding threshold. The
PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.

A PCI/PCIe bus error has occurred. The error

type is unknown. If the device indicated in
the message is the root port, the error
could be reported by any device in the root
PCI/PCIe Device: bus/device/function [dec]/ port's hierachy, or could be reported by the
[dec]/[dec] - [chars]
root port itself.

A PCI/PCIe bus error has occurred. The error

type is unknown. If the device indicated in
the message is the root port, the error
could be reported by any device in the root
PCI/PCIe Device: bus/device/function [dec]/ port's hierachy, or could be reported by the
[dec]/[dec] - [chars]
root port itself.

The PCIe server has encountered an error

on this device. The message contains the
PCI/PCIe Device: bus/device/function [dec]/ device identification and the error
[dec]/[dec] - [chars]
information.

[chars]

The PCIe server has detected an error

condition. The message has the error
information.

[chars]

The PCIe server has detected an error

condition. The message has the error
information.

[chars] - [chars]

Error in PCIE Operation

Failed to reset the PCIe link between

bus/device/function [dec]/[dec]/[dec] and
bus/device/function [dec]/[dec]/[dec]. Error
code [hex] ([chars]).
An attempt to reset the PCIe link has failed.

A PCI bus error has occurred. The message

PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.

A PCI bus error has occurred. The message

PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.
A device has been detecting a PCI bus error
and it is exceeding threshold. The message
PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.
A device has been detecting a PCI bus error
and it is exceeding threshold. The message
PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.

A PCIe bus error has occurred. The

PCI/PCIe Device: bus/device/function [dec]/ message has the root device identification,
[dec]/[dec] - [chars]
error severity, and error type.
A root device has been detecting a PCIe
bus error and it is exceeding threshold. The
PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.

A PCIe bus error has occurred. The

PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.

A PCIe bus error has occurred. The

PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.
A device has been detecting a PCIe bus
error and it is exceeding threshold. The
PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.
A device has been detecting a PCIe bus
error and it is exceeding threshold. The
PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.

A PCI bus error has occurred. The message

PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.

A PCI bus error has occurred. The message

PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.
A device has been detecting a PCI bus error
and it is exceeding threshold. The message
PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.
A device has been detecting a PCI bus error
and it is exceeding threshold. The message
PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.

A PCIe bus error has occurred. The

PCI/PCIe Device: bus/device/function [dec]/ message has the root device identification,
[dec]/[dec] - [chars]
error severity, and error type.
A root device has been detecting a PCIe
bus error and it is exceeding threshold. The
PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.

A PCIe bus error has occurred. The

PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.

A PCIe bus error has occurred. The

PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.
A device has been detecting a PCIe bus
error and it is exceeding threshold. The
PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.
A device has been detecting a PCIe bus
error and it is exceeding threshold. The
PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.

The PCIe link has been reset. This

corrective action is triggered by a fatal
error on the PCIe bus. The device driver will
usually participate in the effort of restoring
the device after the link reset. If this
message is not seen again and no other
The PCIe link between bus/device/function adverse effects are observed then it means
[dec]/[dec]/[dec] and bus/device/function that the link reset is successful. Otherwise,
[dec]/[dec]/[dec] has been reset.
take the following action, *SUPPORT*

A PCI bus error has occurred. The message

PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.

A PCI bus error has occurred. The message

PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.
A device has been detecting a PCI bus error
and it is exceeding threshold. The message
PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.
A device has been detecting a PCI bus error
and it is exceeding threshold. The message
PCI/PCIe Device: bus/device/function [dec]/ has the device identification, error severity,
[dec]/[dec] - [chars]
and error type.
A PCIe bus error has occurred on the root
port. The message has the root device
PCI/PCIe Device: bus/device/function [dec]/ identification, error severity, and error
[dec]/[dec] - [chars]
type.
A root device has been detecting a PCIe
bus error and it is exceeding threshold. The
PCI/PCIe Device: bus/device/function [dec]/ message has the device identification,
[dec]/[dec] - [chars]
error severity, and error type.
PCI/PCIe Device: bus/device/function [dec]/
[dec]/[dec] - [chars]
Device information message.

[chars] - [chars]

PCIE debug information

[chars]

This message describes the PCIe server

initialzation progress.

PCIE Root Complex 1 error detected.

A PCIE error detected in Root Complex 1

PCIE Root Complex 2 error detected.

A PCIE error detected in Root Complex 2

PCIE Fabric Card enumeration error

detected.

A PCIE enumeration error was detected for

this Fabric Card. The error prevents this
card to do traffic switching thereby making
it unusable

fatal s/w error encountered - [chars],

[chars], line [dec]

An unrecoverable fatal s/w error was

encountered, which resulted in process
restart. The exact cause is appended to the
error msg. Contact support with this
information.

pci bus manager mutex lock error: [chars]

The mutex lock for accessing register

returned error.

[chars]() line[dec]: pci bus manager mutex The mutex lock for accessing register
lock error
returned error

pci bus manager mutex unlock error:

[chars]

The mutex unlock for register operation

returned error

[chars]() line[dec]: pci bus manager mutex The mutex unlock for register operation
unlock error
returned error

[chars]() line[dec]: pci bus manager failed

register to platform mgr

The function call to

pm_fault_register_device returned fail

[chars]() line[dec]: pci bus manager failed

register to platform mgr

The function call to

pm_fault_register_device returned fail

[chars] [dec] [chars]

This message describes the PCI manger

process debug information. The message
has the error type and error description
which occured.

[chars] [hex]

This message describes the PCI manger

process debug information. The message
has the error description and status.

[chars] [dec] [dec]

This message describes the PCI manger

process debug information.

[chars] [hex] [hex]

This message describes the PCI manger

process debug information.

[chars] [hex] [chars] [hex] [chars] [hex]

[chars] [hex]

This message describes the PCI manger

device id, class id, vendor id etc debug
information.

[chars] [hex] [chars] [hex] [chars] [hex]

[chars] [hex] [chars] [hex]

This message describes the PCI manger

device, vendor, class, etc debug
information.

[chars] [dec]

This message describes the PCI manger

process debug information.

[chars] [hex]

This message describes the PCI manger

process debug information.

[chars] [pointer]

This message describes the PCI manger

process debug information.

[chars]

This message describes the PCI manger

process debug information.

[chars] [chars] [hex] [chars] [hex]

This message describes the PCI manger

process general debug information.

[chars] [hex] [chars] [hex]

This message describes the PCI manger

process memory and port debug
information. The message has the memory
start and map address.

[chars] [hex] [chars] [hex] [chars] [hex]

This message describes the PCI manger

config bridge and devefunction debug
information.

[chars][[dec]]= [hex]

This message describes the PCI manger

process debug information.

[chars] [chars] [hex] [chars] [hex] [chars]

[dec]

This message describes the PCI manger

process io operations debug information.

[chars] [chars]

This message describes the PCI manger

process debug information.

[chars] [chars] [hex]

This message describes the PCI manger

process debug information.

[chars] [chars] [chars]

This message describes the PCI manger

process debug information.

PCMCIA was not able to register iteslf as a

handler for PCMCIA related interrupts. This
could have happened because of failure in
Could not attach PCMCIA interrupt request setting the IRQ thread properties or failure
handler
in attaching to interrupt.

PCMCIA driver failed to attach to the PCI

device

PCI Device is either a CARDBUS Bridge or

PCI-PCMCIA Bridge. Here it cannot get PCI
device information from PCI bus manager.

PCMCIA Process can't locate PCI server

PCI must be attached before using any

other APIs. PCMCIA driver unable to attach
to PCI bus. PCI_SVR_ATTACH_FAIL occurs
when there is no PCI card.

HFR RP/DRP has 2 PCMCIA slots Create a

Memory mapping for all of I/O Port Space.
The device can be accessed through
address: Base address + port. The memory
mapping function here is actually mapping
PCMCIA driver failed mapping input output the Base address. Memory input output
memory address space
address mapping to pcmcia driver failed.

PCMCIA driver failed to register platform

manager

PM_FAULT_REGISTER_DEVICE registers a
device instance with the fault report API.
This step must be done before the device
driver may report faults. It should be done
at the init phase rather than when an error
occurs. When registration of device
instance failed, fault reports are not
logged.

PCMCIAD failed to start cardmgr with

reason: [chars]

PCMCIAD ws trying to start cardmgr

process but failed with specified reason

PCMCIAD failed to start due to the reason : PCMCIAD failed to come up due to the
[chars]
specified reason.

Signal operation [chars] failed: [chars]

Signal masking or handler installation

failed with the reason shown

kill to pid [dec] failed: [chars]

Probably the process being killed has

already exited

MsgSendPulse operation failed: [chars]

Failed to send pulse to resmgr thread to

handle SIGCHLD

pcmciad died and had come back up. It is

Pcmciad died and has come back up. Killing killing children spawned by old pcmciad so
its old children
that it can respawn new ones.

unlink of file [chars] failed: [chars]

PCMCIAD failed to unlink instance of child

file name shown

Failure to notify node state when [chars]

failed with error code [chars]

This message indicates that the internal

communication channel among pctl
threads is broken i.e. shelfmgr gsp
interaction for node down notifs failed.

Failure to notify node state when [chars]:

[chars]

The internal communication channel

among pctl threads is broken.

[chars]

PDMA SPP Initialization Error message.

Error Allocating <[dec]> bytes of memory

PDMA SPP dll Memory Allocation Error

message.

[chars]: [dec] [chars]

PDMA SPP Transmit over-sized packet drop.

[chars]: [chars]

PDMA SPP Thread Error message.

Packet dropped while injecting from CPU.

Code:[dec] Error reason: [chars]

Packet dropped while injecting from the

CPU of the affected card.

DMAC thread failed to listen for events with DMAC driver failed to listen for packet
error [chars]
events on its queue.

PEX : [chars] Error code [hex] ([chars]).

There was an fail during PEX (PCIE Switch)

driver configuration.The error message has
detailed information. Config fail will usually
result in process restart in an attempt to
configure the PCIE server.

PEX : [chars] Error code [hex] ([chars]).

There was an fail during PEX (PCIE Switch)

driver evnet loop entry.The error message
has detailed information. Entering into
Event loop fail will usually result in process
restart in an attempt to configure and PCIE
driver event loop entry.

Failed to initialize PEX driver: [chars] Error

code [hex] ([chars]).

There was an error during the PEX driver

intialization phase of trace buffer/event
manager creation/asic error lib dll/ fault
manager/platform DLL/interrupt service
routine/ system manager ready state. The
error message has detailed information.
Process initialization error will usually result
in process restart in an attempt to bring up
the process again.

PEX : [chars] Error code [hex] ([chars]).

There was an fail during translate of the

platform version. Plaform info version may
not be same as the driver, the error
message has detailed information. Version
translate fail will usually result in process
restart in an attempt to translate the
correct platform version.

PCIe bridge 8114: [chars] -[dec]- [chars]

An error has occurred on the bridge. The

message has the error register, bit location
and the error description.

link between PCIe bridge 8114 and root

port: [chars]

An error has occurred on the link between

the bridge and its root port. The message
has status and action taken.

PCIE device internal error

There was an internal failure reported by

the PCIE device

PCIE transaction timeout

PCIE transaction timeout

PCIE unsupported request

PCIE device reported an unsupported

request

Initialization error, Exiting. Reason: [[hex]]: The message can be displayed whenever
[chars]
there is a driver initialization error.

PCIE interrupts masked due to large errors PCIE interrupts masked due to large errors

Initialization error, Warning. Reason:

[chars]

The message can be displayed whenever

there is a driver initialization error.

PCIE device internal BIST error

There was a failure in built-in self-test of

PCIE device

PCIE device hardware strap error

PCIE device hardware strap error

PCIE link train failure

PCIE link train failure

PCIE device uncorrectable ECC error

PCIE device uncorrectable ECC error

PCIE device correctable ECC error

PCIE device correctable ECC error

Initialization error, Exiting. Reason: [[hex]]: The message can be displayed whenever
[chars]
there is a driver initialization error.

PCIE interrupts masked due to large errors PCIE interrupts masked due to large errors

Initialization error, Warning. Reason:

[chars]

The message can be displayed whenever

there is a driver initialization error.

Initialization error, Exiting. Reason: [[hex]]: The message can be displayed whenever
[chars]
there is a driver initialization error.

PCIE device internal BIST error

There was a failure in Built-in self test of

PCIE device

PCIE device hardware strap error

PCIE device hardware strap error

PCIE link train failure

PCIE link training failed

PCIE device uncorrectable ECC error

PCIE device uncorrectable ECC error

Initialization error, Warning. Reason:

[chars]

The message can be displayed whenever

there is a driver initialization error.

PCIE device correctable ECC error

PCIE device correctable ECC error

PCIE interrupts masked due to large errors PCIE interrupts masked due to large errors

Initialization error, Exiting. Reason: [[hex]]: The message can be displayed whenever
[chars]
there is a driver initialization error.

Initialization error, Warning. Reason:

[chars]

The message can be displayed whenever

there is a driver initialization error.

[chars]

The card reset was aborted because the

user has disabled card reset to allow
troubleshooting to be performed.

[chars]

Platform Fault Manager Node is performing

a card reset based on recovery action
defined in the Application Fault Condition
Database.

[chars]

The Grace Card Shutdown/Reset request

with the sysmgr timed out. Attempts to
perform a non-grace node reboot instead.

LC Reset: Reason - [chars]

Platform Fault Manager DLL received an

error from one of the LC devices. The LC
MUST be reset.

ProcName: [chars], ProcessId: [dec], Dev

Name: [chars] ([hex]), condName: [chars]
([dec]) is not raised after resync

Platform Fault Manager Node detected a db

inconsistency when performing a resync
with an application.

ProcName: [chars], ProcessId: [dec], Dev

Platform Fault Manager Node detected a db
Name: [chars] ([hex]) is not registered after inconsistency when performing a resync
resync
with an application.

ProcName: [chars], ProcessId: [dec] is not

registered after resync

Platform Fault Manager Node detected a db

inconsistency when performing a resync
with an application.

Not allowed for an Error sev fault: [chars]

Platform Fault Manager Node detects an

invalid Reset action defined in the
Application Fault Condition Database. An
fault of severity Error is not allowed to
perform a card reset recovery action.

Not allowed for an Error sev fault: [chars]

Platform Fault Manager Node detects an

invalid Reset action defined in the
Application Fault Condition Database. An
fault of severity Error is not allowed to
perform a chip reset recovery action.

Not Supported: [chars]

Platform Fault Manager Node detects an

invalid Reset action defined in the
Application Fault Condition Database.

DB internal error, reason = [chars]

Platform Fault Manager NFM encountered

an error due to internal software issue and
is not able recover from the error. A reason
text will be supplied call support with this
text.

Invalid Fault Severity: [chars]

Platform Fault Manager Node detects an

invalid fault severity defined in the
Application Fault Condition Database.

Lib internal error, reason = [chars]

Platform Fault Manager DLL encountered

an error due to internal software issue and
is not able recover from the error. A reason
text will be supplied call support with this
text.

Lib no more memory

Platform Fault Manager DLL was unable to

add a new fault condition due to lack of
memory. This condition will cause the DLL
to exit.

PFM Library can't sent any fault condition

to NFM, reason = [chars]

Platform Fault Manager DLL encountered

an error due to internal software issue and
is not able recover from the error. A reason
text will be supplied call support with this
text.

PFM Node internal error, reason = [chars]

Platform Fault Manager Node encountered

an error due to internal software issue and
is able recover from the error. A reason text
will be supplied call support with this text.

PFM Node internal error, reason = [chars]

Platform Fault Manager Node encountered

an error due to internal software issue and
is able recover from the error. A reason text
will be supplied call support with this text.

PFM Node internal error, reason = [chars]

Platform Fault Manager Node encountered

an error due to internal software issue and
is able recover from the error. A reason text
will be supplied call support with this text.

Sysdb initialization failed, reason: [dec]

([chars])

Sysdb initialization failed during PFM

process startup. This means that the card
reset disable feature may not work on this
node as per configuration.

Unknown Recovery action: [dec], [chars]

Platform Fault Manager Node detects an

invalid Reset action defined in the
Application Fault Condition Database.

[chars]

Useful general info logged by the Platform

Fault Manager that can used to establish a
sequence of events that occurred in the
system.

PFM Node Information: [chars]

Useful general info logged by the Platform

Fault Manager that can used to establish a
sequence of events that occurred in the
system.

[chars] [dec]

PLATFORM BMADJ, error information

[chars] [dec]

PLATFORM BMADJ, error information

[chars]: [chars] ([unsigned int])

PLATFORM BMADJ, error information

[chars]: [chars] ([unsigned int])

PLATFORM BMADJ, error information

[chars]

PLATFORM BMADJ, error

[chars]

PLATFORM BMADJ, error

[chars]

PLATFORM BMADJ, Information

[chars]: [chars]

PLATFORM BMADJ, Information

show_ver_info_init:
du_create_hw_info_type_node failed,
rc=[dec], reason: [chars].

Creating hw information of type as

motherboard, baseboard of node got failed.
Also publishing information to sysdb and
setting up of sysdb name for platform in hw
tree got failed.

Binding of sysdb to hw tree gets failed.

Also publishing information to sysdb and
show_ver_info_init: du_sysdb_hw_tree_bind setting up sysdb name for platform in hw
failed, rc=[dec], reason: [chars].
tree got failed.

Unbinding of sysdb to hw tree gets failed.

show_ver_info_init:
Also publishing information to sysdb and
du_sysdb_hw_tree_unbind failed, rc=[dec], setting up of sysdb name for platform in hw
reason: [chars].
tree got failed.

platform_discovery_packet_init:
packet_region_define failed, rc=[dec],
reason: [chars].

Define particle pools over memory regions.

If there is not enough space to hold all the
particles, less particles will be created.
Each pool can have its own particle size.
Unable to define the packet in the
mentioned pool types.

platform_discovery_packet_init:
packet_send_init_info failed, rc=[dec],
reason: [chars].

Passing of necessary parameters like

packet size, number of packets, etc to the
packet initialisation process got failed.

Define particle pools over memory regions.

If there is not enough space to hold all the
platform_discovery_packet_init:
particles, less particles will be created.
particle_multi_pool_define failed (big pool), Each pool can have its own particle size.
rc=[dec], reason: [chars].
Particle defined as Big pool got failed.

platform_discovery_packet_init:
particle_multi_pool_define failed (giant
pool), rc=[dec], reason: [chars].

Define particle pools over memory regions.

If there is not enough space to hold all the
particles, less particles will be created.
Each pool can have its own particle size.
Particle defined as Giant pool got failed.

platform_discovery_packet_init:
particle_multi_pool_define failed (huge
pool), rc=[dec], reason: [chars].

Define particle pools over memory regions.

If there is not enough space to hold all the
particles, less particles will be created.
Each pool can have its own particle size.
Particle defined as Huge pool got failed.

platform_discovery_packet_init:
particle_multi_pool_define failed (large
pool), rc=[dec], reason: [chars].

Define particle pools over memory regions.

If there is not enough space to hold all the
particles, less particles will be created.
Each pool can have its own particle size.
Particle defined as Large pool got failed.

platform_discovery_packet_init:
particle_multi_pool_define failed (medium
pool), rc=[dec], reason: [chars].

Define particle pools over memory regions.

If there is not enough space to hold all the
particles, less particles will be created.
Each pool can have its own particle size.
Particle defined as Medium pool got failed.

platform_discovery_packet_init:
particle_multi_pool_define failed (qnet
pool), rc=[dec], reason: [chars].

Define particle pools over memory regions.

If there is not enough space to hold all the
particles, less particles will be created.
Each pool can have its own particle size.
Particle defined as Qnet pool got failed.

platform_discovery_packet_init:
particle_multi_pool_define failed (small
pool), rc=[dec], reason: [chars].

Define particle pools over memory regions.

If there is not enough space to hold all the
particles, less particles will be created.
Each pool can have its own particle size.
Particle defined as Small pool got failed.

Define particle pools over memory regions.

If there is not enough space to hold all the
platform_discovery_packet_init:
particles, less particles will be created.
particle_multi_pool_define failed (tiny pool), Each pool can have its own particle size.
rc=[dec], reason: [chars].
Particle defined as Tiny pool got failed.

platform_discovery_packet_init: Unable to
identify the board type, hence unable to
define the SMALL_POOL size as per SPP
requirements

Equating the Small Pool size to the SPP

context size plus rewrite space (which
totally equates to 1080) for Satori cards
only as the small pool is used as a fallback
pool for SPP. Here it unable to identify the
board type, hence unable to define the
SMALL_POOL size as per SPP requiremnets.

Find out physical memory information from

SYSPAGE. If more memory is found than
our defined minimum
MIN_RESERVED_MEM, then a scaling factor
platform_discovery_packet_init:
is created to scale the number of packets,
platform_get_reserved_physmem(pakman) particles, etc, upward.Here reservation of
failed
physical memory got failed.

main: show_ver_info_init: [chars] (rc =

[dec])

Publishing platform information to sysdb. If

it fails to publish the information it displays
this error.

Find out physical memory information from

SYSPAGE. If more memory is found than
our defined minimum
MIN_RESERVED_MEM, then a scaling factor
is created to scale the number of packets,
platform_discovery_packet_init: pak mem particles, etc, upward. Packet memory
size: [hex], pak mem start: 0x[pointer],pak information like size, starting, scaling are
scaling : [dec]
shown

[chars] [dec]

PLATFORM FIB EA, error information

[chars]: [chars] ([unsigned int])

PLATFORM FIB, error information

[chars]

PLATFORM FIB EA, error

PLATFORM FIB EA INIT FAILURE : [chars]

An initialization failure occurred in FIB EA

layer. The message string indicates the
reason for the failure. Here is a list of
possible reasons for this message (not allinclusive). - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects.

A runtime failure occurred in FIB EA layer.

Typically, this is an invalid object passed to
the functions. The message string indicates
the reason for the failure. Here is a list of
possible reasons for this message (not allinclusive). - Invalid objects. This condition
indicates a problem where the object being
PLATFORM FIB EA INVALID OBJECT : [chars] processed by the software is invalid.

PLATFORM FIB EA MEMORY FAILURE :

[chars]

Memory allocation failure occurred in FIB

EA layer. The message string indicates the
reason for the failure. Here is a list of
possible reasons for this message (not allinclusive). - Failed to allocate memory. This
condition indicates a problem with the
memory allocation.

PLATFORM FIB EA PROGRAM FAILURE

[chars]: [chars] ([unsigned int])

A runtime failure occurred in FIB EA layer.

Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
get MD5 router ID. This condition indicates
a problem with the software on the card. Failed to send message to x86. This
condition indicates a problem with sending
message from XR to x86. - Failed to
program router ID. This condition indicates
a problem with the programming router ID.

[chars]

PLATFORM FIB EA, Information

Interface Details : [chars]

PLATFORM FIB EA, Information

[chars] [dec]

PLATFORM FIB, error information

[chars]: [chars] ([unsigned int])

PLATFORM FIB, error information

[chars]

PLATFORM FIB, error

[chars]

PLATFORM FIB, Information

[chars] [hex]

PLATFORM FIB, Information

[chars] [dec]

PLATFORM FIB, error information

[chars] [dec]

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars] [dec]

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars]: [chars] ([unsigned int])

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars]: [chars] ([unsigned int])

PLATFORM FIB, error information

[chars]: [chars] ([unsigned int])

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars]

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars]

PLATFORM FIB, error

[chars]

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars] [hex]

This is an information message in the

ASR9K platform IP FRR FIB specific code
software. The message is for debug
purposes only and not an error.

[chars]

PLATFORM FIB, Information

[chars]

This is an information message in the

ASR9K platform FIB specific code software.
The message is for debug purposes only
and not an error.

[chars] [hex], [chars] [dec], [chars]([dec])

PLATFORM FIB, error information

[chars] [dec]

PLATFORM FIB HAL, error information

[chars] [dec]

PLATFORM FIB, error information

[chars] [hex]

PLATFORM FIB, error information

[chars] [hex]

PLATFORM FIB HAL, feature not supported

[chars] [dec]

PLATFORM FIB, error information

[chars] [dec]

PLATFORM FIB HAL, error information

[chars]: [chars] ([unsigned int])

PLATFORM FIB, error information

[chars]: [chars] ([unsigned int])

PLATFORM FIB HAL, error information

[chars]: [chars] ([unsigned int])

PLATFORM FIB, error information

[chars]: [chars] ([unsigned int])

PLATFORM FIB HAL, error information

[chars]

PLATFORM FIB, error

[chars]

PLATFORM FIB HAL, error

[chars]

PLATFORM FIB, error

[chars]

PLATFORM FIB HAL, error

[chars]

PLATFORM FIB HAL, Information

[chars]
[chars]

PLATFORM FIB, Information

PLATFORM FIB, Critical error

[chars] [dec]

PLATFORM FIB, Critical error information

PLATFORM FIB MPLS ACCESS FAILURE:

[chars] [unsigned int]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen.

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
PLATFORM FIB MPLS ACCESS FAILURE STR : software on the card where the error is
[chars] [chars] ([hex])
seen.

PLATFORM FIB MPLS ACTION FALIURE:

[chars] [unsigned int]

A runtime failure occurred in FIB engine

layer. Typically, this is an registration error.
The message string indicates the reason
for the failure. This message also provides
an error code. Here is a list of possible
reasons for this message (not all-inclusive).
- Failed to register gtrie. This condition
indicates a problem where the gtrie
registration processed by the software is
failed.

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. It also provides a more verbose
information. Here is a list of possible
reasons for this message (not all-inclusive).
- Failed to alloc vclabel stats. This condition
indicates a problem with the software on
PLATFORM FIB MPLS ERROR DETAIL :
the card. Typically, this occurs when the
[chars] [hex], [chars] [dec], [chars] ([dec]) software failed to alloc vclabel stats.

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to program TX Adj. This
condition indicates a problem with the
software while programming TX Adj. Failed to program RX Adj. This condition
PLATFORM FIB MPLS ACTION FAILURE STR : indicates a problem with the software while
[chars] [chars] ([hex])
programming RX Adj.

[chars] [hex], [chars] [dec], [chars]([dec])

PLATFORM FIB, error information

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. It also provides a more verbose
information. Here is a list of possible
reasons for this message (not all-inclusive).
- Failed to retrieve information from FIB
objects. This condition indicates a problem
with the software on the card where the
error is seen. - Failed to initialize objects.
This condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
[chars] [hex], [chars] [dec], [chars] ([dec]) is invalid.

[chars] [dec]

PLATFORM FIB, error information

PLATFORM FIB-MPLS: Error: [chars] [dec]

[chars] [dec]

This error indicates a problem with the

software on programming the hardware.
This typically occurs when there is a
problem with the resource utilization in the
card where the error is seen. Here is a list
of possible reasons for this message. Invalid objects. This condition indicates a
problem where the object being processed
by the software is invalid. - Resource
limitations. This condition indicates a
problem where the software has limited
resources to operate on.
PLATFORM FIB, error information

[chars] [unsigned int]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars] [hex]

PLATFORM FIB, error information

[chars] [hex]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code (in hex). Here is a list of possible
reasons for this message (not all-inclusive).
- Failed to retrieve information from FIB
objects. This condition indicates a problem
with the software on the card where the
error is seen. - Failed to initialize objects.
This condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

PLATFORM FIB-MPLS: Error: [chars]

This error indicates a problem with the

software on programming the hardware.
This typically occurs when there is a
problem with the resource utilization in the
card where the error is seen. Here is a list
of possible reasons for this message. Invalid objects. This condition indicates a
problem where the object being processed
by the software is invalid. - Resource
limitations. This condition indicates a
problem where the software has limited
resources to operate on.

PLATFORM FIB-MPLS: Init. Error: [chars]

[hex]

A runtime error occurred in FIB MPLS.

Typically, this is an error where the
software fails during initialization. Here is a
list of possible reasons for this message
(not all-inclusive). - Failed to initialize
software. This condition indicates a
problem with the software on the card
where the error is seen. Typically, this
occurs when the software tries to initialize
invalid objects. - Invalid objects. This
condition indicates a problem where the
object being processed by the software is
invalid during initialization. - Failed to
program forwarding features. This
condition indicates a problem where the
software fails to program forwarding
features to the hardware during
initialization/ configuration. - Resource
limitations. This condition indicates a
problem where the software has limited
resources to operate on.

PLATFORM IPV4-EA: Init. Error: [chars]

A runtime error occurred in FIB MPLS.

Typically, this is an error where the
software fails during initialization. Here is a
list of possible reasons for this message
(not all-inclusive). - Failed to initialize
software. This condition indicates a
problem with the software on the card
where the error is seen. Typically, this
occurs when the software tries to initialize
invalid objects. - Invalid objects. This
condition indicates a problem where the
object being processed by the software is
invalid during initialization. - Failed to
program forwarding features. This
condition indicates a problem where the
software fails to program forwarding
features to the hardware during
initialization/ configuration. - Resource
limitations. This condition indicates a
problem where the software has limited
resources to operate on.

A runtime error occurred in FIB MPLS.

Typically, this is an error where the memory
allocation / access fails. Here is a list of
possible reasons for this message (not allinclusive). 1) Memory exhaustion due to
overall system load 2) Shared memory
PLATFORM FIB-MPLS: Memory Error: [chars] access failure 3) Memory leaks leading to
[hex]
resource exhaustion

A runtime error occurred in FIB MPLS.

Typically, this is an error where the memory
allocation / access fails. Here is a list of
possible reasons for this message (not allinclusive). 1) Memory exhaustion due to
overall system load 2) Shared memory
access failure 3) Memory leaks leading to
PLATFORM FIB-MPLS: Memory Error: [chars] resource exhaustion

[chars] [chars]([dec])
[chars] [chars]([dec])

PLATFORM FIB, error information

PLATFORM FIB, error information

[chars] [chars] ([hex])

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]
[chars]

PLATFORM FIB, error

PLATFORM FIB, error

[chars]

This error indicates a problem with the

software on programming the hardware.
This typically occurs when there is a
problem with the resource utilization in the
card where the error is seen. Here is a list
of possible reasons for this message. Invalid objects. This condition indicates a
problem where the object being processed
by the software is invalid. - Resource
limitations. This condition indicates a
problem where the software has limited
resources to operate on.

[chars]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

PLATFORM FIB MPLS INIT FALIURE: [chars]

[unsigned int]

A runtime failure occurred in FIB engine

layer. Typically, this is an initialization error.
The message string indicates the reason
for the failure. This message also provides
an error code. Here is a list of possible
reasons for this message (not all-inclusive).
- Failed to initialize debug. This condition
indicates a problem where the debug init
processed by the software is failed. - Failed
to initialize ltrace. This condition indicates
a problem where the ltrace init processed
by the software is failed. - Failed to
initialize p2mp frr timer. This condition
indicates a problem where the p2mp frr
timer init processed by the software is
failed.

PLATFORM FIB MPLS INIT FAILURE STR :

[chars] [chars] ([hex])

A runtime failure occurred in FIB engine

layer. Typically, this is an initialization error.
The message string indicates the reason
for the failure. This message also provides
an error code. Here is a list of possible
reasons for this message (not all-inclusive).
- Failed to initialize debug. This condition
indicates a problem where the debug init
processed by the software is failed. - Failed
to initialize ltrace. This condition indicates
a problem where the ltrace init processed
by the software is failed. - Failed to
initialize p2mp frr timer. This condition
indicates a problem where the p2mp frr
timer init processed by the software is
failed.

PLATFORM FIB MPLS INVALID ACTION :

[chars] [unsigned int]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Invalid
Leaf Action. This condition indicates a
problem where the fib action being
processed by the software is invalid. Failed to retrieve information from FIB
objects. This condition indicates a problem
with the software on the card where the
error is seen. - Failed to initialize objects.
This condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

PLATFORM FIB MPLS INVALID OBJECT:

[chars] [unsigned int]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Invalid
objects. This condition indicates a problem
where the object being processed by the
software is invalid.

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Invalid
objects. This condition indicates a problem
PLATFORM FIB MPLS INVALID OBJECT STR : where the object being processed by the
[chars] [chars] ([hex])
software is invalid.

PLATFORM FIB MPLS INVALID RANGE :

[chars] :[dec]

A runtime failure occurred in FIB engine

layer. Typically, this is a boundary error.
The message string indicates the reason
for the failure. Here is a list of possible
reasons for this message (not all-inclusive).
- Out of supported range. This condition
indicates the value is not in allowed range.

Shared memory [chars], window: [dec]

[hex] [chars]
[chars]
[chars] [dec]
[chars]

PLATFORM
PLATFORM
PLATFORM
PLATFORM

PLATFORM-FIB-RP: Error - [chars] [dec]

PLATFORM FIB, error information

PLATFORM-FIB-RP: Error - [chars] [dec]

PLATFORM FIB, error information

PLATFORM-FIB-RP: Error - [chars] [chars]

[chars] [dec]

PLATFORM FIB, error information

PLATFORM-FIB-RP: Error - [chars] [chars]

[chars] [dec]
PLATFORM-FIB-RP: Error - [chars]
PLATFORM-FIB-RP: Error - [chars]

PLATFORM FIB, error information

PLATFORM FIB, error
PLATFORM FIB, error

CEF has crossed [dec] routes hardware

limit. Please delete routes immediately to
prevent CEF from blocking new routes to
hardware

CEF on the node has detected that the

number of routes has exceeded prescribed
limits. Any further increase could cause
CEF to block the routes from being
programmed in hardware.

FIB,
FIB,
FIB,
FIB,

Shared memory errors

Warning
Warning information
Information

CEF exceeded limits and route updates to

hardware are now blocked. Please delete
routes in the system immediately to
recover

CEF on the node has detected that the

number of routes has exceeded prescribed
limits and route updates to the hardware
have been blocked.

CEF has unblocked route updates to

hardware. Please ensure route limits are
not crossed

CEF on the node had earlier detected that

the number of routes had exceeded
prescribed limits and route updates to the
hardware had been blocked. It has now
been unblocked.

[chars] [chars] [chars] Error [chars]([dec])

The error indicates failure in connecting the

channel.

Function [chars] failed with:[chars] status:

[dec]

The error occurs,if sending message to the

server gets failed.

[chars] [dec]

PLATFORM FIB, error information

[chars] [dec]

PLATFORM FIB, error information

[chars] [dec]

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars] [hex]

PLATFORM FIB, error information

[chars] [unsigned int]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars] [dec]

PLATFORM FIB, INIT error information

[chars] [dec]

PLATFORM FIB, feature not supported

[chars] [hex]

PLATFORM FIB, operational error

information

[chars] [hex]

PLATFORM FIB, PRM error information

[chars] [hex]

PLATFORM FIB, error information

[chars] [dec]

PLATFORM FIB, error information

[chars] [unsigned int]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars] [dec]

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars] [hex]

PLATFORM FIB, show fail error information

[chars]: [chars] ([hex])

PLATFORM FIB, error information

[chars]: [chars] ([unsigned int])

PLATFORM FIB, error information

[chars]: [chars] ([unsigned int])

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]: [chars] ([unsigned int])

PLATFORM FIB, error information

[chars]: [chars] ([unsigned int])

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars]: [chars] ([hex])

PLATFORM FIB, INIT error information

[chars]: [chars] ([unsigned int])

PLATFORM FIB, expected error information

in case of transition between CDSTV/CDSIS
and CGV6 roles on an ISM LineCard.

[chars]: [chars] ([unsigned int])

PLATFORM FIB, error information

[chars]: [chars] ([hex])

PLATFORM FIB, error information

[chars]: [chars] ([unsigned int])

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars]: [chars] ([unsigned int])

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]: [chars] ([hex])

PLATFORM FIB, Access error information

[chars]: [chars] ([hex])

PLATFORM FIB, PRM error information

[chars]

PLATFORM FIB, error

[chars]

PLATFORM FIB, error

[chars]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card. - Failed to initialize
objects. This condition indicates a problem
with the software on the card where the
error is seen. Typically, this occurs when
the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]

PLATFORM FIB, error

[chars]

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars]

PLATFORM FIB, error

[chars]

PLATFORM FIB, error

[chars] [dec] Err:[chars] ([hex])

PLATFORM FIB, error information

[chars]

PLATFORM FIB, INIT error

[chars]

PLATFORM FIB, feature not supported

[chars]

PLATFORM FIB, operational error

information

[chars]

PLATFORM FIB, error

[chars]

PLATFORM FIB, error

[chars]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars]

PLATFORM FIB, show fail error

[chars]

PLATFORM FIB, show fail error information

[chars] [unsigned int]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]: [chars] ([unsigned int])

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars] [dec]

The error indicates the entered buffer size

is not valid.

PLATFORM_FIB MEMORY FAILURE : [chars]

Failed to allocate memory.This error

condition indicates a problem with the
memory allocation.

[chars] [chars] [chars]

The error occurs,if the provided source or

destination ip address is invalid.

[chars] : [chars]

The error indicates that the entered

command format is not proper.

[chars]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card. - Failed to initialize
objects. This condition indicates a problem
with the software on the card where the
error is seen. Typically, this occurs when
the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

[chars]: [chars] ([unsigned int])

PLATFORM FIB, expected error information

in case of transition between CGV6 and
CDSTV/CDSIS roles on an ISM LineCard.

[chars]: [chars] ([unsigned int])

A runtime failure occurred in FIB engine

layer. Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. Here is a list of possible reasons for
this message (not all-inclusive). - Failed to
retrieve information from FIB objects. This
condition indicates a problem with the
software on the card where the error is
seen. - Failed to initialize objects. This
condition indicates a problem with the
software on the card. Typically, this occurs
when the software tries to initialize invalid
objects. - Unexpected events. This
condition indicates a problem where an
event is triggered in the software
unexpectedly on the card. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid.

ysdb_datalist failed: dlist_count= [dec],

dlist=[hex] rc=[hex] Err:[chars] subpath
[chars]\n

This error message occurs because of the

failure while extracting the data from the
database.

[chars] [chars]

The error occurs if the binding or iteration

of the data list in the system database
fails.

FIB_PLATFORM Warning [chars]

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

FIB_PLATFORM Invalid/Uninitialized
Warning:[chars] ErrorCode:[dec]

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

FIB-PLATFORM Warning:[chars] ErrCode:

[dec]

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
FIB-PLATFORM API-context Warning:[chars] situation, so is unlikely to re-occur.

Un-initialized/Invalid [chars]:
Warning[chars] Error:([unsigned int])

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

FIB-PLATFORM [chars]: Warning:[chars]

([unsigned int])

This is an error message in the ASR9K

platform FIB specific code software to
indicate anomolies that are not FATAL. This
error is most likely caused by a temporary
situation, so is unlikely to re-occur.

[chars] not supported on interface

<<CH[hex]>>. Please remove the config.

If a configuration involving an unsupported

protocol is committed under a GRE tunnel
interface, this message will be generated.
The forwarding chain will also be
programmed to drop packets of the
unsupported protocol type resolving over
the GRE tunnel.

[chars] not supported on interface

<<CH[hex]>>. Please remove the config.

If a configuration involving an unsupported

protocol is committed under a GRE tunnel
interface, this message will be generated.
The forwarding chain will also be
programmed to drop packets of the
unsupported protocol type resolving over
the GRE tunnel.

Backup NH: [hex] [TE NH: [hex]] for

Protected interface: [hex] is detected
A backup of the listed protected interface is
incomplete, can cause potential traffic loss found incomplete. This can cause potential
during FRR
traffic loss during FRR.

Protected interface: [hex] and Bkup

tunnel's [hex] underlying interface: [hex]
are same

FRR will not work as Bkup tunnel's

underlying interface is same as the
protected interface.

LFA FRR is not supported for IPv6 when the

protected or backup path is hosted on a
non-Taiko line card. However, LFA FRR may
The non-MSC-140G node [chars] does not still work if the protected and backup paths
support IPv6 LFA FRR, FRR guarantees may are hosted on different line cards, but FRR
not be fulfilled
traffic loss times are not guaranteed.

[chars]

PLATFORM FIB, warning

[chars] [hex]

PLATFORM FIB, Information

[chars] [hex]

IP FRR PLATFORM FIB, Information

This is an information message in the

ASR9K platform IP FRR FIB specific code
Fast-Reroute INFO [chars] [hex] IP FRR Info software. The message is for debug
message
purposes only and not an error.
[chars] [hex]

IP FRR PLATFORM FIB, Information

[chars] [hex]

This is an information message in the

ASR9K platform IP FRR FIB specific code
software. The message is for debug
purposes only and not an error.

[chars] [hex]

This message provides information about

the IP FRR events happening in the
software at the location where the error is
seen. This is not an error message.
Typically, following events are logged in
this message type. - End of successfull
initialization of the software. - Start and
end of a processing of new object that
needs to programmed to the hardware.

[chars] [hex]

This message provides information about

the IP FRR events happening in the
software at the location where the error is
seen. This is not an error message.
Typically, following events are logged in
this message type. - End of successfull
initialization of the software. - Start and
end of a processing of new object that
needs to programmed to the hardware.

[chars]

PLATFORM FIB, Information

[chars]

PLATFORM FIB, Information

API context Info:[chars]

This is an information message in the

ASR9K platform FIB specific code software.
The message is for debug purposes only
and not an error.

[chars]

This message provides information about

the kind of events happening in the
software at the location where the error is
seen. This is not an error message.
Typically, following events are logged in
this message type. - End of successfull
initialization of the software. - Start and
end of a processing of new object that
needs to programmed to the hardware.

[chars]

PLATFORM FIB, info

[chars]

This is an information message in the

ASR9K platform FIB specific code software.
The message is for debug purposes only
and not an error.

This message provides information about

the kind of events happening in the
software at the location where the error is
seen. This is not an error message.
Typically, following events are logged in
this message type. - End of successfull
initialization of the software. - Start and
end of a processing of new object that
needs to programmed to the hardware.
NP[dec]: [unsigned long int]([unsigned long http://wikicentral.cisco.com/display/PROJEC
int])
T/CGv6-ISM-TSG-FAQ
[chars]

PLATFORM FIB, Information

[chars]

PLATFORM FIB, Information

[chars]

PLATFORM FIB, Information

'Details: [chars]'

Print the data for debug purpose or for

change of states

[chars] curr_ver:[dec] new_ver:[dec]

PLATFORM FIB, Information

[chars] : [chars] ([dec])

Failed to initialize the debugging module in

the platform ICPE EA component.

[chars] : [chars] ([dec])

Failed to initialize the debugging module in

the platform ICPE EA component.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the the platform ICPE EA

LTRACE component.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the the platform IFO EA

LTRACE component.

Nv satellite interface provisioning on

Interchassis Link(ifhandle [hex]) failed.
Limit is 1 ICL per NP per satellite when
using bundled ICLs for that satellite. A
different satellite can still have a member
link on the same NP

An internal error has been encountered and

nv satellite ethernet interface cannot be
provisioned.

Nv satellite interface provisioning on

Interchassis Link(ifhandle [hex]) failed.
Limit is 1 ICL per NP per satellite when
using bundled ICLs for that satellite. A
different satellite can still have a member
link on the same NP

An internal error has been encountered and

nv satellite ethernet interface cannot be
provisioned.

[chars] : [chars] ([dec])

Failed to initialize the cerrno module in the

platform ICPE_EA component.

[chars] : [chars] ([dec])

Failed to initialize the cerrno module in the

platform ICPE_EA component.

[chars] : [chars] ([dec])

Failed to initialize the LC hardware in the

platform ICPE_EA component.

[chars] : [chars] ([dec])

Failed to initialize the LC hardware in the

platform ICPE_EA component.

Per ICL access port scale limit exceeded

Exceeded ICL Access Port scale limit, np:
and no further access ports can be
[dec], np_port: [dec], max_supported: [dec] provisioned on this ICL

Exceeded per LC Access Port scale limit,

max_supported: [dec]

Per LC access port scale limit exceeded and

no further access ports can be provisioned
on this LC

Exceeded per LC Satellite scale limit,

max_supported: [dec]

Per LC satellite scale limit exceeded and no

further satellites can be provisioned on this
LC.

Per NP access port scale limit exceeded

Exceeded per NP Access Port scale limit, np and no further access ports can be
: [dec], max_supported: [dec]
provisioned on this NP

Exceeded per NP Satellite scale limit, np:

[dec], max_supported: [dec]

Per NP satellite scale limit exceeded and no

further satellites can be provisioned on this
NP.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the debugging module in

the platform L2FIB ATOM component.

Platform ATOM initialization [chars]

Failed to initialize the platform L2FIB ATOM

component.

[chars] [dec]: [chars] ([dec])

Failed to initialize the ltrace module in the

platform L2FIB ATOM component.

PLATFORM-L2FIB-ATOM: Error - [chars]

[chars] [chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB ATOM component.

PLATFORM-L2FIB-ATOM: Error - [chars]

Failed to initialize the ATOM module in the

platform L2FIB ATOM component.

PLATFORM-L2FIB-ATOM: Error - [chars]

[dec] [chars] [dec]

Failed to initialize the ltrace module in the

platform L2FIB ATOM component.

PLATFORM-L2FIB-BRIDGING: Error - [chars] Failed to delete bridge in the platform

[dec] [dec]
L2FIB BRIDGING component.
PLATFORM-L2FIB-BRIDGING: Error - [chars] Failed to initialize the debugging module in
[chars] [chars] [dec]
the platform L2FIB BRIDGING component.

MAC count mismatch during enqueueing

MAC record of shm_total_count: [dec]
mac_list_index: [dec] mac_count: [dec] :
brg_ctx:0x[pointer] mac_ctx:0x[pointer]
seq#: [dec] TID: [dec] mac_ctx_state: [dec] While enqueueing MAC record in MAC list,
entry_in_hw:% d macstr: [chars]
index is out of bound in the array.
PLATFORM-L2FIB-BRIDGING: Error - [chars] Failed to initialize the Platform LC Hardware
[chars] [chars] [dec]
in L2FIB BRIDGING component.
Failed to initialize the Bridging module in
PLATFORM-L2FIB-BRIDGING: Error - [chars] the platform L2FIB BRIDGING component.
Ignoring elem type : [dec] offset: [dec]

Ignoring incoming chunk element has this

is not expected type

Invalid next avaliable [chars] offset: [dec]

Next avaliable free tcam MAC offset is not

valid

Invalid MAC offset# [dec] While setting

bitlist in MAC region with size: [dec] total
unicast: [dec]next unicast offset: [dec] next Received an invalid MAC offset while
default offset: [dec] current offset: [dec]
setting mac bitlist datastructure
PLATFORM-L2FIB-BRIDGING: Error - [chars] Failed to initialize the ltrace module in the
[dec] [chars] [dec]
platform L2FIB BRIDGING component.
Error unused unicast entry exists for
macregion size: [dec] total unicast entries:
[dec] total default entries: [dec] next
unicast offset: [dec] next default offset:
[dec]
TCAM MAC chunk database is out of sync

MAC count mismatch after

restart/reprogram mac_walk_count: [dec]
shm_total_mac:[dec]

Total MAC count is not matching between

share memory and l2fib walk count.

PLATFORM-L2FIB-BRIDGING: Error - [chars] Failed to initialize the PFI-IFH module in the

[chars] [chars] [dec]
platform L2FIB BRIDGING component.
Redundant MAC create ignored !! bid :
[dec] mac:[chars] seq#:[dec]

Redundant mac create update for already

created MAC object in Bridging.

attempting to set existing offset type: [dec] MAC offset currently being set is already in
offset: [dec]
use
mac region size: [dec] total unicast entries:
[dec] total default entries: [dec] next
unicast offset: [dec] current offset: [dec]
unicast chunk pointer: [pointer] chunk used Maximum allowed MAC entry count is
count: [dec] - chunk overrun attempted
reached in the TCAM MAC chunk
PLATFORM-L2FIB-BRIDGING: Error - [chars] Failure in MAC tcam region management in
[chars] [chars] [dec]
Platform LC L2FIB BRIDGING component.
PLATFORM-L2FIB: Error - [chars] [chars]
[chars] [dec]

Failed to create the Platform LC Hardware

in L2FIB component.

PLATFORM-L2FIB: Error - [chars] [chars]

[hex]

Failed to Attaching event timer to the L2FIB

PD component.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the debugging module in

the platform L2FIB component.

PLATFORM-L2FIB: Error - [chars] [chars]

[chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB component.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the debugging module in

the platform L2FIB L2TP component.

Platform L2TP initialization [chars]

Failed to initialize the platform L2FIB L2TP

component.

[chars] [dec]: [chars] ([dec])

Failed to initialize the ltrace module in the

platform L2FIB L2TP component.

PLATFORM-L2FIB-L2TP: Error - [chars]

[chars] [chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB L2TP component.

PLATFORM-L2FIB-L2TP: Error - [chars]

Failed to initialize the L2TP module in the

platform L2FIB L2TP component.

PLATFORM-L2FIB-L2TP: Error - [chars] [dec] Failed to initialize the ltrace module in the
[chars] [dec]
platform L2FIB L2TP component.

[chars] [chars] [chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB LOCSW component.

Platform LOCSW initialization [chars]

Failed to initialize the platform L2FIB

LOCSW component.

[chars] [dec] [chars] [dec]

Failed to initialize the ltrace module in the

platform L2FIB LOCSW component.

[chars] [chars] [chars] [dec]

Failed to initialize the PFI-IFH module in the

platform L2FIB LOCSW component.

PLATFORM-L2FIB-LOCSW: Error - [chars]

[chars] [chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB LOCSW component.

PLATFORM-L2FIB-LOCSW: Error - [chars]

Failed to initialize the LOCSW module in the

platform L2FIB LOCSW component.

PLATFORM-L2FIB-LOCSW: Error - [chars]

[dec] [chars] [dec]

Failed to initialize the ltrace module in the

platform L2FIB LOCSW component.

PLATFORM-L2FIB-LOCSW: Error - [chars]

[chars] [chars] [dec]

Failed to initialize the PFI-IFH module in the

platform L2FIB LOCSW component.

[chars] [dec] - [chars]: [chars] ([dec])

Failed to initialize the the platform L2FIB

LTRACE component.

PLATFORM-L2FIB: Ltrace Error - [chars]

[dec] [chars] [chars] [dec]

PLATFORM L2FIB, error information

The resynchronization of the MAC address

table is complete [chars]

The command to resynchronize the MAC

address table may take a while to
complete. This message indicates that
resynchronization is complete and the MAC
address table can be displayed..

The resynchronization of the MAC address

table is complete [chars]

The command to resynchronize the MAC

address table may take a while to
complete. This message indicates that
resynchronization is complete and the MAC
address table can be displayed..

object type: [chars] context is null in

[chars] context

Object context does not contain required

parent/child context.

L2FIB Metro L3QinQ failed to initialize

correctly. Without L2FIB Metro L3QinQ init,
[chars] (error: [chars]). L2FIB Metro L3QinQ can not configure L3QinQ vlan
initialization failed!
subinterfaces.

[chars] (error: [chars])

L2FIB Metro L3 QinQ entries programming

in TCAM failed. The hardware and software
entries will be out of sync.

[chars] Error:[chars]([dec])

Failed to initialize the Platform LC Hardware

in L2FIB component.

Oject type: [chars] context is null in [chars] object context does not contain required
context
parent/child context.

[chars] Error:[chars]([dec])

Failed to initialize the Platform LC Hardware

in L2FIB component.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the debugging module in

the platform L2FIB component.

[chars] [dec] - [chars]: [chars] ([dec])

Failed to initialize the the platform L2FIB

LTRACE component.

[chars] Error: [chars] [dec]

Failed to reset btree shared memory

function ptr. This is a software
programming error.

PLATFORM-L2FIB: Error - [chars] [chars]

[chars] [dec]

Failed to initialize the cerrno module in the

platform L2FIB component.

PLATFORM-L2FIB-RP: Error - [chars] [chars] Failed to initialize the debugging module in

[chars] [dec]
the platform L2FIB (D)RP component.

Failed to initialize the module in the

platform L2FIB (D)RP component.This will
PLATFORM-L2FIB-RP: Error - [chars] [chars] not affect the forwarding component as it is
Error:[chars] [dec]
in DRP.
PLATFORM-L2FIB: Error - [chars] [chars]
[chars] [dec]

Failed to initialize the ltrace module in the

platform L2FIB component.

node_count [dec] > alloc count [dec], xid

[hex]

Incoming bridge XID count is more than

allocated XID count.This may occur to due
to a programming error.

Failed to init Platform L2FIB (D)RP [chars]

debug module.Error-[chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB (D)RP component.

[chars] [hex]

VPLS HW MAC is enabled but Metro

resource is configured in BD.

Failed to init Platform L2FIB (D)RP [dec]

ltrace module.Error:[chars] [dec]

Failed to initialize the ltrace module in the

platform L2FIB (D)RP component.

The L2VPN software timed out waiting for

the following event[chars]

The L2VPN software was waiting for the

specified event to occur, but never
received it. The software has recovered and
L2VPN forwarding should not be affected.
This error will only occur on the active RP
on startup or on the newly active RP after
RP failover.

PLATFORM-L2FIB-SNOOP: Error - [chars]

[chars] [dec]

Failed to initialize the IGMP Snooping

module in the platform L2FIB SNOOP
component.

[chars]: [chars] ([hex])

Failed to enqueue PRM async request.

Automatic retry is under way. With a large
scale configuration using
MSTP/MSTAG/.8032, the error may become
persistent. In that case, line card reload
may be needed to recover from error
condition.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the debugging module in

the platform L2FIB VPLS component.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the IMC module in the

platform L2FIB VPLS component.

Platform VPLS initialization [chars]

Failed to initialize the platform L2FIB VPLS

component.

[chars] - [dec]: [chars] ([dec])

Failed to initialize the ltrace module in the

platform L2FIB VPLS component.

[chars] [chars] [chars] [chars] [dec]

PLATFORM L2FIB, error

[chars]: [chars] ([hex])

Attempt to add NP entry that already

exists.

[chars]: [chars] ([hex])

Attempt to delete NP entry that does not

exist.

[chars]: [chars] ([hex])

NP entry exceeded the maximum number

of resources available.

Initialization Error: [chars] [chars] [dec]

Encountered an initialization error for avsm

l2fib.

[chars]: [chars] ([hex])

PRM error occurred.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the cerrno module in the

platform L2FIB component.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the debugging module in

the platform L2FIB component.

[chars]: [chars] ([hex])

Attempt to add NP entry that already

exists.

[chars]: [chars] ([hex])

Attempt to delete NP entry that does not

exist.

[chars] [chars]: [chars] ([dec])

Failed to initialize the LC hardware in the

platform L2FIB component.

[chars]: [chars] ([hex])

Failed to initialize the LC hardware in the

platform L2FIB trident component.

avsm l2fib: [chars]

This is to print process initialisation

messages.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the ltrace module in the

platform L2FIB component.

PLATFORM-L2FIB: Error - [chars] [chars]

[chars] [dec]

Failed to initialize the cerrno module in the

platform L2FIB component.

PLATFORM-L2FIB: Error - [chars] [chars]

[chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB component.

PLATFORM-L2FIB: Error - [chars] [chars]

[chars] [dec]

Failed to initialize the Platform LC Hardware

in L2FIB component.

PLATFORM-L2FIB: Error - [chars] [chars]

[chars] [dec]

Failed to initialize the ltrace module in the

platform L2FIB component.

PLATFORM-L2FIB: Error - [chars] [chars]

[hex] [hex] [hex] [hex]

Received NHOP MODIFY to change rx/tx

TLU address in the platform L2FIB
component.

PLATFORM-L2FIB: Error - [chars] [chars]

[dec]

Failed to register with PFI infra in the

platform L2FIB component.

PLATFORM-L2VPN: Error - [chars] [chars]

[dec]

Failed to initialize the debugging module in

the platform L2VPN component.

Error - [chars] [dec] [chars] [dec]

Failed to allocate FGID for bridge broadcast

doamin.

[chars] Err_str :[chars] [dec]

Failed to initialize the module in the

platform L2VPN component.

Error - [chars] [dec]

Failed to allocate memory from heap.

Error - [chars] [dec]

Failed to reclaim FGID's that were allocated

to bridge domain.

Error - [chars] [dec]

Fgid reallocation timer init has failed.

Failed to init Platform L2VPN debug

module.Error- [chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB (D)RP component.

Failed to init Platform L2VPN ltrace module. Failed to initialize the ltrace module in the
Error: [chars] [dec]
platform L2FIB (D)RP component.

[chars]: [chars] ([dec])

Failed to initialize the module in the

platform L2VPN component.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the ltrace module in the

platform L2VPN component.

Failure to [chars] for [chars]

The specified timer failed to start.

PLATFORM-L2VPN: Ltrace Error - [chars]

[chars] [chars] [dec]

PLATFORM L2VPN, error information

Error - [chars] [dec] [dec]

Failed to extract nodeid to rsi value.

[chars] [dec]

PLATFORM MCAST, error information

[chars] [dec]

PLATFORM MCAST, error information

[chars]: [chars] ([unsigned int])

PLATFORM MCAST, error information

[chars]: [chars] ([unsigned int])

PLATFORM MCAST, error information

[chars]

PLATFORM MCAST, error

[chars]

PLATFORM MCAST, error

[chars]

PLATFORM MCAST, Information

[chars] [chars] [chars] [chars] ([chars],

[chars],[dec])

PLATFORM MCAST, Information

[chars] : [chars] ([dec])

Failed to initialize the debugging module in

the platform NVSAT EA component.

[chars] - [chars]: [chars] ([dec])

Failed to initialize the the platform NVSAT

EA LTRACE component.

Nv satellite interface provisioning on

Interchassis Link(ifhandle [hex]) failed.
Limit is 1 ICL per NP per satellite when
using bundled ICLs for that satellite. A
different satellite can still have a member
link on the same NP

An internal error has been encountered and

nv satellite ethernet interface cannot be
provisioned.

[chars] : [chars] ([dec])

Failed to initialize the cerrno module in the

platform NVSAT_EA component.

[chars] : [chars] ([dec])

Failed to initialize the LC hardware in the

platform NVSAT_EA component.

PLATFORM-THOR-L2FIB-ATOM: Initilization
Warning - [chars] [chars] [chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB ATOM component.

PLATFORM-THOR-L2FIB-ATOM:Init Warning - Failed to initialize the ATOM module in the

[chars]
platform L2FIB ATOM component.
PLATFORM-THOR-L2FIB-ATOM: Warning [chars] [dec] [chars] [dec]

Failed to initialize the ltrace module in the

platform L2FIB ATOM component.

PLATFORM-THOR-L2FIB: Warning - [chars]

[chars] [chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB component.

PLATFORM-THOR-L2FIB-LOCSW: Warning [chars] [chars] [chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB LOCSW component.

PLATFORM-THOR-L2FIB-LOCSW: Warning [chars]

Failed to initialize the LOCSW module in the

platform L2FIB LOCSW component.

PLATFORM-THOR-L2FIB-LOCSW: Warning [chars] [dec] [chars] [dec]

Failed to initialize the ltrace module in the

platform L2FIB LOCSW component.

PLATFORM-THOR-L2FIB-LOCSW: Warning [chars] [chars] [chars] [dec]

Failed to initialize the PFI-IFH module in the

platform L2FIB LOCSW component.

PLATFORM-THOR-L2FIB: HW init Ltrace

Warning - [chars] [dec] [chars] [chars]
[dec]

PLATFORM THOR L2FIB, error information

PLATFORM-THOR-L2FIB-MLD: Error - [chars] Failed to initialize MLD module

PLATFORM-THOR-L2FIB: Warng:[chars]
Failed to initialize the cerrno module in the
Error:[chars] err_str:[chars] return_val:[dec] platform L2FIB component.
PLATFORM-THOR-L2FIB-VPLS:Warng:[chars] Failed to initialize the debugging module in
Error:[chars] err_str[chars] return_val:[dec] the platform L2FIB VPLS component.
PLATFORM-THOR-L2FIB-VPLS:HW Detection Failed to initialize the VPLS module in the
Warning - [chars]
platform L2FIB VPLS component.
PLATFORM-THOR-L2FIB-VPLS:Warng:[chars] Failed to initialize the ltrace module in the
Error:[dec] err_str:[chars] return_val:[dec] platform L2FIB VPLS component.
PLATFORM-THOR-L2FIB: Memory Warning - Failed to initialize the cerrno module in the
[chars] [chars] [chars] [dec]
platform L2FIB component.
PLATFORM-THOR-L2FIB: Warning - [chars]
[chars] [chars] [dec]

Failed to initialize the debugging module in

the platform L2FIB component.

PLATFORM-THOR-L2FIB: Hardware init

Warning - [chars] [chars] [chars] [dec]

Failed to initialize the Platform LC Hardware

in L2FIB component.

PLATFORM-THOR-L2FIB: Warning - [chars]

[chars] [chars] [dec]

Failed to initialize the ltrace module in the

platform L2FIB component.

Exiting because [chars], error code

[chars]\n
PLATFORM-FIB-IPV6: [chars] [dec]
PLATFORM-FIB-IPV6: [chars] [dec]

The ASR9k License sync process exited due

to a fatal error. Check the error string to
determine what has happened.
Platform IPv6 FIB, Error information
Platform IPv6 FIB, Error information

PLATFORM-FIB-IPV6: [chars] [chars] [chars]

[dec]
Platform IPv6 FIB, Error information

PLATFORM-FIB-IPV6: [chars] [chars] [chars]

[hex]
Platform IPv6 FIB, Error information
PLATFORM-FIB-IPV6: [chars]
Platform IPv6 FIB, Error
PLATFORM-FIB-IPV6: [chars]
Platform IPv6 FIB, Error

Error in [chars] \n

Unable to find the physical port for the

given IFH

Failed in [chars], error code [chars]([dec])\n Unable to obtain VQI.

Error failure in [chars], error code [chars]

([dec])\n

Unable to obtain a micro-interface

descriptor block index.

The platform library service call to bind to

Failed to bind to system database module. system database module has failed. The
Reason: [chars].
calling application handles it appropriately.

Failed to cache file contents rc=[dec]

The platform library service call to failed to

cache the file contents of the Board's EMT
file

Failed to retrieve svd platform

configuration. Reason: [chars].

The platform library service call to find the

config tuple for svd platform enable has
failed. The calling application handles it
appropriately.

Failed to detect hardware board type.

Reason: [chars].

The platform library service call to find the

hardware module type has failed. The
calling application handles it appropriately.

Cant read Magic in packet header

This message tells is there was an error in

reading the magic number.

Cant trim cluster NP header in the packet

header

This message tells is there was an error in

trimming the cluster header from the
packet.

Error trimming the HDR from packet

This message tells is there was an error in

trimming the header from the packet.

NULL header after unscrambling

This message tells is there was an error

after unscrambling the packet and a NULL
pointer has been returned.

Failure to add L2 Header RC : [dec]

This message tells is there was an error in

adding the L2 header by SPP.

Error trace Init failed : [chars]

This message tells is the ltrace initialization

for error traces has failed and prints the
error string.

Event trace Init failed : [chars]

This message tells is the ltrace initialization

for event traces has failed and prints the
error string.

Failed to connect the node : [hex] \n

This message signifies that the DLL can not

longer receive any event messages from
the platform process in the router.

Failed to get nodeid of the current card \n

This message signifies that the DLL can not

longer receive any event messages from
the platform process in the router.

This message signifies that the

communication between that the eventcreation manager has failed in context with
Event handler NULL, EVM creation failed \n the Smart-Call-Home feature.

This message signifies that the DLL can not

Event Message Attach failure in the Smart- longer receive any event messages from
Call-Home DLL \n
the platform process in the router.
[chars]: pakman_reserve_start = [dec], size Critical information related to physical
= [dec]\n
memory start and size is displayed

[chars]: publish_mib_sys_object_id failed

for chassis type [dec]\n

An error occurred in platform

component,the reason for the error mib
system object id failed for the particular
chassis type.

[chars]: driver_inv_shmem_create: [chars]

(rc = [dec])\n

An error occurred in platform

component,during shared memory creation

[chars]: show_ver_info_init: [chars] (rc =

[dec])\n

An error occurred in platform

component,during version info initialization

An error occurred in platform

component,the reason for the error is
[chars]: [chars], rc=[dec],reason: [chars]\n updated in the error message.

An error occurred in platform

[chars]:
component,due to
platform_get_reserved_physmem(pakman) platform_get_reserved_physmem function
failed\n
invocation failed
[chars]: pak mem size: [hex], pak mem
start: [pointer] pak scaling : [dec]\n

Information related to physical memory

start size and memory size is displayed.

Failed to detect hardware board type.

Reason: [chars].

The platform library service call to find the

hardware module type has failed. The
calling application handles it appropriately.

Failed to detect Node [chars] card type.

Reason: [chars].

The platform library service call to find the

remote node card type has failed. The
calling application handles it appropriately.

PRP encounters a fatal Nirvana FPGA event: The PRP FPGA Manager gets a fatal Nirvana
[hex], vmon shutdown reg: [hex]
FPGA event, and requests board reload.

PRP encounters a fatal ZenJF FPGA event:

[hex], error capture reg: [hex]

The PRP FPGA Manager gets a fatal ZenJF

FPGA event, and requests board reload.

Node reset initiated by PID: [dec]

The FPGA Manager api for resetting the

board via a control register has been called
by the process with the specified PID.

The FPGA Manager api for resetting the

board via a control register has been called
Node reset initiated by PID: [dec] ( [chars] ) by the process with the specified PID.

Node reset initiated by PID: [dec]

The FPGA Manager api for resetting the

board via a control register has been called
by the process with the specified PID.

Node reset initiated by PID: [dec]

The FPGA Manager api for resetting the

board via a control register has been called
by the process with the specified PID.

catastrophic error with id=[dec]: error

id=[dec] msg:[chars]

PLDMGR client reports a catastrophic error

with error id.

FPD_EN set failed. Please check JTAG_SEL

dip switch configuration. [hex]

The FPD process failed due to software

unable to set FPD_EN bit.

Unable to initialize interrupt handler

thread: interrupt=[dec], errno=[dec]

PLDMGR encountered an error while

attempting to initialize the interrupt
handling thread. This means that interrupts
will not be serviced by PLDMGR until the
process is restarted.

Unable to initialize ltrace buffer [chars]

(error: [chars])

A fault occurred while registering the

mentioned ltrace buffer. This means that
system logging capabilities for the pldmgr
library component will be inoperable.

Unable to allocate memory for ltrace

decode array :[chars]

During ltrace decode, the decode function

retrieves file names, which must be placed
into a dynamically allocated array. If the
allocation calls fail this warning is printed
with the specific error from the system
based on the return code of the allocation
call.

Unable to allocate memory for ltrace

decode array at line [dec]: [chars]

During ltrace decode, the decode function

retrieves file names, which must be placed
into a dynamically allocated array. If the
allocation calls fail this warning is printed
with the specific error from the system
based on the return code of the allocation
call.

Error initializing PD lib [dec]

An error occurred when loading the PD

library for a specific platform's dll for
device access, causing the process to
return unexpectedly.

Could not init ltrace buffer

Due to an error in the ltrace initialization

routines, the init failed. This may be due to
other problems on the system (is ltrace
running?).

This board does not support console

tunneling.

There is a hardware issue and MCU is not

accepting configuration which prevents the
support of console tunneling feature.

The process was unable to map and

configure a shared memory window,
Error while mapping and configuring shared causing the process to return unexpectedly.
memory [dec]
Debugs will provide more info

ignorable warning event with id=[dec]: err PLDMGR client reports an ignorable
id=[dec] msg:[chars]
warning with error id, and description.

[chars]: [chars]

The server process encountered an error

while attempting to initialize a debug
event. This means that additional verbosity
will not be available via the 'debug pldmgr
enable' command in IOS-XR.

External USB fault detected. Check USB

device for failure.

The PRP detects a over-current condition on

external USB port and it is disabled the
port.

Unable to initialize ltrace buffer [chars]

(error: [chars])

A fault occurred while registering the

mentioned ltrace buffer. This means that
system logging capabilities for the pldmgr
library component will be inoperable.

Unable to allocate memory for ltrace

decode array : [chars]

During ltrace decode, the decode function

retrieves file names, which must be placed
into a dynamically allocated array. If the
allocation calls fail this warning is printed
with the specific error from the system
based on the return code of the allocation
call.

MCU is down-rev, upgrade MCU to support To support console tunneling, MCU

console tunneling.
firmware must be at v5 or higher.

No Framer/RAC devices are generating

excessive interrupts

The previously reported excessive

interrupts condition has been cleared.
Interrupt rate limiting has been disabled.

Excessive interrupts from the [chars]

device of port [hex]

The specified device is generating

excessive interrupts. This message
indicates that we are rate limiting the
interrupt coming from this device. This
indicates a potential HW issue, traffic
forwarding (protection switching) may be
impacted.

Initialization of PLIM driver failed: [chars] :

rc = [chars] ; exiting...

PLIM driver encountered the annunciated

error during the driver initialization. The
System Manager process (sysmgr) will
automatically respawn the (plim_16p_oc48)
process, up to a fixed number of times the
error is encountered, to recover. If the
problem continues, sysmgr will trigger
node reload. After a certain number of
node reloads, the shelf manager will
permanently shutdown the node.

Error: [chars] [chars] [hex]

A generic error is occurred in

plim_16p_oc48 PLIM driver. Cause of the
error will be mentioned in the message
displayed. This message is for debugging
purposes.

[chars] : rc = [chars]

PLIM driver failed to obtain either its node

ID or extract rack/slot/instance information
(having obtained the node ID).

Info: [chars] [chars] [hex]

The message is used to report generic info.

Optic Interface Module [chars] for port

[dec]

The Optic Interface Module (OIM) for the

specified port has either been inserted or
removed.

[chars]: [hex], [chars]

An error occurred in plim ipc api module

which could involve failure to transport ipc
messages between host and intelligent
PLIM. Features configured may not work.
%x - indicates where/what error occurred
%s - why the error occurred

[chars]: [hex], [chars]

An error occurred in plim ipc module which

could involve failure to transport ipc
messages between host and intelligent
PLIM. %x - indicates where/what error
occurred %s - why the error occurred

[chars]: [hex], [chars]

An error occurred in PLIM IPC module

during initialization which will restart the
process in order to recover. %x - indicates
where/what error occurred %s - why the
error occurred

[chars]: [hex], [chars]

An event occurred in plim ipc module which

could involve state of PLIM or PPC. %x, %s indicates where/what event occurred

An error occurred in creating/accessing

shared memory between Bambi server &
MANS FPGA server. This error could result
in communication loss between MSC and
Bambi reset fails due to error [chars] [hex] Services PLIM.

[chars] [hex]

An error in boot parameters reception

occurred in Services PLIM. Cause of the
error will be mentioned in the message
displayed. This error blocks Application
Launch on Services PLIM.

Boot param update in MANS SEEPROM

failed due to error : [chars] [hex]

An error in boot parameters reception

occurred in Services PLIM. Cause of the
error will be mentioned in the message
displayed. This error blocks Application
Launch on Services PLIM.

Initialization of the EDM server failed. It is

Plim services EDM initialization fails due to not service impacting error but could
error [chars] [hex]
impact MANS registers access via GASPP.

[chars] [hex]

Initialization of the EDM server failed. It is

not service impacting error but could
impact TEJAS registers access via GASPP.

[chars] [hex]

An error occurred in the event loop. Cause

of the error will be mentioned in the
message displayed. The error could result
in Brahmos PLIM driver process to be in
inconsistent state.

[chars] [hex]

The requested operation could not be

accomplished because of a low memory
condition. This error could impact
Linux/Application image download and
Launch, Services PLIM IPC (Inter Process
Communication) etc.

[chars] [hex]

An error occurred in initialization of PLIM

Services driver. If this occurred during
process startup or RP Switchover, then the
process may be restarted.

[chars] [hex]

Error occured while uprading the uboot

image. Cause of the error will be
mentioned in the message displayed. The
upgrade of uboot image will fail and could
lead the card to be in inconsistent state.

An error occurred in the event loop. Cause

of the error will be mentioned in the
message displayed. The error could result
Plim services may not behave properly due in Roddick PLIM driver process to be in
to error [chars] [hex]
inconsistent state.

[chars] [hex]

An error occurred in READ/WRITE to flash

memory. Exact Cause of the error will be
mentioned in the message displayed. This
error will block Application image launch

[chars] [hex]

Heartbeat failure notification from NPUS

was received by the Services PLIM driver or
a critical error occured in the thread
monitoring heartbeat from NPUS.

Octeon heartbeat failure heppened due to

error [chars] [hex]

Heartbeat failure notification from octeons

was received by the Services PLIM driver or
a critical error occured in the thread
monitoring heartbeat from octeons.

[chars] [hex]

An error occurred in downloading

Linux/Application image. Cause of the error
will be mentioned in the message
displayed. This error prevents Services
PLIM from coming up to its full functional
Active state.

Linux/Application image download is not

successful because [chars] [hex]

An error occurred in downloading

Linux/Application image. Cause of the error
will be mentioned in the message
displayed. This error prevents Services
PLIM from coming up to its full functional
Active state.

[chars] [hex]

An error occurred in launching

Linux/Application image. Cause of the error
will be mentioned in the message
displayed. This error prevents Services
PLIM from coming up to its full functional
Active state.

Linux/Application launch failed because

[chars] [hex]

An error occurred in launching

Linux/Application image. Cause of the error
will be mentioned in the message
displayed. This error prevents Services
PLIM from coming up to its full functional
Active state.

MANS FPGA SquidNet register access fails

due to error [chars] [hex]

An error occurred in read/write access of a

mans fpga device register. This error could
result in communication loss between MSC
and Services PLIM.

An error occurred in MANS initialization.

This means that MANS is currently in
Factory mode and this will cause the
MANS FPGA initialization failed due to error Services PLIM driver initialization to get
[chars] [hex]
blocked.

MANS FPGA octeon memory access

unsuccessful because [chars] [hex]

An error occurred in read/write from/to

octeon memory of a mans fpga device
register. This error could result in
communication loss between MSC and
Services PLIM.

Memory allocation failed [chars] [hex]

The requested operation could not be

accomplished because of a low memory
condition. This error could impact
Linux/Application image download and
Launch, Services PLIM IPC (Inter Process
Communication) etc.

Services PLIM will FAIL because [chars]

Services role configured. without this card

will never come up.

Plim services initialization failed due to

error [chars] [hex]

An error occurred in initialization of PLIM

Services driver. If this occurred during
process startup or RP Switchover, then the
process may be restarted.

PLIM STATE CONSUMER INIT ERROR :

[chars]

An error occurred in during ens

initialization. This could lead to plim_state
not published to XR world.

Services PLIM will not come to OK state

because [chars]

An error occurred while configuring

serviceInfra configuration. Cause of the
error will be mentioned in the message
displayed. This error will prevent launching
application in services PLIM and won't let it
come to UP state.

[chars] [hex]

An error occurred in read/write access of a

tejas fpga device register. This error could
result in communication loss between MSC
and Services PLIM.

[chars] [hex]

An error occurred in TEJAS GASPP register

access. Cause of the error will be
mentioned in the message displayed. This
error means that communication between
Services PLIM and MSC could be affected.

[chars] [hex]

An error occurred in Tejas initialization. This

means that Tejas is currently in Factory
mode and this will cause the Services PLIM
driver initialization to get blocked.

UART port access will fail due to error

[chars] [hex]

An error occurred in UART READ/WRITE

access to octeon memory. Exact Cause of
the error will be mentioned in the message
displayed. This error causes
Linux/Application image download and
launch to fail.

[chars] [hex]

An error occurred in UART READ/WRITE

access to NPU memory. Exact Cause of the
error will be mentioned in the message
displayed. This error causes
Linux/Application image download and
launch to fail.

Error occured while uprading the uboot

image. Cause of the error will be
mentioned in the message displayed. The
Uboot upgrade will fail due to error [chars] upgrade of uboot image will fail and could
[hex]
lead the card to be in inconsistent state.
Info: [chars]

The message is used to report cold reboot

of Services PLIM.

Info: [chars]

Ports consumed have fallen below 90%

threshold for this particular IP. Details will
be given in the meesage displayed

[chars]

Ports consumed have exceeded 90%

threshold for this particular IP. Details will
be given in the meesage displayed

Info: [chars]

Sessions active have fallen below 90%

threshold for this Details will be given in
the meesage displayed

[chars]

Sessions have exceeded 90% threshold

Details will be given in the meesage
displayed

[chars] [hex]

A generic error occurred in Services PLIM

driver. Cause of the error will be mentioned
in the message displayed.

Info: [chars]

The message is used to report generic info

about Services PLIM driver.

[chars] [hex]

A generic error occurred in Tile Manager.

Cause of the error will be mentioned in the
message displayed.

Info: [chars]

The message is used to report generic info

regarding tile Finite state machine.

[chars] [hex]

HA related error occurred in Services PLIM

driver. Cause of the error will be mentioned
in the message displayed.

Info: [chars]

The message is used to report info

regarding Tejas gaspp register access

[chars] failed: [chars]

The PLIM FPD upgrade is failed due to an

internal software problem. %s - indicates
the stage where the failure happens. %s indicates the reason for the the failure.

Hardware Table [dec] Initialisation failed

A particular table failed to initialise. This is

typically due to incorrect parameters
supplied when initialising the table. Any
traffic on that table is impacted.

Errors occured in the HW TBM tables have

been auto corrected. No action needs to be
Hardware Table [dec] consistency restored taken. This is informational message.

Errors were encountered trying to program

hardware tables, forwarding on some
Hardware Table [dec] may be inconsistent. entries may be affected, periodic error
Attempting correction every [dec] seconds correction will be attempted.

Hardware Table [dec] memory failures

corrected with compaction

A particular table had persistent memory

failures due to heavily fragmented
fragmented memory. As a last resort we
attempted an aggressive memory recovery
technique which succeeded. This is an
informational message.

Hardware Table [dec] memory failures

corrected with FORCED compaction

A particular table had persistent memory

failures due to heavily fragmented memory.
This error was unrecoverable by normal
compaction mechanism. As a last resort we
attempted an FORCED memory recovery
technique which succeeded. This is an
informational message.

Un-able to initialise PTMM Process [chars]

An error was encountered while initialising

the PLU/TLU memory manager This can
occur during: 1. Event Manager Creation 2.
Debug Initialization

Process [chars]: [chars]

An error was encountered while initialising

the PLU/TLU memory manager This
condition can occur during: 1. Memory init
2. Checkpoint Init 3. PLU/TLU specific Init 4.
EDM Init

Failed to initialise Server Process([chars])

Error([chars])

An error was encountered while trying to

initialise the Server Process The error can
occur in two conditions. 1. During global
HAL layer initialization 2. During TLU HAL
Layer initialization

An error was encountered while trying to

Failed to restart forwarding on the linecard restart forwarding on the linecard

Failed to initialise ltrace buffers

An error was encountered while initialising

the PLU/TLU memory manager This is a
non-fatal error for PLU/TLU manager caused
by system instability or memory issues

Failed to modify replication mode

An error was encountered while trying to

modify replication mode on linecard

Failed to open shared memory

shm_base_address = [hex], shm_size =
[hex], sizeof(pm_shmwin_header_st) =
[hex], pm_shm_header = [hex]
pm_shmwin_id = [hex] Forwarding may be
impacted on this linecard.
Failed to open platform's shared memory

Failed to get the platform information

GSR_PM_SHMEM_NAME =
[hex],shm_base_address = [hex], shm_size
= [hex] Forwarding may be impacted on
Failed to get platform information for the
this linecard.
shared memory.

Failed to verify PM Shared Memory Ready

Magic Word pm_shm_header = [hex],
pm_shm_header->magic_word = [hex]
PM_SHM_READY_MAGIC_WORD = [hex]
Forwarding may be impacted on this
interface.

Failed to verify that PM's shared memory is

ready to be used. PM checks the validity by
comparing the MAGIC READY Word that
should be initialized in shared memory
prior to using it.

Failed to open shared memory for uidb2ifh

service returning error [chars] Forwarding Failed to open shared memory for uidb to
may be impacted on this linecard.
ifh service.

Failed to allocate default table

default table could not be allocated enough

memory.

Failed to allocate lbl table for hash table

error: [chars]

lbl table for given hash table could not be

allocated enough memory.

Data centre services library failed to map

[chars]: dc_services_lib_ifh_to_pic_element interface handler to Platform interface
failed
context

[chars] ERROR: [chars], nodeid = [dec], pic Mapping between interface handler and
= [hex] \n
engine port failed

Failed to get PIC array for [chars] context,

using PFI context ([hex]) and interface
handle ([hex]). PFI returned error ([chars])
Forwarding may be impacted on this
interface.

Failed to get PIC information from PFI that

is required for forwarding packets from the
specified interface.

failed to initialize [chars]: [chars]

A submodule was unable to initialze due to

the specified error

LC in slot [dec] will come up in GREEN

MODE due to power budget

When E7 card is configured in Performance

mode and there power available is less,
this log message is displayed to warn the
user that the LC will come in Green mode.

Powershelf AC/DC detection failed,status

code [dec]

The AC/DC detection of powershelf failed

due to wrong value read from EEPROM or
read from wrong location of EEPROM.

No alarmcard or busboard module was

found available to talk to the PEMs. This
might occur if the MBus agent associated
with that module became temporarily
unavailable. As such, this error message
should only be a cause for concern if it
appears repeatedly, over a period of
minutes. If it appears just once, it indicates
a transient condition, and may be safely
ignored. Lastly, note that if this message is
seen during chassis boot up, the problem is
far more serious, as during that time, the
path to the PEMs is assumed stable. In this
case, powershelf discovery may fail, and as
No alarmcard/busboard module available to a result, some linecards may be left in
communicate w/ PEM[dec]
unpowered state.

Resource allocation error encountered

during startup

Power Manager subsystem failed during

startup. This was probably due to lack of
system resources. For example low
memory. If the problem is seen, sysldr will
be restarted and if problem persists, RP will
be restarted.

Memory allocation error encountered

during startup

Power Manager subsystem failed during

startup. This was probably due to lack of
system memory resources. If the problem
is seen, sysldr will be restarted and if
problem persists, RP will be restarted.

Not enough power to bringup card in slot

[dec]

The powershelf does not have adequate

capacity to drive the card which is inserted
or POWERED_UP newly. This may occur
during power-mgr initialization, if in-use
power is more than capacity.

Alarmcard/busboard module not ready to

communicate w/ PEM

Alarmcard or busboard module was found

to be resetting or still running from ROM.
This message is seen during chassis boot
up. In this case, test chassis is assumed
and all Line cards will boot up as default
power is assumed. However note that
power manager would still display errors
and envmon module would also display
powershelf related errors

Power consumption has exceeded

supply[chars] by [dec]W; results
unpredictable

The power calculated in use by the chassis

exceeds that available by the powershelf.
This condition could result in an outage of
the chassis if action is not immediately
taken.

Chassis power requirements exceed

capacity by [dec]W [chars]

The powershelf does not have adequate

capacity to drive the entire chassis. This is
occurred during power-mgr initialization.

Failed to get pem=[dec] data, error

status=[chars]

Failed to get good data from Pacific pems

Powershelf capacity insufficient to reserve

power for card in slot [dec]

The powershelf does not have enough

capacity to reserve power for the linecard
in the specified slot. It will be left
unpowered as a result.

Could not create power manager discovery Creation of power manager main thread is
thread
failed.

[chars]

For displaying power manager debugging

information with an errno.

Power usage for card in slot [dec]

unknown; assuming [dec] watts max

An entry in the power table could not be

found for the card specified. To allow
chassis bringup to progress, default values
are being used as specified. Note that this
error should only occur during
development when a new cardtype is being
introduced, but its power data has yet to
be entered.

Power Manager unable to init critical

resource, errno=[chars]

Function sem_init can fail because of the

following reasons. Returns 0 Success. The
semaphore referred to by sem is initialized.
-1 An error occurred (errno is set). Errors
EAGAIN A resource required to initialize the
semaphore has been exhausted. EINVAL
The value argument exceeds
SEM_VALUE_MAX. EPERM The process lacks
the appropriate privileges to init the
semaphore. ENOSPC A resource required to
initialize the semaphore has been
exhausted. ENOSYS The sem_init function
isn't supported

Warning: Interim power entry value being

used for cardtype [hex]

An entry in the power table has been

flagged as interim, meaning it is a
placeholder used during development
while the final power consumption is being
determined. This issue will occur only
during development of new linecards or
power-supplies, and the errmsg exists only
to aid developers.

Invalid PEM combination in [chars]; Found

[dec] pems, recommended at least [dec]
pems

Power Manager has detected less than

minimum number of Pacific Pems. This is
applicable only for 16 slot chassis which
has Pacific Pems.

Could not create nodeid for slot [dec]

error=[chars].

Slot number is probably not known

No power entry found for cardtype [hex]

An entry in the power table could not be

found for the entity specified. This issue
will occur only during development of new
linecards or power-supplies, and the
errmsg exists only to aid developers.

Unable to get Mbus ROM status from

SYSDB. Error =[chars]

Unable to get the Mbus ROM status from

Sysdb.

The sem_post error can fail due to the

following conditions. EINVAL Invalid
Power Manager unable to send notification, semaphore descriptor sem. ENOSYS The
error = [chars]
sem_post function isn't supported.
The card in the specified slot could not be
powered off as part of putting it into a lowpower state. As a result, it is unusable, but
Cannot power off card in slot [dec]; manual still contributing to the power consumed in
removal required
the chassis.

PM: Unable to sysdb_bind :[chars]

SYSDB Bind failed

Failed to create sysdb tuple [chars] for slot

[dec]. error=[chars]
SYSDB Set or Create failed for that item

Sysldr is waiting for power manager to

indicate if it is safe to power up the card.
Timed out waiting for power-up decision for As it did not get a response for 60 seconds,
slot [dec]
it throws this error message.

Unable to determine characteristics of

PEM[dec]; skipping

The characteristics of the power supply

installed in the specified slot could not be
determined. This supply is being skipped,
and discovery of the rest of the powershelf
will continue. If no supplies can be found, a
failsafe type will be used to allow the
chassis to come up to a point at which
debugging of the problem is possible.

Unable to detect installed power supplies;

using failsafe assumptions

The installed power supplies (i.e., PEMs)

could not be detected. To allow the chassis
to come up, a set of conservative
assumptions have been used for
calculating power availability and
consumption. Some linecards may be left
in an unpowered state as a result.

Unable to determine powershelf type;

using failsafe assumptions

The powershelf type could not be

determined during boot up. To allow the
chassis to come up, a set of conservative
assumptions have been used for
calculating power availability and
consumption. Some linecards may be left
in an unpowered state as a result.

Power Manager unable to wait for

notification , error = [chars]

The sem_wait function decrements the

semaphore referred to by the sem
argument. If the semaphore value is not
greater than zero, then the calling process
blocks until it can decrement the counter,
or the call is interrupted by signal. Some
process should eventually call sem_post()
to increment the semaphore. Returns 0 The
semaphore was successfully decremented.
-1 The state of the semaphore is
unchanged (errno is set). Errors EDEADLK A
deadlock condition was detected. EINVAL
Invalid semaphore descriptor sem. EINTR A
signal interrupted this function.

Cannot enqueue event [chars] for device

[dec]

Power Manager internal failure occurred

possibly due to low memory condition.

Cannot enqueue event [chars] for zone

[dec]

Power Manager internal failure occurred;

possible low memory condition.

Invalid condition detected in function

[chars] at line [dec]

A disallowed condition internal to the

Power Manager has been detected.

Power scale factor '[dec]' out of range;

ignoring

The SYSDB Config variable used to dictate

the scale factor for utilizing something
other than worst-case power consumption
values is out of the allowable range.

PEM[dec] has powered down

The power supply specified has powered

down.

The configuration includes a power priority

reservation for a slot that does not have a
linecard installed within it. Power will not
Attempting to reserve power for empty slot be set aside for this slot, and the command
[dec]
should be removed from the config.

Test chassis detected; using default

powershelf configuration

The type of chassis model was detected as

being a test chassis, which does not have
many of the resources the Power Manager
uses to communicate with the PEMs. Thus,
the type of powershelf, as well as type and
number of PEMs installed will default to a
predefined value, intended to allow the
chassis to function unimpeded.

PEM[dec] inserted but unpowered

The power supply specified has been

installed in the chassis but is unpowered,
most likely because of an unconnected
power cord.

Spurious QUEUE_EVENT, dequeueing NULL Power Manager internal failure occurred;

pointer
possible low memory condition.

Unexpected event [dec]; ignoring

Power Manager subsystem failed during

startup; lack of resources.

Mixing legacy and intelligent PEMs is not

recommended

Both legacy as well as the higher-wattage

intelligent PEMs have been detected in the
chassis at the same time. While this is a
supported configuration, it is not
recommended, as it may result in the
legacy PEM eclipsing the intelligent PEM by
reducing the overall powershelf wattage to
that of the former, when running in
redundant mode. The formal
recommendation is to have both PEMs be
of the same type.

PEM[dec] powered up successfully,

supplying [dec] watts

The power supply specified has

successfully powered up.

PEM[dec] removed

The power supply specified has been

removed from the chassis.

Unable to determine type of PEM[dec];

using failsafe assumptions

The type of the power supply installed in

the specified slot could not be determined.
To allow the chassis to come up, it will be
categorized as the failsafe type, which
allows it to be assumed providing modest
power to the chassis. Note that the
wattage provided by a failsafe supply may
be less than that which the supply is
actually providing.

Chassis power consumption is back within

limits[chars]

The power calculated in use by the chassis

has returned to a valid that is within the
power supplied by the powershelf.

Overriding power consumption for card in

slot [dec]; now [dec] watts

Power consumed for the card in the

specified slot has been overridden with a
value from the config

[chars][dec]

power manager debugging information.

[chars]

For displaying power manager's

informational events.

PEM[dec] inserted, supplying [dec] watts

The power supply specified has been

installed in the chassis and is now active

Overriding PEM[dec] rating; now [dec]

watts

Supply power for the PEM specified has

been overridden with a value from the
config.

The number of power zones for the chassis

has been overidden with a value from the
Number of zones being forcibly set to [dec] config.

Error: [chars] err=[dec]

An internal error occurred in the preroute

manager process requiring the restart of
the process. %s - indicates the failure %d value associated with the failure

An internal failure occurred in the preroute

Reason of Failure: [chars] Value associated manager process requiring the restart of
with the Failure =[dec]
the process.

Info: [chars] [hex]

This is a Informational message in the

preroute manager %s - indicates the
informational message. %d - indicates any
additiona data.

Info: [chars] [hex]

This is a Informational message in the

preroute manager %s - indicates the
informational message. %d - indicates any
additiona data.

[FSB Critical [chars] error] Name: [chars],

Description: [chars], Log: [chars]

A critical error has occurred on the FSB

(Front Side Bus) of the Linecard's CPU
complex. The message will display the
name of the error and the description along
with the hardware log. These errors will
cause a card reload. If it is a software error
and persists or if it's a hardware error,
please contact support.

[Internal MCH critical [chars] error] Name:

[chars], Description: [chars], Log: [chars]

A critical error has occurred in the MCH

(Memory Controller Hub) of the Linecard's
CPU complex. The message will display the
name, description, and error log. These
errors will cause a card reload. If it is a
software error and persists or if it's a
hardware error, please contact support.

Failed to handle [chars] error. Blk: [dec],

err_id: [dec], rc = [hex] ([chars])

The Linecard has received an error signal

but failed to handle/log the error properly.
This may be from a program level error.

Initialization for [chars] trace failed. rc =

[hex] ([chars])

Ltrace initialization failed. This may be a

program level error. The failure will cause
the Procmgr process to restart.

[DDR [chars] error] Name: [chars],

Description: [chars], Log: [chars]

A ECC/replay uncorrectable has occurred

from the DDR module of the Linecard's CPU
complex. The message will display the
name, description, and error log. The
linecard will reload after a certain threshold
of number of occurances have been
reached.

An uncorrectable error has occurred on the

FSB (Front Side Bus) of the Linecard's CPU
complex. The message will display the
name and description of the error along
with the error log. If the log indicates 'no
log', that means the error is a subsequent
error. 'Detected MCERR#' and 'B-INIT'
errors do not have a log as well. The
[FSB Uncorrectable Non-fatal [chars] error] linecard will reload after a certain threshold
Name: [chars], Description: [chars], Log:
of number of occurances have been
[chars]
reached.

[Internal MCH critical [chars] error] Name:

[chars], Description: [chars], Log: [chars]

An uncorrectable has occurred in the MCH

(Memory Controller Hub) of the Linecard's
CPU complex. The message will display the
name, description, and error log. The
linecard will reload after a certain threshold
of number of occurances have been
reached.

Performance monitoring is already [chars]

The user is attempting enable/disable the

performance monitoring feature. But the
feature is already enabled/disabled.

Processor Manager Linecard CPU driver

Skipping performance monitoring
doesn't support performance monitoring
ocnfiguration. Performance monitoring not according to the specifications of the
support
hardware.

Failed to register with cerrno library. rc =

[hex] ([chars])

Cerrno Registration failed. This may be a

program level error. The failure will cause
the Procmgr process to restart.

Event Manager create failed.

Procmgr Event Manager create failed. This

may be a program level error. The failure
will cause the Procmgr process to restart.

Procmgr encountered an error during

initialization resulting in restarting the
Procmgr process. This may be a program
level error. The failure will cause the
Procmgr initialization error. reason: [chars] Procmgr process to restart.

Failed to register with [chars] Library. rc =

[hex] ([chars])

Registration with an external library failed.

This may be a program level error. The
failure will cause the Procmgr process to
restart.

Initialization for [chars] trace failed. rc =

[hex] ([chars])

Ltrace initialization failed. This may be a

program level error. The failure will cause
the Procmgr process to restart.

Procmgr initialization may have failed due

to lack of memory

Procmgr encountered a memory allocation

error.

Error succssfully logged in Asic Error and

PCDS library. client_id: [dec], blk: [dec],
err_id: [dec]

Sucessfully logged error into Asic Error

library and PCDS library. Client ID and error
key are shown.

Procmgr failed to raise alarm to Fault

Manager. rc = [hex], ([chars])

Error in raising alarm to Fault Manager. This

may be a program level error. The failure
will cause the Procmgr process to restart.

Sysdb Register EDM failed

Procmgr failed to register with Sysdb EDM.

This may be a program level error.

Procmgr failed to clear asic-error threshold Error in clearing asic-error threshold for a
for error. key: [hex] rc = [hex] ([chars])
particular error.

PRP : **** NVRAM battery is low !!! Please

replace the board

Performance Route Processor (PRP) NVRAM

battery level is low. The effect is that
certain PRP functions dependant on data in
NVRAM may not function properly.

Disk0 is Inserted

Disk0 is inserted on Performance Route

Processor 3 (PRP3).

Disk0 is Removed

Disk0 is removed on Performance Route

Processor 3 (PRP3).

Performance Route Processor disk driver

initialization failed: ([chars] [chars])

Performance Route Processor (PRP) disk

drivers failed to initialize. The effect is that
PRP will not function. %s - indicates the
reason for the failure. %s - is the error
reason.

This message indicates an internal

software error while spawning critical
process. The error(s) might be due to one
of these failures Evm Creation
[chars], Initialization Error with code([dec]) Egress/Ingress QAD look-up Memory
[chars]
allocation

This message indicates an internal

software error while spawning critical
process. The error(s) might be due to one
of these failures Evm Creation
[chars], Initialization Error with code([dec]) Egress/Ingress QAD look-up Memory
[chars]
allocation Rx and Tx Fping Stat Init failed

Rebooting RP in slot [dec] because it

conflicts with an already operational RP in
slot [dec].

Conflicting RP found in the same LR. If the

RP is meant to be used in another logical
router, please ensure it is assigned to the
other LR. In the releases 3.4 and below,
card pairing requires primary/standby cards
in specific slots and active RP's need to be
in seperate LR's. Adjacency is defined by
RP pairing rules (e.g. 0-1, 2-3, 4-5, 6-7). If
it's intended to use the conflicting RP as a
standby partner, please move the RP
adjacent to the active. Card pairing is not
required from 3.5 and above.
Primary/standby cards can be placed in any
slot provided the slots are part of same LR.
%d - indicates the wrong slot number the
RP is inserted %d - indicates the slot
number of the operational RP

Slot [dec] heartbeat lost

The active RP has lost the heartbeat of the

indicated slot. This error happens after a
certain number of messages are lost
between the active and the indicated card.
%d - indicates the slot number of the card
experiencing the problem.

Process initialization failed: ([chars]%s)

The psarb process failed to initialize. This

process is responsible for providing a high
level of availability on the GSR router by
having a pair of active and standby RPs in
the system. When an active RP fails,
another RP can take over the functionality
of the failed RP. %s - indicates the reason
for the failure. %s - the decoded error
reason.

Failed to get LR info after [dec] seconds

rc=[hex], Retrying

PSarb needs LR map and the dSC

information before it can proceed with
active standby arbitration. The LR
information is acquired by connecting to
the LRd on the dSC. This error message
indicates, the connection to LRd did not
succeed, either because the LRd process
does not exist or the dSC selection has still
not taken place. The system will retry
indefinetely to get the LR information and
log this message periodically to alert the
user of the prevailing condition.

Failed to get standby RP (slot [dec]) ready

status. Error Num [dec]

When Primary Standby arbitration

heartbeat messages are missing from
active RP, arbitration module on standby
RP will attempt to takeover as active. In
order to takeover as active role, standby RP
needs to know if it is ready to takeover.
Ready means all applications required for
standby RP to takeover as active are up
and running. A query to system manager is
sent to know the ready status of the
standby RP. If this query fails, arbitration
module on standby RP takes action of
taking over as active RP.

Two primary RPs detected (message from

slot [dec])

There appear to be two PRIMARY RP's in the

system. This is due to messaging error
when the other RP didn't receive the BID
message. %d indicates the primary slot
number displaying the message

At any given time, there should be one

active dSC in the system. In the event that
the active RP detects another active dSC in
the system, the RP should reboot itself to
recover the condition. This event is
expected when creating or deleting SDR
Rebooting RP because an active dSC in slot configuration. %d - indicates the slot
[dec] is detected.
number of the active dSC

This node's partner (slot [dec]) is in a

different LR. The standby node will be
reset.

Adjacent RPs must be in the same LR

unless if they are both to be booted with an
RP image. It is, however, permissable to
boot a DRP in one of these slots. Adjacency
is defined by RP pairing rules (e.g. 0-1, 2-3,
4-5, 6-7). %d - indicates the slot number of
the partner RP

Slot [dec] (internal flavor [dec]) is actually

not from RP family. Reset cancelled

The arbitration module watches the health

of other RP cards in the system and reloads
them if heartbeats are missed. In this case,
we were about to reload a card but a final
check revealed that the card was not of
family RP, so we avoided the reload. This is
a safety check to catch an abnormal
condition. No problem will result from this
type of error.

PSARB sends an mbus message to all RP

running IOS on the chassis, to configure the
RP as an IOS non-participant router,
therefore, does not interfere with IOX
running on this RP. %d - indicates the slot
Detected an RP in slot [dec] is running IOS. number of the RP that is running IOS on the
Configured it as IOS non-participant.
chassis
Reminder: psarb debug mode is still
enabled...Disable using run psarbcmd

This message reminds the user that a

debug mode is enabled and must
eventually be disabled.

The specified RP stopped responding, but

we did not receive any message indicating
that the card is in DUMP mode. Looks like it
Slot [dec] still not in dump mode, forcing it is still in IOX mode and could potentially try
down
to take over. So, force it to go down.

Card is going active.

When an RP initially boots up, it can take

the active role if no other active RP is
present. Also a failure on active or a force
switch over could cause the standby RP to
change state to active. This message is
displayed when the PRP card is going
active.

Card is going standby.

When an RP initially boots up, it can take

the standby role if an active RP is present.
Also a failure on active or a force switch
over causes the active RP to change state
to standby. This message is displayed when
the RP card is going standby.

Now ignoring countdown timeouts

This message confirms the user selected

debug mode

Timeout waiting for active RP heartbeats,

but not taking over because of configured
debug mode

The active RP is no longer sending

heartbeats, but we don't take over
becaused of the configured debug mode.

Timeout waiting for heartbeats from slot

[dec], but ignoring because of configured
debug mode

The specified slot is no longer sending

heartbeats, but we don't take any action
given the configured debug mode.

MBUS receive failure detected on standby

slot [dec], node gracefully rebooting self

The specified Standby RP is experiencing

receive failures on its MBUS and instead of
causing a failover and becoming Primary, it
is gracefully rebooting itself to maintain
proper health of the system.

Resume sending MBUS heartbeats to other This message confirms the user selected
cards
debug mode
Now using normal timeouts

This message confirms the user selected

debug mode

Two primary RPs detected: myself (slot

[dec]) and message from slot [dec]

There appear to be two PRIMARY RP's in the

system. ex-act suicide and the partner
takes over. %d indicates the primary and
partner slot numbers displaying the
message

Now now longer sending MBUS heartbeats This message confirms the user selected
to other cards
debug mode
Resuming countdowns

This message confirms the user selected

debug mode

Rmf not registered with psarb for

notification rebooting self slot [dec]

Redundancy controller process is not

registered for arbitration state notification,
this can leave the system in unstable state.
The node is rebooting self to correct this
situation.

The role of this card has been locked failover was prevented. %d - indicates the
(slot [dec]) failover prevented - card role is slot number of the PRP which it's role is
locked
locked

Receive failures from partner slot [dec]

detected on slot [dec]

The specified RP is experiencing receive

failures from its partner on its MBUS.

Self send failure detected on slot [dec]

The specified RP is experiencing self send

failures on its MBUS.

Standby RP is not ready to takeover as

active RP. Ready state means all
applications required for standby RP to
takeover as active are up and running. In
(slot [dec]) failover prevented - standby RP this case, the operation of standby RP
is not ready.
taking over as active is prevented.
Turning off our countdowns

This message confirms the user selected

debug mode

Take over message received from partner,

transition to primary

The specified RP received a take over

message from its partner, indicating that
the card should transition to Primary role.

Process initialization failed: ([chars]%s)

The psarb-lc process failed to initialize. This

process is responsible for monitoring the
arbitration messages between the primary
and standby RPs and determining which
slot contains the primary RP. %s - indicates
the reason for the failure. %s - the decoded
error reason.

Unable to get LR name [dec] times.

The PASRB_LC process running on a LC fails

to get its LR name after multiple retries
and hence exits.

Resetting myself ([dec]), as DLRSC ([dec])

is not present anymore in my LR.

PSARB knows when a DLRSC (primary RP)

in its LR is down and there is no backup
DLRSC (secondary RP). PSARB then needs
to reset itself as the LR is headless.

Failed to get timer service for PSARB HB

timeout. Error: [chars]

PSARB-LC process failed in getting timer

service to sleep for timeout to check the
HeartBeat status from RPs.

PTP Servo state transition from state

[chars] to state [chars]

PTP Servo state transition event

SIP-700 LC Punt-infra initialization failed:

([chars]%s)

SIP-700 LC punt-inject and internal

interfaces failed to initialize. SIP-700 will
not function as expected. This message
indicates the reason for the failure and the
specific error reason.

Register access failure on Punt switch

Register access failure on Punt Switch.

LINK FAIL-0

PUNT link has failed.

LINK FAIL-1

Punt link failed

LINK FAIL-2

PUNT link has failed.

LINK FAIL-24

Punt link failed

LINK FAIL-25

Punt link failed

LINK FAIL-3

Punt link failed

LINK FAIL-4

PUNT link has failed.

LINK FAIL-5

Punt link failed

LINK FAIL-6

PUNT link has failed.

LINK FAIL-7

Punt link failed

LINK FAIL-8

PUNT link has failed.

LINK FAIL-9

Punt link failed

CPU RGMII RX LINK FAIL-0

CPU RGMII TX or PUNT RX has failed.

CPU RGMII RX LINK FAIL-1

125Mhz clock has failed.

DDR interface failed

Punt DDR interface has failed.

Interlaken interface failed [chars]

Punt interlaken interface has failed.

Register access failure on Punt

Register access failure on Punt FPGA.

Xaui interface failed [chars]

Punt xaui interface has failed.

EBS module errors [chars]

Punt fpga detects egress module errors

IBS module errors [chars]

Punt fpga detects ingress module errors

Interlaken module errors [chars]

Punt fpga detects interlaken module errors

PLL inside the FPGA device is not locked

PLL inside the FPGA device is not locked.

XAUI module errors [chars]

Punt fpga detects xuai module errors

Feature not supported on FP140, MSC-140

PLATFORM-PWHE-EA: [chars] Error - [chars] LCs

Power module [chars] idprom [chars]

validity test.

'The IDPROM may be corrupted.'

Capacity for power-module [chars] is equal

to zero. Condition [chars]
'Capacity in the IDPROM is zero.'

Power-module [chars] failure condition

[chars] [chars]

'Either an internal PEM error, an over

voltage/current/temperature shutdown or
an external input feed error.'

Power-module [chars] warning condition

[chars] [chars]

'Either a feed voltage out of limits warning,

unit in current/power limit or over
temperature warning condition.'

Power-module [chars] firmware upgrade

error: [chars] [chars]

'Error was encountered during firmware

upgrade operation, the operation was
aborted'

Power-module [chars] IO communication

failure condition [chars]

The software is not able to communicate

with the power-module. This may have an
impact on the router's available power
budget, as the software cannot determine
the power-module capacity in this state.
This condition should be resolved prior
adding additional FRU to the router.

Power-module [chars] [chars]

'The power-module has either been

pulled/inserted.'

ClkCtrl detected power supply power

module failure [chars]

ClkCtrl has detected a power supply

module has failed

Power module [chars] idprom [chars]

validity test.

'The IDPROM may be corrupted.'

Capacity for power-module [chars] is equal

to zero. Condition [chars]
'Capacity in the IDPROM is zero.'

Power-module [chars] fail reason: [chars]

'Some power module failure condition has

been raised.'

Power-module [chars] failure condition

[chars]

'Either an internal PEM error, an over

voltage/current/temperature shutdown or
an external input feed error.'

Power-module [chars] warning condition

[chars]

'Either a feed voltage out of limits warning,

unit in current/power limit or over
temperature warning condition.'

Power-module [chars] warning condition

reason: [chars]

'Some power module warning condition has

been raised.'

Power-module [chars] IO communication

failure condition [chars]

The software is not able to communicate

with the power-module. This may have an
impact on the router's available power
budget, as the software cannot determine
the power-module capacity in this state.
This condition should be resolved prior
adding additional FRU to the router.

Power-module [chars] [chars]

'The power-module has either been

pulled/inserted.'

CPP0 Fatal error detected.

The CPP device driver handled a fatal CPP0

error and requested that the QFP-CPU
Bridge device driver report the error to the
Platform Fault Manager.

CPP1 Fatal error detected.

The CPP device driver handled a fatal CPP1

error and requested that the QFP-CPU
Bridge device driver report the error to the
Platform Fault Manager.

QFP-CPU Bridge fatal error detected.

QFP-CPU Bridge detected a fatal error.

QFP-CPU Bridge eCSR0 access error

detected.

QFP-CPU Bridge detected an eCSR0 access

error.

QFP-CPU Bridge eCSR1 access error

detected.

QFP-CPU Bridge detected an eCSR1 access

error.

QFP-CPU Bridge detected an HTDP chain

error on the HT0 interface. This is logged
when the HT interface received a sync
QFP-CPU Bridge HT0 Chain error detected. flood or when HyTop drives a sync flood.

QFP-CPU Bridge HT0 CRC error detected.

QFP-CPU Bridge detected an HTDP CRC

error on the HT0 interface.

QFP-CPU Bridge HT0 EOC error detected.

QFP-CPU Bridge detected an HTDP EOC

error on the HT0 interface. HT0 EOC Error
indicates that a packet has arrived to be
sent on the HT link but the link is not
active.

QFP-CPU Bridge HT0 Erroneous Command

detected.

QFP-CPU Bridge detected an erroneous

command on the HT0 HTDP interface. This
means that the HT host core has received
an HT Flush, Fence, or Broadcast packet.
These packets are not supported and
behavior is undefined after this type of
packet is received. Note: CPP does not
generate these commands.

QFP-CPU Bridge HT0 Invalid Command

detected.

QFP-CPU Bridge detected an invalid

command on the HT0 HTDP interface. This
means that the HT host core has received a
non-posted write command. These packets
are not supported and behavior is
undefined after this type of packet is
received.

QFP-CPU Bridge HT0 Overflow error

detected.

QFP-CPU Bridge detected an HTDP overflow

error on the HT0 interface. This error is
logged when a packet is received and has
no buffer available to receive it.

QFP-CPU Bridge HT0 Protocol error

detected.

QFP-CPU Bridge detected an HTDP protocol

error on the HT0 interface. This is logged
when the HT interface experiences a
protocol error on the HT interface.

QFP-CPU Bridge detected an HTDP chain

error on the HT1 interface. This is logged
when the HT interface received a sync
QFP-CPU Bridge HT1 Chain error detected. flood or when HyTop drives a sync flood.

QFP-CPU Bridge HT1 CRC error detected.

QFP-CPU Bridge detected an HTDP CRC

error on the HT1 interface.

QFP-CPU Bridge HT1 EOC error detected.

QFP-CPU Bridge detected an HTDP EOC

error on the HT1 interface. HT0 EOC Error
indicates that a packet has arrived to be
sent on the HT link but the link is not
active.

QFP-CPU Bridge HT1 Erroneous Command

detected.

QFP-CPU Bridge detected an erroneous

command on the HT1 HTDP interface. This
means that the HT host core has received
an HT Flush, Fence, or Broadcast packet.
These packets are not supported and
behavior is undefined after this type of
packet is received. Note: CPP does not
generate these commands.

QFP-CPU Bridge HT1 Invalid Command

detected.

QFP-CPU Bridge detected an invalid

command on the HT1 HTDP interface. This
means that the HT host core has received a
non-posted write command. These packets
are not supported and behavior is
undefined after this type of packet is
received.

QFP-CPU Bridge HT1 Overflow error

detected.

QFP-CPU Bridge detected an HTDP overflow

error on the HT1 interface. This error is
logged when a packet is received and has
no buffer available to receive it.

QFP-CPU Bridge HT1 Protocol error

detected.

QFP-CPU Bridge detected an HTDP protocol

error on the HT1 interface. This is logged
when the HT interface experiences a
protocol error on the HT interface.

QFP-CPU Bridge local register read error

detected.

QFP-CPU Bridge detected a local register

read error.

QFP-CPU Bridge local register write error

detected.

QFP-CPU Bridge detected a local register

write error.

QFP-CPU Bridge multi-bit memory error

detected.

QFP-CPU Bridge detected a multi-bit

memory error (MBE).

HT0 Drop Inband Message Event: HT

Inband Interrupt(s) have been filtered and
dropped due to a previously sent MSI that
QFP-CPU Bridge HT0 Drop Inband Message has set the H/W mask and has not been
event detected.
cleared by S/W.
HT1 Drop Inband Message Event: HT
Inband Interrupt(s) have been filtered and
dropped due to a previously sent MSI that
QFP-CPU Bridge HT1 Drop Inband Message has set the H/W mask and has not been
event detected.
cleared by S/W.

QFP-CPU Bridge PCIe Core Overrun error

detected.

QFP-CPU Bridge detected a PCIe Core

overrun error. This means that the QFP-CPU
Bridge PCIe core could not accept
Completion errors seen by the receive
interface (CA and UR).

QFP-CPU Bridge single-bit memory error

detected.

QFP-CPU Bridge detected a single-bit

memory error (SBE).

QFP-CPU Bridge non-fatal error detected.

QFP-CPU Bridge detected a non-fatal error.

[chars]

config time warning regarding config

adjustments and any other warning.

[chars]

config time warning regarding config

adjustments and any other warning.

Flow Aware QoS is [chars]. [chars]

'Any change in flow qos max flow count

requires the LC to be rebooted to ' 'take
effect.'

Line-card QoS mode set to [chars].[chars]

'Any change in qos mode requires the LC to

be rebooted to take effect.'

Line-card QoS mode set to [chars].[chars]

'Any change in qos mode requires the LC to

be rebooted to take effect.'

'A configured qos mode is not supported on

Line-card QoS mode [chars] is unsupported this LC.'

QSFP+ Module for port [dec] is not Cisco

compliant

A compliance error was detected during

QSFP+ initialization. A compliance error is
due to unsupported optics, checksum error,
EEPROM CRC error, vendor data error, or
decryption error. The QSFP+ is the
pluggable optics on the line cards. QSFP+
initialization may happen when linecard
boots up, QSFP+ OIR and line card process
restart. The optics will not be enabled if an
QSFP+ compliance error is detected.

A QSFP+ Module not supported for the port

error was detected during QSFP+
initialization. A QSFP+ Module not
supported for the port error is reported
when Optics is not supported on the port.
The QSFP+ is the pluggable optics on the
line cards. QSFP+ initialization may happen
when linecard boots up, QSFP+ OIR and
QSFP Module for port [dec] is not supported line card process restart.

QSFP+ Module for port [dec] is not a

supported Product ID (PID)

A PID not supported error was detected

during QSFP+ initialization. A PID not
support error is reported when either the
PID can not be read or not supported on
the platform. The QSFP+ is the pluggable
optics on the line cards. QSFP+
initialization may happen when linecard
boots up, QSFP+ OIR and line card process
restart. The optics will not be enabled if a
PID not supported error is detected.

QSFP+ Module for port [dec] is not a

supported module type

An QSFP+ supported error was detected

during QSFP+ initialization. This error is
reported when the QSFP+ type can not be
determined or it is not supported on the
platform. The QSFP+ is the pluggable
optics on the line cards. QSFP+
initialization may happen when linecard
boots up, QSFP+ OIR and line card process
restart. The optics will not be enabled if an
QSFP+ supported error is detected.

QSFP+ Case High Bias Alarm

Environmental monitoring has detected a

QSFP+ bias greater than or equal to the
high bias alarm threshold. The QSFP+ is
the pluggable optics on the line cards. The
bias threshold values are read from the
QSFP+.

QSFP+ Case High Temperature Alarm

Environmental monitoring has detected a

QSFP+ temperature greater than or equal
to the high temperature alarm threshold.
The QSFP+ is the pluggable optics on the
line cards. The temperature threshold
values are read from the QSFP+.

QSFP+ Case High Voltage Alarm

Environmental monitoring has detected an

QSFP+ voltage greater than or equal to the
high voltage alarm threshold. The QSFP+ is
the pluggable optics on the line cards. The
voltage threshold values are read from the
QSFP+.

QSFP+ Lane 0 High Bias Alarm

Environmental monitoring has detected a

QSFP+ laser bias greater than or equal to
the high laser bias alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The laser bias threshold values are
read from the QSFP+.

QSFP+ Lane 0 High Rx Power Alarm

Environmental monitoring has detected a

QSFP+ Rx power greater than or equal to
the high Rx power alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The Rx power threshold values are
read from the QSFP+.

QSFP+ Lane 0 High Temperature Alarm

Environmental monitoring has detected a

QSFP+ laser temperature greater than or
equal to the high temperature alarm
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 0 High Tx Power Alarm

Environmental monitoring has detected a

QSFP+ Tx power greater than or equal to
the high Tx power alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The Tx power threshold values are
read from the QSFP+.

QSFP+ Lane 0 Low Bias Alarm

Environmental monitoring has detected a

QSFP+ laser bias less than or equal to the
low laser bias alarm threshold. The QSFP+
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the QSFP+.

QSFP+ Lane 0 Low Rx Power Alarm

Environmental monitoring has detected a

QSFP+ Rx power less than or equal to the
low Rx power alarm threshold. The QSFP+
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the QSFP+.

QSFP+ Lane 0 Low Tx Power Alarm

Environmental monitoring has detected a

QSFP+ Tx power less than or equal to the
low Tx power alarm threshold. The QSFP+
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the QSFP+.

QSFP+ Lane 1 High Bias Alarm

Environmental monitoring has detected a

QSFP+ laser bias greater than or equal to
the high laser bias alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The laser bias threshold values are
read from the QSFP+.

QSFP+ Lane 1 High Rx Power Alarm

Environmental monitoring has detected a

QSFP+ Rx power greater than or equal to
the high Rx power alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The Rx power threshold values are
read from the QSFP+.

QSFP+ Lane 1 High Temperature Alarm

Environmental monitoring has detected a

QSFP+ laser temperature greater than or
equal to the high temperature alarm
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 1 High Tx Power Alarm

Environmental monitoring has detected a

QSFP+ Tx power greater than or equal to
the high Tx power alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The Tx power threshold values are
read from the QSFP+.

QSFP+ Lane 1 Low Bias Alarm

Environmental monitoring has detected a

QSFP+ laser bias less than or equal to the
low laser bias alarm threshold. The QSFP+
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the QSFP+.

QSFP+ Lane 1 Low Rx Power Alarm

Environmental monitoring has detected a

QSFP+ Rx power less than or equal to the
low Rx power alarm threshold. The QSFP+
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the QSFP+.

QSFP+ Lane 1 Low Tx Power Alarm

Environmental monitoring has detected a

QSFP+ Tx power less than or equal to the
low Tx power alarm threshold. The QSFP+
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the QSFP+.

QSFP+ Lane 2 High Bias Alarm

Environmental monitoring has detected a

QSFP+ laser bias greater than or equal to
the high laser bias alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The laser bias threshold values are
read from the QSFP+.

QSFP+ Lane 2 High Rx Power Alarm

Environmental monitoring has detected a

QSFP+ Rx power greater than or equal to
the high Rx power alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The Rx power threshold values are
read from the QSFP+.

QSFP+ Lane 2 High Temperature Alarm

Environmental monitoring has detected a

QSFP+ laser temperature greater than or
equal to the high temperature alarm
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 2 High Tx Power Alarm

Environmental monitoring has detected a

QSFP+ Tx power greater than or equal to
the high Tx power alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The Tx power threshold values are
read from the QSFP+.

QSFP+ Lane 2 Low Bias Alarm

Environmental monitoring has detected a

QSFP+ laser bias less than or equal to the
low laser bias alarm threshold. The QSFP+
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the QSFP+.

QSFP+ Lane 2 Low Rx Power Alarm

Environmental monitoring has detected a

QSFP+ Rx power less than or equal to the
low Rx power alarm threshold. The QSFP+
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the QSFP+.

QSFP+ Lane 2 Low Tx Power Alarm

Environmental monitoring has detected a

QSFP+ Tx power less than or equal to the
low Tx power alarm threshold. The QSFP+
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the QSFP+.

QSFP+ Lane 3 High Bias Alarm

Environmental monitoring has detected a

QSFP+ laser bias greater than or equal to
the high laser bias alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The laser bias threshold values are
read from the QSFP+.

QSFP+ Lane 3 High Rx Power Alarm

Environmental monitoring has detected a

QSFP+ Rx power greater than or equal to
the high Rx power alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The Rx power threshold values are
read from the QSFP+.

QSFP+ Lane 3 High Temperature Alarm

Environmental monitoring has detected a

QSFP+ laser temperature greater than or
equal to the high temperature alarm
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 3 High Tx Power Alarm

Environmental monitoring has detected a

QSFP+ Tx power greater than or equal to
the high Tx power alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The Tx power threshold values are
read from the QSFP+.

QSFP+ Lane 3 Low Bias Alarm

Environmental monitoring has detected a

QSFP+ laser bias less than or equal to the
low laser bias alarm threshold. The QSFP+
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the QSFP+.

QSFP+ Lane 3 Low Rx Power Alarm

Environmental monitoring has detected a

QSFP+ Rx power less than or equal to the
low Rx power alarm threshold. The QSFP+
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the QSFP+.

QSFP+ Lane 3 Low Tx Power Alarm

Environmental monitoring has detected a

QSFP+ Tx power less than or equal to the
low Tx power alarm threshold. The QSFP+
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the QSFP+.

QSFP+ Case Low Bias Alarm

Environmental monitoring has detected a

QSFP+ bias less than or equal to the low
laser bias alarm threshold. The QSFP+ is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the QSFP+.

QSFP+ Case Low Voltage Alarm

Environmental monitoring has detected a

QSFP+ voltage less than or equal to the
low voltage alarm threshold. The QSFP+ is
the pluggable optics on the line cards. The
voltage threshold values are read from the
QSFP+.

QSFP+ Case High Bias Warning

Environmental monitoring has detected a

QSFP+ bias greater than or equal to the
high bias warning threshold. The QSFP+ is
the pluggable optics on the line cards. The
bias threshold values are read from the
QSFP+.

QSFP+ Case High Temperature Warning

Environmental monitoring has detected a

QSFP+ temperature greater than or equal
to the high temperature warning threshold.
The QSFP+ is the pluggable optics on the
line cards. The temperature threshold
values are read from the QSFP+.

QSFP+ Case High Voltage Warning

Environmental monitoring has detected a

QSFP+ voltage greater than or equal to the
high voltage warning threshold. The QSFP+
is the pluggable optics on the line cards.
The voltage threshold values are read from
the QSFP+.

QSFP+ Lane 0 High Bias Warning

Environmental monitoring has detected a

QSFP+ laser bias greater than or equal to
the high laser bias warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The laser bias threshold values are
read from the QSFP+.

QSFP+ Lane 0 High Rx Power Warning

Environmental monitoring has detected a

QSFP+ Rx power greater than or equal to
the high Rx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Rx power threshold values are
read from the QSFP+.

QSFP+ Lane 0 High Temperature Warning

Environmental monitoring has detected a

QSFP+ laser temperature greater than or
equal to the high temperature warning
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 0 High Tx Power Warning

Environmental monitoring has detected a

QSFP+ Tx power greater than or equal to
the high Tx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Tx power threshold values are
read from the QSFP+.

QSFP+ Lane 0 Low Laser Bias Warning

Environmental monitoring has detected a

QSFP+ laser bias less than or equal to the
low laser bias warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The laser bias threshold values are
read from the QSFP+.

QSFP+ Lane 0 Low Rx Power Warning

Environmental monitoring has detected a

QSFP+ Rx power less than or equal to the
low Rx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Rx power threshold values are
read from the QSFP+.

QSFP+ Lane 0 Low Temperature Alarm

Environmental monitoring has detected a

QSFP+ laser temperature less than or
equal to the low temperature alarm
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 0 Low Temperature Warning

Environmental monitoring has detected a

QSFP+ laser temperature less than or
equal to the low temperature warning
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 0 Low Tx Power Warning

Environmental monitoring has detected a

QSFP+ Tx power less than or equal to the
low Tx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Tx power threshold values are
read from the QSFP+.

QSFP+ Lane 1 High Bias Warning

Environmental monitoring has detected a

QSFP+ laser bias greater than or equal to
the high laser bias warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The laser bias threshold values are
read from the QSFP+.

QSFP+ Lane 1 High Rx Power Warning

Environmental monitoring has detected a

QSFP+ Rx power greater than or equal to
the high Rx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Rx power threshold values are
read from the QSFP+.

QSFP+ Lane 1 High Temperature Warning

Environmental monitoring has detected a

QSFP+ laser temperature greater than or
equal to the high temperature warning
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 1 High Tx Power Warning

Environmental monitoring has detected a

QSFP+ Tx power greater than or equal to
the high Tx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Tx power threshold values are
read from the QSFP+.

QSFP+ Lane 1 Low Laser Bias Warning

Environmental monitoring has detected a

QSFP+ laser bias less than or equal to the
low laser bias warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The laser bias threshold values are
read from the QSFP+.

QSFP+ Lane 1 Low Rx Power Warning

Environmental monitoring has detected a

QSFP+ Rx power less than or equal to the
low Rx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Rx power threshold values are
read from the QSFP+.

QSFP+ Lane 1 Low Temperature Alarm

Environmental monitoring has detected a

QSFP+ laser temperature less than or
equal to the low temperature alarm
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 1 Low Temperature Warning

Environmental monitoring has detected a

QSFP+ laser temperature less than or
equal to the low temperature warning
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 1 Low Tx Power Warning

Environmental monitoring has detected a

QSFP+ Tx power less than or equal to the
low Tx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Tx power threshold values are
read from the QSFP+.

QSFP+ Lane 2 High Bias Warning

Environmental monitoring has detected a

QSFP+ laser bias greater than or equal to
the high laser bias warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The laser bias threshold values are
read from the QSFP+.

QSFP+ Lane 2 High Rx Power Warning

Environmental monitoring has detected a

QSFP+ Rx power greater than or equal to
the high Rx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Rx power threshold values are
read from the QSFP+.

QSFP+ Lane 2 High Temperature Warning

Environmental monitoring has detected a

QSFP+ laser temperature greater than or
equal to the high temperature warning
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 2 High Tx Power Warning

Environmental monitoring has detected a

QSFP+ Tx power greater than or equal to
the high Tx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Tx power threshold values are
read from the QSFP+.

QSFP+ Lane 2 Low Laser Bias Warning

Environmental monitoring has detected a

QSFP+ laser bias less than or equal to the
low laser bias warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The laser bias threshold values are
read from the QSFP+.

QSFP+ Lane 2 Low Rx Power Warning

Environmental monitoring has detected a

QSFP+ Rx power less than or equal to the
low Rx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Rx power threshold values are
read from the QSFP+.

QSFP+ Lane 2 Low Temperature Alarm

Environmental monitoring has detected a

QSFP+ laser temperature less than or
equal to the low temperature alarm
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 2 Low Temperature Warning

Environmental monitoring has detected a

QSFP+ laser temperature less than or
equal to the low temperature warning
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 2 Low Tx Power Warning

Environmental monitoring has detected a

QSFP+ Tx power less than or equal to the
low Tx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Tx power threshold values are
read from the QSFP+.

QSFP+ Lane 3 High Bias Warning

Environmental monitoring has detected a

QSFP+ laser bias greater than or equal to
the high laser bias warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The laser bias threshold values are
read from the QSFP+.

QSFP+ Lane 3 High Rx Power Warning

Environmental monitoring has detected a

QSFP+ Rx power greater than or equal to
the high Rx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Rx power threshold values are
read from the QSFP+.

QSFP+ Lane 3 High Temperature Warning

Environmental monitoring has detected a

QSFP+ laser temperature greater than or
equal to the high temperature warning
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 3 High Tx Power Warning

Environmental monitoring has detected a

QSFP+ Tx power greater than or equal to
the high Tx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Tx power threshold values are
read from the QSFP+.

QSFP+ Lane 3 Low Laser Bias Warning

Environmental monitoring has detected a

QSFP+ laser bias less than or equal to the
low laser bias warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The laser bias threshold values are
read from the QSFP+.

QSFP+ Lane 3 Low Rx Power Warning

Environmental monitoring has detected a

QSFP+ Rx power less than or equal to the
low Rx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Rx power threshold values are
read from the QSFP+.

QSFP+ Lane 3 Low Temperature Alarm

Environmental monitoring has detected a

QSFP+ laser temperature less than or
equal to the low temperature alarm
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 3 Low Temperature Warning

Environmental monitoring has detected a

QSFP+ laser temperature less than or
equal to the low temperature warning
threshold. The QSFP+ is the pluggable
optics on the line cards. The temperature
threshold values are read from the QSFP+.

QSFP+ Lane 3 Low Tx Power Warning

Environmental monitoring has detected a

QSFP+ Tx power less than or equal to the
low Tx power warning threshold. The
QSFP+ is the pluggable optics on the line
cards. The Tx power threshold values are
read from the QSFP+.

QSFP+ Low Laser Bias Warning

Environmental monitoring has detected a

QSFP+ bias less than or equal to the low
laser bias warning threshold. The QSFP+ is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the QSFP+.

QSFP+ Case Low Temperature Alarm

Environmental monitoring has detected an

QSFP+ temperature less than or equal to
the low temperature alarm threshold. The
QSFP+ is the pluggable optics on the line
cards. The temperature threshold values
are read from the QSFP+.

QSFP+ Case Low Temperature Warning

Environmental monitoring has detected an

QSFP+ temperature less than or equal to
the low temperature warning threshold.
The QSFP+ is the pluggable optics on the
line cards. The temperature threshold
values are read from the QSFP+.

QSFP+ Case Low Voltage Warning

Environmental monitoring has detected a

QSFP+ voltage less than or equal to the
low voltage warning threshold. The QSFP+
is the pluggable optics on the line cards.
The voltage threshold values are read from
the QSFP+.

[chars] asic instance [dec] rccblock [chars]

ch [dec] failed on BIST[[hex]].
BIST failure

[chars] asic instance [dec] rccblock [chars]

ch [dec] failed on BIST[[hex]].
BIST failure

[chars] asic instance [dec] rccblock [chars]

BIST timedout.
BIST failure

[chars] asic instance [dec] rccblock [chars]

BIST timedout.
BIST failure

[chars] asic instance [dec] rccblock [chars]

failed on initialzation.
Hardware initialization failure

[chars] asic instance [dec] rccblock [chars]

failed on initialzation.
Hardware initialization failure

[chars].

software initialization error

[chars].

software initialization error

Warning: Timeout waiting for the shared

rwlock. The RDM client is holding shared
rwlock for too long.

The RDM server timed-out waiting to

acquire a write lock on the global (context)
read-write lock. This could happen if the
client was holding the lock for too long or
has exited. The RDM server will continue to
operate.

Lock Unavailable. Possible Reason: Other

RP trying to boot up in Normal mode.

Failed to grab lock in DR mode as the lock

is unavailable. Possible reason: Other RP
booted up in Normal mode and
permanantly grabbed the lock.

Node [chars] is not in install reload delay

phase, and it has no fabric connectivity
either

Warning the user that drp reddrv has

checked both install reload phase, and
fabric connectivity. None of the above
conditions check returns TRUE so that the
drp reddrv will follow its normal routine to
handle the case where countdown counter
reaches zero

Fabric ping not ok,check initiated for node

[hex] type [dec].

Need to print the console messagess when

the fabric ping to particular node occurs.

Collecting logs as [chars] detected partial

heartbeat loss from sc_reddrv

The indicated process detected partial

heartbeat loss for active RP/SC node's
sc_reddrv. Debug logs are collected on the
bootflash locally to help identify the the
root cause of the heartbeat loss.

Node underwent install operation and is

going to be reloaded by 'install' within
[dec] seconds

Notify node reset reason - install has

finished current install operation on the
node and would be rebooting it within
specified time. drp-reddrv should refrain
from rebooting the node until timeout
happens.

This DRP's other CPU node went down.

Reload myself.

When a CPU in DRP goes down, the other

CPU should go down as well.

Both the CPUs in DRP needs to be UP for

This DRP's other CPU node didn't come UP DRP active/standby arbitration. If one of
on time. Request shelfmgr to reset this
the CPU is UP and the other CPU is not UP,
DRP.
then request shelfmgr to reset this DRP.

primary-primary glare (primary msg from

node [hex])

There appear to be two PRIMARY RP's in the

system.

PAIR ROLE MISMATCH: call

cleanup_dead_node to reset node, my node
is [hex] my pair in local cache is [hex], my Notify the reason of node reload due to pair
pair in config is [hex]\n
role mismatch.

Failed to run heartbeat loss log collection

script - [chars]

This may be a problem with lack of

resources. The heartbeat loss log won't get
collected.

[chars]; [chars]

The sc_reddrv encountered the

annunciated SW error. The System
Manager process (sysmgr) will
automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. If the problem
continues, sysmgr will trigger node reload.
After a certain number of node reloads, the
shelf manager will permanently shutdown
the node.

Peer node [chars] failed to isolate after

crash, nodeid = [hex]

The Peer RP/SC is not isolated after node

crash. The crash node will be reset
automatically

Failed to set reboot cause into syspage,

error: [chars]

The failure on setting reboot cause to

syspage before performing Kernel Dump.

reddrv process exiting because [chars],

error code [chars]\n

The DRP redundancy driver process exited

for the reason mentioned in the message.

SC REDDRVE failed to [chars] with error :

[chars]

A general failure occured while executing a

resource function. The message contains
info about the cause of the failure and
possibly anticipated actions/effects.

Failure returned by heartbeat loss log

collection script (error code [dec])

The execution of the heartbeat loss log

collection script has failed, and the error
code is indicated in the error message.

sc-reddrv QSM node down notification send

failed as [chars] for node [chars] due to
Reddrv had problem to broadcast dead
error [chars]
node name notification.

(node [hex]) failover prevented - card role

is locked

The role of this card has been locked failover was prevented.

The particular operation mentioned in the

message has failed. As a result, the
mentioned driver on the card that puts this
Failed to [chars], error code [chars]. [chars] message will not be notified of failover of
will not be notified of switchover.\n
RP.

Unexpected:sc_reddrv failed to [chars]:

Error:[chars]

An unexpected condition encountered. This

is not necessarily an error, but may help
with debugging other problems elsewhere!

Detected conflicting criteria comparision:

[chars]

This message indicates that sc-reddrv has

a tie in defining the redundancy role.

Detected conflicting criteria comparision:

[chars]

Detected conflicting criteria.

Failed to open log file for redundancy

driver: [chars]

Failed to open log file for redundancy

driver.

Failed to open log file for redundancy

driver: [chars]

Failed to open log file for redundancy

driver.

Detected Hardware error: [chars].

Detected hardware error.

Detected Hardware error: [chars].

Detected hardware error.

Failed to punch the watchdog on time [dec] Failed to punch the watchdog timer within
seconds [dec] nanosecs
one second.

Failed to punch the watchdog on time [dec] Failed to punch the watchdog timer within
seconds [dec] nanosecs
one second.
Card is becoming active.

Card is becoming active.

Card is going to bid state.

Card is going to bid state.

Card is becoming standby.

Card is becoming standby.

The backup-dlrsc CPU inst on standby DRP

should failover ahead of the ndlrsc CPU
Active DRP's CPU node went down. Failover instance. This is done when we detech that
of backup dlrsc first.
the Active DRP's CPU node went down.

Failover of Standby DRP's (ndlrsc) CPU

instance is delayed.

When an ndlrsc CPU inst on standby DRP

failsover as active, its transition to active
state is delayed. This is done in order to
allow the dlrsc CPU instance to failover first
and thus have a predictibility in the failover
sequence among CPU instances.

Active DRP's CPU node went down. Perform When a CPU in active DRP goes down, the
Failover as I'm standby now.
standby CPU should failover as active.
Node [hex] control ethernet connection
lost, checking fabric connectivity

Control ethernet connection is lost.

Checking fabric connectivity to decide if
reset needs to be done

Active sends poision pill packet to peer

node [chars]

Active reddrv issued a poison pill packet to

reset peer RP or SC

Fabric connection set up failed: [chars]

returned [hex]

During the set up of the connection to

fabric server, one of the calls failed. This is
considered a critical failure.

Reddrv is [chars] to eth_server.

This message indicates that DRP-REDDRV's

connection to the eth_server process status
(trying to connect, connected or
disconnected) and only when connected
DRP-REDDRV is capable of sending &
receiving heartbeats or arbitration
messages

Connection to fabric on node [chars]

successful

The DRP connection through ethernet

failed, however the connection through
fabric was succesful. recommended_action:
*NONE*

Partial heartbeat loss log collection

completed

Collection of heatbeat loss log has been

completed.

This node has lost connectivity via ethernet

with the mentioned node id. An attempt is
Ethernet connection not ok to node [chars], being made (at the time of this msg) to
checking fabric connectivity
connect via fabric to the node.

No active RP detected for [dec] seconds;

resetting this node

The node on which reddrv is running,

resets itself on loss of heartbeat from the
RP.

Active [chars] reset standby peer node

[chars]

Issue hardware reset to peer standby RP or

SC.

Active [chars] reset standby peer node

[chars]

Issue hardware reset to peer standby RP or

SC.

Detected role change to [chars] state due

to [chars]

Detected role change signal.

Failed to send async message to rmf :

[chars]

This message indicates sc-reddrv failed to

send redundancy status to RMF.

Failed to send async message to rmf :

[chars]

Failed to send async message to rmf.

[chars] : [chars]

A general failure occured while executing a

resource function. The message contains
info about the cause of the failure and
possibly anticipated actions/effects.

Standby RP received kdumper keep alive

message

Reddrv has received kernel dumper

message

[chars]

Reddrv has received kernel dumper

message

Exhausted message retry count of messge Received unexpected async error message
type: [chars]
code.

Exhausted message retry count of

message type: [chars]

This message indicates that, sc-reddrv

failed to send message to peer during
redundancy role validations.

Missed heart beat acknowledge from

standby

This message indicates that, sc-reddrv

failed to receive acknowledge from
standby.

Missed heart beat acknowledge from

standby

Received unexpected async error message

code.

Received unexpected message of type:

[dec]

Received unexpected message.

reddrv_msg_handler got [dec] expected

[dec]

reddrv_msg_handler received a message of

unexpected size.

[chars] : [chars] : [chars]

Reddrv had problem to broadcast dead

node name notification.

Rejecting node [chars] reset request as its

currently in [chars] state

The arbitration state machine decided to

reset the peer node but finds it in notrunning state.Either the node is down or
trying to come up or might have been
shutdown (powered-off) due to prior
environmental or thermal issues on its
card. So, refrain from resetting such
node(s).

Resetting node [chars] for correct

active/standby arbitration

The arbitration state machine needs to be

able to reset failed nodes, or other nodes
on the same card as a failed node, in order
to ensure correct behavior of the state
machine and no mixed-role cards.

The arbitration state machine needs to be

able to reset failed nodes, or other nodes
on the same card as a failed node, in order
to ensure correct behavior of the state
Reset of node [chars] failed with error
machine and no mixed-role cards. If this
[chars] - correct active/standby arbitration fails, then arbitration may not occur
may not occur in this case
correctly.

Failed to [chars], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

The arbitration state machine determined

that the peer node or the other node on
No resetting the peer DRP with node
the same card needs to be reset but found
[chars] as one of its CPU node is in isolated the peer node or the other node is in
state.
isolated state.
Rmf registration invoked more than once

The reddrv_rmf_register function was called

multiple times

Detected role change to [chars] state due

to [chars]

Detected role change signal.

Failed to [chars] share memory region:

[chars]

Failed to create, open or size share

memory region.

Failed to [chars] share memory region:

[chars]

Failed to create, open or size share

memory region.

Detected software role error my_role: [dec]

other_role: [dec]
Detected software role error.

Detected software role error my_role: [dec] This message indicates that sc-reddrv have
other_role: [dec]
conflicts in defining the redundancy role.

Unexpected: [chars]: [chars]

An unexpected condition encountered. This

is not necessarily an error, but may help
with debugging other problems elsewhere!

Received unexpected message of type:

[dec]

This message indicates that, sc-reddrv

received unexpected message. This is a
debugging information.

Failed to open connection to control

ethernet server. Err = [chars]

The control ethernet transport connection

has been lost due to which send/receive for
this process over the control ethernet will
not work. This impacts standby RP booting.

This is indicative of some very fundamental

problem in the the system. Some very
Platform call to determine boardtype failed basic system initialization has failed.

I2C access to read backplane EEPROM

failed

This is indicative of some very fundamental

problem in the the system. I2C access to
the backplane not working could be due to
an I2C hang.

Failed to connect to I2C server

I2C service is currently unavailable.

Failed async_free_buff control ethernet

server

The control ethernet transport buffer

problem due to which send/receive for this
process over the control ethernet will not
work. This impacts standby RP booting.

Failed async_get_buff control ethernet

server

The control ethernet transport buffer

problem due to which send for this process
over the control ethernet will not work. This
impacts standby RP booting.

Failed async_get_client_start control

ethernet server. Err = [chars]

The control ethernet transport buffer

problem due to which send/receive for this
process over the control ethernet will not
work. This impacts standby RP booting.

The control ethernet transport buffer

problem due to which send/receive for this
Failed async_get_src_mac control ethernet process over the control ethernet will not
server ERR = [chars]
work. This impacts standby RP booting.

Failed to send reply. Err = [dec]

Failed to send reply to client ROMMON.

[chars]

Failure in Resource Manager Proxy resulting

in error condition %s - indicates the reason
of the failure.

Unable to allocate memory

Failure in Resource Manager Proxy memory

allocation error occurred

[chars]

--

Failed to program [chars].

An error occurred during the rom

programming that caused the operation to
fail.

Board booted using ROMMON A, upgrade

ROMMON B to recover
Bad command option: [chars] [chars]

Rommon A is the backup rom image. The

board will use this image to boot if the
primary (Rommon B) image is corrupted.
The corruption can be fixed by upgrading
the primary (Rommon B) image. When the
board is in this state there is no longer a
failsafe mechanism - further rommon
corruption could require an RMA of your
board.
Bad coammand option.

[chars]: [chars] in function [chars] at line

[dec]

Error occured with file operations.

Failed in allocating memory in function

[chars] at line [dec]

No enough memory.

ROMA can't be burned when it's the boot

Cannot burn ROMA while ROMA is the boot rom because a failure during a burn would
ROM.
render the board inoperable.
[chars] [chars]
Output progress to RP console.
ROMMON version [dec].[dec] is not
supported for this board.

Invalid ROMMON version to RP console.

CPU control FPGA FC_I2C_ERROR_OR_TO

error

Error reported by the cpu control fpga

CPU control FPGA I2C_ERROR error

Error reported by the cpu control fpga

CPU control FPGA I2C_ERROR_2 error

Error reported by the cpu control fpga

CPU control FPGA I2C_TIMEOUT error

Error reported by the cpu control fpga

CPU control FPGA I2C_TIMEOUT_2 error

Error reported by the cpu control fpga

CPU control FPGA PCIE_RESP_FIFO_SBE

error

Error reported by the cpu control fpga

CPU control FPGA PCIE_TX_FIFO_SBE error

Error reported by the cpu control fpga

CPU control FPGA PCIE_TXIF_FIFO_SBE error Error reported by the cpu control fpga

RSP CPU controller driver detected board

revision mismatch

RSP CPU controller driver version is not

compatible with the current Board.

RSP CPU controller driver detected board

revision parity error

RSP CPU controller driver detected a board

revision parity error.

RSP DAO FPGA program error

RSP DAO FPGA program failure with latest

FPGA version. FPGA is programmed with
golden image version.

RSP CPU controller driver version is not

compatible with the hardware version.
[chars]

RSP CPU controller driver version is not

compatable with the hardware version.

RSP DTI FPGA program error

RSP DTI FPGA program failure with latest

FPGA version. FPGA is programmed with
golden image version.

RSP FPD FPGA load error

One of more FPGAs on the RSP has failed to

load the latest image.

RSP CPU controller driver version is not

RSP CPU controller driver PCB version error compatible with the current Board.

CPU controller driver detected peer parity

error

RSP CPU controller driver detected peer

RSP parity error.

RSP CPU controller has detected slot id

RSP CPU controller driver detected a slot id parity. This could be possible if RSP is not
parity error
seated properly.
CPU control FPGA ARB_ECTW_RD_PERR
error

Error reported by the cpu control fpga

CPU control FPGA

ARB_ECTW_RDATA_ACKERR error

Error reported by the cpu control fpga

CPU control FPGA ARB_ECTW_RDATA_TO

error

Error reported by the cpu control fpga

CPI self to LC status incorrect

No RSP is detected in the system by the

LC. Most likely bad board.

CPU control FPGA

PCIE_CORE_ERROR_OVERRUN error

Error reported by the cpu control fpga

CPU control FPGA

PCIE_CORE_ERROR_OVERRUN_2 error

Error reported by the cpu control fpga

CPU control FPGA PCIE_FATAL error

Error reported by the cpu control fpga

CPU control FPGA PCIE_RESP_FIFO_MBE

error

Error reported by the cpu control fpga

CPU control FPGA PCIE_TX_FIFO_MBE error Error reported by the cpu control fpga
CPU control FPGA PCIE_TXIF_FIFO_MBE
error

Error reported by the cpu control fpga

CPU control FPGA SAC0_ECTW_RD_PERR

error

Error reported by the cpu control fpga

CPU control FPGA

SAC0_ECTW_RDATA_ACKERR error

Error reported by the cpu control fpga

CPU control FPGA SAC0_ECTW_RDATA_TO

error

Error reported by the cpu control fpga

CPU control FPGA SCI_CRAM_SBE_ERR error Error reported by the cpu control fpga
CPU control FPGA SFP_ACK_ERR error

Error reported by the cpu control fpga

CPU control FPGA SFP_TIMEOUT error

Error reported by the cpu control fpga

CPU control FPGA SKT_ECTW_RD_PERR

error

Error reported by the cpu control fpga

CPU control FPGA

SKT_ECTW_RDATA_ACKERR error

Error reported by the cpu control fpga

CPU control FPGA SKT_ECTW_RDATA_TO

error

Error reported by the cpu control fpga

[chars] - [dec]: [chars]

Error in RUNA operation.

[chars] - [dec]: [chars] (rc = [hex])

Error in RUNA operation.

An error was previously encountered while

initializing one of modules of the rwmgr
RwString Manager succeeded in initializing server. However, the initialization was
the [chars] module upon retry.
retried and succeeded.

Failed to initialze RwString Manager:

[chars]

This syslog is printed when RwString

Manager or its clients fail to initialize
necessary data structures and memories. If
the error originates from the system call
the error message is also printed.

Failed to allocate memory: [chars]

An explanation is provided in the syslog.

An error was encountered while initializing

one of the modules of configuration
manager server. The failure of this module
RwString Manager was unable to initialize initialization is not critical to configuration
the [chars] module. Error: '[chars]'. [chars]. manager to be completely operational.

[chars] Error:[chars]

This is a non-fatal error and can happen

when router is low on memory. It should
not affect the functioning of the router, but
trace messages may not be logged.

[chars]

An unexpected internal error occurred in

the rwmgr subsystem.

satori get board type failed

Satori get board type has failed and it

might not boot up

[chars]

Procmgr encountered an error during

initialization resulting in restarting the
Procmgr process. This may be a program
level error. The failure will cause the
Procmgr process to restart.

[chars]

Ltrace initialization failed. This may be a

program level error.

pcie_attach failed

pcie attach has failed and process will

respawn

[chars]

Satori RP Kensho-JF CPU Subsystem DLL

warning message. No system functional
impact.

[chars]

Informational Satori RP Kensho-JF CPU

Subsystem DLL message.

Timer set time failed

It is an informational message indicating

that set time has failed, this may be a
program level issue

Failed Identification Test in [chars] [[dec]/

[dec]]\n The module in [chars] in this router
may not be a genuine Cisco product. Cisco
warranties and support programs only
apply to genuine Cisco products. If Cisco
determines that your insertion of non-Cisco
SPA cards or other modules into a Cisco
product is the cause of a support issue,
Cisco may deny support under your
'Hardware in the specified location could
warranty or under a Cisco support program not be identified as a genuine Cisco
such as SmartNet.\n\n
product'
Failed Identification Test in [chars] [[dec]/
[dec]]\n

'There was a problem while identifying

Hardware in the specified location.'

Module ([chars]) is a registered proto-type 'Hardware in the specified location is a

for Cisco Lab use only, and not certified for proto-type module that came from a Cisco
live network operation.\n
Lab'

The ethernet driver cannot get I/O

privileges

The ethernet driver is unable to get the

necessary privileges to perform an
operation vital to its functionality.

This log indicates that SCF server was not

Failed to initialize SCF server tracing, error: able to initialize tracing. As result of this
[chars]
error, SCF server will not have any tracings.

[chars]

An error occurred in the event loop. It may

be possible to rectify it by restarting the
process.

'Failed to block on event, quitting'

An error occurred in the event loop and

there is a failure in event blocking. The SE
P2MP_SRVR will restart by itself.

A critical error occured during the

initialization of SE P2MP_SRVR process
which involves exiting the process. The SE
P2MP_SRVR will restart and unless the
same error occurs on the next attempt the
SE P2MP_SRVR will function normally. If the
error is persistent, it indicates the system
error or HW error which needs further
'APP is not up in the SMDC: [chars], with rc investigation. The cause of the error will be
[hex]'
mentioned in the message displayed.

'Server attach event handlers failed:

[chars]: with rc [hex]'

A critical error occured during the

initialization of SE P2MP_SRVR process
which involves exiting the process. The SE
P2MP_SRVR will restart and unless the
same error occurs on the next attempt the
SE P2MP_SRVR will function normally. If the
error is persistent, it indicates the system
error or HW error which needs further
investigation. The cause of the error will be
mentioned in the message displayed.

A critical error occured during the

initialization of SE P2MP_SRVR process
which involves exiting the process. The SE
P2MP_SRVR will restart and unless the
same error occurs on the next attempt the
SE P2MP_SRVR will function normally. If the
error is persistent, it indicates the system
error or HW error which needs further
investigation. The cause of the error will be
'EVM creation failed: [chars], with rc [hex]' mentioned in the message displayed.

'Failed to get plim type: [chars], with rc

[hex]'

A critical error occured during the

initialization of SE P2MP_SRVR process
which involves exiting the process. The SE
P2MP_SRVR will restart and unless the
same error occurs on the next attempt the
SE P2MP_SRVR will function normally. If the
error is persistent, it indicates the system
error or HW error which needs further
investigation. The cause of the error will be
mentioned in the message displayed.

Failed to get response from cores: [chars]

Some or all the cores didn't respond for a

configuration.

[chars]: [chars]

Encountered an error in debug module.

This error should not impact the major
functionality of the module.

'Failed to initialize debug module: [chars]'

Encountered an error in debug module.

This error should not impact the major
functionality of the module.

Encountered an error in debug module.

This error should not impact the major
'Failed to shutdown debug module: [chars]' functionality of the module.

Failed to [chars] [chars] DLL: [chars]

An error occurred while trying to open or

initialize a DLL. The process will be
restarted.

An error occurred while trying to open or

initialize a DLL. The process will be auto'Failed to initialize Service Engine IPC DLL: restarted. If the error is persistent, it
[chars]'
indicates the system error.

p2mp server process will exit because

[chars]

An error occurred in the event loop. p2mp

server process will exit.

[chars]: [chars]: [hex]

A critical error occured during the

initialization of SE P2MP_SRVR process
which involves exiting the process. The SE
P2MP_SRVR will restart and unless the
same error occurs on the next attempt the
SE P2MP_SRVR will function normally. If the
error is persistent, it indicates the system
error or HW error which needs further
investigation. The cause of the error will be
mentioned in the message displayed.

p2mp server process will exit because

[chars], ERR: [chars]: [hex]

A critical error occured during the

initialization of SE P2MP_SRVR process
which involves exiting the process. The SE
P2MP_SRVR will restart and unless the
same error occurs on the next attempt the
SE P2MP_SRVR will function normally. If the
error is persistent, it indicates the system
error or HW error which needs further
investigation. The cause of the error will be
mentioned in the message displayed.

Error encountered tracing for [chars]:

[chars]

Encountered an error in tracing module.

This error should not impact the major
functionality of the module.

'Error encountered tracing for [chars]:

[chars]'

Encountered an error in tracing module.

This error should not impact the major
functionality of the module.

se_cgn_pd failure due to: [chars] [chars]

Error occured while processing messages

from PI or in allocating memory.

Transmit error on port [dec], error code

[hex]

A transmit fault occurred at the physical

layer on the port. It is an indication of fault
in MAC/Serdes/Module. In most cases, the
fault would bring the link down and cause
complete traffic drop.

Receive error on port [dec], error code

[hex]

A receive error occurred at the physical

layer of the port. It can be a transient selfclearing error when a port is admin
shutdown or enabled. Else, it is an
indication of a fault on the line. In most
cases, the fault would bring the port link
down and cause complete traffic drop. In
case the link is still up, there may be
intermittent packet drops due to encoding
errors in packets received.

Service Agent event loop thread will quit

because [chars]

An error occurred in the event loop. It may

be possible to rectify it by restarting the
process.

Services Agent process will exit because

[chars]:[chars]:[hex]

A critical error occured during the

initialization of Service Agent process
which involves exiting the process. The
Service Agent will restart and unless the
same error occurs on the next attempt the
Service Agent will function normally. If the
error is persistent, it indicates the system
error or HW error which needs further
investigation. The cause of the error will be
mentioned in the message displayed.

'Failed: [chars]'

Associating block with a file descriptor.

'Memory operation fail: [chars]'

The message indicates malloc failure while

allocating block.

'Event: [chars]'

Service Interface Server related

provisioning info.

SFP Module for port [dec] is not Cisco

compliant

A compliance error was detected during

SFP initialization. A compliance error is due
to unsupported optics, checksum error,
EEPROM CRC error, vendor data error, or
decryption error. The SFP is the pluggable
optics on the line cards. SFP initialization
may happen when linecard boots up, SFP
OIR and line card process restart. The
optics will not be enabled if an SFP
compliance error is detected.

SFP Module for port [dec] is not supported

A SFP Module not supported for the port

error was detected during SFP initialization.
A SFP Module not supported for the port
error is reported when Optics is not
supported on the port. The SFP is the
pluggable optics on the line cards. SFP
initialization may happen when linecard
boots up, SFP OIR and line card process
restart. Traffic will not be impacted by this
error.

SFP Module for port [dec] is not a

supported module type

A supported error was detected during SFP

initialization. A support error is reported
when the SFP type can not be determined
or it is not supported on the platform. The
SFP is the pluggable optics on the line
cards. SFP initialization may happen when
linecard boots up, SFP OIR and line card
process restart. The optics will not be
enabled if an SFP supported error is
detected.

SFP High Laser Bias Alarm

Environmental monitoring has detected an

SFP laser bias greater than or equal to the
high laser bias alarm threshold. The SFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the SFP.

SFP High Rx Power Alarm

Environmental monitoring has detected an

SFP Rx power greater than or equal to the
high Rx power alarm threshold. The SFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the SFP.

SFP High Temperature Alarm

Environmental monitoring has detected an

SFP temperature greater than or equal to
the high temperature alarm threshold. The
SFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the SFP.

SFP High Tx Power Alarm

Environmental monitoring has detected an

SFP Tx power greater than or equal to the
high Tx power alarm threshold. The SFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the SFP.

SFP High Voltage Alarm

Environmental monitoring has detected an

SFP voltage greater than or equal to the
high voltage alarm threshold. The SFP is
the pluggable optics on the line cards. The
voltage threshold values are read from the
SFP.

SFP Low Laser Bias Alarm

Environmental monitoring has detected an

SFP laser bias less than or equal to the low
laser bias alarm threshold. The SFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the SFP.

SFP Low Rx Power Alarm

Environmental monitoring has detected an

SFP Rx power less than or equal to the low
Rx power alarm threshold. The SFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
SFP.

SFP Low Tx Power Alarm

Environmental monitoring has detected an

SFP Tx power less than or equal to the low
Tx power alarm threshold. The SFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
SFP.

SFP Low Voltage Alarm

Environmental monitoring has detected an

SFP voltage less than or equal to the low
voltage alarm threshold. The SFP is the
pluggable optics on the line cards. The
voltage threshold values are read from the
SFP.

SFP Module for port [dec] is not a

supported Product ID (PID)

A PID not supported error was detected

during SFP initialization. A PID not support
error is reported when either the PID can
not be read or not supported on the
platform. The SFP is the pluggable optics
on the line cards. SFP initialization may
happen when linecard boots up, SFP OIR
and line card process restart. The optics
will not be enabled if a PID not supported
error is detected.

SFP High Laser Bias Warning

Environmental monitoring has detected an

SFP laser bias greater than or equal to the
high laser bias warning threshold. The SFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the SFP.

SFP High Rx Power Warning

Environmental monitoring has detected an

SFP Rx power greater than or equal to the
high Rx power warning threshold. The SFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the SFP.

SFP High Temperature Warning

Environmental monitoring has detected an

SFP temperature greater than or equal to
the high temperature warning threshold.
The SFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the SFP.

SFP High Tx Power Warning

Environmental monitoring has detected an

SFP Tx power greater than or equal to the
high Tx power warning threshold. The SFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the SFP.

SFP High Voltage Warning

Environmental monitoring has detected an

SFP voltage greater than or equal to the
high voltage warning threshold. The SFP is
the pluggable optics on the line cards. The
voltage threshold values are read from the
SFP.

SFP Low Laser Bias Warning

Environmental monitoring has detected an

SFP laser bias less than or equal to the low
laser bias warning threshold. The SFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the SFP.

SFP Low Rx Power Warning

Environmental monitoring has detected an

SFP Rx power less than or equal to the low
Rx power warning threshold. The SFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
SFP.

SFP Low Temperature Alarm

Environmental monitoring has detected an

SFP temperature less than or equal to the
low temperature alarm threshold. The SFP
is the pluggable optics on the line cards.
The temperature threshold values are read
from the SFP.

SFP Low Temperature Warning

Environmental monitoring has detected an

SFP temperature less than or equal to the
low temperature warning threshold. The
SFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the SFP.

SFP Low Tx Power Warning

Environmental monitoring has detected an

SFP Tx power less than or equal to the low
Tx power warning threshold. The SFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
SFP.

SFP Low Voltage Warning

Environmental monitoring has detected an

SFP voltage less than or equal to the low
voltage warning threshold. The SFP is the
pluggable optics on the line cards. The
voltage threshold values are read from the
SFP.

Error detected while decoding Shelf

Manager client TLV message - [chars]

This message indicates that Shelf Manager

TLVLIB failed to decode the TLV message.

Shelf Manger API TLV Library init failed for

[chars] - [chars]

This message indicates that Shelf Manager

TLVLIB init operation has failed.

One or more of the memory module (DIMM) One or more the Memory Module in the
in the VSM ([chars]) is down
card is not detected or having errors.

The power module drivers have not

reported ready after [dec] seconds.

The power module drivers have not

reported any available power supply
budget for the chassis. Since the power
budget of the system is unknown the
shelfmgr is unable to bootup line cards.

The shelfmgr could not finish initialization

after [dec] seconds due to config load
timeout.

The shelfmgr could not fully initialize due

to not receiving indication of the loading of
the router running config having
completed. If this error happens line cards
may not be booted by shelfmgr.

Failed to validate Peer RSP removal. Peer

slot: [dec]

This error can happen if the active RSP or

its peer RSP is improperly seated in the
chassis.

The shelfmgr could not initialize its card

presence drivers after [dec] seconds.

The shelfmgr could not initialize its card

presence drivers. This can be caused by an
improperly seated RSP card, or damage to
the backplane pins.

Shelfmgr received incorrect presence

indication for this RSP slot.

Shelfmgr received incorrect presence

indication for this RSP slot.

One or more of the CPUs in the

VSM([chars]) is down

One or more the CPUs in the card is not

detected or having errors.

The card type read from the CAN Bus is not

recognized to be valid. The shelfmgr will
not bootup this card. The 'show platform'
[chars] card type [dec] from slot [dec] CBC CLI will not show a card for this slot.

Can API: [chars]

The shelfmgr could not initialize its CAN

Bus Interface, due to the reason mentioned
in the message. The shelfmgr will attempt
to recover by restarting up to 5 times. If
the issue persists, the RSP will be reset
which will cause the standby RSP to take
over as active.

[chars]

The shelfmgr could not initialize its

interface to the slot presence detection
driver, due to the reason mentioned in the
message. The shelfmgr will attempt to
recover by restarting up to 5 times. If the
issue persists, the RSP will be reset which
will cause the standby RSP to take over as
active.

[chars] CBC processor is offline.

The node CAN Bus Controller is currently

offline. Operations such as environmental
monitoring, hardware power control and
card reset may be impaired.

'The power needed for shelf equipment

System power usage [chars] power supply exceeds the capability of the currently
ratings. [chars]
installed power supplies.'

[chars] power to support V2 fan trays

'The power needed for next V2 fantray

exceeds the capability of the currently
installed power supplies.'

Power Feed Failures [chars] protected.

The router will have insufficient power to

sustain traffic in the event of an AC power
feed failure.

The shelfmgr power requirement is invalid The shelfmgr power requirement for the
for card [hex]
given card type is incorrect

Power Requirement not defined for card

type [hex]

The card type read from the CAN Bus is not

recognized to be valid. The shelfmgr will
not bootup this card. The 'show platform'
CLI will not show a card for this slot.

Power Supply Failures [chars] protected.

The router will have insufficient power to

sustain traffic in the event of a power
supply module failure.

Boot Request from [chars], RomMon

Version: [dec].[dec]

Logging the Boot Request Rommon Version

Shelfmgr Card Power Cycle Initiated,

[chars]

The Shelf Manager component has

requested power restart on a line card or
secondary RSP.

The Shelf Manager component has

requested power disable on a line card or
Shelfmgr Card Powerdown Initiated, [chars] secondary RSP.

Shelfmgr Card Powerup Initiated, [chars]

The Shelf Manager component has

requested powerup on a line card or
secondary RSP.

Shelfmgr Card Shutdown, [chars], [chars]

The Shelf Manager component has initiated

a shutdown of a line card or standby RSP.

Cold system bootup on [chars]

In recovery from a system restart, a

powercycle has been successfully initiated
on this slot.

Driver returned inconsistent standby RSP

card presence data. This error might be
Peer card presence inconsistency detected. observed due to a slow removal of the
Peer slot: [dec]
active RSP.

Periodic sanity heartbeat messages from

the line card have not been received. This
is just an alert. If the problem continues a
heartbeat failure message will be
generated and the shelfmgr will attempt
[chars] heartbeat, non-responsive for [dec] recovery by resetting the affected card or
seconds. (Threshold: [dec] seconds),
automatically attempting an RSP failover if
Send/Rcv Seq#: [dec]/[dec]
needed.
Periodic sanity heartbeat messages from
the reported node have not been received.
[chars] heartbeat, non-responsive for [dec] The shelfmgr will attempt recovery by
seconds. (Threshold: [dec] seconds),
resetting the affected card or automatically
Send/Rcv Seq#: [dec]/[dec]
attempting RSP failover if needed.

Power cannot be allocated to node [chars].

[dec] Watts Required, [dec] Watts
'The power required for this card exceeds
Available.
the available power on this system.'
Invalid Boot Request from [chars] rejected. An invalid request to initiate MBI download
[chars]
has been received and therefore rejected.

Can API: slot [dec] [chars] event.

This message indicates CAN bus

information related to on-line/off-line CBC
processor transitions.

Card presence status retrieval failed

The card presence indication driver failed

to return requested status to shelfmgr. The
shelfmgr periodically audits the card
presence driver in an attempt to recover
from any such errors.

Card Bringup: Reboot card to keep Node:

This message indicates that this node was
[hex][[chars]] in the IN-RESET state, Reset parked in the in-reset state due to the
Code: [dec]
reason specified.
CHASSIS SHUTDOWN initiated due to
[chars]\n

Chassis is shutting down due to reason

mentioned.

CRITICAL: CHASSIS SHUTDOWN initiated

due to [chars]\n

Chassis is shutting down due to reason

mentioned.

This message is generated when the node

has failed to boot up repeatedly and
Node [chars] [chars] has reset itself in
indicated to the shelfmgr that the node
multiple ([dec]) unsuccessful boot
reset itself each time. Therefore shelfmgr
attempts, putting it IN_RESET state. The
eventually holds the node IN_RESET state
probable cause is an unexpected event on until a manual reboot request is issued
the node. Please Refer to the Cisco ASR
against it by the user. The probable cause
9000 System Error Message Reference
is an unexpected error on the node leading
Guide for further information if needed.
to the repeated boot failures.

This message indicates that the node has

reached the maximum number of resets
allowed, without successful recovery to
reach or stay at the IOS XR RUN state.
Therefore, it is brought down to IN_RESET
Can not boot node [chars] [chars] due to
state. The probable causes of the error are
multiple resets, putting it IN_RESET state. either an unexpected error on the node
The probable cause is an unexpected event causing it to reset itself, or a failure in the
on the node or a failure in communication expected communication between the
with the node. Please refer to the Cisco
node and the shelfmgr, leading the
ASR 9000 System Error Message Reference shelfmgr to reset the node in an attempt to
Guide for further information if needed.
have it recover.

Critical Alarm: Alarm [chars] because

[chars]

Two possibilities to this message 1) An

alarm has occured. Software cannot access
all fans from all trays. This could be caused
by fan tray loss power or individual fans
were not running. User will have 45
seconds to replace a fan tray. If no action is
taken within 45 seconds, the chassis will be
shut down. 2) A previously occured alarm
has been cleared. Software has detected
that all fan on all trays failed condition is
cleared

Critical Alarm: Alarm [chars] because

[chars]

Two possibilities to this message 1) An

alarm has occured. Software has detected
that all fan trays have been removed from
the chassisbut, but gives user 45 seconds
to insert another tray. If no action is taken
within 45 seconds, the chassis will be shut
down. 2) A previously occured alarm has
been cleared. Software has detected that
all fan trays were removed which would
have shut down the system. But one fan
tray was put back within 45 seconds, thus
removing the need to shut down the
system.

Alarm [chars] because [chars]

Two possibilities to this message 1) An

alarm has occured. Software has detected
that both fan controller cards have been
removed from the chassis but, but gives
user 45 seconds to insert atleast one of
them back into the chassis. If no action is
taken within 45 seconds, the chassis will be
shut down. 2) A previously occured alarm
has been cleared. Software has detected
that both fan controller cards were
removed which would have shut down the
system. But one fan controller was put
back within 45 seconds, thus removing the
need to shut down the system.

Atleast one tray has been inserted within

45 seconds (of removing all trays), so the
chassis will not be shut down\n

Software has detected that all fan trays

were removed which would have shut
down the system. But one fan tray was put
back within 45 seconds, thus removing the
need to shut down the system.

This message indicates that the node has

Power off node [chars] due to multiple
being brought down to IN_RESET state due
critical alarms, putting into IN_RESET state to multiple critical alarms.

[chars]

The system has attempted to powerup the

target node, however the system does not
have the electrical power needed to
execute the request.

[chars] linecards and fabric cards due to

low voltage warning [chars] from power
shelves\n

Received message from environment

monitor that the voltage is low on the
power shelves. So we are shutting down
linecards and fabric cards to prevent
damage to these boards.

Critical Alarm: All fan trays have been

removed from the chassis. If at least one
tray is not inserted within 45 seconds, the
chassis will be shutdown

Software has detected that all fan trays

have been removed from the chassisbut,
but gives user 45 seconds to insert another
tray. If no action is taken within 45 seconds,
the chassis will be shut down.

Remote node notified shelfmgr about its

Node [chars] about to reboot due to cause software reboot with the reboot reason and
code:[hex], [chars]
cause code.
Shutdown node [chars] since CRS-DRP is
not supported on CRS-4-CH

This message indicates that the node is

being shutdown because it is not supported
on the CRS-4 platform.

Shutdown node [chars] since CRS-DRP is

not supported on CRS-4-CH

This message indicates that the node is

being shutdown because it is not supported
on the CRS-4 platform.

This message indicates that the node is

Shutdown node [chars] since CRS-[chars] is being shutdown because it is not supported
not supported on CRS-[chars]'s slot [dec]
on the specified CRS platform.
The Shelfmgr failed to restore its
Error restoring the Shelfmgr Checkpointed checkpoint memory on a process restart or
memory, rc=[hex]([chars])
transition from stby to act.

Attempting to restore unknown Shelfmgr

Chkpt Memory

The Shelfmgr encountered unexpected

checkpoint memory

Can not restore checkpoint for the HB

Monitor DB for nodeid: [hex], slot: [dec],
RecIndex: [dec], rc=[hex] ([chars])

Shelfmgr API call to update the HB Monitor

database failed.

The DRP [chars] is shutdown as it is in the

LR [chars] which has X86 RP in it.

This message indicates that the DRP and

some X86 RP are in the LR, so the DRP is
shutdown.

Received boot request from a RP with an

empty rack serial number, which indicates
an attempt to boot a RP with ROMMON
v1.19x as the standby. Boot request is
being failed ! Refer to customer
documentation for configuring a boot
override

Shelfmgr is failing a boot request because

the serial number string in the boot request
is empty. This happens if a RP with
ROMMON 1.19x or older is sending a boot
request.

Received boot request from a RP with an

empty rack serial number, which indicates
an attempt to boot a RP with ROMMON
v1.19x as the standby. Boot request is
being failed ! Refer to customer
documentation for configuring a boot
override

Shelfmgr is failing a boot request because

the serial number string in the boot request
is empty. This happens if a RP with
ROMMON 1.19x or older is sending a boot
request.

Node [chars] fails to load IOS XR image,

request to reset ...

This message indicates that the node failed

to load the IOS XR image for maximum
number of retries and will be reset.

Node [chars] fails to load IOS XR image,

request to reset ...

This message indicates that the node failed

to load the IOS XR image for maximum
number of retries and will be reset.

This message indicates the board in named

Unable to power up slot [chars], request to slot failed to power up. The node will be
reset. reason: [chars]
reloaded automatically.

Node [chars] is reset due to failed bootup.

Node state was: [dec] Timeout ID: [dec]

This message indicates that the node is not

able to boot up

This message indicates that the node was

in an isolated state from the rest of router
Node [chars] is reset due to excessive time for too long. The recovery action is taken
in isolation. Node state was: [dec] Timeout automatically by shelf manager at this
ID: [dec]
point by rebooting the affected node.

Node [chars] is reset because of failure to

send boot request within [dec] seconds

This message indicates that the node is not

able to boot up. This is because the timer A
has expired on this node before any boot
request was recieved by shelfmgr from this
node, after the node has reached the
ROMMON state.

This message indicates that the node is not

able to boot up. This is because no mbiNode [chars] is reset because no mbi-hello hello heartbeat has been recieved by
heartbeat has been received within [dec]
shelfmgr within the time specified by timer
seconds.
B.

Node [chars] is reset because no XR-hello

has been received within [dec] seconds

This message indicates that the node is not

able to boot up. If an XR-hello is not
recieved within a specified time limit, then
the node will go to ENA-FAILURE.

This message indicates that the node is not

able to boot up after a warm reload. If an
Node [chars] is reset because no MDR-mbi- MDR-mbi-hello is not recieved within a
hello has been received within [dec]
specified time limit, then the node will go
seconds
to ENA-FAILURE.

[chars]

This FC type is not supported in this chassis

type for the ASR9K family of chassis as it is
incompatible to the chassis hardware
architecture for traffic carrying purposes.
Shelf manager raises this alarm when it
detects the presence of the incompatible
FC and clears the alarm when the FC is no
longer seen as being present.

[chars]

This LC type is not supported in this chassis

type for the ASR9K family of chassis as it is
incompatible to the chassis hardware
architecture for traffic carrying purposes.
Shelf manager raises this alarm when it
detects the presence of the incompatible
LC and clears the alarm when the LC is no
longer seen as being present.

Node [chars] is not supported on chassis.

This RP type is not supported in this

chassis type for the ASR9K family of
chassis as it is incompatible to the chassis
hardware architecture for traffic carrying
purposes. Shelf manager raises this alarm
when it detects the presence of the
incompatible RP.

Cannot boot node [chars] due to multiple

resets, putting into IN_RESET state

This message indicates that the node has

reached maximum number of resets
allowed, therefore, it is brought down to
IN_RESET state.

Boot request from node [chars] contains

invalid board type, This board is being
shutdown, moved to the IN_RESET state

This message indicates that the board type

cannot be recognized, therefore, the node
will not be able to boot up. This usually
caused by an invalid eeprom content.

ERR: Can not retrieve my node: rc=[hex]

([chars]), Bringdown Req [dec] not process
for NodeID: [hex], State: [dec]
API Call to nodeid_extract_fields() failed.
Can not decode nodeID: [hex], RecIndex:
[dec], rc=[hex] ([chars])

API Call to nodeid_extract_fields() failed.

A boot request sent to shelfmgr on rack

[dec] (rack type [dec]) is ignored as it
contains invalid slotId [dec] with card type
[chars] ([hex]). Possible seating issue.
Please reseat the suspected card(s).

This message indicates that the slot Id in

the boot request from rommon to shelfmgr
is invalid, therefore ignore the boot
request.

This message indicates that the node was

Node [chars]'s local reboot timed-out while expected to reboot locally but that did not
being in [chars] state. Power-cycle it to
happen. Hence it should be power-cycled
recover.
by ShelfMgr to avoid any issue(s).

System [chars] mixed line card memory

mode

System enters/exits mixed line card

memory mode, as a result of powering up
or removing a line card of different memory
configuration.

Node [chars] is manually brought up.

System in mixed line card memory mode

Target node is brought up by 'admin hwmodule reload' command. System

operating in mixed line card memory
mode, which is only supported temporily
during line card upgrade or downgrade.

Node [chars] is powered, system running

mixed line card memory mode

Target node is brought up because it is up

previously. System operating in mixed line
card memory mode, which is only
supported temporily during line card
upgrade or downgrade.

The system has attempted to power up the

target node. However executing the
request results chassis operating in mixed
Node [chars] is shut, due to conflicting line line card memory mode. Node is not
card memory mode
powered.

Combination of both the RP in the chassis

is not supported, Active Cardtype: [hex],
Standby Cardtype: [hex]

This combination of RP type is not

supported in this chassis type for the
ASR9K family of chassis as in mixed mode
they are incompatible to the chassis
hardware architecture for traffic carrying
purposes. Shelf manager raises this alarm
when it detects the presence of the
incompatible combination of RP.

This message indicates that threads of

shelfmgr were not able to communicate via
Restarting shelfmgr. Failed to send intra
async pulses. Restarting shelfmgr to
thread async pulse because [chars] ([dec]). recover.

This message indicates that there was an

unexexpected error within the shelfmgr
database where the Node Db was not
Unexpected Node DB creation error, Node: found, or could be created. This causes the
[chars][[hex]], evt not processed: [chars]
shelfmgr not processed the event that it
[[dec]]
just received.

Node [chars]'s kernel started to dump

This message indicates that the node's

kernel is dumped to local harddisk or RP's
harddisk.

Reset node [chars] due to timeout in

completing kernel dump.

This message indicates that the node is

being reset because it failed to reset itself
in time while in kernel dump. This means
the kernel dump files that the node
transported to the active RP, could be
incomplete.

Node [chars] in critical alarms, request to

reset ...

This message indicates that the Shelf

Manager or Platform Manager encountered
a critical alarm for the node specified. It
will attempt to reset the board which sends
the alarm.

Node [chars] in critical alarms, request to

reset ...

This message indicates that the Shelf

Manager or Platform Manager encountered
a critical alarm for the node specified. It
will attempt to reset the board which sends
the alarm.

Reset node [chars] due to heartbeat loss

This message indicates that the node is

being reset because it failed to detect
heartbeat pulses.

Reset node [chars] due to heartbeat loss

This message indicates that the node is

being reset because it failed to detect
heartbeat pulses. Please check for any
reboot reasons for the node printed on the
console or shown in the show reboot
history reverse CLI.

This message indicates that the Shelf

Manager, If receive 100 consecutive HB's
from a card, and our OIRd info still says this
card NOT_PRESENT, then the card is
Warning: Partially inserted card [chars] due probably only partially inserted. Send out
to absences in OIR detection and heartbit an ios_msg informing the user of the
counter has reached its limit: [dec]
situation.

Node [chars] is powered off due to admin

power off request

This message indicates that the node will

be reset because user has administratively
'power disable' or 'no power disable' the
node.

Node [chars] is reset through power off,

then power on

This message indicates that the node is

being reloaded on account of critical
fault/alarm detected on the node.

shelfmgr failed to get rack number from

DSC for the rack with serial ID [chars], so
the rack could not be booted up. A possible This message indicates that there is no
cause is that the dsc rack serial ID to rack rack serial ID to rack number mapping
number mapping is not configured.
configuration and a rack is trying to boot.

i2c_server on node [chars] requested

node's reset due to failure: [chars]

This message indicates that the I2C server

on the specified node encountered the
specified failure. Shelfmgr will attempt to
reset the board which sends the alarm.

RP SHUTDOWN INITIATED due to thermal

alarms\n

RP is shutting down due to reason

mentioned.

RP SHUTDOWN INITIATED due to thermal

alarms\n

RP is shutting down due to reason

mentioned.

Isolation message from node [chars]

([hex]) has invalid info: msg destination
nodeid is [hex], my nodeid is [hex], msg
isolation state is [dec]

This message indicates that the isolation

request message from the peer RSP node
contained invalid information and therefore
was not accepted. RSP isolation state is a
temporary debug state in which the system
manager software automatically collects
debug information from the affected RSP
which has experienced a software failure,
before resetting it. If this error message is
seen, the peer RSP should have been reset
already without collecting any debug
information and is expected to come back
to operational state following the reset.

An RSP with different memory

configuration is detected. This resulted in
RSP mixed memory condition in the
RSP with different memory configuration in system. Running the system in this
the system is [chars].
condition is not recommended.

Different types of RSP in the system is

[chars].

Mix of different types of RSP is detected.

Running the system in this condition is not
allowed.

Node [chars] is shutdown due to a critical

alarm

This message indicates that the node will

be brought down because a critical
environmental alarm occured.

Node [chars] is shutdown due to a critical

alarm

This message indicates that the node will

be brought down because a critical
environmental alarm occured.

This message indicates that the node is

Power off node [chars] due to occurence of being brought down to IN_RESET state due
multiple critical faults on it, putting it into to occurence of multiple critical
IN_RESET state
faults/alarms on the node.

Power off node [chars] due to multiple

critical environmental alarms, putting it
into IN_RESET state

This message indicates that the node is

being brought down to IN_RESET state due
to occurence of multiple critical
environmental alarms on the node related
to power/voltage/temperature.

i2c_server on node [chars] requested

node's shutdown due to failure: [chars].
Putting it into IN_RESET state

This message indicates that the node is

being powered-down and moved to
IN_RESET state due to occurence of
specified I2C alarm on its board.

This message indicates that the node has

already undergone mutilple ungraceful
reboots in last one hour or one day and has
reached node's hourly or daily reboot
Node [chars] reached threshold of [dec]
threshold limit of 5 (in last one hour) or 8
ungraceful reload in last one [chars].
(in last one day). In order to avoid further
Powering it off and putting it into IN_RESET disruptions to the netwrok due to this node,
state
its better to shut (power) down this node.
This message indicates that the node will
Node [chars] is reset due to admin shut/no be reset because user has administratively
shut request
'shutdown' or 'no shutdown' the node.

This message indicates that the node will

Node [chars] is reset due to admin shut/no be reset because user has administratively
shut request
'shutdown' or 'no shutdown' the node.

Excessive node state message transmit

The system has detected a possible
time detected. [chars] Seq: [dec], Queue
performance issue causing a delay in shelf
Delay: [dec] sec, Transmit Delay: [dec] sec management operations.

This message indicates that the shelfmgr's

timerQ - keeping pool of free nodes to start
No more free nodes available in timer Q to new timer, is now empty. No more nodes
start [chars] for node [chars]
available to start any new timer.
Unexpected MDR event received for node
id: [chars], event name: [chars][[hex]],
card state: [chars][[dec]]

The system has received an MDR event

that is not supported.

Detected unexpected pulse ([chars]) for

node [chars] while being in [chars] state.
Ignoring this pulse

This message indicates that the node

received an unexpected/illegal pulse while
running in specified state. Node should not
undergo inappropriate action or state
change on receiving such unexpected
pulse.

Warning: [chars] exits, exit reason is

[chars]([hex])

This message indicates that the Shelf

Manager or Platform Manager encountered
a critical system(OS) error. It will exit right
away.

Boot request from node [chars] contains

invalid board type, This board is being
shutdown

This message indicates that the board type

cannot be recognized, therefore, the node
will not be able to boot up. This usually
caused by an invalid eeprom content.

Boot request from node [chars] contains

invalid board type [hex], This board is
being shutdown

This message indicates that the board type

cannot be recognized, therefore, the node
will not be able to boot up. This usually
caused by an invalid eeprom content.

Detected an unknown slot: [dec]\n

When deciding whether the slot belongs to

the RP or not (in dual mode), an unknown
slot (number) was detected'

This is a warning message to indicate that

using '-o override' option while booting the
image, the operator will override the
Command line boot override to permit RPs default IOS XR behavior which blocks the
with ROMMON 1.19x to boot as the standby RP with ROMMON version v1.19x from
has been enabled
coming up as the standby.

[chars] Collecting debug info to [chars]%s

An error condition was hit causing shelfmgr

to collect some debug info via a script.

WARNING: the read from the eeprom has

failed on node [chars]. return value [dec]
(PLIM type is [hex]).

The read of the eeprom to fetch card_type

for the given node has failed.

This informational message informs the

user that the Shelfmgr discovered an
WARNING !!! WARNING !!! Received boot
empty serial number due to an older
request from a RP with an empty rack
ROMMON format, but it will allow the RP to
serial number. Permitting RP to boot due to boot because the operator had configured
[chars] override. Please upgrade RP
to override the restriction of disallow
ROMMON to latest recommended version booting a RP with empty serial number.

WARNING: a legacy fabric card (FC-40G) is

placed in [dec]/SM[dec]/SP, and there are
MSC-140G/FP-140G cards in this rack,
therefore cannot be powered on. Please
A legacy fabric card (FC-40G) may only be
replace the legacy fabric card with FC-140G powered on if there are no MSC140G/FPfabric card, so that it can be powered on.
140G cards in the router.
WARNING: the read from the idprom has
failed on slot [dec]. return value [dec]
(PLIM type is [hex]).

The read of the one_wire prom for the

given slot has failed.

This msg indicates that a PLIM type in the

given slot does not match the card type; or
[dec]/[dec]/CPU0 is shut down as an invalid the card/plim is not appropriate for the
BOARD or PLIM type is in the slot
chassis.

WARNING: a L3LC [chars] is placed in [dec]/

[dec]/CPU0, and there are legacy fabric
cards (FC-40G) in this rack, therefore
cannot be powered on. Please replace all
A MSC-140G/FP-140G card only be powered
the legacy fabric cards with FC-140G fabric on if there are no legacy fabric cards (FCcards, so that the L3LC can be powered on. 40G) in the router.

This indicates that something is wrong in

Shelfmgr has not received any Heart Beats shelfmgr's ability to receive Heart Beats,
from any node for [dec] seconds
OR there are simply no cards sending HBs.

WARNING: a Non-Services PLIM is placed in

slot [dec] (an upper slot), and there is a
Services PLIM in slot [dec] below it,
therefore cannot be powered on. Please
place the PLIM in a lower slot or an upper
slot where there is no Services PLIM in the
slot below it.

Non-Services PLIMs in the upper slot (s =

0..7) may only be powered on if there is no
Services PLIMs powered on in the paired
lower slot (s+8).

a script launch failed in shelfmgr: [chars],

([dec])

A problem was encountered while trying to

spawn a script.

WARNING: a Services PLIM is placed in slot

[dec] (a lower slot), and there is a NonServices PLIM in slot [dec] above it,
therefore cannot be powered on. Please
place the PLIM in an upper slot or a lower
slot where there is no Non-Services PLIM in
the slot above it.

Services PLIMs in the lower slot (s = 8..15)

may only be powered on if there is no NonServices PLIMs powered on in the paired
upper slot (s-8).

Receive [chars] from [chars], while waiting Card seems to have been cold reloaded
for MBI_HELLO_WARM
after an attempt to warm reload the card.

Receive [chars] from [chars], while waiting Card seems to have been cold reloaded
for MBI_HELLO_WARM
after an attempt to warm reload the card.

Shelfmgr Software Error: [chars]

An unexpected software event has caused

the shelfmgr process to restart.

This command is DEPRECATED! Cannot

permit RP/SC with ROMMON version 1.3 or
older to boot as standby. Please upgrade
RP/SC ROMMON to latest recommended
version

This informational message informs the

user that this command is deprecated.
Rack Serial number is empty for RPs/SCs
with ROMMON 1.3 or older. Software
(Shelfmgr process) no longer honors boot
requests from such RPs/SCs.

BOOT_REQUEST count limit reached on

slot: [chars]

If the node sends the maximum number of

boot requests without actually being
booted, it will be powercycled

process [chars] running on [chars]

requested node [chars] to be [chars].
reason: [[chars]]

The reason should be supplied in the IOS

msg itself, but basically this msg means
that shelfmgr is shutting down a node
because a process specifically requested it.

Requesting node [chars] to be [chars].

reason: [[chars]]

The reason should be supplied in the IOS

msg itself, but basically this msg means
that shelfmgr is shutting down a node
because a process specifically requested it.

Shelfmgr [chars] is now connected to

eth_server

This message indicates that shelfmgr is

now connected to the eth_server process
and is therefore capable of of receiving
heartbeats (in the case of the Heart Beat
thread) and boot requests (in the case of
the boot thread).

This message indicates that shelfmgr is

now disconnected from the eth_server
process and is therefore not capable of
receiving heartbeats (in the case of the
Shelfmgr [chars] is now disconnected from Heart Beat thread) or boot requests (in the
eth_server
case of the boot thread).
Node [chars] is reset due to fabric software This message indicates that the fabric card
request, as an attempt to recover from a
will be reset because the fabric software
failure.
has requested to reload the node.

The fabric software request to reset node

[chars] aborted since [chars]

This message indicates that shelf manager

can not comply with the fabric software
request to reload a failed node due to the
reason mentioned in the message. The
fabric software is only to request such an
action upon fabric card failures that it can
not correct without a reload attempt. Reset
requests during shelf manager
initialization, or if the state of the card does
not support such a request are rejected.
For example, if the shelfmgr detects the
card to be not present, or already IN_RESET
due to failed multiple reload recovery
attempts, it will reject the request.
Similarly, if the node is UNPOWERED or if it
is already being reloaded, the request will
be rejected.

Shelfmgr is receiving Heart Beats again

after not receiving any for [dec] seconds

Shelfmgr has previously missed HBs, but is

now receiving them again.

Can not power on node [chars] due to

absence of PLIM

This message informs the user that the

linecard will not be powered on because
there is no PLIM inserted.

Can not power on node [chars] due to

absence of PLIM

This message informs the user that the

linecard will not be powered on because
there is no PLIM inserted.

Node [chars] CPU reset detected.

This message indicates that the Shelfmgr

detected the CPU of the specified node has
reset. The specified node will attempt
software reload.

Node State Discovery complete

Shelf Manager node discovery complete.

[chars] [chars] has completed IMDR

Card transition to IMDR completion

occurred.

Node [chars] indicates it is doing a kernel

dump.

This message indicates that the specified

node is doing a kernel dump. This can
happen in case of a failure that leads to the
node software deciding to do a kernel core
dump and then reset the node.

This message indicates that the reset

request caused by a critical alarm or
Node [chars] is in NMON state, Cancel reset heartbeat loss will not take effect because
request\n
the node is being put in NMON state.

Node [chars] is in NMON state, Cancel

shutdown or reset request\n

This message indicates that the reset

request caused by a critical alarm or
heartbeat loss will not take effect because
the node is being put in NMON state.

Node [chars] reset detected.

[chars] [chars] state:[chars]

This message indicates that the shelf

manager detected the specified node has
reset. Node reload will be attempted.
Card state transition occurred.

Node [chars] is reset due to UNKNOWN

reason

This message indicates that the node has

been reset but the cause is unknown.

Node [chars] is reset due to UNKNOWN

reason [[dec]]

This message indicates that the node has

been reset but the cause is unknown.

Node [chars] is powered off due to admin

power off request

This message indicates that the node will

be reset because user has administratively
'power disable' or 'no power disable' the
node.

Node [chars] is reset through power off,

then power on

This message indicates that the node is

being reloaded because of a critical
environmental alarm.

[chars] is isolated from the rest of the

router.

This message indicates that the RSP is in

an isolated state from the rest of the
router. This means it is held in isolation for
the collection of debug information and will
be subsequently rebooted by software
automatically.

The system is recovering either from a cold

System cold start detected. Resetting Line restart situation or a state where no valid
Cards.
shelf controller cards were available.
Node [chars] is reset due to user reload
request

This message indicates that the node will

be reset because user has requested to
reload the node.

Node [chars] is reset due to user reload

request

This message indicates that the node will

be reset because user has requested to
reload the node.

Node [chars] is unable to reset due to

[chars]

This message indicates that the node is

unable to comply with a requested user
reload request.

Receive MBI_HELLO_ENA from [chars] at

[WARM-RLD], status jumped to IOX-RUN

Card comes up without MBI_HELLO or

MBI_HELLO_WARM, need to check warmreload is really done successfully.

Receive MBI_HELLO_WARM from [chars] at

[Present], LC seems to be under warmreload
Card seems warm reloaded successfully
Receive MBI_HELLO_WARM from [chars],
new processes are coming up

Card seems warm reloaded successfully

Receive MBI_HELLO_WARM from [chars],

new processes are coming up

Card seems warm reloaded successfully

CRITICAL: CHASSIS SHUTDOWN initiated

due to [chars]\n

Chassis is shutting down due to reason

mentioned.

Critical Alarm: Alarm [chars] because

[chars]

Two possibilities to this message 1) An

alarm has occured. Software cannot access
all fans from all trays. This could be caused
by fan tray loss power or individual fans
were not running. User will have 45
seconds to replace a fan tray. If no action is
taken within 45 seconds, the chassis will be
shut down. 2) A previously occured alarm
has been cleared. Software has detected
that all fan on all trays failed condition is
cleared

Critical Alarm: Alarm [chars] because

[chars]

Two possibilities to this message 1) An

alarm has occured. Software has detected
that all fan trays have been removed from
the chassisbut, but gives user 45 seconds
to insert another tray. If no action is taken
within 45 seconds, the chassis will be shut
down. 2) A previously occured alarm has
been cleared. Software has detected that
all fan trays were removed which would
have shut down the system. But one fan
tray was put back within 45 seconds, thus
removing the need to shut down the
system.

Alarm [chars] because [chars]

Two possibilities to this message 1) An

alarm has occured. Software has detected
that both fan controller cards have been
removed from the chassis but, but gives
user 45 seconds to insert atleast one of
them back into the chassis. If no action is
taken within 45 seconds, the chassis will be
shut down. 2) A previously occured alarm
has been cleared. Software has detected
that both fan controller cards were
removed which would have shut down the
system. But one fan controller was put
back within 45 seconds, thus removing the
need to shut down the system.

[chars] Alarm: Fan Controller has been

[chars]. Alarm generated by FC module
[chars]

1) An alarm has occured. The Fan Controller

card has been removed. 2) A previously
occured alarm has been cleared. The Fan
Controller Card has been re-inserted.

This message indicates that shelfmgr was

An ENS notification was induced by user for induced to send out an ens notification for
node [chars], ([hex]), state [chars] ([dec]) the given node by the user.

A GSP node down was induced by user for

node [chars], ([hex]), rc: [dec]

This message indicates that shelfmgr was

induced to send out a gsp node-down
notification for the given node by the user.

A GSP node up was induced by user for

node [chars], ([hex]), rc: [dec]

This message indicates that shelfmgr was

induced to send out a gsp node-up
notification for the given node by the user.

This message indicates that shelfmgr was

A QNET node down was induced by user for induced to send out a qnet node-down
node [chars], ([hex]), rc: [dec]
notification for the given node by the user.

A shelfmgr node notification was induced

by user for node [chars], ([hex]), state:
[chars] ([dec])

This message indicates that shelfmgr was

induced to send out a notification for the
given node by the user.

[chars] [dec] [chars]

This message indicates that infrastructure

that shelfmgr depends on has failed.

Power allotted to cards in this rack has

exceeded the available rack power budget. This message indicates that power allotted
Please check the 'show power' command to to cards in this rack has exceeded the
resolve this situation.
available rack power budget.
Power allotted in zone [dec] has exceeded
the available zone power budget. Please
This message indicates that power allotted
check the 'show power' command to
to the zone has exceeded the available
resolve this situation.
zone power budget.
The indicated node notified shelfmgr about
Node [chars] about to reboot due to cause its software reboot with the reboot reason
code:[hex], [chars]
and cause code.

i2c_server on node [chars] requested it's

card reset due to failure: [chars]

This message indicates that the I2C server

on the specified node encountered the
specified failure. Shelfmgr will attempt to
reset the board which sends the alarm.

i2c_server on node [chars] requested it's

card shutdown due to failure: [chars].
Putting it into IN_RESET state

This message indicates that the node is

being powered-down and moved to
IN_RESET state due to occurence of
specified I2C alarm on its board.

Standby RP node notified shelfmgr about

Node [chars] about to reboot due to cause its software reboot with the reboot reason
code:[hex], [chars]
and cause code.

CRITICAL Alarm: Alarm generated because

Zone [dec] has lost power. Check that
power modules Ax and Bx are providing
This message indicates that zone has lost
power
power.

This message indicates that shelfmgr

Shelfmgr failed to create alarm thread with cannot create consumer thread for setting
errCode:[dec] errInfo:[chars]
LED display or alpha display.

Shelfmgr failed to initialized [chars] during This message indicates that shelfmgr
alpha display setup with errCode :[dec]
cannot initialize envirnoment for setting
errInfo:[chars]
LED display or alpha display.

Received [chars] [chars] alarm in isolated

state.

This message indicates that an alarm is

received by shelfmgr when the RP is in
isolated state. For critical alarm, reboot is
followed.

Board incompatibility detected for [chars]

in [chars]: [chars]

This indicates that a board boot attempt

was made with board types that are either
not supported in the slots or combinations
that they are presently in. Therefore, the
board(s) were powered down.

The affected node is booting again after a

failure attempt to power it off. The system
Still getting boot request from node [chars] will try to correct this problem by
after a power off operation.
performing a forced power off operation.

Shelf manager unable to Power Up Node

This message indicates that Shelf Manager
[chars] due to errCode:[dec] errInfo:[chars] has failed to power up the specified node.

Failed to reload node [chars] - error code is This message indicates that shelfmgr has
[dec] ([chars])
failed to reload the specified node.

Shelf manager unable to shutdown Node

[chars] due to errCode:[dec]([chars]) in
Context:[chars]

This message indicates that Shelf Manager

has failed to power down the specified
node..

Shelf manager unable to create CCB for

slot [dec] due to Error:[dec]([chars])

This message indicates that Shelf Manager

failed to create a nodeid based on the
supplied rack, slot, and instance.

Shelf manager failed to create CCB Name

for slot [dec] due to errCode:[dec] errInfo:
[chars]

This message indicates that Shelf Manager

failed to create a node name based on the
supplied rack, slot, and instance.

[chars], [chars] table ([hex]), error [hex]

([chars])

The reason should be supplied in the IOS

msg itself, but basically this message
means that shelfmgr usbale to update HA
cheackpoint.

Can't process checkpoint table name of

'[dec]'

An invalid checkpoint table name was

detected. The affected checkpoint
operation will not be processed.

Bad record length in [chars] table ([dec])

for object ID [hex] (expected [dec] bytes,
returned [dec] bytes)

The reason should be supplied in the IOS

msg itself, but basically this messge means
that shelfmgr received bad length during
standby HA check Point update.

Node [chars] is shutdown due to a critical

alarm

This message indicates that the node will

be brought down because a critical
environmental alarm occured.

Failed to send dcdc_enable for node [chars] This message indicates that Shelf Manager
as the I2C server node is in state [dec]
has failed to send a dcdc_enable request to
([chars])
the remote board.

Failed to send ENS notifications for node

[chars] and state [dec] ([chars]) due to
error [dec] ([chars])

This message indicates that Shelf Manager

has failed to notify clients of state changes
via ENS.

[chars]

This message indicates that a failure has

occured in Shelf Manager, but there is not
corresponding error code.

Failed to execute [chars] script for [chars] - A problem was encountered while trying to
[chars]
spawn a script.

Failed to allocate memory for a new rack

item

This message indicates that memory

allocation failed while adding the rack to
queue Shelf Manager

Failed to get smgr_sys_clk_delta,reset all

perday perhour timestamps, post_data
error counts and valid timestamps

This message indicates that Shelf Manger

unable to sync to system clock. Shelf
manager resets all per Hour/day threshold
counters and valid time stamps.

[chars] [hex] [chars]

an external API has failed in Shelf Manager.

The details are supplied with the msg.

[chars] [chars], rc = [dec], [chars]

an external API has failed in Shelf Manager.

The details are supplied with the msg.

Forced power off has failed again on node

[chars] after [dec] attempts. Further boot
requests sent from the node will be
ignored.

Multiple attempts to force the powering off

of the node have failed. No further
attempts will be made, all boot request
sent from this affected node will not be
processed.

Failed to create [chars] timer for node

[chars] due to error [dec] ([chars])

This message indicates that Shelf Manager

has failed to create a timer that is intended
to check a nodes boot progress.

This message indicates that Shelf Manager

was unable to initialize the timer
Failed to create root timer for node [chars] infrastructure required to monitor the
due to error [dec] ([chars])
booting of nodes.

Failed to get my boardtype, error code is

[dec], ([chars])

This message indicates that getting board

type from hardware has failed.

This message indicates that Shelf Manager

Failed to get name for nodeid [hex] due to has failed to translate the given nodeid into
error [dec] ([chars])
a human readable string.
This message indicates that decoding of
Failed to decode TLV heartbeat message of TLV format HB message failed with the
[dec] bytes ([hex] - [chars])
indicated error code and error message.

The [chars] [chars] is shutdown as it is in

the SDR [chars] which has [chars] in it.

This message indicates that the card got

shutdown is incompatible with the other
type of card in the same SDR.

This message indicates that the nodeid

Failed to extract slot from ([hex]). rc: [dec], passed is not valid, and therefore the
[chars]
power-up request is being rejected.

Detected invalid POST run request for card This message indicates that an unexpected
[chars] (current run [dec]). Ignoring this
post run request is present and shelfmgr
request.
will ignore this request.
A boot request sent to shelfmgr on rack
[dec] (rack type [dec]) is ignored as it
contains invalid slotId [dec] with card type
[chars] ([hex]). Possible seating issue.
Please reseat the suspected card(s).

This message indicates that the slot Id in

the boot request from rommon to shelfmgr
is invalid, therefore ignore the boot
request.

Failed to kill [chars] with thread id [dec] for A problem was encountered while
[chars] - [chars]
executing the indicated script.

MBI validation failed. Error code is [dec]

This message indicates that Shelf Manager
([chars]), node is [dec]([chars]), card type has failed to validate the mbi path supplied
is [dec]([chars]), hardware revision is [dec] during a boot request.

Timeout waiting for valid boot request from This message indicates that the card is
node [chars], resetting card [chars] to
being reset because of a failure to get valid
recover from this failure
boot request from a specific node.

Reset node [chars] due to heartbeat loss

This message indicates that the node is

being reset because it failed to detect
heartbeat pulses. Debug information would
have been collected before the reset
operation and then saved under
harddisk:/shelfmgr_debug directory (debug
files collected for each node will be created
under its own subdirectory) after the node
recovers from the failure. Also crashinfo
and core file would have been created as
part of the reset opeartion under
harddisk:/.

Timeout waiting for new version of MBI

processes start during IMDR from node
[chars], resetting card [chars] to recover
from this failure

This message indicates that the card is

being reset because of timeout waiting for
start of new version of MBI processes
during IMDR from a specific node. This is
an indication of IMDR operation failure
during ISSU.

Node [chars]'s kernel started to dump

This message indicates that the node's

kernel is dumped to local harddisk or RP's
harddisk.

This message indicates that the card is

being reset because of timeout waiting for
KDUMP operation to complete from a
specific node. This is an indication of
KDUMP operation taking longer that what is
Timeout waiting for KDUMP completion
expected. The kernel core file collected
from node [chars], resetting card [chars] to under this error condition might not be
recover from this failure
complete.

Timeout waiting for MBI heartbeat from

node [chars], resetting card [chars] to
recover from this failure

This message indicates that the card is

being reset because of a failure to get MBI
heartbeat from a specific node. This is an
indication of an error condition during MBI
BOOTING state.

Failed to poweroff node [chars]. Reason:

[chars]

The power off operation for the indicated

node has failed.

This message indicates that the card is

being reset because of timeout waiting for
the indicated node to perform software
reboot. This failure recovery action
happens after shelf manager has received
Timeout waiting for reboot on node [chars], notification from the node about its intent
resetting card [chars] to recover from this to reboot, the failure to self reboot
failure
triggered the reset action on the card.

Node [chars] in critical alarms, request to

reset ...

This message indicates that the Shelf

Manager or Platform Manager encountered
a critical alarm for the node specified. It
will attempt to reset the board which sends
the alarm.

This message indicates that the node has

already undergone mutilple reboots and
has reached node's reboot threshold limit
Node [chars] being powered down due to of 6. In order to avoid further disruptions to
multiple boot failures. Last reboot cause:
the netwrok due to this node, its better to
'[chars]', now putting it into IN_RESET state shut (power) down this node.

[chars], node name [chars] [node id [hex]], This message indicates that an operation
rc: [dec], [chars]
specific to a node has failed.

Timeout waiting for XR heartbeat from

node [chars], resetting card [chars] to
recover from this failure

This message indicates that the card is

being reset because of a failure to get XR
heartbeat from a specific node. This is an
indication of an error condition during MBI
RUNNING state.

Card name is [chars]

This message indicates that Shelf Manager

was unable to form a pointer to a shared
memory block.

Failed to send async message to FSM:

[chars] [dec] [chars]

This message indicates that an IPC failure

has occured in Shelf Manager.

[chars] [dec] [chars]

This message indicates that a Shelf

Manager has failed to notify QNET of a
node state change.

shelfmgr failed to get rack number from

DSC for the rack with serial ID [chars], so
the rack could not be booted up. A possible This message indicates that there is no
cause is that the dsc rack serial ID to rack rack serial ID to rack number mapping
number mapping is not configured.
configuration and a rack is trying to boot.
Request for node [chars] to be [chars] by
process [chars] was rejected. [chars].

The requested action was not performed.

RP SHUTDOWN INITIATED due to thermal

alarms\n

RP is shutting down due to reason

mentioned.

The [chars] script exited with error for

[chars]: [chars]

A problem was encountered while

executing the indicated script.

Killed [chars] script for [chars] as it failed

to collect reset debug info within the time
limit of [dec] seconds

The execution of the indicated script has

been terminated due to failure in
completing the debug collection task in
time.

This message indicates that the node has

already undergone mutilple ungraceful
reboots in last one hour or one day and has
reached node's hourly or daily reboot
Node [chars] reached threshold of [dec]
threshold limit of 5 (in last one hour) or 8
ungraceful reload in last one [chars].
(in last one day). In order to avoid further
Powering it off and putting it into IN_RESET disruptions to the netwrok due to this node,
state.
its better to shut (power) down this node.

Failed to find CCB while [chars] [slot :

[dec]] Error: [dec]([chars])

This message indicates that an operation

to get Card Control Block CCB for specific
to a slot has failed.

sysDB Bind failed during [chars] with

ErrCode:[dec]([chars])

This message indicates that bind to config

namespace in SysDB has failed.

sysdb Bind/Unbind failed during [chars]

with Error:[dec]([chars])

This message indicates that bind/unbind to

config namespace in SysDB has failed.

[dec] [chars]

This message indicates that config

notification registration with SysDB has
failed.

sysDB unbind failed during [chars] with

Error:[dec]([chars])

This message indicates that unbind to

config namespace in SysDB has failed.

This message indicates that a HB was

Unexptected heartbeat received from node received from a node that was not
[chars]
previously detected.
Unexpected [chars] of [chars] script by
signal [dec]

The execution of the indicated script has

been exited due to reception of the
indicated signal.

This message indicates that the board type

cannot be recognized, therefore, the node
will not be able to boot up. This may be
Boot request from node [chars] contains
caused by an invalid eeprom content; or
invalid board type [hex], this board is being happens in a rare corner case which may
reset.
recover after a board reset.

Boot request with unknown boot protocol

[dec] received

This message indicates that Shelf Manager

has received an unknown boot protocol
with a boot request.

Unknown boot request message version of Shelf manager received a version of boot
'[dec]' was detected during [chars].
request message that it cannot support.

This message indicates that the board type

cannot be recognized, therefore, the node
will not be able to boot up. This may be
Boot request from node [chars] contains
caused by an invalid eeprom content; or
invalid board type [hex], rejecting this boot happens in a rare corner case which may
request.
recover after a board reset.

Unsupported board of type [hex] detected

in [chars]

This indicates that the indicated board type

is not supported by the current IOS XR
release and it will be powered down.

Failed to [chars], error code is [dec],

([chars])

This message indicates that shelfmgr has

problem in handling events for setting LED
display or alpha display.

WARNING: Please, avoid inserting thermally

sensitive PLIM in slot [dec] (a upper
slot).Thermally sensitive PLIMs are confined Thermally Sensitive PLIMs are confined to
to lower slots only.
lower slots only.
process [chars] running on [chars]
requested node [chars] to be [chars].
reason: [[chars]]

This msg means that shelfmgr is shutting

down a node because a process specifically
requested it.

The POST configuration is accepted but the

feature will not be performed since IFD
diagnostic PIE can not be located. Please
The check of the IFD diagnostic image
install the required PIE.
returned failure as the PIE is not installed.

Card reloading on [chars] due to [chars]

error, however, power-on self test will not
perform as there is no diagnostic test
available on falling device [chars]. Card will
be reloaded to XR-RUN. Diags not available
- error code [dec], ([chars])

The card is reloaded due to a faulty

HW/ASIC. The check on Online Diags
indicates there is no diagnostic test
available on the falling device, hence the
card will then be reloaded with XR image.

Card reloading on [chars] due to [chars]

error, however, power-on self test will not
perform on falling device [chars] as Diags
failed the request. Card will be reloaded to
XR-RUN. Diags failure - error code [dec],
([chars])

The card is reloaded due to a faulty

HW/ASIC. The Online Diags process can't
perform the required diagnostic testing on
the falling device, hence the card will then
be reloaded with XR image.

The card is reloaded due to a faulty

HW/ASIC. The IFD image will be loaded and
diagnostic tests on the falling device will be
performed. The card will then be reloaded
Card reloading on [chars] due to [chars]
with XR image if nothing wrong in the
error, IFD image will be loaded and power- device; otherwise it will be placed IN-RESET
on self test on [chars] will be performed.
mode.
This message indicates that requested
Card in slot [dec] is power-disabled. Cannot node cannot be powered up because its in
power it on
admin-config power-disabled state.
Timeout waiting for node [chars] to
transition into [chars] state. Collecting
debug info before resetting the node.

An timeout condition was hit causing

shelfmgr to collect some debug info via a
script.

WARNING: Combination of 6-10GE-WLOFLEX PLIM in slot [dec] (a lower slot) and

CRS-CGSE-PLIM in slot [dec] (an upper slot)
is not supported.

Due to thermal restriction, the combination

of 6-10GE-WLO-FLEX PLIM in the lower slot
(s = 8...15) and CRS-CGSE-PLIM in the
upper slot (s = 0...7) is not supported.

Forcing power off of node [chars]

An attempt to force the powering off of the

node has been performed to make sure
that the affected node will remain in
powered off state.

WARNING: A High Powered PLIM is inserted

in slot [dec] (a lower slot), and there is Non
High powered PLIM in slot [dec] above it.
Therefore PLIM in slot [dec] (a lower slot)
cannot be powered on. Please, insert the
PLIM in an upper bay slot or in a lower bay
slot where the slot above it is either empty
or having an High Powered PLIM.

High Powered PLIMs in the lower slot (s =

8..15) may only be powered on if there is
an High Powered PLIM powered on in the
paired upper slot (slot = s-8) or if the
paired upper slot is empty.

WARNING: A High Powered PLIM is inserted

in slot [dec] (an upper slot), and there is a
Non Identical High Powered PLIM in slot
[dec] below it. Therefore PLIM in slot [dec]
(an upper slot) cannot be powered on.
Please, insert the PLIM in a lower bay slot
where the slot above it is either empty or
having an Identical High Powered PLIM or
insert the PLIM in an upper bay slot where
the lower slot is either empty or having an
Identical High Powered PLIM or a Non High
Powered PLIM.

High Powered PLIMs in the upper slot (s =

0..7) may only be powered on if there is an
Identical High Powered PLIM powered on in
the paired lower slot or if the paired lower
slot is empty or if the paired lower slot is
having a Non High Powered PLIM.

This message indicates that the

Received REMOTE_RESET event while node REMOTE_RESET event is received when the
[chars] ([hex]) is in IOS XR ISOLATED state, node is in isolated state. No action is taken
sysmgr will not allow the node to reboot.
as sysmgr will not allow the node to reboot.

Invalid Card type Command: [dec]

The card information will be provided with

message itself, but basically this message
mean card information passed to command
is invalid type. Please check for
Rack/Slot/Node id before executing the
command.

Failed to initialize the [chars] ltrace file

Error:[dec] ([chars])

This message indicates that ShelfmgrV2

ltrace initialization has failed. Embedded
string provides the details of failed function
name and the error details.

This message informs the user that the

Power down node [chars] due to absence of linecard will be powered down because
PLIM
there is no PLIM inserted.
RPFO happened while node [chars] is in IOS
XR ISOLATED state, abort the isolation by This message indicates that node isolation
resetting the card.
is aborted.

WARNING: a Non High Powered PLIM is

inserted in slot [dec] (an upper slot), and
there is a High Powered PLIM in slot [dec]
below it, therefore it cannot be powered
on. Please insert the PLIM in any lower slot
or an upper slot where there is no High
Powered PLIM in the slot below it.

Non High Powered PLIMs in the upper slot

(s = 0..7) may only be powered on if there
is no High Powered PLIMs powered on in
the paired lower slot (s+8).

WARNING: a Non-Services PLIM is placed in

slot [dec] (an upper slot), and there is a
Services PLIM in slot [dec] below it,
therefore cannot be powered on. Please
place the PLIM in a lower slot or an upper
slot where there is no Services PLIM in the
slot below it.

Non-Services PLIMs in the upper slot (s =

0..7) may only be powered on if there is no
Services PLIMs powered on in the paired
lower slot (s+8).

Rack power is now being allotted from all

power modules. Power module redundancy
is no longer available, a single power
module failure might result in card power
loss.

This message indicates rack power is now

being allotted from all power modules.
Power module redundancy is no longer
available, a single power module failure
might result in card power loss.

The power-zone [dec] has gone down.

This indicates that the given power-zone

has gone down, and therefore the related
nodes are being brought down.

Shelf manager failed to notify Rack down

for Node [chars] due to errCode:[dec]
errInfo:[chars]

The reason should be supplied in the IOS

message itself, but basically this message
means that shelfmgr unable to send the
rack down notification

Card in slot [dec] is [chars]. Cannot

perform reload operation

This message indicates that requested

node cannot be reloaded because its in
UNPOWERED (admin-config powerdisabled) state or not ready for reload
operation.

Reset debug information was not fully

collected, any information that was able to
Successfully saved partial reset debug info be collected before script was aborted are
for [chars] in \[chars]/[chars]\.
saved in the indicated file.
Successfully saved reset debug info for
[chars] in \[chars]/[chars]\.

Reset debug information are saved in the

indicated file.

WARNING: a Services PLIM is placed in slot

[dec] (a lower slot), and there is a NonServices PLIM in slot [dec] above it,
therefore cannot be powered on. Please
place the PLIM in an upper slot or a lower
slot where there is no Non-Services PLIM in
the slot above it.

Services PLIMs in the lower slot (s = 8..15)

may only be powered on if there is no NonServices PLIMs powered on in the paired
upper slot (s-8).

process [chars] running on [chars]

requested node [chars] be shutdown.
reason: [[chars]]

The reason should be supplied in the IOS

msg itself, but basically this msg means
that shelfmgr is shutting down a node
because a process specifically requested it.

Failed stats SHIP registration of client:

[chars] Error:[dec]([chars])

This message indicates that stats SHIP

register initialization operation has failed.
Embedded string provides the information
about the error and the failed SHIP register.
There is no functional impact as this stats
is for debugging purposes only.

sysDB set item operation failed, error is

[chars], pathname [chars], tuple [chars]

The reason should be supplied in the IOS

msg itself, but basically this msg means
that shelfmgr unable to set the default
parameters in sysDB.

tried to read an unknown cfg type ([dec])

shelfmgr tried to read a config type that

does not make sense, and so does not exist
in the sysdb space.

Field Diagnostic heartbeat loss event has

been detected on the indicated node. And
Have not received Field Diagnostic
the node will stay in FDIAG FAILURE state
heartbeat messages from [chars] for more until shelf manager resume reception of
than [dec] seconds.
FDIAG heartbeat messages.

Reload event for card [chars] is being

cancelled because of multiples ungraceful
reload events on node [chars].

This message indicates that a previous

delayed reload event is being cancelled
due to multiples ungraceful reloads on the
indicated node.

Reload event for card [chars] is being

delayed because node [chars] is
performing kernel dumping operation. The
reload operation will resume after kernel
dumping operation completes.

This message indicates that the received

reload request is being delayed due to one
of nodes performing kernel dumping
operation. This reload request will be
processed after kernel dumping operation
completes.

Card [chars] is powered off due to admin

power off request

This message indicates that the card will

be powered off because user has
administratively configured 'hw-module
power disable location <node>'
configuration in one of the nodes of the
card.

Failed to receive valid boot request from

node [chars], boot request timer has
expired

This message indicates that Shelf Manager

did not receive boot requests within the
alotted time from the given node.

Power to be allotted for card [hex] in slot

[dec] is unknown. Assuming 123 W.

Power to be allotted for the given is

unknown. Assuming 123 W.

Received DSC change event: event type

[chars] ([dec]), old dsc [chars] ([hex]), new
dsc [chars] ([hex]).
This is an information log.
[chars]
This is an information log.

This message indicates that node is

configured in NMON (No MONitor) mode by
the user and would not be reloaded by
shelfmgr until restored back to MON config.
Primary purpose of configuring node in
NMON is to analyze and debug the node or
its card behavior. Exception: shelfmgr
NMON (reset auto disable) config applied to ignores node's NMON config on occurence
[chars]
of a critical alarm at node's end.

This message indicates that node is out of

its NMON (No MONitor) config now and
would be monitored by shelfmgr. While it
was in NMON config, node or its card was
Node [chars]'s NMON (reset auto disable) not being monitored or reloaded by
config removed. Ensure to reload it so as to shelmgr, so might have undergone
get its card back to normal state
indeterministic state.
This message indicates that the reset
request caused by a critical alarm or
Node [chars] is in NMON state, cancel reset heartbeat loss will not take effect because
request due to [chars]
the node is being put in NMON state.

Node [chars] is in NMON state, cancel

shutdown request due to [chars]

This message indicates that the shutdown

request caused by a critical alarm or
heartbeat loss will not take effect because
the node is being put in NMON state.

This message indicates that power

Power allotment in this rack is now normal. allotment in this rack is now normal. Power
Power module redundancy restored.
module redundancy restored.
Power budget is now sufficient for rack
power.

This message indicates that power budget

is now sufficient for rack power.

Power budget for zone [dec] is now

sufficient for zone power

This message indicates that Power budget

for the zone is now sufficient for zone
power.

[chars], [chars] [chars], [chars] timer has

expired

This message indicates that a timer

shelfmgr was using to monitor a nodes
boot progress has expired.

Node [chars] is reset due to user reload

request

This message indicates that the user has

requested to reload the node.

CRITICAL Alarm: Alarm cleared because

Zone [dec] is now receiving power.

This message indicates that zone is now

receiving power.

A Version Manager CLI command was

unable to bind to the interface
infrastructure, due to error [chars].

A Version Manager CLI command was

unable to bind to the interface
infrastructuree from which it obtains
information. The command will not contain
all expected information.

A Version Manager CLI command was

unable to bind to the system database
A Version Manager CLI command was
from which it obtains information. The
unable to bind to the system database, due command will not contain all expected
to error [chars].
information.

Failed to perform APIV bind operation for

[chars] module

APIV bind operation failed.

Failed to initialize APIV data for [chars]

module

APIV data initialization operation failed.

Failed to APIV listening thread for [chars]

module

APIV bind operation failed.

[chars] APIV message encoding failed [chars]

API Version message encoding failed.

Failed to send [chars] message to [chars] - API Version message send to the indicated
[chars]
target failed.

[chars] APIV failed to negotiate versions

due to incompatible version

API Version negotiation failed due to

incompatible version.

[chars] APIV failed to negotiate versions

after [dec] seconds ([chars] status)

API Version negotiation failed due to

timeout.

[chars] APIV registration failed - [chars]

API Version registration failed.

Failed to create APIV transport layer for

[chars] module

APIV transport layer creation failed.

Error: [chars] Bytes recieved: [unsigned

int], Maximum bytes expected: [unsigned
int]

The length of the received message exceed

the buffer size.

[chars]

SIM ENS operation error.

[chars]: event_block failed ([chars])

This is an error message which indicates

the blocking of an event.

Execution of [chars] configuration

command for [chars] failed - [chars]

SAM command operation error.

Execution of [chars] command for [chars]

failed - [chars]

SAM command operation error.

[chars]

SAM inventory operation error.

Service Engine failed to process sent

platform info - [chars]

The platform information sent to Service

Engine failed to get processed.

Failed to send platform info message to

Service Engine after [dec] retries - [chars]

The platform information sent to Service

Engine failed to get processed.

[chars]

SIM inventory operation error.

ISM Agent: [chars]

An internal software error has occurred for

SIM SW infrastructure.

Failure returned by [chars]() API - [chars]

SysDB operation error.

Failure to [chars] for [chars] - [chars]

SysDB operation error.

Install role :[chars] [chars]

Role installation completed.

Details: [chars]

Printing the data for test purpose from the

database.

[chars]: [chars] [chars] [dec]

The error occurs due to the failure while

binding the system database.

[chars] [chars] [chars]

Encountered an error in the debug

module.This error should not impact the
major functionality of the module.

Failed to get SE node ID([chars]) LCP

nodeid = [hex]\n

The message indicates failure in getting

the status of nodes for shutting it down.

SIM_IPC ERROR : [chars]

The message indicates failure in any of the

process initialisation like installing or
downloading the image gets failed, failed
to allocate memory or any failure in service
engine.

[chars]: [chars]

An internal software error has occurred for

the SIM IPC.

sysdb_list_next failed for [chars] at : [dec]

[dec] [chars]

The message indicates the failure while

updating the data items in the system
database.

[chars] [char]

The message indicates,the user has

entered an unknown option .

[chars]: [chars]

An internal software debug SIM IPC Service

Engine.

API Versioning Negotiation failure detected,

SE will be out of service state.
TBD.

[chars] BIOS init failure detected

(state=[dec], error=[dec], status=[dec]).

TBD.

All [dec] retries to boot the SIM Service

Engine has failed. Please contac technical
support.

TBD.

Service Engine system shut detected due

to cpu thermal shut, it will be reloaded to
recovery from this failure after cool down.

TBD.

Disk file system check failure detected.

TBD.

Disk file system check timeout detected.

TBD.

[chars]

HA Data path test failed, reloading ISM.

[chars]

HA test error.

[chars]

HA Punt path test failed, reloading ISM.

Service Engine heartbeat failed, reloading

SE node to recover from the failure

SIM Service Engine complex heartbeat

failed, reloading SE complex

CHANNEL: [unsigned int], RX GOOD/DROP:

[unsigned long long int] / [unsigned long
long int] : [unsigned long long int] /
[unsigned long long int], TX GOOD/DROP:
[unsigned long long int] / [unsigned long
long int] : [unsigned long long int] /
[unsigned long long int], TX QUEUE:
[unsigned int] / [unsigned int] / [unsigned SIM heartbeat failed, log heartbeat failure
int] : [unsigned int] / [unsigned int]
statistic

Failed to send heartbeat message to

Service Engine, reloading the complete SIM SIM heartbeat sent to Service Engine
node to recover from the failure
failed, reloading

[chars]

An internal software error has occurred for

the specified SIM Service Engine heartbeat
machanism.

SE Kernel core dump file is generated, SE

will be reboot.

TBD.

SE Kernel is crashed, Kernel core dump file

is generating ...
TBD.

Service Engine system KEXE initialization is

expired, it will be reloaded to recovery from
this failure.
TBD.

latest BIOS boot failure, will boot golden

BIOS.

TBD.

Service Engine system init failure ([chars]). TBD.

Failed to load maintenance image to

Service Engine, the node will be reloaded
to recovery from this failure.

TBD.

Cannot find the Maintenance Image in the

following path: [chars]

The Maintenance Image could not be

located in the indicated path.

[chars]

An internal software error has occurred for

the specified SIM Service Engine.

Service Engine system init failure detected,

it will be reloaded to recovery from this
failure.
TBD.

Failure returned by [chars]() API - [chars]

SysDB operation error.

[chars]

HA test warning.

Booting of Maintenance Image is being

requested by Service Engine in slot [dec]
because of boot error [hex] with BIOS
status code [hex].

TBD.

The role configuration determines the type

of service ISM card is going to run. This
message is generally encounterd in the
cases of RMA or location change of ISM
Installed Role: [chars] on ISM card does not card. It means that the ISM card is not
match with Configured Role: [chars].
running the service which it is expected to
Service functionality may not work.
run.

[chars]

Display HA test info.

[chars]

For displaying SIM Service Engine

information message.

Service Engine is in [chars] state.

For displaying state of the SIM Service

Engine

Failed to initialize Service Logger, [chars].

This log indicates that Service Logger was

not able to initialize. As result of this error,
Service Logger will not log be able to log
data in the log file.

Failed to initialize Service Logger tracing,

error: [chars].

This log indicates that Service Logger was

not able to initialize tracing. As result of
this error, Service Logger will not have any
tracings.

Connection to mentioned CAPI service

[chars] Capi connection failed, Error [chars] failed

config mgr registration (for partition-done- Registration fail for config mgr partitionnotification) error, [chars] [chars]
done notification

Failed to initialize the SliceMgr Proxy

process: [chars] Error Code [hex] ([chars])

The SliceMgr Proxy process failed to

initialize. The System Manager will restart
the process.

Failed to initialize shmwin, Error [chars]

Initialization of shared memory window

failed

Sysdb bind failed for [chars], path [chars].

Error([dec]): [chars]

Sysdb bind error

sysdb registration (notification) error,

[chars] [chars], [chars]

Registration fail for sysdb notification

sysdb registration (verification) error,

[chars] [chars], [chars]

Registration fail for sysdb verification

Failed to verify slice config, [chars] sysdb

tuple, [chars] at <[chars]:[dec]>

Invalid sysdb tuple

connection fail: [chars]() [chars]

This indicates a channel setup or

communication failure within the process.
This will lead to incomplete initialization of
the driver impacting driver functionality.

'Error: [chars] - [dec]: [chars]'

Some error encountered like initialization

failure or connection failure

Memory operation fail: [chars]() [chars]

The message indicates failure in memory

allocation/mapping. This will lead to
incomplete initialisation of the driver,
hence the software functionality will be
impacted.

'[chars] memory map fail'

The message indicates failure in memory

allocation/mapping. This will lead to
incomplete initialisation of the driver,
hence the software functionality will be
impacted.

The message indicates failure in FPGA re'[chars] FPGA Programming failed or done' programming.

Smith init error: [chars] : [chars]

This msg can be an indication of

incomplete smith driver initialization or an
intermittent failure of HW register reads. It
may or may not have functional impact
depending on cause of failure.

Smith error: [chars] : [chars] : [dec]

This msg can be an indication of

incomplete smith driver initialization. or
any event error. It may or may not have
functional impact depending on cause of
failure.

'Error: [chars] - [dec]: [chars] (rc = [hex])'

Error encountered in memory allocation or

in message sending.

'[chars] failed with [chars]'

Error encountered in initializing system

manager.

HW read/write fail: [chars]

The message indicates HW read/write

timeout. The software will retry the action
to recover.

'Details: [chars]'

Print the data for debug purpose or for

change of states

[chars]

SOCKET SPP Initialization Error message.

Error Allocating <[dec]> bytes of memory

SOCKET SPP dll Memory Allocation Error

message.

[chars]: [chars]

SOCKET SPP Thread Error message.

JBI-Err: [chars]

This is an error message from the altera

JTAG player, it indicates that something has
gone wrong with FPGA programming.

JBI-Err: [chars]

This is an error message from the FPGA

upgrade facilitator , it indicates that
something has gone wrong with FPGA
programming.

JBI-Info: [chars]

This is an informational message from the

altera JTAG player

JBI-Info: [chars]

This is an informational message from the

FPGA upgrade facilitator

JBI-Debug: [chars]

This is a debuging message from the altera

JTAG player

JBI-Debug: [chars]

This is a debuging message from the FPGA

upgrade facilitator

[chars]: [chars] ([dec])

An error was detected in the Platform SPAN

module.

'[chars]: [chars] ([dec])'

An error was detected in the Platform SPAN

module which causes the span module to
exit. The reasons might be *Failed to
initialize the shared memory AVL tree
*Failed to get local source port *Failed to
delete AVL entry tree *Failed to initialize
debug and ltrace events

Failure to allocate memor for [chars]

A low-memory condition was detected in

the Platform SPAN module.

Failure to allocate memor for [chars]

A low-memory condition was detected in

the Platform SPAN module.

[chars]: [chars]

An unexpected condition was detected in

the Platform SPAN module.

'Info is: [chars]'

Entered crs_span_ea_hal_v4_tlu_write()
dummy.

Fatal error

SPA Bridge ASIC unrecoverable error.

Out Of Sync condition detected

SPA Bridge ASIC register access failure.

ERP error detected

SPA Bridge ASIC detected an ERP timeout,

parity, or protocol error.

MBIT ECC Error detected

SPA Bridge ASIC detected a MultiBit

uncorrectable ECC error.

Parity Error detected

SPA Bridge ASIC detected a Parity error.

Rx eSPI4 Error detected

SPA Bridge ASIC detected a

FRAME/FIFO_OVF/DIP2/OOF Error.

Tx eSPI4 Error detected

SPA Bridge ASIC detected a

OOF/DIP4/LOS/SEQ/BURST/EOP_ABORT/PKT
_GAP Error.

SBIT ECC Error detected

SPA Bridge ASIC detected a SingleBit

correctable ECC error.

SPA fatal interrupt in bay [dec]

SPA Bridge ASIC has detected a SPA fatal

interrupt.

SPA Bus 1 Parity Error detected

SPA Bridge ASIC detected a Parity Error on

SPA Bus for SPA0 (SPA Bridge0) or SPA1
(SPA Bridge1).

SPA Bus 3 Parity Error detected

SPA Bridge ASIC detected a Parity Error on

SPA Bus for SPA2 (SPA Bridge0) or SPA3
(SPA Bridge1).

SPI4 or SPA Bus 1 Error detected

SPA Bridge ASIC detected a SPI4 or SPA Bus

Error for SPA0 (SPA Bridge0) or SPA1 (SPA
Bridge1).

SPI4 or SPA Bus 3 Error detected

SPA Bridge ASIC detected a SPI4 or SPA Bus

Error for SPA2 (SPA Bridge0) or SPA3 (SPA
Bridge1).

Unable to recover the I2C bus [dec]

The attempted I2C bus hang recovery was

not successful.

Hang detected on I2C bus [dec],

attempting recovery

An I2C bus hang has been detected.

Recovery is automatically attempted.
Should the recovery be successful, a
BUS_UNHANG_SUCCESS message is issued;
otherwise, an UNRECOVERABLE_BUS_HANG
is issued.

Successfully recovered the i2c bus [dec]

The I2C bus hang has been cleared

successfully. I2C communication is restored
on the bus.

Unable to recover the I2C bus [dec]

The attempted I2C bus hang recovery was

not successful.

Hang detected on I2C bus [dec],

attempting recovery

An I2C bus hang has been detected.

Recovery is automatically attempted.
Should the recovery be successful, a
BUS_UNHANG_SUCCESS message is issued;
otherwise, an UNRECOVERABLE_BUS_HANG
is issued.

Successfully recovered the i2c bus [dec]

The I2C bus hang has been cleared

successfully. I2C communication is restored
on the bus.

A driver PCI bus transaction failed,

restarting driver

A PCI bus transaction on the device has

failed due to an inconsistency between the
hardware and software state of the
ethernet device. To recover, the driver
must be restarted and the hardware reset.

A driver PCI bus transaction failed,

restarting driver

A PCI bus transaction on the device has

failed due to an inconsistency between the
hardware and software state of the
ethernet device. To recover, the driver
must be restarted and the hardware reset.

Invalid media rate read from onboard PHY

When performing an MDI read to the PHY

over the PCI bus, the returned value
indicated an invalid media rate (speed).

Invalid media rate read from onboard PHY

When performing an MDI read to the PHY

over the PCI bus, the returned value
indicated an invalid media rate (speed).

The ethernet driver cannot get I/O

privileges

The ethernet driver is unable to get the

necessary privileges to perform an
operation vital to its functionality.

The ethernet driver cannot get I/O

privileges

The ethernet driver is unable to get the

necessary privileges to perform an
operation vital to its functionality.

[chars]

Internal error while receiving a packet over

the control network on to the service
processor. Error is harmless if only one or
two are seen. If seen in a persistent
manner, call support.

[chars]

Internal error while receiving a packet over

the control network on to the service
processor. Error is harmless if only one or
two are seen. If seen in a persistent
manner, call support.

[chars]

Internal error while receiving a packet over

the control network on to the service
processor. Error is harmless if only one or
two are seen. If seen in a persistent
manner, call support.

EA debug initialization failed, err [dec]

([chars]).

Debug initialization failed in packet

programming path. Packet path
initialization is aborted and may be retried.

EA trace initialization failed, err [dec]

([chars]).

Trace initialization failed in packet

programming path. Packet path
initialization is aborted and may be retried.

Protocol packet path initialization failed:

Invalid PID:[dec]

Protocol packet path initialization failed due

to invalid protocol ID provided by protocol
module. Initialization is aborted and may
be retried.

Trace initialization failed, err [dec]

([chars]).

Trace initialization failed in packet path.

Packet path initialization is aborted and
may be retried.

Protocol([dec]) packet path initialization

failed: No packet event notify registration

Protocol packet path initialization failed due

to no packet event notification registered
from protocol module. Initialization is
aborted and may be retried.

Protocol packet path initialization failed due

Protocol packet path initialization failed: No to no protocol data from protocol module.
protocol data
Initialization is aborted and may be retried.

Protocol([dec]) packet path initialization

failed: No Rx notify function

Protocol packet path initialization failed due

to no Rx packet reception function provided
by protocol module. Initialization is aborted
and may be retried.

PLIM event thread creation failed. Packet

PLIM event thread creation failed, exiting... path initialization is aborted and may be
[dec] ([chars])
retried.

Unsupported CFM config on interface

handle [hex]. Total packets dropped [dec]

Ethernet OAM CCMs are configured for an

Layer 2 VPN interface over an unsupported
pseudowire encapsulation.

[chars]: CFM bundle offload is not

supported on this card.

CFM is configured over bundle interfaces

with bundle members configured on trident
line cards. Bundle offload is globally
configured. Bundle offload is only
supported on typhoon line cards.

[chars]: CFM bundle offload is not

supported on standby DSC.

CFM is configured over bundle interfaces

with bundle members configured on
standby DSC of cluster. Bundle offload is
globally configured. Bundle offload is only
supported on line cards on the primary
DSC.

Large numbers of single bit ECC errors

Excessive [chars] errors in last hour: [dec]. have been detected on the sp node in the
Node reboot scheduled
past hour. The node will be rebooted.

[chars]: Failed to mmap to Kernel dumper

information in syspage, error: [chars].

Failed to mmap to Kernel dumper

information in syspages.

[chars]: Failed to set reboot cause into

syspage, error: [chars].

The failure on setting reboot cause to

syspage before performing Kernel Dump.

Hourly summary of ECC errors : single bit

ECC errors: [dec]

If SBE errors are detected, the IOS message

prints the number of SBEs seen in the last
hour.

[chars]

SPP PDMA Initialization Error message.

Error Allocating <[dec]> bytes of memory

SPP PDMA dll Memory Allocation Error

message.

[chars]: [chars]
[chars] [chars]

SPP PDMA Thread Error message.

Output progress to RP console.

Internal error: String [chars]

This is an informational message in the SSE

FIB NPU to indicate that an internal error
was seen when trying to check consistency
of internal data structures.

PD Infra error: [chars]: String [chars]

This is an informational message in the SSE

FIB NPU to indicate that an error was seen
when trying to access PD infra resource.

Attribute error: String [chars]

This is an informational message in the SSE

FIB to indicate that engine layer identified
an error with attribute passed by upper
layers

Init error: [chars]: Caused by [chars]

This is an informational message in the SSE

FIB to indicate that an error was seen
during init operation. A return code is
returned to PI which can do a retry or exit
based on if error persists.

Internal error: String [chars]

This is an informational message in the SSE

FIB to indicate that an internal error was
seen when trying to check consistency of
internal data structures.

PD Infra error: [chars]: String [chars]

SSE IPV4-EA: Critical error: [chars]
SSE IPV4-EA: Error: [chars] [dec]
SSE IPV4-EA: Error: [chars]
SSE IPV4-EA: Error: [chars] [pointer]
SSE IPV4-EA: Debug info: [chars]
SSE IP-EA: Critical error: [chars]
SSE IP-EA: Error: [chars] [dec]
SSE IP-EA: Error: [chars]
SSE IP-EA: Error: [chars] [pointer]
SSE IP-EA: Debug info: [chars]
SSE MPLS-EA: [chars]

This is an informational message in the SSE

FIB to indicate that an error was seen when
trying to access PD infra resource.
SSE IPV4-EA, Critical error
SSE IPV4-EA, error
SSE IPV4-EA, error
SSE IPV4-EA, error
SSE IPV4-EA, Debug information
SSE IP-EA, Critical error
SSE IP-EA, error
SSE IP-EA, error
SSE IP-EA, error
SSE IP-EA, Debug information
SSE MPLS-EA, error

SSE MPLS-EA: [chars] Error: [chars]([dec])

SSE MPLS-EA: [chars]: [chars]

SSE MPLS-EA, error

SSE MPLS-EA, Debug information

Prefix count is below 90-percent of the

hardware limit of [dec] prefixes

PLU resmon on the node has detected that

prefix usage is below the limit

Using 95-percent of the hardware limit of

[dec] prefixes, delete the routes
immediately to prevent any traffic loss

PLU resmon on the node has detected that

the number of routes has exceeded
prescribed limits. Any further increase
routes will lead to traffic loss.

PLU resmon on the node has detected that

Above the hardware limit of [dec] prefixes, the number of routes has exceeded
delete the routes immediately to prevent
prescribed limits. Any further increase
any traffic loss
routes will lead to traffic loss.

Using 90-percent of the hardware limit of

[dec] prefixes, delete the routes
immediately to prevent any traffic loss

PLU resmon on the node has detected that

the number of routes has exceeded
prescribed limits. Any further increase
routes will lead to traffic loss.

[chars].

software initialization error

Performance Traffic Monitoring: configured

monitoring interval duration value is
rounded to the closest supported number
on this linecard. Applied interval duration is
[unsigned int] seconds.

On a certain type of ASR9k linecards,

different step values are supported in
monitoring interval duration configuration.
When unsupported value is configured, the
closest supported value will override user
configuration.

Some metric types of performance traffic

monitoring are not supported on a few
types of linecards. User added a new
bundle-ethernet member that belongs to a
linecard with limitation. As a result,
performance traffic monitoring on the
bundle-ethernet interface will have
limitation on that specific member port.
Existing member ports will receive the
Performance Traffic Monitoring: A new
same metric coverage of performance
bundle-ethernet member is added on a line traffic monitoring. Also, the new bundle
card that does not support RTP or MDI
member will not be fully activated and
metric.
overall bundle state will remain out of sync.

Error! [chars]: Invalid number of

arguments\n

An error occurred due to invalid argument

as input to the function in stats infra
component.

Error! [chars]: Invalid argument [chars] \n

An error occurred due to invalid argument

as input to the function in stats infra
component.

[chars]: event_manager_create failed. rc = An error occurred in stats infra during

[dec]\n
event manager creation

[chars]:[dec]
stats_infra_map_stats_segment failed :
([hex])[chars]\n

An error occurred in stats infra component.

The error occurs if the pointer to the root
page for the stats infrastructure is not
received .

Mutex Revive failed [chars] [chars]\n

An error occurred in stats infra component.

The mutex could not be revived.

Error! fabric stats infra is already

running.pid:[dec]\n

An error occurred since stats infra process

is running already.

[chars]: ErrStr:[chars]\n

An error occurred in stats infra component.

The error string gives the reason for the
error.

ErrStr:[chars]\n

An error occurred in stats infra component.

The error string gives the reason for the
error.

ErrStr:[chars]\n

An error occurred in stats infra component.

The error string gives the reason for the
error.

[chars] rc=[chars]\n

An error occurred in stats infra component.

The error string and return value gives the
reason for the error.

[chars]: ErrStr:[chars]\n

An error occurred in stats infra component.

The error string gives the reason for the
error.

[chars], rc=[chars]\n

An error occurred in stats infra component.

The error string and return value gives the
reason for the error.

ErrStr:[chars]\n

An error occurred in stats infra component

timer initialization function. The error string
gives the reason for the error.

Spanning Tree Port [chars] state changed

to [chars]

Spanning Tree Port's state change

indication.

[chars], [dec]

Error condition from switch driver which

may affect spanning tree operation on
control ethernet. Normally spanning tree
can tolerate a few of these errors as long
as the driver comes back to a good state.
Large number of these messages can
indicate bad health of control-ethernet.

Reload notification received. Reloading in

[dec] secs

Message indicating that the kAA on the

card has received a reload notification from
sysldr for powering off the card and the
card is going to reload soon. card state is
IOX_RUNNING

Calling reboot ([chars])

Message indicating that the node has

received a reload notification and the node
is going to reload soon. This message is
logged after the delay over since the
NODE_RELOAD message is logged.

KAA: could not create [chars]: [chars]

During the KAA process Initialization we

create an separate path for the LWM
Channel which acts as a rendezvous point
for the client to send responses back.

The Connect to the MBUS Client Failed to

Initialize for the Slot [dec]

When the Keep Alive Agent (KAA) is

Initialized it tries to establish an connection
with the MBUS Server using the event
Manager thread.This connection is cached
for any future communication. Failure in
this leads to process respawn

KAA : Couldn't create Event Manager for

the Slot [dec]

Create an Event Manager for the KAA to

handles all its events. Failure in this event
thread creation leads to the KAA process
Initialization issues.

KAA : Couldn't fetch event

While Monitoring the health of our local

agent using ping-reply mechanism if we
dont get an proper agent to respond to the
ping we wait on an infinite loop for events.
In case of Failure the communication
breaks.

Couldn't register to mdr notification

Once the KAA process has started the

information is sent to the sysmgr process
indicating its readiness. Then we register
with the MDR application to get
notifications on the shutdown events.The
Failure in this registration can cause sync
up issues.

KAA - could not create [chars] Thread

An Failure has been detected while

spwaing an thread for the process initiated.
Error is displayed in the Message.

Failed to initialize ltrace buffer in [chars].

Error: [chars]

Ltrace buffer will not be available.

Debuggability will be reduced because of
lacking of ltrace buffer.

msg_send failed to server : [chars]

Call failed to send message to MBI-Hello

LWM server.

Failed to connect to server : [chars]

A communication problem occurred

between the MBI client and server, perhaps
because the communications infrastructure
is not set up. The MBI operation in progress
will not be carried out.

Timer timed out from server : [chars]

Timer timed out between the MBI client

and server, perhaps because the
communications infrastructure is not set
up. The MBI operation in progress will not
be carried out.

Timeout is ignored due to Warm Reload

Ping request is not received from RP. It's

not normal but expected under Warm
Reload situation. Only when Warm Relad
fails, please collect information.

[chars]

KAA process failed to collect the Fabric ping

diagnostic date.

Calling reboot ([chars])

Message indicating that the PRP has

received a reload notification and it is
going to be reloaded soon. This message is
logged after the delay over since the
NODE_RELOAD message is logged.

Reload notification received. Reloading in

[dec] secs

Message indicating that the mbi-hello on

the standby PRP has received a reload
notification from sysldr for powering off the
card and the card is going to reload soon.
The card is currently in MBI-RUNNING state.

[chars]

A fatal error was encountered while trying

to use OS resources, KAA process exits
from here preventing the card going to IOXRUN state.

Failed to initialize ltrace buffer in [chars].

Error: [chars]

Ltrace buffer will not be available.

Debuggability will be reduced because of
lacking of ltrace buffer.

Excess memory size : [chars]

The DRAM memory size got from the card

is out of range to accommodate in the
message to be sent to DSC. The size is
truncated to 0 and sent.

msg_send failed to server : [chars]

A communication problem occurred while

sending message between the MBI client
and server. The 'send message' operation
is retried continuously with 1 second
interval.

Failed to connect to MBI ping server :

[chars]

A communication problem occurred

between the MBI client and server, perhaps
because the communications infrastructure
is not set up. The operation to connect is
carried out continuously. If the error
persists, system manager will restart the
process.

Timer timed out from MBI ping server :

[chars]

Timer timed out between the MBI client

and server, perhaps because the
communications infrastructure is not set
up. The operation to connect is carried out
continuously.

[chars]

Unexpected low severity problem. The

problem could be OS system call failures or
MBUS access failures.

LC in slot [dec] configured in [chars]

'Whenever A E7 card is configured to

change the mode, this warning message is
displayed'

slot [dec]: ping failure using the fabric

connection, last sequence# tx=[unsigned
int], rx=[unsigned int]

Fabric ping is failed for the specified card.

The card was OK for a while, but then failed
to reply to fabric pings. The affected card
will be reloaded after collection of
debugging files.

slot [dec]: timeout waiting for initial ping

using the fabric connection, last tx
sequence#=[unsigned int]

Following boot, the card never succeeded

in replying to fabric pings.

User configured to disable Self ping

through fabric/mbus using CLI, '(adminFailed self-ping for a sustained period. Local config)#service sysldr XXX-ping warn'. Now
connection to fabric must be down. autoSelf fabric ping timed out. But this will not
reset disabled by user config, so no action cause Router reboot because, user
will be taken.
configured auto-reset disable.

Self fabric ping is failed for the active RP.

slot [dec]: self ping failure using the fabric The chassis will be reloaded with non
connection, last sequence# tx=[unsigned redundant RP chassis or the failover will
int], rx=[unsigned int]
happen with the redundant RP chassis.

slot [dec]: timeout waiting for initial self

ping using the fabric connection, last tx
sequence#=[unsigned int]

Self fabric ping is failed for the active RP.

The chassis will be reloaded with non
redundant RP chassis or the failover will
happen with the redundant RP chassis.

slot[dec]: [chars]

sysldr encountered an critical error

condition. The conditions include fping diag
thread creation failures.

slot [dec]: fabric connection is down.

Reloading.

Fabric ping failure for the card, which was

in IOX-RUNNING state. Card network is nonresponsiveness.

slot [dec]: fabric connection to MBI is down. Fabric ping failure for the card, which was
Reloading.
in MBI state.

It is inability of MBI to boot a node's full

image. This indicates a problem in
communication or installation. Tech support
should be contacted. Several attempts will
be made to retry the image loading, and
slot [dec]: MBI cannot load IOX, retrying by then the card will be put in the 'reset' state
reloading
after too many failures.

Reload Full Chassis to apply New Shared

Memory Window Size

User configured new shmwin size. Router is

running with old Shared Memory Window
Size. New Shared Memory Window Size will
come in to effect once user reload
complete chassis.

Sysldr process will be exited with failure.

System manager will attempt to recreate
Could not determine Active dsc node, Error: the process. If the problem persists, system
[chars]
manager will reload the card.

Fabric bandwidth change: Shutting down

card in slot [dec]

Loss or OIR of one or more fabric cards has

led to the card being shut down Card will
be powered off and put in admin down
state

Card ungraceful reboot detected in slot

[dec].

Card is going to reboot UNGRACEFULLY,

due to some error condition.

Failed to initialise debug in plugin thread

Sysldr process will be exited with failure.

System manager will attempt to recreate
the process. If the problem persists, system
manager will reload the card.

ECM thread creation failed. Sysldr process

will be exited with failure. System manager
will attempt to recreate the process. If the
problem persists, system manager will
Could not create ECM thread, Error: [chars] reload the card.

Shutting down card in slot [dec], ordered

by Envmon.

Volatile shutdown was ordered by Envmon

because environmental problems (with
temperature, voltage, power etc) were
detected.

slot[dec]: [chars], errno=[dec]

For displaying sysldr error information with

an errno.

[chars] errno=([dec])

For displaying sysldr error information with

error string.

Connection to event manager to receive

and send events failed. The failure can
happen either in creating or clearing
connection. Sysldr process will be exited
with failure. System manager will attempt
to recreate the process. If the problem
Event manager connection failed in [chars], persists, system manager will reload the
Error: [chars]
card.

Attaching event message from clients of

shelf manager to event manager failed.

Attaching event message type from clients

of shelf manager to event manager failed.
Sysldr process will be exited with failure.
System manager will attempt to recreate
the process. If the problem persists, system
manager will reload the card.

Failed to create an instance of event

manager for receiving events from other
applications: Error: [chars]

Creation of event manager instance is

failed. Sysldr process will be exited with
failure. System manager will attempt to
recreate the process. If the problem
persists, system manager will reload the
card.

plugin thread exited event dispatch loop

Sysldr process will be exited with failure.

System manager will attempt to recreate
the process. If the problem persists, system
manager will reload the card.

Registration for OIR events, fabric

bandwidth chnage and any card
malfunction event because of fabric errors
from fabric controller. Sysldr process will be
exited with failure. System manager will
attempt to recreate the process. If the
Registration with fabric controller to receive problem persists, system manager will
events failed. Error: [chars]
reload the card.

slot [dec]: fabric connection down. Please

investigate the cause

The card network is non-responsiveness

and the fabric ping is failed. The card is not
reloaded because of 'service sysldr fabricping warn' configuration. This indicates a
problem in qnet communication.

False removal notification from FCTL,

restarting: Slot=[dec]

This error indicates that sysloader received

a false notification from fabric controller
about a OIR of a card. Further The card will
be reloaded by sysloader to get the card
fresh booted.

slot=[dec], [chars]: [chars] \n

Field diagnostic binary image download

errors.

Could not create Field Diagnostics process

Failed in creating field diagnostics process

failed. Sysldr process will be exited with
failure. System manager will attempt to
recreate the process. If the problem
persists, system manager will reload the
card.

Sysldr process will be exited with failure.

System manager will attempt to recreate
Could not create fabric [chars]ping thread, the process. If the problem persists, system
Error: [chars]
manager will reload the card.

Could not create sysldr FSM information

thread

Sysldr process will be exited with failure.

System manager will attempt to recreate
the process. If the problem persists, system
manager will reload the card.

Unable to locate mbus firmware file

mbus firmware (aka 'ucode') file cannot be

found

Failed to init gsp notification APIs. Exiting

Sysldr process will be exited with failure.

System manager will attempt to recreate
the process. If the problem persists, system
manager will reload the card.

Hardware error on slot [dec] - stopping

Card is shutdown due to persistent

hardware errors reported by MBUS of the
card.

Failed to detect the issu phase, Error:

[chars]

Could not determine in which phase the

ISSU operation currently running.

No valid iMSG license found for LC Card will

No valid license: Shutting down card in slot be powered off and put in admin down
[dec]
state
slot [dec]: DRAM memory is insufficient.
Available memory: [dec]M Minimum
Required: [dec]M, Recommended:
[chars]M. LC not loaded

For indicating insufficient LC CPU (ie. dram)

memory

slr_server_field_diag_handle: could not

create path: [chars], Error: [chars]

Could not create path for LWN channnel.

Sysldr process will be exited with failure.
System manager will attempt to recreate
the process. If the problem persists, system
manager will reload the card.

Shutting down card in slot [dec], card is

malfunctioning.

Volatile shutdown was ordered by FCTL

because card is malfunctioning.

slot [dec]: too many reload attempts stopping

Sysldr has attempted maximum reloads to

bring the card up. The card did not come
up. Sysldr puts the card in reset state.

slot [dec]: CPU not responding, last

sequence# [dec], please investigate the
cause.

For displaying notification of LC software

non-responsiveness. The slot is not
reloaded because of the 'service sysldr
mbus-ping warn' configuration. This
indicates a problem in communication w/
the card's CPU via MBUS.

MBUS Shut operation failed. Error type:

[dec].

MBUS SHUT operation triggered by CLI,

'sysldr_tool mbusshut <slot>' failed due to
error type mentioned.

LC in slot [dec] will be brought in GREEN

mode(Data structure corrupted)

'When this message is displayed the LC's

context data structure is corrupted and
doesn't take into consideration the
configured mode of E7 card and LC will
come in Green mode irrespective of the
configuration'

Nodecontrol operation failed. Error type:

[dec].

Node control operation triggered by CLI,

'sysldr_tool nodecontrol [shut|shutsync|
unshut] <slot>' failed due to error type
mentioned.

Node isolation operation triggered by CLI,

'sysldr_tool nodeisolation [isolate|
Node isolation operation failed. Error type: query_status] <slot>' failed due to error
[dec].
type mentioned.

For displaying notification of card software

non-responsiveness. This indicates a
slot [dec]: [chars] CPU not responding, last problem in communication w/ the card's
sequence# [dec], reloading
CPU via MBUS.

slot [dec]: Failed to allocate a pcode, Error

= [chars]

Sysldr process will be exited with failure.

System manager will attempt to recreate
the process. If the problem persists, system
manager will reload the card.

PFI thread exited event dispatch loop

Packet Forwarding Infra thread exited in

event dispatch loop. Sysldr process will be
exited with failure. System manager will
attempt to recreate the process. If the
problem persists, system manager will
reload the card.

Could not create plugin thread for slot:

[dec], Error: [chars]

Failed to create thread responsible for card

state transitions. Sysldr process will be
exited with failure. System manager will
attempt to recreate the process. If the
problem persists, system manager will
reload the card.

Could not create power manager main

thread

Creation of power manager main thread is

failed. Sysldr process will be exited with
failure. System manager will attempt to
recreate the process. If the problem
persists, system manager will reload the
card.

slot [dec]: too many ungraceful reloads stopping

Sysldr has attempted maximum reloads to

bring the card up. The card did not come
up. Sysldr sends a mbus message to set
the config-register of the affected RP to
zero and puts it in ROMMON. This could be
due to standby RP booted up with wrong
mbi image.

Shutting down card in slot [dec], shutdown Shutdown of the card was configured using
configured.
the 'hw-module shut' command.

Could not get my slot# [chars], Error:

[chars]

Request to mbus to get the local slot

number is failed. Sysldr process will be
exited with failure. System manager will
attempt to recreate the process. If the
problem persists, system manager will
reload the card.

Could not create SPA polling thread, Error:

[chars]

Failure in creating SPA polling thread.

Sysldr process will be exited with failure.
System manager will attempt to recreate
the process. If the problem persists, system
manager will reload the card.

Error in setting up system database:

[chars], Error: [chars]

Setting up system database is failed. Sysldr

process will be exited with failure. System
manager will attempt to recreate the
process. If the problem persists, system
manager will reload the card.

slot [dec]: Failed to create a timer, Error =

[chars]

Sysldr process will be exited with failure.

System manager will attempt to recreate
the process. If the problem persists, system
manager will reload the card.

Failed to initialize a timer for slot=[dec]

with Error: [chars]

Indicates that one of the timer initialization

requests made by sysldr process could not
be completed. In such case state machine
not run as expected and may result in an
undesired state of the card sysldr process
will be reloaded to recover from such
situation.

slot [dec]: LC image too large, not loading

For displaying notification of LC image

being too large to download. LC will be
reloaded by sysldr as MBI download fails
with this reason.

slot=[dec] mod=[dec] [chars]

An unexpected module in LC sent reply to

sysldr for agent report request. Sysldr
expects MBUS agent / ROMMON / MBI-Hello
/ KAA to respond to report request
message. The response is got from none of
these agents.

Powering Off card in slot [dec], power-down power off was configured using the 'hwconfigured.
module power disable' command.

Shutting down card in slot [dec], ordered

by Envmon/FCTL/PSARB

Card is shut down by Envmon or FCTL or

Psarb. It is Volatile shutdown.

Could not determine if I am dsc, Error:

[chars]

Sysldr process runs only on DSC. Since it

could not determine if it is on dsc, it can
not determine to run or not. Sysldr process
will be exited with failure. System manager
will attempt to recreate the process. If the
problem persists, system manager will
reload the card.

Message size used by shelf manager does

not match with the size assumed by
clients. Size at Shelf manager: [dec], size
at clients : [dec]

Sysldr (shelf manager) sends a message to

publish the card state to clients. The size
used in sysldr does not match with the size
used by clients. This message indicates the
mismatch in the size.

slot [dec]: [chars] is down-rev (V[dec].

[dec]), suggest upgrade to (V[dec].[dec]),
[chars]

For displaying notification of ucode of the

card is less than the bundled version
(down-rev).

OS service to publish common data

initialization failed: Error: [chars]

OS service to publish common data

initialization failed:.

[chars] ([chars])

For displaying sysldr debugging

information with an errno string.

Mbus Connect Failed

Could not establish a connection to mbus.

slot [dec]: unsupported mbus fw v[dec].

[dec] found, replacing ...

Found an unsupported mbus firmware

version running.

slot [dec]: mbus agent in ROM,

downloading RAM mbus fw v[dec].[dec] ...

This means MBUS agent on the card was

running with ROM FW and sysldr
attempting to download RAM FW. If the
download fails, contact cisco support for
analysis.

slot [dec]: card failed, auto-reset disabled,

needs 'hardware-module location r/s/i
Warning a user that a card has failed while
reload'
they have disabled auto-reset.

slot [dec]: LC failed, simulated OIR has

been requested - LC is now admin-down

Warning a user that a card has failed while

they have turned on 'simulated-OIR'

Packet client cleanup returned error

Sysldr process will be exited with failure.

System manager will attempt to recreate
the process. If the problem persists, system
manager will reload the card.

Pakman Init Failed

Could not establish a connection to

pakmgr.

slot[dec]: [chars]

This is to indicate the error occurred while

discovering inserted SPA types.

slot [dec]: LC type currently unsupported

For displaying notification of software nonsupport.

Receive DOWNLOAD_SUCCESS from slot

[dec], while waiting for
DOWNLOAD_SUCCESS_WARM

Card seems to have been cold reloaded

after an attempt to warm reload the card.

slot[dec]: warm reload not initiated by

sysmgr ([chars])

The card WARM reload request to sysmgr

returned an error

[chars]

For displaying sysldr warning information.

slot [dec]: [dec]M present, recommend

[dec]M memory
[chars]

For indicating possibly insufficient LC CPU

(ie. dram) memory
Unexpected low severity problem.

Fabric bandwidth change: [chars]

Failure/recovery/OIR of one or more SFC's

or CSC's

Fabric bandwidth change: Restarting card

in slot [dec]

Restoration or OIR of fabric bandwidth has

allowed a card to be restarted

The RP is going to bring down from IOX

running state because keep alive message
ping is not received by sysldr from the
DRP in slot [dec] is now disabled, reloading card.

Event manager connection open failed for

[chars], Error: [chars]

Opening connection to event manager to

receive and send events failed. The failure
can happen either in opening connection to
configuration or operational or inter
process communication areas.

Joined slot [dec] - already running IOX-LC

LC join notification because of either sysldr

restarted or RP failover occurred.

LC in slot [dec] is now running IOX

For displaying health and readiness of LC

slot [dec]: Unable to get mbus eeprom

contents

For displaying notification of mbus

nonresponsiveness to get eeprom contents.

Now monitoring DRP in slot [dec] - running For displaying notification of discovered
IOX-DRP
DRP and keep alive monitorable state.
Now monitoring RP in slot [dec] - running
IOX-RP

For displaying notification of discovered RP

and keep alive monitorable state.

OIR: Node [chars] inserted\n

Entity specified in the messages is inserted

into the chassis.

OIR: Node [chars] removed\n

Entity specified in the messages is

removed from the chassis.

Restarted slot [dec] - now running IOX-LC

For displaying LC restart notification.

Accepted restart request for slot [dec].

[chars]

For displaying LC restart request.

RP in slot [dec] is now disabled, reloading

The RP is going to bring down from IOX

running state because keep alive message
ping is not received by sysldr from the
card.

RP in slot [dec] is now running IOX

For displaying health and readiness of RP

slot[dec]: [chars]

For displaying sysldr informational events

on card removal / insertion.

The non-volatile MBUS CAN jam reset

counter is incremented when the MBUS
agent detects a CAM jam condition and
hard-resets itself in an attempt to recover.
It is an idication thet there might be a
faulty MBUS module somewhere in the
system, not necesarily on this particular
slot [dec]: non-zero CAN jam reset counter card.

Card graceful reboot detected in slot [dec]. The specified slot is graceful rebooting

'When fping failure is detected on the

remote node, sysldr sends a message to
the remote node to collect all the debug
information. This message is to convey the
Media connection to the node [dec] failed, user that diag collection is going to happen
Collecting the debug information which
on the remote node which may take few
may take few minutes
minutes'

'Whenever a fping failure is detected on

the remote node, sysldr sends a message
to the remote node to collect all the debug
information. This message is to convey the
Media connection to the node [dec] failed, user that diag collection is going to happen
Node will be reloaded after collecting the
on the remote node which may take few
debug information which may take few
minutes and subsequently the node will be
minutes
reloaded'

MBI cannot be downloaded on that card

Incompatible rommon versions.[dec].[dec] because ROMMON does not support that
for RP in slot [dec]
feature.

Failed to initialize ltrace buffer in [chars].

Error: [chars]

Ltrace buffer will not be available.

Debuggability will be reduced because of
lacking of ltrace buffer.

ROMMON upgrade is completed for card in ROMMON Upgrade is completed on the

Slot [dec], Card is being reset
card. The card will be reset.
ROMMON Upgrade is happening on the
card. Any OIR operations or hw-module
reload or shutdown or power disable
commands could interrupt the ROMMON
upgrade which may result in card going to
ROMMON upgrade is in progress for card in indeterminate state. This message cautions
Slot [dec], Please do not perform any card user not to perform any of these
restart operations on the card
operations.
Presently unsupported card WARM reload
condition: [chars]

The card WARM reload is presently

unsupported in the specified condition

Checkpoint initialization failed, Sysldr hot

standby is disabled. Error: [chars]
slot[dec]: [chars]

Failed to initialize checkpoint and hot

standby is disabled so standby can not
sync with active RP. Sysldr process will be
exited with failure. System manager will
attempt to recreate the process. If the
problem persists, system manager will
reload the card.
sysldr debugging information.

[chars]: debug_init_event([chars]) failed

error [chars]

Failed to switch ON debug event on sysldr

server side.

[chars]: debug register failed error [chars]

Failed to register debug events on sysldr

server side.

Insufficient memory.

Unable to allocate more heap memory.

Connection to sysdb path '[chars]' failed:

'[chars]'.

Unable to maintain connection to a critical

sysdb path.

slot [dec]: sysdb_item_delete failed for

item '[chars]' in file=[chars], line=[dec]
([chars] [hex])

Unable to delete a sysdb item.

slot [dec]: sysdb_item_get failed for item

'[chars]' in file=[chars], line=[dec] ([chars]
[hex])
Unable to get a sysdb item.
Notification for changes to sysdb bindpoint Unable to receive notifications of changes
'[chars]', tuple '[chars]' failed: '[chars]'.
to a critical sysdb tuple.
slot [dec]: sysdb_item_set failed for item
'[chars]' in file=[chars], line=[dec] ([chars]
[hex])
Unable to set a sysdb item.
Event initialization failed, Error: [chars]

Initialization of events with event manager

failed.

[chars], error=[dec]

Error in thread/event manager creation for

sysldr process.

[chars]

For displaying sysldr's informational

events. The events include the field diag
test activities, fabric ping simulation events
and configuration apply notifications.

Internal Error. File [chars], line [dec]:

[chars].

Serious internal logic or data error.

couldn't lock mutex at File [chars], line

[dec]

Failed in locking mutex resource.

couldn't unlock mutex at File [chars], line

[dec]

Failed in unlocking mutex resource.

Receive DOWNLOAD_SUCCESS_WARM from

slot [dec], new processes are coming up
Card seems warm reloaded successfully
slot[dec]: [chars]

For displaying sysldr debugging

information.

Wrong context to report MBUS fault

Event context to report MBUS message is

wrong. This will result in no MBUS
messages to report faults are received.

Error: [chars] [hex]

The message is used to report TEJAS

DRIVER critical errors.

Error: [chars] [hex]

The message is used to report TEJAS

DRIVER generic errors.

Info: [chars]

The message is used to report TEJAS

DRIVER generic info.

Slot [chars] sensor [chars] temperature

[dec].[dec]C [chars] threshold [dec].0C

LC on die temperature sensor is risen

above or fallen below critical threshold.LC
or Port will be shutdown in 24 Hrs

Slot [chars] sensor [chars] temperature

[dec].[dec]C [chars] threshold [dec].0C

LC on die temperature sensor is risen

above or fallen below major threshold.

Slot [chars] sensor [chars] temperature

[dec].[dec]C shutdown in ([dec]) hours

LC or port shutdown is schedulded if the

temperature value stays above the critical
thresold for 24 hrs or more

A software error occurred in the ToFab

driver component during initialization:
[chars]

The fabricq_prp_driver process which

controls the ToFab driver on the route
processor has failed to initalize and cannot
recover automatically. This is a software
fault. The ToFab driver controls the
hardware that transmits data to the fabric.
It runs in the fabricq_prp_driver process. An
unrecoverable failure of the
fabricq_prp_driver process may prevent
this route processor card from
communicating with other cards on the
chassis. %s indicates the type failure

TFQ: bad memory alignment on ptr [hex] of TFQ encountered a fatal memory allocation
bytes [dec]\n
error

This message indicates that a packet was

attempted to be sent over the fabric but
Buffer header invalid, length [unsigned int] the buffer header was invalid. This usually
start offset [unsigned int]
indicates a software error.

Chopper desc queue [dec] full - pri

[unsigned int] enq [unsigned int] deq
[unsigned int] blog [unsigned int] mask
[hex]

This message indicates that too many

messages are being sent to the chopper.
There is no more room in the chopper
descriptor queue to send new packets. This
is a temporary condition that should get
cleared or the FIA registers on both PRP
and LC need investigation.

Could not complete operation due to lack

of memory: Purpose for memory [chars]

The system is running out of memory and

was not able to allocate sufficient memory
to carry out a management operation. %s
indicates what the memory was intended
for.

tfq manager encountered a fatal error and

is not able recover from the error. A reason
text will be supplied call support with this
tfq: fatal error encountered, reason=[chars] text.

tfq: fatal error encountered,

reason=[chars], Error: [dec], Function:
[chars]

tfq encountered a fatal error and is not able

to recover from the error. A reason text will
be supplied call support with this text. An
integer errno will also be printed.

tfq: general information,<[chars]>

The TFQ's informational message.

tfq: service degrading error, reason =

[chars]

The tfq encountered an error that would

lead to degraded service.

TFQ: slot [dec] alloc [dec] bytes error on ptr TFQ encountered a fatal memory allocation
[hex] of max [hex]\n
error

TFQ: memory alloc [dec] bytes error on ptr TFQ encountered a fatal memory allocation
[hex] of max [hex]\n
error

No memory available for Chopper queues

in [chars]

This message indicates that Chopper driver

is not able to allocate memory for the
Queues and other use. This usually
indicates a memory problem.

Packet [unsigned int] too large: size

[unsigned int], status [unsigned int]

An application attempted to send a packet

larger than the hardware can handle from
the route processor to another card. This
usually indicates a software error. packet
%u is the packet or buffer handle size %u
is the packet or buffer size status %u is the
buffer status flags

Particle size too large [unsigned int]

This message indicates that a packet was

attempted to be sent over the fabric but
was too large to be sent. This usually
indicates a software error.

This message indicates that a packet was

attempted to be sent over the fabric but
Node Id invalid, rc:[dec] node:[hex] stream: the node id was invalid. This usually
[dec] paktype:[dec]
indicates a software error.

tfq: this function <[chars]> is not yet

implemented

TFQ, a function was not implemented.

Failed to duplicate packet sent to the

chopper old:[hex] new:[hex] loc:[dec]

This message indicates that there was

failure in the case where the Chopper
driver had to duplicate a packet.

The fabric driver has failed to return a

packet buffer to the free list. If this error
keeps recurring it could result in the
depletion of buffer for packets sent from
The toFab driver failed to return a buffer to the route processor to the fabric. %s is the
the free list. Details: [chars]
entity processing the packet.

Invalid packet sent to the chopper [hex]

This message indicates that an invalid

packet was sent to the Chopper driver.

Invalid packet sent to the fabric driver.

Packet [hex]

This message indicates that an invalid

packet was sent to the driver handling
packets to be sent from the router
processor card to other cards in the
chassis. The packet will be dropped and the
system should recover from the error. %x
packet handle.

TFQ: packet type [dec]

TFQ is using a legacy packet type

PRP To Fabric Queue pri:[dec] slot:[dec] is

blocked, report fault to sysldr

The PRP to fabric queue of the particular

priority and slot is blocked. This means
packets that go that slot of that priority will
fail. In addition, at least one of the
multicast queues (high or low priority) is
blocked as well. This likely means the
particular slot is failing to accept packets
and will cause backpressure on the PRP to
fabric queue. Because of hardware design,
if a multicast packet includes the one faulty
slot then it will be stuck in the tofab
multicast queue, and subsequent multicast
packets will be stuck even if they do not
include the faulty slot in their slotmask.
Having the unicast queue blocked is
somewhat allowable, but having the
multicast queue blocked is not acceptable.
This error message is raised when both
unicast and multicast are blocked. In order
to alleviate this problem, the fault is sent to
sysldr, for sylsdr to decide to reload the
slot. It is very likely that the problem slot
was not accepting packets. priority:%d is
either 0-low priority or 1-high priority slot:
%d is the slot that is back pressuring to the
PRP

tfq: invalid option <[chars]> passed to tfq

server

Startup option supplied to TFQ is not valid.

A packet destined for a remote card was

received by the fabric driver. The
destination node in the packet header
could not be decoded by the ToFab
component of the fabric driver on the route
processor. This is a software error and the
packet will be dropped. rc:%d is the return
code of the function that parsed the node.
node Id %u is the node identifier received
by the driver which failed to parse stream:
%d is the message stream over which the
Node identifier is invalid, rc:[dec] node Id packet was sent to the driver. flags %u are
[unsigned int] stream:[dec] flags:[unsigned flags used by packet manager to identify
int]
the packet.

Unexpected packet has been received by

ToFab driver. Type: [dec]

An unexpected packet type was sent to the

ToFab driver This will not impact
functionality or performance. It is being
reported for informational purposes only.
Type: %d is the type of the packet that the
driver rejected.

Asr9k pagent process exiting because

[chars], func:[chars] , line [dec], error code The pagent process exited due to the
[chars]\n
reason mentioned in the message.

[chars], func: [chars] ,Info - [chars]\n

Informational condition and/or failure. The

process can continue functioning as
expected despite the failure.

[chars] in func: [chars]\n

This is a programmed diagnostic debug

message.

Failed to [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

failed to connect to the active/standby

arbitration process, ([chars])

The c12000 arbitration process could not

be contacted. This process provides the
active/standby state information required
to decide whether the local time should be
aligned to the chassis system time. This
problem may cause the system error
messages reported by the specified card to
be offset in time, or being displayed
without a timestamp.

Unable to get the active/standby state from

the arbitration process. This process
provides the active/standby state
information required to decide whether the
local time should be aligned to the chassis
system time. This problem may cause the
system error messages reported by the
unable to get the active/standby arbitration specified card to be offset in time, or being
state, ([chars])
displayed without a timestamp.

failed to get system time, ([chars])

An attempt to read the local time has

failed. This can prevent local time to be
reported as a response to the 'show clock
sync' command. It can also prevent
alignment of the local time to the chassis
system time broadcasted by the dsc. This
may cause the system error messages
reported by the specified card to be offset
in time, or being displayed without a
timestamp.

This process needs to know if it runs on the

DSC or standby DSC. An error occured
while trying to get the information from the
DSC process. The process will voluntary
Failed to learn if we are running on the DSC exit, and should get automatically
([chars])
restarted.

failed to read a message from MBUS,

([chars])

A failure was encountered when receiving a

message from the MBUS driver. MBUS is
the communication service over which
chassis system time is broadcasted. This
problem may cause the system error
messages reported by the specified card to
be offset in time, or being displayed
without a timestamp.

failed to set system time, ([chars])

An attempt to set the local time has failed.

This problem will prevent alignment of the
local time to the chassis system time
broadcasted by the dsc. This may cause
the system error messages reported by the
specified card to be offset in time, or being
displayed without a timestamp.

failed to write a message to MBUS,

([chars])

A failure was encountered when sending a

message to the MBUS driver. MBUS is the
communication service over which chassis
system time is exchanged. This problem
will cause the local time to be missing in
the 'show clock sync' response.

Local clock is set to [chars]

Local clock is set by timesync client.

failed to connect to the active/standby

arbitration process, ([chars])

The c12000 arbitration process could not

be contacted. This process provides the
active/standby state information required
to decide whether the local time should be
broadcasted over MBUS communication to
other cards. This problem may cause other
cards in the chassis to have an unaligned
time base, and may cause system error
messages reported by the other cards to
appear offset in time, or to be displayed
without a timestamp.

Unable to get the active/standby state from

the arbitration process. This process
provides the active/standby state
information required to decide whether the
local time should be broadcasted over
MBUS communication to other cards. This
problem may cause other cards in the
chassis to have an unaligned time base,
and may cause system error messages
reported by the other cards to appear
unable to get the active/standby arbitration offset in time, or to be displayed without a
state, ([chars])
timestamp.

failed to get system time, ([chars])

An attempt to read the local time has

failed. This can prevent local time from
being broadcasted to other cards in the
chassis. This problem may cause other
cards in the chassis to have an unaligned
time base, and may cause system error
messages reported by the other cards to
appear offset in time, or to be displayed
without a timestamp.

failed to write a message to MBUS,

([chars])

A failure was encountered when sending a

message to the MBUS driver. MBUS is the
communication service over which chassis
system time is exchanged. This problem
may cause other cards in the chassis to
have an unaligned time base, and may
cause system error messages reported by
the other cards to appear offset in time, or
to be displayed without a timestamp.

Logical Router information is required to

know if the local time should be
broadcasted to other cards in the system.
The process failed to get the Logical Router
information within what is considered a
normal period. This problem may cause
other cards in the chassis to have an
unaligned time base, and may cause
system error messages reported by the
failed to get Logical Router information, still other cards to appear offset in time, or to
trying...([chars])
be displayed without a timestamp.

FAILED DUE TO : [chars]

An internal software error has occurred in

Turbo IPCP library

Invalid entry address T-[dec] chan:[dec]

Addr:[hex] cerr: [dec]

An error was encountered while validating

tlu address range

Failed to initialze Topology Manager:

[chars]

This syslog is printed when Topology

Manager or its clients fail to initialize
necessary data structures and memories. If
the error originates from the system call
the error message is also printed.

Failed to allocate memory: [chars]

An explanation is provided in the syslog.

Child interface not found: ifhandle =

[unsigned int]

Although a reference to a child interface is

found in the parent interface, the child
interface cannot be found via the search
routine. Either the child interface failed to
be added in the first place or the reference
was not cleared when the child was
deleted.

TSEC([chars]): Detected error(s). Last error: TSEC driver on CPU received an errored
[chars]. Error code: [hex]
packet. The packet was dropped.

[chars] for tsec[dec], value [hex], error

[dec].\n

The particular operation mentioned in the

message failed due to the reason indicated
by the error code. This is critical failure.
Driver cannot operate.

The particular operation mentioned in the

message failed due to the reason indicated
by the error code. This is not a critical
failure. The process can continue
[chars] tsec[dec], value [hex], error [dec]\n functioning as expected despite the failure.

[chars] for tsec[dec], hwq [hex], count

[dec].\n

A packet buffer passed to driver is not

aligned to required boundary. This is not a
critical failure and corrected by driver.
Driver can continue function.

[chars] for tsec[dec] is [hex].\n

The particular operation mentioned in the

message gave an informative message.
This is not a failure.

tsec[dec] [chars]([hex])=[hex]\n

The particular operation mentioned in the

message gave an informative message
with one register value. This is not a
failure.

tsec[dec] [chars]([hex])=[hex], [chars]

([hex])=[hex]\n

The particular operation mentioned in the

message gave an informative message
with two register values. This is not a
failure.

[chars] for tsec[dec] is [hex].\n

The particular operation mentioned in the

message gave an informative message.
This is not a failure.

GRE Tunnel is not supported on SIP700

linecards in ASR9K. If the SIP700 exists in
the chassis where GRE Tunnel is
configured, ASR9K will emit this warning
message and GRE Tunnel interface is not
created in SIP700 hardware. The GRE
Tunnel adjacency will be programmed to
drop on the SIP700 linecard. That means
any prefixes resolving over the GRE Tunnel
GRE Tunnel not supported on this linecard. will point to drop adjacency on the SIP700.
Set the network topology to avoid this line If SIP700 receives GRE encapsulated
card for GRE Tunnel packets
packets, those will be dropped as well.

[chars], error [chars]

This is an error message in the CRS

platform specific code software to indicate
anomolies that are not FATAL. This error is
most likely caused by a temporary situation
within the feature code. %s - indicates the
reason for the failure. %s - is the decoded
error reason.

High Priority Interrupt received [chars]

A High priority Interrupt was received from

the Turbo FPGA. The current RP will failover
as part of recovery.

Severe problem in ACTIVE SMDC and

STANDBY SMDC is not available/ready

Severe error happened in the ACTIVE

SMDC, needs switchover but STANDBY
SMDC is not available/ready.

Failed to create event channel

SMDC fault manager: Failed to create event

channel.

Failed to allocate memory for msgbuf

SMDC fault manager: Failed to allocate

memory for msgbuf.

Received ABORT Interrupt

The SPP dump was aborted since it

received an interrupt.

SPP DUMP MMAP failed

Need to memory map the PCI memory in

order to do IPC, but unable to mmap the
PCI memory of the SMDC

Card Shutdown configured, going to shut it The SMDC is configured shut down.

Initiating SMDC Switchover

Severe error happened in the SMDC card,

so initiating switch over.

LINUX HBB MMAP failed

There is a problem in memory mapping the

linux heartbeat buffer used in order to
communicate to linux.

Got an interrupt from Octeon processor:

[chars]

An interrrupt is received from the octeon

code with the cause %s

Unable to mmap for OCTEON interrupt

cause code of SMDC

Need to memory map for getting the

octeon interrupt cause code, but unable to
mmap.

Unable to mmap PCI device memory of

SMDC

Need to memory map the PCI memory in

order to do communicate, but unable to
mmap the PCI memory of the SMDC.

Interrupt received [chars]

An interrupt was received from the Turbo

FPGA.

The turbo has received a error from the

module with some severity. And necessary
Received an error notification from Module: actions like SMDC shut or switch over are
[chars] Severity: [chars]
automatically taken.

Please reload [chars] for the 'no booster

shutdown loc' command to take effect

The daughter card has to be reloaded since

the config has been modified.

Reload notification received

Sysldr reload notification received by the

SMDC fault manager.

Failed to allocate memory for SPP Dump

SMDC fault manager: Failed to allocate

memory for SPP Dump.

Card is going to silent reload

The SMDC is going in for a silent reload due

to internal failures.

Booster turbo driver initialization failed:

([chars] [chars])

Booster turbo driver failed to initialize. The

effect is that Interrupt handling in turbo will
fail to function. %s - indicates the reason
for the failure. %s - is the error reason.

UDLD protocol detects if a link is unidirectional and disables the port. UniUDLD protocol detected Uni-directional link directional links can cause problems in
on [chars], Port Disabled
ethernet networks and should be fixed.

UDLD api mutex lock failed line[[dec]]

err[[chars]]

A mutex lock acqure failed in the api

context, for UDLD lib around the line
number specified in error message.

UDLD api mutex unlock failed line[[dec]]

err[[chars]]

A mutex unlock failed in the api context,

for UDLD lib around the line number
specified in error message.

[chars]

A fatal error was encountered, and the

program exited. A separate thread is
created to handle 'fpd upgrade'. If this
pthread_create fails, we are posting this
CRITICAL error. This might be a rare
situation.

Failed to attach async message handler :

[chars]

Failed to attach async message handler. An

handler is not being setup for receving all
asynchronous messages. This involves
exiting the upgrade_fpd or lc_upgrade_fpd
process.

Failed to create upgrade-fpd channel :

[chars]

Failed to create lc_fpd_upgrade (driver)

channel using event_manager_create. An
error occured in fpd proceses, to creae
event manager which causes a channel to
be created. This might involve exiting the
upgrade_fpd or lc_upgrade_fpd process.
Some features like 'upgrade hw-module
fpd' may not work if this error is seen.

Event block failed : [chars]

Failed to block event

AUTO FPD UPGRADE ERROR: [chars]

Errors from the fw manager process. This

error might occur due to 'AUTO UPGRADE'
feature getting some errors due to
sysdb_bind(), getting invalid arguments
etc.,

ERROR occured while FPD upgrade: [chars] An error was encountered

Msg reply failed : [chars]

Failed to send message reply.

lc_upgrade_fpd process sends a reply
message to RP so that RP is unblocked by
calling msg_reply().

Failed to update FPD : [chars] [chars]

The update operation for the specified FPD

has failed.

Failed to attach sync message handler :

[chars]

Failed to attach sync message handler. An

handler is not being setup for receiving all
synchronous message. This involves exiting
the upgrade_fpd or lc_upgrade_fpd
process.

[chars] instance [dec] is down-rev (V[dec].

[dec]), upgrade to (V[dec].[dec]). Use
the \upgrade hw-module fpd\ CLI in admin
mode.
For displaying down-rev notification.
[chars] instance [dec] is running minimum
software version supported (V[dec].[dec]),
it can be upgraded to (V[dec].[dec]). Use
the \upgrade hw-module fpd force\ CLI in
admin mode.

Currently running FPD version meets the

minimum software version required for the
image, but a higher version FPD is
available in the image and can be
upgraded using 'force' CLI option.

[chars] instance [dec] is down-rev (V[dec].

[dec]), upgrade to (V[dec].[dec]). Please
consult TAC or Firmware Upgrade
documentation before proceeding to
upgrade rommonA.
For displaying down-rev notification.
[chars] instance [dec] is severely up-rev
(V[dec].[dec]), downgrade to (V[dec].
[dec]). Use the \upgrade hw-module fpd\
CLI in admin mode.

For displaying severely up-rev notification.

A Warning message while doing

fpd_upgrade: [chars]

display warning messages

AUTO_FPD_UPGRADE_INFO: [chars]

These messages indicate some kind of info

related to the auto FPD upgrade process
when it runs in the context of the install
upgrade.

It indicates that a FPD has been upgraded

or downgraded successfully. The current
Successfully [chars] [chars] subtype image image version and the upgraded image
for [chars] on location [chars]
version are displayed.

Starting to [chars] [chars] subtype image

from [dec].[dec] to [dec].[dec] for [chars]
on location [chars]

It indicates that a FPD image upgrade or

downgrade has started. The current image
version and the upgraded image version
are displayed.

[chars]

It indicates the status of FPD upgrade like

start, in-progress, end.

Upgrade is going on: [chars] [chars]

It indicates the status of FPD upgrade on a

particular location.

[chars] [chars] instance [dec] on location

It indicates the status of FPD upgrade for
[chars] cannot be upgraded using location certain FPGAs on a particular location when
all option
location all option is used.
Overflow in fabric-loader upgrade.\nNew
fabric-loader size=[dec] > available
size=[dec]

When upgrading the new fabric-loader, if

the size of the new fabric-loader is greater
than the available size overflow error is
reported.

Flash device unsupported. RP ROMMON

upgrade aborting

The flash type discovered does not match

the list of supported devices.

The upgrade was unable to complete

Unable to find upgrade image for this card because the image to burn into flash could
type within IOX. Internal Error
not be located within IOX.

Invalid image type specified in upgrade

message ([dec])

The message used to initiate the upgrade

contained an image type that was invalid.

Invalid message type specified in upgrade The message used to initiate the upgrade
message ([dec])
contained a message type that was invalid.

Overflow in ROM monitor upgrade.\nNew

ROM monitor size=[dec] > available
size=[dec]

When upgrading the new rommon, if the

size of the new rommon is greater than the
available size overflow error is reported.
Current upgrade operation is aborted. The
size of the flash on the card is to be
extended before retrying.

Overflow in ROM monitor upgrade.\nNew

ROM monitor size=[dec] > available
size=[dec]

When upgrading the new rommon, if the

size of the new rommon is greater than the
available size overflow error is reported.

Daughter(Booster) card not present,

upgrade failed.

NO Daughter card present for specified

slot. So RP couldn't upgrade uboot. CLI
'(admin)#upgrade uboot location <slot>',
Failed.

[chars]

When upgrading the new rommon, RP's

rommon will be corrupted if the user reload
the RP. So, The user must not reload RP
when its rommon is being upgraded. If RP's
rommon is corrupted, it needs to be RMAd.

Unable to properly set up upgrade

infrastructure. Internal error

The upgrade was unable to complete

because the type of the card did not fall
into the expected set of possibilities. This is
likely due to an internal programming error.

Unable to complete upgrade. Cannot

determine version info (rc=[dec])

The upgrade was unable to complete

because the version of either the current
ROMMON image or the version of the
image to be used for the upgrade could not
be determined.

Rommon / BSL upgrade Complete.

The upgrade process lost its connectivity

with upgrade_rom process. It could be due
to some crash in upgrade_rom process.
However, upgrade of rommon / BSL was
not interrupted, and its complete. The
version may not be updated in System
Database. It will be updated after next
reload of the slot.

Rommon / Fabric-downloader upgrade

Complete.

The upgrade process lost its connectivity

with upgrade_rom process. It could be due
to some crash in upgrade_rom process.
However, upgrade of rommon / Fabricdownloader was not interrupted, and its
complete. The version may not be updated
in System Database. It will be updated
after next reload of the slot.

Erase sectors fail for [chars]

The upgrade of the ROMMON failed

because failed to erase sectors.

Erase sectors fail for [chars]

The upgrade of the specfied component

(ROMMON/Fabric-loader) failed because
failed to erase sectors.

Failed to read file [chars]

The upgrade of the ROMMON failed

because failed to read the file buffer. It will
not affect the existing service on the card.

Failed to read file [chars]

The upgrade of the specfied component

(ROMMON/Fabric-loader) failed because of
a file read system call failed.

Failed to create upgrade ROM channel :

[chars]

Failed to create upgrade ROM channel

using event manager.

Debug initialization failed

Initialization of the debug event failed

during ROMMON upgrade. This can be
observed when the debug is enabled.

Debug registration failed : [chars]

debug registration call failed during

ROMMON upgrade. This can be observed
when the debug is enabled.

[chars] : [chars]

Generic failure of any event manager API.

Failed to open file [chars] : [chars]

The upgrade of the ROMMON failed

because failed to open the image file. It will
not affect the existing service on the card.

Failed to open file [chars] : [chars]

The upgrade of the specfied component

(ROMMON/Fabric-loader) failed because of
a system call fails to open the relevant file.

Failed to send reply message : [chars]

KAA process failed to reply back to sysldr

client on the upgrade results using LWM.

Failed to allocate memory

This indicates a low memory condition. The

upgrade of the specfied component would
fail.

Failed to allocate memory

This indicates a low memory condition. The

upgrade of the specfied component would
fail.

Flash Device is not Supported - Linecard

upgrade won't continue

The current driver only supports

AM29LV800B flash device.

Failed to get slot number

The platform library call to retrieve the slot

information failed.

Failed to map device address : [chars]

A system call failed to map the device

physical address. Current upgrade
operation is ended. If the problem persists,
contact TAC for analysis.

Failed to map device address : [chars]

A system call failed to map the device

physical address.

Failed to unmap mapped object : [chars]

A system call failed to un-map the device

physical address. Current upgrade
operation is aborted.

Failed to unmap mapped object : [chars]

A system call failed to un-map the device

physical address.

Programming flash fail for [chars]

The upgrade of the ROMMON failed

because failed to erase sectors.

Programming flash fail for [chars]

The upgrade of the specfied component

(ROMMON/Fabric-loader) failed because
failed in programming flash.

Programming flash header fail for [chars]

The upgrade of the specfied component

(ROMMON/Fabric-loader) failed because
failed in programming flash header.

Failed to access file [chars] : [chars]

The upgrade of the ROMMON failed

because failed to get file stat. It will not
affect the existing service on the card.

Failed to access file [chars] : [chars]

The upgrade of the specfied component

(ROMMON/Fabric-loader) failed because of
file download statistic system call failure.

Failed to send status

The KAA process failed to send the upgrade

status to the client, sysldr.

Verify flash fail for [chars]

The upgrade of the ROMMON failed

because failed to verify FLASH.

Verify flash fail for [chars]

The upgrade of the specfied component

(ROMMON/Fabric-loader) failed because
failed to verify flash.

Verify flash header fail for [chars]

The upgrade of the specfied component

(ROMMON/Fabric-loader) failed because
failed to verify flash header.

USB Controller transaction taking longer

than 5 seconds

Controller transaction is taking excess

time.

EUSB0 device not available

EUSB0 device not available

EUSB0 device not responding

EUSB0 device not responding

The internal usb device 0, transaction

taking longer than 5 seconds

USB device 0 transaction is taking excess

time.

EUSB1 device not available

EUSB1 device not available

EUSB1 device not responding

EUSB1 device not responding

The internal usb device 1, transaction

taking longer than 5 seconds

USB device 1 transaction is taking excess

time.

Hub transaction taking longer than 5

seconds

USB Hub transaction is taking excess time.

An USB operation is taking too long. If the

USB:DEV=[hex]:EPT=[hex]:QH=[hex]:TD=[ device refers to an internal device, the
hex]:ELAPSED=[dec]s:START=[chars]
board needs immediate attention.

CompactFlash transaction taking longer

than 5 seconds

Compact Flash transaction is taking excess

time.

Bag register failed for rules. Reason:

[chars]

EDM Bags are used to share information

between components using sysdb. This
Error indicates that bag registration failed.

Dll Initialization for [chars] failed. Reason:

[chars]

Cpuctrl driver tried to register for a dll but

it encountered an error. The driver might
lose some of its functionality.

Event Manager create failed for [chars].

Reason: [chars]

Cpuctrl Event Manager create error

Event Manager notify failed for [chars].

Reason: [chars]

Cpuctrl Event Manager notify error

Sysdb Register EDM failed. Reason: [chars] Cpuctrl Sysdb Register EDM error

Port [dec] is in OTN mode, loopback not

supported\n

Loopback is not supported in OTN mode.

MAC Address is not configured for this

card \n

This message provides information about

the mac configuration.

MIB stats collection encountered an issue

for port [dec] error [chars]\n

MIB stats collection failed due to some

internal error.

MAC Address is not configured for MPA

bay_id : [dec] \n

This message provides information about

the MPA mac configuration. A typical
reason is that MPA is not inserted properly.

Advanced optic pie is deactivated for

OTN(G709). Port [dec] is shutdown\n

Advanced optic pie is deactivated for

OTN(G709).

A valid license for OTN (G709) is not found.

Port [dec] is shutdown\n
Necessary license for G709 is not found.

PFM failure : [chars]\n

PFM module issue. Message string details

the exact issue.

PFM failure : [chars] port [dec] \n

PFM module issue. Message string details

the exact issue.

UDLR is not supported. This may happen if

Interface doesn't support UDLR port [dec]\n the loopback is configured.
This message provides information about
the pluggable tranceiver. Possible causes
[chars] for port [dec] is disabled - [chars]\n are not supported speed, autoneg.

[chars]\n

This message provides information about

the kind of events happening in the
software at the location where the error is
seen. This is not an error message.
Typically, following events are logged in
this message type. - End of successfull
initialization of the software. - Start and
end of a processing of new object that
needs to programmed to the hardware. Configuration is not applicable to the port.

Exiting because [chars], error code

[chars]\n

The Ether-Ctrl process exited due to the

reason mentioned in the message.

[chars], port [dec], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

Failed to [chars], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

[chars] [chars]\n

The particular operation mentioned in the

message occured due to some reason. This
is not a critical failure, the process can
continue functioning as expected despite
the failure.

Exiting because [chars], error code

[chars]\n

The Ether-Ctrl process exited due to the

reason mentioned in the message.

[chars], port [dec], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

Failed to [chars], error code [chars]\n

The particular operation mentioned in the

message failed due to some reason. This is
not a critical failure, the process can
continue functioning as expected despite
the failure.

[chars] [chars]\n

The particular operation mentioned in the

message occured due to some reason. This
is not a critical failure, the process can
continue functioning as expected despite
the failure.

SIP_LCPM_SHOW: [chars] , [chars]

sip-pm show encountered trouble in sysdb

operations, im control server bind or imc
interface get operations

sip_lcpm_show: invalid option passed to

sip_lcpm_show command. [chars]

Startup option supplied to SIP_LCPM_SHOW

is not valid.

Shared memory access:[chars]. rc [hex],

[chars] \n

Shared memory access operations like

init,open or bind might have failed.

sip_pm_test: fatal error encountered,

reason=[chars]

sip_pm test encountered a fatal error and is

not able recover from the error. A reason
text will be supplied call support with this
text.

sip_pm_test: fatal error encountered,

reason=[chars], errno=[unsigned int]

sip_pm_test encountered a fatal error and

is not able to recover from the error. A
reason text will be supplied call support
with this text. An integer errno will also be
printed.

Platform Manager encountered an

initialization error A reason text will be
sip_pm: error encountered, reason=[chars] supplied to describe the error.

sip_pm encountered a non-recoverable

sip_pm: error encountered, reason=[chars], error A text reason and error number will
errno=[dec]
be supplied to describe the error.

Platform Manager warning: [chars]

The Platform Manager encountered a

provisioning warning.

THOR CPP PM: [chars]

sip_pm for information purpose only.

Error creating trace file <[chars]%s>; rc

[hex] ([chars])

The ltrace file could not be created.

PLATFORM IPV4-EA: Error: [chars] [hex]

A runtime error occurred in IP EA. Typically,

this is an error where the software fails due
to failure during forwarding feature
programming. Here is a list of possible
reasons for this message (not all-inclusive).
- Failed to initialize software. This condition
indicates a problem with the software on
the card where the error is seen. Typically,
this occurs when the software tries to
initialize invalid objects. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid. - Failed to program forwarding
features. This condition indicates a problem
where the software fails to program
forwarding features to the hardware.

PLATFORM IPV4-EA: Error: [chars]

A runtime error occurred in IP EA. Typically,

this is an error where the software fails due
to failure during forwarding feature
programming. Here is a list of possible
reasons for this message (not all-inclusive).
- Failed to initialize software. This condition
indicates a problem with the software on
the card where the error is seen. Typically,
this occurs when the software tries to
initialize invalid objects. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid. - Failed to program forwarding
features. This condition indicates a problem
where the software fails to program
forwarding features to the hardware.

A runtime error occurred in IP EA. Typically,

this is an error where the software fails
during initialization. Here is a list of
possible reasons for this message (not allinclusive). - Failed to initialize software.
This condition indicates a problem with the
software on the card where the error is
seen. Typically, this occurs when the
software tries to initialize invalid objects. Invalid objects. This condition indicates a
problem where the object being processed
by the software is invalid during
initialization. - Failed to program forwarding
features. This condition indicates a problem
where the software fails to program
forwarding features to the hardware during
PLATFORM IPV4-EA: Init. Error: [chars] [hex] initialization/ configuration.

PLATFORM IPV4-EA: Init. Error: [chars]

A runtime error occurred in IP EA. Typically,

this is an error where the software fails
during initialization. Here is a list of
possible reasons for this message (not allinclusive). - Failed to initialize software.
This condition indicates a problem with the
software on the card where the error is
seen. Typically, this occurs when the
software tries to initialize invalid objects. Invalid objects. This condition indicates a
problem where the object being processed
by the software is invalid during
initialization. - Failed to program forwarding
features. This condition indicates a problem
where the software fails to program
forwarding features to the hardware during
initialization/ configuration.

PLATFORM IPV4-EA: Memory Error: [chars]

[hex]

A runtime error occurred in IP EA. Typically,

this is an error where the memory
allocation / access fails. Here is a list of
possible reasons for this message (not allinclusive). 1) Memory exhaustion due to
overall system load 2) Shared memory
access failure 3) Memory leaks leading to
resource exhaustion

PLATFORM IPV4-EA: Memory Error: [chars]

A runtime error occurred in IP EA. Typically,

this is an error where the memory
allocation / access fails. Here is a list of
possible reasons for this message (not allinclusive). 1) Memory exhaustion due to
overall system load 2) Shared memory
access failure 3) Memory leaks leading to
resource exhaustion

PLATFORM IPV4-EA: Error: [chars] [hex]

A runtime error occurred in IP EA. Typically,

this is an error where the software fails to
initialize or programming of forwarding
feature fails. Here is a list of possible
reasons for this message (not all-inclusive).
- Failed to initialize software. This condition
indicates a problem with the software on
the card where the error is seen. Typically,
this occurs when the software tries to
initialize invalid objects. - Invalid objects.
This condition indicates a problem where
the object being processed by the software
is invalid. - Failed to program forwarding
features. This condition indicates a problem
where the software fails to program
forwarding features to the hardware.

PLATFORM IPV4-EA: Error: [chars]

A runtime error occurred in IP EA. Here is a

list of possible reasons for this message
(not all-inclusive). - Invalid objects. This
condition indicates a problem where the
object being processed by the software is
invalid. - Resource limitations. This
condition indicates a problem where the
software has limited resources to operate
on.

VKG IPV4-EA: [chars] Failure: [chars] [hex]

This is a failure message in the ASR9K

platform specific code software to indicate
anomolies that are not serious failure . This
failure is most likely caused by a temporary
situation, so is unlikely to re-occur.

VKG IPV4-EA: [chars] Failure: [chars]

This is an failure message in the ASR9K

platform specific code software to indicate
anomolies that are not serious failure. This
failure is most likely caused by a temporary
situation, so is unlikely to re-occur.

VKG IPV4-EA: [chars] Failure: [chars]

[chars] [hex]

This is an failure message in the ASR9K

platform specific code software to indicate
anomolies that are not serious FAILURE.
This Failure is most likely caused by a
temporary situation, so is unlikely to reoccur.

VKG IPV4-EA: Debug info: [chars]

This is an information message in the

ASR9K platform specific code software. The
message is for debug purposes only and
not an error.

PLATFORM IPV6-EA: Error: [chars] [hex]

A runtime error occurred in IPv6 EA.

Typically, this is an error where the
software fails due to failure during
forwarding feature programming. Here is a
list of possible reasons for this message
(not all-inclusive). - Failed to initialize
software. This condition indicates a
problem with the software on the card
where the error is seen. Typically, this
occurs when the software tries to initialize
invalid objects. - Invalid objects. This
condition indicates a problem where the
object being processed by the software is
invalid. - Failed to program forwarding
features. This condition indicates a problem
where the software fails to program
forwarding features to the hardware.

PLATFORM IPV6-EA: Error: [chars]

A runtime error occurred in IPv6 EA.

Typically, this is an error where the
software fails due to failure during
forwarding feature programming. Here is a
list of possible reasons for this message
(not all-inclusive). - Failed to initialize
software. This condition indicates a
problem with the software on the card
where the error is seen. Typically, this
occurs when the software tries to initialize
invalid objects. - Invalid objects. This
condition indicates a problem where the
object being processed by the software is
invalid. - Failed to program forwarding
features. This condition indicates a problem
where the software fails to program
forwarding features to the hardware.

A runtime error occurred in IPv6 EA.

Typically, this is an error where the
software fails during initialization. Here is a
list of possible reasons for this message
(not all-inclusive). - Failed to initialize
software. This condition indicates a
problem with the software on the card
where the error is seen. Typically, this
occurs when the software tries to initialize
invalid objects. - Invalid objects. This
condition indicates a problem where the
object being processed by the software is
invalid during initialization. - Failed to
program forwarding features. This
condition indicates a problem where the
software fails to program forwarding
features to the hardware during
PLATFORM IPV6-EA: Init. Error: [chars] [hex] initialization/ configuration.

PLATFORM IPV6-EA: Init. Error: [chars]

A runtime error occurred in IPv6 EA.

Typically, this is an error where the
software fails during initialization. Here is a
list of possible reasons for this message
(not all-inclusive). - Failed to initialize
software. This condition indicates a
problem with the software on the card
where the error is seen. Typically, this
occurs when the software tries to initialize
invalid objects. - Invalid objects. This
condition indicates a problem where the
object being processed by the software is
invalid during initialization. - Failed to
program forwarding features. This
condition indicates a problem where the
software fails to program forwarding
features to the hardware during
initialization/ configuration.

PLATFORM IPV6-EA: Memory Error: [chars]

[hex]

A runtime error occurred in IPv6 EA.

Typically, this is an error where the memory
allocation / access fails. Here is a list of
possible reasons for this message (not allinclusive). 1) Memory exhaustion due to
overall system load 2) Shared memory
access failure 3) Memory leaks leading to
resource exhaustion

PLATFORM IPV6-EA: Memory Error: [chars]

A runtime error occurred in IPv6 EA.

Typically, this is an error where the memory
allocation / access fails. Here is a list of
possible reasons for this message (not allinclusive). 1) Memory exhaustion due to
overall system load 2) Shared memory
access failure 3) Memory leaks leading to
resource exhaustion

PLATFORM IPV6-EA: Error: [chars] [hex]

A runtime error occurred in IPv6 EA.

Typically, this is an error where the
software fails to initialize or programming
of forwarding feature fails. Here is a list of
possible reasons for this message (not allinclusive). - Failed to initialize software.
This condition indicates a problem with the
software on the card where the error is
seen. Typically, this occurs when the
software tries to initialize invalid objects. Invalid objects. This condition indicates a
problem where the object being processed
by the software is invalid. - Failed to
program forwarding features. This
condition indicates a problem where the
software fails to program forwarding
features to the hardware.

PLATFORM IPV6-EA: Error: [chars]

A runtime error occurred in IPv6 EA. Here is

a list of possible reasons for this message
(not all-inclusive). - Invalid objects. This
condition indicates a problem where the
object being processed by the software is
invalid. - Resource limitations. This
condition indicates a problem where the
software has limited resources to operate
on.

VKG IPV6-EA: [chars] Failure: [chars] [dec]

This is a failure message in the ASR9K

platform specific code software to indicate
anomolies that are not serious failure. This
failure is most likely caused by a temporary
situation, so is unlikely to re-occur.

VKG IPV6-EA: [chars] Failure: [chars]

This is a failure message in the ASR9K

platform specific code software to indicate
anomolies that are not serious failure. This
failure is most likely caused by a temporary
situation, so is unlikely to re-occur.

VKG IPV6-EA: Debug info: [chars]

This is an information message in the

ASR9K platform specific code software. The
message is for debug purposes only and
not an error.

VKG_LCPM_SHOW: [chars] , [chars]

VKG_LCPM_SHOW encountered an error

vkg_pm_show: invalid option passed to

vkg_pm_show command. [chars]

Startup option supplied to

VKG_LCPM_SHOW is not valid.

PLATFORM MPLS-EA: [chars]

A runtime error occurred in MPLS EA.

Typically, this is an error where the
software fails to initialize or programming
of forwarding feature fails. Here is a list of
possible reasons for this message (not allinclusive). - Failed to initialize software.
This condition indicates a problem with the
software on the card where the error is
seen. Typically, this occurs when the
software tries to initialize invalid objects. Invalid objects. This condition indicates a
problem where the object being processed
by the software is invalid. - Failed to
program forwarding features. This
condition indicates a problem where the
software fails to program forwarding
features to the hardware.

PLATFORM MPLS-EA: [chars] [hex]

A runtime error occurred in MPLS EA.

Typically, this is an error where the
software fails to initialize or programming
of forwarding feature fails. Here is a list of
possible reasons for this message (not allinclusive). - Failed to initialize software.
This condition indicates a problem with the
software on the card where the error is
seen. Typically, this occurs when the
software tries to initialize invalid objects. Invalid objects. This condition indicates a
problem where the object being processed
by the software is invalid. - Failed to
program forwarding features. This
condition indicates a problem where the
software fails to program forwarding
features to the hardware.

PLATFORM MPLS-EA: [chars]

A runtime error occurred in MPLS EA.

Typically, this is an error where the
software fails to initialize or programming
of forwarding feature fails. Here is a list of
possible reasons for this message (not allinclusive). - Failed to initialize software.
This condition indicates a problem with the
software on the card where the error is
seen. Typically, this occurs when the
software tries to initialize invalid objects. Invalid objects. This condition indicates a
problem where the object being processed
by the software is invalid. - Failed to
program forwarding features. This
condition indicates a problem where the
software fails to program forwarding
features to the hardware.

PLATFORM MPLS-EA: [chars] Error: [chars]

([hex])

A runtime error occurred in MPLS EA.

Typically, this is an error where the
software fails to initialize or programming
of forwarding feature fails. Here is a list of
possible reasons for this message (not allinclusive). - Failed to initialize software.
This condition indicates a problem with the
software on the card where the error is
seen. Typically, this occurs when the
software tries to initialize invalid objects. Invalid objects. This condition indicates a
problem where the object being processed
by the software is invalid. - Failed to
program forwarding features. This
condition indicates a problem where the
software fails to program forwarding
features to the hardware.

PLATFORM MPLS-EA: Init. Error: [chars]

[hex]

A runtime error occurred in MPLS EA.

Typically, this is an error where the
software fails to initialize or programming
of forwarding feature fails. Here is a list of
possible reasons for this message (not allinclusive). - Failed to initialize software.
This condition indicates a problem with the
software on the card where the error is
seen. Typically, this occurs when the
software tries to initialize invalid objects. Invalid objects. This condition indicates a
problem where the object being processed
by the software is invalid. - Failed to
program forwarding features. This
condition indicates a problem where the
software fails to program forwarding
features to the hardware.

PLATFORM MPLS-EA: Init. Error: [chars]

A runtime error occurred in MPLS EA.

Typically, this is an error where the
software fails to initialize or programming
of forwarding feature fails. Here is a list of
possible reasons for this message (not allinclusive). - Failed to initialize software.
This condition indicates a problem with the
software on the card where the error is
seen. Typically, this occurs when the
software tries to initialize invalid objects. Invalid objects. This condition indicates a
problem where the object being processed
by the software is invalid. - Failed to
program forwarding features. This
condition indicates a problem where the
software fails to program forwarding
features to the hardware.

A runtime error occurred in MPLS EA.

Typically, this is an error where the memory
allocation / access fails. Here is a list of
possible reasons for this message (not allinclusive). 1) Memory exhaustion due to
overall system load 2) Shared memory
PLATFORM MPLS-EA: Memory Error: [chars] access failure 3) Memory leaks leading to
[hex]
resource exhaustion

A runtime error occurred in MPLS EA.

Typically, this is an error where the memory
allocation / access fails. Here is a list of
possible reasons for this message (not allinclusive). 1) Memory exhaustion due to
overall system load 2) Shared memory
access failure 3) Memory leaks leading to
PLATFORM MPLS-EA: Memory Error: [chars] resource exhaustion

vkg_pm_test: fatal error encountered,

reason=[chars]

vkg_pm test encountered a fatal error and

is not able recover from the error. A reason
text will be supplied call support with this
text.

vkg_pm_test: fatal error encountered,

reason=[chars]

vkg_pm test encountered a fatal error and

is not able recover from the error. A reason
text will be supplied call support with this
text.

vkg_pm_test: fatal error encountered,

reason=[chars], errno=[dec]

vkg_pm_test encountered a fatal error and

is not able to recover from the error. A
reason text will be supplied call support
with this text. An integer errno will also be
printed.

vkg_pm_test: fatal error encountered,

reason=[chars], errno=[dec]

vkg_pm_test encountered a fatal error and

is not able to recover from the error. A
reason text will be supplied call support
with this text. An integer errno will also be
printed.

PM: runtime error encountered,

reason=[chars], errno=[dec]

Platform Manager encountered a runtime

error. A text reason and an error number
are supplied to describe the error. Runtime
errors usually concern individual interfaces.
PM continues. Applications often retry the
same operation to recover.

svc pm encountered a fatal error and is not

able to recover from the error. A text
svc-pm: error encountered, reason=[chars], reason and error number will be supplied to
errno=[dec]
describe the error.

PM: initialization error encountered,

reason=[chars]

Platform Manager encountered an

initialization error. A reason text is supplied
to describe the error. Platform Manager
exits on initialization error. System
Manager will restart platform manager to
recover the situation. If the situation is not
recoverable (i.e. platform manager restarts
multiple times), the line card will be
reloaded by system manager.

Service Platform Manager encountered an

initialization error A reason text will be
svc-pm: error encountered, reason=[chars] supplied to describe the error.

MISMATCH Index [dec] to ifh [hex] to e-adj

index [dec]\n

The error indicates the mismatch between

the egress and ingress interface.

svc-pm: error encountered, reason =

[chars] [dec] [dec]

The error indicates the mismatch between

the egress and ingress interface.

[chars] rc=[hex] [chars]\n

The error occurs due to failure in creating

the interface.

[chars] rc = [dec] status = [dec]\n

The error occurs due to failure in creating

the interface.

Interface Handle:[hex] Error:[chars]

rc=[hex] [chars]\n

The error indicates memory allocation gets

failed. No action is required as the software
should be able to recover from this error.

Error:[chars] buffer:[dec] subif:[dec]\n

The size of received buffer is less than the

required size. This will cause degraded
perforamce in IPC calls.

The Service Platform Manager encountered

Service Platform Manager warning: [chars] an provisioning warning.
[chars] [dec]:ifh [hex]\n

Generic info messages pertaining to

service PM.

[chars] : Bifh=[hex], Mifh=[hex]\n

Generic info messages pertaining to

service PM.

Info:[chars] [chars] = [dec] [chars] = [dec]

[chars] = [dec] [chars] = [dec] [chars] =
The Service Platform Manager encountered
[dec]
an provisioning info.

Info:[chars] [chars] = [chars] [chars] =

[dec]

The Service Platform Manager encountered

an provisioning info.

[chars] =[hex]\n

Generic info messages pertaining to

service PM.

Service Platform Manager info: [chars]

The Service Platform Manager encountered

an provisioning info.

[chars] =[hex]\n

Generic info messages pertaining to

service PM.

ifh=[hex] [chars] (rc=[dec])\n

Generic info messages pertaining to

service PM.

stats_ptr[[dec]]: [hex]\n

Generic info messages pertaining to

service PM.

Info : [chars] Interface:[hex]\n

Generic info messages pertaining to

service PM.

[chars]=[unsigned long long int]\n

Generic info messages pertaining to

service PM.

Info:[chars] = [dec]\n

The Service Platform Manager encountered

an provisioning info.

Info:[chars] [chars]:[dec] [chars]:[dec]

[chars]:[dec]

The Service Platform Manager encountered

an provisioning info.

svc-pmlib-client: error encountered,

reason=[chars], errno=[dec]

svc pmlib client encountered a fatal error

and is not able to recover from the error. A
text reason and error number will be
supplied to describe the error.

svc-pmlib-client: warning: [chars]

svc pmlib client encountered an

provisioning warning.

svc-pmlib-im: error encountered,

reason=[chars], errno=[dec]

svc pmlib IM encountered a fatal error and

is not able to recover from the error. A text
reason and error number will be supplied to
describe the error.

svc-pmlib-im: warning: [chars]

svc pmlib IM encountered an provisioning

warning.

pmlib: error encountered, reason=[chars]

Platform Manager client library

encountered an initialization error A reason
text will be supplied to describe the error.

pmlib: error encountered, reason=[chars],

errno=[dec]

The Platform Manager client library

encountered a fatal error and is not able to
recover from the error. A text reason and
error number will be supplied to describe
the error.

svc-pmlib: error encountered,

reason=[chars], errno=[dec]

svc pmlib encountered a fatal error and is

not able to recover from the error. A text
reason and error number will be supplied to
describe the error.

svc-pmlib: warning: [chars]

svc pmlib encountered an provisioning

warning.

[chars], [dec] error code [chars]\n

A runtime failure occurred in Serdes layer.

Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code. The process can continue functioning
as expected despite the failure.

Failed to [chars], error code [chars]\n

A runtime failure occurred in Serdes layer.

Typically, this is an internal error. The
message string indicates the reason for the
failure. This message also provides an error
code and a string interpretation of the error
code. The failure indicates the Serdes
device configuration failed.

[chars] [chars]\n

This message provides information about

the kind of events happening in the Serdes
software. This is not an error message.
Typically, following events are logged in
this message type. - End of successfull
initialization of the software. - Start and
end of a processing of new object that
needs to programmed to the hardware.

sis: error encountered, reason=[chars],

errno=[dec]

Service Interface Server encountered a

fatal error and is not able to recover from
the error. A text reason and error number
will be supplied to describe the error.

sis: error encountered, reason=[chars]

Service Interface Server encountered an

initialization error A reason text will be
supplied to describe the error.

sis: error encountered, reason=[chars],

errno=[dec]

Service Interface Server encountered a

fatal error and is not able to recover from
the error. A text reason and error number
will be supplied to describe the error.

sis warning: [chars]

Service Interface Server encountered an

provisioning warning.

sis event: [chars]

Service Interface Server related

provisioning info.

HW Watchdog: instance: [dec], tid: [dec]

failed to tick, curr failed tick count: [dec],
tick_owner: [dec]

Some kind of internal fault has occurred.

HW Watchdog: detected an internal error,

<[chars]:[dec]>

Some kind of internal fault has occurred.

HW Watchdog: invalid ticker thread tid:

[dec], not registered

Some kind of internal fault has occurred.

HW Watchdog: registration for sysmgr srp

state change notification failed, rc: [dec],
[chars]

Some kind of internal fault has occurred.

HW Watchdog: invalid ticker thread added,

CPU: [dec], tid: [dec]
Some kind of internal fault has occurred.

HW Watchdog: disabled on this node.

The driver software has detected that the

watchdog is disabled on the node.
Disabling the watchdog is not a
recommended as it can lead to
unrecoverable node halts.

HW Watchdog: [chars], [chars]

Some kind of internal fault has occurred.

[chars]: Failed to set reboot cause into

syspage, error: [chars].

There is a failure in setting reboot cause to

syspage before performing a Kernel Dump.

[chars]: Failed to set reboot cause into

syspage, error: [chars].

The failure on setting reboot cause to

syspage before performing Kernel Dump.

[chars]: Failed to set reboot cause into

syspage, error: [chars].

The failure on setting reboot cause to

syspage before performing Kernel Dump.

[chars]: ErrStr:[chars] [dec],rc: [hex]

Crossbar driver encountered an Error in

operation. Error string updates the reason
for this error.

[chars] - ErrStr[chars]

This message indicates an error condition

in client library api while communicating
with the server process. It may be caused
due to invalid api arguments by client
process or a transient condition while the
server process is initializing the ASIC

[chars] - ErrStr[chars] [dec]

This message indicates an error condition

in client library api while communicating
with the server process. It may be caused
due to invalid api arguments by client
process or a transient condition while the
server process is initializing the ASIC

[chars] -ErrStr[chars] [chars]

This message indicates an error condition

in client library api while communicating
with the server process. It may be caused
due to invalid api arguments by client
process or a transient condition while the
server process is initializing the ASIC

[chars] -ErrStr[chars] [dec] [chars]

This message indicates an error condition

in client library api while communicating
with the server process. It may be caused
due to invalid api arguments by client
process or a transient condition while the
server process is initializing the ASIC

Error: [hex] getting cardtype for nodeid:

[hex]\n

Crossbar driver encountered an Error. The

cardtype of the nodeid is not correct .

[chars] - reason:[chars]

Crossbar driver encountered an Error in

operation.

ErrStr:[chars]\n

Crossbar driver encountered an Error in

operation.

Crossbar driver encountered an error

Initialization Error: [chars] Reason: [chars]. during ASIC init and will re-attempt
Exiting.
initialization.

Crossbar driver encountered a fatal error

and is not able recover from the error. A
Initialization Error: [chars] Reason: [chars]. reason text will be supplied call support
Exiting.
with this text.

Error Allocating <[dec]> bytes of memory

Crossbar driver encountered a fatal

memory allocation error

Continuing execution: [chars]: Caused by

[chars]

This message indicates an error occurred

beyond which execution of the sc_driver
may continue, attempting to effect
recovery or work-around internally,
minimizing loss of information/functionality.

Event Manager create failed for [chars].

Reason: [chars]

Crossbar driver Event Manager create error

Event Manager notify failed for [chars].

Reason: [chars]

Crossbar driver Event Manager notify error

Exit on error: [chars]: Caused by [chars]

An error occurred in crossbar driver which

requires exiting (and, hence, restarting) the
process.

Exit on error: [chars]: Caused by [chars]

An error occurred in crossbar driver which

requires exiting (and, hence, restarting) the
process.

LWM Event Manager event block failed.

Reason: [chars]

Crossbar driver Event Manager event block

error

An error occurred during LWM message

reply. Reason: [chars]

Crossbar driver LWM reply error

debug init [dec] failed [hex]

This is an informational message from the

XCVR stating that failed to initialize a
debug event type structure provided by the
application with the supplied data

debug register failed [hex]

This is an informational message from the

XCVR stating that registering with sysdb
fails.

XCVR-Err: [chars]

This is an error message from the XCVR, it

indicates that something has gone wrong
internally in the XCVR.

XCVR-FAILURE: [chars]

This is a failure message from the XCVR

which indicates default xcvr notification
other than the notifications like removed,
ready, failed, presence_even_ack

Transceiver([chars] :rack:[dec]/slot:
[dec]/bay:[dec]/port:[dec]) ENABLED

Add device to list of devices on spa plugin

which refers to the xcvr which is added is
enabled and ready %s - xcvr type

XCVR-Info: [chars]

This is an informational message from the

XCVR. Evaluate whether transceiver should
be enabled or disabled. Unsupported
transceivers are allowed as long as we
have no other reason to disable them.
Security has failed, the identification and
compatibility information may be incorrect;
ignore them.

Transceiver([chars] :rack:[dec]/slot:
[dec]/bay:[dec]/port:[dec]) REMOVED

This is an informational message which

notifies that XCVR is removed from
particular location %s - xcvr type

XFP Module for port [dec] is not Cisco

compliant

A compliance error was detected during

XFP initialization. A compliance error is due
to unsupported optics, checksum error,
EEPROM CRC error, vendor data error, or
decryption error. The XFP is the pluggable
optics on the line cards. XFP initialization
may happen when linecard boots up, XFP
OIR and line card process restart. The
optics will not be enabled if an XFP
compliance error is detected.

An XFP Module not supported for the port

error was detected during XFP initialization.
An XFP Module not supported for the port
error is reported when Optics is not
supported on the port. The XFP is the
pluggable optics on the line cards. XFP
initialization may happen when linecard
boots up, XFP OIR and line card process
XFP Module for port [dec] is not supported restart.

XFP Module for port [dec] is not a

supported Product ID (PID)

A PID not supported error was detected

during XFP initialization. A PID not support
error is reported when either the PID can
not be read or not supported on the
platform. The XFP is the pluggable optics
on the line cards. XFP initialization may
happen when linecard boots up, XFP OIR
and line card process restart. The optics
will not be enabled if a PID not supported
error is detected.

XFP Module for port [dec] is not a

supported module type

An XFP supported error was detected

during XFP initialization. This error is
reported when the XFP type can not be
determined or it is not supported on the
platform. The XFP is the pluggable optics
on the line cards. XFP initialization may
happen when linecard boots up, XFP OIR
and line card process restart. The optics
will not be enabled if an XFP supported
error is detected.

XFP High Laser Bias Alarm

Environmental monitoring has detected an

XFP laser bias greater than or equal to the
high laser bias alarm threshold. The XFP is
the pluggable optics on the line cards. The
laser bias threshold values are read from
the XFP.

XFP High Rx Power Alarm

Environmental monitoring has detected an

XFP Rx power greater than or equal to the
high Rx power alarm threshold. The XFP is
the pluggable optics on the line cards. The
Rx power threshold values are read from
the XFP.

XFP High Temperature Alarm

Environmental monitoring has detected an

XFP temperature greater than or equal to
the high temperature alarm threshold. The
XFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the XFP.

XFP High Tx Power Alarm

Environmental monitoring has detected an

XFP Tx power greater than or equal to the
high Tx power alarm threshold. The XFP is
the pluggable optics on the line cards. The
Tx power threshold values are read from
the XFP.

XFP Low Laser Bias Alarm

Environmental monitoring has detected an

XFP laser bias less than or equal to the low
laser bias alarm threshold. The XFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the XFP.

XFP Low Rx Power Alarm

Environmental monitoring has detected an

XFP Rx power less than or equal to the low
Rx power alarm threshold. The XFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
XFP.

XFP Low Tx Power Alarm

Environmental monitoring has detected an

XFP Tx power less than or equal to the low
Tx power alarm threshold. The XFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
XFP.

XFP High Laser Bias Warning

Environmental monitoring has detected an

XFP laser bias greater than or equal to the
high laser bias warning threshold. The XFP
is the pluggable optics on the line cards.
The laser bias threshold values are read
from the XFP.

XFP High Rx Power Warning

Environmental monitoring has detected an

XFP Rx power greater than or equal to the
high Rx power warning threshold. The XFP
is the pluggable optics on the line cards.
The Rx power threshold values are read
from the XFP.

XFP High Temperature Warning

Environmental monitoring has detected an

XFP temperature greater than or equal to
the high temperature warning threshold.
The XFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the XFP.

XFP High Tx Power Warning

Environmental monitoring has detected an

XFP Tx power greater than or equal to the
high Tx power warning threshold. The XFP
is the pluggable optics on the line cards.
The Tx power threshold values are read
from the XFP.

XFP Low Laser Bias Warning

Environmental monitoring has detected an

XFP laser bias less than or equal to the low
laser bias warning threshold. The XFP is the
pluggable optics on the line cards. The
laser bias threshold values are read from
the XFP.

XFP Low Rx Power Warning

Environmental monitoring has detected an

XFP Rx power less than or equal to the low
Rx power warning threshold. The XFP is the
pluggable optics on the line cards. The Rx
power threshold values are read from the
XFP.

XFP Low Temperature Alarm

Environmental monitoring has detected an

XFP temperature less than or equal to the
low temperature alarm threshold. The XFP
is the pluggable optics on the line cards.
The temperature threshold values are read
from the XFP.

XFP Low Temperature Warning

Environmental monitoring has detected an

XFP temperature less than or equal to the
low temperature warning threshold. The
XFP is the pluggable optics on the line
cards. The temperature threshold values
are read from the XFP.

XFP Low Tx Power Warning

Environmental monitoring has detected an

XFP Tx power less than or equal to the low
Tx power warning threshold. The XFP is the
pluggable optics on the line cards. The Tx
power threshold values are read from the
XFP.

Nirvana FPGA is booted from backup PROM

- host_status_reg:[hex]
-Rommon is booted from backup spi flash enso status reg=[hex]. Rommon primary
flash needs to be reprogrammed

The system is booted from backup

Rommon spi flash on Kensh-JF board.

Zen-JF FPGA is booted from backup PROM enso status reg=[hex]. ZJF primary PROM The system is booted from backup Zen-JF
needs to be reprogrammed
FPGA prom.

the board debug jumper is set, please

remove this debug jumper in production
system. host_status_reg:[hex]

The debug jumper on Satori RP base board

is set. The system will not conform to
functional specification if the jumper is set.
This is used for debug purpose only. It
should not be set on a production system.

the fmea debug flag is set, please remove

this debug flag in production system.

The FMEA debug flag on Satori RP KJF FPGA

scatchpad is set. The system will not
conform to functional specification if the
jumper is set. This is used for debug
purpose only. It should not be set on a
production system.

[chars]: ftruncate fail [hex], [dec] [dec]\n

An error occurred in ClkCtrl driver due to

ftruncate function call failed

[chars]: mmap fail [dec] [dec]\n

An error occurred in ClkCtrl driver due to

memory map failed

[chars]: shm_open fail [dec]\n

An error occurred in ClkCtrl driver due to

shared memory could not be opened.

Error Allocating <[dec]> bytes of memory

Zarlink driver encountered a fatal memory

allocation error

Initialization Error:[chars] Reason: [chars].

Exiting.

Zarlink driver initialization failed.

Error Allocating <[dec]> bytes of memory

There is no sufficient memory for

allocation.

[chars] Initialization Error. Reason: [chars].

Exiting.
Zarlink client Api initilization failed.

Mutex [chars] failed: '[chars]'

The policy obj library had trouble

locking/unlocking mutex.

'Policy object name' library initialization

failed in [chars]:'[chars]'

The policy manager obj name library could

not be initialized. This may affect the
function of using AAA downloaded policies.

Failed to [chars] debug [chars]:'[chars]'

The policy manager ui library debug(s)

could not be initialized. The is a non-fatal
error and should not affect the normal
functioning of the system. The only effect
of this error will be that the policy manager
ui library debugs may not show up .

Inplace modification for a given transaction

The last inplace policy modification
is ongoing. This could happen if during
operation (internal transaction id: [dec]) is inplace modification producer (policymgr)
still in progress. Please retry the policy
gets restarted and the client is not aware of
modification after some time.
it.

Failed to allocate %zu bytes.

The node which logged this message is

running low on memory and the requested
operation could not be completed.

Failed to [chars] debug [chars]:'[chars]'

The policy manager bag ops library

debug(s) could not be initialized. The is a
non-fatal error and should not affect the
normal functioning of the system. The only
effect of this error will be that the policy
manager ui library debugs may not show
up .

AF-Mon Test EA error occurred at function

[chars]:[unsigned int] - [chars]

The AFMon EA test process encountered

the specified error

Afmon MA caps remove failed: caps:

[unsigned int], ifhandle: [hex], error:
[chars]

The AFMon MA process encountered the

specified error while trying to remove the
caps.

AFMon MA initialization failed in function

[chars]: [chars]

The Afmon MA process encountered the

specified error while initializing the
specified facility. If this error occurs, the
sysmgr process will restart the Afmon MA
process.

The Afmon MA process encountered the

specified error in the 'apply' phase. The
The service policy '[chars]' on '[chars]',
incorrect caps type is present in the AFMON
'[chars]' is in inconsistent state. Please
MA DB. This could be the result of an
remove and reconfigure the service policy. incorrect operation in the'verify' phase.

EFCM-Err: [chars]

This is an error message from the EFCM, it

indicates that something has gone wrong
internally in the EFCM.

EFCM-Info: [chars]

This is an informational message from the

EFCM

EFCM-Debug: [chars]

This is a debuging message from the EFCM

QOSEA: updated bandwidth for ifh [hex]

with [dec] [chars] [chars]

This is an informational message from the

QoS EA Process, it indicates that bandwidth
change happened for an interface.

QoS EA Clear Qos Counter Failed for ifh

[chars] ul_ifh [chars] policy_name [chars]
dir [dec] failed: [chars]

The QoS EA process encountered the

specified error during Clear Qos Counter
execution. With this message clear qos
counter will not clear the hardware counter.
The failure might be becuase of no memory
avaible. Please reexecute the CLI clear qos
counter. If you see the issue please follow
the recommended_action.

service-policy [chars] [chars] on interface

[hex] member [hex] [chars], [chars]

The QoS policy could not be applied on the

bundle interface member specified.

QoS EA initialization [chars] failed: [chars]

The QoS EA process encountered the

specified error

QoS EA initialization [chars] failed: [chars]

The QoS EA process encountered the

specified error.

[chars]

The QoS EA process encountered the

specified error.

QoS EA inplace modification failed for

[chars]

The QoS EA process encountered the

specified error.

The QoS policy on the interface specified

could not be modified successfully in
inconsistency detected due to ANCP or
response to an ANCP or interface speed
Bandwidth modification. Execute show qos change notification. This may happen
inconsistency, to obtain information.
because the QoS policy is now invalid with
[chars]
the new reference bandwidth.
QoS EA test error ocured at function
[chars]: [chars]

The QoS EA test process encountered the

specified error

QoS EA verify policy failed, error [chars]:

[chars]

The QoS EA policy verification encountered

the specified error. This may happen
because the QoS policy is invalid and
cannot be applied successfully.

QoS EA verify policy failed, error [chars]:

[chars]

The QoS EA policy verification encountered

the specified error. This may happen
because the QoS policy is invalid and
cannot be applied successfully.

[chars]: [chars]: [hex]-'[chars]'

The QoS EA process encountered the

specified error

Failed to initialize the QoS EA process:

[chars] Error Code [hex] ([chars])

The QoS EA process failed to initialize. The

System Manager will restart the EA
process.

Failed to initialize the QoS EA process:

[chars] Error Code [hex] ([chars])
[chars]: [chars]

The QoS EA process failed to initialize. The

System Manager will restart the EA
process.
Informational message

An error occurred during debug

initialization. Error: [chars]

The QoS FIFO dll encountered a problem

while initializingg the debug facility. This is
not a fatal error. QoS FIFO will continue to
execute properly, but will not be able to
use the debugging facility.

Qos lib ltraces will not work as the ltrace

initialization failed. The failure may be due
to one of the following reasions. 1. Due to
invalid magic number in existing buffer 2.
Due to invalid length field in existing buffer
ltrace initialization failed for file '[chars]' : 3. Due to failure in allocating memory 4.
[dec]([chars]). QoS lib ltraces will not work Due to unexpected system error
QoS MA caps add failed: caps: [unsigned
int], proto: [unsigned int], ifhandle: [hex],
service_policy: [chars], error: [chars]

The QoS MA process encountered the

specified error while trying to add the caps.

QoS MA caps remove failed: caps:

[unsigned int], proto: [unsigned int],
ifhandle: [hex], error: [chars]

The QoS MA process encountered the

specified error while trying to remove the
caps.

The QoS MA process encountered the

QoS MA DPC (delete) failed: ifhandle: [hex], specified error while trying to send a
caps: [unsigned int], error: [chars]
critical operation to the EA.
The QoS MA process encountered the
QoS MA bandwidth update failed: ifhandle: specified error while trying to update it's
[hex], bandwidth: [unsigned int], error:
database with the new bandwidth update
[chars]
from ANCP or Ifmgr.
Invalid bandwidth entry in QoS-MA
bandwidth table: ifhandle: [hex],
bandwidth: [unsigned int]

The QoS MA process encountered an

invalid entry while receiving updates from
ANCP or Ifmgr.

[chars] Error [hex]:[chars]

A critial operation attempted by QoS MA

has failed. It may affect the proper
functioning of QoS features.

L2 overhead adjustment can not be

applied/modified after QoS policy has been
programmed. Please remove and reapply
the QoS policy on 'subscriber label
0x[unsigned long int]' for the new L2
overhead value to take effect. This
message might not be displayed for other
subscribers hitting the same problem for
the next few seconds

Modification of L2 overhead value will not

take effect for existing subscribers with
QoS policies. For the new value to take
effect, remove and reapply the QoS policy.

Clearing QoS statistics counters. This may

take several minutes to complete for all
interfaces in high scale QoS configs

Clearing QoS statistics. This may require a

few minutes depending on QoS servicepolicy interface scale.

The QoS MA process encountered the

The switch-fabric service policy '[chars]'
specified error upon startup or restart. The
was not accepted correctly by the EA. Error: EA did not process the FABQOS policy
[chars]
correctly.

QoS MA initialisation failed in function

[chars]: [chars]

The QoS MA process encountered the

specified error while initializing the
specified facility. If this error occurs, the
sysmgr process will restart the QoS MA
process.

The QoS MA process encountered the

specified error in the 'apply' phase. The
The service policy '[chars]' on '[chars]',
incorrect caps type is present in the QOS
'[chars]' is in inconsistent state. Please
MA DB. This could be the result of an
remove and reconfigure the service policy. incorrect operation in the'verify' phase.
The dpc error array '[hex]' and caps error
array '[hex]' have invalid codes at the
same index '[dec]'.

An internal error was encountered while

processing QoS configuration.

Netio-TXM: An error occured during ens

consumer init :[chars]

The QOS TXM hit an error condition when

registering with ens. Due to this failure
LOCP feature may not work. This failure
occurs in one of the following conditions: 1.
Failed to get the event manager of the
netio control thread 2. Failed to initialize
ENS subsystem in LR-scope. 3. Failed to
create new nrs class/data handle. 4. Failure
during ens/nrs registration.

The QOS TXM process encountered an error

while initializing the debug facility. This is
not a fatal error. QOS TXM will continue to
A error occurred during debug initialization, execute properly, but will not be able to
err: [chars]
use the debugging facility.
The QOS TXM process encountered an error
in its initialsation sequence. This is a
serious error. QOS TXM functioning
An error occurred in initialization sequence correctly is not guranteed depending upon
for iface: [chars]
the exact problem in initialisation sequence
Memory alloc error [chars] [chars]

The router cannot allocate more memory.

Error encountered while clearing redq entry

for an interface default queue associated
QMgr encountered an error while
with an interface in [chars] PSE. Error:
programming redq entry for an interface
[chars]
default queue in the associated PSE

Server connection failed - [chars]. Error

code - [chars]

Connection to some server failed.

Server connection failed - [chars]. Error

code - [chars]

Connection to IM server failed during QoS

EA process init. This would lead to an
inablility of QoS EA to process CAPS from
QoS MA and to a potential disconnect
between the hardware/software views of
the configured qos policies on the system.

Error occurred while registering for

debugging services

Error occurred while waiting for an event.

Error encountered while creating ICL

interface: [chars] (ifh: [hex]), Error [chars]

QoS EA encountered an error when an ICL

interface was being created. No hardware
programming was done for the ICL
interface. The error may be becasue there
was a QoS Policy already applied on the
interface.

Error encountered during QoS

programming for bundle member [chars]
(ifh: [hex]) of bundle <<CH[hex]>>,
direction: [chars], error: [chars]

A member was added to the bundle or it

was added earlier and link came up now.
This triggers update event and an error is
encountered in QoS EA process while
handling update event for the bundle
member.

Error encountered during caps resync with

IM for interface: [chars] (ifh: [hex]),
QoS EA encountered an error during resync
direction: [chars], error: [chars]
of QoS capsulations with IM.

QoSEA encountered a policy in a failed

state. ifh: [hex], direction: [chars]. Aborting QoS EA encountered a policy in a failed
iMDR during IMDR_SHUTDOWN state
state during an iMDR shutdown state.

Error encountered while trying to ACK to an

MIPC event notification [unsigned int]. Error QoS EA encountered an error while ACKing
[chars]
to an MIPC event

QoS EA encountered an error when

modifying the policy on an interface, upon
which a rollback was attempted on this
interface to restore the old policy. There
was an error encountered during this
Error encountered during rollback of policy rollback too, due to which neither the old
modification on interface: [chars] (ifh:
policy nor the new policy is applied in
[hex]), direction: [chars], error: [chars]
hardware for this interface.

Statsd registration failed(Error: [chars]).

QoS drops will not be reported for any qos
enabled interfaces in the output of show
interface CLI.

Statsd registration failed. QoS drops will

not be reported for any qos enabled
interfaces in the output of show interface
CLI.

QoS_EA failed to initialize stats shared

Shared memory initialization failed(Error:
memory(after retry count = 5). QoS drops
[chars]). QoS drops will not be reported for will not be reported for any qos enabled
any qos enabled interfaces in the output of interfaces in the output of show interface
show interface CLI.
CLI.

Failed to setup event manager

Failed to setup event manager.

Failed to create event manager

Failed to create event manager.

Error encountered during the allocation of QMgr encountered an error during the
queueing resources for interface, ifh: [hex] allocation of queueing resources within a
in [chars] queueing asic. Error: [chars]
queuing asic as part of interface create.
Error encountered during the de-allocation
of queueing resources for interface, ifh:
QMgr encountered an error during the de[hex] in the [chars] queueing asic. Error:
allocation of queueing resources within a
[chars]
queuing asic as part of interface delete.

Error encountered during the reprogramming of queueing resources for

interface, ifh: [hex] in the [chars] queueing
asic. Error: [chars]

QMgr encountered an error during the reprogramming of queueing resources within

a queuing asic as part of interface modify
operation.

Error encountered while programming redq QMgr encountered an error while

entry for interface default queues in [chars] programming redq entry for interface
PSE. Error: [chars]
default queues in the associated PSE

Error encountered during the update of

REDQ entries to hw in [chars] PSE. Error:
[chars]

QMgr encountered an error when flushing

shadow REDQ entries to hardware.

QMgr encountered an error in obtaining the

interface default queue in a queuing asic
for a given interface. This prevented QMgr
from programming REDQ entry for the
Unable to ascertain interface default queue corresponding queue. Even though the
in [chars] queueing asic for interface, ifh: interface is created, it will not be able to
[hex]. Error: [chars]
carry traffic

Encountered errors while updating

interface bandwidth for interface [hex]

QoSEA encountered errors while updating

the interface bandwidth of an interface in
response to a bandwidth notification from
IM.

Error occurred while waiting for an event

Error occurred while waiting for an event.

Unrecoverable error in event loop. Error:

[chars]

An error (other than EINTR) occured in the

event loop. The process has exited and
restarted.

Failed to initialise debug infra within QoS

EA. Error: [chars]

Debug initialization failed within EA.

Debugs may not be printed

Failed to initialise ltrace infra within QoS

EA. Error [chars]

Ltrace initialization failed within EA. Ltraces

may not be printed

Failed to process MIPC notification

QoS EA encountered an error while
[unsigned int] within QoS EA. Error [chars] processing an MIPC event notification

Failed to set packet shape Q to [dec].

Dropping packet. Error: [chars]

Could not set the outgoing queue

associated with this packet. As a
consequence the packet is being dropped.
During normal operation of the system, an
occasional (very in-frequent) packet drop in
the slow-path is tolerable.

QoS_EA failed to allocate space for parent

ifhandle in parent_qos_array. This will
Could not find space in
cause the policymap attaching to parent
parent_qos_index_array for parent ifhandle and sub-interfaces. And conflicting qos
[hex]
actions.

Debug initialization failed within the qfifo

Failed to initialise debug infra within the
node on the NetIO chain. Debugs may not
qfifo node on the netio chain. Error: [chars] be printed.

QoSEA-Err: Member Add/Remove: [chars]

This is an error message from the QoS EA

Process, it indicates that something has
gone wrong in QoS EA while
adding/removing a bundle member. Error
can happen with/without QoS on bundle.

This is an error message from the QoS EA

bandwidth change Process, it indicates that
something has gone wrong internally in the
QoS EA during bandwidth change. %x QOSEAERR: update bandwidth for ifh [hex] Indicates ifh %d - New bandwidth %s with [dec] [chars] [chars] [chars]
Direction %s - errormsg %s - errormsg

[chars]: Insert intf info in db is failed

This is a syslog error message from the

QoS EA Process

QoSEA-Err: [chars]

This is an error message from the QoS EA

Process, it indicates something has gone
wrong internally in QoS EA. %s - Indicates
the reason of failure.

QoSEA-Err: [chars] [chars]

This is an error message from the QoS EA

Process, it indicates that something has
gone wrong internally in QoS EA. %s - Both
strings indicate the reason of failure.

Note : Hier policies do not apply to E3

Bundle tx mcast.

This is a syslog error message from the

QoS EA Process

This is an error message from the QoS EA

bandwidth change process,it indicates that
something has gone wrong internally in the
QOSEAERR: im_attr_get bandwidth [chars] QoS EA during bandwidth attribute get. %s
[hex] Error: [chars]
- Errormsg %x - ifh %s - Errormsg

Inconsistent Configuration state :[chars]

This is a syslog error message from the

QoS EA Process

[chars]:
ipv4_acl_register_check_usage_callback
register is failed

This is a syslog error message from the

QoS EA Process

[chars]:
ipv4_acl_register_res_check_callback
register is failed

This is a syslog error message from the

QoS EA Process

[chars]:
ipv6_acl_register_check_usage_callback
register is failed

This is a syslog error message from the

QoS EA Process

[chars]:
ipv6_acl_register_res_check_callback
register is failed

This is a syslog error message from the

QoS EA Process

Could not create Msg chan: [chars] error:

[chars]

The QoS EA could not create the necessary

message channel due to the given error

An error occurred in the [chars] message

handler

An error occurred during message handling

in the indicated message handler

QoSEA-Err: class:[chars], [chars]

This is an error message from the QoS EA

Process, it indicates that something has
gone wrong internally in QoS EA. %s - Both
errormsg indicates the reason of failure

QoSEA-Rollback-Err: [chars]

This is an error message from the QoS EA

Process, it indicates that rollback failed in
the QoS EA. %s - Errormsg

The QoS EA received an unhandled

message

The QoS EA received a message that it was

unable to handle'

An unknown message was dispatched to

the [chars] message handler: Msg: [hex]

An incoming message was demuxed to the

incorrect message handler

QoSEA-Warn: [chars]

This is a warning message from the QoS EA

Process

QoSEA-Notice: [chars]

This is a notice message from the QoS EA

Process

QoSEA-Policer-Param-Notice: [chars]

This is a notice message from the QoS EA

Process

QOSEA: updated bandwidth for ifh [hex]

with [dec] [chars] [chars]

This is an informational message from the

QoS EA Process, it indicates that bandwidth
change happened for an interface.

[chars][[dec]]: HP Disassociates failed [dec] This is a syslog Info message from the QoS
continuing..
EA Process
QoSEA-Info: [chars]

This is an informational message from the

QoS EA Process

An Asynchronous message was received

The QoS EA received an asynchronous

message.

QoSEA-Info: class:[chars], [chars]

This is an informational message from the

QoS EA Process. It indicates that something
can not be configure in service policy.

[chars][[dec]]: skipping subifs beyond [dec] This is a syslog Info message from the QoS
to [dec]
EA Process
[chars]: skipping Vlans beyond [dec] in
group [dec]

This is a syslog Info message from the QoS

EA Process

QoSEA-Debug: [chars]

This is a debuging message from the QoS

EA Process

Failed to open DLL '[chars]' : '[chars]'

This message is seen when the process

fails to open the DLL
'libqos_ea_ui_supp.dll'. This failure may
occur only on RP. It may fail to open the
DLL due to any one of the following
reasons: 1. list of DLL objects is empty or
the list itself doesn't exits. 2. if no symbol
in executable. 3. if the memory allocation
fails at any stage 4. if the dll is not unique
with respect to the other DLL's loaded and
placed in the list.

Failed to close DLL '[chars]' : '[chars]'

This message is seen when the process

fails to close the DLL
'libqos_ea_ui_supp.dll'. It may fail to close
the DLL due to any one of the following
reasons: 1. Due invalid handle passed to
the function. 2. DLL may have been already
closed.

Invalid combination of datalink: [dec],

encap1: [dec], encap2: [dec] for ALE

While validating the AAA attributes

provided by the template manager,
received incorrect value pair for Access
Loop Encapsulation.

QoSRM-DLL-Err: [chars]

This is an error message from the QoS RM

DLL, it indicates that something has gone
wrong internally in the QoS RM dll.

Could not create Msg chan: [chars] error:

[chars]

The QoS RM dll could not create the

necessary message channel due to the
given error

An error ([chars]) occurred in the [chars]

message handler,Msg:[hex]

An error occurred during message handling

in the indicated message handler

The QoS RM dll received an unhandled

message

The QoS RM dll received a message that it

was unable to handle'

An unknown message was dispatched to

the [chars] message handler: Msg: [hex]

An incoming message was demuxed to the

incorrect message handler

Unknown Q-Type in message: [hex]

The QoS RM dll received a message, but

was unable to determine which resource
the message was intended for because the
Q-Type field was incorrect.

QoSRM-DLL-Warn: [chars]

This is a warning message from the QoS

RM DLL

QoSRM-DLL-Info: [chars]

This is an informational message from the

QoS RM DLL

An Asynchronous message was received

The QoS RM dll received an asynchronous

message.

QoSRM-DLL-Debug: [chars]

This is a debuging message from the QoS

RM DLL

QoSRM-Err: [chars]

This is an error message from the QoS RM

Process, it indicates that something has
gone wrong internally in the QoS RM.

Could not create Msg chan: [chars] error:

[chars]

The QoS RM could not create the necessary

message channel due to the given error

Event: [chars] occurred in the [chars]

message handler, Msg:[hex]

An error occurred during message handling

in the indicated message handler

The QoS RM received an unhandled

message

The QoS RM received a message that it

was unable to handle'

An unknown message was dispatched to

the [chars] message handler: Msg: [hex]

An incoming message was demuxed to the

incorrect message handler

Unknown Q-Type in message: [hex]

The QoS RM received a message, but was

unable to determine which resource the
message was intended for because the QType field was incorrect.

QoSRM-Warn: [chars]

This is a warning message from the QoS

RM Process

QoSRM-Info: [chars]

This is an informational message from the

QoS RM Process

An Asynchronous message was received

The QoS RM received an asynchronous

message.

QoSRM-Debug: [chars]

This is a debuging message from the QoS

RM Process

[chars]: queue cnt is null [hex]

This is a debuging message from the QoS

EA Process

DISPLAY INTERFACE TABLE: [chars]

This is a debuging message from the QoS

EA Process

DISPLAY MGID LIST: [chars]

This is a debuging message from the QoS

EA Process

DISPLAY TEST IFH LIST: [chars]

This is a debuging message from the QoS

EA Process

[chars]: failed to allocate lmgid list

This is a debuging message from the QoS

EA Process

Qprep QoS EA Info: [chars]

This is a debuging message from the QoS

EA Process

Failed to free qos-lmgid list from memory

This is a debuging message from the QoS

EA Process

[chars]: EXITING - Failed to allocate

memory for idb_list

This is a debuging message from the QoS

EA Process

[chars]: failed to alloc mem for test case

[dec]

This is a debuging message from the QoS

EA Process

[chars]: failed to alloc midb mem for test

case [dec]

This is a debuging message from the QoS

EA Process

[chars]: Failed to Initialize debugging for

QPREP Lib

This is a debuging message from the QoS

EA Process

Qprep QoS EA Info: [chars]

This is a debuging message from the QoS

EA Process

Qprep QoS EA Info: [chars]

This is a debuging message from the QoS

EA Process

[chars]: Invalid type message received

[dec]

This is a debuging message from the QoS

EA Process

Need to remove dummy. LMGID doesn't

exist

This is a debuging message from the QoS

EA Process

[chars]: displaying list of lmgids after

freeing

This is a debuging message from the QoS

EA Process

[chars]: displaying list of lmgids returned

by function

This is a debuging message from the QoS

EA Process

LIST FUNCTION UNDER TEST: [chars]

This is a debuging message from the QoS

EA Process

MCAST QUEUE INFO: [chars]

This is a debuging message from the QoS

EA Process

MIDB LIST: [chars]

This is a debuging message from the QoS

EA Process

Qprep QoS EA Info: [chars]

This is a debuging message from the QoS

EA Process

[chars]: EXITING - This is not an E3 card

This is a debuging message from the QoS

EA Process

POLICY EVENT INFO: [chars]

This is a debuging message from the QoS

EA Process

SHOW IFQ LIST: [chars]

This is a debuging message from the QoS

EA Process

SHOW MCAST IF TABLE: [chars]

This is a debuging message from the QoS

EA Process

Shared memory window critical error:

[chars]

The SSE QoS EA module encountered a

critical shared memory error. The message
will provide further details on the error.

Policy: [chars] level [unsigned int] Class

[chars] : [chars]

The minimum bandwidth or shape rate

configured is out of the supported
bandwidth range at this level. The message
will provide further details on the error.

Policy: [chars] level [unsigned int] (parent

class name: [chars]): [chars]

The bandwidth ratio is invalid at this level.

The message will provide further details on
the error.

Policy: [chars] level [unsigned int] (parent

class name: [chars]): [chars]

The bandwidth remaining ratio is invalid at

this level. The message will provide further
details on the error.

Internal database corruption error: [chars]

The SSE QoS EA module encountered a

database corruption error. The message
will provide further details on the error.

After a modify rollback failure, QoS EA will

attempt to reset its database, but this reset
attempt failed. The database for the said
Failed to reset the database after a modify interface might be in an unknown state.
rollback failure on interface: [chars] (ifh:
Neither the old policy nor the new policy is
[hex]), direction: [chars], error: [chars]
applied in hardware for this interface.

Error encountered during policy

modification on interface: [chars] (ifh:
[hex]), direction: [chars], error: [chars]

QoS EA encountered an error when

modifying the policy on an interface.
Neither the old policy nor the new policy is
applied in hardware for this interface.

Error encountered during capsulation

resynchronization with Interface Manager
for interface: [chars] (ifh: [hex]), direction: QoS EA encountered an error during resync
[chars], error: [chars]
of QoS capsulations with IM.

The SSE QoS EA module failed to initialize.

Failed to initialize the SSE QoS EA module: The System Manager will restart the EA
[chars] Error Code [hex] ([chars])
process.

QoS EA encountered an error when

modifying the policy on an interface, upon
which a rollback was attempted on this
interface to restore the old policy. There
was an error encountered during this
Error encountered during rollback of policy rollback too, due to which neither the old
modification on interface: [chars] (ifh:
policy nor the new policy is applied in
[hex]), direction: [chars], error: [chars]
hardware for this interface.

Shared memory window error: [chars]

The SSE QoS EA module encountered a

shared memory error. The message will
provide further details on the error.

Failed to initialize debug utility within QoS

EA. Error [chars]

Debug initialization failed within EA.

Debugs may not be printed

Failed to initialize ltrace within QoS EA.

Error [chars]

Ltrace initialization failed within EA. Ltraces

may not be printed

The maximum number of clone profiles

([unsigned int]) allowed by the system has
been exceeded. Current value ([unsigned
int])

'There is a maximum number of clone

profile list entries that the ' 'system
supports, and this number has been
exceeded'

Consumer processes make use of

adjacencies in the AIB database, and lock
the adjacency while they do so. The
Unexpected unlock by adjacency consumer identified consumer made an invalid
(Job ID [unsigned int]) on adjacency
attempt to unlock an adjacency. There may
[pointer] (interface [hex], protocol
be no immediate impact on traffic, but this
[unsigned int])
issue should be addressed.

AIB unexpected event handling condition:

[chars] (errno=[unsigned int])

AIB internally manages its activity using

'events'. An error occurred while processing
events. This will not normally affect
existing traffic but may affect the ability to
process forwarding updates.

AIB has reached zero refcount for

clientdata ([pointer])

AIB has reached zero refcount for

clientdata. This indicates the accounting is
incorrect.

AIB maintains a database for interfacetype-specific DLL information but was

unable to initialize it. The process will
attempt to recovery by restarting. This will
not normally affect existing traffic but may
AIB failed to initialize the dllinfo database: affect the ability to process forwarding
[chars]
updates.

AIB has reached zero refcount for dllinfo

([pointer])

AIB has reached zero refcount for dllinfo.

This indicates the accounting is incorrect.
There may be no immediate impact on
traffic, but this issue should be addressed.

AIB cannot create the IDB for interface

[hex]

AIB maintains a database for interfaces,

but was unable to add an entry to it. This
will not normally affect existing traffic but
may affect the ability to process forwarding
updates.

AIB cannot register with the platform DLL:

[chars] (errno=[unsigned int])

AIB uses the platform specific adjacency

DLL when creating adjacencies. An error
occurred while trying to load the DLL, and
the adjacency database will not be created.
The process will attempt to recovery by
restarting. This will not normally affect
existing traffic but may affect the ability to
process forwarding updates.

Version mismatch between AIB and the

platform DLL (actual version is [unsigned
int], expected [unsigned int])

AIB uses the platform specific adjacency

DLL when creating adjacencies. The DLL
found has an unusable version number,
and AIB cannot continue to process any
adjacency information. The process will
attempt to recovery by restarting. This will
not normally affect existing traffic but may
affect the ability to process forwarding
updates.

Interface EAs may store private information

as 'client data' on interfaces in AIB. An
interface EA made an invalid attempt to
AIB cannot change client data length:
change the size of this data. There may be
interface [hex], old len [unsigned int], new no immediate impact on traffic, but this
len [unsigned int]
issue should be addressed.

AIB failed to open trace file: [chars]

AIB process was unable to open the trace

buffer use to record its activity for
diagnostic purposes. The 'show trace
adjacency' command may not work. The
process will attempt to recovery by
restarting. This will not normally affect
existing traffic but may affect the ability to
process forwarding updates.

AIB failed to initialize the interface

database: [chars]

AIB maintains a database for interfaces,

but was unable to initialize it. The process
will attempt to recovery by restarting. This
will not normally affect existing traffic but
may affect the ability to process forwarding
updates.

AIB shared memory error: [chars] [chars]

AIB uses shared memory to store

adjacencies, but encountered an error
when trying to initialize it. The process will
attempt to recovery by restarting. This will
not normally affect existing traffic but may
affect the ability to process forwarding
updates.

There was an AIB initialization error. The

process will attempt to recovery by
restarting. There will be no effect on traffic
unless shared memory is unusable, and
AIB [chars]: [chars] (errno=[unsigned int]) needs to be reset.

Failed to allocate memory for [chars].

[chars]

Internal error.

[chars]. Error: [chars]

Internal error.

[chars]%s : [chars]

Internal error.

[chars]Sysdb backend scan failed for

[chars] : [chars]

Internal error.

ERROR : [chars] - [chars]

Internal error.

Sysdb Registration error : [chars] for

[chars] [[chars]]

Internal error.

Event connection manager error : [chars],

[chars]

Failed to open connection to Connection

Manager.

Error : [chars] failed - [chars]

General Error.

A call to [chars] returned [chars]

A problem occurred when a call to IM was

made.

Initialization failed : [chars]

autorp_candidate_rp failed to initialize

successfully.

A call to [chars] returned [chars]

A problem occurred when a call to one of

the IPARM APIs was made.

Timer Error : [chars]

Timer Error.

Debug error : [chars]

This error indicates an error in the debug

initialization.

Event connection manager error: [chars],

[chars]

Failed to open connection to Connection

Manager.

A call to event_manager_create() failed

A problem occurred while calling the

event_manager_create() API during the
initialization of the mapping-agent.

The function [chars] returned error : [chars] Failed some IM related operation.

Initialization failed : [chars]

The autorp mapping agent failed to

initialize successfully.

'[chars]' initialization failed : [chars]

autorp_mapping_agent failed to initialize

successfully.

A call to [chars] returned [chars]

A problem occurred when a call to one of

the IPARM APIs was made.

The [chars]maximum number ([unsigned

int]) of cache entries has been reached.
Auto-RP cache creation is now throttled.
Configure a higher '[chars]' value or take
steps to reduce the number of Auto-RP
mapping agent cache entries.

This router has reached the maximum

value for the number of Auto-RP mapping
agent cache entries. Each Auto-RP
candidate-RP sends the mapping agent a
set of group-to-RP mapping ranges and PIM
mode for which it desires to have RP
candidacy. These mappings are cached by
the Auto-RP mapping agent and distributed
through the domain to all PIM routers.
Reaching the limit on the number of cache
entries can cause multicast traffic loss for
some or all multicast groups. Steps should
be immediately taken to reduce the
number of cache entries or to configure a
higher maximum value.

Socket Error : [chars] : [chars]

A socket error occurred in the map agent

packet handling.

Timer Error : [chars]

This error indicates that a timer

initialization failed.

The [chars]number ([unsigned int]) of

cache entries is now below the maximum
([unsigned int]). Normal cache entry
creation will now resume.

This router has fallen below the maximum

value for the number of cache entries
allowed.

The [chars]threshold number ([unsigned

int]) of cache entries has been reached.
Auto-RP cache creation will soon be
throttled. Configure a higher '[chars]' value
or take steps to reduce the number of
Auto-RP mapping agent cache entries.

This router has reached the threshold value

for the number of Auto-RP mapping agent
cache entries. This is a warning that the
maximum value is being approached and
steps should be immediately taken to
reduce the number of cache entries or to
configure a higher maximum value.

Failed to allocate memory for [chars]

The requested operation could not be

accomplished because of a low memory
condition. BGP may not operate correctly
until the process is restarted.

Failed to store [chars] ID [hex] for VRF

[chars].

A ID has been received from RSI that

duplicates an existing VRF or table ID. As a
result, the new ID has been ignored, and
subsequent operation for that VRF will be
incorrect.

Initialization failed ([chars]%s)

An error occurred while initializing the BGP

VRF module. The BPM process will be
restarted.

Failed to add import RT [chars] to vrf

[chars]. System may now be in an
inconsistent state.

The import RT is failed to be added to the

vrf due to the maximum allowed number of
import RTs for each vrf.

Failed to apply configuration change for:

[chars] ([chars]).

A notification of a configuration change

could not be applied, leaving the internal
data structures inconsistent with the
configuration.

Failed to apply RD configuration change for The RD value for the VRF failed to be set,
[chars]. System may now be in an
leaving the internal data structures
inconsistent state.
inconsistent with the configuration.

Failed to publish RD configuration: [chars].

System may now be in an inconsistent
The RD value for a VRF or set of VRFs failed
state.
to be published.

Failed to add net [chars] to the BGP table

An error occurred whilst trying to insert a

net to the BGP table database.

Error in event loop for [chars] thread:

[chars]

'An error occurred in the event loop. In

most of the cases'' 'it will recover.'
*RECUR*

Failed to allocate memory for [chars]

The requested operation could not be

accomplished because of a low memory
condition. BGP may not operate correctly
until the process is restarted.

Deadlock detected (thread [unsigned int]): BGP detected a lock being held when all
holding: [chars]
locks should have been released.

Fatal error: A call to [chars] failed

unexpectedly: [chars]

A function call failed unexpectedly - this is

probably a system problem

Failed to read Address Family data file:

[chars] [chars]

'File/Directory open operation failed, or the

data in the file was corrupt'

Failed to read Address Family data file

[chars]: [chars] on line [unsigned int]

'The data in the Address Family data file

was corrupt'

Due to [chars], with error [chars], rc

[unsigned int]

This message indicates that the BGP async

ipc operation has error condition with the
specified reason. BGP being an application
of the AIPC services, it relies on the
infrastructure to deliver it's ipc messsages,
BGP will have recovery mechanism such as
close the channel, or try to resend the
message if it failed. Sometimes, this error
can be 'normal' due to process restart, FO,
or too much IPC messages cause IPC
queues to be congested.

Failed to [chars] RIB due to an invalid

attribute key number ([hex])

There is a problem with the attribute key

generation routine.

Bad reference count value ([unsigned int]) 'This indicates a internal data structure
for [chars] ([pointer] index [dec])
inconsistency'
Autonomous system number is not set yet
in system database so can not apply other This warning will show up for possible out
configuration.
of order system database notification.

Initialization failed ([chars]%s)

An error occurred while initializing the BGP

process manager. If this occurred during
process startup or RP Switchover, then the
process may be restarted.

Failed to start [chars] process [chars]:

[chars]

The BPM failed to start the process in the

error message. As a result, the process will
not be running.

Failed to stop [chars] process [chars]:

[chars]

An error occurred when trying to stop the

process specified in the error message. As
a result, the process may still be running,
which could adversely affect the operation
of other processes.

Failed to switch to [chars] mode: [chars]

([chars])

An error occurred when switching between

standalone and distributed mode.

Initialization failed ([chars]%s)

An error occurred while initializing the BGP

RIB. If this occured during process startup
or RP Switchover, then the process may be
restarted.

Whilst trying to format a string, the buffer

A string buffer was too short during a string passed in was too short and the string was
print operation (string \[chars]\ truncated) truncated.

[chars] [unsigned int] [unsigned int]

Standby BGP received invalid Route

Distinguisher information from Active BGP.
*SUPPORT*

Notify delete of [chars] failed with warning: A speaker or the bRIB failed to process the
[chars], no further action necessary.
removal of some configuration.

Apply for fast-external-fallover failed:

[chars]

A speaker failed to process a configuration

change for 'fast-external-fallover'

Notify for [chars] failed with error: [chars],

system may now be in an inconsistent
state.

A speaker or the bRIB failed to process a

configuration change.

An error occurred whilst applying the

Failed to apply debug configuration: [chars] debug configuration

Attempted to delete path from empty net

[chars]

An attempt was made to delete a path

from a net with a path count of 0

Failed to [chars] [chars] DLL: [chars]

An error occurred whilst trying to open or

initialize a DLL. The process will be
restarted if this error occurs during process
startup.

EDM server initialization failed: [chars]:

[chars]

Initialization of the EDM server failed. The

process will be restarted.

ALM/LSD API: [chars] - [chars] failed

An ALM/LSD API returned an error.

Unable to allocate label: [chars] - net

[chars] tableid [hex] request type [dec]
fpi_err:[hex]

The ALM/LSD API was unable to allocate a

requested label.

Failed to do [chars] event file attach [chars]

An error occurred when bgp try to do event

file attach.

[chars]

A non-fatal fault occurred.

Error encountered during [chars] of path

element of network [chars] for \[chars]\
address-family. Error code is [dec] (\
[chars]\).

There was an error associated with path

element operation, most likely due to low
memory conditions. BGP may not operate
correctly until the process is restarted.

Failed to create extended community:

[chars]

The import table list associated with an

extended community set could not be
created. This can occur if there is
insufficient memory to allocate the import
table list, or the number of importing tables
exceeds the hard coded limit on the
number of tables that a route may be
imported into.

While attaching extended communities to

the path attribute we reached the
maximum extended community limit and
Failed to add one or more [chars] extended as a result we failed to add one or more
community for table [chars] prefix [chars] extended community to the path attribute.

Failed to initialize [chars] database for

table [chars]. Error: [chars]

There was an error while initializing the

local label database of the BGP process at
the time of process startup. This can cause
the per-CE label for some nets to change at
the time of a BGP process restart or after a
failover without NSR.

Failed to [chars] for Gateway Context (VRF A software error has occurred whilst trying
[chars], Gateway address-family [chars])
to initialize the gateway context database.

Initialization failed ([chars]%s)

High Availabality initialization failed. If this

occured during process startup or RP
Switchover, then the process may be
restarted.

Failed to register for DMZ link bandwidth

change for neighbor [chars]: [chars]

BGP failed to register with interface

manager for DMZ link bandwidth change
notifiction for a given neighbor

Initialization failed ([chars]%s)

An error occurred while initializing the

import thread. If this occurred during
process startup, then the process may be
restarted.

An error occurred when retrieving a

Failed to obtain [chars] during initialization: required value during initialization. As a
[chars]
result the BGP process can not initialize.

[chars]

The number of prefixes synced by active

doesn't match the expected count.

Failed to allocate memory for [chars]

The requested operation could not be

accomplished because of a low memory
condition.

Internal error ([chars])

A non-fatal fault occurred.

Initialization failed ([chars]%s)

An invalid Redundancy Role was delivered

to BGP. If this occured during process
startup or RP Switchover, then the process
may be restarted.

An error occurred while initializing the IO

thread in the speaker process. The process
Initialization failed: [chars] [chars] ([chars]) will be restarted.

[chars] - for session, retry

A problem occurred in TCP init sync.

Initialization of BGP/LABEL failed ([chars]:

[chars])

An error occurred whilst initialising the

LABEL thread. This could be caused by
failure to allocate resources or by errors
when calling the MPLS label manager.

Attempt to recursively lock net [pointer]

(lock: [hex])

A software error has occurred whilst trying

to lock a network entry in the BGP Table
database.

This message indicates that the UPDATE

message contains one or more malformed
attributes. Depending on the nature and
severity of the error and error-handling
Malformed UPDATE message received from configuration, one of the following actions
neighbor [chars] (VRF: [chars]) - message has been taken: discard the attribute, or
length [unsigned int] bytes, error flags
treat the UPDATE as withdraw, or reset the
[hex], action taken \[chars]\. Error details: \ session, or ignore the entire update
[chars]\. NLRIs: [[chars]][chars]%s
message.

No. of importing VRFs exceeds max

([unsigned int]), limited to [unsigned int]
tables: (Err: [chars])

There is a hard coded limit on the number

of tables that a route may be imported
into. This limit has been exceeded, so the
route may not be present in some of the
importing tables. The limit is such that this
message should not be seen under normal
operation.

The value of [chars] ([unsigned int])

exceeds the maximum value: [unsigned
int]

The value of an internally computed

variable has exceeded the maximum value.

BGP MIB init failed ([chars])

An error occurred while initializing the BGP

MIB.

NSR disabled on neighbor [chars] due to

[chars]

NSR has been temporarily disabled on the

neighbor due to transport issues.

Negative path counter for peer [chars]

The counter value for accepted prefixes is

wrong and less than zero

Attempt to recursively lock nexthop

[pointer] (lock: [hex], vrf: [chars], afi:
[chars])

A software error has occurred whilst trying

to lock a nexthop entry in the BGP nexthop
Table database.

Failed to unlock nexthop node [pointer] (nh

'[chars]', lock [hex], vrf '[chars]', afi
A software error has occurred whilst trying
'[chars]', cnt [unsigned int], ln [unsigned
to unlock an entry in the BGP nexthop
int])
Table database.

Failed to allocate memory for [chars],

resetting neighbor

The requested operation could not be

accomplished because of a low memory
condition. One or more neighbor sessions
have been reset to free some memory.

Failed to allocate [unsigned int] bytes from A request was made to allocate a message
the memory pool for message of type
size for which there was not enough
[unsigned int]
memory.

An error occurred to send msg to the NPL

NPL send error [chars] - BGP will reinitialize queue - this triggers NSR
NSR
resynchronization.

NPL timeout - BGP will reinitialize NSR

A message is dropped in the NPL queue this triggers NSR resynchronization.

Failed to build [chars]: [chars] ([chars])

Internal error in the routing policy library.

There was an internal error in the routing

Failed to build ORA[chars]: [chars] ([chars]) policy library.

Could not apply policy operation [chars] to

attribute [chars] because [chars]
Internal error in the routing policy library.

[chars] counter overflow

A counter with maximum value was

incremented.

Failed to [chars] for route distinguisher

[chars], address-family [chars]

A software error has occurred whilst trying

to initialize a route distinguisher node
inside BGP Table database.

Attempt to recursively lock route

distinguisher information [pointer] (lock:
[hex])

A software error has occurred whilst trying

to lock a network entry in the BGP Table
database.

Failed to unlock RD node [pointer] (lock:

[hex])

A software error has occurred whilst trying

to unlock an entry in the BGP RD Table
database.

Failed to register with the RIB for

redistribution of [chars] [chars] [chars]
routes: [chars]

A RIB client library call for redistribution of

routes failed.

Failed to open connection to the RIB for

address family [unsigned int]: [chars]

BGP's connection to the RIB could not be

established and a retry timer could not be
started. This is transient message and BGP
should recover without user intervention.

Failed to [chars] for [chars] while calling

the RIB instance [unsigned int]: [chars]

A RIB library call failed unexpectedly.

Initialization failed ([chars]%s)

An error occurred while initializing the BGP

RIB thread. The process will be restarted if
this error occurs during process startup.

Initialization to RIB failed for [chars]:

[chars]

An error occurred whilst initialising the RIB

for a new address family. This could be
caused by failure to allocate resources or
by errors when calling the Table Resource
Manager or the RIB.

RIB route retry failure: [chars] for [chars]

Some routes were not successfully installed

in the RIB. Consequently, an attempt was
made to save these routes to retry later.
However, an error was encountered during
the save attempt.

An error was encountered during some

operation for the specified address family
and RIB table. This could be due either to a
Failed to [chars] for [chars], RIB table [hex] lack of resources or a software problem.

RPC set [chars] operation: Table [chars].

Error: [chars]

A non-critical error has been encountered

while allocating a per-CE label or while
accessing the label database of the BGP
process. An error while accessing the label
database can cause the per-CE label for
some nets to change at the time of a BGP
process restart or after a failover without
NSR.

An error occurred while initializing the

Scanner library initialization failed ([chars] scanner library. The process will be
%s)
restarted.

Initialization failed ([chars]%s)

An error occurred while initializing the BGP

speaker process. If this occurred during
process startup or RP Switchover, then the
process may be restarted.

Failed to create table context for the VRF

[chars] AFI/SAFI [dec]/[dec]: [chars]

An error occurred when creating the table

context for the shown VRF name, AFI, SAFI.
As a result table can't be activated.

Unable to propagate table attribute

versions for [chars] : [chars]

An internal error was encountered.

failed for neighbor [chars], [chars]

There was an error in IOS-XR managed

timer library API. *SUPPORT*

[chars] counter underflow

A counter with zero value was

decremented.

BGP received a low memory notification

BGP received a notification about an
from wdsysmon for an unknown memory
unknown system memory state ([unsigned state, ie not NORMAL, MINOR, SEVERE or
int])
CRITICAL. As a result, no action was taken.

Failed to unlock net [pointer] (lock: [hex])

A software error has occurred whilst trying

to unlock a network entry in the BGP Table
database.

The update message used when

advertising prefix [chars] in table \[chars]\ /
update-group [chars] / sub-group [chars] is
too small to format attributes. Message
details: datagram size [unsigned int], total
length [unsigned int], attributes length
[unsigned int] (calculated [unsigned int])

An allocated message did not have enough

space required to format all the attributes
of a prefix. When such an error
encountered, a Withdraw message is
generated for the prefix under
consideration.

Failed to create VRF context for the VRF

[chars] : [chars]

An error occurred when creating the vrf

context for the shown VRF name. As a
result VRF can't be enabled.

VRF [chars] still has undeleted table

AFI/SAFI [dec]/[dec]. Table will be deleted.

An error occurred while deleting the VRF.

An address-family table under the VRF is
still not deleted. Ideally all the tables under
the VRF should be deleted first before VRF
is deleted.

[chars] length received from neighbor

[chars] (VRF: [chars]) is [unsigned int]
bytes which is above the [unsigned int]
byte limit; the associated NLRIs will be
withdrawn.

This message indicates that the UPDATE

message contains AS_PATH or AS4_PATH
attribute that is too long. Such long
ASPATHs could be the result of an error on
the neighbor and are not found in normal
updates. The received UPDATE message is
subject to 'treat-as-withdraw' behavior i.e.
the associated NLRIs are withdrawn.

The attribute key generation routine has

BGP detected an inconsistency in attribute gone beyond the checkpointed value. This
key generation. Will correct the problem by is a rare condition to occur as the key
renumbering all attributes
generation algorithm is very simple.

Attempt to register BFD session on invalid

neighbor: [chars]

Internal error indicating that an attempt

has been made to create a BFD session for
a neighbor type that is not supported by
BFD.

BGP and sysdb are out of sync (neighbor

BGP and sysdb are out of sync (neighbor
config present but no neighbor in bgp) and
configuration was present but no neighbors as a result, unconfiguring neighbor results
in BGP)
in negative neighbor count in BGP

Capability 4-byte-as suppress

misconfigured for neighbor [chars]

Possible misconfiguration with 'capability 4byte-as suppress'. This configuration can

be inherited from either a neighbor-group
or a session-group by a neighbor whose
remote-as is a 4-byte as number. Suppress
should be off for such neighbor.

This message indicates that more than one

instances of IGP protocols are using the
More than one instances of [chars] are
same BGP-LS identifier. This may result in
configured with the same BGP-LS identifier. incorrect behavior.

'BGP has resized its bit fields, so the old bit

field chunks should be ' 'destroyable.
Nonetheless, BGP is unable to destroy the
Chunk pool \[chars]\ is no longer in use but old chunk and, ' 'hence, cannot release
cannot be destroyed
unwanted memory.'
Encoding [chars] has overrun the msg
buffer (writen size [unsigned int], max size Encoding the net has overrun the msg
[unsigned int])
buffer. It may corrupt some memory.
Ignored Received malformed entry
message in [chars]

The ORF entry is encoded wrongly

out-of-order feedback from RIB for table

[chars], table-id [hex], version [unsigned
int], prev [unsigned int]

This message indicates that BGP has

received an out-of-order feedback from RIB.
The system will recover by itself.

outside range feedback from RIB for table

[chars], table-id [hex], version [unsigned
int], table version [unsigned int]

This message indicates that BGP has

received a feedback from RIB that is larger
than the table version. The system will
recover by itself.

The internal state representing the

configuration was invalid, but has now
Detected inconsistent config state: [chars] been fixed.
This message indicates that the AS_PATH
and AS4_PATH attributes in the UPDATE
received an UPDATE from [chars] with
consist of segments that are inconsistent
Inconsistent AS_PATH and AS4_PATH, action when doing a merge, discard the AS4_PATH
[chars]
in this case

[chars]

There was problem during init sync

Trying to Readd L2VPN [chars] when

previous instance is still in Deletion

BGP detected that an attempt was made to

instantiate an L2VRF when the instance is
in the process of being deleted. This will
happen when the router-id is unconfigured,
configured with another value and
reconfigured with the first value all in very
quick succession.

RD 0x [pointer] is marked both local and

remote

BGP detected that the RD is marked both

local and remote This means that the local
table_ctx points to this rdinfo but this rdinfo
points to the shared tabel_ctx

Trying to Readd L2VPN [chars] when

previous instance is still there

BGP detected that an attempt was made to

instantiate an L2VRF when the instance still
exists. This will happen when the L2VPN
module can issue two successive adds
followed by delete wheres they meant to
send add, delete and then add.

Same RD Net [chars] or [chars] does not

match VRF Signalling Type

BGP detected that the prefix was learnt

with a signalling type different from what is
configured for the vrf. We do not allow both
types of signalling for nets with the same
RD

Net [chars] or [chars] is learnt via both

types of Signalling

BGP detected that the same prefixwas

learnt with a signalling type different from
what was learnt initially. We do not allow
both types of signalling for nets with the
same RD

Ignored import operation for Net received

for L2 table [chars]

The import operations will not be done for

nets whose signalling type does not match
that for the importing VRF. The import
operation has been ignored.

This message indicates that there is a

Label [unsigned int] collision: prev: [chars] collision in the assignment of a label in
curr: [chars]
BGP.
Label [unsigned int] inconsistency: type:
[chars] flags: [unsigned int]

This message indicates that there is an

inconsistency in the BGP label database.

Locking order violation (thread [unsigned

int]): [chars] gained while holding: [chars]

BGP detected a violation of lock ordering

requirements

Lock released without being held (thread

[unsigned int]): [chars] gained [unsigned
int], released [unsigned int]

BGP detected a lock being released when it

was not held.

This message indicates that the UPDATE

message contains an NLRI with a length
that is too long. Such long NLRI could be
NLRI length received is [unsigned int] bytes the result of an error on the neighbor and
which is above the [unsigned int] byte
are not found in normal updates. The
limit; the NLRI will be withdrawn.
associated NLRI is considered withdrawn.

No. of [chars] prefixes received from

[chars]: [unsigned int] exceed limit
[unsigned int]

Number of prefixes received from a

neighbor for a given address family has
exceeded the limit configured with the
'max-prefix' command.

Detected missing neighbor AF sub-grp.

Correcting: [chars]

BGP detected that a Neighbor AF did not

correctly belong to an update sub-group.
BGP attempted to correct this error.

Nbr [chars] (state: [unsigned int]) is on

Active scoped ilist already

An attempt to add nbr to active scoped ilist

while it is on the ilist already

A path with unrecognized flags has been

synchronized to standby RP during NSR
synchronization for a net. This may result
Path with unrecongnized flags synchronized in inconsistent state between active and
for network [chars] path id [unsigned int] standby BGP which may impact operation
version [unsigned int] flags [hex]
after RP switchover.
An attempt was made to allocate an
There was and attempt to generate an
oversized message during update
oversized update message when
generation. This is usually due to the
advertising prefix [chars] in table \[chars]\ / presence of large sized attributes for one
update-group [chars] / sub-group [chars]. or more prefixes. When such an error
Message details: total size [unsigned int], encountered, a Withdraw message is
attributes size [unsigned int], NLRI size
generated for the prefix under
[unsigned int]
consideration.

Reached the maximum limit ([unsigned

int]) of path elements of network [chars]
for \[chars]\ address-family

An attempt was made to create a path

element beyond the maximum limit. The
advertisement and installation of the
network in the BGP table may be
inconsistent with additional-paths
configuration.

Community overflow from policy

application

Policy tried to add more communities than

a BGP route can hold.

A policy attached to an eBGP neighbor

[chars] operations in [chars] [chars] policy \ performs operations that are illegal for
[chars]\ will be ignored for external
eBGP routes, such as modifying the localneighbor/update-group [chars]
preference.
A policy attached to an iBGP neighbor
[chars] operations in [chars] [chars] policy \ performs operations that are illegal for
[chars]\ will be ignored for internal
iBGP routes, such as modifying the AS-path
neighbor/update-group [chars]
or MED.

The policy '[chars]' attempted to set a

next-hop on [chars] with an unsuitable
address type. The next-hop will not be
modified.

The specified route-policy (or a policy

applied by that policy) is configured perhaps on a neighbor or for redistribution
- and it is attempting to set the next-hop of
the specified route to an address that
doesn't match the address-family of the
route. For example, it might be setting an
IPv6 next-hop on an IPv4 route. Since this
does not make any sense, the attempt will
be ignored, and the next-hop will not be
changed. (Note that this message is ratelimited, so it will not appear for every
single route that is affected). Use the
command 'show rpl policy <name>
attachpoints' to determine where this
policy is in use. Use the command 'show rpl
policy <name> uses policies' to determine
which other policies this policy applies
(since the relevant 'set next-hop' may be in
one of these policies).

Potential for deadlock detected: Locks:

[chars]

BGP detected the potential for a deadlock

to occur. The process will be restarted.

This trcaeback indicates that BGP lost

connection to RIB and an one attempt to
reconnect to RIB failed. This is expected in
the following situations 1) Before FO, the
standby BGP connects to the active RIB.
after FO, the new active BGP has to
connect to the new active RIB although it is
not restarted. 2) After FO, the new active
RIB is restarted due to process placement
especially in muli-chassis scenario. 3) RIB
restarted either due to an unplanned exit
or due to user initiated restart Since BGP
doesn't restart, it tries to connect to RIB
right away and there is the possibility that
the LWM channels may not have been
published by RIB yet or RIB is unable to
accept the connection due to heavy CPU
churn (especially after FO). In all such
cases, BGP will continue to try the
connection to RIB. One can verify whether
the connection has gone through or not
checking the RIB clients. The ultimate
verification would be to make sure that the
RIB tables are in sync with the BGP tables
and there is no traffic drop. There is always
a very small possibility that this is due to a
problem in the connection logic. So if the
RIB tables are not in sync with the BGP
tables, the traceback decode helps in
Failed to register BGP protocol with RIB for figuring out the code-path and possible
[chars]: [chars] (error code: [hex])
source of any problem.

Ignored import policy set operation for

same RD import on [chars] path received
from [chars]

The import policy must not perform set

operations on paths, received from a PE
neighbor, whose RD is the same as the RD
for the importing VRF. The set operation
has been ignored.

slow feedback from RIB for AFI [unsigned

int], fwdtable_version [unsigned int],
acked_fwdtable_version [unsigned int],
slow ack count [unsigned int]

This message indicates that BGP has

detected a condition of slow feedback from
RIB. The system will recover by itself.

BGP AS number has changed from [chars]

to [chars] - bgp (speaker) process will be
restarted.

The bpm process was terminated

improperly and the speaker process did not
receive the notification to terminate. A new
bpm process has started with a different AS
number due to a new bgp configuration
while the speaker process is still running
with the previous AS number.

BGP detected that a table_ctx is being

Deleting table_ctx: [chars] in ACTIVE state deleted even though it is in active state

Unknown ACL action: [unsigned int]

BGP received an unknown action

(permit/deny/etc) from the ACL library

There was a failure to allocate a message

buffer during update generation for Table \
[chars]\ / update-group [chars] / sub-group
[chars]. Message details: type [unsigned
int], update type [unsigned int], size
[unsigned int], attribute size [unsigned int],
Nexthop length [unsigned int]

An error was encountered when allocating

update message buffer. Update generation
for the affected update-group will be
retried after some time and will recover
when the memory condition improves.

Writing to Socket Failed: [chars]

BGP detected that a socket write failed This

happens in the standby.

neighbor [chars] [chars]

A BGP neighbor has either come up or gone

down. This message appears only if the
<Bold>bgp log neighbor
changes<nobold> command is configured
for the BGP process.

neighbor [chars] [chars]

A BGP neighbor has either come up or gone

down. This message appears only if the
<Bold>bgp log neighbor changes
detail<nobold> command is configured for
the BGP process. This is the detailed
variant of the neighbor state change
message. Included in this message is a list
of AFI/SAFI which were advertized
(supported) by each end of the session and
are common to both. The AFI/SAFI values
are defined in RFC 1700, RFC 4760.

Cannot [chars]%s: already done

An operation could not be performed

because it had already been completed.

[chars]%s:([chars])inst-id [unsigned int],

[chars]

This notice message indicates that the BGP

async ipc operation has an important
status change, such as connection is up or
down, or the instance has received all the
initial configurations from BPM.

IPARM returned no valid router ID. This is

No router ID available. Cannot connect to due to lack of a global router ID or a
neighbors (retry in [unsigned int] seconds) loopback interface.

[chars] - set id [hex]

A problem occurred in TCP sync, retry TCP

sync.

A SEVERE low memory condition has been

encountered on the node where the BGP
process is running, and so to free some
memory, BGP has reset a neighbor. BGP
will continue to reset neighbors periodically
until the low memory condition abates. The
neighbors which are reset will be shut
down until a 'clear bgp' command is used
to bring them back up. They will not come
neighbor [chars] reset due to SEVERE low up automatically when the low memory
memory condition - use 'clear bgp [chars]' condition abates - this is to prevent the
to re-enable
node oscillating between memory states.

BGP is shutting down due to [chars] low

memory condition - use 'process restart
bgp location <node>' to restart

BGP received a notification that CRITICAL

low memory state has been entered, or
that SEVERE low memory state has been
entered while BGP is in READ-ONLY mode,
and consequently it has shut itself down in
order to free memory.

No. of [chars] prefixes received from

[chars] has reached [unsigned int], max
[unsigned int]

Number of prefixes received from a

neighbor for a given address family has
reached the warning level configured with
the 'max-prefix' command.

NSR disabled on neighbor [chars] on

standby RP due to [chars]

A BGP neighbor has NSR disabled on

standby temporarily due to transport
issues.

Changed state to [chars]

BGP changed its global NSR state.

Policy configuration change on neighbor

[chars] requires HARD reset (clear bgp
[chars]) to take effect.

Automatic soft reset on policy change is

not possible as the neighbor does not
support ROUTE_REFRESH and 'softreconfiguration inbound' is not configured.

[chars]

A BGP notification message of

unacceptable hold time has been received.

This informational message appears as

Router-id config (inst=[chars], vrf=[chars], user-configured router-id is the same as
rtrid=[chars]) cannot be the same as
IPARM's default router id. User should
IPARM's default router-id.
change the router-id.
Default BGP instance cannot use IPARM's
default router-id ([chars]) as its router id
since it is used by another BGP instance
already.

This informational message appears as

user-configured router-id of another BGP
instance is the same as IPARM's default
router id. User should change the router-id.

[chars] [chars] [chars]

An RPKI cache has either come up or gone

down.

[chars]

A BGP notification message of

unacceptable hold time has been sent.

Wrong table context ([chars], [pointer]) is

passed in for table attr [pointer] unlock correct table context [chars] ([pointer])

A warning was encountered during some

operation for tblattr for a table context. The
table context passed in is not same as the
table context under which the tblattr is
created. Normally this message will not
cause any issue. In rarely case it might.
The message is added for debug purpose
only to help the DE to find such cases.

Local tunnel update: remote tunnel route

for [chars], ifhandle is NULL

This informational message appears as

ifhandle of local tunnel route is NULL.
Interface must be down. It should not be
NULL if interface is up.

Remote tunnel route [chars]%s ifhandle is

NULL

This informational message appears as

ifhandle of remote tunnel route is NULL.
Interface must be down. It should not be
NULL if interface is up.

One or more attributes were filtered from

UPDATE message received from neighbor
[chars] (VRF: [chars]) - message length
[unsigned int] bytes, action taken \[chars]\.
Filtering details: \[chars]\. NLRIs: [[chars]]
[chars]%s

This message indicates that the UPDATE

message contained one or more attributes
that were filtered based on user
configuration. One of the following actions
has been taken: discard the attribute, or
treat the UPDATE as withdraw.

No routing policy has been configured for

the specified eBGP neighbor in the given
direction (inbound or outbound) for the
address family named. To avoid unintended
No [chars] [chars] policy is configured for routing effects, no prefixes will be accepted
eBGP neighbor [chars]. No [chars] prefixes in that direction until some policy is
will be [chars] the neighbor until [chars]
configured. 'Policy' can be a route-policy, or
policy is configured.
(for inbound policy) it can be a prefix list.

NSR has been restarted - [chars]

BGP has restarted NSR due to the reason

shown. There is no impact on forwarding.

Triggering switch-over to keep NSR up,

Failure reason: [chars]

If NSR switch-over is configured, active bgp

will trigger the switch over in case of TCP
failure or BGP failure, if NSR is ready and
an install operation is not in progress.

Neighbor update filter message buffers

resizing will not take effect after filtering
action has started. Current buffer size is
[unsigned int] messages while newly
configured buffer size is [unsigned int]
messages for neighbor [chars]

Currently resizing of update filter message

buffers is not supported.

Memory consumption for transient update

Update generation has recovered from a
messages has fallen below the recovery
previous throttle event for [chars] \[chars]\ threshold for a given entity (Process or
because the memory consumption
Address-family or Update sub-group).
([unsigned int] bytes) decreased below the Update generation had been previously
recovery threshold (upper limit is [unsigned throttled for this entity and is now being
int] bytes)
recovered.

Memory consumption for transient update

messages has crossed the effective upper
threshold for a given entity (Process or
Address-family or Update sub-group).
Update generation has been throttled for
Hence update generation has been
[chars] \[chars]\ because the memory
throttled. It will recover automatically when
consumption ([unsigned int] bytes) crossed the messages are freed after sending them
the upper limit of [unsigned int] bytes
to the peers.
Update limit accounting inconsistency.
Details: \[chars]\

An error was encountered when counting

update messages. It is automatically
corrected.

Warning: A call to [chars] failed

unexpectedly: [chars]

A function call failed unexpectedly - this is

probably a system problem

Failed to checkpoint allocation of [chars]

([chars]) to speaker [unsigned int]

The BPM failed to record the allocation in

the checkpoint table. This could cause
operational problems if the BPM is later
restarted.

Unable to [chars] for [chars]. [chars] RIB

table [hex]
[chars] failed

A warning was encountered during some

operation for the specified address family
and RIB table. This could be due a software
timing issue, caused by configuration
changes.
A tree operation failed.

Process initialization failed: ([chars]%s)

[chars] - [chars]
[chars] - [chars]
[chars]

MRIB (multicast routing information base)

failed to initialize. MRIB is the central
routing information base for multicast
components. It provides coordination
among all multicast routing components
and forwarding. The effect is that multicast
forwarding will not function. %s - indicates
the reason for the failure.
'development message'
'development message'
'development message'

Thread connection failed: ([chars]%s)

The linecard MDT EA thread failed to

connect its to the route processor
processes during process initialization. The
MDT EA process thread handles MDT tunnel
interface information between the route
processor and the linecard hardware
drivers. If the MDT EA fails to connect, no
MDT tunnel interfaces can be created or
deleted on the line cards. %s - indicates
the reason for the failure. %s - is the
decoded error reason.

[chars]%s

The linecard MDT EA thread failed during

platform lib init. The MDT EA process
thread handles MDT tunnel interface
information between the route processor
and the linecard hardware drivers. If the
MDT EA fails , no MDT tunnel interfaces can
be created or deleted on the line cards. %s
- pthread library call failure. %s - is the
decoded error reason.

[chars]

'A software exception occurred during the

initialization of the c12000 ' 'multicast
library.'

[chars]

'Fragmentation occurred in multicast fast

path '

[chars] - [chars] ([hex])

'A software exception occurred during the

cleanup of the platform ' 'multicast library.
This is not a service impacting error, but '
'might result into memory leak.'

[chars] - [chars]

'A software exception occurred during

interaction with Interface Manager '
'process. This could be due to low memory'

[chars] - [chars]

'A software exception occurred resulting in

the failure of platform ' 'multicast library
initialization.'

[chars] - [chars] ([hex])

'A software exception occurred during the

initialization of the platform ' 'multicast
library. This is not a major service
impacting issue. It ' 'impacts just that
functional module as mentioned in the
error.'

[chars]

'A software exception occurred in platform

multicast library'

Unexpected packet num [unsigned int]

received on the LC

CLNS on the LC does not process any

packet. It will ignore any packets it receives
on the LC.

Failed to setup ingress packet handler for

NetIO: [chars]

CLNS encounted errors when initializing its

connection with NetIO.

CLNS failed to register with packet

manager for FSV area. It only affects the
algorithm used to pick a bundle member. If
CLNS failed to register with packet process no bundles are configured for ISIS - this
for bundle FSV area: [chars]
error can be ignored.

Cannot initialize CLNS configuration:

[chars]

CLNS could not initialize its configuration

mechanism, and all future CLNS
configuration will fail.

Failed to open connection for [chars]:

[chars]

CLNS encounted errors when opening its

connection with the process mentioned in
the message. CLNS will reattempt the
connection by restarting.

Stopping CLNS debug initialization

attempts after [unsigned int] tries

CLNS tried to initialize packet debugging

functions but was unable to succeed even
after a number of attempts. No more
attempts will be made.

[chars]. Dropping packet

CLNS encountered an internal error while

trying to process a packet (usually for
output). As a result CLNS dropped the
packet.

Error during operation '[chars]': [chars]

CLNS EDN client (usually a show command)

failled to perform certain operation.

Bad encoding failed for [chars]: [chars]

CLNS failed encode a bag for EDM.

CLNS show command failed to initialyze

the EDM server. 'show' command will likely
Operation '[chars]' during EDM initialization fail, although CLNS should be able to
failed: [chars]
operate.

Cannot register CLNS error codes: [chars]

CLNS could not initialize its error code.

CLNS will work, but error messages won't
be user friendly!

Incorrect MAC address length [dec]

The MAC address length provided for the

ethernet encapsulation is wrong.

Error creating '[chars]' connection: [chars]

CLNS failed to create a connection to an

essential service during initialization. This
is an internal error. It requires a restart of
the process for recovery.

Error registering for critical events on

'[chars]' connection: [chars]

During initialization, CLNS failed to register

for essential notifications regarding the
state of the connection for the specified
service. This is an internal error. It requires
a restart of the process for recovery.

[chars]:[chars]

CLNS encountered errors during

initialization.

Cannot get traffic information: [chars]

CLNS show command failed to get the

required information.

CLNS failed to register for an HSSD area:

[chars]

CLNS failed to register for an HSSD area.

This is an internal error.

Operation '[chars]' on CLNS interface

[chars] failed: [chars]

CLNS could not initialize its interface.

CLNS was unable to resolve an interface

while installing cap/decap chain.

CLNS was unable to look up local interface

information. As a result the system may
not be able to send/receive ISIS packets
over this interface. This may be due to
problems with either CLNS or the
forwarding infrastructure.

Couldn't add clns binding to lpts port

arbitrator, error = [chars]

The clns process was unable to add a

binding to LPTS. This is an internal error.

Couldn't delete CLNS binding from Port

Arbitrator, result = [chars]

The clns process was unable to delete a

binding from LPTS. This is an internal error.

Cannot set the LPTS option '[chars]':

[chars]

An operation failed during LPTS option

setting.

CLNS failed to register for media callback

with netio during initialization. As a result,
CLNS will not be able to add its caps and
CLNS failed to register media callback with wont receive or send packets. It's an
netio: [chars]([dec])\n
internal error.

CLNS failed to setup encap callback with

this particular media or base capsulation.
As a result CLNS will not be able to receive
CLNS netio encap callback for media caps: CLNS packets on this caps on any interface
[chars]([dec]) failed [chars]([dec])\n
on this node.

CLNS netio set mapping for media caps:

[chars]([dec]) failed [chars]([dec])\n

CLNS failed to setup mapping with this

particular media or base capsulation. As a
result CLNS will not be able to receive CLNS
packets on this caps on any interface on
this node.

Packet operation '[chars]' failed: [chars]

An operation failed during packet handling.

Socket initialisation task '[chars]' failed:

[chars]

An operation failed during socket

initialisation.

Internal socket error on packet reception:

[chars]

An operation failed during packet

reception.

error encountered when parsing path:

[chars]

CLNS was unable to extract the xipc & job

id from the socket path. This might cause
communication problems between ISIS and
CLNS.

Failed to setup the clns socket as a

resource manager: [chars]

The clns process failed to advertise itself to

the system as a resource manager.

An operation failed during the Stats Server

Cannot connect to the stats server: [chars] Connection opening.

Cannot [chars] with the stats server for

interface <<CH[hex]>> ([hex])

An operation failed during the Stats Server

Interface registration.

Error starting thread for [chars]

processing : [chars]

CLNS failed to create the thread for the

operation mentioned in the message. CLNS
will try to recover by restarting.

Operation '[chars]' failed during packet

timestamping: [hex] ([chars])

An operation failed during timestamp

processing.

IM base capsulation lookup for interface

<<CH[hex]>> ([hex]) failed: [hex],
'[chars]'

The Interface Manager returned an

unexpected error when CLNS attempted to
lookup an interface's base capsulation
type. This may be a resource problem but
is probably an internal error.

Error setting the linear retry period for

'[chars]': '[chars]'

CLNS failed to set the linear retry period for

connecting to sysdb. We set the retry
period in order to avoid immediate
reconnection attempt from clns to sysdb
server when the latter restarts. This
prevents clns from blocking on sysdb and
cause any traffic drop.

Failed to register with the debugging

subsystem: [hex], '[chars]'

CLNS failed to register with the debugging

subsystem. If this message has been
generated then CLNS debugging may not
be available. This may be a system
resource problem.

[chars]: Netio IDB not found for interface

<<CH[hex]>> ([hex]), packet 0x[pointer]
dropped

CLNS was unable to find the NetIO IDB for

the interface handle in the message. If this
is seen during NetIO restart, it could be
transient condition that should recover
once NetIO is back up with all the IDBs in
steady state. If this is seen in steady state,
the ISIS adjacency on this interface could
be affected. *RECUR*

IM control handler setup failed: [chars]

CLNS failed to establish signal event in the

Interface Manager control plane. It's an
internal error.

CLNS was not able to send a packet to

NetIO. This could be because of
Failed to send packet 0x[pointer] to NetIO communication problems between CLNS
on interface <<CH[hex]>> ([hex]): [chars] and NetIO.

Failed to process packet 0x[pointer] from

ISIS: [chars] [chars]

CLNS was not able to process a packet

from ISIS successfully and hence dropped
the packet.

Failed to process packet 0x[pointer] from

NetIO: [chars]:[chars]

CLNS was not able to process a packet

from NetIO successfully and hence dropped
the packet.

Failed to send Hello PDU(0x[pointer]) type

[chars] ([hex]) from interface
<<CH[hex]>>([hex]) to ISIS instance
[chars]: [chars]

CLNS was not able to send a hello class

PDU to ISIS. This could be because of
communication problems between CLNS
and ISIS.

Failed to send PDU(0x[pointer]) type

[chars] ([hex]) from interface
<<CH[hex]>>([hex]) to ISIS instance
[chars]: [chars]

CLNS was not able to send non-Hello class

PDU to ISIS. This could be because of
communication problems between CLNS
and ISIS.

Failed to init debug tracing support :

[chars]

CLNS failed to init with the ltrace

subsystem. This affects the debuggability
of the component. CLNS will attempt to
restart to recover from the situtation.

Unknown media ([dec]) on interface

<<CH[hex]>> ([hex])

The specified interface media is not

supported by CLNS. This means that IS-IS
and other CLNS protocols cannot run over
the specified interface. This is an internal
programming error.

Failed to add CLNS encapsulation to

interface <<CH[hex]>> ([hex]): [chars]

CLNS failed to add caps to its

encapsulation chain. It's an internal error.

CLNS failed to connect to packet area\n

CLNS failed to connect to packet

subsystem during initialization. As a result,
CLNS will not be able to receive or send
packets. It's an internal error.

CLNS failed to create the thread for debug

registration and to handle debug events.
Thus, causing unavailability of debugs. But
CLNS should continue with the normal
Error starting thread for debug registration: functionality, so the process should not exit
[dec]
even if this thread is not created.

CLNS failed to initialize the L2 hash

function: [chars]\n

CLNS failed to initialize the L2 hash

function. It's an internal error.

policy_repository is unable to listen for

events of package un-installs because:
[chars]

A failure occured while trying to setup the

event listen structure for package uninstalls.

Invalid setup at [chars]@[dec]: [chars]

There was something illegal about the

setup operations that where performed.
This should be a straight coding error that
will fail everytime and should be cleaned
up before releasing the code.

policy_repository was unable to bind to

sysdb because: [chars]

The bind operation has failed for the above

reason. This is something that should not
occur under normal operations.

The DAD library attempts to delete the old

policy_repository was unable to delete
protocol information before writing out the
previous protocol info from sysdb because: new information. This delete operation
[chars]
failed for the above reason.

The DAD library encountered an error while

policy_repository was unable to write policy writing out the policy information for the
information into sysdb because: [chars]
above reason.

policy_repository is unable to notify sysmgr A failure occured while trying to tell sysmgr
process availability because:[chars]
that we are available.

policy_repository is unable to listen cleanup

notices for package un-install because:
A failure occured while trying to ask sysmgr
[chars]
for cleanup events for package un-installs.

policy_repository is unable to notify sysmgr A failure occured while trying to tell sysmgr
process ready because : [chars]
that we are ready for processing.

[chars]

An internal software error occurred

Failed to build [chars]: [chars] ([chars])

Internal error in the routing policy library.

There was an internal error in the routing

Failed to build ORA[chars]: [chars] ([chars]) policy library.

Could not apply policy operation [chars] to

attribute [chars] because [chars]
Internal error in the routing policy library.

EIGRP-[chars]: [chars] [dec]: Could not

allocate memory for [chars]

There is not enough memory available for

the process.

EIGRP-[chars]: [chars] [dec]: Anchor count

negative

Internal error in the flow control module in

EIGRP.

EIGRP-[chars]: [chars] [dec]: Invalid path

count for route [chars], [dec] successors,
[dec] paths

A bad reference count has been detected

while adding a path for a prefix.

EIGRP-[chars]: Failed to create [chars]

Event Manager: [dec], '[chars]'

The process failed to create an Event

Manager to receive events in the specified
thread. This is most likely to be caused by
a resource starvation problem, but may
also be due to an internal programming
error.

EIGRP-[chars]: [chars] [dec]: No [chars]

registered for [chars] [chars] (version:
[unsigned int])

EIGRP could not find an encoder/decoder to

be used to transmit/receive packets.

EIGRP-[chars]: Error signaling process

ready: [hex], '[chars]'

The process was unable to signal process

ready to the IOS-XR infrastructure.

EIGRP-[chars]: Error while checking for

more configuration batches [chars]: [hex],
'[chars]'

An unexpected error occurred whilst

checking for more configuration batches
after receiving request to shutdown the
process. This may be due to resource
starvation or an internal programming
error.

EIGRP-[chars]: [chars] The system

database connection could not be
established at the path [chars]: [hex],
'[chars]'

The process failed to bind to system

database while opening a connection to it.

EIGRP-[chars]: Registration verification

failed for [chars]: [hex], '[chars]'

The process failed to register for

verification of changes to its configuration
data.

The process failed to initialize the handler

EIGRP-[chars]: [chars] Verification function functions for verification of changes to its
initialization failed: [hex], '[chars]'
configuration data.

EIGRP-[chars]: Event handler error in

[chars]: [dec], '[chars]'

Event handler error ERRNO. This system

encountered an error ERRNO trying to get
an event from the event handler.

EIGRP-[chars]: [chars] [dec]: [chars]

An internal error occured in the process.

EIGRP-[chars]: [chars] [dec]: Flow control

error, [chars], on [chars]

Error in the flow control algorithm in EIGRP.

EIGRP-[chars]: [chars] [dec]: No metric set Metric is not configured during

while redistributing route [chars]/[dec]
redistribution.

EIGRP-[chars]: [chars] [dec]: No buffers

available for [unsigned int] byte packet

EIGRP could not allocate a packet buffer to

transmitting a packet.

EIGRP-[chars]: [chars] [dec]: Failed to

Error in constructing a packet, to be
construct packet to send on [chars]. [chars] transmitted by EIGRP.

EIGRP-[chars]: [chars] [dec]: [dec] peers

exist on [chars]

One or more peers exist on an interface

which is being deleted.

EIGRP-[chars]: [chars] [dec]: [chars] prefix 'Number of prefixes for eigrp has reached
limit reached
the configured ' 'or default limit.'

EIGRP-[chars]: [chars] [dec]: Interface

removed, but route [chars], nexthop
[chars] ([chars]), origin [chars], has path

Routes exist over an interface being

deactivated.

EIGRP-[chars]: [chars] [dec]: Negative

refcount in packet descriptor 0x[pointer]

Internal reference count error in EIGRP.

EIGRP-[chars]: [chars]: Route [chars] stuck- Neighborship was reset to the specified
in-active state in instance [dec]. Cleaning peer, due to a prefix being in stuck-inup
active state.

EIGRP-[chars]: Unknown timer type [dec]

expiration

Unknown timer encountered in EIGRP.

EIGRP-[chars]: [hex], '[chars]'

This system was unable to register the

internal error DLL. This is probably due to a
faulty installation.

EIGRP-[chars]: Error registering for debug

events: [hex], '[chars]'

The process failed to register with the

debug module for printing messages.

EIGRP-[chars]: [chars] [dec]: Error

[chars]setting [chars] option in [chars]

EIGRP was unable to set the specified

socket option on the specified interface or
VRF.

EIGRP-[chars]: Error disconnecting [chars]

system database connection: [hex],
'[chars]'

The process failed to disconnect from

system database. The error will not affect
operation but does indicate that a
programming error has occurred.

EIGRP-[chars]: [chars] [dec]: [chars]

ISSU in EIGRP works on top of NSF and GR.

If NSF is disabled, during ISSU, EIGRP will
not be able to retain the routes learnt from
its peers and may result in traffic loss.

EIGRP-[chars]: [chars] [dec]: [chars]

threshold prefix level reached

'Number of prefixes in the topology

database has reached ' 'the configured or
default threshold level.'

EIGRP-[chars]: [chars] [dec]: [chars]

There is a subnet mismatch between eigrp

neighbors.

EIGRP-[chars]: [chars] [dec]: Neighbor

[chars] ([chars]) is [chars]: [chars]

An EIGRP neighbor has gone UP or DOWN.

EIGRP-[chars]: [chars] [dec]: [chars]

An EIGRP event logged into the trace

buffer.

EIGRP-[chars]: The [chars] \[chars]\ is

invalid

The name chosen for the process matches

or is a subset of an EIGRP show or clear
command. This can cause ambiguities with
subsequent show or clear commands for
this process. Hexadecimal and octal
numbers are not allowed. If Decimal, it
should be in range of 1 to 65535.

EIGRP-[chars]: [chars] [dec]: Failed to send

packet on [chars]. [chars]
Failed to send a packet from EIGRP.

Failed to [chars] : [chars]

This message indicates an error is binding

to the ifh server or obtaining the correct
interface from the ifh server.

Process initialization failed: ([chars]%s)

MRIB (multicast routing information base)

failed to initialize. MRIB is the central
routing information base for multicast
components. It provides coordination
among all multicast routing components
and forwarding. The effect is that multicast
forwarding will not function. %s - indicates
the reason for the failure.

No memory, [chars]: [chars]

Allocation of the specified resource failed

because of a low memory condition.

The ForUs client library debug failed to

initialize, event: [chars], error: [chars]

Initialization of debugging in the ForUs

client library failed.

[chars]: [chars]

The CEF system could not allocate the data

structures needed to initialize a new
forwarding table.

CEF table creation failure, id:[dec] [chars]

An internal software error occurred that

prevented the creation of a new forwarding
table.

Attribute [hex] insert failed [hex], [chars].

FIB is dropping this attribute due to error

FIB cleanup of quarantined idb extension

failed. Encoded info: IDB_ext:(0x[pointer])
Proto:([chars]) Interface:([hex]). Flags:
([hex]), Ref_count:([dec]), NH_count:
([dec]), Glean_nhinfo:(0x[pointer]).
Detailed info dump at: [chars]

FIB failed to cleanup an IDB on detecting

interface handle recycle to a new interface.
Some of the routes may be in incorrect
state and may affect traffic forwarding for
those routes. There is no self recovery.

FIB initialization failed on this node.

Reason: [chars]. Decoded error reason:
[chars]

FIB initialization has failed due to the

reason indicated in the message. The
process will attempt to recovery by
restarting. If the restart count is excessive
then the node may reload. This will not
normally affect existing traffic but may
affect the ability to process forwarding
updates.

FIB thread [chars], received an invalid

message. Decoded error reason: [chars].
Encoded return value:([unsigned int])

FIB internally manages its activity using

'events'. An error occurred while processing
events. The process will attempt to
recovery by restarting. If the restart count
is excessive then the node may reload. This
will not normally affect existing traffic but
may affect the ability to process forwarding
updates.

Dropping add/modify route [chars]/

[unsigned int] msg due to low memory.

FIB is not adding or modifying this route

due to a low memory condition.

Dropping delete route [chars]/[unsigned

int] msg due to low memory.

FIB is not deleting this route due to a low

memory condition.

Dropping route [chars]/[unsigned int] due

to no knowlege of memory available. err
[hex], [chars].

FIB is dropping this route because it is

unable to find the memory available.

Dropping routes due to no knowlege of

memory available. err [hex], [chars].

FIB is dropping this route because it is

unable to find the memory available.

FIB has run out of [chars] resource memory. The FIB process on the node has detected
No more route updates will be handled by an out of resource condition for the
FIB. Please delete routes, and then clear
indicated resource. Normal operation
FIB on this node to resume normal
cannot resume until routes are deleted and
operation.
customer does a clear cef on the node.

FIB has run out of table resource memory.

This table [hex] could not be created.
Please check the memory on the card and
then recreate/reconfigure the table when
enough memory is available.

The FIB process on the node has detected

an out of resource condition for the
indicated resource. Normal operation
cannot resume until routes/tables are
deleted and customer does a recreate of
the table.

FIB protocol [chars], initialization failed.

Reason: [chars]. Decoded error reason:
[chars]. Encoded return value:([unsigned
int])

FIB protocol-specific initialization has failed

due to the reason indicated in the
message. The process will attempt to
recovery by restarting. If the restart count
is excessive then the node may reload. This
will not normally affect existing traffic but
may affect the ability to process forwarding
updates.

Dropping route update to [chars]/[unsigned FIB is not processing this route update due
int] path [dec] interface [hex]
to internal error
FIB initialization has failed due to the
reason indicated in the message. The
process will attempt to recovery by
restarting. If the restart count is excessive
then the node may reload. This will not
FIB startup failed at state: [chars]. Decoded normally affect existing traffic but may
error reason: [chars]. Encoded return value: affect the ability to process forwarding
([unsigned int])
updates.

FIB thread [chars], initialization failed.

Reason: [chars]. Decoded error reason:
[chars]. Encoded return value:([unsigned
int])

FIB thread-specific initialization has failed

due to the reason indicated in the
message. The process will attempt to
recovery by restarting. If the restart count
is excessive then the node may reload. This
will not normally affect existing traffic but
may affect the ability to process forwarding
updates.

CEF : fail to add route for [chars] [unsigned

int]
CEF fails to add a prefix entry.

FIB error in AIB communication [chars]:

[chars]

An error occurred when FIB tried to

communicate with AIB. The process will
attempt to recovery by restarting. If the
restart count is excessive then the node
may reload. This will not normally affect
existing traffic but may affect the ability to
process forwarding updates.

An internal consistency check failed. There

may be no immediate impact on traffic, but
FIB internal inconsistency detected: [chars] this issue should be addressed.

An internal consistency check failed. There

may be no immediate impact on traffic, but
FIB internal inconsistency detected: [chars] this issue should be addressed.

FIB error in attribute operation: [chars]: for FIB maintains a per-table attribute
[chars] ([dec], [chars])
database, but was unable to process it.

BCDL failed during [chars]: [chars]

An internal software error occurred that

prevented the FIB from working properly
with BCDL.

FIB error in BCDL operation: [chars] for

group [chars]: [chars]

An error occurred when FIB tried to

communicate with BCDL, which is the
mechanism via which route updates are
propagated. This will not normally affect
existing traffic but may affect the ability to
process forwarding updates.

Config registration error: [chars] [chars]

An internal software error ocurred.

CEF CLIENT: [chars] [chars]

CEF client internal error.

FIB error in EA client [chars]

communication [chars]: [chars]

A FIB client behaved erroneously or there

was an unexpected state.

FIB error while creating default route:

[chars]

A route update was skipped because of an

internal error

CEF : fail to delete route for [chars]

[unsigned int]

CEF fails to delete a prefix entry.

FIB error while attempting to restore

dummy real zero: [hex] [chars]

Cannot restore the dummy real zero route

to its original state

FIB is removing dummy real zero because

of error: [hex] [chars]

Forced to delete because cannot restore

the dummy real zero because of error

Gtrie initialization default value failed,

[chars] [chars]

An internal software error occurred that

prevented the FIB subsystem from starting

FIB general error: [chars]

A software error occurred. There may be no

immediate impact on traffic, but this issue
should be addressed.

FIB error in generic trie operation: [chars]:

[chars]

FIB internally manages its prefix databases

using generic tries. An error occurred while
processing prefixes using the generic tries.

Gtrie delete failed, [chars]/[unsigned int]

(Err: [hex], [chars])

An internal software error occurred that

prevented the FIB subsystem from
removing a route

FIB error in IDB operation for interface

[hex]: [chars]: ([dec], [chars])

FIB maintains a database for interfaces, but

was unable to process an entry. This will
not normally affect existing traffic but may
affect the ability to process forwarding
updates.

FIB graceful exit following initialisation

failure timed-out, exiting ungracefully

An internal software error occurred

FIB internal error: [chars]

An internal software error occurred There

may be no immediate impact on traffic, but
this issue should be addressed.

FIB received invalid path flags from BGP:

[hex], PL: 0x[pointer]

Received an invalid combination of BGP

path flags

This is an unexpected state where after

FIB LEAF-DEL-ERR: All dependents of leaf
leaf deletion, leaf still has some dependent
[pointer] did not unlink, leaf-ref-count:[dec] paths pointing to it. This could prevent the
first-dep:[pointer]
leaf from getting freed

FIB failure maintaining lisp eid tbl in vrf

[chars]: [chars]

This reflects a failure in the maintenance of

the lisp eid table used to control lisp
decapsulation in the specified VRF.

This reflects a failure in the maintenance of

FIB failure maintaining iid [unsigned int] for the lisp instance id to EID table mapping
rloc table [chars]: [chars]
for the specified RLOC table.

FIB failure maintaining lisp rloc tbl in vrf

[chars]: [chars]

This reflects a failure in the maintenance of

the lisp rloc table used to control lisp
decapsulation in the specified VRF.

FIB couldn't allocate memory for some

internal processing. It might be in an
FIB heap memory allocation failure: [chars] consistent state.

Malloc Failure, [chars]

An internal software error ocurred. CEF

switching disabled on this slot.

Failed to find CEF forwarding table [chars]

An internal software error ocurred.

FIB platform error: [chars]

When FIB processes forwarding updates, it

may have to program the underlying
platform hardware. The software controlling
the platform hardware encountered the
error shown during this programming. This
will not normally affect existing traffic but
may affect the ability to process forwarding
updates.

FIB mismatch in interface type for ifh [hex],

flags [hex], iftype [unsigned int], PFI iftype
[unsigned int]
An internal consistency check failed.

CEF : [chars] ifh:[hex], if:<<CH[hex]>>

CEF fails to connect or get information from

pfi_ifh server,

When FIB processes forwarding updates, it

may have to program the underlying
platform hardware. A failure occurred
during this programming. This will not
FIB platform update failed: Obj=[chars]
normally affect existing traffic but may
[ptr=[pointer],refc=[hex],flags=[hex]]
affect the ability to process forwarding
Action=[chars] Proto=[chars]. Cerr=[chars] updates.

CEF : rt_check_send_msg failed: [chars]

CEF fails to send rcc error messages,

FIB route check failed table [hex], protocol

[chars]: [chars] This will not normally affect An internal software error occurred that
existing traffic but may affect the ability to prevented the FIB from completing the
process forwarding updates.
route check.

RCC failed finding [chars] table

The Route Consistency Checker failed

finding specified table.

FIB recursive loop: [chars]

A forwarding loop has been detected,

where a prefix ends up recursing via itself.

FIB retry failed [chars]: [chars]

During normal operation, if FIB cannot fully

process an update, it may queue the
update to be retried later. An error occurred
which prevented the retry. This will not
normally affect existing traffic but may
affect the ability to process forwarding
updates.

FIB [chars]: [chars]

An internal software error occurred during

route handling. This will not normally affect
existing traffic but may affect the ability to
process forwarding updates.

Unable to initialize CEF RCP handler:

[chars] program [dec] version [dec]
protocol [dec]

The CEF system could not initialize an RPC

server and therefore cannot handle show
and clear commands from the parser.

CEF SERVER: [chars] [hex]

CEF server internal error.

CEF SERVER: [chars] [chars]

CEF server internal error.

FIB error in shared memory operation:

[chars]: [chars]

An internal software error occurred that

prevented the FIB from working properly
with shared memory.

Shared memory failure: error code [dec],

[chars]

An internal error ocurred.

An internal software error occurred that

prevented the FIB from working with
FIB error in table operation: [chars]: [chars] multiple tables.

Thread processing error: [chars]

An internal software error ocurred.

FIB timer inititalization failed [chars]:

[chars]

FIB internally manages sone activity using

'timers'. An error occurred while initializing
timers. The process will attempt to
recovery by restarting. If the restart count
is excessive then the node may reload. This
will not normally affect existing traffic but
may affect the ability to process forwarding
updates.

Missing cef idb for ifh:[hex],

<<CH[hex]>>, during [chars]

An internal software error occurred.

FIB idb lookup failed ifh [hex],

if:<<CH[hex]>> [chars]: [hex], [chars]

An internal software error occurred.

[chars]: [chars]

Internal error.

FIB platform update type - [chars] for

interface [chars] (idb 0x[pointer], protocol
[chars]) took too long - [dec] secs

We don't expect platform updates to take

too long. This can block other processes
that need to communicate with fib_mgr, for
instance, for config, etc.

FIB error in IM operation: [chars], [chars]

An error occurred when FIB tried to

communicate with IM.

fail to connect to IM [chars]

An internal software error occurred.

IP CEF initialization failure: [chars]

Initialization of CEF failed

FIB has a limit on the number of local

FIB has run out of local attribute resources attribute indices it allocates per per table.
for proto: [chars], VRF: [chars], max
Check if the maximum number make sense
attribute count: [dec]. OOR state: red
from BGP routes/config.

Failed to open trace file: [chars]

The FIB process was unable to open the

trace buffer for automatic tracing (show
trace cef may not work).

fail to connect to PFI_IFH [chars]

An internal software error occurred.

fail to lookup information in PFI_IFH [chars]

for ifh [hex]
An internal software error occurred.

FIB failed to create FRR state for proto

[chars], interface [hex] (parent [hex]),
nexthop [chars] - [chars]

We don't expect this FRR state setup to fail.

It can only happen under low memory or
some unexpected conditions.

FIB unexpected event handling condition:

proto [unsigned int], opc [unsigned int],
[chars]

FIB internally manages its activity using

'pulses'. An error occurred while processing
pulses. This will not normally affect existing
traffic but may affect the ability to process
forwarding updates.

Error initializing IP CEF radix tree

Initialization of the radix tree could not be

accomplished because of a low memory
condition.

The FIB process has detected that average

utilization for specified resource has risen
above a predefined high watermark value,
and has enterred resource contrained
FIB running low on [chars] resource
forwarding mode. In this mode, the cef will
memory. FIB will now begin resource
only handle route deletes which may
constrained forwarding. Only route deletes potentially freeup some memory. Due to
will be handled in this state, which may
this operational mode, RIB and FIB will be
result in mismatch between RIB/FIB. Traffic out of sync. Once routes are deleted and
loss on certain prefixes can be expected.
resource utilization level drops to
FIB will automatically resume normal
acceptable levels again, cef will come out
operation, once the resource utilization
of this operational mode and resume
returns to normal level.
normal operation.

FIB internal error [chars]: [chars]

An internal software error occurred.

FIB dropping route update: [chars]

An internal software error occurred and FIB

had to throw away a route update

IPV4-FIB: Debug registration failed: [chars] Debug message registration failed

Unbind for object type [chars] failed from

parent type [chars] - no unbind handler
found

FIB internal APIs need/expect an unbind

handler, which wasn't found. This can lead
to FIB not cleaning up state on interface
delete events.

[chars]

FIB is restarting with a reset of it's shared

memory to possibly recover from an
unrecoverable state

FIB local attribute resource state has

returned to normal for proto: [chars], VRF:
[chars], attribute count: [unsigned int].
OOR state: green

The local attribute index database on the

LC has resources available. The number of
attributes programmed to local attribute
index zero while the OOR state was red is
displayed. If you wish to recover them,
then issue a 'clear cef vrf <vrf>'.

The FIB process had previously detected

that the hardware,software resources
required for operation were running low,
FIB resource state has returned to normal. and had enterred resource constrained
FIB has exited resource constrained
forwarding. Now resources have been
operation and normal forwarding has been restored and FIB has resumed normal
restored
operation.

SMU installed will reset shared memory,

which will impact traffic till fib_mgr
initializes.

SMU installed has been designed to cause

SHM reset without having to reload the
router. Till fib_mgr initializes there will be
impact on traffic.

The process is being restarted either

because we failed to initialize or we
[chars] restart_count = [dec] mode = [dec] finished resetting shared memory and we
([chars])
are starting fresh.

Failed to [chars] : [chars]

Internal error.

Failed to add LC [dec] into FGID [dec]:

[chars]

Internal error.

Failed to [chars]: [chars]

Internal error.

Failed to remove LC [dec] from FGID [dec]:

[chars]
Internal error.

Failed to open a file [chars] to dump the

[chars] database

Internal error.

Failed to [chars] : [chars]

Internal error.

im_interface_name error in function [chars]

: [chars]
Internal error.

Failed to [chars]

Init error.

Failed to [chars] : [chars]

Internal error.

Failed to [chars] : invalid fgid value [hex]

Internal error.

Failed to [chars] for [chars]

Internal error.

Failed to [chars]

Internal error.

Event error: [chars] in [chars]

Event error

Init error: [chars]

Initialization error

Memory error: [chars] in [chars]

Memory error

msg error: [chars] in [chars]

Messaging error

Socket error: [chars] in [chars] : [chars]

Socket error

Error registering igpte-lib [chars] bags:

[hex], '[chars]'

IGP failed to register its bag files with the

bag library.

Error registering for IGP debug events:

[hex], '[chars]'

IGP failed to register with the debug

module for printing messages.

Error initializing LTRACE buffers: [hex],

'[chars]'

A process failed to initialize internal tracing

buffers in the IGP/TE API DLL

Failed to bind to SysDB: error [hex]

([chars])

An error occurrred when accessing the

system database

Failed to register for [chars] notifications:

error [hex] ([chars])

An error occurrred when accessing the

system database

Failed to unregister for [chars] notifications: An error occurrred when accessing the
error [hex] ([chars])
system database

Failed to allocate [unsigned int] bytes for

'[chars]'

The process failed to allocate memory for

the specified resource.

Data queue is full and it cannot accept

message queue is full. Cannot accept more more element. It could be a result of
element.
memory limitation.

Failed to allocate [unsigned int] bytes for

'[chars]'

The process failed to allocate memory for

the specified resource. This could be
because the topology is too large for the
memory installed in the router.

Data ([dec]) is too big or small([dec])

Failed to send data due to the limitation of

the buffer size. This is an internal error. It
requires to reduce the number of
interfaces.

Error in saving client's message channel

information

IGP failed to save its client's message

channel information. This could be a result
of channel down or resource allocation
failure.

IGP failed to release its client's message

Error in releasing client's message channel channel information. This could be a result
information
of channel down already.

: [chars], Interface Handle - [hex]

The nexthop is resolved over an

unsupported BFD interface.

Failed to delete idb for interface [chars]

from '[chars]' thread

The static routing process failed

unexpectedly to delete an interface
descriptor block from the idb WAVL tree.

The static routing process has failed at

[chars] with error [chars]

The static routing process has either failed

a function that expected to succeed, or has
got into an inconsistent state.

Error processing [chars] event for [chars]

from ITAL, table [hex] : [chars]

A static routing process failed unexpectedly

when processing an IP address change
event. This may lead to spurious or missing
connected and local routes in the routing
table.

Error handling create event for interface

[chars]: [chars]

The static routing process failed to

correctly handle a create event for an
interface which it was tracking.

A static routing process failed function

ip_static_ital_vrf_register for table [chars]:
[chars]

A static routing process failed to register a

table with ITAL. This may lead to routes
associcated with the failed interface, to be
added in the routing table.

Failed to delete nhdb for next-hop [chars]

for table [hex]

The static routing process failed

unexpectedly to delete an next-hop
descriptor block from the nhdb AVL tree.

Failed to delete otdb for object [chars]

The static routing process failed

unexpectedly to delete an objet tracking
descriptor block from the otdb AVL tree.

Failed to delete backpointer to path

[chars]/[unsigned int] from [chars] [chars]

The static routing process failed

unexpectedly to delete a path from an
interface or next-hop descriptor block's
path backpointer list.

[chars]: Failed to send RIB batch buffer repopulating RIB for table [hex]: [chars]

The static routing process failed

unexpectedly to update RIB with a batch of
updates.

Error re-installing route after a clear table

event for prefix [chars]/[unsigned int] in
table [hex]: [chars]

There was an error re-installing a route in

the RIB after receiving a 'clear prefix'
event.

Error re-installing routes after a clear table There was an error re-installing routes in
event for table [hex]: [chars]
the RIB after receiving a 'clear table' event.

Received a clear event for unknown prefix

[chars]/[unsigned int] in table [hex]

The static routing process received a clear

event from RIB for a prefix which it was not
tracking.

Received a clear event for unknown table

[hex] (Prefix [chars])

The static routing process received a clear

event from RIB for a table which it was not
tracking.

Failed to update RIB after ECMP

The static routing process failed
recalculation for table [hex], prefix [chars]/ unexpectedly to update RIB after an ECMP
[unsigned int]: [chars]
recalculation.

Error fetching event from RIB: [chars]

The static routing process failed

unexpectedly to fetch a notification event
from RIB.

Failed to update RIB during full topology

download for table [hex], prefix [chars]/
[unsigned int]: [chars]

The static routing process failed

unexpectedly to update RIB after RIB
restarted.

Failed to update RIB for table [hex], prefix

[chars]/[unsigned int], after receiving
interface state event for [chars]: [chars]

The static routing process failed

unexpectedly to update RIB after an
interface state change event.

Failed to update RIB for table [hex], prefix The static routing process failed
[chars]/[unsigned int] after receiving next- unexpectedly to update RIB after a nexthop resolution event for [chars]: [chars]
hop resolution event.

The static routing process failed

unexpectedly to register a next-hop
resolution event. Future state change
events on the next-hop may cause further
Failed to register next-hop notification with messages to be generated by the static
RIB for table [hex], prefix [chars]: [chars]
process.

Failed to unregister next-hop notification

with RIB for table [hex], prefix [chars]:
[chars]

The static routing process failed

unexpectedly to unregister a next-hop
resolution event. Future state change
events on the next-hop may cause further
messages to be generated by the static
process.

Failed to update RIB for table [hex], prefix The static routing process failed
[chars]/[unsigned int] after receiving object unexpectedly to update RIB after an object
state up event for [chars]: [chars]
state up event.

Prefix [chars]/[dec]: Maximum path count

exceeded. Please remove (next-hop
[chars], interface [chars]) from the running
configuration.

The maximum allowed number of next-hop

paths for a single destination prefix has
been exceeded. One or more paths have
not been installed in the RIB, and should be
removed from the running configuration.

Process is shutting down: [chars]

The static routing process has performed a

graceful shutdown and will be restarted.

Failed to delete tdb for table [hex]'

The static routing process failed

unexpectedly to delete a table descriptor
block from the tdb AVL tree.

A static routing process failed function

ip_rib_protocol_register for table [hex]:
[chars]

A static routing process failed to register a

table with RIB. This may lead to routes
associcated with a the failed to be added in
the routing table.

Failed to send 'update complete'

notification to RIB for table [hex]: [chars]

The static routing process unexpectedly

failed an attempt to signal to the RIB that
the given table is now in sync

Route for [chars] is configured via ethernet The static route via ethernet interface
interface without nexthop, Please check if without nexthop is configured. This may
this is intended
cause come inconsistancy.
The maximum number of configurations for The maximum number of static route
static routes has been changed from
configurations which may be entered has
[unsigned int] to [unsigned int]
been changed.
The next-hop [chars] for table [hex] is a
local route. The static route(s) that has the The nexthop of a static route is a local
matching next-hop will not be installed.
route. This is an invalid configuration.
The next-hop [chars] for route [chars] in vrf
[chars] is outside of the subnet for [chars] The nexthop of a static route is outside of
and will not be installed in the routing
outgoing interface. This is an invalid
table.
configuration.
The next-hop [chars] for route [chars] in vrf
[chars] which was previously outside of the
subnet for [chars], is now within the subnet
and will be installed in the routing table.

The nexthop of a static route was outside

of outgoing interface. Now it has resolved
through the the same interface so became
valid configuration.

Received a [chars] event for unknown

interface [chars]

The static routing process received a

change notification event from ITAL for an
interface which it was not tracking.

[chars]

This is a catch all error message. It usually

means an uncorrectible problem

[chars] [dec] [chars] [dec] [chars]\n

Internal error. GTRIE debug library

initilization failed

[chars] [dec] [chars] [dec] [chars]\n

Internal non-serious error. GTRIE debug

library termination failed

[chars]

Internal error. Usually sever problems such

as failing to free memory

[chars]

Error while initializing Gtrie. Initialization

failed and aborted

[chars]

Error while initializing Gtrie. Initialization

will continue

[chars]

Internal error. A significant event but we

can still continue

Malloc Failure in trying to add adj for

[chars]

An internal software error ocurred.

Update for ifh:[hex], if:<<CH[hex]>>,

[chars] skipped. Reason: either no fib or
netio IDB

The layer 2 adjacency could not be

installed for the interface. This might cause
problems in forwarding traffic to this
interface.

Could not register ipv4 l2 loadhash function Call to register IPv4 l2 loadhash function
with AIB. Error=[chars]
failed.

IP-ADJ: No fibidb

Adding an adjacency to the adjacency

database failed. Reason for this failure is no
fib IDB

Update for ifh:[hex], if:<<CH[hex]>>,

[chars] failed. Unable to update database

The layer 2 adjacency could not be

installed for the interface. This might cause
problems in forwarding traffic to this
interface.

IP-ADJ([chars]): macaddr change out of

bounds

Extra large MAC change

ipv4_adj: Debug registration failed: [chars] Debug message registration failed

Unknown aib message opcode [dec]

The event manager passed an unknown

message code

IGMP accounting was unable to add a

record: [chars]%s: [chars]

Due to an unexpected internal error, the

IGMP accounting subsystem was not able
to add a record to acccount for join/leave
related events. The logs may therefore be
incomplete and missing some entries.

Failed to create chunk for [chars]

Internal error.

[chars] [chars]

Internal error.

ERROR : [chars] - [chars]

Internal error.

[chars]Fail to add [chars] into group

database

Internal error.

[chars]Group [chars] failed: [chars]

Internal error

Fail to find [chars] in group database

Internal error.

[chars]Fail to add [chars] into database

Internal error.

[chars]Fail to free [chars] from database:

[chars]

Internal error.

[chars]Interface [chars][[hex]][stale
[chars]] handle mishmatch, handle in IM
update [hex]

Internal error.

[chars] - [chars]

Internal error.

[chars]Interface [chars][[hex]] is still

present in vrf [chars]. check_idb [chars]
[[hex]] loc [dec]

Internal error.

[chars]Fail to monitor interface state of

[chars]

Internal error.

[chars]Interface [chars](context [chars])

doesn't belong to context [chars], please
clear config error

Internal error.

[chars]Interface [chars] has configured

under context [chars] already

Internal error.

[chars]Invalid state for IM state registration

batch on [chars] ([chars])
Internal error.

Failed to [chars]

Internal error.

[chars]%s [chars] in SSM range. Join

operation postponed

Internal error.

Failed to [chars]: [chars]

Internal error

MRIB connection error - [chars] in [chars]

Internal error

[chars]%s : [chars]

Internal error.

[chars]%s : [chars]

Internal error.

Sysdb Bind error for [chars] : [chars]

Internal error.

[chars]Sysdb backend scan failed for

[chars] : [chars]

Internal error.

ERROR : [chars] - [chars]

Internal error.

Sysdb Registration error : [chars] for

[chars] [[chars]]

Internal error.

Received an invalid event from WDSysmon Internal error.

[chars]

Internal error.

Received [chars] memory depletion

warning, stop creating new igmp state

Internal error.

Node memory back to normal, new igmp

states will be created

Internal error.

[chars]%s: [dec]

Maximum number of group accepted,

either per interface or globally.

[chars]ACL applied, removed [chars] from

[chars]

ACL applied to interface on which denied

groups join previously.

Dropping iparms update: type [chars] for

[chars] [[hex]]

Internal error

Failed to [chars] : [chars]

Internal error.

[chars] [dec] [chars] [dec] [chars]\n

Internal error. Multicast NetIO debug library

initilization failed

[chars] [dec] [chars] [dec] [chars]\n

Internal non-serious error. Mcast netio

debug library termination failed

Un-able to register BAG. Message: [chars]

The MFWD-HFR library encountered

internal error during EDM init setup.

Un-able to register SysDB notification for

MFWD-Config. Message: [chars]

MFWD-HFR library encountered error

during config notification registration.

Un-able to initialize SysDB EDM for MFWD- MFWD-HFR library encountered error while
Action function handlers. Message : [chars] initializing the EDM action event handlers

Un-able to initialize SysDB EDM init for

MFWD-Operation function handlers.
Message : [chars]

MFWD-HFR library encountered error while

initializing the edm oper handlers

Un-able to register SysDb EDM. Message

[chars] : [chars]

The MFWD-HFR library encountered

internal error during EDM oper/action setup

Retrying to bind with SysDB: [chars],

retry_count:[dec], Message: [chars]

The MFWD-HFR library encountered

internal error during Sysdb init setup. The
init setup will be retried for finite number of
retries.

[chars] : [chars]

The MFWD-HFR library encountered

internal error during Sysdb init setup. The
init setup will be retried for finite number of
retries.

Retrying to initialize SysDB: [chars],

retry_count:[dec], Message: [chars]

The MFWD-HFR library encountered

internal error during Sysdb init setup. The
init setup will be retried for finite number of
retries.

Couldn't register bags : [chars]

The MFWD-HFR library encountered

internal error during sysdb/edm init setup.
The init setup will be retried for finite
number of retries.

Couldn't register edm : [chars]

The MFWD-HFR library encountered

internal error during EDM init setup. The
init setup will be retried for finite number of
retries.

[chars] failed : [chars]

MFWD-HFR library encountered error

during setup. The init setup will be retried
for finite number of retries.

[chars] ([chars],[chars]/[dec]) has been

detected.

Inactive flow has been detect. This error is

normally cause by lack of traffic from the
source due to errors.

[chars] : [chars]

The MFWD-VIKING library encountered

internal error during Sysdb init setup. The
init setup will be retried for finite number of
retries.

[chars] : [chars]

The MFWD-ASR9K library encountered

internal error during Sysdb init setup. The
init setup will be retried for finite number of
retries.

Couldn't register bags : [chars]

The MFWD-VIKING library encountered

internal error during sysdb/edm init setup.
The init setup will be retried for finite
number of retries.

Couldn't register bags : [chars]

The MFWD-ASR9K library encountered

internal error during sysdb/edm init setup.
The init setup will be retried for finite
number of retries.

Couldn't register edm : [chars]

The MFWD-VIKING library encountered

internal error during EDM init setup. The
init setup will be retried for finite number of
retries.

Couldn't register edm : [chars]

The MFWD-ASR9K library encountered

internal error during EDM init setup. The
init setup will be retried for finite number of
retries.

[chars] failed : [chars]

MFWD-VIKING library encountered error

during setup. The init setup will be retried
for finite number of retries.

[chars] failed : [chars]

MFWD-ASR9K library encountered error

during setup. The init setup will be retried
for finite number of retries.

[chars] [chars] : [chars]

Internal error: Cannot create the adjacency

for a particular interface. Will retry for few
times

[chars] [chars] : [chars]

Internal error.

[chars]

These are unexpected errors

[chars]: [chars]

Internal error.

Failed to map AIB table: [chars]

Internal error.

[chars]: [chars]

We were not able to set all cached

adjacencies to zero when we got ELIBBAD
from AIB

Failed to initialize and chain together the

debug event discriptors : [chars]

Internal error.

Sysdb registration for debug config failed :

[chars]
Internal error.

[chars] : [chars]

Internal error.

Event connection create for [chars] failed:

[chars]

Internal error.

Event connection notify for [chars] failed:

[chars]

Internal error.

Event connection open for [chars] failed:

[chars]

Internal error.

Error while setting event connection

setretry. This will cause ipv4_mfwd_partner
and ipv6_mfwd_partner processes to exit.
When process exists, sysmgr will
automatically respawn the process for
some number of times. If it still fails,
Event connection setretry for [chars] failed: process remains in the exit state. This will
[chars]
impact multicast forwading.

Cannot create event manager : [chars]

Internal error.

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

Cannot initialize IDB library : [chars]

Failed while initializing IDB library.

Failed to [chars] : [chars]

Internal error.

Failed to initialize pfi ifh connection: [chars] Internal error.

Failed to initialize IFH server : [chars]

Internal error.

Failed to [chars] : [chars]

Internal error.

Failed to initialize im control server

connection: [chars]

Internal error.

im_caps_datapath_control error for [chars] :

[chars]
Internal error.

[chars]

These are unexpected errors

[chars] [hex]

These are unexpected errors

[chars] [chars]

Failed while initializing multicast library.

Failed to initialize MRIB connection : [chars]

failed : [chars]
Internal error.

Failed to initialize Multicast NSF : [chars]

Internal error.

Failed to initialize packet connection:

[chars]

Internal error.

[chars] : [chars]

Internal error.

Error in bag decoding : [chars]

Internal error

Error in bag free : [chars]

Internal error

Couldn't register bags : [chars]

Internal error.

SysDB operation [chars] failed: [chars]

Internal error.

Error in datalist free : [chars]

Internal error

Error in datalist next : [chars]

Internal error

SysDB operation [chars] failed: [chars]

Internal error.

SysDB operation [chars] failed: [chars]

Internal error.

SysDB operation [chars] failed: [chars]

Internal error.

SysDB operation [chars] failed: [chars]

Internal error.

Unexpected exit

Internal error.

[chars] : [chars]

Internal error.

[chars] [chars]

Internal error.

[chars]: [chars]

error while doing an HA operation (e.g.

starting frequent restart monitor)

[chars] [chars]

Internal error.

[chars] operation failed on [chars] [chars] :

[chars]
Internal error.

IM lookup failed for [chars] : [chars]

Internal error.

[chars] : [chars]

Error while performing

upgrade/downgrade/install operation

[chars] : [chars]

Internal error.

Cannot connect to [chars] using event conn Reached the maximum number of retries to
Mgr after [dec] retries: [chars]
connect to server using event conn

Failed to disable multicast after [dec]

retries: [chars]

Reached the maximum number of retries to

disable multicast

Failed to enable multicast [dec] retries:

[chars]

Reached the maximum number of retries to

enable multicast and

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

[chars] : [chars]

Failed to clear, set, or get transaction

pending flag. That can only happen if the
APIs to do that are called before shared
mem window is opened, or if thereis a bug

[chars] [chars]: [chars]

Failed to apply a TTL threshold config. The

operation will be retried.

[chars] [chars] : [chars]. Retrying

Internal error: Cannot create the adjacency

for a particular interface. Will retry for few
times

[chars] [chars]

Failure while doing all reource cleanup

Failed to [chars] AIB for interface [chars] :

[chars]

Internal error

[chars] [chars]

Error ocured while enabling mcast

Failed to initialize MRIB connection in

[chars]. Retrying later: [chars]

Internal error.

Failed to post signal to MRIB in [dec]

retries. Reseting connection: [chars]

Internal error.

[chars]: [chars]

Internal error.

[chars]: [chars]

Internal error.

[chars]: [chars]

Internal error.

[chars]: [chars]

Internal error.

MFIB couldn't process update from MRIB :

[chars] - [chars]

Internal error.

MFIB couldn't process update from MRIB :

[chars] - [chars]

Internal error.

[chars]

Internal error.

[chars] [chars]

Error ocured while disabling mcast

MFIB couldn't post MDT upd to MRIB:

[chars]

Internal error.

MFIB couldn't post MOFRR upd to MRIB:

[chars]

Internal error.

MFIB couldn't post update to MRIB: [chars] Internal error.

[chars] [chars]

Information regarding all resource cleanup

[chars] : [chars]

NetIO or Mfwd terminated while holding

shared mem mutex. Recovery action will be
taken

[chars] [chars]

APplying one or more IP address configs

may have failed. We will retry them. This is
a not a problem unless it keeps showing up
continuously.

[chars] [chars]

Most likely mfwd restarted and while it was

down mcast was disabled. The other
possibility is that mfwd retsarted while
disabling mcast. In either case, when mfwd
comes up, it will find that mcast is already
disabled. Hence it will log this message and
exit normally

[chars] : [chars]

Got notification that the the MFIB has been

reset. Will clear MFIB and restart

[chars] [chars]

Processing one or more updates may have

failed. We will retry them. This is a not a
problem.

[chars] [chars]

Error while enabling/disabling per route

accounting for a route

[chars] [chars]

Error while enabling/disabling per route

accounting for a route

[chars] Restarting to recover.

Was not able to commit at least one route

after retrying for the maximum number of
times. In this case, mfwd will restart in an
attempt to recover. This is not an error. It
just indicates that mfwd is restarting to
recover from possible stale route problem.

Cannot [chars] per prefix accounting for

table [chars]. [chars] [chars]

Error while enabling/disabling per route

accounting in a table

Cannot [chars] per prefix accounting for

table [chars]. [chars] [chars]

Error while enabling/disabling per route

accounting in a table

Cannot [chars] rate for routes for table

[chars]. [chars] [chars]

Error while enabling/disabling per route

rate in a table

Cannot [chars] rate for routes for table

[chars]. [chars] [chars]

Error while enabling/disabling per route

rate in a table

[chars] [chars]

Most likely some one tried to

upgrade/downgrade mfwd while we're not
connected to NetIO. In this case, teh
upgrade will wipe out all MFIB and traffic
will be disrupted

[chars]

This is a catch all error message. It usually

means an uncorrectible problem

[chars] [dec] [chars] [dec] [chars]\n

Internal error. MLIB debug library

initilization failed

[chars] [dec] [chars] [dec] [chars]\n

Internal non-serious error. MLIB debug

library termination failed

Number of multicast routes has crossed

[dec] hardware limit. Please delete some
routes immediately to prevent new routes
being blocked

MFIB on the node has detected the number

of multicast routes has exceeded the
prescribed limits. Any further routes
increase could cause MFIB to block the
routes from being programmed in
hardware.

MFIB has unblocked the multicast route

update to hardware. Please ensure
multicast routes are not crossed the
hardware limit

MFIB has unblocked the multicast route

update to hardware. The node had
detected the number of multicast routes
exceeded the prescribed limits and route
update to hardwared had been blocked.
The situation has been cleared, hence
mulitcast route update has been
unblocked.

Number of multicast routes has exceeded

the hardware limits and new routes are
now blocked. Please delete routes
immediately to recover

MFIB on the node has detected the number

of multicast routes has exceeded the
prescribed limits and new routes have been
blocked.

im_caps_datapath_control error in function

[chars] : [chars]
Internal error.

Delete Failed for ([chars] [chars]/[dec])

from [chars] table [chars]\n

Internal error. Deleting an entry from

ingress or egress failed

Cannot open event connection manager:

[chars]

Internal error.

Cannot create event manager: [chars]

Internal error.

[chars] [chars]: [chars]

Error while doing shmwin operation

[chars] [chars]

Internal error.

[chars] [chars]

Error while enabling/disabling per route

accounting for a route

[chars] [chars]

Error while enabling/disabling per route

accounting for a route

[chars]

Error while enabling/disabling per route

accounting in a table

Cannot [chars] per prefix accounting for

table [chars]. [chars] [chars]

Error while enabling/disabling per route

accounting in a table

Cannot get ACL for [chars] [chars]: ([dec])

[chars]

Internal error.

Failed to register callback for acl [chars]:

([dec]) [chars]

Internal error

[chars]Invalid state - active grange in mrib

[chars]/[dec] RP - [chars]
Internal error.

Fatal AIPC error: - ([chars])

Internal error

PIM BGP communication [chars], [chars]

Internal error

Failed to create PIM context for vrf [chars]

Internal error.

[chars] [chars]

Internal error.

Ital init failed [dec]

Internal error.

[chars] : [chars]

Internal error.

[chars] : [chars]

Error in allocating memory.

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

Error sending async message to [chars]

thread during [chars] with pulse code
[dec]: error=[dec]([chars])

Internal error.

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

[chars]Invalid state for IM state registration

batch on [chars]
Internal error.

Failed to [chars]

Internal error.

Interface Manager error - [chars] [chars] :

[chars]

Error in adding CAPS

Interface Manager error - [chars] [chars] :

[chars]

Error while sending dpc message

[chars]Interface Manager error - [chars]

[chars] : [chars]

Error while creating an IM interface.

[chars]Interface Manager error - [chars]

[chars] : [chars]

Error while deleting an IM interface.

[chars]%s : [chars]

Error during initialization.

[chars]List error : [chars] : [chars]

Internal error.

ltrace_init failed for '[chars]': [chars]

Internal error

A software error has occurred while trying

[chars]RIB max path exceeded for [chars], to read out the checkpointed rpf data. PIM
total paths: [dec], reset to maximum
rpf info may be incorrect

[chars]for [chars] [chars]

Internal error.

[chars] : [chars]

Internal error.

[chars]%s : [chars]

Internal error.

[chars] : [chars]

Internal error.

MRIB connection error - [chars] : [chars]

Internal error

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

Error in bag decoding : [chars]

Internal error

Error in bag free : [chars]

Internal error

Error in datalist free : [chars]

Internal error

Error in datalist next : [chars]

Internal error

[chars] : [chars]

Internal error.

[chars] : [chars]

Internal error.

Received an invalid event from WDSysmon Internal error.

[chars]

Internal error.

[chars]Error - [chars] [chars]

A general error.

Interface handle mismatch, handle in IM

update [chars]:[hex], handle in PIM [chars]:
[hex]
Internal error

[chars]%s : [chars]

Internal error.

[chars]Interface [chars] belongs to VRF

contexts [chars] and [chars]. Same
interface cannot be configured under
multiple VRFs

Internal error

[chars]Interface Forward Reference Store

error - [chars]: [chars]

Internal error

[chars]Interface [chars] should not be

configured as mhost default

Internal error

[chars] : [chars]

Internal error.

[chars] [chars] multicast topology incorrect

sysdb deletes received, refcount [dec]
Internal error

[chars]%s multicast intact incorrect sysdb

deletes received, refcount [dec]

Internal error

[chars]%s : [chars]

Internal error. If the error is seen during

transient system state, for instance during
LC OIR, it is harmless and can be safely
ignored.

[chars]OOR [chars] counter has turned

negative: [dec]

Internal error.

Global BSR candidate-rp maximum

reached: [dec], new CRP-cache not added

OOR Error.

Global BSR group range maximum reached:

[dec], new group range not added
OOR Error.

This router has reached the maximum

value for the number of group ranges
allowed to be received through the given
group-to-RP mapping distribution
mechanism. This can cause an
The [chars] maximum number ([unsigned inconsistancy between routers in the PIM
int]) of group ranges received through the domain as to which RP a group maps. This
[chars] group-to-RP mapping distribution
inconsistancy can cause multicast traffic
mechanism has been reached. Group range loss for some or all multicast groups. Steps
creation is now throttled. Configure a
should be immediately taken to reduce the
higher '[chars]' value or take steps to
number of group ranges being distributed
reduce the number of [chars] distributed
by the given mechanism or to configure a
group-to-RP mapping ranges.
higher maximum value.

VRF: [chars] BSR candidate-rp maximum

reached: [dec], new CRP-cache not added

OOR Error.

[chars] BSR group range maximum

reached: [dec], new group range not added OOR Error.

[chars]%s - [chars] : [chars]

Internal error.

[chars]%s : [chars]

Internal error.

Error in [chars]

Internal error.

Invalid grange

Internal Error

Invalid vrf-id ([hex])

Invalid vrf-id received from pim/pim6

Data MDT core routes missing ([chars],

[chars])

Missing data MDT core routes

Could not allocate memory for message

header

Internal Error

[chars]%s

Internal error.

ITAL create notification for table with

pending cleanup old vrf_id [hex], table_id
[hex] : route count [dec] : new vrf_id [hex]
table_id [hex]
Internal error

[chars]Failed to [chars] [chars]

Internal error.

[chars]Failed operation: [chars] for [chars] [chars]

Internal error.

Received [chars] memory depletion

warning, stop creating new pim state

Internal error.

Node memory back to normal, new pim

states will be created

Internal error.

Global BSR candidate-rp range threshold

reached: [dec] CRP creation will soon be
throttled.

Internal error.

Global BSR group range threshold reached:

[dec] Group Range creation will soon be
throttled.
Internal error.

The [chars] number ([unsigned int]) of

group ranges received through the [chars]
group-to-RP mapping distribution
mechanism is now below the maximum
([unsigned int]). Normal group range
creation will now resume.

This router has fallen below the maximum

value for the number of group ranges
allowed to be received through the given
group-to-RP mapping distribution
mechanism.

This router has reached the threshold value

for the number of group ranges allowed to
The [chars] threshold number ([unsigned
be received through the given group-to-RP
int]) of group ranges received through the mapping distribution mechanism. This is a
[chars] group-to-RP mapping distribution
warning that the maximum value is being
mechanism has been reached. Group range approached and steps should be
creation will soon be throttled. Configure a immediately taken to reduce the number of
higher '[chars]' value or take steps to
group ranges being distributed by the
reduce the number of [chars] distributed
given mechanism or to configure a higher
group-to-RP mapping ranges.
maximum value.

[chars]The number of PIM Register states

([unsigned int]) is now below the
maximum. Normal PIM Register handling
will resume.

Internal error.

[chars]The threshold number of PIM

Register states ([unsigned int]) has been
reached. Register state creation will soon
be throttled. Configure a higher maximum
or take steps to reduce Register state.
Internal error.

[chars]The maximum number of PIM

Register states ([unsigned int]) has been
reached. Register state creation will be
throttled. Configure a higher maximum or
take steps to reduce Register state.

Internal error.

[chars]The number of PIM routes

([unsigned int]) and route-interfaces
([unsigned int]) are now below the
maximum. Normal PIM route handling will
resume.

Internal error.

[chars]The threshold number of PIM routes

([unsigned int]) or route-interfaces
([unsigned int]) has been reached. Route
creation will soon be throttled. Configure a
higher maximum or take steps to reduce
multicast state.
Internal error.

[chars]The maximum number of PIM routes

([unsigned int]) or route-interfaces
([unsigned int]) has been reached. Route
creation will be throttled. Configure a
higher maximum or take steps to reduce
multicast state.
Internal error.

VRF: [chars] BSR candidate-rp range

threshold reached: [dec] CRP creation will
soon be throttled.

Internal error.

VRF: [chars] BSR group range threshold

reached: [dec] Group Range creation will
soon be throttled.

Internal error.

[chars]%s in [chars] : [chars]

Internal error.

RPF Redirect exhausted all member's

bandwidth: ([chars], [chars]) [chars] join
dropped

Internal error.

RPF Redirect bandwidth available on

[chars], ([chars], [chars]) [chars]

Internal error.

RPF Redirect bandwidth exhausted:

([chars], [chars]) join dropped on [chars]

Internal error.

RPF Redirect ([chars], [chars]) on [chars],

duplicate checkpoint playback.

Internal error.

RPF Redirect ([chars], [chars]) on [chars]

preempted by snooped ([chars], [chars])

Internal error.

RPF Redirect bandwidth exhausted:

([chars], [chars]) forwarded by [chars] on
[chars]

Internal error.

RPF Redirect bandwidth exceeding

threshold: ([chars], [chars]) on [chars] rpf
[chars] [[dec]:[dec]:[dec]:[dec]]

Internal error.

RPF Redirect bandwidth exceeding

threshold: ([chars], [chars]) on [chars]

Internal error.

RPF Redirect ([chars], [chars]) join on

[chars] rejected by upstream [chars]

Internal error.

TE Router ID [chars] Mismatch with MDT

source [chars], Please fix config

Internal error.

[chars]PIM interface [chars] [chars]

PIM interface state change message.

[chars]PIM invalid (*, [chars]) J/P message

from [chars] with RP address [chars]

PIM invalid J/P notification.

[chars]PIM invalid register message from

[chars] for group [chars] RP address
[chars], [chars]

PIM invalid register message notification.

[chars]PIM neighbor [chars] [chars] on

[chars] [chars]

PIM neighbor state change message.

[chars]PIM [chars] for [chars]/[dec] RP

[chars] proto [chars]

PIM RP mapping change notificaiton.

[dec] [chars] [chars]\n

Internal error. Cannot Register with CERR_V

subsystem

[chars] [dec] [chars]\n

Internal error. Static Mcast debug library

initilization failed

Cannot Initialize sigevent structure: [chars] Internal error.

Event Manager creation Failed: [chars]\n

Internal error. Failed while creating event

manager

Cannot initialize IDB list: [chars]

Internal error. Cannot create initialize IDB

list

Error [chars] [chars]

Internal error. Error while doing IM or IDB

stuff

[chars]: [chars]

Internal error. Error while doing MRIB API

[dec]: [chars] ([chars],[chars]/[dec])

Internal error.

Cannot obtain pulse code for the timer:

[chars]\n

Internal error.

Cannot create timer leaf: [chars]

Internal error. Cannot create manageed

timer leaf

Cannot create managed timer: [chars]

Internal error. Cannot create manageed

timer

Cannot create static topology

Internal error. Cannot create manageed

timer leaf

Rejecting RIB Update for [chars]/[dec]

status [dec]

Rejected a route update from the RIB.

PFI-IFH Server Error for [hex] status =

([dec])

Cannot talk to the PFI-IFH process

There was an internal error in the routing

Failed to build policy operation '[chars]' for policy library and as a result routing policy
attribute '[chars]'.[chars]%s ([hex])
may not be applied correctly.

The router with the system ID SYSTEM-ID

has transmitted too many LSPs in brief
Possible duplicate system ID [chars]
period of time, which could indicate
detected; Duplicate LSP received from host constant LSP reflooding caused by a
[chars], on interface [chars]
duplicate system ID.

IS-IS failed to create a session with the BFD

server. Creation will be reattempted on the
next received IIH. Depending on the
Can't create BFD session to [chars]: [chars] neighbor's support of BFD this may cause
([hex])
adjacencies to go down.

IS-IS failed to initialize one of its debug

services. The process cannot continue
without its debug services and so will have
aborted, but should have been restarted
rapidly afterwards. This message will have
been preceded by another one providing
more precise details of the failure. The
problem may be due to low memory
resources and the detail of the preceding
IS-IS failed to initialize its debug resources error message provides an indication of
and will abort
whether this is the case.

Error [chars]: [chars]: '[chars]', [hex]

An unexpected error occurred whilst

performing an atomic ring operation. This
may be due to resource starvation or an
internal programming error.

A packet which IS-IS has received from its

network socket contains a socket address
with an invalid length. This is an internal
error which indicates that the packet has
been corrupted after being received by the
local router but before being received by
IS-IS. The problematic packet has been
dropped. If this is an occassional problem
then IS-IS should be able to continue
Bad socket address length ([unsigned int], operating normally when the packet is
should be [unsigned int] or [unsigned int]) resent. If the message recurs, then IS-IS
in packet 0x[pointer]
may start to operate incorrectly.

Failed to encode data for [chars] for

external data manager (Reason: [chars])

A process has requested information

through SysDB, probably as the result of
executing a show command. An attempt to
encode data for this has failed.

Failed to register bag structures with bag

server (Reason: [chars])

The process could not register the data

structures used by IS-IS statistics and
management agents.

Error retrieving or setting the time of the

[chars] clock: [chars] ([hex])

An unexpected error occurred whilst

retrieving the time of a System Clock. This
may be due to resource starvation or an
internal programming error.

Error during communication of [chars]

information to TE processes: [chars]

IS-IS was unable to inform the TE processes

of its configuration or basic operational
state.

Failed to add an entry to an external data

manager data list for [chars] (Reason:
[chars])

A process has requested information

through SysDB, probably as the result of
executing a show command. The attempt
to add an item to an external data
manager datalist has failed.

Failed to create external data manager

data list for [chars] (Reason: [chars])

A process has requested information

through SysDB, probably as the result of
executing a show command. The creation
of the datalist to be returned has failed.

Failed to set the 'more data' flag on a

returned [chars] data list: error [hex]
([chars])

A process has requested information

through SysDB, probably as the result of
executing a show command. The attempt
to set the 'more data' flag to an external
data manager datalist has failed.

The IS-IS process failed to initialize the

handler functions for external data
[chars] management function initialization management. As a result, show and clear
failed: [hex], '[chars]'
commands will not function.

[chars] SysDB registration failed: [hex],

'[chars]'

The process could not register with SysDB

for management of the data used by IS-IS
statistics and management agents. As a
result, show and clear commands will not
function.

Failed system manager call to get IS-IS

job_id: [hex], '[chars]'

IS-IS failed on a call to system manager to

get its job_id. It's an internal fatal error. ISIS process will abort.

IS-IS failed on a call to system manager to

get the node related state information. It's
Failed system manager call to get the node an internal fatal error. IS-IS process will
state information: [hex], '[chars]'
abort.

Failed system manager call to retrieve the

process tag name: [hex], '[chars]'

IS-IS failed on a call to system manager to

retrieve its tag name during process
initialization. It's an internal fatal error. IS-IS
process will abort.

Error [chars]: '[chars]', [hex]

An unexpected error occurred whilst

performing an SNMP ifindex operation. This
may be due to resource starvation or an
internal programming error.

Failed to add an entry to an external data

manager list for [chars] (Reason: [chars])

A process has requested information

through SysDB, probably as the result of
executing a show command. The attempt
to add an item to an external data
manager list has failed.

A process has requested information

through SysDB, probably as the result of
Failed to create external data manager list executing a show command. The creation
for [chars] (Reason: [chars])
of the list to be returned has failed.

An unxpected error occurred whilst trying

Unexpected error '[chars]' trying to [chars] to lock or unlock an IS-IS resource. This
the [chars]
implies an internal programming error.

Error [chars] trace buffer '[chars]': [chars]

([hex])

An unexpected error occurred whilst

accessing a tracing buffer. This may be due
to resource starvation or an internal
programming error.

Failed to create the [chars]

IS-IS failed to create a memory pool. IS-IS

cannot operate without this resource and
will abort. The most likely cause is a low
memory condition.

Failed to register with system manager to

get node state change notification: [hex],
'[chars]'

IS-IS failed on a call to system manager to

register to get node state change
notification. It's an internal fatal error. IS-IS
process will abort.

Error [chars] a packet buffer (0x[pointer]):

[chars]

IS-IS encountered an error whilst accessing

a packet buffer. The relevant packet has
been ignored. The message describes the
nature of the error. If the problem is
transient then IS-IS will recover. The error
may be due to a low memory condition.

Error [chars] the managed connection to

the packet server: [chars] ([dec])

IS-IS encountered an error whilst trying to

set up a managed connection to the Packet
Server. This is a serious error as IS-IS
requires Packet I/O services to be able to
form adjacencies, and the IS-IS process will
shut itself down in response. This may be
due to a low memory condition but is more
likely to be a programming error. The error
string and error code provide more
information about the cause.

Error obtaining a packet buffer of length

%zu

IS-IS encountered an error whilst

attempting to acquire a packet buffer to
use to send a packet. The relevant packet
has been dropped. The problem may be
due to resource starvation. IS-IS will
recover when sufficient resources become
available.

IS-IS failed on a call to system manager to

indicate that it has completed all its
Failed system manager call to indicate that initialization and is now completely online.
IS-IS has completed initialization: [hex],
It's an internal fatal error. IS-IS process will
'[chars]'
abort.

IS-IS failed on a call to system manager to

Failed system manager call to indicate that indicate that it's ready to proceed. It's an
IS-IS is ready: [hex], '[chars]'
internal fatal error. IS-IS process will abort.

Received [chars] in the [chars] message

from TE

The process has received a TE message

with invalid contents. As a result, the TE
message is ignored and TE tunnel may not
come up.

Error receiving packet: [chars]

An internal error has occurred receiving the

packet. This is most likely due to some
failure in a system service or a limited
resource being exhausted.

Unexpected error [chars] batch of [chars]

RIB updates ([dec])

IS-IS encountered an unexpected error

whilst defining a batch of updates to be
sent to the RIB. This is an internal
programming error.

Unexpected error installing a path to

[chars] in the [chars] RIB ([dec])

IS-IS was unable to install a path to the

specified network in the the specified RIB
because the RIB rejected the request. This
is an internal programming error.

Error sending IS-IS packet: [chars]

The process encountered an error while

sending the IS-IS packet.

Error [chars] [chars] SysDB item ([chars]):

[hex], '[chars]'

An unexpected error occurred whilst

accessing the specified SysDB item. This
may be due to resource starvation or an
internal programming error.

Error in SysDB batch: [chars]: [chars]

([hex])

An unexpected error occurred whilst

checking for more SysDB batches after
receiving request to shutdown the process.
This may be due to resource starvation or
an internal programming error.

[chars] SysDB connection could not be

established at the path [chars]: [hex],
'[chars]'

IS-IS failed to bind to SysDB while opening

a connection to it.

Error [chars] SysDB datalist containing

[chars]: [chars] ([hex])

An unexpected error occurred whilst listing

the contents of a directory in SysDB. This
may be due to resource starvation or an
internal programming error.

Failed to register for SysDB notifications on IS-IS failed to register for notification of
path [chars] ([chars])
changes on the displayed SysDB path.

Failed to [chars] ([chars])

IS-IS failed to register for verification of

changes to its configuration data.

Error [chars] a '[chars]' string: [hex],

'[chars]'

IS-IS failed to encode or decode a string

using the SysDB encoding. Aa result IS-IS
will not be able to complete the operation
it was performing which it encountered the
error. The message describes the string
which was being encoded or decoded and
this should indicate the nature of the
operation which was being performed.

Error retrieving process tag name: [hex],

'[chars]'

An IS-IS process failed to retrieve its

process tag name during process
initialization. This is a fatal error and the ISIS process will abort.

Error starting [chars] thread: [dec]

IS-IS failed to create a thread essential to

its operation. This is an internal error. It
requires a restart of the process for
recovery.

Error creating '[chars]' registry for thread

specific value: [chars]

IS-IS failed to create a key to store thread

specific values such as the name of a
thread. This may be due to a low memory
condition but is most likely to be an
internal programming error.

IS-IS failed to initialize the specified

Error performing a once per thread lifetime resource. This is an internal programming
operation to initialize [chars]: [chars]
error.

Error associating [chars] with thread:

[chars]

IS-IS failed to associated the specified perthread resource with the thread. This may
be due to a low memory condition but is
most likely to be an internal programming
error.

[chars] verification function initialization

failed: [hex], '[chars]'

The IS-IS process failed to initialize the

handler functions for verification of
changes to its configuration data.

Error creating '[chars]' connection: [chars]

IS-IS failed to create a connection to an

essential service during initialization. This
is an internal error. It requires a restart of
the process for recovery.

Failed to remove [chars] from the [chars]

queue: [hex], '[chars]'

An unexpected error occurred whilst

removing the specified object from the
specified queue.

Failed to enqueue [chars] on the [chars]

queue: [hex], '[chars]'

An unexpected error occurred while

enqueueing the specified object on the
specified queue.

Failed to retrieve the size of the [chars]

queue: [hex], '[chars]'

An unexpected error occurred whilst

retrieving the size of the specified queue.
As a result IS-IS's internal state may be
inconsistent. This indicates an internal
programming error.

Failed to register handler for IM [chars]

events: [hex], '[chars]'

IS-IS failed to register a handler for IM

events relating to the specified protocol.
This may be due to a low-memory
condition but may also be due to internal
programming error.

Unexpected error retrieving connection ID

from IMD connection context: [hex],
'[chars]'

IS-IS failed to retrieve a connection ID from

the IMD connection context. This may be
due to a low-memory condition.

Failed to add [chars] to the set of [chars]:

[hex], '[chars]'

An unexpected error occurred whilst trying

to add an interface to the specified
collection of interfaces. This is most likely
to be due to a low memory condition, but
may be an internal programming error.

Error [chars] IPv6 local address consumer

service: [hex], '[chars]'

An unexpected error occurred whilst IS-IS

was using the IPv6 Local Address Consumer
Service.

The IS-IS process failed to configure linkLink-group add [chars] failed on '[chars]', rc group on the interface with specified error
[hex], [chars]
reason.

Link-group verification error [chars]: [chars] An unexpected error occurred while

[dec] [chars] [dec]
verifying link-group configuraton.
The process was unable to add information
Unable to [chars] due to insufficient space to an outgoing PDU. This is most likely an
in outgoing PDU
MTU issue.

RSI [chars] failure, [hex], '[chars]'

The IS-IS process failed to initialize the RSI

service for the specified error reason.

RSI init failure, [hex], '[chars]'

The IS-IS process failed to initialize the RSI

service for the specified error reason.

Unexpected Error in releasing snmp index: An unexpected error occurred while

expected idb:[pointer] got *idb_elem:
releasing an SNMP index. This may be due
[pointer]
to an internal programming error.

Operation '[chars]' failed during packet

timestamping: [hex] ([chars])

An operation failed during timestamp

processing.

An operation failed during log trigger

Operation '[chars]' failed during log trigger processing. This is not critical and IS-IS
processing : [chars]
functionality should be unaffected.

Too many IS-IS areas--cannot route to area

AREA-ADDRESS. This system has exceeded
the limit of three learned area addresses.
Too many IS-IS areas--cannot route to area The largest address AREA-ADDRESS has
[chars]
been dropped from the list of active areas.

Attempt to connect to the BFD server

failed: [chars] ([hex])

IS-IS failed to connect to the BFD server.

The connection will be retried.

IS-IS failed to create one or more sessions

with the BFD server. The connection to the
Attempt to create [dec] BFD session[chars] server will be reset in an attempt to
failed: [chars] ([hex])
recover from the error.

IS-IS failed to delete one or more sessions

with the BFD server. The connection to the
Attempt to delete [dec] BFD session[chars] server will be reset in an attempt to
failed: [chars] ([hex])
recover from the error.

IS-IS failed to admin shutdown one or more

Attempt to admin shutdown [unsigned int] sessions with the BFD server. The
BFD session[chars] as a result of
connection to the server will be reset in an
deconfiguration failed: [chars] ([hex])
attempt to recover from the error.
IS-IS failed to locate a BFD session for a
Failed to locate BFD session over [chars] to given adjacency. If necessary IS-IS will
[chars] for an adjacency.
reconnect to the server to correct.

[chars]

This system was unable to register the

CERR DLL. This is probably due to a faulty
installation.

Error registering for IS-IS debug events:

[hex], '[chars]'

IS-IS failed to register with the debug

module for printing messages.

Level [unsigned int] LSP [chars] contains

multiple ([unsigned int]) MT capability
items for [chars].[chars]%s

The specified LSP contains multiple items

advertising the same MT capability. This is
an indication that the router which owns
the LSP has generated its LSP incorrectly. If
the MT capability items contain conflicting
overload state then the message indicates
this and IOS-XR determines that the router
which issued the LSP is overloaded. If the
MT capability items contain conflicting
attached state then the message indicates
this and IOS-XR determines that the router
which issued the LSP is not attached.

IS-IS encountered the specified unexpected

error whilst performing the specified
operation on the specified access-list. As a
result IS-IS's operation will not correctly
reflect the contents of the ACL. This may
Unexpected error whilst [chars] [chars] ACL be due to a low-memory condition but may
[chars]: [hex], '[chars]'
also be due to internal programming error.

Error adding IS-IS to advertising mask of

[chars] ([chars]): [hex], '[chars]'

IS-IS failed to add itself to the advertising

mask for the specified route and topology,
that route corresponding to a connected
route on an interface over which IS-IS is
running. This means that any protocols
which redistribute IS-IS into themselves will
not receive the specified route. The
problem is most likely to be caused by a
failure by ipv4-io or ipv6-io to install the
route at all, although it could also be due to
low memory conditions.

Bad circuit type ([dec]) from [chars]

Bad circuit type (CIRCUIT-TYPE) from

SOURCE_IF. This system received an IS-IS
hello with a header reporting an invalid
circuit type of CIRCUIT-TYPE. This is the
result of a mal-formed packet rather than a
configuration error. The packet has been
ignored.

Bad circuit type ([dec]) from [chars]

Bad circuit type (CIRCUIT-TYPE) from

SOURCE_IF. This system received an IS-IS
hello with a header reporting an invalid
circuit type of CIRCUIT-TYPE. This is the
result of a mal-formed packet rather than a
configuration error. The packet has been
ignored.

The packet header length (HDRLEN) is

invalid for a(n) PDUTYPE, (should be
EXPECTED) from SOURCE_IF This system
received a PDUTYPE packet from
The packet header length %zu is invalid for SOURCE_IF claiming a header length of
a(n) [chars], (should be [unsigned int])
ACTUAL, rather than EXPECTED. The packet
from [chars]
has been ignored.

The packet header length (HDRLEN) is

invalid for a(n) PDUTYPE, (should be
EXPECTED) from SOURCE_IF This system
received a PDUTYPE packet from
The packet header length %zu is invalid for SOURCE_IF claiming a header length of
a(n) [chars], (should be [unsigned int])
ACTUAL, rather than EXPECTED. The packet
from [chars]
has been ignored.

Bad system ID length (ID-LENGTH, should

be 0 or EXPECTED-LENGTH) from
SOURCE_IF. This system received a pdu
reporting an invalid system ID length of IDLENGTH. This system only accepts values
Bad system ID length ([unsigned int],
of 0 and 6 (both indicate 6). The packet has
should be 0 or [unsigned int]) from [chars] been ignored.

Bad system ID length (ID-LENGTH, should

be 0 or EXPECTED-LENGTH) from
SOURCE_IF. This system received a pdu
reporting an invalid system ID length of IDLENGTH. This system only accepts values
Bad system ID length ([unsigned int],
of 0 and 6 (both indicate 6). The packet has
should be 0 or [unsigned int]) from [chars] been ignored.

Bad max area addresses ([dec], should be

0 or [dec]) from [chars]

Bad max area addresses (MAX-AREAADDRESSES, should be 0 or EXPECTEDMAX) from SNPA (INTERFACE-NAME). This
system received a pdu reporting an invalid
number of configurable area addresses.
This system only accepts values of 0 and 3
(both indicate 3). The packet has been
ignored.

Bad max area addresses ([dec], should be

0 or [dec]) from [chars]

Bad max area addresses (MAX-AREAADDRESSES, should be 0 or EXPECTEDMAX) from SNPA (INTERFACE-NAME). This
system received a pdu reporting an invalid
number of configurable area addresses.
This system only accepts values of 0 and 3
(both indicate 3). The packet has been
ignored.

The length (%zu) reported in the packet

buffer is greater than the maximum packet IS-IS has received a packet which is larger
length that IS-IS can receive ([unsigned
than its internal buffers can handle. The
int])
packet has been ignored.

[chars] received from [chars] contains a

format error: [chars]

IS-IS has received a PDU containing a

format error. This indicates that the system
which built the PDU is not conforming to
the protocol specification. In most cases
this is the neighbor, but in the case of LSPs
it is the system which generated the LSP.
The message contains the type of the PDU,
the interface it was received over (and, in
the case of a LAN interface, the SNPA), and
a description of the format error. IS-IS will
not use any of the information contained in
this PDU. In the case of an LSP, IS-IS will
not flood the LSP to neighbors.

[chars] received from [chars] contains a

format error: [chars]

IS-IS has received a PDU containing a

format error. This indicates that the system
which built the PDU is not conforming to
the protocol specification. In most cases
this is the neighbor, but in the case of LSPs
it is the system which generated the LSP.
The message contains the type of the PDU,
the interface it was received over (and, in
the case of a LAN interface, the SNPA), and
a description of the format error. IS-IS will
not use any of the information contained in
this PDU. In the case of an LSP, IS-IS will
not flood the LSP to neighbors.

The length (%zu) reported in the [chars]

header is greater than the packet length
([unsigned int]) from [chars]

The length (PDU_LENGTH) reported in the

PDUTYPE header is greater than packet
length (PKTLEN) from SOURCE_IF This
system received an IS-IS packet that was
LENGTH bytes long, which is shorter than
the required header length for a PDUTYPE
packet. The packet has been ignored.

The length (%zu) reported in the [chars]

header is greater than the packet length
([unsigned int]) from [chars]

The length (PDU_LENGTH) reported in the

PDUTYPE header is greater than packet
length (PKTLEN) from SOURCE_IF This
system received an IS-IS packet that was
LENGTH bytes long, which is shorter than
the required header length for a PDUTYPE
packet. The packet has been ignored.

The PDU version reported in the IS-IS

header is invalid (VERSION, should be
EXPECTED) from SNPA (INTERFACE-NAME)
This system received a protocol packet
bearing an invalid VERSION in the header.
The router originating the packet is either
The PDU version reported in the IS-IS
placing the wrong protocol version number
header is invalid ([unsigned int], should be in the packet, or else it is running an
[unsigned int]) from [chars]
incompatible version of the IS-IS protocol.

The PDU version reported in the IS-IS

header is invalid (VERSION, should be
EXPECTED) from SNPA (INTERFACE-NAME)
This system received a protocol packet
bearing an invalid VERSION in the header.
The router originating the packet is either
The PDU version reported in the IS-IS
placing the wrong protocol version number
header is invalid ([unsigned int], should be in the packet, or else it is running an
[unsigned int]) from [chars]
incompatible version of the IS-IS protocol.

Bad protocol version ([dec], should be

[dec]) from [chars]

Bad protocol version (VERSION, should be

EXPECTED-VERSION) from SOURCE_IF. This
system received a pdu with an invalid
protocol version of VERSION instead of
EXPECTED-VERSION. The packet has been
ignored.

Bad protocol version ([dec], should be

[dec]) from [chars]

Bad protocol version (VERSION, should be

EXPECTED-VERSION) from SOURCE_IF. This
system received a pdu with an invalid
protocol version of VERSION instead of
EXPECTED-VERSION. The packet has been
ignored.

Overload bit not set due to failure in

registering for BGP convergence: [hex],
'[chars]'

IS-IS is configured to set the overload bit in

its LSPs upon startup and to wait for BGP to
converge before resetting the overload bit,
but an error has occurred whilst registering
for notification of BGP convergence. As a
result, the overload bit will not have been
set upon startup. This may be due to a lowmemory condition but may also be due to
internal programming error.

Error unregistering for BGP convergence

notification: [hex], '[chars]'

IS-IS failed to unregister for notification of

BGP convergence. The error will not affect
IS-IS operation but does indicate
unexpected system behavior.

Failed to register a handler for '[chars]'

messages: [chars]

IS-IS failed to register a handler for the

specified class of event. This is an
initialization error and implies that IS-IS will
not be able to operate correctly. The IS-IS
process must be restarted in order to
recover. The cause may be a resource
starvation problem but is most likely to be
an internal programming error. The error
message should give more details.

Failed to register a [chars] callback

handler: [chars]

IS-IS failed to register a callback handler

due to the error. This is an initialization
error and implies that the function in IS-IS
will not be able to operate correctly. The ISIS process must be restarted in order to
recover.

Failed to create [chars] Event Manager:

[chars]

IS-IS failed to create an Event Manager to

receive events in the specified thread. This
is most likely to be caused by a resource
starvation problem, but may also be due to
an internal programming error.

Failed to send '[chars]' to '[chars]': [chars]

IS-IS failed to send the specified message.

The cause may be a resource starvation
problem but is most likely to be an internal
programming error. The error message
should give more details.

Failed system manager call to fetch

respawn, assuming respawned: [hex],
'[chars]'

A call to system manager to obtain the

process respawn count failed. This is a
recoverable error, and the count will be
assumed to be 1.

L[unsigned int] LSP database checksum

verification failed for LSP [chars]. IS-IS will
restart itself

A corrupt LSP was found during a periodic

check of the sanity of the specified level's
LSP database. When it encounters this
condition the IS-IS process restarts itself to
recover.

L[unsigned int] LSP database checksum

verification failed for LSP [chars]. IS-IS will
restart itself

A corrupt LSP was found during a periodic

check of the sanity of the specified level's
LSP database. When it encounters this
condition the IS-IS process restarts itself to
recover.

LSP input queue overflow: [unsigned int]

total drops; [unsigned int] LSP drops,
[unsigned int] SNP drops

An incoming LSP or SNP pdu was dropped

because the input queue was full

Failed to allocate [unsigned int] bytes from IS-IS failed to allocate memory from the
'[chars]'
specified pool.

The length (%zu) described in the [chars]

header is smaller than the minimum
([unsigned int]) from [chars]

The length (PDU_LENGTH) described in the

PDUTYPE header is smaller than the
minimum (MINLEN) from SOURCE_IF This
system received an IS-IS packet that was
LENGTH bytes long, which is shorter than
the required header length for a PDUTYPE
packet. The packet has been ignored.

The length (%zu) described in the [chars]

header is smaller than the minimum
([unsigned int]) from [chars]

The length (PDU_LENGTH) described in the

PDUTYPE header is smaller than the
minimum (MINLEN) from SOURCE_IF This
system received an IS-IS packet that was
LENGTH bytes long, which is shorter than
the required header length for a PDUTYPE
packet. The packet has been ignored.

The length (%zu) of the [chars] received

from [chars] is smaller than the minimum
([unsigned int])

The length (PKTLEN) of the PDUTYPE

received from the interface SOURCE is
smaller than the minimum (MINLEN) This
system received an IS-IS packet that was
LENGTH bytes long, which is shorter than
the required header length for a PDUTYPE
packet. The packet has been ignored.

The length (%zu) of the [chars] received

from [chars] is smaller than the minimum
([unsigned int])

The length (PKTLEN) of the PDUTYPE

received from the interface SOURCE is
smaller than the minimum (MINLEN) This
system received an IS-IS packet that was
LENGTH bytes long, which is shorter than
the required header length for a PDUTYPE
packet. The packet has been ignored.

Error changing a local message channel

setting to [chars]: [chars] ([dec])

IS-IS failed to convert a local connection

channel to a global connection channel.
This could be the result of a problem with
the channel.

IS-IS failed to retrieve its local connection

ID for a client attached to the specified
Error retrieving client's connection ID to the channel. This is an internal programming
[chars] channel: [chars] ([dec])
error.

Error replying to the client [chars]: [chars]

([dec])

IS-IS failed to reply to its client through

message channel. This could be a result of
channel down or resource allocation failure.

Unexpected error whilst [chars]: [hex],

'[chars]'

IS-IS encountered an unexpected error

whilst performing the specified using the
Route Policy client library. As a result
information may be omitted from the local
system's LSPs. This may be due to a lowmemory condition.

Failed system manager call to register for

shutdown notification: [hex], '[chars]'

A call to system manager to register for

shutdown notification failed. This is a
recoverable error in that shutdown actions
are not critical.

IS-IS encountered an unexpected error

whilst performing the specified RIB
operation. This may be a resource
Unexpected error whilst [chars] the [chars] starvation problem but is most likely to be
RIB: [hex], '[chars]'
an internal programming error.

Unexpected error sending a batch of

[chars] RIB updates ([dec])

IS-IS encountered an unexpected error

whilst sending a batch of RIB updates to
the RIB. This may be a resource starvation
problem, or a problem with IS-IS's
connection to the RIB, or an internal
programming error.

Error setting the RIB linear retry period:

[hex] '[chars]'

IS-IS failed to set the linear retry period for

connecting to the RIB. This error will not
affect IS-IS operation but does indicate an
unexpected result.

Unexpected error whilst [chars]: [hex],

'[chars]'

IS-IS encountered an unexpected error

whilst performing the specified operation
using the RIB client library. This may be a
resource starvation problem but is most
likely to be an internal programming error.

Received an unexpected notification with

code [unsigned int]

IS-IS received an unexpected RIB

notification pulse and will ignore it.

IS-IS was unable to install a path to the

Insufficient memory whilst installing a path specified network in the RIB because the
to [chars] in the [chars] RIB
RIB encountered a low memory condition.

IS-IS failed to register for notification of

changes on the displayed SysDB path. The
Error registering show protocol information: error will not affect IS-IS operation but does
[hex], '[chars]'
indicate unexpected system behavior.

Error disconnecting [chars] SysDB

connection: [hex], '[chars]'

IS-IS failed to disconnect from SysDB. The

error will not affect IS-IS operation but does
indicate that a programming error has
occurred.

Error unregistering for SysDB notification:

[hex], '[chars]'

IS-IS failed to unregister for notification of

changes on the displayed SysDB path. The
error will not affect IS-IS operation but does
indicate unexpected system behavior.

Error destroying [chars] thread: [dec]

IS-IS failed to destroy a thread. This is an

internal error. If the error occurred whilst
unconfiguring IS-IS then it may be
necessary to forcefully terminate the IS-IS
process. If the error occurred during normal
operation then it may be necessary to
restart the IS-IS process to recover.

Error setting name of thread [dec] to

[chars]: [chars] ([hex])

An unexpected error occurred whilst setting

a thread name. This may be due to
resource starvation or an internal
programming error. This is not a fatal error
as the name is only used for debugging
and error messages.

IS-IS encountered an error whilst

registering or deregistering with
WDSysMon for notifications of changes to
the router's memory state. If the error
occurs during registration (i.e. when the ISIS process is initializing) then it will abort
and the system may recover automatically
when the IS-IS process is restarted. If the
error occurs during deregistration (i.e.
Unexpected error whilst [chars] for memory when the IS-IS process is shutting down)
state changes: [chars] ([hex])
then it is harmless and may be ignored.

Error [chars] the '[chars]' trigger: [hex],

'[chars]'

IS-IS encountered an unexpected error

using one of the infrastructure libraries.
This may be due to a low memory
condition but is more likely to be a
programming error. The error message
should provide more information about the
cause.

After detecting an error with the connection

to the specified service, IS-IS failed to reset
that connection. This is an internal error. It
requires a restart of the process for
Error resetting '[chars]' connection: [chars] recovery.

Error registering for data events on

'[chars]' connection: [chars]

During initialization, IS-IS failed to register

for input or output notifications for the
specified service. This is an internal error. It
requires a restart of the process for
recovery.

IS-IS failed to retrieve the file descriptor

Error retrieving the Connection ID from the associated with the specified service. This
'[chars]' connection: [chars]
is an internal error.

Error registering for critical events on

'[chars]' connection: [chars]

During initialization, IS-IS failed to register

for essential notifications regarding the
state of the connection for the specified
service. This is an internal error. It requires
a restart of the process for recovery.

Error opening '[chars]' connection: [chars]

IS-IS failed to open a connection to an

essential service during initialization. This
is an internal error. It requires a restart of
the process for recovery.

Failed to create the [chars] event queue:

[hex], '[chars]'

An unexpected error occured whilst

creating an event queue during process
initialization. This may be a system
resource problem. As a result IS-IS will be
unable to operate correctly.

Area address TLV length [dec] contains

more than ISIS_MAX_AREA_ADDRESSES
from [chars] ([chars]).

Area address TLV length TLV_LENGTH

contains more than
ISIS_MAX_AREA_ADDRESSES from
SNPA_STRING (INTERFACE_NAME). This
system recieved a hello or LSP containing
more than the maximum number of area
addresses. The additional addresses have
been ignored.

This is not critical and IS-IS functionality

Unexpected objid [hex] for [chars]
should be unaffected. A non-null OBJID for
(CSCek33169) collect log and tech-support INTERFACE-NAME was encountered.

The specified interface has more addresses

than can be fitted into a single TLV (255
bytes). RFC 1195 specifies that each IIH
may contain at most one IPv4 Interface
Address TLV, i.e. 63 IPv4 addresses. Thus if
there are more than 63 IPv4 addresses
configured on the interface then only 63
addresses are included in the IIH. If the
interface has a primary address it is always
included first. The secondary addresses are
added in their natural numerical order until
there is no more space. If there is an IS on
the LAN which does not share a subnet
with any of the advertised addresses then
[chars] has more [chars] interface
it will not be able to form an adjacency
addresses than can fit into a single TLV
with this IS. This problem should not apply
(255 bytes). Outgoing IIHs can only include to IPv6 as each interface should have a
the first [unsigned int] addresses.
single link local address.

Error initializing the IM attribute library:

[hex] '[chars]''

IS-IS failed to initialize the IM attribute

library. This error will prevent IS-IS from
normal operations.

IM notification received for an unknown

and unexpected capsulation number:
[unsigned int]

IS-IS has received an IM message referring

to a capsulation number that IS-IS does not
recognized and is not able to handle. This
is an internal programming error.

The length of the context string used to

register for Interface Manager callbacks
exceeded internal limits and was
truncated. If truncation results in
Interface Manager context name '[chars]' registration contexts no longer being
length exceeds string length limit of [dec]; unique, this could cause problems with
truncated to '[chars]'
event registrations.

Error during registration for interface IP

address changes: [chars]

IS-IS failed to register for notification of

interface IP address changes. This is may
be due to lack of resources or an internal
error (the error message will indicate
which). It requires a restart of the process
for recovery.

Failure while [chars] on [chars]: [hex]

'[chars]''

A call to the IM attribute library failed. This

can be caused by faulty hardware, or it
may indicate an interface resource is
currently unavailable. Recovery may
require a restart of the IS-IS process.

Failed to allocate circuit ID to interface

[chars]: all [dec] IDs already in use

IS-IS failed to allocate a circuit ID to the

specified LAN interface.

IS-IS failed to initialize its interface

Failed to initialize CLNS interface registery: registration process wth CLNS It requires a
[chars]
restart of process for recovery.

Failed to [chars] LPTS entry for interface

[chars]: [chars]

IS-IS failed to create or remove LPTS entry

on the specified interface. It may require a
restart of process for recovery.

Failed to notify CLNS of a MAC address

change on interface [chars]: [chars]

IS-IS failed to notify the CLNS protocol

stack of MAC address changes to the
specified interface. It requires a restart of
process for recovery.

Interface [chars] is already configured

This is a duplicate configuration received

for the same interface. Most likely the
previous cleanup (commit replace) or
removal of ISIS config was not successful
(CSCsy26037/CSCsv89872). ISIS may be in
unstable state.

Failed to lookup Interface Handle for

interface [chars]: [hex] '[chars]'

An unexpected error occurred looking up

an interface handle from an interface
name. This may be due to a low memory
condition but is most likely to be an
internal programming error.

Error during initialization of forwardreferenced interface store: [chars]

IS-IS failed to initialize its storage for

forward-referenced interfaces. This is may
be due to lack of resources or an internal
error (the error message will indicate
which). It requires a restart of the process
for recovery.

Registering for [chars] [chars] changes on

interface [chars] failed, will retry it: [hex],
'[chars]'

IS-IS failed to register for notification of the

specified changes on the specified
interface and protocol. This may happen in
case of ifmgr not ready to process the
request. For example ifmgr restart. This
may be an internal programming error, but
is most likely to be a resource starvation
problem.

Unexpected [chars] [chars] notification on

[chars]

The specified event was unexpected

because the address family is not active on
that interface. The operation of IS-IS is not
affected by this message and it may safely
be ignored. The message is due to an
internal programming error.

Error [chars] for [chars] address changes

on interface [chars]: [hex], '[chars]'

IS-IS failed to register with IP-ARM for

notification of the address changes on the
specified interface and address family. This
may be an internal commuincation error,
but is most likely to be a resource
starvation problem.

Failed [chars] [chars] link local addresses

on [chars]: [hex], '[chars]'

An unexpected error occurred whilst

accessing the link-local address details for
the specified interface. As a result IS-IS will
not be able to use the specified addressfamily on the specified interface. This could
be due to a low memory condition or an
internal programming error.

Incorrect MAC address size for [chars]

(returned: [dec], expected: [dec])

The MAC address size returned for the

specified interface does not match the
expected size (6 bytes). This can be caused
by a faulty hardware.

Joining [chars] multicast group on [chars]

failed: [chars], ISIS will retry again

IS-IS was unable to join the specified

multicast group on the specified interface,
Will retry again.

The multicast address is too large for

[chars] (supplied: [dec], maximum: [dec])

The multicast address requested for the

specified interface is larger than the
maximum permissible size. This requires
restarting the IS-IS process.

The IS-IS MTU was adjusted to

accommodate the fabric MTU of the
IS-IS MTU value of [unsigned int] on [chars] system. This new MTU may be smaller than
adjusted to [unsigned int] to accommodate the actual MTU allowable by the physical
fabric MTU
interface.

CLNS MTU value of [unsigned int] on

[chars] is too small. Minimum acceptable
value is [unsigned int]

The MTU for CLNS on the specified

interface is too small to allow IS-IS to send
packets over that interface. This may be
due to a configuration error or an internal
error.

An unexpected error occurred looking up

an interface's name from it's handle. The
error code should provide an indication of
what the problem is. The most likely
explanation is that the interface with the
specified handle no longer exists although
the message may be caused by low
Failed to lookup an interface name from its memory conditions or an internal
handle ([hex]): [hex], '[chars]'
programming error.

IS-IS has detected a mismatch between the

media class (i.e. Point to Point vs. LAN) of
an interface as determined by IS-IS's
checkpoint state and IM. As a result the
Media class mismatch between checkpoint interface will not participate in the NSF
table ([chars]) and reality ([chars]) on
restart. This is an internal programming
interface [chars]
error.

Protect infra [chars] failed for interface

[chars]: [hex], '[chars]'

IS-IS failed to register or unregister with

protect infrastructure for high priority linkdown notifications on the specified
interface. IS-IS will still react to regular linkdown events.

RSI SRLG [chars] failed for interface

[chars]: [hex], '[chars]'

IS-IS failed to register or unregister with RSI

for SRLG notifications on the specified
interface. IS-IS will reset RSI connection
and retry.

IS-IS was unable to perform the specified

operation on the specified interface. This is
most likely to be a resource starvation
Error [chars] [chars] [chars] internal [chars] problem, but may be an internal
store: [hex], [chars]
programming error.

Unknown or unsupported interface media

type ([chars]) on [chars]

This interface media is not supported by ISIS. An IS-IS process restart is required for
recovery.

IS-IS received invalid value for the

L[unsigned int] LSP [chars] sn [hex] cs
remaining LSP life time using the timer
[hex] has invalid remaining life time
library. IS-IS will handle this gracefully by
[unsigned int], max allowed - [unsigned int] limiting the value to maximum allowed.

IS-IS received invalid value for the

L[unsigned int] LSP [chars] sn [hex] cs
remaining LSP life time using the timer
[hex] has invalid remaining life time
library. IS-IS will handle this gracefully by
[unsigned int], max allowed - [unsigned int] limiting the value to maximum allowed.

Failed to [chars] for [chars] address

information: [hex], '[chars]'

IS-IS has encountered an error whilst

manipulating a set of interface IP
addresses. This may be a resource
starvation problem or an internal
programming error.

add_item_entry called with size [dec]:

errant entry was not added to the LSP

add_item_entry called with size SIZE. An

internal error occurred while this system
was trying to construct its LSPs. The errant
entry was not added to the LSP.

add_item_entry called with size [dec]:

errant entry was not added to the LSP

add_item_entry called with size SIZE. An

internal error occurred while this system
was trying to construct its LSPs. The errant
entry was not added to the LSP.

Failure to deactivate Key Chain [chars]:

'[chars]''

A call to the Key Chain library failed. This

may indicate an internal error.

The specified LSP contains a link

advertisement to itself and this link has
been ignored. There is no possible impact
to routing as the link would not be used by
other routers in their calculations. This
Level [unsigned int] LSP [chars] contains a message is however indicative of a
link advertsisement to itself ([chars] MT
problem in the router which issued the LSP
ID). This link will be ignored in subsequent as it should not have advertised such a
route calculations.
link.

Bad L-# LSP LSP-ID checksum ACTUALCKSUM received on INTERFACE-NAME,

length PDU-LENGTH should be EXPECTEDCKSUM, bad count CKSUM-ERROR-COUNT.
This system received a level L-# LSP with a
wrong checksum. If the IS-IS configuration
option 'isis-ignore-cksum-errors' is set, the
Bad L[dec] LSP [chars] checksum [hex]
packet has been ignored. Otherwise it has
received on [chars], length [dec], should be been handled according to the
[hex], bad count [dec]
specification.

Bad L-# LSP LSP-ID checksum ACTUALCKSUM received on INTERFACE-NAME,

length PDU-LENGTH should be EXPECTEDCKSUM, bad count CKSUM-ERROR-COUNT.
This system received a level L-# LSP with a
wrong checksum. If the IS-IS configuration
option 'isis-ignore-cksum-errors' is set, the
Bad L[dec] LSP [chars] checksum [hex]
packet has been ignored. Otherwise it has
received on [chars], length [dec], should be been handled according to the
[hex]
specification.

L[unsigned int] LSP filled to capacity,

dropping routes

L-LEVEL LSP filled to capacity, dropping

routes. This system cannot originate any
more routes or adjacencies because it
cannot build any more LSP fragments in
which to advertise them.

L[unsigned int] LSP filled to capacity,

dropping routes

L-LEVEL LSP filled to capacity, dropping

routes. This system cannot originate any
more routes or adjacencies because it
cannot build any more LSP fragments in
which to advertise them.

L[dec] LSP [chars] size [dec] bigger than

interface [chars] MTU [dec], LSP dropped

L-LEVEL LSP LSP-ID size LSP-LENGTH bigger

than interface INTERFACE-NAME MTU
INTERFACE-MTR, LSP dropped. This system
was unable to flood an LSP out INTERFACENAME because the interface MTU was too
small. The LSP has not been transmitted on
the interface.

L[dec] LSP [chars] size [dec] bigger than

interface [chars] MTU [dec], LSP dropped

L-LEVEL LSP LSP-ID size LSP-LENGTH bigger

than interface INTERFACE-NAME MTU
INTERFACE-MTR, LSP dropped. This system
was unable to flood an LSP out INTERFACENAME because the interface MTU was too
small. The LSP has not been transmitted on
the interface.

Level [unsigned int] LSP [chars] contains

an [chars] prefix advertsisement to the
invalid prefix [chars]. This prefix will be
ignored in subsequent route calculations.

The specified LSP contains a prefix

advertisement to an invalid martian prefix
and the prefix has been ignored. As the
prefix is invalid there should be no impact
to routing as no traffic should be destined
to the prefix. This message is however
indicative of a problem in the router which
issued the LSP as it should not have
advertised such a prefix.

This configuration is redistibuting more

than the allowable number of prefixes into
an IS-IS topology. IS-IS will not advertise
Topology [chars] level [unsigned int] is
some of these routes. This is to prevent
[chars]exceeding the maximum number of inadvertant redistribution of the Internet
redistributed prefixes
via IS-IS.

Failed to allocate %zu bytes for '[chars]'

The process failed to allocate memory for

the specified resource. This could be
because the IS-IS topology is too large for
the memory installed in the router.

Failed to allocate %zu bytes for '[chars]'

The process failed to allocate memory for

the specified resource. This could be
because the IS-IS topology is too large for
the memory installed in the router.

Error [chars] the [chars] [chars] timer:

[chars]

IS-IS encountered an unexpected error

using the Managed Timer library. This is
most likely to be due to a low memory
condition but may also be an internal
programming error. The error message
should provide more information about the
cause.

Failed to [chars] checkpoint record(s)

[chars] [chars] table: [hex], '[chars]'

An unexpected error occurred whilst IS-IS

was accessing entries in the specified
checkpoint table. If this error occurs during
an NSF Cisco restart then that NSF restart
may be aborted in favour of a traditional
restart. If this error occurs during normal
operation then the relevant checkpoint
table may not be correct, and a subsequent
NSF restart may not succeed. If however
the error does not recur then the
checkpoint tables should synchronize. The
error may be caused by a low memory
condition or through programming error.

NSF checkpoint init failure, [hex], '[chars]'

The IS-IS process failed to initialize the

checkpoint service for the specified error
reason.

Failed to [chars] [chars] checkpoint table:

[hex], '[chars]'

An unexpected error occurred whilst IS-IS

was accessing the specified checkpoint
table. If this error occurs during an NSF
Cisco restart then that NSF restart may be
aborted in favour of a traditional restart. If
this error occurs during normal operation
then the relevant checkpoint table may not
be correct, and a subsequent NSF restart
may not succeed. The error may be caused
by a low memory condition or through
programming error.

Failed to create L[unsigned int] NSF

adjacency to [chars] ([chars]) ([chars])

TBD.

Failed to restore L[unsigned int] TE tunnel

([hex]) to [chars] ([chars]) ([hex], [chars])

An unexpected error occured whilst

recreating TE tunnel from the checkpointed
information. NSF may abort.

Socket operation '[chars]' failed: [chars]

Failed to perform a socket operation.

L[unsigned int] [chars] configuration on

P2P interface [chars] will not be used

Any level specific configuration on a P2P

interface is ignored. The configuration may
be accepted but not used if the interface
type is unknown or changed later to pointto-point.

Error [chars] for redistribution of routes

from [chars] [chars] into IS-IS

The RIB returned an unexpected error

when IS-IS attempted to (de)register for
the redistribution of routes in the specified
topology and owned by the specified
protocol. If this is a registration error then
routes from the specified protocol may not
be advertised in IS-IS's system LSPs. If this
is a deregistration error then IS-IS may
receive unnecessary redistribution updates
from the RIB but the system LSPs will be
correctly generated. The problem may be
caused by a low memory condition but is
most likely to be an internal programming
error.

Attempt to register for a VRF failed: [chars] IS-IS failed to register for notification of
([hex])
changes to a VRF.

An LSP is received with a System ID same

as the local System ID but with a different
Received self originated LSP with system ID hostname. This could be happen in the
[chars], on interface [chars], differs in
following cases: 1) A new router is
hostname; Local hostname [chars],
introduced into the network with a
Received hostname [chars]. Please check if duplicate system ID as the local router. 2)
this host was connected inadvertently to
The local hostname has changed and isis is
the network or if the local hostname has
receiving an old LSP generated with the old
been changed.
hostname.

An LSP originated by this system has had

its sequence number wrap around to 0. The
IS-IS specification states that this system
should shutdown for 20 minutes waiting for
Sequence number wrapped in LSP [chars]. the LSP to age out before resuming routing.

An LSP originated by this system has had

its sequence number wrap around to 0. The
IS-IS specification states that this system
should shutdown for 20 minutes waiting for
Sequence number wrapped in LSP [chars]. the LSP to age out before resuming routing.

IS-IS encountered an error whilst

configuring the socket it uses for network
I/O. As a result the socket is unuseable and
Error setting the value of the '[chars]' IS-IS IS-IS cannot perform I/O. IS-IS will attempt
network socket option to '[chars]' (length
to recover by closing the current socket
[unsigned int]): [chars]
and schedule an attempt to reconnect.

Internal memory allocation failure, display

incomplete

The requested display output may be

incomplete due to an internal memory
allocation problem.

Process is shutting down ([chars]): [chars]

IS-IS has encountered a problem which

means that is no longer able to continue
and so it is shutting down. The message
includes a brief description of the problem
but will also have been preceded by
another message providing a more detailed
description of the problem. There are
several types of reason why IS-IS may have
to shutdown which include a fatal error
during process initialization, a fatal
problem with a critical service during
normal operation, and a roll-over of one of
the local system's LSP's sequence
numbers. The message also describes
whether or not IS-IS has automatically been
restarted.

L[dec] SNP size [dec] too big for interface

[chars] MTU [dec], trimmed to interface
MTU

L-LEVEL SNP size SNP-LENGTH bigger than

interface INTERFACE-NAME MTU
INTERFACE-MTR, trimmed to interface MTU
This system was unable to flood an SNP out
INTERFACE-NAME because the LSP MTU
setting is too big for the interface MTU. The
SNP packet size was trimmed to fit the
interface MTU.

L[dec] SNP size [dec] too big for interface

[chars] MTU [dec], trimmed to interface
MTU

L-LEVEL SNP size SNP-LENGTH bigger than

interface INTERFACE-NAME MTU
INTERFACE-MTR, trimmed to interface MTU
This system was unable to flood an SNP out
INTERFACE-NAME because the LSP MTU
setting is too big for the interface MTU. The
SNP packet size was trimmed to fit the
interface MTU.

Received a spurious pulse in thread [chars] IS-IS Recevied a spurious (unexpected)

(pulse value: [hex])
pulse value and will ignore it.

Error recording a timestamp ([dec])

An unexpected error occurred whilst

recording a timestamp. This implies an
internal programming error.

Unknown address family [unsigned int]

IS-IS has encountered an unrecognized

address family ID. This is an internal
programming error.

In the topology [chars] [chars] has a wide

metric of [unsigned int] but level
L[unsigned int] is configured to generate
narrow metrics. Maximum narrow value
[unsigned int] is used instead

The specified interface and topology has

been configured with a metric value that
requires metric-style wide to be configured
for the relevant level.

The specified LSP contains a link

advertisement with an invalid metric of 0.
Zero cost links have the potential to break
the SPF algorithm and are not permitted by
the IS-IS specification (ISO 10589 version
Level [unsigned int] LSP [chars] contains
2) and so the IOS-XR router will ignore the
an invalid link advertsisement to [chars]
link in any subsequent route calculations.
([chars] MT ID) with a metric of 0. This link As a result traffic which should be routed
will be ignored in subsequent route
via the affected routers may be dropped or
calculations.
enter a routing loop.

IIH zero holdtime from [chars]

IS-IS has received an IIH containing a zero

holdtime from a neighbor with which no
adjacency currently exists. The IIH has
been discarded. The message indicates the
interface and, in the case of a LAN
interface, the SNPA from which the IIH was
received.

IIH zero holdtime from [chars]

IS-IS has received an IIH containing a zero

holdtime from a neighbor with which no
adjacency currently exists. The IIH has
been discarded. The message indicates the
interface and, in the case of a LAN
interface, the SNPA from which the IIH was
received.

Adjacency to [chars] ([chars]) ([chars])

[chars], [chars]

Adjacency to SYSTEM-ID (INTERFACENAME) Up|Down, REASON. The adjacency

to the system with SYSTEM-ID has gone up
or down due to REASON.

Key Chain digest computation for [chars]

failed due to [chars]

The process encountered an error when

computing the authentication digest. This
may be due to misconfiguration on the
local or remote system. It is possible that
no currently valid keys are available.

The process encountered an error when

authenticating an incoming PDU and
dropped the PDU. This may be due to
misconfiguration on the local or remote
Dropped [chars] from [chars] due to [chars] system.

Key Chain digest verification for incoming

[chars] failed due to [chars]

The process encountered an error when

verifying the authentication digest. This
may be due to misconfiguration on the
local or remote system. It is possible that
no currently valid keys are available or the
remote system is using an invalid
authentication key.

[chars] L[unsigned int]: Neighbor [chars]

[chars]

The adjacency on the INTERFACE-NAME

and LEVEL with the system SYSTEM-ID
STARTED responding or STOPPED
responding during the NSF-restart of the
SYSTEM-ID.

[chars] queue is full.

The atomic ring for the indicated queue is

full.

Unknown debug filter tracepoint name

[chars]

An unknown tracepoint name requested for

a debug filter.

Duplicate System ID [chars] already used

by [chars] detected in IIH received on
[chars]

IS-IS has received an IIH from a router

claiming to have the same System ID as
either the local system or another station
on a LAN interface. The message indicates
the interface and, in the case of a LAN
interface, the SNPA from which the IIH was
received. It also indicates whether we
ourselves use this system ID, or the SNPA
of the other station using the system ID.

Duplicate System ID [chars] already used

by [chars] detected in IIH received on
[chars]

IS-IS has received an IIH from a router

claiming to have the same System ID as
either the local system or another station
on a LAN interface. The message indicates
the interface and, in the case of a LAN
interface, the SNPA from which the IIH was
received. It also indicates whether we
ourselves use this system ID, or the SNPA
of the other station using the system ID.

Error destroying '[chars]' connection:

[chars]

During process termination IS-IS failed to

destroy a connection to a service provided
by another process. This is an internal
error.

Event handler error [dec]

Event handler error ERRNO. This system

encountered an error ERRNO trying to get
an event from the event handler.

Failed to destroy the [chars] event queue

[hex]: [hex], '[chars]'

An unexpected error occured whilst

destroying an event queue. This is an
internal programming error, but will not
affect protocol operation as it occurred
whilst IS-IS was destroying resources which
are no longer required.

Failed to create adjacency for [chars]

([chars]): [chars]

Failed to create adjacency to the displayed

IS via the displayed interface for the reason
specified.

Failed to create adjacency for [chars]

([chars]): [chars]

Failed to create adjacency to the displayed

IS via the displayed interface for the reason
specified.

IIH received from [chars] contains [chars]

[chars] interface address: [chars]

IS-IS received an IIH from the specified

source containing an invalid and potentially
unusable interface address for the
specified address family. The message
contains details of why the interface
address is invalid. The message implies
that the router sending the bad IIH is either
misconfigured or is not conforming to the
IS-IS specification. If the message describes
the address as unusable, then IS-IS is not
able to use the adjacency as a next hop for
the specified address family. Otherwise ISIS will still attempt to use the adjacency as
a next hop.

[chars] controlled start aborted. Reason:

[chars]

Startup state-machine controlled startup

aborted for the specified reason. Some of
the reasons indicate an internal software
error, or the failure of anther software
service. Other reasons are due to
configuration or other operational
problems. Finally NSF restart may abort
due to no adjacencies being restored, if
there were in fact no adjacencies present
prior to restart/switchover then this is
expected behavior.

[chars] controlled start completed

Startup state-machine controlled startup

process ends here.

Resorting to cold start: [chars].

The startup state-machine has determined

that a cold (re)start must be performed
regardless of current NSF configuration for
the reason specified.

[chars] controlled start beginning

Startup state-machine controlled startup

process begins here.

MAC address change notification received

for P2P interface: [chars]

IS-IS received MAC address change

notification for non LAN interface. ISIS
ignores the notification. The message is
only informational.

Unable to allocate input buffer

This system failed to allocate an input

buffer because there was insufficient
memory to do so.

Unable to allocate input buffer

This system failed to allocate an input

buffer because there was insufficient
memory to do so.

Error in creating message queue to MPLS

The process failed to create a message

queue to communicate with MPLS.

Error in reading message: [chars]

The process failed to read the message.

Error in reading message length: [chars]

The process failed to read the message

length.

Invalid IS-IS packet type [unsigned int]

received on [chars] ([chars] code)

An invalid packet was received on the

specified interface (and, in the case of a
LAN interface, SNPA). The packet is invalid
because its type code is either
unrecognized or inappropriate (e.g. a point
to point IIH on a LAN interface). The packet
has been ignored.

Invalid IS-IS packet type [unsigned int]

received on [chars] ([chars] code)

An invalid packet was received on the

specified interface (and, in the case of a
LAN interface, SNPA). The packet is invalid
because its type code is either
unrecognized or inappropriate (e.g. a point
to point IIH on a LAN interface). The packet
has been ignored.

Received an invalid length TE message for The process has received an invalid length
[chars]: expected ([unsigned int]), received TE message. As a result, the TE message is
([unsigned int])
ignored and TE tunnel may not come up.

The process has received a TE message

with an incompatible version. As a result,
Received an invalid version of TE message the TE message is ignored and TE tunnel
for [chars]: ([unsigned int])
may not come up.

Failed to send a [chars] message to TE

The process encountered an error while

sending message to TE.

Skipping stale purge event for L[dec] LSP

[chars] pseudo-node

The router has re-elected itself DIS after

initiating a purge of its L-LEVEL LSP LSP-ID
due to a previous resignation.

Skipping stale purge event for L[dec] LSP

[chars] pseudo-node

The router has re-elected itself DIS after

initiating a purge of its L-LEVEL LSP LSP-ID
due to a previous resignation.

Backend scan failed for config path

'[chars]': [chars]

LDP failed to read existing configuration

during startup.

An internal inconsistency was detected:

[chars]

LDP has detected an internal inconsistency.

Please capture a core file for analysis.

VRF '[chars]' ([hex]), Failure to initialize

LDP context

During LDP [vrf] context creation, the

initialization of some of the module has
failed. This is a severe condition and results
in LDP to go non-operational state for given
VRF (or default VRF).

VRF '[chars]' ([hex]), Failed to add an entry Failed to add entry for the specified prefix
for [chars]/[dec] in Label Information Base into the Label Information Base.

ACL '[chars]' must be configured as a

prefix-list for longest-match LSPs

Only IP prefix-lists can be used to enable

longest-match LSPs.

Installation of LPTS UDP Hello filters for

VRF '[chars]' ([hex]), Failed to [chars] LPTS targeted LDP neighbors failed. This failure
UDP Hello filter for local [chars]
can prevent sessions to LDP targeted
remote=[chars]: [chars]
neighbors from being established.
LSD application connection failed: [chars]

LDP encountered a problem while trying to

connect with LSD server.

LSD interface [chars] failed for [chars] (ifh

[hex]): [chars]

LDP encountered some problem while

trying to enable/disable MPLS on an
interface via LSD server.

NSR ACK check failed. Please perform show

NSR ACK check failed: [chars]; count [dec] mem heap for analysis.

Repeated internode transport failures, reinitiating NSR sync

LDP encountered too many consecutive

transport errors while trying to send NSR
messages which triggers NSR sync again.

Peer NSR init-sync: No matching Socket

([chars])

Standby LDP received Init-Sync-Done

notification from TCP but has no socket
information from Active LDP.

Peer [chars]; operation='[chars]'; [chars]

Standby LDP instance encountered an error

during processing of NSR synchronization
data sent by Active LDP instance.

Failed to initialize '[chars]': [chars]: Process A fatal error occurred during initialization of
now terminating
an LDP subsystem.

LDP process is shutting down due to

'[chars]' memory state.

LDP process exiting due to unknown/critical

node memory state.

VRF '[chars]' ([hex]), Prefix [chars]/[dec]

update ignored due to 'Unsupported
protection type ([chars])'

In deployments in which Remote LFA FRR is

not supported or in which a specific flavour
of protection is not supported, IGP should
not be computing such primary/remotebackup path.

VRF '[chars]' ([hex]), Received incorrect

[chars] prefix len [dec] from peer [chars]

An LDP message containing a destination

IP Prefix with a bad prefix length has been
received from a peer.

VRF '[chars]' ([hex]), A message with

invalid PDU length (len = [dec]) received
from peer [chars]

A message with invalid PDU length was

received from the peer.

VRF '[chars]' ([hex]), TLV Check failed for a

message (type [hex]) received from peer
LDP received a message with a bad TLV
[chars]
from a peer.

Redundant '[chars]' ([dec]) protocol

registration notification received

LDP has received a redundant protocol

registration notification.

TCB free on open socket, fd = [dec]

TCB free on open socket.

A capability was
installed/updated/uninstalled by an LDP
VRF '[chars]' ([hex]), LDP session(s) reset client. LDP peers that don't support
required to propagate capability change of Dynamic Announcement will not learn of
'[hex] ([chars])' to peers that do not
the change until the LDP session has been
support Dynamic Announcement capability reset.

CPU load or blockage caused latent

transmission of UDP discovery to [chars]:
interval=[dec] sec, expected=[dec] sec.
Hold=[dec] sec

Heavy CPU load or process blockage

resulted in slip of discovery transmission.
This may result in session/adjacency flap.

VRF '[chars]' ([hex]), Label Information

Base revision number has wrapped

The Label Information Base revision

number used to manage advertisement of
labels to LDP peers overflowed. This will
result in faulty label distribution to LDP
peers. The system recovers by toggling
dynamic label switching off and on, which
forces the revision number to be reinitialized.

VRF '[chars]' ([hex]), Invalid FEC type [hex] LDP received an invalid FEC type in a
received from peer [chars]
message from a peer.
VRF '[chars]' ([hex]), Rejecting LDP
adjacency ([chars]): Exceeded maximum
([dec]) number of discovered neighbors.

Discovered more neighbors than

supported. This may lead to nondeterministic set of established sessions on
restart and bootup.

VRF '[chars]' ([hex]), Rejecting LDP

neighbor ([chars]): Reached maximum
([dec]) number of neighbors supported.

Reached maximum number of neighbors

supported.

Global synchronization lost

LDP Non-stop routing synchronization lost

with the standby node.

TCP message enqueue failed: invalid

transmit context.

Message was enqueued with non-NULL

transmit context when NSR is disabled.

TCP message enqueue failed: node is not

active.

Standby Node tried to transmit LDP

message which is not allowed as per
architecture.

VRF '[chars]' ([hex]), [dec] Duplicate

address(es) advertised by more than one
peer

LDP peer address database has some

duplicate addresses which are received
from (and hence bound to) more than one
peer. The presence of one or more
duplicate address confuses LDP control
plane and may lead to potential traffic
blackholing due to unlabelled forwarding
path setup for paths using this address as
the nexthop IP address.

VRF '[chars]' ([hex]), A message with a bad

address [chars] for [chars] is received from Invalid address received from peer for
peer [chars]
given address family.

VRF '[chars]' ([hex]), Received a bad PDU

header from peer [chars], Header: [chars]

Received a bad PDU header from a peer.

VRF '[chars]' ([hex]), Duplicate address

[chars] advertised by peer [chars] is
already bound to peer [chars]

LDP received an address advertisement for

an address from a peer, but the address is
already bound to a different peer.

VRF '[chars]' ([hex]), Malformed packet

received from peer [chars]

Packet received was malformed.

VRF '[chars]' ([hex]), Unexpected Message

type ([unsigned int]) received from peer
An unexpected message type is received
[chars]
from peer.

The session parameters proposed by an

LDP peer differ from those preferred by the
platform. The differences are not sufficient
VRF '[chars]' ([hex]), Received unsupported to prevent the LDP session from being
session parameter ([chars]) from peer
established, but may have an impact on
[chars]
label distribution operation.

VRF '[chars]' ([hex]), Unexpected FSM

event: peer [chars] ([int]), current
state='[chars]', new event='[chars]'

An unexpected FSM event occured. The

given event is not possible in the current
state.

CPU load or blockage caused latent

transmission of LDP keepalive to [chars]:
interval=[dec] sec, expected=[dec] sec.
Hold=[dec] sec

Heavy CPU load or process blockage

resulted in slip of discovery transmission.
This may result in session flap.

VRF '[chars]' ([hex]), Unsolicited open

failed for peer [chars]

Cannot create/find the peer adjaceny

construct in peer database

After LDP local restart, LDP GR forwarding

state hold timer has expired, and MPLS
forwarding is now being updated and
reinstated by LDP application. This
message appears only if the <Bold>mpls
End of GR forwarding state hold time after ldp log graceful-restart<NoBold>
local process restart
command is configured.

GR is being aborted on an LDP GR session

under recovery. This means that current GR
[recovery] is aborted and any pending GR
state is cleaned up. The next time session
connects as new GR session. The reason
for aborting GR on the session helps in
finding the trigger for this abort. This
VRF '[chars]' ([hex]), GR session [chars]
message appears only if the <Bold>mpls
(instance [dec]) GR being aborted (reason: ldp log graceful-restart <NoBold>
[chars])
command is configured.

VRF '[chars]' ([hex]), GR session [chars]

(instance [dec][chars]) [chars]

An LDP GR session state change has

occured - such as disconnected,
reconnected, timed out, and cleaned up.
This message appears only if the
<Bold>mpls ldp log graceful-restart
<NoBold> command is configured.

VRF '[chars]' ([hex]), GR session [chars]

identifier changed to [chars]

A previously known GR peer has

reconnected with a new ldp-id. This
message appears only if the <Bold>mpls
ldp log graceful-restart<NoBold>
command is configured.

VRF '[chars]' ([hex]), Adjacency ([chars])

[chars] with Nbr [chars] [chars] [chars]

An LDP hello adjacency has changed state

(up/down). If adjancency has went down,
then a reason for adjacency going down is
also displayed. This message appears only
if the <Bold>mpls ldp log
adjacency<NoBold> command is
configured.

LDP checkpointing has a limit for maximum

number of neighbors per interface due to
LDP IGP Sync feature requirements. It is not
recommended to cross the limit provided
by Engineering. If crossed, undesired
affects can be seen and LDP IGP Sync
Limit reached for maximum ([dec]) number feature may not work. This only applies to
of neighbors per interface
shared media interfaces.

VRF '[chars]' ([hex]), Skipping LDP [chars]

message for peer [chars] ([chars])

An attempt to queue an LDP message for

transmission to a peer failed.

VRF '[chars]' ([hex]), neighbor [chars],

[chars] [chars]

A LDP neighbor has changed state

(up/down). If neighbor has gone down, then
a reason for session going down is also
displayed. This message appears only if
the <Bold>mpls ldp log neighbor<NoBold>
command is configured.

VRF '[chars]' ([hex]), Peer [chars]

synchronization lost

LDP Non-stop routing synchronization to

standby RP node has been lost for the peer.
This message appears only if the
<Bold>mpls ldp log nsr<NoBold>
command is configured.

LDP Non-stop routing initial-sync event has

Initial synchronization successfully done for completed successfully for some or all
[dec] peers
peers.

VRF '[chars]' ([hex]), Peer [chars] initial

synchronization done

LDP Non-stop routing peer initial-sync

event has completed successfully. This
message appears only if the <Bold>mpls
ldp log nsr<NoBold> command is
configured.

Initial synchronization started for [dec]

peers

LDP Non-stop routing initial-sync event has

been started for all eligible peers.

VRF '[chars]' ([hex]), [chars] for peer

[chars]

An informational LDP notice was generated

for a Session Protection event. This
message appears only if the <Bold>mpls
ldp log session-protection<NoBold>
command is configured.

A capability was
installed/updated/uninstalled by an LDP
client. LDP peers will not learn of the
VRF '[chars]' ([hex]), LDP session(s) being change until the LDP session has been
reset to propagate LDP capability changes reset.

[chars]

Error occurred in lmrib client lib. This could

be a memory error, thread lock fail or a
problem that the LMRIB client is unable to
register with LMRIB.

Initialization failed: [chars] [chars]

Error occurred at client initialization.

[[dec]] [chars] : [chars]

Error occurred in lmrib client lib. This is to

indicate that lmrib_flush did not complete.

RPC failure: [chars]

An RPC-related error occurred in an RPC

call from the LMRIB API. This indicates a
problem in client table registration or
unregistration.

[chars]::[chars]

An internal software error occurred

[chars]

It was not possible to obtain the lock

required to access the databases. This may
be due to the main thread being very busy
processing events.

[chars] failed: error=[hex] ([chars])

An error occurred in event manager or

event connection operations. The text of
the message displays the failed operation
with error code.

[chars] failed: error=[hex] ([chars])

System failed during an API call to

database or event manager in the
initialization phase of LSPV_SERVER
process or its debugging subsystem. The
text of the message displays the failed
operation with error code.

'[chars]'. Process now terminating

Process failed to initialize a necessary

system lock required to facilitate
debugging and display of database results.
This may be occurring due heavy resource
utilization on the system.

Failed to initialize '[chars]': error=[hex]

([chars]). Process now terminating

Successful initialization of a sub-system

required by LSPV_SERVER process failed.
This may have occurred due to heavy
resource utilization in the system or lack of
disk space.

An error occurred during the initialization of

global master or parent timer. The text of
the message displays the failed operation
with the error code. Process cannot
Initialization of global timer: [chars] failed: continue execution in the absence of above
error=[hex] ([chars])
timers.

[chars] cfg counter already 0. Can't

decrement : Item is [chars].

A general error.

Failed to initialize and chain together the

debug event discriptors : [chars]

An error related to the debugging

subsystem occurred.

Sysdb registration for debug config failed : An error related to the debugging
[chars]
subsystem occurred.

[chars] : [chars]

A general error.

Event connection create for [chars] failed :

[chars].
A general error.

Event connection notify for [chars] failed :

[chars].

A general error.

Event connection open for [chars] failed :

[chars].

A general error.

Cannot create event manager : [chars]

An unrecoverable error occurred at system

initialization time.

Error in imc control server bind : [chars]

Internal error

[chars] : [chars]

An unrecoverable error occurred at system

initialization time.

[chars]

A general error.

[chars]

Internal error

[chars] : [chars]

Internal error

Error in bag decoding : [chars]

Internal error

Error in bag free : [chars]

Internal error

Cannot register bags : [chars].

A general error.

Error in sysdb bind : [chars]

Internal error

Error in datalist free : [chars]

Internal error

Error in datalist next : [chars]

Internal error

SysDB Oper - [chars] failed : [chars].

A general error.

SysDB Oper - [chars] failed : [chars].

A general error.

SysDB operation [chars] failed: [chars]

A general error.

SysDB operation [chars] failed: [chars]

A general error.

[chars] failed : [chars].

A general error.

Initialization failed: [chars] [chars]

An unrecoverable error occurred at system

initialization time.

[chars] failed for [chars] [[hex]] : [chars]

A general error.

idb [chars] has handle [[hex]], IM update

has [[hex]]

A general error.

[chars]

A general error.

Failed to build ORA [chars] ([chars])

[chars], Add [chars] branch [chars]
[chars], Delete [chars] branch [chars]
[chars], Modify [chars] branch [chars]

There was an internal error in the routing

policy library.
A mLDP branch has been added.
A mLDP branch has been deleted.
A mLDP branch has been modified.

MLDP is disabled

MLDP has been disabled by configuration.

MLDP is enabled

MLDP has been enabled by configuration.

Failed to initialize MLDP

A fatal error occurred during initialization of

MLDP subsystem.

[chars] ([chars],[chars]/[dec]) has been

detected.

LC control plane detected that traffic is

already coming on backup path which is
currently the selected path for forwarding
traffic to egress LCs. Then set the HW
watchdog of ingress NP to monitor traffic
loss event on the path instead of
monitoring traffic activity.

[chars] ([chars],[chars]/[dec]) has been

detected.

LC control plane detected that traffic is

already coming on primary path. Then set
the HW watchdog of ingress NP to monitor
traffic loss event on the path instead of
monitoring traffic activity.

[chars] ([chars],[chars]/[dec]) has been

detected.

LC control plane detected that either no

traffic coming or traffic loss is occurred on
backup path. Data plane should switch
over to the MoFRR primary path already.
But somehow the traffic switchover
notification message sent from data plane
has been lost from NP on the way to LC
CPU. With this detection, control plane will
re-sync with data plane on MoFRR route.

[chars] ([chars],[chars]/[dec]) has been

detected.

LC control plane detected that either no

traffic coming or traffic loss is occurred on
primary path. Data plane should switch
over to the MoFRR backup path already.
But somehow the traffic switchover
notification message sent from data plane
has been lost from NP on the way to LC
CPU. With this detection, control plane will
re-sync with data plane on MoFRR route.

By removing the over-configured MoFRR

routes, the total number of MoFRR enabled
flows is being reduced. When the total
number is first time reduced to exactly
75% of maximum supported (1024) MoFRR
Total number of MoFRR enabled multicast routes of current release, i.e., 768 routes,
routes is no longer at maximum ([unsigned this message will be printed on the console
int]).
and only once.

Currently ASR9K supports maximum 1024

flows which are guaranteed to have traffic
switchover time within 50 ms. In addition, a
line card encounters HW out-of-resource
condition when the total number of MoFRR
Total number of MoFRR routes has reached routes reaches 2048 MoFRR routes. Thus,
maximum ([unsigned int]). MoFRR will not any new configured 'MoFRR' beyond 1024
be supported on new routes.
flows are not supported.

[chars] : [chars]

An internal system error occured.

No memory for '[chars]'

The requested operation could not be

accomplished because of a low memory
condition.

bag(s) registration failed: [chars]

Some error occured while trying to register

edm bags. The text of the message
displays the failed operation with error
code.

[chars] failed: [chars]

Some requested operation failed. The text

of the message displays the failed
operation with error code.

[chars] failed: [chars]

Some error occured in event/event

manager/event connection operations. The
text of the message displays the failed
operation with error code. The traceback
can be used to get the function/line
number of error generating code.

sysdb_bind failed for '[chars]': [chars]

Some error occured in sysdb bind operation

bind. The text of the message displays the
failed operation for the bindpoint with error
code.

[chars] failed: [chars]

Some error occured in sysdb operation. The

text of the message displays the failed
operation with error code. The traceback
can be used to get the function/line
number of error generating code.

[chars]. Error = [chars] (errno=[dec]).

There was a critical system call failure

resulting in a failure to provide some
system service as indicated in the message
text.

[chars]. Error = [chars] (errno=[dec]).

Hardware memory allocation for table

lookup unit (TLU) failed. This can be
because the system has more forwarding
entries than supported limits or there is a
software defect.

[chars]. Error = [chars] (errno=[dec]).

Hardware memory write for table lookup

unit (TLU) failed. This can because 1)
connection to mipc lost. 2) mipc/metro
problem.

[chars]. Error = [chars] (errno=[dec]). Out

label = [dec].

There was a critical system call failure

resulting in a failure to provide some
system service as indicated in the message
text.

[chars]. Error = [chars] (errno [dec]).

There was an internal failure that may

impact non-essential system function.

[chars]. Error = [chars] (errno [dec]). Out

label = [dec].

There was an internal failure that may

impact non-essential system function.

MPLS LIB IM client could not register for

debugging ([chars])

MPLS LIB IM client library failed to register

for debugging.

[chars] failed :[chars]

Some error occurred in Alloc/Chunk related

memory operations. The text of the
message displays the failed operation and
the related memory construct. The
traceback can be used to get the
function/line number of error generating
code.

[chars]: [chars]

Some informational message with cerrno.

[chars] failed: [chars]

Some error occurred in operations with IM.

The text of the message displays the failed
operation and the related error code. The
traceback can be used to get the
function/line number of error generating
code.

[chars] failed: [chars]

Some error occurred in Packet

(IP/MPLS/ICMP) related operations. The text
of the message displays the failed
operation and the related error code. The
traceback can be used to get the
function/line number of error generating
code.

[chars] failed for '[chars]': [chars]

Some error occurred in Managed Timer

related operations. The text of the
message displays the failed operation and
the related timer construct with error code.
The traceback can be used to get the
function/line number of error generating
code.

[chars] failed (tree=[chars]): [chars]

Some error occurred in WAVL operations

The text of the message displays the failed
operation and the related wavl tree. The
traceback can be used to get the
function/line number of error generating
code.

The show thread waited [unsigned int]

seconds and could not acquire the
mutex.\n\ Aborting show request. Please
try again. If this problem persists,\n\ please
contact your technical service
representative.

The show thread could not acquire the

mutex to service the show request. The
main thread in te_control may be
busy/blocked/hogging while holding That
mutex.

[chars]

An internal system error occured.

Attempted a LSD client API call ([chars])

while not connected

LSD client was not connected and an lsd

client api was called.

Insufficient memory for '[chars]', [unsigned MPLS LSD terminated due to lack of
int] bytes, terminating
memory for a critical operation.
[chars]

Obituary Call to reinitialize bcdls has been

unsuccessful.

Callback from ENS on incorrect thread,

actual/expected = [dec]/[dec]
(CSCsd51829)

Detected single-threaded mpls-lsd code

running on an unknown thread. This
concurrency can result in corruption.

[chars]

Rewrite creation or modification failed due

to presence of multiple IP route elements.

MPLS LSD on Standby failed to add invalid

Invalid label provided by Checkpoint ([dec]) label provided by CHeckpoint.

[chars]

Client error

[chars]

Miscellaneous MPLS LSD error.

Initialization of MPLS LSD failed,

op='[chars]' ([chars])

MPLS LSD failed to initialize for the reason

displayed.

Initialization of RCC [chars] library for MPLS MPLS LSD failed to initialize RCC library for
LSD failed, (error: [chars])
the reason displayed.

control clear mapping for [chars] mpls

proto [dec] failed [chars]

MPLS could not clear control mapping for

underlying protocol.

control set mapping for [chars] to [hex]/

[hex] mpls proto [dec] failed [chars]

MPLS could not set control mapping for

underlying protocol.

Pkt([pointer]) with no nexthop in HSSD,

output interface - <<CH[hex]>>. MPLS
label stack:[chars]. IP info:[chars]. HSSD
info:[chars].

MPLS slowpath got a packet for which ARP

needs to be done, but, it doesn't have the
nexthop needed. The pkt is dropped.

[chars] FAILED: [chars]

Some miscellaneous error occured. The

text of the message explains the
err/warning and traceback can be used to
get the function/line number of error
generating code.

Peer [chars] (node-id: [chars]) state

changed from [chars] to [chars]
Memory allocation failed for [chars]

An PCE peer has changed state. This

message appears only if the <Bold>mpls
traffic-eng pce logging events peerstatus<NoBold> command is configured
for the PCE.
Allocation of memory failed.

Connection to the [chars] failed ([chars])

MPLS static process could not connect with

a manager.

Initialization of MPLS Static failed - [chars]

([chars])

Initialization of the MPLS Static process

failed.

The system detected [dec] label

discrepancies (static label could not be
allocated due to conflict with other
applications). Please use 'clear mpls static
local-label discrepancy' to fix this issue.
To clear label discrepancy

The show thread waited [unsigned int]

seconds and could not acquire the
mutex.\n\ Aborting show request. Please
try again. If this problem persists,\n\ please
contact your technical service
representative.

The show thread could not acquire the

mutex to service the show request. The
main thread in te_control may be
busy/blocked/hogging while holding That
mutex.

A callback from the IOX-XR infrastructure

was not handled by the MPLS-TE process
A callback ([chars]) has been received in
because it was received in the wrong
the wrong thread ([unsigned int], should be thread. The TE process may now be in an
\ in [unsigned int]). The callback has not
inconsistent state with the rest of the
been handled.
system.

A callback ([chars]) has been received in

the wrong thread (%zu, should be \ in
[unsigned int]). The callback has not been
handled.

A callback from the IOX-XR infrastructure

was not handled by the MPLS-TE process
because it was received in the wrong
thread. The TE process may now be in an
inconsistent state with the rest of the
system.

The TE checkpoint table translation library

TE checkpoint translation received an
was invoked with an invalid translation
invalid translation direction: [unsigned int] direction.

'[chars]' had a value of '[chars]', which did

not match the expected value '[chars]'.
An internal data consistency check failed.
The creation of the auto-tunnel backup
Auto-tunnel backup creation failed because aborted since all IDs in the auto-tunnel
\ the ID pool limit of [dec] has been
backup ID range have already been
exhausted
allocated.
Auto-backup tunnel [dec] creation failed
The creation of the auto-tunnel backup
because \ the maximum tunnel destination aborted since it would have exhausted the
limit [dec] has been exhausted
tunnel destination scale limit
Auto-backup tunnel [dec] creation failed
because \ the maximum tunnel interface
limit is [dec] exhausted

The creation of the auto-tunnel backup

aborted since it would have exhausted the
tunnel interface scale limit

Auto-tunnel [dec] creation failed because \ The creation of the auto-tunnel aborted
maximum tunnel interface limit [dec]
since it would have exhausted the tunnel
exhausted
interface scale limit
Auto-mesh tunnel (destination [chars] in
mesh group [dec]) creation failed because \ The creation of the auto-mesh tunnel
the tunnel ID range limit of [dec] has been aborted since all tunnel IDs in the range
exhausted
have already been allocated.
Auto-mesh tunnel [dec] (destination [chars]
in mesh group [dec]) creation failed
The creation of the auto-mesh tunnel
because \ the maximum tunnel destination aborted since it would have exhausted the
limit [dec] has been exhausted
tunnel destination scale limit

Auto-mesh tunnel [dec] (destination [chars]

in mesh group [dec]) creation failed
The creation of the auto-mesh tunnel
because \ the maximum tunnel interface
aborted since it would have exhausted the
limit [dec] has been exhausted
tunnel interface scale limit
P2MP auto-tunnel [dec] destination
creation failed because \ maximum tunnel
destination limit [dec] exhausted

The creation of the P2MP auto-tunnel

destination aborted since it would have
exhausted the tunnel destination scale
limit

The creation of the P2MP auto-tunnel

aborted since all IDs in the P2MP autoP2MP auto-tunnel creation failed because \ tunnel ID range have already been
ID pool limit of [dec] exhausted
allocated.
P2MP auto-tunnel [dec] creation failed
The creation of the P2MP auto-tunnel
because \ maximum P2MP tunnel interface aborted since it would have exhausted the
limit [dec] exhausted
tunnel interface scale limit

Unable to add route to [chars] via [chars]

to RIB: maximum route path limit [dec]
exceeded

TE was unable to add an announced

destination to the RIB because the \ system
limit on the number of parallel paths to an
address would have \ been exceeded

MPLS TE encountered error \[chars]\ while

[chars] via the Interface Manager

Interface Manager returned an error during

a tunnel interface operation. The system
internal tunnel status might now be
inconsistent which might prevent the
tunnel from coming up or traffic flowing
over this tunnel to be dropped.

MPLS TE encountered error \[chars]\ while

[chars] via the Interface Manager

Interface Manager returned an error during

a tunnel interface operation. The system
internal tunnel status might now be
inconsistent which might prevent the
tunnel from coming up or traffic flowing
over this tunnel to be dropped.

[chars](): line [unsigned int]: [chars]

An inconsistency in internal state was

detected.

[chars](): line [unsigned int]: [chars]

An inconsistency in internal state was

detected.

[chars](): line [unsigned int]: [chars]: error An inconsistency in internal state was
[chars] ([hex])
detected.

[chars](): line [unsigned int]: [chars]: error An inconsistency in internal state was
[chars] ([hex])
detected.

[chars] failed for Tunnel [dec] (LSP ID:

[dec], Source: [chars], PHOP: [chars],
NHOP: [chars], \ Label: [unsigned int], Role: A LMRIB Label Rewrite related error
[chars])
occurred.

[chars] failed for Tunnel [dec] (LSP ID:

[dec], Source: [chars], PHOP: [chars],
NHOP: [chars], \ Label: [unsigned int], Role: A LMRIB Label Rewrite related error
[chars]) [error: [dec], [chars]]
occurred.

[chars] failed for [chars] (LSP ID: [dec],

Label: [unsigned int])

A LMRIB Tunnel Rewrite related error

occurred.

[chars] failed for [chars] (LSP ID: [dec],

A LMRIB Tunnel Rewrite related error
Label: [unsigned int]) [error: [dec], [chars]] occurred.

Memory allocation failed for [chars]

Allocation of memory failed.

Memory allocation failed for [chars]

Allocation of memory failed.

[chars]: [chars]: [chars]

A Bag related error occurred.

[chars]: [chars]: [chars]

A SysDB free related error occurred.

[chars]: [chars] failed for path [chars] :

[chars]

A sysdb error occurred.

Traffic-eng event tracing subsytem

initialization failed

Traffic-eng could not initialize the tracing

module

Traffic-eng event tracing subsytem

initialization failed

Traffic-eng could not initialize the tracing

module

Client '[chars]' has not processed an

update [dec] seconds after being notified.
Forcing reconnect. PID=[dec],

TE server is forcing the specified client to

reconnect, as the client has not processed
a notification after a substantial timeout
period.

GMPLS NNI support, including this

GMPLS NNI support, including this
command, will be removed in release 4.3.0 command, will be removed in release 4.3.0.

The show thread waited [unsigned int]

seconds and could not acquire the mutex.\
Aborting show request. Please try again. If
this problem persists,\ please contact your
technical service representative.

The show thread could not acquire the

mutex to service the show request. The
main thread in te_control may be
busy/blocked/hogging while holding That
mutex.

The show thread waited [unsigned int]

seconds and could not acquire the mutex.\
Aborting show request. Please try again. If
this problem persists,\ please contact your
technical service representative.

The show thread could not acquire the

mutex to service the show request. The
main thread in te_control may be
busy/blocked/hogging while holding That
mutex.

Process is shutting down ([chars]): [chars]

TE process has encountered a problem

which means it is no longer able to
continue and is shutting down. The
message includes a brief description of the
problem. The message also describes
whether or not TE process has
automatically been restarted.

Process is shutting down ([chars]): [chars]

TE process has encountered a problem

which means it is no longer able to
continue and is shutting down. The
message includes a brief description of the
problem. The message also describes
whether or not TE process has
automatically been restarted.

[chars]

An internal system warning occurred.

[chars]

An internal system warning occurred.

Traffic-eng FSM dropped an event ([chars])

for S2L (tid [unsigned int], etid [unsigned Traffic-eng FSM dropped an event, because
int], lspid [unsigned int],\ p2mpid
the S2L was created after the event was
[unsigned int], subgroupid [unsigned int]) posted.
Traffic-eng FSM dropped an event ([chars])
for S2L (tid [unsigned int], etid [chars],
Traffic-eng FSM dropped an event, because
lspid [unsigned int],\ p2mpid [unsigned
the S2L was created after the event was
int], subgroupid [unsigned int])
posted.

Backup Tunnel ([chars], LSP Id: [unsigned

int]) state changed to [chars].

The specified backup tunnel interface has

changed it's FRR status.

Backup Tunnel ([chars], LSP Id: [unsigned

int]) state changed to [chars].

The specified backup tunnel interface has

changed it's FRR status.

Bandwidth change on [chars] (signalledname: [chars], LSP id: [unsigned int]): new The signalled bandwidth on the specified
bandwidth \ [unsigned int] kbps
tunnel interface has changed.

[chars] (signalled-name: [chars], LSP Id:

[unsigned int]) failed to [chars] because
of \ insufficient bandwidth.

The specified interface, with the specified

LSP Id, cannot be setup \ or reoptimized
because of insufficient bandwidth. The first
argument \ is the tunnel name and the last
argument is 'setup' or 'reoptimize'. \ LSP Id
will be always 0 (zero), if failure happens
during setup time.

Path calculation failed on [chars] (signalled- Path calculation failed for the specified
name: [chars], LSP [unsigned int]): [chars] tunnel and LSP.

Tunnel [dec] ([chars], LSP Id: [unsigned

int]) has been preempted at [chars].

The specified interface, with specified LSP

Id, has been preempted \ at specified IP
Address or local node. The first %s refers to
\ signalled tunnel name and the second %s
refers to either \ the IP Address (of the
remote node) or 'local node'.

[chars] (signalled-name: [chars], LSP Id:

[unsigned int]) record-route[chars].

The specified interface record-route has

changed.

[chars] (LSP Id: [unsigned int]) has been

reoptimized.

The specified interface has been

reoptimized with the specified LSP.

The specified interface, with the old LSP Id,

has been reoptimized \ with the new LSP Id,
because of the specified reason. The first \
argument is the the tunnel name, the
second argument is the \ signalled-name,
and the last argument is the reason
reoptimization \ was triggered. The trigger
reasons are - - Periodic Timer Expiry Bandwidth CLI Change - FRR - CLI request Metric Type Change - Received Preferred
Path Exists Msg - Received Preferred Tree
Exists Msg - PO switchover trigger - Soft
[chars] (signalled-name: [chars], old LSP Id: Preemption - AUTO-BW Overflow - AUTO[unsigned int], new LSP Id: [unsigned int]) BW Underflow - AUTO-BW Adjustment has been \ reoptimized; reason: [chars].
Topology change

[chars] (LSP Id: [unsigned int]) has been

fast-rerouted.

The specified interface has been rerouted.

[chars] (signalled_name: [chars], LSP Id:

[unsigned int]) has been [chars].

The specified interface has been rerouted.

The first %s \ refers to the tunnel name,
the second argument is the \ signalledname, and the last %s refers to \ any of the
following depending on the trigger - - fastrerouted - rerouted due to topology change

The specified interface is fast-reroute

enabled and in UP state; path verification
failed but it did not take down the
interface. Interface is now in re-route
pending state and may stay in this state
[chars] (LSP Id: [unsigned int]) is in re-route forever until the interface finds a valid
pending state.
path.

The specified interface is fast-reroute

enabled and in UP state; path verification
failed but it did not take down the
interface. Interface is now in re-route
pending state and may stay in this state
[chars] (signalled-name: [chars], LSP Id:
forever until the interface finds a valid
[unsigned int]) is in re-route pending state. path.

The specified interface is fast-reroute

enabled and in UP state; earlier path
verification failed but it did not take down
the interface and got into reroute-pending
state. Interface is now getting out of re[chars] (old LSP Id: [unsigned int], new LSP route pending state as a result of
Id: [unsigned int]) has been reoptimized.
reoptimization.

The specified interface is fast-reroute

enabled and in UP state; earlier path
verification failed but it did not take down
the interface and got into reroute-pending
[chars] (signalled-name: [chars], old LSP Id: state. Interface is now getting out of re[unsigned int], new LSP Id: [unsigned int]) route pending state as a result of
has been [chars].
reoptimization or CLI changes.

The specified interface, with the specified

LSP Id, has been soft \ preempted at
specified IP address or local node. The first
%s refers to \ the signalled tunnel name
and the second %s refers to the interface
name \ where the preemption was
singalled. The third %s refers to the
address of \ the signalling interface. The
fourth and fifth %s are filled out if frr \
Tunnel [dec] ([chars], LSP Id: [unsigned
rewrite is done during soft preemption. The
int]) has been soft preempted at \ interface fourth %s is a message stating \ the traffic
[chars] ([chars]), timeout after [unsigned
has been moved to a backup tunnel and
int] seconds. [chars] [chars]
fifth %s is the name of \ the backup tunnel.
Tunnel [dec] ([chars], LSP Id: [unsigned
int]) torn down due to soft preemption
timeout

The specified interface, with the specified

LSP Id, was attempting a soft \ preemption
but timed out and was torn down.

Tunnel [dec] ([chars], LSP Id: [unsigned

int]) has been soft preempted at [chars]

The specified interface, with the specified

LSP Id, has received a path \ error message
and will be soft preempted.

[chars] (Standby LSP Id: [unsigned int])

[chars]

The specified interface has changed

operational state.

[chars] (Standby LSP Id: [unsigned int])

[chars]

The specified interface has changed

operational state.

[chars] (signalled-name: [chars], LSP Id:

[unsigned int]) state changed to [chars]

The specified interface has changed

operational state.

[chars] (LSP Id: [unsigned int]) state

changed to [chars]

The specified interface has changed

operational state.

[chars] (signalled-name: [chars], LSP Id:

[unsigned int] Dest: [chars]) BFD session
went down, \ Resv RRO addresses: [chars]

The BFD session for the specified interface

destination went down. \ The first
argument is the tunnel name. The second
argument is the \ singalled name, and the
fourth argument is Sub-LSP destination.
The \ last argument is the list of RRO
addresses. \

[chars] (signalled-name: [chars], LSP Id:

[unsigned int] Dest: [chars]) BFD session
did not \ come up within timeout duration
([unsigned int] seconds), Resv RRO
addresses: [chars]

The BFD session for the specified interface

destination timed out. \ The first %s refers
to the tunnel name. The second %s refers
to \ Sub-LSP destination. The third %s
refers to list of RRO addresses. \

[chars] (signalled-name: [chars], LSP Id:

[unsigned int] Dest: [chars]) BFD session
came up

The BFD session for the specified interface

destination came up. \ The first argument
is the tunnel name. The the second
argument is \ the signalled name, and the
last argument is the Sub-LSP destination. \

[chars] (LSP Id: [unsigned int] Dest:

[chars]) failed to [chars] because of
insufficient bandwidth.

The specified P2MP Sub-LSP, with the

specified LSP Id and destination, \ cannot
be setup or reoptimized because of
insufficient bandwidth. \ The first %s refers
to the tunnel name, the second %s refers
to \ Sub-LSP destination and the second %s
refers to either \ 'setup' or 'reoptimize'. LSP
Id will be always 0 (zero), if \ failure
happens during setup time.

Path calculation failed on [chars] (signalledname: [chars], Dest: [chars], LSP:

Path calculation failed for the specified
[unsigned int]):\ [chars]
tunnel, destination and LSP.

The specified P2MP Sub-LSP, with specified

LSP Id and destination, \ has been
preempted at specified IP Address or local
node. \ The first %s refers to signalled
tunnel name, the second %s \ refers to
Tunnel [dec] ([chars], LSP Id: [unsigned int] Sub-LSP destination and the third %s refers
Dest: [chars]) has been preempted at
to either \ the IP Address (of the remote
[chars].
node) or 'local node'.

[chars] (LSP Id: [unsigned int] Dest:

[chars]) has been fast-rerouted.

The specified sub LSP has been rerouted.

[chars] (signalled-name: [chars], LSP Id:

[unsigned int] Dest: [chars]) has been
[chars].

The specified sub LSP has been rerouted.

The first %s \ refers to the tunnel name,
the second %s refers to signalled-name \
and the third %s refers to the destination
and the last one refres \ to any of the
following depending on the trigger - \ - fastrerouted - rerouted due to topology change

[chars] (signalled-name: [chars], LSP Id:

[unsigned int] Dest: [chars]) state changed The specified interface destination has
to [chars]
changed operational state.

[chars] (LSP Id: [unsigned int] Dest:

[chars]) state changed to [chars]

The specified interface destination has

changed operational state.

[chars] : [chars]

An internal system error occurred.

[chars] : [chars]

An internal system error occurred.

'[chars] LSP of tunnel-tp[unsigned int]

[chars] lockout state'

The indicated LSP has entered or exited

lockout state due to administrative action
at one endpoint.

The MPLS-TP tunnel-tp interface has

changed the LSP over which it data traffic
is carried, possibly due to a fault or
'tunnel-tp[unsigned int] switched to [chars] administrative action, or to restore traffic to
as active'
the working-LSP after LSP recovery.

'tunnel-tp[unsigned int] changed the state

to [chars]'
The MPLS-TP tunnel changed state.

Asynchronous error: [chars]

'An unhandled asynchromous error

occurred in the MRIB API'

Corrupted update: [chars]. (expected %zd

bytes, got %zd bytes)

'A corrupted update was received from the

MRIB by the MRIB API'

[chars]%s

Error occurred in mrib client lib.

Initialization failed: [chars] [chars]

Error occurred at client initialization.

[[dec]] [chars] - [chars]

Error occurred in mrib client lib.

RPC failure: [chars]

'An RPC-related error occurred in an RPC

call from the MRIB API'

Warning: [chars]

'A recoverable error condition occurred in

the MRIB API'

[chars]No memory for [chars] in [chars]

The requested operation could not be

accomplished because of a low memory
condition.

The requested operation could not be

accomplished because of a low memory
Resource unavailable for [chars] in [chars] condition.

Route collapse IPC Init failed at [chars]!

The route collapse IPC could not be

initialized

Error in EDM activity : [chars] - [chars]

An error occurred when MRIB tried to

initialize conn to Sysdb for show
commands.

[chars]

An error occurred in MRIB MVPN EXTRANET

operation.

[chars]%s

A general error.

Communication error: [chars] [chars]

A Inter Process Communication error

occurred.

Initialization failed: [chars] [chars]

An unrecoverable error occurred at system

initialization time.

[chars]

An error occurred in MRIB interface cache

operation.

[chars]

An internal software error occurred.

Internal error: [chars] in [chars] line [dec]

([chars])

An internal software error occurred.

LRD Error: [chars] - [chars]

A general error.

[[dec]] [chars] - [chars]

Internal error.

MRIB LWM error: [chars] - [chars]

Internal error.

Interface [chars] has no modified flags.

Shouldn't be present in list.

An error occurred when MRIB tried to walk

the modified interfaces list.

[chars]

An error occurred in MRIB NSF.

An internal error occurred when MRIB

Error modifying MRIB Non-stop Forwarding attempted to transition to/from Non-stop
state in [chars]: [chars]
Forwarding mode.

[[dec]] Platform API failed to parse nodeid

from ifh [hex] [err: [chars]]

Platform API failed to get node id for

underlying interface

[chars]

An error occurred in MRIB route collapse

operation.

The initialization of a functionality failed.

This component might still operate without
Initialization of \[chars]\ functionality failed the functionality.

[chars]

An error occurred in MRIB TLC operation.

Failed to [chars] [chars] interface in

interface tree of [chars].

An error occurred when MRIB tried to

perform a tree operation.

Tunnel entry [hex] being added & removed IIR sends addition & deletion of bundle
in same batch ([dec])
member mapping in same batch

Client [CCB ID [dec]]. Update size = [dec]

bytes. [chars]

A client attempted to write an invalid

update.

Debugging error: [chars] in [chars] line

[dec] ([chars])

An error related to the debugging

subsystem occurred.

[chars]

A warning occurred in MRIB MVPN

EXTRANET operation.

Filter violation error: conn [dec] ([chars]:

[chars]) in [chars]

A client tried to modify a route attribute not

owned by it

[chars]

A general warning.

Illegal parameter in function call ([chars])

in [chars]

An externally accessible function has been

called with illegal parameter(s). the
parameter(s) has been casted to an
acceptable value.

The requested operation could not be

accomplished because of a low memory
No memory for [chars] in [chars]. Handling: condition but the problem has ben handled
[chars]
locally.

[chars]%s

A pfi query was made for a stale interface

handle, possibly transient error.

Failed to [chars]: [chars]

Internal error.

the peer [chars] has changed to an illegal

state: [dec]

The MSDP peer entered a new state which

was not one of the valid states.

cache error: [chars] [chars]

An error occured updating the SA cache.

This indicates a problem adding an
element into the MSDP database.

[chars] error: [chars]

A peer has incorrectly attempted to

establish a connection with us.

error: show server error: [chars] [chars]

An error occured with a show client

communicating with the msdp. show
server.

event [chars] failure: [chars]

An unrecoverable error occurred during the

event loop.

Initialization failed: [chars]

An unrecoverable error occurred at system

initialization.

Initialization failed: [chars], [chars]

An unrecoverable error occurred at system

initialization.

[chars]: [chars] [chars]/[chars]

An error occured due to inconsistent

internal state.

I/O failure: [chars] [dec], [chars], [chars]

An error has occurred during a socket

operation.

Failed to register on interface [chars]:

[chars]

An error occured when registering to ITAL.

ltrace_init failed for '[chars]': [chars]

Internal error

mrib error: [chars], [chars]

An error has occurred during

communication with the MRIB.

out of memory: [chars] [chars]

Eliminate system processes or add memory

[chars] active SA limit [dec] exceeded SA

count

Resource limit has been hit

sysdb error: [chars] [chars]

An error occured while communicating with

sysdb.

This indicates a problem with the event

received from the watchdog system
Received an invalid event from WDSysmon monitor.

[chars]

Internal error.

config failed: [chars] [chars], [chars]

'reconfigure'

Received [chars] memory depletion

warning, stop creating new msdp SA state

Internal error.

Node memory back to normal, new msdp

states will be created

Internal error.

peer error: [chars] [chars]

Some peer error occured. This is just a

warning. Please ensure that the msdp
peers are configured correctly.

rib error: [dec] [chars]: [chars]

An error has occurred during

communication with the RIB.

[chars] [chars] [chars]

This is a notice saying that the MSDP Peer

UP/DOWN.

Could not load DLL [chars] : [chars]

There was a problem loading the DLL perhaps the router has run out of memory,
or there was a problem reading the file.

There was a problem locating the DLL with

matching signature - the problem is
Could not locate DLL [chars]([chars]), using resolved by using existing dll installed on
[chars]([chars])
this node.

Unable to register cerrno dll [chars]

because [chars]

The given cerrno dll could not be marked

for use. This does not change the
functionality of the system but does
obscure the meaning of error codes
presented by this part of the system.

Memory allocation failed because of low

memory condition

The requested operation could not be

accomplished because of a low memory
condition.

Dock entry add failed because duplicate

ORAA was detected

This message appears because the ORAA

was defined twice.

DLL [chars] has missing init function

because it is not installed properly

The library is incorrectly installed.

The base type '[chars]' v'[chars]' was used One of the operations in one of the ORAs
as a [chars] in a [chars] :'[chars]'. The
used a base type that was not defined in
operator is defined as [chars]
any of the ORA math sets.

Route access library [chars] has no [chars]

function as DLL not installed properly
The library is incorrectly installed.
There is a function declared within the
various docked ORAs at this attach point
that uses an operator that does not exist
The operator '[chars]' was not found in any with the same set of docked ORAs. Please
of the '[chars]'s ORAs.
contact support.

Threading operation '[chars]' for '[chars]'

failed because: [chars]

The presented threading operation failed. It

is likely that policy multi-version calls will
stop working and thus policy may not be
operational.

Unable to register cerrno dll [chars]

because [chars]

The given cerrno dll could not be marked

for use. This does not change the
functionality of the system but does
obscure the meaning of error codes
presented by this part of the system.

Some base type(s) was(were) unavailable

during AP merging at: [chars]

One or more base types were not available

when bringing together the parts of this
attach point. This is an item that should be
caught during testing. If it does show up,
support should be contacted.

This is most likely an internal logic error

The dock data for docking item [chars] was that resulted in a given ora docking being
missing
released more than once.
The debug event initialization failed. The
Unable to bring up debug event structures: ora docker will still run correctly, but debug
[chars]
commands may be unavailable.

Unable to shutdown debug event

structures: [chars]

The debug event shutdown failed. The ora

docker will still run correctly, but debug
commands may be unavailable.

Failed to add an external data manager

datalist for [chars]

A process has requested information

through SysDB, probably as the result of
executing a show command. The attempt
to add an item to an external data
manager datalist has failed.

Failed to create external data manager

datalist for [chars]

A process has requested information

through SysDB, probably as the result of
executing a show command. The creation
of the external data manager datalist has
failed.

Failed to set external data manager more

flag for datalist [chars]

A client has requested information through

SysDB from OSPF. During execution of the
request an attempt to set a flag indicating
there is more data for the client failed.

Failed to encode [chars] data in external

data manager

A process has requested information

through SysDB, probably as the result of
executing a show command. The data
requested could not be encoded.

Failed to add to an external data manager

list for [chars]

A process has requested information

through SysDB, probably as the result of
executing a show command. The attempt
to add an item to an external data
manager list has failed.

A process has requested information

through SysDB, probably as the result of
executing a show command. The creation
Failed to create external data manager list of the external data manager list has
for [chars]
failed.

Failed to connect to SysDB ([chars])

The process failed to connect to SysDB

while starting.

Failed to build [chars], reason [chars] cer

[chars]

Internal error in policy library.

Could not apply policy operation [chars] to

attribute [chars] because [chars]
Internal error in policy library.

Error adding path to batching buffer for

[chars]/[dec], data len [dec], max msg len
[dec], max buf len [dec]

An error was encountered in the call to

ipv4_rib_batch_add_path.

Error deleting path from batching buffer for

[chars]/[dec], data len [dec], max msg len An error was encountered in the call to
[dec], max buf len [dec]
ipv4_rib_batch_delete_path.

Error changing purgetime

An error was encountered in the call to

ipv4_rib_protocol_modify.

Error adding route header to batching

buffer for [chars]/[dec], data len [dec], max An error was encountered in the call to
msg len [dec], max buf len [dec]
ipv4_rib_batch_add_route.

Error informing rib that batch is complete

An error was encountered in the call to

ipv4_rib_batch_complete.

RIB batch error, [chars] (result [dec]), prefix

[hex]/[dec] next_hop [hex] intf [chars]. \n The specified error was encountered in the
Retrying
OSPF RIB batching code.

RIB batch error, [chars]

The specified error was encountered in the

OSPF RIB batching code.

RIB batch error, [chars] ([hex])

The specified error was encountered in the

OSPF RIB batching code.

Believes [chars]/[dec] and [chars]/[dec]

differ

The RIB batching API believes that it

already has this router header in the
batching buffer.

Failed to register internal error codes:

[chars]

An error occurred during the registration of

OSPF error codes.

An error occurred during initialization of the

Error initializing ospf_uv debugging: [chars] ospf_uv process.

Failed to allocate %zu bytes for '[chars]'

The ospf_uv process was unable to allocate

memory for the specified resource.

Error signaling process ready: [chars]

The ospf_uv process was unable to signal

process ready to sysmgr.

Error binding to SysDB: [chars]

The ospf_uv process was unable to bind to

SysDB.

Error unbinding from SysDB: [chars]

The ospf_uv process was unable to unbind

from SysDB.

Error registering with SysDB: [chars]

The ospf_uv process was unable to register

with SysDB.

Error setting SysDB callback functions:

[chars]

The ospf_uv process was unable to initialize

SysDB callbacks.

Error in event loop: [chars]

An error occurred in the main ospf_uv

event loop.

Error creating event connection manager:

[chars]

The ospf_uv process was unable to create

an event connection manager instance.

Error initializing forward-reference store:

[chars]

The ospf_uv process was unable to initialize

the forward-reference store library.

Caution: The OSPF process name \[chars]\

conflicts with a show or clear command
name

The name chosen for the OSPF process

matches an ospf show or clear command,
or a command abbreviation. This can cause
ambiguities with subsequent show or clear
commands for this process.

No memory, [chars], process terminated

Memory allocation of a critical OSPF

resource failed because of a low memory
condition. The OSPF process was
terminated.

Allocation error, %zu bytes for [chars]

Allocation of the specified resource failed

because of a low memory condition.

[chars]: area pointer is NULL

An internal software error occurred

ospf router received bad message type

[dec]

An internal software error occurred.

Bad refcount at [pointer] (refcount=[hex])

in [chars]

An internal software error occurred.

Resources may be in inconsistent state.

Managed Timer error, [chars]:

Unrecognized timer type [dec]

A timer was found with an unrecognized

type

Debug init error, [chars]: event [chars],

error [dec]

Unable to initialize a debugging flag

OSPF detected duplicate router-id [chars]

from [chars] on interface [chars]

OSPF received hello packet from a neighbor

which has the same router-id as this
routing process. A full adjacency cannot be
established.

No memory could be allocated for the

resource, [chars]

Allocation of the specified resource failed

because of a low memory condition. This
could affect the protocol functionality.

External Event Manager error, [chars], error A call to an external event manager
[chars] [[hex]]
function failed.

External Event Manager error, [chars]:

[chars] code [dec], error [chars] [[hex]]

A call to an external event manager

function failed. The impact of this error is
insignificant, unless the error condition
persists for a duration close to the minimal
DeadInterval used over all OSPF interfaces.

raw_conn momentarily not usable, [chars]

raw_conn not available to send the packet

External error, [chars]

An external software error occurred.

External error, [chars], error [hex]

An external software error occurred.

FRIS error, [chars], [chars] error [chars]

[[hex]]

The FRIS request failed.

IDB error, [chars]: [chars], intf [chars] cerr

[chars]

Error encountered while attempting to

activate an idb. Problem could be corrupt
data from IM or IP/ARM or the FRIS.

Interface [chars] is attached to more than

one area

An internal consistency check has failed.

An interface appears to be associated with
more than one area.

Interface init error, interface [chars]

OSPF failed to initialize data structures for

an interface.

External IFMGR error, [chars], intf [chars]

error [chars] [[hex]]

The specified interface manager request

failed.

IGP/TE error, [chars]: [chars] error [dec]

Error encountered while attempting to use

the IGP_TE Library.

Init error, [chars], error [hex]

An error occurred during initialization.

Initialization failure, [chars], error [chars],

process terminated

An error occurred during initialization,

causing the process to terminate.

Internal error, [chars]

An internal software error occurred.

Internal error, [chars], error [hex]

An internal software error occurred.

External IP-ARM error, [chars], error [chars]

[[hex]]
A call to an external IP-ARM function failed.

External light-weight msg error, [chars],

error [chars] [[hex]]

A call to an external light-weight

messaging function failed.

Multicast error, [chars] [chars] on [chars],

error [chars]

The above specified multicast operation

failed

Media error, [chars]: Interface [chars]

unknown type: [chars]

Media table lookup failed.

Mutex error, [chars], [chars] mutex, error

[chars] [[hex]]

An error occurred in the pthread functions

used for thread synchronization. This is
most likely a system error.

Flagged as being an ABR without a

backbone area

The router was flagged as an Area Border

Router (ABR) without backbone area in the
router.

No IP Addr on interface [chars]. OSPF will

not be run over it.

This message is displayed if ospf is

configured on an unnumbered interface
that is not of type point to point. In this
case, ospf will not run on this interface.

if [chars] if_state [dec]

An internal error occurred. An interface was

not fully initialized when an OSPF related
event occurred.

Cannot configure neighbor on [chars].

Interface must be NBMA or P2MP

Neighbor address cannot be configured on

the interface if it is not type NBMA or point
to multipoint.

NSR SYNC error: [chars], [chars], [chars],

[hex]

Error occurred during the NSR sync

between active and standby OSPF
processes.

Path-id out of range for [chars]/[dec]

An error was encountered when allocating

path-id for the path.

Raw socket error, [chars]: packet dropped, An input packet was dropped for the
[chars]
specified reason.

lsid [chars] adv [chars] type [dec] gateway

[chars] metric [dec] network [chars] mask OSPF found inconsistency between a
[chars] attr [hex] net-metric [dec]
database entry and its associated path.
OSPF process is being reset, and it is going
to select a new router-id. This will bring
OSPF process [chars] is changing router-id. down all virtual links. To make them work
Reconfigure virtual link neighbors with our again, virtual link configuration needs to be
new router-id
changed on all virtual link neighbors.

External RIB error, [chars], error [chars]

[hex]

A call to an external RIB function failed.

External RIB error, [chars]

A call to an external RIB function failed.

External RPC error, [chars], error [chars]

[[hex]]

An RPC error occurred

RSI library error, [chars], error [chars]

[[hex]]

A call to an external event manager

function failed.

External socket error, [chars], error [chars]

[[hex]]
The above specified socket operation failed

External SysDB error, [chars], error [chars] An external OSPF error occurred when
[[hex]]
accessing the system database.

Thread create error, [chars], error [chars]

[[hex]]

OSPF failed to create a thread essential to

its operation. This is an internal error. An
automatic restart of the OSPF process was
necessary to attempt recovery.

Reached unknown state in neighbor state

machine

An internal software error occurred. When

processing and DBD packet, the neighbor
was found to be in an indeterminate state.

Invalid length [dec] in OSPF packet from

[chars] (ID [chars]), [chars]

The system received an OSPF packet with a

length field of less than normal header size
or inconsistent with the size of the IP
packet in which it arrived. This indicates an
error in the sender of the packet.

The router received an LSA with invalid LSA

Type. The cause is either memory
Invalid lsa: [chars] Type [dec], LSID [chars] corruption or unexpected behavior on a
from [chars], [chars], [chars]
router.

Found LSA with the same host bits but

different mask. \n LSA with shorter mask
will be used. \n LSA 1: [chars]/[dec] \n LSA
2: [chars]/[dec]

An LSA could not be generated because

there is a supernet lsa with the host bit set
LSA ID that conflicts with the major net LSA
ID that also needs to have host bit set.

\router-id [chars]\ command has been

deprecated. Please delete \router-id
[chars]\ and reconfigure router-id.

OSPF router-id <interface> has been

deprecated.

At the time of the redistribution of BGP with

4 byte AS number, domain-tag wasn't
Domain-tag must be configured with 4-byte confiured. User needs to be aware that in
AS number in vrf [chars]
this case domain-tag must be configured.

OSPF failed to retrieve its local connection

ID for a client attached to the specified
Error retrieving client's connection ID to the channel. This is an internal programming
[chars] channel: [chars] ([dec])
error.

Error replying to the client [chars]: [chars]

([dec])

OSPF failed to reply to its client through

message channel. This could be a result of
channel down or resource allocation failure.

Received invalid packet: [chars] from

[chars], [chars]

An invalid OSPF packet was received.

Details are included in the error message.
The cause might be a misconfigured OSPF
or an internal error in the sender.

Unable to get interface index for [chars]:

[chars]

An error occurred when trying to get a

numeric interface index value for the
specified interface. Ietf nsf restart might
fail.

Key [unsigned long int] [chars]

An error occurred when trying to configure

an ospf authentication key.

Interface limit [dec] exceeded. Dropping

interface [chars]

The number of interfaces configured

exceeds the interface limit.

Maximum number of non self-generated

LSAs has been exceeded \[chars]\ - [dec]
LSAs

Maximum number of non self-generated

LSAs has been exceeded

Threshold for maximum number of non

self-generated LSAs has been reached \
[chars]\ - [dec] LSAs

Threshold for maximum number of non

self-generated LSAs has been reached

[chars] [chars] mutex ([pointer]), tid [dec]

owner [hex] count [dec], error [chars]
[[hex]]

An error has been returned by the

functions used for locking/unlocking an
OSPF synchronization mutex.

Neighbors were configured when NBMA or

P2MP. Changing network type will abandon
that configuration. Please remove
configured neighbors.

Neighbors had been configured earlier

when the network type was nonbroadcast.
The current configuration request will
cause these configured neighbors to be
abandoned.

Unexpected non-zero DR [chars] in hello

packet from [chars]

OSPF has received a hello packet with nonzero Designated Router field on an
interface that is not a multiaccess
interface. Indicates a misconfiguration of
network type among the OSPF routers in
the given subnet.

Received [chars] from unknown neighbor

[chars], vrf [chars] vrfid [hex]

OSPF hello, database description, or

database request packet was received, but
the router could not identify the sender.
This is a normal occurrance if a link flap
occurs on the router receiving the packet.

OSPF failed while attempting to allocate a

OSPF process [chars] cannot start without a router ID from the IP address of one of its
router id. Configure router-id with the
interfaces as no suitable IP address was
\router-id\ command.
available.
Command \[chars]\ has been upgraded by \ The command has been replaced by a
[chars]\. Use the new command.
newer command.

Pakman event [chars] received,

code=[dec], [chars]

An error has occurred and pak manager

sent us an event. If we can't recover from
the error (ABORT event), OSPF will exit.

An error was encountered configuring

policy, [chars]: [chars]

A problem was encountered while setting

up route policy configuration. Some of the
routing policy may not have been
configured correctly.

Raw socket output err: [chars], src=[chars], An error has occured when OSPF is in
dest=[chars], if=[chars], msglen=[dec],
process of sending a packet to the the raw
error [chars] [[hex]]
socket.

An error occurred while OSPF was setting

OSPF was unable to configure redistribution up redistribution for the named protocol.
for protocol [chars]
The redistribution will not take place.
Redistribution prefix limit has been reached We have reached the maximum number of
- [dec] prefixes
redistributed prefixes
Redistribution prefix threshold has been
reached - [dec] prefixes

We have reached the threshold level of

number of redistributed prefixes.

Router is currently an ASBR while having

only one area which is a stub area

Router is configured as an ASBR but is only

connected to a single stub area. This can
waste resources since the router has
nowhere to send the external LSAs that it is
generating.

OSPF process [chars] encountered an error

while finding a new router ID. The old
router ID [chars] is being used as an
interim value. \clear ip ospf process\ will
force another attempt to find a valid router
ID.

OSPF failed while attempting to allocate a

router ID from the IP address of one of its
interfaces due to an unexpected internal
problem.

Virtual link information found in nonbackbone area: [chars]

An internal error occurred.

Process [chars], Nbr [chars] on [chars] in

area [chars] from [chars] to [chars],
[chars], vrf [chars] vrfid [hex]

An OSPF neighbor has changed state. The

message describes the change and the
reason for it. This message appears only if
the <Bold>log-adjacencychanges<NoBold> command is configured
for the OSPF process.

Interface [chars], cost-fallback [chars],

metric [dec]

Cost-fallback activated or deactivated on

interface.

Process [chars]: [chars]

[chars]

Used for logging of HA events like process

startup, entry and exit of NSF/GR or NSR
procedures and related events.
First log upon process startup.

Checksum Failure in database in area

[chars] Link State Id [chars] Old Checksum OSPF has detected a checksum error in an
[hex] New Checksum [hex]
LSA due to memory corruption.

area [chars] lsid [chars] mask [chars] adv

[chars] type [dec]

OSPF has an invalid duplicate copy of an

LSA, which could lead to a memory leak.

[chars]

Informs user of graceful shutdown events.

User needs to be aware of these activities.

Process [chars]: [chars]

Used for logging of HA events like process

startup, entry and exit of NSF/GR or NSR
procedures and related events.

Process [chars] vrf [chars]: LSA refresh

interval changed. Old: [dec] New: [dec].
May take 10 minutes for the new interval
to be in effect.

User has changed the configuable LSA

refresh interval.

Current max-metric timer is running. \

[chars]\

One of the following applies 1. maximummetric LSA origination setting was changed
while the maximum-metric origination was
still active. The change will not take effect
until the next time the system is restarted.
2. no-abr-off configuration was removed
while in max-metric mode. The change will
not take effect until the next max-metric
event (process restart, migration or reload)
is seen. 3. no-abr-off configuration was
added while in max-metric mode. ABRdisable mode is exited immediately.

[chars] [chars].

An unexpected event from the system

monitor was seen.

External Managed Timer error, [chars],

error [chars] [[hex]]

An external managed timer support routine

failed. The affect this error has on the
proper operation of OSPF depends on
where and when this error occurred.

User has changed the configuable resource

[chars] limit changed. Old: [dec] New: [dec] limit.

build_ex_route(): don't redistribute net

[chars]/[dec], [chars] advertises it already

For information only. Another router with a

greater router ID is advertising the same
external LSA. This router will stop
originating the LSA to eliminate the
redundancy.

Reference bandwidth is changed. Please

ensure reference bandwidth is consistent
across all routers.

Informational message reminding the user

that reference bandwidth should be
consistent across all routers in the area.

Message-digest is used when both it and

cleartext password are configured

Inform user that when both a clear text

password and message-digest key are
configured the message-digest key will be
used.

[chars]: Unexpected external ReadyQ count

of 0, &db=[hex], &rtr=[hex]
An internal software error occurred

InReadyQ flag set for external DB, db

[chars] on rtr_rt [chars]

An internal software error occurred

dld [chars] is NULL

An internal software error occurred

Double link queue count is 0 before

decrement, &queue=[hex]

An internal software error occurred

TE IDB error, [chars], [chars] error [chars]

[[hex]]

Error in creating a tunnel interface.

Initialization failure, [chars], process

terminated

An error occurred during initialization,

causing the process to terminate.

[chars]

An error was encountered during OSPF

operation and a traceback was produced.

VRF delete error [chars] [chars] [chars]

An internal software error occurred

Failed to add an external data manager

datalist for [chars]

A process has requested information

through SysDB, probably as the result of
executing a show command. The attempt
to add an item to an external data
manager datalist has failed.

Failed to create external data manager

datalist for [chars]

A process has requested information

through SysDB, probably as the result of
executing a show command. The creation
of the external data manager datalist has
failed.

Failed to set external data manager more

flag for datalist [chars]

A client has requested information through

SysDB from OSPF. During execution of the
request an attempt to set a flag indicating
there is more data for the client failed.

Error initializing EDM thread: [chars]:

[chars]

An error occurred during initialization of the

EDM thread.

Failed to encode [chars] data in external

data manager

A process has requested information

through SysDB, probably as the result of
executing a show command. The data
requested could not be encoded.

Failed to connect to the event manager:

[chars]

The process failed while attempting to

connect to an event manager channel for
the indicated subsystem.

Failed to add to an external data manager

list for [chars]

A process has requested information

through SysDB, probably as the result of
executing a show command. The attempt
to add an item to an external data
manager list has failed.

A process has requested information

through SysDB, probably as the result of
executing a show command. The creation
Failed to create external data manager list of the external data manager list has
for [chars]
failed.

Data for [chars] is not available

The data needed for the specified OSPF

show command was not available. This
would occur for non-critical data such as
trace or debug information.

Failed to register show protocol information OSPFv3 was unable to register for support
: [hex], '[chars]'
of the show protocol command.

Failed to register its [chars] external data

manager, '[chars]'

The process failed when attempting to

register its external data manager with
SysDB.

Failed to connect to SysDB ([chars])

The process failed to connect to SysDB

while starting the indicated subsystem.

Failed to convert during a conn to coid

conversion

The process failed to convert a conn to a

coid while starting the indicated
subsystem. This generally can only occur
when starting up.

The process failed while attempting to

Failed to register its external data manager register its external data manager data
data blocks
blocks with SysDB.

Failed to build [chars], reason [chars] cer

[chars]

Internal error in policy library.

Could not apply policy operation [chars] to

attribute [chars] because [chars]
Internal error in policy library.

Unable to allocate space for rib batching

buffer: No Memory

Insufficent memory to allocate buffer for

RIB batching API'

Unable to bind to the RIB

An error occurred on a request to bind to

the RIB.

Unable to register with the RIB to receive

the default route: [chars]

An error occurred on a request to have the

RIB send us route updates for the default
route.

Error while disconnecting RIB Event

connection

An error occurred during an attempt to tear

down the RIB Event connnection.

Error informing rib that batch is complete

An error was encountered in the call to

ipv6_rib_batch_buffer_complete.

Error adding path-add to batching buffer

(#[hex])

An error was encountered in the call to

ipv6_rib_batch_add_path.

Error adding path-delete to batching buffer An error was encountered in the call to
([hex])
ipv6_rib_batch_delete_path.

Error adding route header to batching

buffer for [chars]/[dec] ([hex])

An error was encountered in the call to

ipv6_rib_batch_add_route.

Error informing rib that update is complete: An error was encountered in the call to
[chars]
ipv6_rib_update_complete.

Unable to get a RIB handle for [chars]

routes: [chars]

An error occurred on a request to find the

handle for the specified type of routes.

Error removing OSPFv3 routes from the

IPv6 RIB: [chars]

An error was encountered in the call to

ipv6_rib_purge_protocol.

Unable to register with the RIB to receive

updates for [chars] routes: [chars]

An error occurred on a request to have the

RIB send us route updates for the specified
type of routes.

Unable to register OSPFv3 with the RIB:

[chars]

An error occurred on a request to register

the OSPFv3 protocol with the RIB.

Failed to register internal error codes:

[chars]

An error occurred during the registration of

OSPFv3 error codes.

Error initializing ospfv3_uv debugging:

[chars]

An error occurred during initialization of the

ospfv3_uv process.

Failed to allocate %zu bytes for '[chars]'

The ospfv3_uv process was unable to

allocate memory for the specified resource.

Error signaling process ready: [chars]

The ospfv3_uv process was unable to signal

process ready to sysmgr.

Error binding to SysDB: [chars]

The ospfv3_uv process was unable to bind

to SysDB.

Error unbinding from SysDB: [chars]

The ospfv3_uv process was unable to

unbind from SysDB.

Error registering with SysDB: [chars]

The ospfv3_uv process was unable to

register with SysDB.

Error setting SysDB callback functions:

[chars]

The ospfv3_uv process was unable to

initialize SysDB callbacks.

Error in event loop: [chars]

An error occurred in the main ospfv3_uv

event loop.

Error creating event connection manager:

[chars]

The ospfv3_uv process was unable to

create an event connection manager
instance.

Error initializing forward-reference store:

[chars]

The ospfv3_uv process was unable to

initialize the forward-reference store library.

Caution: The OSPFv3 process name \

[chars]\ conflicts with a show or clear
command name

The name chosen for the OSPFv3 process

matches an ospf show or clear command,
or a command abbreviation. This can cause
ambiguities with subsequent show or clear
commands for this process.

No memory for [chars]

The requested operation could not be

accomplished because of a low memory
condition.

Unable to get prefix-list [chars]: [chars]

An error occurred when trying to get the

named prefix-list.

An error occurred when trying to register

Unable to register prefix-list [chars]: [chars] for changes to the named prefix-list.

[chars] allocation failed: [chars]

Allocation of the specified resource failed,

probably due to low memory.

A lower-level support function returned an

Call to [chars] from [chars] returns: [chars] unexpected status.

Router thread received an invalid message

type: [dec]
An internal software error occurred.

Unrecognized [chars] timer type [dec]

A timer was found with an unrecognized

type

Failed to register internal error codes:

[chars]

An error occurred during the registration of

OSPFv3 error codes.

Unable to connect to server [chars] :

[chars]

OSPFv3 was unable to open a connection

to a server. This is an internal error.

Debug event initialization failed: [chars]

Unable to initialize a debugging flag.

Debug registration failed: [chars]

Unable to initialize debugging flags. Debug

commands will not function.

Cannot delete virtual link, backbone is

being deleted

The virtual link cannot be removed

because OSPFv3 is in the process of
deleting the backbone area. Try again later.

dld [chars] is NULL

An internal software error occurred

Detected duplicate router ID [chars] from

[chars] on interface [chars]

OSPFv3 received hello packet from a

neighbor which has the same router ID as
this routing process. A full adjacency
cannot be established.

Detected router with duplicate router ID

[chars] in area [chars]

OSPFv3 has received multiple router LSAs

with our router ID.

Detected router with duplicate router ID

[chars] in inter-area router LSA advertised
by [chars]

OSPFv3 has received an inter-area router

LSA with our router ID.

Event blocking error in [chars] thread:

[chars]

An error occurred while a thread was

blocked waiting for an event. *RECUR*

A call to an external event manager

function failed. The impact of this error is
insignificant, unless the error condition
persists for a duration close to the minimal
External Event Manager error, [chars], error DeadInterval used over all OSPFv3
[chars] [[hex]]
interfaces.

Error obtaining the [chars] file descriptor:

[chars]

A call to get the file descriptor associated

with an event manager connection failed.

Unable to set event manager retry values

for the [chars] connection: [chars]

A call to the external event manager to set

connection retry values failed.

External error, [chars]

An external software error occurred. This is

a non-OSPFv3 errors triggered from
external DLLS, libraries, or inter-process
calls.

External error, [chars], error [hex]

An external software error occurred. This is

a non-OSPFv3 errors triggered from
external DLLS, libraries, or inter-process
calls.

Unable to insert interface [chars] in the

forward reference list: [chars]

An error occurred when adding the

interface to the forward-reference list.

Error initializing hello thread: [chars]:

[chars]

An error occurred during initialization of the

hello thread.

Unable to get interface index for [chars]:

[chars]

An error occurred when trying to get a

numeric interface index value for the
specified interface.

Initialization failure for interface [chars]

OSPFv3 failed to initialize data structures

for an interface.

[chars] failed: [chars]

The specified interface manager request

failed.

[chars] failed for interface [chars]: [chars]

The specified interface manager request

failed.

Initialization failed [[chars]], process

terminated

An error occurred during initialization,

causing the OSPFv3 process to terminate.

Init error, [chars], error [hex]

An unexpected error occurred during

initialization.

Unable to register for package installation

notifications: [chars]

An error occurred when trying to register

with the packaging subsystem.

Unable to unregister for package

installation notifications: [chars]

An error occurred when trying to unregister

with the packaging subsystem.

Internal error: [chars]

An internal software error occurred.

Internal error, [chars], error [hex]

An unexpected internal software error

occurred.

[chars] failed: [chars]

The specified IP/ARM request failed.

[chars] failed for interface [chars]: [chars]

The specified IP/ARM request failed.

Error terminating IPSec processing for

interface [chars]: [chars]

An error occurred when trying to close an

IPSec SA for the named interface.

Unable to initialize ipsec debugging:

[chars]

An error occurred when trying to initialize

the ipsec debug commands.

Error initializing IPSec support: [chars]%s

An error occurred when trying to initialize

the OSPFv3 IPSec subsystem.

Error initiating IPSec processing for

interface [chars]: [chars]

An error occurred when trying to open an

IPSec SA for the named interface.

External light-weight msg error, [chars],

error [chars] [[hex]]

A call to an external light-weight

messaging function failed.

Multicast [chars] on [chars] failed: [chars]

The specified multicast operation failed.

Failed to allocate %zu bytes for '[chars]'

OSPFv3 was unable to allocate memory for

the specified resource.

Error [chars] for [chars] mutex: [dec]

A error occurred in the initialization of the

primitives used for thread synchronization.
This is most likely a system error.

Unable to add host route for virtual link

endpoint in area [chars]

No IPv6 address was available to use as an

endpoint for a virtual link.

Flagged as being an ABR without a

backbone area

The router was flagged as an Area Border

Router (ABR) without backbone area in the
router.

Interface [chars] if_state [dec]

An internal error occurred. An interface was

not fully initialized when an OSPFv3 related
event occurred.

Cannot configure neighbor on [chars]:

interface must be NBMA or P2MP

Neighbor address cannot be configured on

interface if it is not type NBMA or point to
multipoint.

NSR SYNC error: [chars], [chars], [chars],

[hex]

Error occurred during the NSR sync

between active and standby OSPFv3
processes.

Packet dropped: [chars]

An input packet was dropped for the

specified reason.

Packet dropped: [chars]: [chars]

An input packet was dropped for the

specified reason.

Error initializing OSPFv3 process: [chars]:

[chars]

An error occurred during OSPFv3 process

initialization.

[chars] [chars]/[dec]: [chars] (rc [dec])

An error occurred on a request to the RIB.

Failed to modify purgetime with V6 RIB. Old An error occurred on a request to modify
[dec] New [dec]: [dec]
the purge time in RIB.

RSI library error, [chars], error [chars]

[[hex]]

A call to an external event manager

function failed.

Error initializing router thread: [chars]:

[chars]

An error occurred during initialization of the

router thread.

Socket operation [chars] failed: [chars]

The specified socket operation failed.

SysDB error: [chars]([chars]): [chars]

An error occurred when accessing the

system database.

[chars] failed: [chars]

A specified system manager request failed.

Error starting [chars] thread: [dec]

OSPFv3 failed to create a thread essential

to its operation. This is an internal error. An
automatic restart of the OSPFv3 process
was necessary to attempt recovery.

Unicast [chars] on [chars] failed: [chars]

The specified unicast filter operation failed.

Reached unknown state in neighbor state

machine

An internal software error occurred. When

processing a DBD packet, the neighbor was
found to be in an indeterminate state.

The interface type is not yet supported by

Unsupported interface type [chars]: [chars] OSPFv3.

Received invalid packet: Incorrect area

number ([chars]) from [chars], [chars]

The system received an OSPFv3 packet

with an area ID that does not match the
area that the interface belongs to.

Received invalid packet: Incorrect length

([dec]) from [chars], [chars]

The system received an OSPFv3 packet

with a length field of less than normal
header size or inconsistent with the size of
the IPv6 packet in which it arrived. This
indicates an error in the sender of the
packet.

The router received an invalid LSA. The

Invalid LSA: [chars], Type [hex] LSID
cause is either memory corruption or
[unsigned int] from [chars], [chars], [chars] unexpected behavior on a router.

Received invalid packet: Incorrect OSPF

version ([dec]) from [chars], [chars]

The system received an OSPFv3 packet

with an OSPF version field other than 3.
This indicates an error in the sender of the
packet.

\router-id [chars]\ command has been

deprecated. Please delete \router-id
[chars]\ and reconfigure router-id.

OSPFv3 router-id <interface> has been

deprecated.

Received invalid packet: [chars] from

[chars], [chars]

An invalid OSPFv3 packet was received.

Details are included in the error message.
The cause might be a misconfigured
OSPFv3 or an internal error in the sender.

Database error: [chars], Type [hex] LSID

[unsigned int] from [chars]

OSPFv3 detected an error with its link state

database.

Unable to initialize the ltrace buffer [chars]: An error occurred when trying to create a
[chars]
buffer for tracing.

Neighbor ID configuration requires nonbroadcast or NBMA network type

An OSPFv3 neighbor ID has been

configured over an invalid network type.

Unexpected non-zero DR [chars] in hello

packet from [chars]

OSPFv3 has received a hello packet with

non-zero Designated Router field on an
interface that is not a multiaccess
interface. Indicates a misconfiguration of
network type among the OSPFv3 routers in
the given subnet.

Received [chars] from unknown neighbor

[chars] on [chars]

OSPFv3 hello, database description, or

database request packet was received, but
the router could not identify the sender.
This is a normal occurrance if a link flap
occurs on the router receiving the packet.

OSPFv3 process [chars] could not pick a

router-id, please configure manually

OSPFv3 failed while attempting to allocate

a router ID.

Packet dropped: [chars]

An input packet was dropped for the

specified reason.

An error was encountered configuring

policy, [chars]: [chars]

A problem was encountered while setting

up route policy configuration. Some of the
routing policy may not have been
configured correctly.

Redistribution prefix limit has been reached We have reached the maximum number of
- [dec] prefixes
redistributed prefixes
Redistribution prefix warning threshold has We have reached the warning threshold
been reached - [dec] prefixes
number of redistributed prefixes.

Socket operation [chars] failed: [chars]

The specified socket operation failed.

Router is currently an ASBR while having

only one area which is a stub area

Router is configured as an ASBR but is only

connected to a single stub area. This can
waste resources since the router has
nowhere to send the external LSAs that it is
generating.

OSPFv3 process [chars] encountered an

error while finding a new router ID. The old
router ID [chars] is being used as an
interim value.

OSPFv3 failed while attempting to allocate

a router ID from the IPv4 address of one of
its interfaces due to an unexpected internal
problem.

Virtual link information found in nonbackbone area: [chars]

An internal error occurred.

An OSPFv3 neighbor has changed state.

The message describes the change and the
reason for it. This message appears only if
the <Bold>log-adjacencyProcess [chars], Nbr [chars] on [chars] from changes<NoBold> command is configured
[chars] to [chars], [chars]
for the OSPFv3 process.

Process [chars]: [chars]

[chars]

Used for logging of events like process

startup, entry and exit of GR events.
First log upon process startup.

Area [chars] is being deleted, please try

later

The configuration command could not be

accepted because OSPFv3 is in the process
of deleting the specified area. Try again
later.

Error creating area [chars]: [chars]

An error was encountered when trying to

create an area.

Checksum Failure in database: area [chars]

LSA type [hex] LSID [hex] adv rtr [chars]: OSPFv3 has detected a checksum error in
Old Checksum [hex] New Checksum [hex] an LSA due to memory corruption.

[chars]

Informs user of graceful shutdown events.

User needs to be aware of these activities.

Process [chars]: [chars]

Used for logging of HA events like process

startup, entry and exit of NSF/GR or NSR
procedures and related events.

External Managed Timer error, [chars],

error [chars] [[hex]]

An external managed timer support routine

failed. The affect this error has on the
proper operation of OSPF depends on
where and when this error occurred.

OSPFv3 process is being reset, and it is

going to select a new router-id. This will
OSPFv3 process [chars] is changing router- bring down all virtual links. To make them
id. Reconfigure virtual link neighbors with work again, virtual link configuration needs
our new router-id
to be changed on all virtual link neighbors.
Reference bandwidth is changed. Please
ensure reference bandwidth is consistent
across all routers.

Informational message reminding the user

that reference bandwidth should be
consistent across all routers in the area.

Failed to [chars] : [chars]

Internal error.

Mrib library Initialization failed: [chars]

[chars]

An unrecoverable error occurred at system

initialization time.

Failed to add LC [dec] into FGID [dec]:

[chars]

Internal error.

Failed to [chars]: [chars]

Internal error.

Failed to remove LC [dec] from FGID [dec]:

[chars]
Internal error.

Failed to open a file [chars] to dump the

[chars] database

Internal error.

Failed to [chars] : [chars]

Internal error.

im_interface_name error in function [chars]

: [chars]
Internal error.

Failed to [chars]

Init error.

[chars] : [chars]

Internal error.

Failed to [chars] : invalid fgid value [hex]

Internal error.

Failed to [chars] for [chars]

Internal error.

Failed to [chars]

Internal error.

Fabric Manager returned error for one or

more transactions. [chars] [chars]

Internal error.

[chars]%s

Connection error with IM or PIM.

[chars]%s[chars]

Internal error.

[chars] failed : '[chars]'

PIM Netio dll failed initialization or

registration with the debugging subsystem.
This resulted in the restart of NetIO
process.

Failed to build [chars]: [chars] ([chars])

Internal error in the routing policy library.

There was an internal error in the routing

Failed to build ORA[chars]: [chars] ([chars]) policy library.

Could not apply policy operation [chars] to

attribute [chars] because [chars]
Internal error in the routing policy library.

An error was encountered as the node

location was being added to the attach
point item. This will prevent the successful
Cannot add node location:[chars] protocol: registration for this attach point and will
[chars], version:[chars], ap_name:[chars]
leave this configuration space unverified
because [chars]
with respect to policy configuration.

An error was encountered as attach point

data was being created. This could cause
problems with future configuration
attempts, and it does indicate an internal
Cannot create attach point data for
inconsistency so it might be best to restart
dynamic registration item:[chars] because the policy_repository to try to clear this
[chars]
inconsistency.

Cannot extract [chars] data for protocol:

[chars], version:[chars], ap_name:[chars],
because [chars]

An error was encountered as data was

being extracted for the registration of this
attach point. As such, the registration
failed and the verification of configuration
related to this attach point registration will
NOT be performed. Thus, configuration
could be accepted but could be unable to
be processed by the protocols.

An error was encountered as attach point

data was being deleted. This could cause
problems with future configuration
attempts, and it does indicate an internal
inconsistency so it might be best to restart
Cannot delete attachpoint data for dynamic the policy_repository to try to clear this
registration item:[chars] because [chars]
inconsistency.

An error was encountered as new attach

point data was being docked. As a result,
the new data has not been activated for
Cannot dock new data for protocol:[chars], this attach point. At this point is would be
version:[chars], ap_name:[chars], because: best to restart the policy_repository to try
[chars]
to clear this inconsistency.

Cannot find data for protocol: [chars],

version: [chars], ap_name: [chars] during
[chars] operation because [chars]

An error was encountered as we were

looking up data for the above attach point.
The operation in question do not succeed
since we could not find this entry, and thus
the policy_repository could be in an
inconsistent state.

An error was encountered as attach point

data was being registered for verification.
Cannot register attach point data for
At this point is would be best to restart the
dynamic registration item: [chars] because policy_repository to try to clear this
[chars]
inconsistency.

Cannot undock old [chars] data for

protocol:[chars], vers':[chars], ap_name:
[chars] because:[chars]

An error was encountered as old attach

point data was being undocked for new
data. As a result, the old data is either still
activated, or NO data is activated for this
attach point. As this point is would be best
to restart the policy_repository to try to
clear this inconsistency.

An error was encountered as old attach

point data was being unregistered for new
data. As a result, the registration for the
Cannot unregister the old attach point data old data is still activated for this attach
(for verification) for protocol: [chars],
point. As this point is would be best to
version: [chars], ap_name: [chars] because restart the policy_repository to try to clear
[chars]
this inconsistency.

An error was encountered as new attach

point data was being swapped out for old
data. As a result, the old data is either still
activated, or NO data is activated for this
Cannot install the new attach point data for attach point. As this point is would be best
protocol: [chars], version: [chars],
to restart the policy_repository to try to
ap_name: [chars] because [chars]
clear this inconsistency.

Cannot find attach point data for a [chars]

for protocol: [chars], version: [chars],
ap_name: [chars] because [chars]

An error was encountered as we were

looking up data for the above attach point.
The operation in question did not succeed,
and thus the policy_repository could be in
an inconsistent state.

An error was encountered as old attach

point data was being unloaded for new
data. As a result, the old data is either still
activated, or NO data is activated for this
Cannot unload the old attach point data for attach point. As this point is would be best
protocol: [chars], version: [chars],
to restart the policy_repository to try to
ap_name: [chars] because [chars]
clear this inconsistency.

We have detected a condition where there

are conflicting registration values for
protocol: [chars], version: [chars],
ap_name: [chars]. Swapping out the
current values for new values

An error was encountered as the node

location was being added to the attach
point item. This will prevent the successful
registration for this attach point and will
leave this configuration space unverified
with respect to policy configuration.

policy_repository cannot encode [chars]

data in external data manager

A process has requested information

through SysDB, probably as the result of
executing a show command. The data
requested could not be encoded.

policy_repository is unable to bind to sysdb The process failed to connect to SysDB

because [chars]
while starting the indicated subsystem.

policy_repository cannot generate [chars]

data in external data manager

A process has requested information

through SysDB, probably as the result of
executing a show command. The data
requested could not be generated.

policy_repository cannot add to external

data manager list for [chars]

A process has requested information

through SysDB, probably as the result of
executing a show command. The attempt
to add an item to an external data
manager list has failed.

policy_repository cannot create external

data manager list for [chars]

A process has requested information

through SysDB, probably as the result of
executing a show command. The creation
of the external data manager list has
failed.

policy_repository cannot register its

external data manager with sysdb

The process failed when attempting to

register its external data manager with
SysDB.

policy_repository is unable to disconnect

with sysdb because [chars]

The process failed to disconnect from

SysDB before starting the indicated
subsystem.

The process failed while attempting to

Failed to register its external data manager register its external data manager data
data blocks
blocks with SysDB.

policy_repository cannot allocate memory

for [chars]

The policy_repository process failed

allocated memory for the operation
specified.

Failed to dock with ORA [chars], version =

[chars], location = [chars], path = [chars]
because: [chars]. This will result in NO
policy being monitored or processed for
this client

The policy_repository process, while trying

to dock with the client ORA encountered an
error that is specified in the error message.

policy_repository in inconsistent state

because : [chars] ([chars])

The user is trying to do an operation which

encountered inconsistent state for a policy
object

The system is attempting to process a

policy_repository object ([chars]) cannot be policy object set or named policy and
decoded because ([chars])
cannot decode the object.

policy_repository cannot connect to the

sysdb '[chars]' because [chars]

The policy_repository process failed to bind

to the system database at the displayed
bind point.

Cannot retrieve configuration item : [chars] The policy_repository process failed to

from sysdb (Reason: [chars])
retrieve an item from the system database.

The policy_repository process failed to

policy_repository cannot register for sysdb register for notification of changes on the
notifications at: [chars] (Reason: [chars])
displayed database path.

Cannot register for sysdb verifications at

location : [chars] (Reason: [chars])

The policy_repository process failed to

register for verification of changes on the
displayed database path.

Policy parser DLL: [chars]: [chars]

A system call failed inside the routing

policy parser DLL.

policy_repository cannot clean up policy

'[chars]' ([chars])

When deleting the specified policy, the

policy_repository process encountered a
problem. This could leave memory unfreed.

RPL editor: [chars]

A system call failed inside the RPL editor

program.

policy_repository cannot delete policy

[chars] (Reason: [chars])

The policy_repository process encountered

an error while trying to remove the data for
a deleted policy.

An error occurred while trying to get the

system [active/standby] state. A state of
REDUNDANCY_UNKNOWN will be assumed.
This process also registers for notification
of changes to the [active/standby] state.
Thus, the state can be determined by this
means as well. Failure to receive
notification for either one of these means
could result in this process not functioning
properly. Note At least one of the processes
Failed to receive the [active/standby] state in an active/standby pair must be active in
indication. Error: [chars]
order to assure proper functioning.

Argument list mismatch for statement

'[chars] [chars]' in policy [[chars]].

The user is trying to do an operation in

which the number of arguments entered
does not match the number of argument
expected.

Failed to associate [chars] attach point

item '[chars]' to policy [chars]. This will
leave the policy repository in an
inconsistent state.

The policy_repository process was not able

to add the attach point to the policy in
question. This means that the policy
repository will not verify the statements in
this policy against the attach point in
question. This could allow statements to be
added to the policy that (could) result in
run time errors in the client at this attach
point.

Failed to process [chars] attach point item

'[chars]' because [chars]. This will leave
the policy repository in an inconsistent
state.

The policy_repository process was not able

to extract the policy name OR id value for
this attach point path. This means that the
policies that are actually using this attach
point will NOT be recorded and thus
policies *could* be deleted while still in
use.

policy_repository failed to initialize [chars]. The policy_repository was atempting to

Error ([hex]): [chars]
initialize a data object and failed.

Failed to rebuild the [chars] data. Error

([hex]): [chars]

The system was atempting to rebuild an

object and it failed.

The item of type [chars] and value ([dec])

is not recognized by policy_repository.

The policy_repository process was not able

to extract the the item for this type. Please
add support to the policy_repository or
remove support from the protocols.

Policy [[chars]] contains a large number of

statements and would cause the policy
repository to exceed resource limits. The
policy repository is now inconsistent with
the running configuration. To regain
consistency, rollback to the previous
configuration for this policy.

The policy named is very long and/or

complex, and in compiling it for execution,
the policy repository exhausted resource
limits. This was not detected by the usual
checks at configuration verification time.
Rather than crash, the policy repository is
left with the previous configuration for this
policy, if any.

policy_repository encountered an internal

inconsistency in rebuilding sets for policy
[chars] (Reason: [chars])

The policy_repository process failed to

rebuild the set references for the policy in
question. This will result in an inconsistent
state in the policy_repository and the
process should be restarted. This could
result in policies not functioning properly.

The policy_repository process, while

verifying a change to a policy, encountered
an error while checking the validity of the
Policy [[chars]] failed verification for use in change in the policies that are applied by
policy [[chars]]
that policy.

ORAA retriever function to compare route

attributes not present.

This is a logic error in the construction of

one of the ORA entities. The function to
actually perform the compare retriever
operation was not defined.

This is a logic error in the construction of

one of the ORA entities. A compare
ORAA function to compare route attributes function was missing at the 'per route' level
not present.
of detail.

ORAA retriever function not present

This is a logic error in the construction of

one of the ORA entities. The function to
actually perform the retriever operation
was not defined.

ORAA function to set route attributes not

present.

This is a logic error in the construction of

one of the ORA entities. The function to
actually perform the setter operation was
not defined.

Unable to register cerrno dll [chars]

because [chars]

The given cerrno dll could not be marked

for use. This does not change the
functionality of the system but does
obscure the meaning of error codes
presented by this part of the system.

ORAA function to compare 2 routes not

present.

This is a logic error in the construction of

one of the ORA entities. The compare for
checking two different route values against
each other was missing.

The debug event initialization failed. The

Unable to bring up debug event structures: rasf will still run correctly, but debug
[chars]
commands may be unavailable.
Unable to shutdown debug event
structures: [chars]

The debug shutdown failed. The rasf will

still run correctly, but debug commands
may be unavailable.

RCMD Lib found version mismatch marker

[dec] type [dec]

A version mismatch detected by RCMD, the

message was discarded.

RCMD Lib initialization failure for [chars] in An error occurred during RCMD library
component [dec] error [dec]([chars])
intialization, causing the process to restart.

RCMD Prefix monitoring list config in

component [dec] error [dec]([chars])

The prefix list configured for Prefix

monitoring errored. Retry after sometime.

The prefix list configured for Prefix

monitoring matches more than
RCMD Prefix monitoring limit reached, max recommended number of prefixes. This
of [dec] prefixes
affects the routing convergence.

IP Frr Coverage for Protocol \[chars]\ VRF \

[chars]\ AFI \[chars]\ SAFI \[chars]\ SPF \
[unsigned int]\ Priority \[chars]\ is
[unsigned int]% below configured threshold Threshold configured for RCMD Frr
value of [unsigned int]%
Coverage monitoring was reached.

MPLS LDP Label Coverage for Remote Node

Sessions in Remote-LFA Event \[unsigned
int]\ is [unsigned int]% below configured
Threshold configured for RCMD Label
threshold value of [unsigned int]%
Coverage monitoring was reached.

Threshold for Protocol \[chars]\ VRF \

[chars]\ AFI \[chars]\ SAFI \[chars]\ SPF \
[unsigned int]\ Priority \[chars]\ is \
[unsigned int]\ msec above configured
threshold value of \[unsigned int]\ msec

Threshold configured for RCMD monitoring

was exceeded. This notification can be
monitored by RCMD diagnostics mode to
trigger collection of additional debugging
data.

Error occured for uploading report [dec]

([chars])

Transfer of RCMD report for archival

purpose has failed.

RCMD Assert - [chars], [dec], [dec], [dec],

[dec], [dec], [dec]

Provides information about the assert in

RCMD.

Found duplicate inst id [dec], Protocol

[chars], Current Name [chars], New Name
[chars]

This indicates that RCMD has detected a

duplicate instance of the protocol that it is
monitoring. It is a very rare condition
arising out of a race condition and can
affect RCMD feature working.

Initialization failure [dec]([chars]), process An error occurred during initialization,

terminated
causing RCMD process to restart.

Memory leak for type [chars] count

[unsigned int] activity [unsigned long long
int] / [unsigned long long int] / [unsigned
int]
Memory issue found in RCMD process.

Invalid string size requested [dec]

Internal error due to request for string size

larger than supported.

Invalid configuration exists for non-linecard

Invalid Configuration for Node Diagnostics - location. Diagnostics configuation can be
[chars]
only for linecard slots.

Maximum size applicable only for local

storage. Config will be ignored for TFTP
storage.

Provides information about the maximum

size configuration cannot be apllied for tftp
storage.

NTP Time drifted for New Instance, Process

[chars] Instance Name [chars] Create Time Provides information about the NTP time
[chars]
drift in RCMD.

Throttled trigger for collection

RCMD is ignoring a trigger for collecting

convergence information since collection is
already in process or has been recently
collected.

Starting/Restarting RCMD Server process

Provides indication that the RCMD feature

has been enabled and monitoring is
starting

[chars] [dec] [chars] [chars]\n

Internal error. Retry debug library

initilization failed

[chars] Pthread [chars], unexpected fatal

error [[chars]]

An unexpected fatal error occured when

trying operate on a pthread lock.

Error fetching RIB update - [chars]

Unexpected error fetching a RIB update

notification. See error message for more
information.

A client passed a pointer to rib_bind which

RIB client binding with a non-NULL
points to a non-NULL connection. This
connection handle. Potential client memory implies a connection leak in the client
leak.
code.

Failed to [chars] during client unbind [chars]

Unexpected error during client unbind

operation. This may result in a resource
leak.

A failure occurred during the registration of

the DLL for decoding error codes from the
Failure registering cerrno DLL with subsys component. This may render certain codes
num [unsigned int] and DLL name [chars]. unprintable, but otherwise has no negative
Error: [chars] ([hex])
impact.

There was an internal error in the routing

Failed to build policy operation '[chars]' for policy library and as a result routing policy
attribute '[chars]'.[chars]%s ([hex])
may not be applied correctly.

There was an internal error in the routing

policy library and as a result routing policy
Failed to build ORA: [chars]; [chars] ([hex]) may not be applied correctly.

There was an internal error in the routing

Could not apply policy operation '[chars]' to policy library and as a result routing policy
attribute '[chars]': [chars] ([hex])
may not be applied correctly.

A RIB download client (typically

bcdl_agent), unregistered from a table
while it was out of sync with its parent. The
Child [chars] ([chars]) ([dec]) unregistering number of routes may no longer be insync
from Vrf: \[chars]\ Tbl: \[chars]\ Safi: \
in all FIBs. If corresponding bcdl_agent
[chars]\, table id [hex], is not caught up
restarted just before this message was
with parent. Route inconsistency possible seen, this error message can be ignored.

A RIB download client (typically

bcdl_agent), reregistered from a table while
it still has children referring to this table.
The number of routes may no longer be
Parent [chars] ([chars]) ([dec])
insync in all FIBs. If corresponding
reregistering for Vrf: \[chars]\ Tbl: \[chars]\ bcdl_agent restarted just before this
Safi: \[chars]\, table id [hex], it still has
message was seen, this error message can
[dec] dependants
be ignored.

A RIB download client (typically

bcdl_agent), unregistered from a table
while it still has children referring to this
table. The number of routes may no longer
Parent [chars] ([chars]) ([dec])
be insync in all FIBs. If corresponding
unregistering from Vrf: \[chars]\ Tbl: \
bcdl_agent restarted just before this
[chars]\ Safi: \[chars]\, table id [hex], it still message was seen, this error message can
has [dec] dependants, context [chars]
be ignored.
Protocol batch [chars] from client [dec] for An error has occured processing protocol
table [hex] protocol [hex] failed: [dec]
register batch from a RIB client.

Client \[chars]\ has last signalled version

[dec] which is less than the RIB version
[dec] for Vrf: \[chars]\ Tbl: \[chars]\ Safi: \
[chars]\

A client updated the RIB for convergence

but not with the latest version as known by
RIB. This will have delayed or prevented
the convergence of the routing table, and
hence the purging of any stale routes from
the forwarding table.

Path add exceed max number of paths

supported by protocol. Table [hex], prefix
[chars]/[dec], protocol [chars], intf [hex],
tunnelid [dec], nexthop_table [hex],
nexthop [chars]

Protocol has registered for no ecmp support

but is adding more than one path for a
route.

Path add exceed max number of paths

supported by hardware. Table [hex], prefix
[chars]/[dec], protocol [chars], intf [hex],
tunnelid [dec], nexthop_table [hex],
Protocol is trying to add more than
nexthop [chars]
supported number of paths for a route.
[chars] [dec], line [dec], client [chars]
([dec]) table [hex] Vrf: \[chars]\ Tbl: \
[chars]\ Safi: \[chars]\

An unexpected error occured when trying

to add a path to the next-hop database.

Path delete failure for Table [hex], prefix

[chars]/[dec], protocol [chars], intf [hex],
tunnelid [dec], nexthop_table [hex],
nexthop [chars]

An error occured when trying to delete a

path from a route.

Pthread lock [chars], unexpected fatal error An unexpected fatal error occured when
[[chars]]
trying operate on a pthread lock.
Table [hex], prefix [chars]/[dec], intf [hex], An unexpected lookup error occured when
unexpected lookup results in [chars]
trying to lookup a prefix.

Failed to allocate memory for RIB

operations

Failed to allocate memory for RIB

operations probably out of memory
because of huge configuration or a
memory leak.

[chars]

An unexpected error occured when trying

to clear redist information for a client.

Mutex [chars], context '[chars]',

unexpected fatal error [[chars]]

An unexpected fatal error occured when

trying to lock or unlock a RIB mutex.

[chars]

An unexpected error occured, a nexthop

which is a RIB-only nexthop should not
have path information but has.

[chars], table [hex]

An unexpected nh notification packing

error occured.

Could not add [chars] to nh db for Vrf: \

[chars]\ Tbl: \[chars]\ Safi: \[chars]\

An unexpected error occured when trying

to add a path to the next-hop database.

[chars], table [hex], client [chars] [chars]

([dec])

An unexpected error occured when trying

to clear redist information for a client.

Client [chars] [chars] warning [[chars]]

An unexpected but non-fatal error occurred

when a client performed an input/output
operation. See error message for more
information.

[chars], [chars] [chars] id [hex], [chars]

An unexpected RSI error occured during a

table creation/deletion/modification
operation.

[chars], table [hex] [chars]

Some type of table related error occurred.

An unexpected fatal error during a RIB

Thread pool [chars] unexpected fatal error thread pool operation. See error message
[[chars]]
for more details.

Failed to set [chars] event boolean to

[chars]: [chars]
[chars]: [chars]

Unexpected error during event boolean set.

This may result in unreleased memory
resources in RIB server.
A generic RIB error is seen.

Failed to transition from active to standby - Fatal error handling node state transition to
[chars]
active.

Node role state regressed from active state

Node state changed from active to standby to standby state. This is not currently
- don't know what to do
supported by RIB.
Received improper prefix, mask length
[chars]/[dec] from client: \[chars]\ proto: \
[chars]%s\ for Vrf: \[chars]\ Tbl Id: [hex]

A client sent a batch to RIB containing an

invalid op code.

Interface database: failed to [chars] the

entry for [chars] with table id [unsigned
int]

The rib unexpectedly failed to update the

interface -> IP address database.

Received invalid batch operation from

client: [unsigned int]

A client sent a batch to RIB containing an

invalid op code.

BCDL client [chars] ([dec]) registering with

parent [chars] ([dec]) which also has a
parent
Invalid BCDL registration detected.

A client attempted to access invalid table:

[hex]

A client attempted to access a RIB table

that does not exist.

Protocol [chars] [chars]([dec]) trying to

modify the local-label for Table [hex], prefix
[chars]/[dec], protocol [dec] has already
Route already has a local-label from
added label [dec]
another protocol.
RIB ltrace init failed. Error initialising
[[chars]] trace buffer. Process terminated :
[chars]
The ltrace buffer could not be initialised

Failed to send reply to client - [chars]

Unexpected error sending reply to a RIB

client.

Main thread initialization failed [[chars]:

[chars]]. Process terminated

An error occurred during main thread

initialization, causing the process to
terminate. Check the details of the error
message for more information.

Management thread initialization failed

[[chars]:[chars]]. Process terminated

An error occurred during management

thread initialization, causing the process to
terminate. Check the details of the error
message for more information.

Failed to unregister next-hops for client

[chars] - [chars]

Unexpected error unregistering client nexthops. This may lead to a slow memory
leak.

Failed to insert client [chars]/[chars] for

nexthop [chars]/[dec]

An unexpected error occured when trying

to clear redist information for a client.

Could not add nexthop to nh db, error

[chars]

An unexpected error occured when trying

to clear redist information for a client.

Cannot insert nh_entry into the heap,

[chars]

An unexpected error occured when trying

to clear redist information for a client.

Failed to allocate resources required for

NSF [chars]

Unexpected resource error during NSF

initialization. This may result in NSF
failures.

The route prefix table has become full-The route prefix table ([hex]), VRF: [chars], either because the table reached the
is full with limit of [unsigned int] prefixes
configured maximum fill level, or a
exceeded.
maximum of 2,000,000 prefixes are stored.

Couldn't allocate a purge timer. Old routes

Not enough memory to allocate purge
for this protocol may not automatically get
timer for Protocol [chars] (Instance [chars]) purge from the FIB table.
RIB failed function qsm_add_service to add RIB failed to advertise it local channel
local service: [chars]
during failed over.

Failed to notify RUMP of new protocol:

[chars]

Failed to notify RUMP about a newly

registered protocol. See error message for
more details. The result is that routes from
the new protocol will not be redistributed
into the multicast table.

Process is shutting down: [chars]

Failed to get timestamp from kernel

The RIB process has performed a graceful

shutdown and will be restarted.
A call to clock_gettime failed.

Client \[chars]\ updated the RIB without

signaling update completion for Vrf: \
[chars]\ Tbl: \[chars]\ Safi: \[chars]\

A client updated the RIB without signaling

update completion. This will have delayed
the convergence of the routing table, and
hence the purging of any stale routes from
the forwarding table.

RIB received an unexpected error([dec])

from sysdb

RIB recevied an unexpected error number

from sysdb API.

Client \[chars]\adding opaque data of type A client adding an opaque data type for
[hex] for which it has not register to RIB
which it did register to RIB.

The previously full route prefix table

([hex]), VRF: [chars] is no longer full and
can accept more routes.

The route prefix table is no longer

considered full. This warning is generated
after a full route prefix table frees off some
route prefixes.

This warning indicates the number of

prefixes in the specified prefix table
reached the configured fill threshold. This is
an informational message that may be
used to alert changing trends in the
number of active prefixes. This threshold is
set using the 'maximum prefix
{max_prefixes}
The fill level for the route prefix table
{low_threshold_percentage}' command.
([hex]), VRF: [chars], reached the low
This command can be set per virtual router
warning fill level of [unsigned int] prefixes. (vrf) or for the main routing table.

The maximum recursion depth has

changed. In order for the new value to take
effect, the process has to be restarted. This
Maximum recursion depth changed. Please warning is generated to remind the the
restart process to take effect.
customer to restart the RIB processes.

Client [chars] on [chars] - File select input

ignored

Internal notification error.

Failed to retrieve node state from sysmgr:

[chars]

Sysmgr returned a failover from a node

state query.

Bad memory state received from

wdsysmon ([dec])

A memory state transition notification was

received from wdsysmon with an invalid
state.

[chars], [chars]/[dec] in table [hex]

A route has extended communities

attached to it unexpectedly.

This notification indicates that there is

Nexthops in Vrf: [chars] Tbl: [chars] ([hex]) atleast one nexthop in this RIB table that is
Safi: [chars] are getting damped
getting damped.

Rib locking context[[dec]] [chars],

operation: [chars], thread id: [dec]

Display a single entry of locking context

information. The cause of this informational
message should be evident from the
context in the log.

[chars] in function [chars]

Display the operation being performed on

lock, and the function the operation is
taking place in. This will only be displayed
in verbose locking debugging.

Recursion loop looking up prefix [chars] in

Vrf: \[chars]\ Tbl: \[chars]\ Safi: \[chars]\
[chars]

Recursive route lookup for resolving the

prefix has exceeded the maximum
recursion depth allowed(possibly because
of a routing loop).

RIB is closing sysdb EDM connection, fd:

[dec]

This notification indicates that RIB

component is closing the connection with
sysdb. Ignore the log if RIB or sysdb is
restarting.

Failed to build [chars]: [chars] ([chars])

Internal error in the routing policy library.

There was an internal error in the routing

Failed to build ORA[chars]: [chars] ([chars]) policy library.

Could not apply policy operation [chars] to

attribute [chars] because [chars]
Internal error in the routing policy library.

Could not allocate memory for [chars]:

instance \[chars]\

There is not enough memory available to

RIP process.

Failure in RIP authentication module in

context \[chars]\: instance [chars]:
error=[chars]

Internal error encountered in RIP

authentication module.

Error during configuration in context \

[chars]\: error=[chars]

Internal error encountered in RIP

configuration functions.

Error in clear server in context \[chars]\:

error=[chars]

Internal error encountered in RIP clear

server.

Event handling error in context \[chars]\:

type [dec]: error=[chars]

Internal error encountered in RIP event

handling mechanisms.

Error in interface module in context \

[chars]\: instance \[chars]\: error=[chars]

Internal error encountered in RIP interface

module.

Initialization error in context \[chars]\:

instance \[chars]\: error=[chars]

There was an error during initialization of

one of RIP's components.

ITAL error in context \[chars]\: VRF [chars]:

Interface [chars]: IPAddress [chars]:
Internal error encountered in RIP ITAL
error=[chars]
module.

Error in handling out-of-memory condition

in context \[chars]\: state=[chars]:
error=[chars]

An internal error encountered in RIP's OOM

module. This may affect RIP's behavior only
under low memory conditions; otherwise
RIP will operate normally.

Authentication failure for RIP [chars] packet

in context \[chars]\: instance [chars]:
Authentication failure during RIP
error=[chars]
send/receive packets.

Packet receive error in context \[chars]\:

instance \[chars]\: error=[chars]

Error encountered during RIP packet

receive operation.

Policy error in context \[chars]\: name

[chars]: error=[chars]

Internal error with route policies used by

RIP.

RDB error in context \[chars]\: VRF [chars]: Error encountered in RIP's routing
TableID [unsigned int]: error=[chars]
database.

Redistribution error in context \[chars]\:

protocol [chars]: instance \[chars]\:
error=[chars]

Internal error encountered during

redistribution of other protocols into RIP.

RIB error in context \[chars]\: VRF [chars]:

IPAddress/PrefixLen [chars]/[unsigned int]: Error encountered by RIP during interaction
error=[chars]
with RIB.

Error [chars] locking [chars] in context \

[chars]\: error=[chars]

Internal error during locking of a RIP

resource.

Error unlocking [chars] in context \[chars]\: Internal error during unlocking of a RIP
error=[chars]
resource.

Route operation error in context \[chars]\:

VRF [chars]: IPAddress/PrefixLen [chars]/
[unsigned int]: error=[chars]

Internal error encountered in RIP's topology

module.

RIP out-of-memory event \[chars]\:

new/current state=[chars]: old
state=[chars]

This is an event associated with out-ofmemory conditions on the router. If the

new state is MINOR, no new VRF contexts
or interfaces will be activated. If the new
state is SEVERE, some VRF contexts and
interfaces may be forcible deactivated in
order to free up memory. If the new state is
CRITICAL, the RIP process will be shutdown.
If the new state is NORMAL, RIP will behave
normally. If a VRF context or interface is
forcibly deactivated, it will not be activated
again when memory state returns to
NORMAL unless the user explicitly clears
the out-of-memory condition in the VRF
context or the interface using the 'clear rip'
command.

The rpl multi-version coordinator was

unable to obtain the event handler. This
handle is required for all base level
communitions with the rest of the system,
Unable to create communication channel : so the coordinator was shutdown so
[chars]
sysmanger could attempt to restart.

Error seen in primary wait loop: [chars]

The rpl multi-version coordinator saw an

error in the primary event loop. The
coordinator may still be functioning and
route policy may not be operational until
this is resolved.

Sysmgr rejected process available

notification : [chars]

The system manager did not accept the

proccess available that the rpl multiversion coordinator tried to post. The
coordinator will exit so the system
manager can restart it. Route policy may
not be operational until this is resolved.

Sysmgr rejected process ready

notification : [chars]

The system manager did not accept the

proccess ready that the rpl multi-version
coordinator tried to post. The coordinator
will exit so the system manager can restart
it. Route policy may not be operational
until this is resolved.

The rpl multi-version coordinator was

unable to create the group services group
that is required to coordinate with other
route policy entities. The coordinator will
Creation of '[chars]' services group failed
exit to allow the system manager to restart
because [chars] will retry to create service it. Route policy may not be operational
group
until this is resolved.

Unable to publish own communication

channel to other system entities: [chars]

The rpl multi-version coordinator was

unable to publish its channel in the global
space. The coordinator will exit so the
system manager can restart it. Route policy
may not be operational until this is
resolved.

Unable to register for software change

notification with install manager because
[chars]

The attempt to register with the install

manager for change of software notification
failed. The process will restart in an
attempt to clear the problem. Route policy
may not be operational until this is
resolved.

Unknown message type: [dec]. Message

ignored.

The rpl multi-version coordinator received a

message with a type it did not recognize.
The message was ignored.

The call to install_default_action failed

because [chars]

During the processing of a software change

notice, the command to take the default
restart action failed. The routine will now
fall back on a straight exit.

The query to install_check_dll_changes

failed because [chars]

During the processing of a software change

notice, the command to check the list of
open dlls vs changed dlls failed. The
routine will now attempt to fall back on
default disposition.

The query for docked dlls failed because

[chars]

During the processing of a software change

notice, the command to get a list of dlls
that this process had open failed. The
routine will now attempt to fall back on
default disposition.

Unable to setup remote dll manager:

[chars]

The attempt to setup the rpl remote dll

coordinator failed. This will prevent the rpl
coordinator from running and may prevent
route policy from executing.

Dll '[chars]' find failed ([chars]). No

response sent

When the rpl multi-version coordinator

tried to locate the dll, an error was
encountered. Because of this, no response
will be returned.

Group message from outside route access

component ([dec] vs [dec]). ignored.

The rpl multi-version coordinator received a

group services message from a component
other than itself. The message was ignored
and thus the operations of the coordinator
are unaffected. However, this can be a sign
that something else is going wrong in the
system.

A 'who has this' message longer ([dec])

than required [dec] octets. Ignored.

A 'who has this' dll message was longer

than its content implied. This indicates
either a corruptions of the message itself
or a failure of the client to build the
message correctly.

A 'who has this' message shorter ([dec])

than required [dec] octets. Ignored.

A 'who has this' dll message was shorted

than its content implied. This indicates
either a corruptions of the message itself
or a failure of the client to build the
message correctly.

The call to indicate install ready failed

because [chars]

The attempt to notify install manager of

install complete failed. If this is the initial
startup, there should be no side affects. If
this is the result of a software
upgrade/downgrade, it is likely the process
will be restarted by sysmgr after a timeout
period.

The rpl multi-version coorindator was

unable to respond to a 'who has this'
request and was forced to ignore the
message. This will likely cause a timeout
on the client side. If this was the only node
with the version of the dll being requested
active on it, the client will be unable to
access this version. If other nodes have it,
rpl multi-version Coordinator could not get the multi-version dll operation will
memory to respond to 'who has this'
continue. The status of this node remains
request.
in uncertain in any case.

During the processing of a software change

notice, the command to get reboot
information for this notice failed. The
install_will_this_node_reboot failed because routine will now attempt to fall back on
[chars]
default disposition.

Unable to setup debug handlers: [chars]

The rpl multi-version coordinator was

unable to setup the debug handlers. This
will not affect its operational, but will
prevent debug commands for the
coordinator from functioning.

The rpl multi-version coordinator received a

message response instead of a request.
Response to message [chars] received, but This has been ignored and it is likely no
coordinator only supports requests
other problems will result from this.
The given message string should have
arrived with a null terminator in it. The
library has repaired this, but it should not
The message string '[chars]' was missing it have occured in the first place. No
null terminator from [chars]:[chars]
operational impact should be visible.
[chars] [dec]

A failure at an attempt to allocate memory

was detected.

[chars] [dec]

Allocation of memory failed.

RSVP checkpoint translation received a

The RSVP checkpoint table translation
translation request with insufficient space library was invoked with insufficient space
to store the transformed checkpoint record to store the transformed checkpoint record.

The RSVP checkpoint table translation

RSVP checkpoint translation received an
library was invoked with an invalid
invalid translation direction: [unsigned int] translation direction.

RSVP checkpoint translation received a

translation request for an unsupported
type: [unsigned int]

The RSVP checkpoint table translation

library was invoked with an unsupported
translation type.

Notification queue for client '[chars]' is

overflowing

This message indicates that notification

queue for the specified client has
overflowed, and probably indicates RSVP is
handling the number of messages beyond
its capacity.

Failed to get a new LSP resource

Resources to setup new LSP's are

exhausted.

RSVP event tracing subsytem initialization RSVP could not initialize the event tracing
failed
module

RSVP path create latency has risen above

threshold and will drop path create
packets.

The RSVP process has received more path

create messages than the system can
handle in a short period of time. Path
create messages will be dropped until the
system can catch up.

Process is shutting down ([chars]): [chars]

RSVP process has encountered a problem

which means it is no longer able to
continue and is shutting down. The
message includes a brief description of the
problem. The message also describes
whether or not RSVP process has been
automatically restarted.

Incoming [chars] from [chars] to [chars]

discarded - bad digest using key chain
'[chars]' key [unsigned long long int],
[chars]

The router received an RSVP message with

a bad integrity digest. RSVP discarded the
message because the digest verification
failed. The 'key-strings' used may not be
configured the same on both
sender/receiver.

The router received an RSVP message with

an authentication sequence number that
has already been seen. RSVP discarded the
Incoming [chars] from [chars] to [chars]
message because an untrusted source may
discarded - authentication seq #[unsigned be (unsuccessfully) attempting an RSVP
long long int] is a duplicate, [chars]
message replay attack.

The router received an RSVP message with

a bad integrity digest. RSVP discarded the
Incoming [chars] from [chars] to [chars]
message because the digest verification
discarded - key [unsigned long long int] is failed. The received key ID specified is not
not eligble using key chain '[chars]', [chars] currently active/configured.

The router received an RSVP message with

a bad authentication sequence number. It
Incoming [chars] from [chars] to [chars]
may be possible in some cases that bursts
discarded - authentication seq #[unsigned of RSVP messages become re-ordered
long long int] is outside authentication
between RSVP neighbors. It may also be
window ([unsigned long long int]), [chars] possible that an attack was attempted.

Incoming [chars] from [chars] to [chars]

discarded - sender is using [chars] as the
digest for key chain '[chars]' key [unsigned
long long int], [chars]

The router received an RSVP message with

an authentication digest type that does not
match the type configured on the router.
RSVP discarded the message because the
digest cannot be verified.

Outgoing [chars] from [chars] to [chars]

discarded - no active keys from keysource \[chars]\ -- [chars], [chars]

The router is unable to authenticate

outgoing RSVP messages due to a lack of
availaible keys.

RSVP path create latency has dropped

below threshold and will no longer drop
packets

The average time taken for path creates to

be processed by the system was above a
defined threshold, but a path out message
has come in below the threshold signifying
that the problem has passed.

The RSVP Graceful Restart Hello session

with a neighbor has gone down. This may
be due to either a problem in the
communication link with the neighbor or
Graceful restart hello session to [chars] has the neighbor's RSVP control plane may be
changed to the down state
restarting.
A graceful restart hello session to [chars]
has been established

A new hello session with a neighbour has

been established

No memory for [chars]

The requested operation could not be

accomplished because of a low memory
condition.

Initialization failed for [chars] ([chars])

An error occurred during initialization.

SysDB Error: [chars] ([chars])

An error occurred when accessing the

system database.

Internal error: [chars], [chars]

An internal software error occurred.

RIB failure for [chars] ([chars])

RIB initialization failed.

Restarting because [chars] restarted

RUMP is restarting because the

corresponding RIB proc restarted.

Bag related error: [chars] : [chars]

This error can occur only when the SAP had

a problem in registering for SAP bags for
multicast from SysDB.

Event connection manager error:[chars] [chars]

This indicates that the SAP listener packet

handling process failed to open connection
to Connection Manager.

A call to event_manager_create() failed

A problem occurred while calling the

event_manager_create() API. or a
connection to the event_manager failed
during the initialization of the SAP listener.

[chars] : [chars]

This message is displayed when the

system manager process is not ready or
when an error occured while attaching the
managed timer.

Socket Error : [chars] - [chars]

A socket operation failed while adding into

the group membership or dropping the
group membership.

Sysdb registration error: [chars]

This message can occur when the SAP has

trouble registering as a notifier with SysDB.
This can be registration or verification.

ctrace server initialization failed.

During system initialization trace server

failed to initialize.

inet_ntop error first time itself

A call to inet_ntop failed on first attempt.

Failed to initialize module [chars].

CM failed to initialize specified module

when system is starting.

Serial number is missing.

Connection to PM failed.

Mandatory information serial number is

missing.
CM failed to connect to PM module.

Failed to allocate memory using [chars]

inside function: [chars] having size: [dec]

System failed to allocate specified memory

using specified allocator function. The most
likely cause is a low memory condition.

OIR card [chars] having serial number:

[chars].

CM got notification that a card has been

inserted or removed.

Got process update: [chars].

CM got notification from process manager

about process/system health.

Bad service info from DS

Bad service information received from DS.

Failed to add SDR [chars] to the card

[chars].

Failed to add specified SDR to the given

card.

Failed to create and initialize memory for

chunk: [chars] having size: [dec]

System failed to create and initialize

memory chunk. The most likely cause is a
low memory condition.

Publish with interface address failed.

Could not publish the rack lead information

using interface address.

Failed to start [chars] thread.

CM failed to start the specified thread.

Failed to create thread [chars].

CM failed to allocate resource for the

specified thread.

Lead type: [chars] System: [chars].

CM has got notification about the lead

selection as specified.

[chars]::[chars]

An internal software error occurred in the

library used for messaging between
components. The message is generated
from the context of the process sending or
receiving a message at the time the error
occurred, but is internal to the library.

[chars] : [chars]

An error occured with the line control

library

Server initialization failure: [chars]

The ucp lctrl server could not be initialized.

At least one IPCC is now available for

neighbor [chars]

An IPCC has come back up or newly

configured for a neighbor.

[chars]

An internal system error occurred.

[chars] LMP Router ID changed (from:

[chars], to: [chars])

All existing optical tunnels will go down and

will be re-established using the new router
ID value.

[chars] LMP application does NOT have a

router ID to use

All existing optical tunnels will NOT come

up until an application LMP router ID value
is specified using CLI.

All existing MPLS TE optical tunnels will

MPLS TE LMP application does NOT have a NOT come up until a Global or MPLS TE
router ID to use
router ID value is specified using CLI.
All IPCCs are down or removed for neighbor All IPCCs are down or removed for a
[chars]
neighbor.

OUNI application does NOT have a router

ID to use

All existing OUNI connection will NOT come

up until a Global or OUNI router ID value
will be specified using CLI.

OUNI support, including this command, will GMPLS OUNI/NNI support, including this
be removed in release 4.3.0
command, will be removed in release 4.3.0.
O-UNI Connection Destroyed on [chars]

A connection was destroyed.

O-UNI Connection Established on [chars]

A connection was established.

[chars]

An internal system error occured.

vkg_cpp_mcast_gtrie: IP multicast gtrie

failure ,[chars]

Error while initializing Gtrie. Initialization

failed and aborted

vkg_cpp_mcast_gtrie: IP multicast gtrie leaf

lookup failure ,[chars]
Error in platform Gtrie Lib

vkg_cpp_mcast_gtrie: IP multicast gtrie

warning ,[chars]

Error while initializing Gtrie. Initialization

will continue

Process initialization failed: ([chars])

MRIB (multicast routing information base)

failed to initialize. MRIB is the central
routing information base for multicast
components. It provides coordination
among all multicast routing components
and forwarding. The effect is that multicast
forwarding will not function. %s - indicates
the reason for the failure.

Couldn't init sysdb due to internal error,

[chars] : [chars]

The VIKING-MCAST library encountered

internal error during SysDB init setup. The
init setup will be retried for finite number of
retries.

Couldn't register bags : [chars]

The VIKING-MCAST library encountered

internal error during SysDB/EDM init setup.
The init setup will be retried for finite
number of retries.

Couldn't register edm : [chars]

The VIKING-MCAST library encountered

internal error during SysDB/EDM init setup.
The init setup will be retried for finite
number of retries.

Generic failure : [chars] failed : [chars]

VIKING-MCAST library encountered error

during setup. The init setup will be retried
for finite number of retries.

Error: '[chars]'. [chars]

Error encountered while running AAA Base

Warning: '[chars]'. [chars]

An internal software error has occurred

Debug: '[chars]'

Informational log only

[chars]: [chars]

Error message from AAA task debug

module

Error encountered in dllmain for [chars]:

[chars]

Error message from debug module

AAA task debug flag [dec] does not exist

An internal software error occurred.

[chars]: [chars]

Internal debugging message.

[chars]: [chars]

Encountered an error in debug module.

[chars]: [chars]

Error encountered in debug module.

[chars]: DES initialization failed

An internal software error occurred.

[chars]: [chars]

Error encountered while initializing AAA

client library DLL.

Error encountered while initializing DLL for Error message from DLL initialization
[chars]: [chars]
module

[chars]

None at this time

Not enough memory available while [chars] Failed to allocate necessary memory.

The AAA debug flag [dec] does not exist

The debug flag specified is not supported.

Not enough memory available while [chars] Failed to allocate memory.

sysdb_bind returned error :[chars] in

function :[chars]

Error while trying to bind to sysdb.

WARNING: The server key contained

trailing whitespace and was truncated

Whitespace is not allowed at the end of a

server key.

Failed to open event connection for a

[chars]: [chars]

The initial connection failed, but a retry has

been successfully rescheduled.

[chars] path [chars]: [chars]

'Failed to execute a SysDB operation'

Password which is a single digit is not

permitted

Single digit passwords are not allowed.

Failed to encode [chars] bag: [chars]

Failed to encode a bag.

Failed to unregister [chars] bag: [chars]

Failed to unregister a bag.

Clearing the [chars] DB failed. DB state is

unknown

Error encountered when attempting to

clear the DB. DB might be in any state now
& so usage of hat DB might fail with
unexpected results.

[chars]: [chars]

Error encountered in debug module.

Failed to register EDM - [chars]

Failed to initialize EDM.

[chars]: [chars]

AAA failed to recognize the specified server

group name. It may be undefined.

[chars]: pthread [chars] failed: [chars]

The call to pthread functions, such as

pthread_create, lock/unlock a mutex or
wait on a condition, failed. The error is
displayed in the message.

Group [chars] is not valid for [chars]

RADIUS does not support command

authorization and command accounting.

Buffer size is insufficient to hold the

required data: [chars]

A buffer is required in order to fill a certain

data but the buffer size was too small.

Method list [chars] is not defined

Trying to configure a method list in the line

configuration that is not defined in AAA

Failed to add the username [chars] to

lightweight authentication password
database - [chars]. (Please remove/rename
the file '/disk0:/AAA', which is in conflict
A file with the same name as aaa directory
with the directory '/disk0:/aaa/'.)
detected.

Failed to add the username [chars] to

lightweight authentication password
database: [chars]

Failed to enable this user to log into ksh.

Failed to remove the username [chars]

from lightweight authentication password
database - [chars]

Failed to remove a username from the LWA

DB.

Failed to malloc [unsigned int] bytes

acctd failed to allocate the required

amount of memory.

[chars]: [chars]

Error encountered while handling

messages received by acctd.

[chars]: Size ([dec]) - [chars]

An internal error occurred.

The username \'[chars]\' is already

configured in the other plane (Admin/LR),
please choose a different one

The username has to be unique across the

Admin and LR plane.

Error on changing redundancy state to

[chars]: [chars]

Error encountered during redundancy state

transistion.

[chars]: path [chars], error: [chars]

Accounting daemon failed to

create/remove the root user database on
the disk0. This will affect authentication to
ksh since it refers to this database.

A lock operation on shared resource, called

by acctd lwDB failed due to the mentioned
Failed lock operation '[chars]'. Error: [chars] error.

Changing priority of acctd failed: [chars]

Changing acctd priority failed.

Failed to initialize shared memory used for

AAA configuration - [chars]
Failed to initialize shared memory window

[chars]: [chars]

acctd process failed to shutdown properly.

Failed to send sigevent to [chars] - [chars]

An internal software error occurred.

[chars]: [chars]

acctd process failed to startup properly.

Failed to initialize standby - [chars]

Failed to initialize acctd on standby node.

Failed to send the accounting record for

request id [dec] - [chars]

Failed to send an accounting record to

RADIUS or TACACS+ server

Failed to handle timeout for sending an

accounting record (request id [dec]) [chars]

Failed to send an accounting record to

RADIUS or TACACS+ server

[chars]: [chars]

acctd failed to register error codes.

Error encountered while registering the

checkpoint table [chars] - [chars]

Encountered a checkpoint register failure

Error encountered while recovering from

checkpoint table [chars] - [chars]

Encountered a checkpoint recovery failure

Error encountered while saving to

checkpoint table [chars] - [chars]

Encountered a checkpoint save failure

Warning: The password is configured too

for user '[chars]'

An internal software error has occurred

Warning: The secret is configured too for

user '[chars]'

An internal software error has occurred

[chars] [chars]: [chars]

Error encountered while using the System

Database.

[chars]: [chars]

Error encountered while using TTY

management library.

[chars]: [chars]
[chars]: [chars]

Generic error message used for internal

debugging.
An error occurred in ace_grp dll

[[dec]]>[chars]

ACE SPA SYSLOG message

[[dec]]>[chars]

ACE SPA SYSLOG message

[[dec]]>[chars]

ACE SPA SYSLOG message

[[dec]]>[chars]

ACE SPA SYSLOG message

[chars]: [chars]

ACE Driver Fatal Error.

[[dec]]>[chars]

ACE SPA SYSLOG message

[chars]: [chars]
[[dec]]>[chars]
[[dec]]>[chars]
[chars]: [chars]

ACE
ACE
ACE
ACE

[chars] [dec] [chars]

ACE QAD Erros

[chars]

ACE TSB Fatal Error.

[chars]: [chars]

ACE TSB Informational message

[chars]: [chars]
[chars]: [chars]

ACE TSB warning message.

ACE TSB Debug Information

driver warning message.

SPA SYSLOG message
SPA SYSLOG message
driver Informational message

[chars]

CEPKI general error message with one

prameter.

[chars] [chars]

CEPKI general error message with two

prameters.

[chars]

CEPKI general info message with one

prameter.

[chars]

CEPKI general warning message.

Failed to allocate memory

The requested operation could not be

accomplished because of a low memory
condition.

Crypto conditional debug does not work.

The request to use condition for a crypto

debug message could not be accomplish.

Crypto conditional debug using IP address

does not work.

The request to use using IP address as

condition for a crypto debug message
could not be accomplish.

Illegal IP-address/IP-mask was configured.

Illegal IP-address and/or IP-mask were

configuring as condition to crypto debug
message.

[chars]:Failed to send IPC using mq_send.

reason: [chars]

Failed to send IPC message to IKE process.

Most likely casue the process is too busy

[chars]

Internal Warning.

Failed to allocate memory.

A memory allocation failure has occurred

from which the process cannot
automatically recover.

Failed to send an Accounting record of

type: [chars], error: [chars]

An error occurred while attempting to send

an accounting record to the external AAA
server

IKE detects failure adding key, name

[chars], ip address [unsigned int]

IKE found failure when adding key

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: Authentication
method [dec] failed with peer.

The IKE process was unable to authenticate

its security association with its remote
peer.

IKE detects bad certificate was used,

[chars], [chars]

IKE found bad certificate was used

IKE detects bad DOI notify, DOI is [dec],

address is [unsigned int]

IKE found bad DOI notify

Bad [chars] magic number ([hex]).

'An internal software error.'

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: EN/DE-crypto services IKE found failure returned from
failure, [chars] during [chars].
encryption/decryption service.

[chars], [chars]

IKE general error message with two

prameters.

Session node empty (no ipsec/ike SAs) DB

maybe inconsisten. Peer [chars]/[dec] vrf
[chars]

Internal error, Session node does not

include any ipsec and ike SAs, This
indicates an internal data structure
inconsistency.

[chars]

Internal error.

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: Failed to compute
SKEYSEED.

Failed to generate SKEYID.

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: [chars].
grpname=[chars].

Group authorization failed.

Failed to upload the IKE groups from the

running config to the local AAA server.
rc=[dec], errpr=[chars]

An error occured while the IKE process was

uploading its localy configured groups to
the localy running AAA server. This means
that the system is in inconsistent state. the
IKE groups that are seen in the running
config are not configured in the local AAA
DB that can be seen using 'show aaa
ikegroups'.

[chars]

An IKE initialization error

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: [chars] Interface:
[chars].

[1] When an interface is configured with a

VRF that is not configured globally, it is
treated as invalid VRF. SAs should not be
created on this interface. [2] When an
interface state is not UP SAs should not be
created on this interface.

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: IKE detects invalid
certificate - [chars].

The certificate given by remote peer has

either been revoked or expired (certificate
invalid) or the signature check on the
certificate failed (bad signature).

Failed to notify about a used IP address to An error occurred while attempting to

the Address Pool component. pool=[chars], notify IP local Address Pool about used
vrf=[chars], IP=[chars], err=[chars]
addresses
Failed to free a local pool IP address :
poolname=[chars], ip=[chars]

An error occurred while attempting to free

an IP address back to the local pool

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: Key not found in
ISAKMP profile '[chars]'.

In Main Mode, The ID payloads are

exchanged only in MM5 and MM6. Since
keyring material is needed in earlier stages
of the negotiation, it is looked up based on
peer address. This error is seen when the
selected keyring appears to not match the
keyring configured under the ISAKMP
profile for that peer.'

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: [chars].
grpname=[chars], username=[chars],
pool=[chars].

Failed to allocate IP address for client.

A quick sanity check is done on all received

ISAKMP messages to verify that all
component payload types are valid, and
that the sum of their individual lengths
equals the total length of the received
[[chars] ([char]) failed with peer:[chars]
message. This message failed the sanity
fvrf:[chars]] Reason: IKE message failed its check. This continous bad messages could
sanity check or is malformed.
imply denial of service attack

[chars]:Failed on [chars]:[chars]

An internal software error occurred.

[chars]:Failed to send IPC using mq_send.

reason: [chars]

Failed to send IPC message to IKE process.

Most likely casue the process is too busy

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: No cert, encryption
key or pre-shared address key with peer.

Failed to derive peer key through either of

the following ways: pre-shared keys, RSA
keys, or certiifcates. Applies only to
initiator mode.

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: Failed to process the This error message implies a severe error
packet, probably results from internal error. condition, likely as result of internal error.
[[chars] ([char]) failed with peer:[chars]
fvrf:[chars]] Reason: Phase-II: peer proposal Phase-II parameters negotiation failed with
rejected.
peer.
[[chars] ([char]) failed with peer:[chars]
fvrf:[chars]] Reason: No offers accepted.

Phase I policy parameters negotiation

failed with peer.

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: Failed to find preshared key. grpname=[chars],
username=[chars].

Failed to find pre-shared key.

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: [chars] [chars].

[1] No ISAKMP profile found matching peer

identity. applicable to RESPONDER mode
only. [2] No ISAKMP profile found matching
interface name. applicable only to
INITIATOR mode. [3] Peer identity doesn't
match the ISAKMP profile associated with
the interface. applicable only to INITIATOR
mode.

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: Timer to complete
phase-I has expired.

We can't wait forever before we start quickmode and initiate phase II.

[[chars] ([char]) with peer:[chars] fvrf:

[chars]] AAA user '[chars]' authentication
failed

AAA user authentication faild.

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: Retransmission limit
exceeded.

Retransmission limit exceeded.

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: [chars].

Failed to query RSA key.

The IKE security association with the

remote peer was not authenticated; yet the
peer attempted to begin a Quick Mode
[[chars] ([char]) failed with peer:[chars]
exchange. This exchange must only be
fvrf:[chars]] Reason: Cannot accept Quick done with an authenticated security
Mode exchange if SA is not authenticated. association.

IKE detects SA not being offered [unsigned

int], [chars]
IKE found SA not offered

[[chars] ([char]) failed with peer:[chars]

fvrf:[chars]] Reason: [chars].
grpname=[chars], username=[chars].

Processing of phase 1.5 (xauth) with peer

failed.

[[chars] ([char]) with peer:[chars] fvrf:

[chars]] Invalid DOI value: [dec] in a SA
offer.

The DOI field in a SA offer is needed for

message parsing. SA offer with unknown
DOI can't be parsed.

[[chars] ([char]) with peer:[chars] fvrf:

[chars]] Certificate doesn't match [chars]
ID:[chars], id_type:[dec] ,cert:[chars].

Peers claimed identity doesn't match what

we can glean from the certificate.

[[chars] ([char]) with peer:[chars] fvrf:

[chars]] Certificate issuer name:[chars] is
not a trusted root.

During IKE phase-I signature verification,

the initiator will send a list of its CA
certificates. This warning will be printed by
the responder if none of the CAs in the list
is a trusted root. Note this is not
necessarily an error, as there may be
multiple cert-req payloads

The packet size is limited to 32K, in case

ISAKMP packet from [chars] is larger ([dec]) that peer sends out long length info forcing
than the maximum size permitted.
large buffer allocation (DOS).
[[chars] ([char]) with peer:[chars] fvrf:
[chars]] Too many IPV4 routes from spoke,
got [dec], max routes supported [dec]

Spoke sent too many IPV4 routes during

negotiation.

Message is not processed, ike is disabled.

Trying to initiate a tunnel while ike is

disabled. The request message for
establishing the tunnel is not processed
and dropped.

No SA found for peer (src:[chars] fvrf:

[chars]) and it is not an initial offer.

No security association exists for this

packet and it is not an initial offer from the
peer to establish one. These errors could
imply denial of service attack.

Trying to send an ISAKMP packet that is

above the maximum UDP packet size
allowed. That can happen if an inordinately
ISAKMP packet is too long. Size:[dec] bytes, large number of IKE policies were being
max allowed:[dec] bytes.
proposed by the initiator.
[[chars] ([char]) with peer:[chars] fvrf:
[chars]] IKE Packet wasn't encrypted and it Received packet should have been
should have been.
encrypted by peer but wasn't.

ISAKMP data is a payload of UDP packet, as

such its length should be less than the UDP
length. Each ISAKMP message has its own
ISAKMP message from [chars] (fvrf [chars]) message length field. The message length
larger ([dec]) than the UDP packet length field of this message was greater than the
([dec])
length of the UDP packet.
[[chars] ([char]) with peer:[chars] fvrf:
[chars]] Received message with unknown
exchange [dec].

IKE performs actions on messages based

on defined exchanges. A message received
with an unknown exchange.

[[chars] ([char]) with peer:[chars] fvrf:

[chars]] Received INFO message before
peer has been authenticated.

Received INFO message before peer has

been authenticated that is why it is called
unreliable.

[chars]

Internal Warning.

[chars], [chars]

Internal Warning.

[chars]

Call admission control policy is configured

on the device. Consequently an IKE SA
request was denied due to the reason
described in the error message.

Crypto tunnel is [chars]. Peer [chars]:[dec]

[chars] [chars] [chars] [chars] [chars]
[chars] [chars] [chars]
Report tunnel status.

[[chars] ([char]) with peer:[chars] fvrf:

[chars]] IKE default policy was matched
and is being used.

The default policy is being used because

the local configured policies did not match
with the peer's policies.

[[chars] ([char]) with peer:[chars] fvrf:

[chars]] ISAKMP SA is to be deleted, reject
phase-2 request on top of it.

Due to major configuration change or

manual delete, this session is to be
deleted. No new IPSec SAs can be
established now on the session.

Processing of [chars] mode failed with peer

at [chars]
Negotiation with the remote peer failed.

[chars] [chars]

Internal error.

[chars]

Internal Warning.

[chars], [chars]

Internal Warning.

[chars]

Crypto Configuration (SAs/ACLs) failed

[chars]

An internal software fatal error occurred.

[chars]:Failed on [chars]:[chars]

An internal software error occurred.

[chars]

SVI has already tunnel with type different

from the one that is trying to be
established. Single sa tunnel can't be on
the same svi as regular tunnel. first tunnel
type determines the SVI type

[chars]

An internal software error occurred.

Process [chars] is ready

Notification that the process is done its

initialization phase and ready to process
events.

[chars] [chars]

Error description, error.

Cannot allocate memory in function [chars] Internal error. System is out of memory ()
malloc failed.

[chars]

The IPSec IPP encountered some problem

in genric nature or plain information.

[chars]

IPSec Base component Fatal Error.

[chars]

IPSec Base component warning message.

[chars]

IPSec Base component Informational

message

[chars]

An internal software fatal error occurred.

Receive invalid message type [dec]

An internal software error occurred.

Password which is a single digit is not

permitted

Single digit passwords are not allowed.

Failed to encode [chars] bag: [chars]

Failed to encode a bag.

Failed to unregister [chars] bag: [chars]

Failed to unregister a bag.

Clearing the [chars] DB failed. DB state is

unknown

Error encountered when attempting to

clear the DB. DB might be in any state now
& so usage of hat DB might fail with
unexpected results.

[chars]: [chars]

Error encountered in debug module.

Failed to register EDM - [chars]

Failed to initialize EDM.

Opening the File [chars] failed

Error encountered while opening the file

Writing to the File [chars] failed

Error encountered while writing to the file .

[chars]: [chars]

AAA failed to recognize the specified server

group name. It may be undefined.

[chars]: pthread [chars] failed: [chars]

The call to pthread functions, such as

pthread_create, lock/unlock a mutex or
wait on a condition, failed. The error is
displayed in the message.

Group [chars] is not valid for [chars]

RADIUS does not support command

authorization and command accounting.

[chars]: [chars]

Generic error message used for internal

debugging.

Buffer size is insufficient to hold the

required data: [chars]

A buffer is required in order to fill a certain

data but the buffer size was too small.

Method list [chars] is not defined

Trying to configure a method list in the line

configuration that is not defined in AAA

Failed to add the username [chars] to

lightweight authentication password
database - [chars]. (Please remove/rename
the file '/disk0:/AAA', which is in conflict
A file with the same name as aaa directory
with the directory '/disk0:/aaa/'.)
detected.

Failed to add the username [chars] to

lightweight authentication password
database: [chars]

Failed to enable this user to log into ksh.

Failed to remove the username [chars]

from lightweight authentication password
database - [chars]

Failed to remove a username from the LWA

DB.

Failed to malloc [unsigned int] bytes

locald failed to allocate the required

amount of memory.

[chars]: [chars]

Error encountered while handling

messages received by locald.

[chars]: Size (%zd) - [chars]

An internal error occurred.

The username \'[chars]\' is already

configured in the other plane (Admin/LR),
please choose a different one

The username has to be unique across the

Admin and LR plane.

Error on changing redundancy state to

[chars]: [chars]

Error encountered during redundancy state

transistion.

[chars]: path [chars], error: [chars]

Locald failed to create/remove the root

user database on the disk0. This will affect
authentication to ksh since it refers to this
database.

A lock operation on shared resource, called

by locald lwDB failed due to the mentioned
Failed lock operation '[chars]'. Error: [chars] error.

Changing priority of locald failed: [chars]

Changing locald priority failed.

Failed to initialize shared memory used for

AAA configuration - [chars]
Failed to initialize shared memory window

[chars]: [chars]

locald process failed to shutdown properly.

Failed to send sigevent to [chars] - [chars]

An internal software error occurred.

[chars]: [chars]

locald process failed to startup properly.

Failed to initialize standby - [chars]

Failed to initialize locald on standby node.

Failed to send the accounting record for

request id [dec] - [chars]

Failed to send an accounting record to

RADIUS or TACACS+ server

Failed to handle timeout for sending an

accounting record (request id [dec]) [chars]

Failed to send an accounting record to

RADIUS or TACACS+ server

[chars]: [chars]

locald failed to register error codes.

Error encountered while registering the

checkpoint table [chars] - [chars]

Encountered a checkpoint register failure

Error encountered while recovering from

checkpoint table [chars] - [chars]

Encountered a checkpoint recovery failure

Error encountered while saving to

checkpoint table [chars] - [chars]

Encountered a checkpoint save failure

Warning: The password is configured too

for user '[chars]'

An internal software error has occurred

Warning: The secret is configured too for

user '[chars]'

An internal software error has occurred

[chars] [chars]: [chars]

Error encountered while using the System

Database.

[chars]: [chars]

Error encountered while using TTY

management library.

Failed to [chars] debug module: [chars]

Failed to initialize or shutdown the debug

module.

Error encountered while initializing the DLL, Error message from debug initialization
path [chars]: [chars]
module.

The login debug flag [dec] does not exist

The debug flag specified is not supported.

Not enough memory was available while

[chars]

Failed to allocate necessary memory.

This is an error message from debug

module of aaa component. This might have
been caused by 1. Entering wrong
username/password. 2. The user is not
Failed authentication attempt by
configured on the box and hence can not
user \'[chars]\' from \'[chars]\' on \'[chars]\' login.

Successfully authenticated user \'[chars]\'

from \'[chars]\' on \'[chars]\'

This is an info message from debug module

of aaa component. This indicates that user
has succesfully authenticated.

[chars]

An internal software fatal error occurred.

[chars]: [chars]

An internal software error occurred.

[chars]: [chars]

Updated Management Plane configuration.

[chars]

CEPKI general error message with one

prameter.

[chars] [chars]

CEPKI general error message with two

prameters.

[chars]

CEPKI general error message with one

prameter.

Failed to notify the completion of

accounting to sender - [chars]

An internal software error occurred.

Failed to notify the completion of

accounting to sender - [chars]

An internal software error occurred.

Adding NAS IP address failed, omitted:

[chars]

An internal software error has occurred.

Adding NAS IP address failed, omitted:

[chars]

An internal software error has occurred.

Failed to add VSA av-pair [dec] with [chars]

- [chars]
Failure encountered while adding a VSA.

Failed to add VSA av-pair [dec] with [chars]

- [chars]
Failure encountered while adding a VSA.

Bad AAA avpair [dec] with length [dec]

detected

An internal software error occurred.

Bad AAA avpair [dec] with length [dec]

detected

An internal software error occurred.

Unsupported message type [dec]

encountered while [chars]

Found an unsupported AAA message type

in avlist.

Unsupported message type [dec]

encountered while [chars]

Found an unsupported AAA message type

in avlist.

Format bit is not set for VSA [chars]

Format bit is not set for VSA %s according

to table bitmap.

Format bit is not set for VSA [chars]

Format bit is not set for VSA %s according

to table bitmap.

Inconsistent [chars] VSA length [dec] was

encountered

VSA format error found in radiusd while

translating.

Inconsistent [chars] VSA length [dec] was

encountered

VSA format error found in radiusd while

translating.

Bad [chars] VSA type [dec] with vendor_id VSA format error found in radiusd while
[dec] encountered, possibily out of range
translating.

Bad [chars] VSA type [dec] with vendor_id VSA format error found in radiusd while
[dec] encountered, possibily out of range
translating.

Vendor specified for VSA [chars] is not

recognized

Vendor specified for the VSA is not

recognized according to table bitmap. An
internal software error occurred.

Vendor specified for VSA [chars] is not

recognized

Vendor specified for the VSA is not

recognized according to table bitmap. An
internal software error occurred.

Failed to encode [chars] bag: [chars]

An internal software error occurred.

Failed to encode [chars] bag: [chars]

An internal software error occurred.

Failed to unregister bag [chars]: [chars]

An internal software error occurred.

Failed to unregister bag [chars]: [chars]

An internal software error occurred.

Encountered configuration error while

[chars]

An internal software error occurred.

Encountered configuration error while

[chars]

An internal software error occurred.

[chars]: [chars]

Error encountered in debug module.

[chars]: [chars]

Error encountered in debug module.

Failed to register EDM - [chars]

An internal software error occurred.

Failed to register EDM - [chars]

An internal software error occurred.

Failed to create a server entry: [chars]

A configuration error has occured.

Failed to create a server entry: [chars]

A configuration error has occured.

Unable to apply server group '[chars]'

configuration: [chars]

A configuration error has occured.

Unable to apply server group '[chars]'

configuration: [chars]

A configuration error has occured.

Error while setting or unsetting a

parameter in server entry: [chars]

A configuration error has occured.

Error while setting or unsetting a

parameter in server entry: [chars]

A configuration error has occured.

Failed to bind to SysDB at [chars]: [chars]

An internal software error occurred.

Failed to bind to SysDB at [chars]: [chars]

An internal software error occurred.

Both ttyname ([chars]) and ifh ([hex]) are

present in the message

In the AV pair message recieved from the

radiusd clients should have either ttyname
or interface handle, not both.

Both ttyname ([chars]) and ifh ([hex]) are

present in the message

In the AV pair message recieved from the

radiusd clients should have either ttyname
or interface handle, not both.

Failed to attach handler for async events:

[chars]

An internal software error occurred.

Failed to attach handler for async events:

[chars]

An internal software error occurred.

IP address [chars] is too long ([dec])

An internal software error has occurred.

IP address [chars] is too long ([dec])

An internal software error has occurred.

Failed to obtain or release [chars] lock

(error: [chars])

radiusd has either failed to obtain or

release a lock.

Failed to obtain or release [chars] lock

(error: [chars])

radiusd has either failed to obtain or

release a lock.

Failed to malloc [unsigned int] bytes

radiusd has failed to allocate the required

amount of memory.

Failed to malloc [unsigned int] bytes

radiusd has failed to allocate the required

amount of memory.

[chars]: [chars]

Error encountered while handling

messages received by tacacsd.

[chars]: [chars]

Error encountered while handling

messages received by tacacsd.

[chars]: size [dec] - [chars]

An internal error occurred

[chars]: size %zd - [chars]

An internal error occurred

The specified attribute [dec] is a non-VSA

radius attribute

Encountered a non VSA attribute.

The specified attribute [dec] is a non-VSA

radius attribute

Encountered a non VSA attribute.

[chars]

RADIUS was passed an invalid parameter.

[chars]

RADIUS was passed an invalid parameter.

Binding to RIB failed: [chars]

An internal software error has occurred.

Binding to RIB failed: [chars]

An internal software error has occurred.

NAS IP not found; address omitted: [chars] An internal software error has occurred.

NAS IP not found; address omitted: [chars] An internal software error has occurred.

Failed to initialize mutex in radiusd

An internal software error occurred.

Failed to initialize mutex in radiusd

An internal software error occurred.

Changing priority failed [dec]

Attempt to change priority failed.

Changing priority failed [dec]

Attempt to change priority failed.

[chars]: [chars]

TACACS+ process failed to shutdown

properly.

[chars]: [chars]

TACACS+ process failed to shutdown

properly.

[chars]: [chars]

TACACS+ process failed to startup properly.

[chars]: [chars]

TACACS+ process failed to startup properly.

daemon VSA [dec] does not match type

string in [chars].

VSA format error in daemon user config.

daemon VSA [dec] does not match type

string in [chars].

VSA format error in daemon user config.

Parsing error on daemon VSA '[chars]' (no

protocol or type field)

VSA format error in daemon user

configuration.

Parsing error on daemon VSA '[chars]' (no

protocol or type field)

VSA format error in daemon user

configuration.

Parsing error on daemon VSA '[chars]' (no

value field or invalid length)

VSA format error in daemon user

configuration.

Parsing error on daemon VSA '[chars]' (no

value field or invalid length)

VSA format error in daemon user

configuration.

Parsing error on daemon VSA '[chars]',

order number [dec] (not 0-254) is not
supported

VSA format error in daemon user

configuration.

Parsing error on daemon VSA '[chars]',

order number [dec] (not 0-254) is not
supported

VSA format error in daemon user

configuration.

Parsing error on daemon VSA '[chars]'

(invalid type field)

VSA format error in daemon user

configuration.

Parsing error on daemon VSA '[chars]'

(invalid type field)

VSA format error in daemon user

configuration.

VSA [dec] ([chars]) not found in daemonto-nas tables after string comparing

VSA not found in the deamon to NAS

mapping table.

VSA [dec] ([chars]) not found in daemonto-nas tables after string comparing

VSA not found in the deamon to NAS

mapping table.

Table [chars] entry [dec] has inconsistent

ignore flag and standard attribute type

An internal software error occurred.

Table [chars] entry [dec] has inconsistent

ignore flag and standard attribute type

An internal software error occurred.

[chars]: [dec] [dec]

The deadtimer expiry event repeatedly

occured with a deadtime value of zero. This
could lead to cpu hogging by radiusd
process.

[chars]: [dec] [dec]

The deadtimer expiry event repeatedly

occured with a deadtime value of zero. This
could lead to cpu hogging by radiusd
process.

[chars]: [chars]

radiusd failed to register error codes.

[chars]: [chars]

radiusd failed to register error codes.

WARNING: Cannot obtain handle for the

interface [chars]: [chars]

Error encountered while obtaining handle

for the interface specified as the source
interface.

WARNING: Cannot obtain handle for the

interface [chars]: [chars]

Error encountered while obtaining handle

for the interface specified as the source
interface.

WARNING: No IP address configured for

[chars], using default address instead:
[chars]

There is no IP address configured for the

specified interface.

WARNING: No IP address configured for

[chars], using default address instead:
[chars]

There is no IP address configured for the

specified interface.

WARNING: No IP address has been

configured for [chars]

There is no IP address configured for the

specified interface.

WARNING: No IP address has been

configured for [chars]

There is no IP address configured for the

specified interface.

WARNING: Specified source interface

[chars] is not present: [chars]

The interface specified as source interface

is not present.

WARNING: Specified source interface

[chars] is not present: [chars]

The interface specified as source interface

is not present.

Warning: Server [chars]/[dec]/[dec] is not

defined

An internal software error occurred.

Warning: Server [chars]/[dec]/[dec] is not

defined

An internal software error occurred.

WARNING: Specified source interface

[chars] is not UP

The interface specified as source interface

is not UP.

WARNING: Specified source interface

[chars] is not UP

The interface specified as source interface

is not UP.

Encountered bad attribute length [dec]

(attr [dec]) while [chars], ignored

An internal software error has occurred.

Encountered bad attribute length [dec]

(attr [dec]) while [chars], ignored

An internal software error has occurred.

Encountered bad attribute type [dec] while

[chars], ignored
An internal software error has occurred.

Encountered bad attribute type [dec] while

[chars], ignored
An internal software error has occurred.

Cannot convert accounting task id to

accounting session id: [chars]

Accounting task id is probably larger than

2^24 - 1

Cannot convert accounting task id to

accounting session id: [chars]

Accounting task id is probably larger than

2^24 - 1

reply attr size=[dec] not equal to sum of

parts=[dec]

The length of the reply attribute does not

equal its parts.

reply attr size=[dec] not equal to sum of

parts=[dec]

The length of the reply attribute does not

equal its parts.

Using incorrect AAA attribute for

RAD_ACCT_SESSID_ATTR [chars]

Check consistancy between radius_table

and nas_to_daemon_av_table

Using incorrect AAA attribute for

RAD_ACCT_SESSID_ATTR [chars]

Check consistancy between radius_table

and nas_to_daemon_av_table

Cannot allocate leaf timer - [chars]

None at this time

Cannot allocate leaf timer - [chars]

None at this time

Error in binding socket: [chars]

None at this time

Error in binding socket: [chars]

None at this time

Error in opening socket: [chars]

None at this time

Error in opening socket: [chars]

None at this time

Event connection destroy failed while

[chars]: [chars]

An internal software error occured

Event connection destroy failed while

[chars]: [chars]

An internal software error occured

Failed to initialize event connection for

[chars] (error: [chars])

An internal software error occured

Failed to initialize event connection for

[chars] (error: [chars])

An internal software error occured

Encountered a Cisco VSA while processing

non Cisco VSAs
An internal software error has occurred.

Encountered a Cisco VSA while processing

non Cisco VSAs
An internal software error has occurred.

Cannot query state of interface [chars]

(source interface not applied): [chars]

An internal software error occured.

Cannot query state of interface [chars]

(source interface not applied): [chars]

An internal software error occured.

Invalid authorization type [dec]

encountered while [chars]

An internal software error has occurred.

Invalid authorization type [dec]

encountered while [chars]

An internal software error has occurred.

Found invalid VSA attr [dec] while [chars],

ignored

An internal software error has occurred.

Found invalid VSA attr [dec] while [chars],

ignored

An internal software error has occurred.

Length of attribute [chars] exceeds limit

[chars]

An internal software error has occurred.

Length of attribute [chars] exceeds limit

[chars]

An internal software error has occurred.

snprintf failed while [chars]: [chars]

An internal software error has occurred.

snprintf failed while [chars]: [chars]

An internal software error has occurred.

Found unsupported vendor id [dec] while

[chars], ignored

An internal software error has occurred.

Found unsupported vendor id [dec] while

[chars], ignored

An internal software error has occurred.

[chars]: [chars]

Generic error message used for internal

debugging.

[chars]: [chars]

Generic error message used for internal

debugging.

Error copying CRL from [chars] to [chars]

Internal error.

Failed to delete CA certificate from SysDB

[chars] during merge oper

Internal error.

Failed in MD5 operation for file: [chars],

[chars]

Internal error.

Invalid device name '[chars]'

Internal error.

Installed file, [chars], does not have SAM

index entry

Internal error.

Out of memory

Internal error.

Failed opening file: [chars], [chars]

Internal error.

Could not register SAM_MSGNO message

handler for message id [dec]: [chars]

Internal error.

Failed to encode bag for log entry [dec]

during restore, [chars]

Internal error.

Failed to get item [chars] in SysDB: [hex],

[chars]

Internal error.

Failed to set item [chars] in SysDB: [hex],

[chars]

Internal error.

Failed writing file : [chars], [chars]

Internal error.

NVRAM is not available, nvram process

might have been down.

Internal error.

SPM is not available, [chars].

Internal error.

server terminating..

SAM server caught a signal, and

terminated

SAM log backup file is not present. [chars]

Backup file of SAM log is not present. The

action taken is specified in the string

Found digest mistmatch for SAM's SysDB

name space, the SAM portion of SysDB had
Cannot guarantee the integrity of SAM
been deleted. If SAM backup files exists,
SysDB name space, SAM internal tables
this should not impact SAM's functionality;
had been discarded, and will try to recover otherwise, CA root certificate and CRL will
from backup files.
be lost

SAM detects the CA certificate had expired, SAM found the expired CA certificate in
but accepted by user
table had been accepted by user.

SAM detects the PIE certificate had expired, SAM found the expired CSS certificate in
but accepted by user
table had been accepted by user.

[chars]

SAM general error message with one

prameter.

[chars], [chars]

SAM general error message with two

prameters.

SAM found no ENA device with sufficient

space to backup the modified SAM table,
the change will not be persistent until a
successful ENA installation on a flash
device.

SAM found there is nowhere to backup the

modified SAM table.

Secure digest file is not found, cannot

guarantee the integrity of memory
installed files.

SAM found digest file in NVRAM is missing,

discard the memory packages.

Secure digest file not present, SAM will re- SAM found digest file missing from NVRAM,
init the secure digest file
re-init the file.

SAM failed to initialize log backup file

SAM failed to initalize log backup file in

NVRAM, log entry not backed up

SAM will remove backup files for memory

digest tables and users MUST re-install the SAM found MEM digest compare not
memory packages.
successful, discard the memory packages.

[chars]

SAM general warning message.

[chars] is detected insecure, backup not

restored

Internal error.

[chars] has been changed since last

installed.

Internal error.

[chars]

See Manual

[chars]: [dec]

See Manual

[chars]

See Manual

[chars]

See Manual

[chars]: [dec]

See Manual

[chars]

See Manual

[chars]

See Manual

[chars]: [dec]

See Manual

[chars]

See Manual

[chars]: [chars]

Details an error occurring in the boot

sequence.

Failed to update the SanOS and X-Scale

clocks

An Error occurred when trying to send clock

update to SanOS. SanOS and X-Scale
clocks will not be updated automatically.
The main effect is on the time displayed in
debug messages and in the SanOS/X-Scale
syslog messages.

Event handler function [chars] failed:

[chars]

A failure occurred when trying to use event

handling.

[chars]

See Manual

[chars]: [dec]

See Manual

[chars]

See Manual

SanOS Driver initialisation failed: [chars]:

[chars]

A failure occurred during the process

startup of the SanOS Driver. This is most
likely caused by a failure of some piece of
infrastructure used by the SanOS Driver.
The error message may give an indication
of the root cause of the failure.

Error in initiating attach session: [chars]

A failure occurred when initiating an attach

session

[chars]

Details an error occurring in the image.

[chars]

A failure occurred when trying to use the

connection infra.

[chars]

See Manual

[chars]: [dec]

See Manual

[chars]

See Manual

IPCP function [chars] failed, returning:

[chars]

A failure occurred when trying to use IPCP.

Attach module Received an invalid

message from IPCP: [chars]

Details an error occurring in message

passing

Syslog module received an invalid message Details an error occurring in message

from IPCP: [chars]
passing
[chars]

See Manual

[chars]: [dec]

See Manual

[chars]

See Manual

[chars]
[chars]

Details information about the image status.

Details information about the boot.

[chars]

See Manual

[chars]: [dec]

See Manual

[chars]

See Manual

[chars]

See Manual

[chars]: [dec]

See Manual

[chars]

See Manual

[chars]

An internal software fatal error occurred.

[chars] [chars]

An internal software error occurred.

[chars]

An internal software error occurred.

Message chan connect ([chars]) failed

Internal error.

Unable to find a delete entry for : [chars]

Internal error.

SPM server received invalid event : [chars] Internal error.

Cannot allocate memory in function [chars]

()
Internal error.

[chars]

Internal error.

Error in opening secure file : [chars]

Internal error.

pthread create error : [chars]

Internal error.

pthread attr init error : [chars]

Internal error.

pthread set detach state error : [chars]

Internal error.

Unknown pulse code ([dec]) received

Internal error.

Could not register async handlers : [chars] Internal error.

Could not register SPM_MSGNO message

handler for message id - [dec] : [chars]

Internal error.

Could not reply to client message : [chars] Internal error.

Delete file [chars] token mismatch

Internal error.

[chars] [chars] [chars]

Error description, client address, error.

[chars] [chars]

Error description, error.

[chars]

SSH encounterd some error.

Cannot allocate memory in function [chars] Internal error. System is out of memory ()
malloc failed.

Cannot bind to sysdb in function [chars]()

Internal error.

Cannot get datalist in function [chars]()

Internal error.

sysdb_item_delete failed for tuple [chars]

in function [chars]()

Internal error.

Cannot pack tuple in function [chars]()

Internal error.

sysdb_item_set failed for tuple [chars] in

function [chars]()

Internal error.

Failed authentication attempt by user

'[chars]' from '[chars]' on '[chars]'

SSH encountered authentication warning.

The requested term-type '[chars]' is not

supported

The sshd encountered a warning condition.

[chars]

The sshd encountered some problem in

genric nature or plain information.

Successfully authenticated user '[chars]'

from '[chars]' on '[chars]'(cipher '[chars]',
mac '[chars]')

The sshd successful login information.

Successfully authenticated user '[chars]'

from '[chars]' on '[chars]'(cipher '[chars]',
mac '[chars]', command '[chars]')

The sshd successful login information.

Failed to encode bag information

for \'[chars]\' - [chars]

An internal software error occurred.

Failed to unregister bags - [chars]

An internal software error occurred.

[chars]: [chars]

Error encountered in debug module.

Failed to register EDM - [chars]

Failed to start the EDM.

Not attaching event handler to socket [dec]

- [chars]
An internal software error occurred.

Error while setting or unsetting TACACS+

[chars] configuration - [chars]

A configuration error has occured.

Error while setting or unsetting [chars] in a

server entry - [chars]
A configuration error has occured.

Cannot create a TACACS+ server entry [chars]

Error occured while creating TACACS+

server entry.

Unable to add the server \'[chars]\' to

group \'[chars]\' - [chars]

A configuration error has occured.

Unable to create the server

group \'[chars]\' - [chars]

A configuration error has occured.

Unable to delete the server \'[chars]\' from

group \'[chars]\' - [chars]
An internal software error occurred.

Unable to delete the server

group \'[chars]\' - [chars]

A configuration error has occured.

Failed to bind to SysDB for path [chars]

after [dec] retries

An internal software error occurred.

Failed to allocate [unsigned int] bytes while tacacsd has failed to allocate the required
[chars]
amount of memory

[chars]: [chars]

Error encountered while handling

messages received by tacacsd.

[chars]: size %zd - [chars]

A message with illegal size was received or

to be sent.

[chars]

An invalid argument was passed to either

the tacacsd or one of its funtions.

Unable to create thread to probe status of

TACACS+ server [chars]/[dec]

An internal software error occurred.

Failed to change server priority - [chars]

Attempt to change priority failed.

[chars]: [chars]

TACACS+ process failed to shutdown

properly.

[chars]: [chars]

TACACS+ process failed to startup properly.

[chars]: [chars]

tacacsd failed to register error codes.

WARNING: Cannot obtain handle for the

interface [chars]: [chars]

Error encountered while obtaining handle

for the interface specified as the source
interface.

WARNING: No IP address has been

configured for [chars]

There is no IP address configured for the

specified interface.

WARNING: Specified source interface

[chars] is not present: [chars]

The interface specified as source interface

is not present.

WARNING: Specified source interface

[chars] is not UP

The interface specified as source interface

is not UP.

Warning: Server [chars] is not configured

An internal software error occurred.

WARNING: Wrong key configured for the

server [chars]/[dec]

Tacacs+ server key configured on the

router is wrong.

No valid command provided for [chars]

An internal software error occured.

Encountered a NULL request pointer while

[chars]

An internal software error occured.

TACACS+ server [chars]/[dec] is DOWN Socket [dec]: [chars]

TACACS+ server is unreachable or down.

TACACS+ server [chars]/[dec] is UP

TACACS+ server is reachable or up.

A time out event has been ignored for

context key [chars] (session [hex])

An internal software error occured.

[chars]: [chars]

Error message for internal debugging

purposes.

Error processing service failure action

change: [chars]

An error occurred in FAA or associated

services whilst it was attempting to process
the creation, update, or removal of default
failure action configuration for a Virtual
Firewall. More information on the course of
the failure is contained in the message.

An error has occured during packet

handling in the FMI base capsulation, and
no error counters can be updated. If errors
are seen for an extended period then it can
be assumed that no packets can be
forwarded through FMI interfaces. This is
likely to be a symptom of a problem in the
Packets have been dropped in the FMI base Packet Forwarding Infrastructure - earlier
capsulation, but no error counts could be
error messages might indicate the root
updated ([chars]).
cause of the problem.

The Firewall Controller failed to remove

interface [chars] (firewall [chars]) from its
database

A call into the IOS-XR AVL tree library

failed. This may result in the firewall
controller unexpectedly restarting after this
message is seen.

The Firewall Controller failed to create an

entry for [chars] [chars]%s[chars] in the
[chars] database

The Firewall Controller has been informed

of the existence of a new interface or
firewall, but attempts to create an entry for
it in the relevant database have failed. The
most likely cause of this problem is a lack
of memory. This will have left the system in
an inconsistent state.

The Firewall Controller failed to update

configuration following [chars] of [chars]
[chars]%s[chars]: [chars]

The Firewall Controller has been informed

of an interface/firewall create/delete by the
firewall application but has failed to update
its configuration. This will have left the
system in an inconsistent state.

The Firewall Controller has been told to

update firewall information as a result of a
firewall state change but has been unable
The Firewall Controller failed to find firewall to find the firewall in the firewall database.
with id [unsigned int] in the firewall
This indicates that the system is in an
database
inconsistent state.

Firewall controller initialisation failed:

[chars]: [chars]

A failure occurred during the process

startup of the firewall controller. This is
most likely caused by a failure of some
piece of infrastructure used by the firewall
controller. The error message may give an
indication of the root cause of the failure.

The Firewall Controller has been informed

of diversion removal for an interface, but
found that the relevant firewall does not
exist in the database. This error message
The Firewall Controller could not find the
indicates an inconsistency in the firewall
firewall with ID [unsigned int] for interface database, which will cause the Firewall
[chars] when removing diversions
Controller process to restart.

The Firewall Controller failed to write an

invalid entry to the the SPU context table
on firewall delete

The Firewall Controller's attempt to set an

invalid entry in the SPU context table
following a firewall delete has failed. This
will have left the system in an inconsistent
state.

The Firewall Controller's attempt to inform

the Service Director of a change to either
The Firewall Controller failed to update the interface/firewall state has failed. This will
Service Director when [chars] [chars]
have left the system in an inconsistent
[chars]%s[chars]: [chars]
state.

The Firewall Controller failed to remove

firewall [chars] from its database

A call into the IOS-XR WAVL tree library

failed. This may result in the firewall
controller unexpectedly restarting after this
message is seen.

Firewall manager initialisation failed:

[chars]: [chars]

A failure occurred during the process

startup of the firewall controller. This is
most likely caused by a failure of some
piece of infrastructure used by the firewall
controller. The error message may give an
indication of the root cause of the failure.

[chars] failed to notify SysMgr of intention

to exit: [chars]

A failure occurred during shutdown of the

specified process, and it was unable to
notify the System Manager that it was
about to exit. In rare cases, this could
result in a failure by the System Manager
to restart the process when it ought to do
so.

Firewall Controller failed to process

configuration change for firewall [chars]:
failed to [chars] default-interface: [chars]

An error occurred in the firewall controller

whilst it was attempting to handle the
default-interface configuration for the
firewall specified in the message.

Firewall controller failed to reset '[chars]'

connection: [chars]

After detecting an error with the connection

to the specified service, the Firewall
controller failed to reset that connection.
This is an internal error. It requires a restart
of the process for recovery.

The Firewall Controller saw an interface

handle mismatch when updating FMI
information for interface [chars] (firewall
[chars]) in its database

The Firewall Controller has been informed

of the creation of a Firewall Management
Interface, but found that the interface
handle for the interface differs from the
handle in its database. This error message
indicates an inconsistency in the firewall
database, which may result in unexpected
behaviour.

The Firewall Controller [chars] FMI info

already present when updating interface
[chars] (firewall [chars]) in its database

The Firewall Controller has been informed

of the creation of a Firewall Management
Interface that already exists, or has
received an update about a Firewall
Management Interface that does not exist.
This error message indicates an
inconsistency in the firewall database,
which may result in unexpected behaviour.

The Firewall Controller received a message

from the Firewall Application with an
Firewall Controller received a message from unexpected version. This could indicate a
the Firewall Application with an unexpected mismatch in software versions between
version: expected version [unsigned int],
IOS-XR and the Firewall Application as a
received version [unsigned int]
result of a software upgrade.

Failed to process a received message:

[chars]

The Firewall Controller encountered an

error while processing a message received
from the Firewall Application, for example a
corrupt message. As a result, some virtual
firewalls may not operate correctly.

The Firewall Controller found [chars]

already present when updating interface
[chars] (firewall [chars]) in its database

If the interface ID is already present, the

Firewall Controller has been informed of a
Firewall Application interface create, but
found that its database already contains
the Firewall Application interface ID. If
diversions were already present, the
Firewall Controller has been informed of
diversion creation for an interface, but
found that its database already contains
diversion information for the interface. This
error message indicates an inconsistency in
the firewall database, which may result in
unexpected behaviour.

The Firewall Controller has been informed

of diversion creation for an interface, but
found that the interface handle for the
The Firewall Controller saw an interface
diversion differs from the handle in its
handle mismatch when updating diversions database. This error message indicates an
for interface [chars] (firewall [chars]) in its inconsistency in the firewall database,
database
which may result in unexpected behaviour.

The Firewall Controller has tried to remove

an attachment as a result of a notification
from RSPP, but has failed to do so. This
The Firewall Controller failed to remove an may result in inconsistent data in the
attachment for an interface in firewall
firewall controller and unexpected
[chars]
behaviour.

Failed to receive an event: [chars]

The process failed to receive an event from

the Operating System. As a result, some
aspects of the process may fail to function
correctly.

Two Firewall Management interfaces of the

same type (follow-active or follow-standby)
have been configured on the specified
Two Firewall Management interfaces of the firewall. Both of the interfaces will be
same type have been configured on the
brought down until the conflicting
same firewall ([chars]).
configuration is removed.
[chars] intf cant be moved from one cgn
instance to another without first removing
it from the latter

ServiceApp interface cannot be moved

from one cgn instance to another without
first removing it from the latter.

[chars] intf cant be moved from one cgn

instance to another without first removing
it from the latter

ServiceApp interface cannot be moved

from one cgn instance to another without
first removing it from the latter.

Information received for Current inst

[chars] and New inst [chars] for interface
[chars] are different

The received instance info for this interface

is same as waht had already been
configured.

Information received for Current inst

[chars] and New inst [chars] for interface
[chars] are different

The received instance info for this interface

is same as waht had already been
configured.

It is fine to have Current inst [chars] and

New inst [chars] for interface [chars] as
same

The received instance info for this interface

is same as what had already been
configured.

It is fine to have Current inst [chars] and

New inst [chars] for interface [chars] as
same

The received instance info for this interface

is same as what had already been
configured.

Configuration failed to apply for cgn

'[chars]'. Use 'show cgn trace master-agent some core(s) not responding from the
apply reverse' command for failure details. Roddick.
Configuration failed to apply for cgn
'[chars]'. Use 'show cgn trace master-agent
apply reverse' command for failure details.
[chars]
[chars]

some core(s) not responding from the

Roddick.
EA failed to apply the config.
EA failed to apply the config.

[chars]:[dec]:[chars]

A failure occurred during the initialization

of the CGN process on a particular node.
The process will be restarted. Until the
process starts successfully, any

[chars]:[dec]:[chars]

A failure occurred during the initialization

of the CGN process on a particular node.
The process will be restarted. Until the
process starts successfully, any

[chars] IP address:[chars] is INVALID

The ip address is invalid.

[chars] IP address:[chars] is INVALID

The ip address is invalid.

[chars]: Error code: [dec]. Error msg:

[chars]

An LWM related operation failed.

[chars]: Error code: [dec]. Error msg:

[chars]
[chars]:[chars]
[chars]:[chars]

An LWM related operation failed.

Message Q operation failed.
Message Q operation failed.

[chars]

Roddick was not updated with change in vrf

db.

[chars]

Roddick was not updated with change in vrf

db.

[chars]:[chars]

An SD related operation failed.

[chars]:[chars]

An SD related operation failed.

Inside IP: [chars] And Port: [dec] Statically

Mapped To Outside IP:[chars] And Port:
[dec]

The static port mapping requested has

succeeded.

Inside IP: [chars] And Port: [dec] Statically

Mapped To Outside IP:[chars] And Port:
[dec]

The static port mapping requested has

succeeded.

[chars]

The VRF database in cgn-ma was not

updated .

[chars]

The VRF database in cgn-ma was not

updated .

[chars]

CGN modules are failed to allocate memory

due to low memory conditions in the
System.

[chars]

CGN modules are failed to allocate memory

due to low memory conditions in the
System.

Could not register the application with the

checkpointing server: [chars]

Failed to register an application with the

checkpointing server.

Could not register the application with the

checkpointing server: [chars]

Failed to register an application with the

checkpointing server.

Got a null [chars] but non-null value was

expected

Failed to do further processing because we

got a null data when a non-null value was
expected.

Got a null [chars] but non-null value was

expected

Failed to do further processing because we

got a null data when a non-null value was
expected.

Could not save a record into a

checkpointing table: [chars]

Failed to save a record into the given

checkpointing table.

Could not save a record into a

checkpointing table: [chars]

Failed to save a record into the given

checkpointing table.

Failed to initialize [chars]: [chars]

Could not initialize a table with the

checkpointing server.

Failed to initialize [chars]: [chars]

Could not initialize a table with the

checkpointing server.

Could not recover the checkpointed

[chars]: [chars]

Failed to recover a checkpointed table.

Could not recover the checkpointed

[chars]: [chars]

Failed to recover a checkpointed table.

Could not delete a record from a

checkpointing table: [chars]

Failed to delete a record from the given

checkpointing table.

Could not delete a record from a

checkpointing table: [chars]

Failed to delete a record from the given

checkpointing table.

Could not reset a record in a checkpointing Failed to reset a record in the given
table: [chars]
checkpointing table.

Could not reset a record in a checkpointing Failed to reset a record in the given
table: [chars]
checkpointing table.

[chars]:[chars]

A sysdb operation failed. See error

message text for details of error. This may
impact some functionality of CGN
depending upon where the error occured.

[chars]:[chars]

A sysdb operation failed. See error

message text for details of error. This may
impact some functionality of CGN
depending upon where the error occured.

Error setting up adjacencies for an

interface: [chars]

An error was encoutered while trying to set

up adjacencny information for a InterFlex
interface. The exact error is detailed in the
error message. Packets will not be
forwarded to the affected interface.

Failure during initialization: [chars]

A failure occurred during the initialization

of the InterFlex EA process on a particular
node. The process will be restarted. Until
the process starts successfully, any
InterFlex interface pairs located on that
node will not come up. (If there is a
standby node the interfaces should come
up on the standby).

Error while sending messages to Service

Director: [chars]

A problem was encountered while trying to

send a batch of messages to the Service
Director. The Service Director may not be
up to date with the state of services on this
node, so InterFlex interfaces located on this
node may fail to forward packets.

Error while sending messages to Service

Director at SSC batch end: [chars]

A problem was encountered while trying to

send a batch of messages to the Service
Director. The Service Director may not be
up to date with the state of services on this
node, so InterFlex interfaces located on this
node may fail to forward packets.

A problem was encountered while trying to

send a single message to the Service
Director. The Service Director may not be
up to date with the state of this services on
this node, so the associated InterFlex
Error while sending message about [chars] interfaces located on this node may fail to
to Service Director: [chars]
forward packets.

The Interflex EA library was unable to

synchronize interfaces

In order to correct any problems, the

Interflex EA will reconnect to IM to prompt
a resync. If this message is displayed then
this resync is failing. This may cause
configured interfaces to no longer forward
traffic, or interfaces which have been shut
down or deleted to continue to do so.

Failed to cleanup after interface creation

failed. Error: [chars]

The Interflex Manager failed to completely

clean up interface state after an interface
creation failed. This will have left the
system in an inconsistent state. The most
likely reason for this error is memory
exhaustion.

The Interflex Manager failed to clean up

interface from interflex db after an
interface creation failed. This will have left
the system in an inconsistent state. The
Failed to delete interface from interflex DB. most likely reason for this error is memory
Error: [chars]
exhaustion.

The Interflex Manager failed to completely

clean up interface from the DPC queue
after an interface creation failed. This will
have left the system in an inconsistent
Failed to remove interface from DPC queue. state. The most likely reason for this error
Error: [chars]
is memory exhaustion.

Failed to get interface bandwidth from

platform at initialization of Interflex. Error:
[chars]

The Interflex Manager failed to get the

interface bandwidth from platform at the
startup. The process will be automatically
restarted, if it keeps restarting with same
message *DDTS*

The Interflex Manager failed to get

supported card type from platform at
Failed to get the supported card types from startup. The process will be automatically
platform at initialization of Interflex. Error: restarted, if it keeps restarting with same
[chars]
message *DDTS*

Failed to get max number of interfaces

from platform at initialization of Interflex.
Error: [chars]

The Interflex Manager failed to get max

number of interfaces from platform at
startup. The process will be automatically
restarted, if it keeps restarting with same
message *DDTS*

Failed to get node id from platform at

initialization of Interflex. Error: [chars]

The Interflex Manager failed to get the

node id from the platform at startup. The
process will be automatically restarted, if it
keeps restarting with same message
*DDTS*

Unable to reconnect to perform a resync:

[chars]

The Interflex Manager process was unable

to reconnect to another process in order to
prompt a resync. Interflex may now be out
of sync with the rest of the system until it
is restarted.

There were not enough hardware MAC

addresses available to assign to the
configured interfaces.

The Interflex Manager was unable to obtain

enough MAC addresses for the configured
Interflex interfaces. The system has a finite
number of MAC addresses in the hardware,
which are all currently used.

There were not enough hardware MAC

addresses available to assign to the
configured interfaces while resync.

The Interflex Manager was unable to obtain

enough MAC addresses for the configured
Interflex interfaces. The system has a finite
number of MAC addresses in the hardware,
which are all currently used.

Failure during initialization. Error: [chars]

A failure occurred during the initialization

of the IPSec SVI EA process on a particular
node. The process will be restarted. Until
the process starts successfully, any IPSec
SVI interfaces located on that node will not
come up. (If there is a standby node the
interfaces should come up on the standby).

[chars]

An unexpected internal error has occurred

in the IPSec SVI EA process. The process
will restart.

[chars] : [chars]

An unexpected internal error has occurred

in the IPSec SVI EA process. The process
will restart.

Error while [chars]ing [unsigned int]

interfaces: [chars]

An error occurred while attempting to

program HW for IPSec SVI on specified
node. The interfaces will not come up. If
there is a standby node configured for the
interfaces, they may come up on the
standby.

Received request for an interface

(0x[pointer]) that is not in our database

The IPSec SVI EA process received a

request to process an interface that does
not exist in its database. This indicates
some sort of internal inconsistency.

Error while sending messages to Service

Director: [chars]

A problem was encountered while trying to

send a batch of messages to the Service
Director. The Service Director may not be
up to date with the state of services on this
node, so IPSec SVI interfaces located on
this node may fail to forward packets.

A problem was encountered while trying to

send a single message to the Service
Director. The Service Director may not be
up to date with the state of this services on
this node, so the associated IPSec SVI
Error while sending message about [chars] interfaces located on this node may fail to
to Service Director: [chars]
forward packets.

While the IPSec SVI EA process was

checking the state for the specified
interface, an error was encountered. The
An error occurred while checking the state interface in question may be left in an
for '[chars]': [chars]
inconsistent state.

A failure occurred during the initialization

of debug for the NetIO caps. If this occured
during an upgrade operation then it will
cause the NetIO process to reload.
Otherwise this will cause the capsulation to
Failure of debug intialization during [chars]. be unloaded, and an error returned to the
Error: [chars]
user.

Failure initializing tracing ([chars] buffer).

Error: [chars]

A failure occurred during the initialization

of tracing for the NetIO caps. This will
cause the capsulation to be unloaded, and
an error returned to the user.

[chars]

Internal error.

[chars]

Internal error.

[chars]

Internal error.

[chars]

Internal Warning.

[chars]

Internal Warning.

[chars]

Internal Warning.

[chars]

Internal information. for example: track

state changes.

[chars]

Internal information. for example: track

state changes.

[chars]

Internal information. for example: track

state changes.

[chars] : [chars]

An error has occurred while doing a sysdb

operation. See the message text for error
details.

A clone request is to be enqueued as the

producer is not available to handle ens
Could not enqueue as the queue size [dec] request. Enqueuing a clone request to alert
is exceeded
clone queue failed due to queue size limit.

Cannot update flow record due to nfsvr

isn't up yet.

The monitored flow has traffic issues as

indicated by the react trigger. The problem
is introduced either at some upstream
router or even at the traffic source itself.
[chars]: [chars]|[chars]|ID [unsigned int]|
Alternatively, a configuration mismatch
React [unsigned int] [chars]|Src_IP [chars], between the traffic source and this router
Src_Port [unsigned int], Dst_IP [chars],
(for the flow data rates etc) can cause this
Dst_Port [unsigned int]
error.

The monitored flow has traffic issues as

indicated by the react trigger. The problem
is introduced either at some upstream
router or even at the traffic source itself.
Alternatively, a configuration mismatch
between the traffic source and this router
[chars]: [chars]|[chars]|Class [chars]|React (for the flow data rates etc) can cause this
[unsigned int] [chars]
error.

The monitored flow has traffic issues as

indicated by the react trigger. The problem
is introduced either at some upstream
router or even at the traffic source itself.
[chars]: [chars]|[chars]|ID [unsigned int]|
Alternatively, a configuration mismatch
React [unsigned int] [chars]|Src_IP [chars], between the traffic source and this router
Src_Port [unsigned int], Dst_IP [chars],
(for the flow data rates etc) can cause this
Dst_Port [unsigned int]
error.

The monitored flow has traffic issues as

indicated by the react trigger. The problem
is introduced either at some upstream
router or even at the traffic source itself.
Alternatively, a configuration mismatch
between the traffic source and this router
[chars]: [chars]|[chars]|Class [chars]|React (for the flow data rates etc) can cause this
[unsigned int] [chars]
error.

The monitored flow has traffic issues as

indicated by the react trigger. The problem
is introduced either at some upstream
router or even at the traffic source itself.
[chars]: [chars]|[chars]|ID [unsigned int]|
Alternatively, a configuration mismatch
React [unsigned int] [chars]|Src_IP [chars], between the traffic source and this router
Src_Port [unsigned int], Dst_IP [chars],
(for the flow data rates etc) can cause this
Dst_Port [unsigned int]
error.

The monitored flow has traffic issues as

indicated by the react trigger. The problem
is introduced either at some upstream
router or even at the traffic source itself.
Alternatively, a configuration mismatch
between the traffic source and this router
[chars]: [chars]|[chars]|Class [chars]|React (for the flow data rates etc) can cause this
[unsigned int] [chars]
error.

The monitored flow has traffic issues as

indicated by the react trigger. The problem
is introduced either at some upstream
router or even at the traffic source itself.
[chars]: [chars]|[chars]|ID [unsigned int]|
Alternatively, a configuration mismatch
React [unsigned int] [chars]|Src_IP [chars], between the traffic source and this router
Src_Port [unsigned int], Dst_IP [chars],
(for the flow data rates etc) can cause this
Dst_Port [unsigned int]
error.

The monitored flow has traffic issues as

indicated by the react trigger. The problem
is introduced either at some upstream
router or even at the traffic source itself.
Alternatively, a configuration mismatch
between the traffic source and this router
[chars]: [chars]|[chars]|Class [chars]|React (for the flow data rates etc) can cause this
[unsigned int] [chars]
error.

Failed to [chars] debug for service

diversion drop caps: [chars]

A problem with the debug infrastructure

was encountered by the service diversion
drop processing in NetIO. This is not fatal,
and simply means that the 'debug services
diversion drop' commands may be
unavailable. All non-verbose messages are
still traced in a circular buffer, and the
most recent of these can be inspected with
the 'show services diversion drop trace'
commands.

Unable to [chars] packet (can't [chars])

[chars]%s

A pre-routed packet created on the router's

host stack hit a problem during service
diversion processing. The packet was
dropped.

Failed to [chars] when initializing service

diversion drop caps (id [dec]): [chars]

A failure occurred when installing the

capability in NetIO to process slow path
packets for service diversion. If this
occurred during an upgrade operation then
it will cause the NetIO process to reload.
Otherwise this will cause the capsulation to
be unloaded,and an error will be returned
to the user.

Unable to undivert packet (can't [chars]):

[chars]

A packet could not be sent out to its

original destination after firewalling. The
packet was dropped.

An error was detected whilst performing

[chars] for [chars] (Error: [chars]). Traffic
Diversion may now be inconsistent.

Some aspect of diversion implementation

has failed. This means that traffic may be
inconsistently diverted for the specified
interface (ie traffic may be diverted to the
service card in the ingress direction, but
not on egress). Note that, where the error
message indicates a single interface that is
affected, there may also be other
attachments impacted by the error.

Error receiving event: [chars]

An error occured receiving an event from

the OS. The process will restart.

A persistent error has occured during the

implementation of one or more
attachments. Diversion may be in an
inconsistent state

Whilst attempting to implement one or

more attachments, the service diversion
infrastructure has hit one or more problems
that were not solved by a retry, and as
such one or more diversions may be in an
inconsistent state. Retries will continue to
be made, and a further message will be
printed if this situation clears.

Failure during intialization of RSPP MA

[chars]. Error: [chars]

A failure occurred during the initialization

of the RSPP MA, the process responsible for
managing the diversion of packets to
services such as firewalls. The initialization
will be aborted and retried.

Non-fatal error during intialization of RSPP

MA [chars]: [chars] Continuing with
initialization.

A non-fatal failure occurred during the

initialization of the specified module of
RSPP MA, the process responsible for
managing the diversion of packets to
services such as firewalls. This will typically
mean that some level of debugging
support will not be provided for the process
(e.g. error codes will not be decoded), but
the functioning of the process is not
otherwise affected. Restarting the process
should restore full debugging support.

An error has occurred while removing the

diversion implemented for the given
interface. The error string will give more
Failed to process local configuration delete detail on the type of error that has
for interface [chars]. Error: [chars]
occurred.

An error has occurred while implementing

Failed to process local configuration update the diversion required for the given service
for attachment of service [chars] of type
attachment. The error string will give more
[chars] to interface [chars] with attachment detail on the type of error that has
ID [chars]. Error: [chars]
occurred.

RSPP MA was started when the firewalls

package was not installed. Exiting

RSPP MA, the service diversion

management agent, could not complete
initialization as the firewall service package
could not be found in the current installed
image. Restart will not be attempted.

An error has occurred while indicating the

deletion of the given service attachment
removal to nodes other than that local to
the interface indicated. Packet diversion
may now be inconsistent. The error string
Failed to publish local configuration delete will give more detail on the type of error
for interface [chars]. Error: [chars]
that has occurred.

An error has occurred while indicating the

occurence of the given update to nodes
other than that local to the interface
Failed to publish local configuration update indicated. Packet diversion may now be
for attachment of service [chars] of type
inconsistent. The error string will give more
[chars] to interface [chars] with attachment detail on the type of error that has
ID [chars] to remote nodes. Error: [chars]
occurred.

An error has occurred while processing the

attachment of a service to an interface
Failed to process remote config notification remote to this node. Packet diversion may
of [chars] of attachment of service [chars] now be inconsistent on this node. The error
of type [chars] to interface [chars] with
string will give more detail on the type of
attachment ID [chars]. Error: [chars]
error that has occurred.

If a virtual firewall or other service is

attached to an interface, then all cards in
the system need to know. Similarly, if a
service attachment is deconfigured, then
all cards needs to be notified. This will not
happen if the interface's line card is down
(eg a preconfigured attachment is removed
while the card is absent from the chassis
and then re-inserted). A backup
mechanism exists for this case, that
ensures that any attachments that were
deconfigured in such a situation really are
removed globally. This error indicates that
a problem occurred with this backup
mechanism. So if a service attachment was
deconfigured while the card was down, the
rest of the system might not have caught
Error deleting any stale attachment
up, and could still be diverting or dropping
publications to remote nodes. Error: [chars] traffic for that interface.

Attachment of service [chars] of type

[chars] to interface [chars] with attachment The same service attachment has been
ID [chars] invalid due to duplicate
configured on two or more interfaces,
attachment to interface [chars]. Both
resulting in both attachments being viewed
attachments will be invalidated.
as failed and moved in to failure state.

An error has occurred processing an invalid

configuration whereby the same service
attachment has been configured on two or
more interfaces (which should result in
Error withdrawing attachment of service
both attachments being viewed as failed
[chars] of type [chars] to interface [chars] and moved in to failure state). Packet
with attachment ID [chars] (invalid due to diversion may now be inconsistent. The
duplicate attachment to interface [chars]): error string will give more detail on the
[chars]
type of error that has occurred.

The given attachment configuration, which

Attachment of service [chars] of type
was previously invalid due to duplicate
[chars] to interface [chars] with attachment attachments being configured on different
ID [chars] now valid due to removal of
interfaces, is now valid as the duplicate
duplicate attachment to interface [chars]. attachment configuration has been
Attachment will be reimplemented.
removed.

Error reinstalling attachment of service

[chars] of type [chars] to interface [chars]
with attachment ID [chars] (now valid due
to removal of duplicate attachment to
interface [chars]): [chars]

The given attachment configuration, which

was previously invalid due to duplicate
attachments being configured on different
interfaces, is now valid as the duplicate
attachment configuration has been
removed, but an error has occurred
reimplementing the attachment. The error
string given should give more details on
the error that has occurred.

One or more errors occurred in RSPP MA,

the service diversion management agent,
during the processing of a set of
configuration detailing the failure policies
to be applied in the event of service failure.
The configured failure policies may now not
Errors occurred processing batch of failure be implemented on the node indicated.
action notifications. Total Errors: [unsigned The error string will give more detail on the
int], First Error [chars]
type of error that has occurred.

Failed to signal [chars] of batch of remote

config publications. Error: [chars]

An error has occurred sending information

on service attachments to interfaces local
to the node to remote nodes.

An error has occurred during the handling

of a notification from Sysmgr indicating a
Error handling change in redundancy state. change in the redundancy state of the card
Error [chars]
indicated (e.g. from standby to online).

Unable to handle redundancy state

notification. New redundancy state
[unsigned int], previous state [unsigned
int]

A notification has been received from

Sysmgr indicating that the redundancy
state (e.g. active, standby, etc) of the card
has changed to a state unknown to RSPP
MA. RSPP MA will continue to use the old
state.

Failed to resync diversions correctly. Error:

[chars]

An error has occurred following a restart of

RSPP MA in the reconciliation of persistent
data structures with the current
configuration. Packet diversion may now be
inconsistent.

One or more errors occurred in RSPP MA,

the service diversion management agent,
during the processing of a set of
notifications from Service Director,
containing service locations and diversion
information. Diversions for service
attachments may now be inconsistent on
Errors occurred processing batch of Service the given node. The error string will give
Director notifications. Total Errors:
more detail on the type of error that has
[unsigned int], First Error [chars]
occurred.

When a service attachment (e.g. a firewall

attachment) is configured on an interface,
the local RSPP MA process (the service
diversion management agent) must
request information on the attached
service from Service Director to be able to
implement the required diversion. This
Error requesting service information from error indicates that a problem has arisen in
the Service Director on services referenced this request. The error string given should
by the last batch of attachment or failure
give more details on the error that has
action configuration. Error [chars]
occurred.
This message should only be seen after a
corresponding IMP_ERROR message has
All pre-existing persistent errors have been been seen. It indicates that any problems
cleared. All diversion should now be
with diversions should now have been
operating correctly.
resolved.

Problem ensuring an orderly exit: [chars]

The process implementing service

diversions (eg for virtual firewalls) has just
exited, since the last service attachments
have just been deconfigured. As part of this
orderly shutdown, the process tried to
inform System Manager that this was
happening, but hit a problem in signalling
this fact. The system should have
recovered from this problem fully; however,
very rarely it is possible that some other
service attachment configuration in the
same commit could be rejected.

Error encountered by REPO whilst

processing a dual adjacency update
request for the adjacency for interface
handle [hex]: [chars]

An error has occurred in the FIB library

responsible for implementing diversions
(e.g. for virtual firewall attachments) on a
service card, following a call by FIB to
retrieve the post-egress diversion
forwarding information. If the interface
given has a service attached then
forwarding following egress diversion to
this service may now be incorrect as a
result of this error.

Error initializing REPO: [chars]

An error has occurred during the

initialization of the FIB library responsible
for implementing diversions (e.g. for virtual
firewall attachments). Service attachments
may now fail to be implemented properly
as a result of this error.

An error has occurred in the IPC between

the Management Agent for service
diversions (e.g. for virtual firewall
attachments) and the FIB Library
responsible for implementing them, in the
initialization stage. The initialization will be
Error encountered by REPO whilst
aborted, and no changes to service
processing the initialization message from attachment configuration will be made in
RSPP MA: [chars]
the forwarding plane

An error has occurred in the FIB library

responsible for implementing diversions
(e.g. for virtual firewall attachments)
following a request from FIB to check
Error encountered by REPO whilst
whether a diversion should be in place for
processing an adjacency update request for the given adjacency. The adjacency given
the adjacency for interface handle [hex]:
may now be incorrect as a result of this
[chars]
error.

Error encountered by REPO whilst

processing the diversion update message
([hex]) from RSPP MA: [chars]

An error has occurred in the IPC between

the Management Agent for service
diversions (e.g. for virtual firewall
attachments) and the FIB Library
responsible for implementing them, during
a diversion update. The update will not be
implemented.

Failed to initialize diversion manager

external data manager, error: [chars].
Diagnostic show commands may not
function correctly, other functionality is
unaffected.

During intialization of the EDM an error

occurred. The EDM was not successfully
registered, so show commands and other
manageability applications may not
function correctly. Otherwise the diversion
manager will work correctly.

The diversion manager was unable to

connect to IM Proxy to register as an
interface capsulation. Diversion information
may not be correctly applied or
Failed to connect to IM Proxy. Error: [chars] inconsistent.

Failure [chars] during intialization of

diversion exectution agent. Error: [chars]

A failure occurred during the initialization

of the RSPP REX library. This is used to
divert packets, e.g. to a virtual firewall.

During processing of a new or updated

diversion, insufficient memory was
Diversion manager failed to get memory
available. The diversion information was
[chars]. Diversions (e.g to a virtual firewall) not applied, and future updates may also
may not have been correctly applied.
not be applied correctly.

Unable to send a reply to diversion

manager's client. Error: [chars]

The diversion manager process was unable

to send a reply to a message sent to one of
its clients. Diversion information may be
inconsistent.

Diversion manager failed to communicate

with SysDB. Error: [chars]

The diversion manager was unable to

communicate with SysDB. Notifications
may be missed, and manageability
functionality may not be available.

The diversion manager has reached an

unexpected situation ([chars] dumping
core - this is NOT a crash.

An unexpected situation was reached; the

diversion manager has voluntarily
produced a core dump for debugging
purposes. This does not affect the
operation of the diversion manager.

An error occurred during initialization of the

service ingress diversion debug facility. The
'debug services diversion rio ea' command
will not function correctly. Otherwise
service ingress diversion will work correctly.
Executing the command 'proc restart
rspp_rio_ea' for the node where the error
Failed to initialize service ingress diversion message originated might resolve this
debug facility: [chars]
condition.

Failed to remove service ingress diversion

(ifh=[hex]). Could not remove [chars]:
[chars]

An error occurred during service ingress

diversion removal from the specified
interface.

During initialization of the EDM an error

occurred. The EDM was not successfully
registered, so show commands and other
manageability applications may not
function correctly. Otherwise service
ingress diversion will work correctly.
Executing the command 'proc restart
rspp_rio_ea' for the node where the error
Failed to initialize service ingress diversion message originated might resolve this
External Data Manager: [chars]
condition.

An error was received during event_block:

[chars]

The service ingress diversion process

received an error while waiting for events
from other processes in the system. The
process will be restarted.

RSPP RIO event manager create failed:

[chars].

An error occurred during initialization of

service ingress diversion process. The
process could not create an event queue
used to communicate with other processes
in the system. The initialization will be
aborted and retried.

Could not re-synchronize with feature

manager process: [chars]

During the initialization of ingress diversion

process, feature manager process
requested a replay of all current diversions
but the replay operation failed.

IMP initialization failed during [chars]:

[chars]

The service ingress diversion process failed

while trying to connect to Interface
Manager Proxy process. The process will be
restarted. If error still exists, execute the
command 'proc restart imp' for the node
where the error message originated.

Ingress Diversion process initialization

failed following [unsigned int] function
call(s): [chars].

An error occurred during the initialization of

service ingress diversion process. The
initialization will be aborted and retried.
Current and future service to an interface
will fail until successful process
initialization.

During ingress diversion installation or

update, failed to get memory for [chars]

During processing of a new or existing

service ingress diversion, insufficient
memory was available. The diversion
information was not applied, and future
updates may also not be applied correctly.

An error occurred during initialization of the

trace facility. There will be no trace
messages for service ingress diversion. The
'show services diversion rio ea trace'
command on this node will not function
correctly. Otherwise service ingress
diversion will work correctly. Executing the
command 'proc restart rspp_rio_ea' for the
Failed to initialize service ingress diversion node where the error message originated
trace facility: [chars]
might resolve this condition.

\nassertion '[chars]' failed in [chars]

([chars]:[dec])

Assertion Failure.

The service ingress diversion process has

reached an unexpected situation ([chars]
dumping core - this is NOT a crash.

An unexpected situation was reached; the

service ingress diversion process has
voluntarily produced a core dump for
debugging purposes. Unless other
symptoms are seen than it can be assumed
that the system has recovered.

The service ingress diversion NetIO DLL

capsulation builder function failed. Service
The capsulation build function failed
ingress diversion in NetIO for the specified
because '[chars]' (ifh=[hex]). Error: [chars] interface will not function properly.

The service ingress diversion NetIO DLL

capsulation function failed. Service ingress
The capsulation control function failed
diversion in NetIO for the specified
because '[chars]' (ifh=[hex]). Error: [chars] interface will not function properly.
The service ingress diversion NetIO DLL
capsulation unbuilder function failed.
Service ingress diversion in NetIO for the
The capsulation unbuild function failed
specified interface will not be removed
because '[chars]' (ifh=[hex]). Error: [chars] from NetIO process.

Service ingress diversion NetIO DLL failed

to initialize the debug facility during
[chars]: [chars]

A failure occurred during the initialization

of debug for the service ingress diversion
NetIO DLL. If this occurred during an
upgrade operation then it will cause the
NetIO process to reload. Otherwise this will
cause the capsulation to be unloaded,and
an error will be returned to the user.

An error occurred during initialization of the

trace facility. There will be no NetIO trace
messages for service ingress diversion. The
'show services diversion rio netio trace'
Failed to initialize service ingress diversion command on this node will not function
[chars] trace facility within NetIO process: correctly. Otherwise service ingress
[chars]
diversion will work correctly.
Service ingress diversion NetIO DLL failed
to register the RIO subblock: [chars]

The service ingress diversion NetIO DLL

initialization function failed to register the
RIO subblock type.

Service ingress diversion NetIO DLL

termination failed because '[chars]'. Error:
[chars]

The service ingress diversion NetIO DLL

termination function failed.

The replicated interface owner was unable

to connect to IM Proxy to register as an
interface owner. Diversion information may
Failed to connect to IM Proxy. Error: [chars] not be correctly applied or inconsistent.

Failure [chars] during intialization of

replicated interface owner. Error: [chars]

A failure occurred during the initialization

of the replicated interface owner process.
This means that attaching services (e.g a
firewall) on the card producing this error to
interfaces may not work.

Replicated interface owner failed to get

memory [chars] during diversion update
processing. Diversions (e.g to a virtual
firewall) may not have been correctly
applied, and future diversion may also not
be correctly applied.

During processing of a new or updated

diversion, insufficient memory was
available. The diversion information was
not applied, and future updates may also
not be applied correctly.

Bulked operation to [chars] [unsigned int]

replicated interface(s) (including [hex])
failed with error: [chars]. Packet diversion
may now be incorrectly set up.

During the processing of interface create or

delete notifications an error occurred that
means the interfaces may not have been
replicated or unreplicated correctly. This
might result in the packets that are
diverted to the node being dropped. A user
with cisco-support privileges may find the
interface name corresponding to the given
interface handle using 'show im chains
ifhandle <ifhandle>'

MPF_INFO: [chars]\n

The system is in normal state. This is info

log.

SBC_INFO: [chars]\n

The system is in normal state. This is info

log.

SBC resource monitor: [chars] alarm raised.

System is now congested. All new calls will The system is in congested state. Red
be rejected. cpu usage = [dec], mem state alarm has been raised. No new calls will be
= [dec] \n
accepted

SBC resource monitor: [chars]

The system is not able to carry on

congestion handling.

SBC resource monitor: Alarm cleared.

System is now in normal state. cpu usage
= [dec], mem state = [dec] \n

The system is in normal state. Alarms have

been cleared.

SBC resource monitor: [chars] [dec] \n

Debug messages

[chars]: [chars] \n

Log level in sbc app is set to higher than

nbb_console_unconditional_log_level. Use
errmsg facilty to print error message

[chars]: [chars] \n

Log level in sbc app is set to higher than

nbb_console_unconditional_log_level. Use
errmsg facilty to print error message

[chars]: [chars] \n

Log level in sbc app is set to higher than

nbb_console_unconditional_log_level. Use
errmsg facilty to print error message

[chars]: [chars] \n

Log level in sbc app is set to higher than 40

and less than 50. This is an info message.

[chars]\n SBC billing paths will not be

available

Couldn't not establish the SBC instance

name from SysDB. SBC instance name is
required for the billing cach paths SBC
billing application will not be able to save
billing records.

Error: SBC billing cache location [chars]

[chars]: [chars]. Make sure that SBC billing
drive is installed and formatted. \nSBC
billing paths will not be available

A failure occurred during the creation of an

sbc billing cache path. SBC billing
application will not be able to save billing
records

SBC billing path [chars] [chars] [chars]

The SBC billing cache path might require

some user action to save the billing records
in an SBC-instance-specific directory. SBC
billing will still work properly but the billing
records could either be saved in an SBCshared directory if the SBC instance name
is too long or not saved at all if there is no
space left in the drive.

SBC billing path [chars] [chars] [chars]

The SBC billing cache path mount point

status has changed and is being reported
to the user for an easier access to the SBC
billing records.

Failure during initialization. Error: [chars]

A failure occurred during the initialization

of the SBCSVI EA process on a particular
node. The process will be restarted. Until
the process starts successfully, any SBCSVI
interface located on that node will not
come up. (If there is a standby node the
interfaces should come up on the standby).

[chars]

An unexpected internal error has occurred

in the SBCSVI EA process. The process will
restart.

[chars] : [chars]

An unexpected internal error has occurred

in the SBCSVI EA process. The process will
restart.

Error while [chars]ing [unsigned int]

interfaces: [chars]

An error occurred while attempting to join

together the two halves of some SBCSVI
pairs on the specified node. The pairs will
not come up. If there is a standby node
configured for the pairs, they may come up
on the standby.

Received request for an interface

(0x[pointer]) that is not in our database

The SBCSVI EA process received a request

to process an interface that does not exist
in its database. This indicates some sort of
internal inconsistency.

Error while sending messages to Service

Director: [chars]

A problem was encountered while trying to

send a batch of messages to the Service
Director. The Service Director may not be
up to date with the state of services on this
node, so SBCSVI interfaces located on this
node may fail to forward packets.

A problem was encountered while trying to

send a single message to the Service
Director. The Service Director may not be
up to date with the state of this services on
this node, so the associated SBCSVI
Error while sending message about [chars] interfaces located on this node may fail to
to Service Director: [chars]
forward packets.

While the SBCSVI EA process was checking

the state for the specified interface pair, an
error was encountered. The interface pair
An error occurred while checking the state in question may be left in an inconsistent
for '[chars]': [chars]
state.

A failure occurred during the initialization

of debug for the NetIO caps. If this occured
during an upgrade operation then it will
cause the NetIO process to reload.
Otherwise this will cause the capsulation to
Failure of debug intialization during [chars]. be unloaded, and an error returned to the
Error: [chars]
user.

Failure initializing tracing ([chars] buffer).

Error: [chars]

A failure occurred during the initialization

of tracing for the NetIO caps. This will
cause the capsulation to be unloaded, and
an error returned to the user.

A required control message could not be

sent. The reason for the failure is detailed
in the message. The failure is unexpected,
and likely caused by a failure in the
underlying transport. Services controlled by
this process are likely to be out of sync as a
Failed to send a '[chars]' message: '[chars]' result.

ASSERT failure: [chars]

The process is in an inconsistent state. The

process will exit and restart. All data will be
resynchronised after the restart.

Initialisation failed, module: [chars],

operation: [chars], error: [chars]

The Service Director has failed to start up.

The operation being attempted is detailed
in the error message. The Service Director
will be restarted automatically.

Unexpected error in event loop: [chars]

An unexpected error has been encountered

in the main Service Director event loop.
The Service Director will be automatically
restarted, and should recover by itself.

Insufficient resources: [chars]

There are insufficient resources to perform

some action. The error message contains
more details about what action failed. In
any case, services may not be operating
correctly, and states may be out of sync.

SysMgr didn't respond when told we're

exiting: [chars]

The Service Director attempted to notify

SysMgr that it was exiting and SysMgr
returned an error. If this coincides with an
attempt to configure the locations of a
service, then further error may be
observed from SysDB.

An invalid Service Find request was

received (type [hex])

The Service Director received a batch with

an invalid service type field. This can be
due to message corruption, or due to a
timing issue but is most likely due to an
error in a service process. Except in the
latter case (when it will most probably be
repeated) this error is not fatal.

Invalid SSC is sending updates on node

[hex]. Beginning recovery

A Service Controller process not currently

registered is sending updates from a node.
The Service Director will now attempt to
recover from this by resynchronising with
its clients.

The Service Director process requires a

restart in order to synchronize data. This
message is informational and requires no
further action. The reason for restart is:
[chars]

The Service Director encountered an error

when trying to send a control message,
which could leave the system in an
inconsistent state. The error results from an
unexpected failure in the transport
infrastructure. The process is now
restarting and will then be able to
resynchronize its state, restoring system
consitency. This message is for
informational purposes only, and no further
action is required as a result. On
completion of the resyncronization, the
system will have self-healed, unless any
further errors are encountered.

[chars] [chars] the error is : [chars]

The message indicates the failure in

binding the data.

The message indicates an error in the

Error reason [chars] : Error Function [chars] interface information.

[chars]: unknown msg received ([unsigned The message indicates the message type
int])
received is not a valid one.

Function [chars] : Error reason [chars]

The message indicates the failure in

registering the user service instance in the
database.

error reason:[chars] error function:[chars]

error decriptor:[dec]

The message indicates the failure in

initializing the ltrace module or debug
module.

Info: [chars] Interface: [hex] \n

The message is just an information about

the interface.

Failure during initialization. Error: [chars]

A failure occurred during the initialization

of the SESVI EA process on a particular
node. The process will be restarted. Until
the process starts successfully, any SESVI
interface located on that node will not
come up. (If there is a standby node the
interfaces should come up on the standby).

[chars]

An unexpected internal error has occurred

in the SESVI EA process. The process will
restart.

[chars] : [chars]

An unexpected internal error has occurred

in the SESVI EA process. The process will
restart.

Error while [chars]ing [unsigned int]

interfaces: [chars]

An error occurred while attempting to join

together the two halves of some SESVI
pairs on the specified node. The pairs will
not come up. If there is a standby node
configured for the pairs, they may come up
on the standby.

Received request for an interface

(0x[pointer]) that is not in our database

The SESVI EA process received a request to

process an interface that does not exist in
its database. This indicates some sort of
internal inconsistency.

[chars] : [dec]

The message indicates the failure in

opening or creating the shared memory.

Error while sending messages to Service

Director: [chars]

A problem was encountered while trying to

send a batch of messages to the Service
Director. The Service Director may not be
up to date with the state of services on this
node, so SESVI interfaces located on this
node may fail to forward packets.

A problem was encountered while trying to

send a single message to the Service
Director. The Service Director may not be
up to date with the state of this services on
this node, so the associated SESVI
Error while sending message about [chars] interfaces located on this node may fail to
to Service Director: [chars]
forward packets.

While the SESVI EA process was checking

the state for the specified interface pair, an
error was encountered. The interface pair
An error occurred while checking the state in question may be left in an inconsistent
for '[chars]': [chars]
state.

[chars] = [dec]

The message is just an information of the

role bit.

A failure occurred during the initialization

of debug for the NetIO caps. If this occured
during an upgrade operation then it will
cause the NetIO process to reload.
Otherwise this will cause the capsulation to
Failure of debug intialization during [chars]. be unloaded, and an error returned to the
Error: [chars]
user.

Failure initializing tracing ([chars] buffer).

Error: [chars]

A failure occurred during the initialization

of tracing for the NetIO caps. This will
cause the capsulation to be unloaded, and
an error returned to the user.

Memory allocation failure during ([chars])

SI modules are failed to allocate memory

due to low memory conditions in the
System.

Error happened in sysdb operation

([chars]): Error:[chars]

A sysdb operation failed. Error message

provides the information about this sysdb
operation. If this error happens in
verify/apply module config operation will
not succeed. If this in EDM module then
operational show/get may not work.

A failure occurred during the initialization

of the SI process on a particular node. The
process will be restarted. Until the process
Service initialization error in module[chars]: starts successfully, any SI configuration is
Error([dec]):[chars]
not accepted.

And internal API call errored during

([chars]). Error:[chars]

Invalid argument (mostly NULL) was

passed to SI API.

Failed to perform service director

operation([chars]).Error:[chars]

And API call to service director failed.

Details of the operation are part of the
error message. This may impact service
bringup on the configured location.

A change in role requires Node [chars] to

go down for reboot.

The Service Role Agent has determined a

role change requires a reboot of the
specified node. This is not an error.

SRD Library notification failure: [chars]

The Service Role Daemon client library

received a notification, but was unable to
perform the necessary operations to
execute the client's callback function. The
client process is unaware of a role change
event that has occured, and as such
services running on the affected node are
likely to be out of sync.

ASSERT failure: [chars]

The process is in an inconsistent state. The

process will exit and restart. All data will be
resynchronised after the restart.

Initialisation failed, module: [chars],

operation: [chars], error: [chars]

The Service Role Daemon has failed to

start up. The operation being attempted is
detailed in the error message. The Service
Role Daemon will be restarted
automatically.

Unexpected error in event loop: [chars]

An unexpected error has been encountered

in the main Service Role Daemon event
loop. The Service Role Daemon will be
automatically restarted, and should recover
by itself.

Insufficient resources: [chars]

There are insufficient resources to perform

some action. The error message contains
more details about what action failed.

A node has been set to a role which is not

supported. This could be because the
The role you are attempting to assign is not wrong card is at this location, or no card is
supported by the node you have selected. there.

SRD Unable to process OIR notification:

[chars]

The Service Role Daemon received an LRd

event which it was unable to process. This
could potentially mean that a card does not
have it's specified role enacted, or
removed if it was taken down.

The Service Role Change Agent returned an

error while running on this node. The role
Unable to update role on card with Node ID has not been correctly applied on the
[chars]: [chars]
specified card.

An error occured while setting role. Role

not applied.

Required data was not available when a

timer expired. A role that should be applied
now is unable to be applied.

Interface '[chars]' of type [unsigned int]

already exists as type [unsigned int]

An attempt was made to create an

interface that already existed, but with a
different type. It is likely that the given
interface will no longer be operating as
expected.

Interface '[chars]' of type [unsigned int]

already exists as type [unsigned int]

An attempt was made to create an

interface that already existed, but with a
different type. It is likely that the given
interface will no longer be operating as
expected.

Insufficient memory: [chars]

SVII EA ran out of memory. The exact

operation being attempted is detailed in
the error message.

Insufficient memory: unable to allocate

buffer to handle batch of ppIndex change
notifications from HAL. Some service
interfaces at this location will no longer
work

SVII EA ran out of memory. The exact

operation being attempted is detailed in
the error message.

An error occured during periodic statistics

Failed in checkpoint interaction, resulting in collection for the interface specified. This
zero stats returned for [chars] (expected
means that the statistics (as reported by
length [unsigned int], found [unsigned
eg. 'show interface') will be inaccurate for
int]): [chars]
as long as this error is seen.

Unrecoverable error in event loop. Error:

[chars]

An error (other than EINTR) occured in the

event loop. The process must exit.

Failed to handle forwarder connection

being lost - error: [chars]

The forwarder driver has restarted, but this

process was unable to handle this as the
error was unexpected. It is possible, though
not necessarily true, that slow path packet
processing for some interfaces owned by
this process may be broken.

A failure occurred during the initialization

of the Service Virtual Interface
Failure during intialization of [chars]. Error: infrastructure. This resulted in the restart
[chars]
of the process.

Failed during [chars] stage of sending a

'[chars]' message - Error: [chars]

A control message could not be sent from

the EA to the MA. See error message for a
possible reason. An interface may now be
in the wrong up/down state.

The process was initialized successfully but

Failure communicating readiness to System was unable to inform System Manager of
Manager. Error: [chars]
the success.

The Service Infrastructure was unable to

reconnect to IM: [chars]

If the Service Infrastructure becomes out of

sync with IM, then it reconnects in order to
prompt a resync. If this message is
displayed then it has been able to
reconnect. This may cause configured
interfaces to no longer forward traffic, or
interfaces which have been shut down or
deleted to continue to do so.

A failure occured while processing a SPA

state or type change notification. Service
Failed to report SPA [chars] change to SVIA; interfaces configured on the given SPA may
reason: [chars]; error [chars]
not be appropriately (un)replicated.

Failure during activation of [chars]. Error:

[chars]

A failure occurred during the activation of

the Service Virtual Interface infrastructure.
Activation occurs when the card transitions
to ACTIVE state. This error resulted in the
restart of the process.

Unrecoverable error in event loop. Error:

[chars]

An error (other than EINTR) occured in the

event loop. The process must exit.

A failure has occurred during creation of a

new event manager as part of initialization
Error during setup/creation of [chars]. Error: of SVI infrastructure. This resulted in the
[chars]
restart of the process.

Failure communicating exit to System

Manager. Error: [chars]

The process was unable to inform System

Manager of its graceful shutdown.

A failure occurred during the initialization

of the Service Virtual Interface
Failure during intialization of [chars]. Error: infrastructure. This resulted in the restart
[chars]
of the process.

Failed to send a '[chars]' message - Error:

[chars]

A control message could not be sent from

the MA to the EA. See error message for a
possible reason. An interface may now be
in the wrong up/down state.

The process was initialized successfully but

Failure communicating readiness to System was unable to inform System Manager of
Manager. Error: [chars]
the success.

The Service Infrastructure was unable to

reconnect to IM: [chars]

If the Service Infrastructure becomes out of

sync with IM, then it reconnects in order to
prompt a resync. If this message is
displayed then it has been able to
reconnect. This may cause configured
interfaces to no longer forward traffic, or
interfaces which have been shut down or
deleted to continue to do so.

The Service Infrastructure was unable to

synchronize interfaces

In order to correct any problems, the

Service Infrastructure will reconnect to IM
to prompt a resync. If this message is
displayed then this resync is failing. This
may cause configured interfaces to no
longer forward traffic, or interfaces which
have been shut down or deleted to
continue to do so.

Error setting up adjacencies for an

interface: [chars]

An error was encoutered while trying to set

up adjacencny information for a VASI
interface. The exact error is detailed in the
error message. Packets will not be
forwarded to the affected interface.

Failure during initialization. Error: [chars]

A failure occurred during the initialization

of the VASI EA process on a particular node.
The process will be restarted. Until the
process starts successfully, any VASI
interface pairs located on that node will not
come up. (If there is a standby node the
interfaces should come up on the standby).

Error while [chars]ing [unsigned int]

interfaces: [chars]

An error occurred while attempting to join

together the two halves of some VASI pairs
on the specified node. The pairs will not
come up. If there is a standby node
configured for the pairs, they may come up
on the standby.

Received request for an interface

(0x[pointer]) that is not in our database

The VASI EA process received a request to

process an interface that does not exist in
its database. This indicates some sort of
internal inconsistency.

Error while sending messages to Service

Director: [chars]

A problem was encountered while trying to

send a batch of messages to the Service
Director. The Service Director may not be
up to date with the state of services on this
node, so VASI interfaces located on this
node may fail to forward packets.

A problem was encountered while trying to

send a single message to the Service
Director. The Service Director may not be
up to date with the state of this services on
this node, so the associated VASI interfaces
Error while sending message about [chars] located on this node may fail to forward
to Service Director: [chars]
packets.

While the VASI EA process was checking

the state for the specified interface pair, an
error was encountered. The interface pair
An error occurred while checking the state in question may be left in an inconsistent
for '[chars]': [chars]
state.

Failed to initialise VASI interface owner

process. Stage: [chars], error: [chars]

The VASI Manager failed to startup

correctly. Though it will get automatically
restarted, the error is unlikely to be
recoverable.

The VASI Manager has failed to create an

interface. This can happen primarily due to
low memory condition in the system or in
Failed to create an interface. Error: [chars] some cases due to an internal error.

Failed to cleanup after interface creation

failed. Error: [chars]

The VASI Manager failed to completely

clean up interface state after an interface
creation failure. This would have left the
system in an inconsistent state. This will
mostly occur due to invalid arguments.

An error has occured during packet

handling in the VASI base capsulation, and
no error counters can be updated. If errors
are seen for an extended period then it can
be assumed that no packets can be
forwarded through VASI interfaces. This is
likely to be a symptom of a problem in the
Packets have been dropped in the VASI
Packet Forwarding Infrastructure - earlier
base capsulation, but no error counts could error messages might indicate the root
be updated ([chars]).
cause of the problem.

A failure occurred during the initialization

of debug for the NetIO caps. If this occured
during an upgrade operation then it will
cause the NetIO process to reload.
Otherwise this will cause the capsulation to
Failure of debug intialization during [chars]. be unloaded, and an error returned to the
Error: [chars]
user.

Failure initializing tracing ([chars] buffer).

Error: [chars]

A failure occurred during the initialization

of tracing for the NetIO caps. This will
cause the capsulation to be unloaded, and
an error returned to the user.

Insufficient Memory to perform [chars]

operation \n

The MIB had trouble allocating memory.

Mutex [chars] failed \n

The MIB had trouble locking/unlocking

mutex.

ATM MIB support initialization failed

([chars]%s)

First %s : Error Description Second %s :

Return code string An error occurred while
initializing ATM MIB support in snmpd
process. If this occurred during process
startup, then the process may be restarted.
The error could be a part of one/more of
the following: - database initialization ifmib notify registration - sysdb binding
process - registration for a trap initialization of a trap OID string

ATM SNMP: Message-> [chars]: Method->

[chars]: Index-> [dec]: Retcode-> [dec]
ATM SNMP: [chars]

A high severity error is encountered. The

error relates to an interaction with interface
manager.
debug msg

ATM SNMP: Message-> [chars]: Location-> This message indicates the ATM SNMP
[chars]: Retcode-> [dec]
library fails to perform a SYSDB operation.

Insufficient memory to perform [chars]

operation

No memory in the process.

Could not create a bulk file processing

thread

There are no resources available to create

a bulk file processing thread

Insufficient Memory to perform [chars]

operation \n

The MIB had trouble allocating memory.

Mutex [chars] failed \n

The MIB had trouble locking/unlocking

mutex.

[chars] to stats request. Those nodes will

not be polled for the next 30 seconds.

There was an issue in retrieving stats for

one of the interfaces. This could happen if
one of the participating processes (qos_ma,
qos_ma_ea, qos_ma_ea, ifmgr, etc) was
busy and could not process the stats
request. The interface in question will not
be polled for the next 30 seconds to allow
recovery from the problem state.

Failed to get memory for [chars]

Memory unavailable

Unable to allocate memory for process

name\n

The MIB had trouble allocating memory for

process name'

Clock operation Error: [chars]

The MIB had trouble in getting time

Spawn Error: [chars]

The MIB had trouble in spawning a process.

Sysdb related error: [chars]

The MIB had trouble reading from or writing

to or binding/unbinding SysDB.

[chars] : Failed to [chars] target config for

[chars] : [chars]

error occured during config manager

operation.

Timer Error: [chars]

Timer error has occured

Could not create event manager for [chars] Attempt to create an event manager fails
([chars])
for some reason.

Entry for id [dec] doesn't exist.

An attempt to remove an entry from a

queue was made, but the entry was not
found.

Insufficient memory to [chars]

No memory to perform edm or bag

operations.

Invalid codepath encountered - exitting.

An invalid codepath has been encountered

- the process is exitting and restarting.

The MIB was unable to marshall or

unmarshall a set of data, error: [chars]

This may be due to invalid data being sent

by the agent or request, or due to an error
in the data-marshalling infrastructure. The
current request cannot be completed.
Check the request and try again.

Failed to convert an SNMP supplied

OctetString to a string.

An illegal string was passed in to the MIB

by the agent. The current request cannot
be completed.

The SNMP management station tried a set

request without specifying a request index.
The SNMP request did not specify an index. Check the request and try again.

Internal error occurred: [chars]

The MIB has reached an expected state,

and will not be able to service the current
request.

Could not allocate memory

The MIB has failed to aquire the required

amount of memory.

The MIB was unable to access the system

database, error: [chars]

The MIB was unable to read to or write

from the system database, so will be
unable to provide some requested MIB
data.

The MIB was unable to connect to the

system database, error: [chars]

The MIB was unable to connect to the

system database, so will be unable to
provide the MIB data. This may be because
the communications infrastructure is not
yet up.

Failure during initialization. Error: [chars].

A failure occured during the initialization of

the process.

Insufficient memory to perform [chars]

operation

No memory in the process.

Could not create a FTP request processing

thread

There are no resources available to create

a FTP request processing thread

The HSRP MIB could not connect to the

HSRP process. ([chars])

The HSRP MIB was unable to create a

SysDB connection to the HSRP process for
the purpose of retrieving management
information.

Failed to register HSRP MIB debug control:

[chars]

During initialisation of the HSRP MIB, it was

not possible to register to be notified of
changes to the debugging state. The MIB
will continue to function, but it will not be
possible to turn on debugging for the MIB.

Failed to register for notification of state

changes. ([chars])

During initialisation of the HSRP MIB, it was

not possible to register to be notified of
changes in active state of an HSRP group.
The MIB will continue to function, but no
traps will be generated for the
cHsrpStateChange notification.

Failed to construct OID in trap generation.

([dec])

An OID (object identifier) string failed to be

constructed during trap generation. The
trap for a cHsrpStateChange notification
did not get sent.

IF-MIB duplicate interface index detected

during [chars] operation.

An attempt to allocate an interface index

has failed because it had been previously
allocated.

IF-MIB unable to restore all interface

indices from interface index persistence
file.

An attempt to restore all interface indices

from the interface index persistence file
has failed.

Error Opening persistence file for write

'[chars]'

An attempt to open interface index

persistence file has failed while trying to
wrile interface index changes into file.

ifindex_server initialize falied : [chars]

An unexpected internal error occurred in

the ifindex subsystem.

'[chars]' error during intialization of LW

tracing for ifindex provider

An error occured while initializing LW

tracing for ifindex provider library.

Received an invalid message, field '[chars]' The message received requesting an

is incorrect
operation is malformed.
Failed to [chars] ifIndex=[dec] to/from
ifSpecific tableId=[dec]; due to [chars]

The operation requested could not be

performed due to an internal error.

SNMP MIB interface specific (e.g. SONET,

Ethernet) table operation error
(operation=[chars], table id=[dec],
reason=[chars])

'A software problem has been detected

that prevents SNMP from ' 'completing the
requested interface specific table
operation. ' 'Operation of the interface
specific MIB (e.g. SONET, Ethernet) is '
'impacted.'

Failed to [chars] debugging of IF-MIB IfSpec The operation requested could not be
Client DLL, due to [chars]
performed due to an internal error.
Failed to [chars] debugging of IF-MIB IfSpec The operation requested could not be
Server DLL, due to [chars]
performed due to an internal error.

IFMIB DLL error:[chars]

Failed to do DLL operation

Due to lack of memory falied to allocate

memory for [chars]

This error message indicates unable to

create ifstackEntry or not able to allocate
memory for duplicate interface name. due
to a low memory condition.

Failed to compile regexp:[chars] , Error :

[chars]

Failed to compile given regular expression

for linkUp/Down notif status.

Failed sysdb operation: [chars], err: [chars] Ifmib has failed during sysdb operation.

verification for 'snmp interface subset'

command failed because of some invalid
input. Ifmib database is not updated
because of this config but in sysdb, config
might have happened. For recovering from
Configuration got applied with Err:[chars]. this 'no snmp interface subset <subsetRemove this configuration from the system no>' is required.

'An operation on a bag failed: [chars]'

A problem occurred while encoding or

decoding information from a bag.

'Operation [chars] failed, error [chars]'

The MIB had trouble reading from or writing

to or binding/unbinding SysDB.

snmpd is being shut down due to lack of

memory required for initialization. Try
restarting snmpd after freeing some
memory

Not enough memory was available for

snmpd to set up its internal data
structures.

Initialization Failure: [chars]: [chars]

The MAC accounting MIB was unable to

initialize successfully. It is likely that an
SNMP query that was in progress will not
have been completed.

Attempted to perform the indicated

Attempt to [chars] unknown transport type: operation on an unknown transport type.
[dec]
This is an internal software error.

MIB Library not properly initialized

The MIB library was not properly initialized

by the SNMP agent. This is an internal
software error.

Failed to [chars], due to lack of memory

The requested operation could not be

performed due to a low memory condition.

event block call failed: [chars]

A software error occured when the ping

mib process try to Event block call

Insufficient memory to perform [chars]

operation

A software error occured when the ping

mib process try to request more memory.
The requested operation by pingmib could
not be accomplished because of a low
memory condition.

A software error occured when the ping

Could not create a PING request processing mib process try to create a PING request
thread
processing thread

debug register call failed: [chars]

A software error occured when the ping

process try to register for debug
initialization. call failed.The process will
attempt to recover from this situation by
exit. If this message is not seen again and
no other adverse effects are observed then
there is no need to take any action.
Retrying ping mib with time gap migh help.

Insufficient Memory to perform [chars]

operation \n

The MIB had trouble allocating memory.

Entry for [chars] not found in [chars] or

insufficient memory \n

The particular entry was not found in the

list or MIB had trouble allocating memory.

Internal verification for RFMIB registration

failed [chars]

While registering a verifier for sysdb MIB

configurations of the RFMIB, failure
occured. If not corrected, RFMIB might
provide partial data upon query.

Failed to register EDM - [chars]

Failed to initialize EDM.

[chars]: [chars]

Generic error message used for internal

debugging.

Failed to alloc memory : [chars]

iedgemon failed to allocate the required

amount of memory.

error encountered in [chars]: and err

message is [chars]

iedgemon encountered error and cerr code

is returned

[chars]: [chars]

Error encountered in debug module.

[chars]: and err message is [chars]

iedgemon encountered error and cerr code

is returned

showcmd - [chars]

'The failure pertains to show commands in

snmp.' 'This does not indicate feature
failures or issues'

showcmd - [chars] [chars]

'The failure pertains to show commands in

snmp, when sending reciving the data'
'This does not indicate feature failures or
issues'

showcmd - Wrong data length, [dec] >

[dec]

'The failure pertains to show commands in

snmp to validating the data length ' 'This
does not indicate feature failures or issues'

showcmd - Wrong msg [dec] received

'The failure pertains to show commands in

snmp to validating the data ' 'This does not
indicate feature failures or issues'

showcmd svr failied. Err:[chars]

'This is for debug message for show

command in snmp to print the buffer '

[chars] Err: [chars]

This is an internal software error in snlib

test.

SNMP ipc init failed : [chars] :[chars]

SNMP library incurred an internal software

error. This error indicates falied to create
thread-specific or debug/ltrace initlization
failed.

Failed to allocate memory for [chars]

SNMP library failed to allocate memory for

an object due to low memory conditions in
the System.

[chars] 0x[dec]

This is an internal software error in snmp

test.

Failed to snmp configuration [chars]

[chars]: [chars]

Failed to perform the indicated

configuration operation. This could be due
to a low memory condition, an unsane
configuration, or an internal software error.
Failed in Host config: Received a good tuple
for the snmp-server host CLI command, but
could not configure it. This is likely due to
lack of memory, which may be a transient
condition, or may be due to SNMP
supporting too many MIBS with large
amounts of data. Try this command again
after a few minutes. If it continues to fail,
you may wish to undo some SNMP
configurations and then retry the
command.

Data size exceeded for [chars]. Length of

data is %zd(max length is %zd)

The maximum size of the data has been

exceeded. This could be due to user
configuration or internal error.

Failed to load MIB dll : [chars]: [chars]

Failed to load the given MIB, for the given

reason. This could be due to a low memory
condition.

Failed to map MIB dll: [chars] to an

address: [chars]

An attempt to map a MIB DLL symbolic

name to an address failed. This MIB will be
unloaded. This could be due to a corrupted
MIB configuration file, a corrupted DLL, or a
MIB configuration file that is out-of-sync
with its corresponding MIB DLL.

Received error from event_wait: [chars]

SNMP receives messages from an event

manager. While trying to retrieve a
message, an error occured, preventing
successful receipt of the message.

Failed to initialize the snmpd process,

unable to [chars], Error : [chars]

This is internal error while intialising the

datastructure during snmpd process
intialization.

Snmp Trap source issue : [chars]:[chars]

General internal failure. This is likely an

internal software error.

This is an internal software error. TupleType: The retrieved datatype for the given
SysDB tuple does not match the expected
datatype. Bad-host: Received a tuple for
the snmp-server host CLI command, but
could not parse it. Unpack: Failed to
Sysdb tuple Error : [chars] [chars] [chars] : decode/unpack the retrieved SysDB tuple
[chars]
value.

Failed to allocate memory for [chars]

Due to a low memory condition we not able

to process any request or response PDU or
we could not allocate memory for context
name and not able create view .

Error in getting MIB config data. [chars],

[chars]

Error in opening cfg directory : The MIB

configuration files should be located in the
directory '/ios/mib'. This directory could not
be read, for some reason. General Error: A
syntax error was encountered while parsing
the given MIB configuration file. The MIB
referred to by this configuration file will not
be loaded. Failed to read MIB Cfg file: This
could be due to a low memory condition.
Missing config entries: One or more
required entries are missing from the given
MIB configuration file. The MIB referred to
by this configuration file will not be loaded.

Failed to add sysObjectID to notification

view for trapstring: [chars]

Every trapstring supported by the 'snmp

host' command corresponds to one or more
notification OIDs. Each of these
notifications will have zero or more
varbinds that are carried as payload - each
MIB tells snmpd about these varbinds so
that a 'notification view' can be built for
them. An extra varbind - sysObjectID - is
required to be sent with all v2c
notifications. This message indicates that
an attempt to register this varbind failed.
Sending v2c notifications for the trapstring
specified in the error message may fail. You
can workaround this by not specifying any
trapstring in the 'snmp host' configuration this will enable all notifications for that
destination.

One of the mibd process has failed to

register its oid's with snmpd. Either due to
failure in mibd init or issue in
communication channel between snmpd
snmp agent is missing part of oid list in the and mibd. This would result in failure of
tree
snmpd get or next request on those oids.

Failed initialize Sub-Agent:[chars]

Error indicating that one of the SNMP SubAgent could get initialized.

Failed to bind to SysDB for MIB

notifications: [chars]

SNMP binds to SysDB to receive

notifications on the MIB's behalf. MIBs
typically use these notifications as triggers
to send out SNMP notifications (e.g. Traps).
If SNMP cannot bind to SysDB, these SysDB
notifications will not be received, and thus
some SNMP notifications may never be
generated.

Failed to list of SNMP view tuples : Error :

[chars]

An attempt to read from SysDB failed, the

result being that whatever action was
being performed cannot be completed by
the SNMP agent.

Cannot find notification target [chars]

A configuration command refers to an

SNMP target that has not yet been
configured.

Failed to initialize snmp request queue :

[chars]: error: [chars]

Failed to communicate with the SNMP

transport process. This could be due to a
low memory condition or failed to initialize
incommingQ or overload control, or the fact
that there is no SNMP transport process
(udp) running.

Failed to send trap to [chars]

A trap destined for the given address could

not be sent. This could be due to a low
memory condition. It also might be due to
the fact that there is no SNMP transport
process(udp process) running for that
transport protocol.

Failed to retrieve tuple [chars]%s: [chars]

Failed to retrieve the given SysDB tuple for

the given reason. This may or may not
have a detrimental effect on the behavior
of the SNMP agent (depends on which tuple
it is).

The command \[chars]\ could not be

applied at this time because the oid \
[chars]\ may be invalid or duplicate

The snmpd process attempted to load the

bulkstat OID, but the OID did not
correspond to any known MIB module.

Duplicate debug registration for the MIB

[chars]

The given MIB attempted to register for

MIB debug handling more than once. This
is an internal software error. It may not
have a detrimental effect on the behavior
of the SNMP agent.

Failed debug registration for the MIB

[chars]

Failed to initialize support for the command

'debug snmp mib xxx', where 'xxx' is the
MIB indicated in the error message. This
could be due to a low memory condition or
an internal software error. The result is that
this command cannot be used.

Maximum incoming trap queue size

reached, emitting the oldest trap from
correlation incoming queue

SNMP trap correlation incoming queue is

full; traps already in the queue is emitted
on a FIFO basis to free up room for more
incoming traps

Internal trap Queue [chars]

SNMP agent recieves trap requests from all

the sub agents on a internal queue, then
the traps are classified based on several
factors and passed on to different set of
queues.

mib related config may not take effect, if

it's not taken effect need to re-apply it

While snmp startup sub-agents need to

come up within 30 sec, if it happens in both
active & standby nodes no issues will
come, but if subagents not came up on
active node and came up in standby node,
mib related config verification will not
validate by snmpd & active mibd so there
was a chance to miss the mibd related
config.

An error was encountered during

installation of a new MIB or deletion of an
old MIB. These messages are printed when
Failed to cleanup debuggging entry for MIB MIB installation/deletion failed.

The given MIB attempted to register more

[chars] MIB attempt to register for [chars] than once for the given MIB notifications.
notifications again: existing handlers: [hex] This should have no detrimental effect on
[hex]
the behavior of the system.

Failed to send PDU response to [chars]

A response destined for the given address

could not be sent. This could be due to a
low memory condition. It also might be due
to the fact that there is no SNMP transport
process(udp) running for that transport
protocol .

Notification target [chars] is in use

An attempt was made to unconfigure an

SNMP target, however that target is still in
use by one or more other SNMP
configuration commands.

snmpd timer warning :[chars]: [chars]

This is internal error. This error will

indicates can be Failed create snmpd mgd
timer or it can be Failed to register or
restart the SNMP QMON timer & DLL timer.

Found empty trap, destined for [chars]

A trap destined for the given address was

empty. This is an internal software error.

User \'[chars]\' will be available only on

crypto pie installation

SNMP user configured with aes and 3des

encryption will be available for snmp
operations only if crypto pie is installed on
the router. Though the user config will be
available in the router, user will not be
operational.

Could not create view: [chars]

Could not create an SNMP view using the

'snmp-server view' CLI command. Possible
causes could be poorly formatted
viewnames or oid subtrees.

The command \[chars]\ could not be

applied at this time because the oid \
[chars]\ does not belong to a known MIB
module.

The snmpd process attempted to load the

view OID, but the OID did not correspond to
any known MIB module.

Failed to register bags with SysDB for

providing SNMP statistics and MIB
information: [chars]

Failed to register the bags with SysDB. The

access to SNMP statistics and MIB items
in /oper/snmp/info through 'sysdbcon'
might not be available. This is likely due to
an internal software error.

Due to a low memory condition we could

not enable (or disable) the specified traps
or we could not register to receive the
specified MIB notifications. Until available
memory is increased and the SNMP process
is restarted, these notifications will not be
Insufficient memory to [chars] from :[chars] generated by the agent.

Failed to encode a bag due to [chars]

Failed to encode a bag. The access to SNMP

statistics and MIB information through
'show snmp' CLI command might not be
available. This is likely due to an internal
software error.

Failed to register as EDM for providing

SNMP statistics and MIB information:
[chars]

Failed to register as EDM. The access to

SNMP statistics and MIB information
through 'show snmp' CLI command will not
be available. This is likely due to an
internal software error.

Failed to register for notifications on tuple

name: [chars] : [chars]

Failed to register for receipt of the given

notifications. This could be due to a low
memory condition or an internal software
error.

Persistence file [chars] will be created on

initialization, reset snmpEngineBoots to 1

SNMP agent reads default engineID and

engineboots from a persistence file on
startup. File is missing, and will be created,
reset engineboots to 1

An operation on a bag failed: [chars]

A problem occurred while encoding or

decoding information from a bag.

An operation on a bag failed: [chars]

A problem occurred while encoding or

decoding information from a bag.

Failed to [chars], due to lack of memory

The requested operation could not be

performed due to a low memory condition.

Failed to [chars], due to lack of memory

The requested operation could not be

performed due to a low memory condition.

Sysdb related error: [chars]

The MIB had trouble reading from or writing

to or binding/unbinding SysDB.

Sysdb related error: [chars]

The MIB had trouble reading from or writing

to or binding/unbinding SysDB.

pthread_create([chars]) failed

Sonet MIB API had trouble in creating

thread.

An operation on a bag failed: [chars]

A problem occurred while encoding or

decoding information from a bag.

Event manager create failed : [chars]

An internal operation failed. The system

will attempt to recover.

Failed [chars], due to lack of memory

The requested operation could not be

performed due to a low memory condition.

Sysdb related error: [chars]

SonetMIB API had trouble

registering/deregistering EDM or
binding/unbinding SysDB.

pthread_create([chars]) failed

Sonet MIB API had trouble in creating

thread.

An operation on a bag failed: [chars]

A problem occurred while encoding or

decoding information from a bag.

Event manager create failed : [chars]

An internal operation failed. The system

will attempt to recover.

Failed [chars], due to lack of memory

The requested operation could not be

performed due to a low memory condition.

Sysdb related error: [chars]

SonetMIB API had trouble

registering/deregistering EDM or
binding/unbinding SysDB.

[chars]

A Debug message

[chars] : [chars]

A Debug message

[chars] : [chars]

An internal operation failed. The system

will attempt to recover.

Send SNMP [chars] trap notification to

[chars] : [hex]

A Debug message

Insufficient memory to perform [chars]

operation

No memory on the system to perform this

opertion.

Failed to parse [chars]

This is given out if there are problems

parsing the encoded tuple from
syslogd/sysdb.

Failed to [chars]. Error: [chars]:

The syslog mib reads the sysdb tuples and

gets information about the syslog mib
objects. If due to some reason the sysdb
error occurs this message is printed out.

[chars] : Failed to [chars] target config for

[chars] : [chars]

An internal software error occurred.

Failed to initialize UDP process : [chars],

Error: [chars]

This is indicates the udp process

Initialization failed . This could be due to a
low memory condition or an internal
software error.

Failed to allocate memory for [chars]

The requested operation could not be

performed due to a low memory condition.

Failed to retrive trap statitics :[chars] due

to sysdb error:[chars]

udp reads the snmp trap Q length and trap

timeout from the sysdb. If udp is not able
to read it then this error is printed. Or is
printed when sysdb configuration for trap
host does not have valid format. This is an
internal error.

udp_snmpd binds to SysDB to receive

notifications on the trap destinations
udp_snmpd typically use these notifications
to add trap destination to the trap Q. If
udp_snmpd cannot bind to SysDB, these
SysDB notifications will not be received,
and thus some trap desination will not be
added and traps will not be sent to those
Failed to bind to SysDB for [chars]: [chars] destinations.

Failed to register for snmp notifications :

[chars] [chars]: [chars]

Failed to register for receipt of the given

notifications or receipt of the verification
event. This could be due to a low memory
condition or an internal software error.

Failed to [chars]

Failed to execute a system call. This could

be due to low memory condition or an
internal software error.

LWM Message transport Error : [chars]

[chars]: [chars]

SNMP-UDP process received a bad Message

or failed to send a message to Agent. This
may be due to a invalid message number
or an internal software error.

Failed to find VRF details for [dec]/[chars]

Failed to find VRF related information that

is required to send an SNMP PDU. This
could be due to an internal software error.

Failed to inform SysMgr on SNMP-UDP

initialization, [chars]\n

Failed to inform SysMgr on end of

initialization of UDP transport module for
SNMP. This could be due to a block in
snmpd initialization. If snmpd process does
not come to normal execution even after
some time need to take the recommended
action.

Failed to initialize Functionality for SNMP :

[chars]: [chars]

Failed to initialize a functionality for snmp like debugging, setup event manager for
notification timer. Or failed to send PDU
since the outgoing PDU is greater than the
configured maximum PDU size, the PDU
will be dropped. This could be due to an
internal software error.

SNMP Utilities Library not properly

initialized

The SNMP Utilities library was not properly

initialized by the SNMP agent. This is an
internal software error.

Bag encode/decode Error : [chars]

The VLAN Interface table relationship MIB

encountered an error while encoding /
decoding some data. It is likely that an
SNMP query that was in progress will not
have been completed.

Failed to [chars]

The VLAN Interface table relationship MIB

encountered an internal error during
initialisation. It is likely that an SNMP query
that was in progress will not have been
completed.

Failed to [chars]

The VLAN Interface table relationship MIB

was unable to allocate sufficient memory to
complete an operation. It is likely that an
SNMP query that was in progress will not
have been completed.

Failed to [chars]

The VLAN Interface table relationship MIB

encountered an internal error. It is likely
that an SNMP query that was in progress
will not have been completed.

SysDB failed to [chars]

The VLAN Interface table relationship MIB

encountered an error while connecting to,
or accessing data within the System
Database. It is likely that an SNMP query
that was in progress will not have been
completed.

Failed to initialize [chars], because of

[chars]

Initialization process such as getting an

evm failed. The acct_ea process cannot
proceed without this module initialization,
and will exit.

A policy-map containing prepaid and/or idle

timeout commands must also contain a
Policy-map [chars] must have \'accounting AAA accounting command. Without
aaa list\' configured with idle timeout or
accounting configured, prepaid quota
prepaid commands.
cannot be accounted for.

Policy-map [chars] has an unsupported

An accounting policy-map must contain a
class-map. Accounting policy-map support class-map of type IPv4 ACL. This is the only
is limited to class-maps of type IPv4 ACL.
supported match type.

The prepaid configuration name that was

specified in the prepaid command has not
Prepaid configuration [chars] is not defined. been defined in the system.

Failed to initialize [chars], because of

[chars]

Initialization of an internal module, such as

debug, failed. This message is normally
seen when the acct_ma process is starting.
The acct_ma process cannot proceed
without this module initialization, and will
exit.

Merged and non-merged service-policies

cannot be mixed in the same session.

The merge keyword must be configured to

combine same-direction service-polices
from different dynamic-templates for a
session. This helps avoid any
inconsistencies in seriver-policy.

Policy-map [chars] is not defined.

The policy-map name that was configured

in the service type dynamic-template has
not been defined in the system.

Prepaid session request error: [chars]

There is an internal failure when starting a

new prepaid session or requesting a new
quota. This can be seen when acct_ma
sends a request to subscriber manager
(iedged) process to initiate a prepaid event
to AAA.

Subscriber Database Manager was unable

to initialize the [chars] module. Error:
'[chars]'. Initialization will be tried again
after 60 seconds.

An error was encountered while initializing

one of the critical modules of the
configuration manager server. Without
proper initialization of this module,
configuration manager can not operate
properly. Initialization will be retried every
60 seconds if required.

An error was previously encountered while

initializing one of the critical modules of
the configuration manager server.
Subscriber Database Manager succeeded However, the initialization was retried and
in initializing the [chars] module upon retry. succeeded.

Subscriber Database Manager was unable

to initialize the [chars] module. Error:
'[chars]'. [chars].

An error was encountered while initializing

one of the modules of configuration
manager server. The failure of this module
initialization is not critical to configuration
manager to be completely operational.

[chars] Error:[chars]

This is a non-fatal error and can happen

when router is low on memory. It should
not affect the functioning of the router, but
trace messages may not be logged.

[chars]

An unexpected internal error occurred in

the configuration subsystem.

Error encountered in the event loop:

[chars].

An error occured in the event loop. The

process will restart which should recover
the situation.

Failed to initialize [chars], because of

[chars]

An error occurred during the initialization of

IPSUB EA process. The process will restart
which should recover the situation.

Process initialization failed with error \

[chars]\: [chars].

An error occurred during the initialization of

IPSUB MA process. The process will restart
which should recover the situation.

No more sessions can be initiated. The

number of configured sessions ([dec])
reached

This syslog is printed when the number of

sessions have reached the configured
session limit. New sessions will not be
allowed.

Reached the number of sessions ([dec])

allowed

This syslog is printed when the number of

sessions is over the limit of the licenses
available.

No more sessions can be initiated. The

number of entitled sessions ([dec]) has
been reached

This syslog is printed when the number of

sessions has reached the limit of the
licenses available. New sessions will not be
allowed

Session threshold of [dec] has been

exceeded

This syslog is printed when the configured

session threshold has been exceeded.

Error resetting IMP connection: [chars]

After detecting an error with the IMP

connection, PPPoE EA failed to reset that
connection. This is an internal error. It
requires a restart of the process for
recovery.

Error encountered in the event loop:

[chars]. The PPPoE EA process will restart

An error occured in the event loop. The

process will restart which should recover
the situation.

Failure during initialization of the [chars].

Error [chars]. The PPPoE EA process will
restart

A failure occured during the initialization of

the process. The process will restart which
should recover the situation.

Failed to allocate [unsigned int] bytes for

'[chars]'

The process failed to allocate memory for

the specified resource.

Unexpected error whilst [chars]: [chars]

PPPoE EA encountered an error

communicating with Rewrite Manager. The
error message describes what operation
has failed and why it failed. The most likely
reason for this is a temporary connection
problem with the Rewrite Manager Server
process, but the error could also be caused
by low memory resource or programming
error.

A batch from IMProxy contained multiple

notifications for a single interface. This
<<CH[hex]>>: Multiple [chars]
should not occur but the situation has been
notifications received in a single batch from recovered successfully by the PPPoE EA. No
improxy
problems should be seen as a result.

Failed to initialize the PPPoE GBL debug

and trace: [chars]

PPPoE MA encountered an error initializing

its Debug and Trace The error message
describes what operation has failed and
why it failed. This is a fatal error and the
PPPoE GBL process cannot continue. It will
abort and subsequently be restarted by
SysMgr in an attempt to recover.

Error creating the PPPoE GBL Event

Manager: [chars]

PPPoE GBL failed to create its Event

Manager which is a critical resource for the
operation of the process. This error may be
caused by low memory resources. The
process will abort and be restarted in an
attempt to recover.

Unexpected error encountered whilst

[chars]: [chars]

PPPoE MA encountered an error using AAA

attribute APIs. The error message describes
what operation has failed and why it failed.
The most likely reason for this a low
memory condition but the error could also
be caused by a programming error.

Unexpected [chars] received while AAA

connection down

PPPoE MA received a notification from AAA

while the connection was down. The most
likely reason for this a programming error.

Unexpected error encountered whilst

[chars]: [chars]

PPPoE MA encountered an error using AAA

session APIs. The error message describes
what operation has failed and why it failed.
The most likely reason for this a low
memory condition but the error could also
be caused by a programming error.

Disconnecting subscriber session with

sub_label [hex] failed. The session should
be cleared manually using the 'clear
subscriber' command: [chars]

PPPoE MA failed to call AAA to disconnect a

session. The session may now need to be
cleared manually using the 'clear
subscriber' CLI command. The most likely
reason for this a low memory condition but
the error could also be caused by a
programming error.

Unexpected config-value received for the

'[chars]' BBA-Group config item

PPPoE MA received an unexpected configvalue for a piece of BBA-group config

through SysDB. The error message
describes which config item was invalid.
The most likely reason for this a
programming error in the verifier for the
config item.

Error initializing '[chars]': [chars]

PPPoE MA encountered an error initializing

its Debug and Trace The error message
describes what operation has failed and
why it failed. This is a fatal error and the
PPPoE MA process cannot continue. It will
abort and subsequently be restarted by
SysMgr in an attempt to recover.

Unexpected error encountered whilst

[chars]: [chars]

PPPoE MA encountered an error using the

CDM Service. The error message describes
what operation has failed and why it failed.
The most likely reason for this a low
memory condition but the error could also
be caused by a programming error.

Unexpected error encountered whilst

[chars]: [chars]

PPPoE MA encountered an error using the

Checkpoint Service. The error message
describes what operation has failed and
why it failed. The most likely reason for this
a low memory condition but the error could
also be caused by a programming error.

Corrupt [chars] checkpoint record found:

[chars]

Whilst restoring one of its checkpoint

tables PPPoE MA found a corrupt
checkpoint entry. The entry will be ignored
and so the relevant PPPoE session will be
lost.

Duplicate [chars] checkpoint record found

for <<CH[hex]>>

Whilst restoring one of its checkpoint

tables PPPoE MA found multiple entries for
the same interface. PPPoE MA will use the
first checkpoint entry it finds for each
interface and ignore any subsequent
duplicates. This is caused by a
programming error.

Unexpected error encountered whilst

[chars]: [chars]

PPPoE MA encountered an error using the

debug service. The error message
describes what operation has failed and
why it failed. The error could be caused by
low memory resource or programming
error.

Error closing '[chars]' connection: [chars]

PPPoE MA failed to close a connection to an

essential service. This is an internal error
and it requires a restart of the process for
recovery.

Error creating '[chars]' connection: [chars]

PPPoE MA failed to create a connection to

an essential service during initialization.
This is an internal error. It requires a restart
of the process for recovery.

After detecting an error with the connection

to the specified service, PPPoE MA failed to
reset that connection. This is an internal
error. It requires a restart of the process for
Error resetting '[chars]' connection: [chars] recovery.

PPPoE MA failed to retrieve the file

Error retrieving the Connection ID from the descriptor associated with the specified
'[chars]' connection: [chars]
service. This is an internal error.

Error registering for critical events on

'[chars]' connection: [chars]

During initialization, PPPoE MA failed to

register for essential notifications regarding
the state of the connection for the
specified service. This is an internal error. It
requires a restart of the process for
recovery.

Error opening '[chars]' connection: [chars]

PPPoE MA failed to open a connection to an

essential service during initialization. This
is an internal error. It requires a restart of
the process for recovery.

Failed to register a handler for '[chars]'

messages: [chars]

PPPoE MA failed to register a handler for

the specified class of event. This is an
initialization error and implies that PPPoE
MA will not be able to operate correctly.
The PPPoE MA process will abort and be
restarted in an attempt to recover. The
cause may be a resource starvation
problem but is most likely to be an internal
programming error. The error message
should give more details.

Error creating the PPPoE MA Event

Manager: [chars]

PPPoE MA failed to create its Event

Manager which is a critical resource for the
operation of the process. This error may be
caused by low memory resources. The
process will abort and be restarted in an
attempt to recover.

Error encountered in the event loop:

[chars]. The PPPoE MA process will restart

An error occured in the event loop. The

process will restart which should recover
the situation.

Failed to send '[chars]': [chars]

PPPoE MA failed to send the specified

message. The cause may be a resource
starvation problem but is most likely to be
an internal programming error. The error
message should give more details.

Error creating event queue for '[chars]':

[chars]

This is an unexpected error. The PPPoE MA

process will attempt to recover by
restarting. The cause may be a resource
starvation problem. The error message
should provide more details.

This is an unexpected error. The PPPoE MA

process will attempt to recover by
restarting. The cause may be a resource
starvation problem. The error message
Error dequeuing event for '[chars]': [chars] should provide more details.

Error queuing event for '[chars]': [chars]

This is an unexpected error. The PPPoE MA

process will attempt to recover by
restarting. The cause may be a resource
starvation problem. The error message
should provide more details.

Unexpected IfMgr error encountered

[chars]: [chars]

PPPoE MA encountered an error

communicating with Interface Manager.
The error message describes what
operation has failed and why it failed. The
most likely reason for this is a temporary
connection problem with the Interface
Manager Control Server, but the error could
also be caused by low memory resource or
programming error.

Interface <<CH[hex]>> already in global

session tree

PPPoE MA tried to insert an interface into

the global session tree which was already
there. The error is probably caused by a
programming error.

Invalid [chars] callback: [chars]

PPPoE MA received an invalid callback from

another process. The error message
describes why it is invalid. This is most
likely to be a programming error, either in
PPPoE or in one of the processes it interacts
with.

Unexpected MTU set for <<CH[hex]>>:

[unsigned int] bytes. Expected [unsigned
int] bytes.

An access-interface has been configured

with an MTU that is incompatible with a
PPPoE sub-interface. The <CmdBold>PPPMax-Payload<noCmdBold> tag provided by
connecting peers is used to places a lower
bound on the MTU that can be configured
on an access-interface.

Failed to allocate [unsigned long int] bytes The process failed to allocate memory for
for '[chars]'
the specified resource.

Unexpected error encountered whilst

[chars]: [chars]

PPPoE MA encountered an unexpected

error using the Managed Timer library. This
is most likely to be due to a low memory
condition but may also be an internal
programming error. The error message
should provide more information about the
cause.

Packet with invalid session ID ([dec])

received on access interface
<<CH[hex]>>.

A packet with an invalid session ID has

been received. This indicates that a
subscriber has started communicating with
this AC after initiating this session with
another AC.

Unexpected platform error encountered

when calling [chars]: [chars]

PPPoE MA encountered an error using a

platform API to parse the interface name.
The error message describes what
operation has failed and why it failed. The
error is most likely caused by a
programming error.

New session limit applied for circuit ID

[chars] and remote ID [chars], via
<<CH[hex]>>. Overridden limit was
[unsigned int], now [unsigned int].

The RADIUS override port limit

configuration had already been applied
once, and now a different limit has been
configured. This is unexpected behaviour,
and indicates that there has been some
sort of misconfiguration via RADIUS.

RADIUS override Port limit has been

[chars], resulting in [unsigned int] sessions
with circuit ID [chars] and remote ID
[chars] being disconnected.

The number of PPPoE sessions on a

particular Circuit ID and Remote ID has
reached the maximum which has been
supplied via RADIUS.

Failed to compile regular expression

'[chars]' for [chars]

The process failed to compile the given

regular expression.

Unexpected error encountered whilst

[chars]: [chars]

PPPoE MA encountered an error using

SubDB The error message describes what
operation has failed and why it failed. The
most likely reason for this a low memory
condition but the error could also be
caused by a programming error.

Unexpected error encountered whilst

[chars]: [chars]

PPPoE MA encountered an error using

SysDB APIs. The error message describes
what operation has failed and why it failed.
The most likely reason for this a low
memory condition but the error could also
be caused by a programming error.

Unexpected Sysmgr error encountered

calling [chars]: [chars]

PPPoE MA encountered an error

communicating with Sysmgr. The error
message describes what operation has
failed and why it failed. The most likely
reason for this is a temporary initialization
problem, but the error could also be caused
by programming error.

An event was hit that should only occur

during testing: [chars]

PPPoE MA hit some code that it shouldn't

be possible to hit except during testing.
This must be related to a programming
error.

Unexpected error encountered whilst

[chars]: [chars]

PPPoE MA encountered an unexpected

error using the Timer Wheel library. This is
most likely to be due to a low memory
condition but may also be an internal
programming error. The error message
should provide more information about the
cause.

Failed to unpack tuple for '[chars]'

The process failed to unpack a tuple.

PPPoE MA received an asynchronous

callback from another process when the
session was in an incorrect state. The error
message describes which callback was
received. This is most likely to be a
Unexpected [chars] callback, when session programming error, either in PPPoE or in
in [chars] state
one of the processes it interacts with.

Unexpected [chars], when session in

[chars] state

PPPoE MA is trying to cleanup a session

when it is in an unexpected state. The error
message describes which state it was in,
and what was triggering the cleanup. This
is most likely to be a programming error,
either in PPPoE or in one of the processes it
interacts with.

Access interface <<CH[hex]>> session

limit maximum ([unsigned int] sessions)
reached. Further connection attempts will
be rejected.

The number of PPPoE sessions on the

access interface has reached the
configured maximum.

Access interface <<CH[hex]>> session

limit threshold ([unsigned int] sessions)
reached. Maximum: [unsigned int]
sessions.

The number of PPPoE sessions on the

access interface has exceeded the
configured threshold.

Card session limit maximum ([unsigned int]

sessions) reached. Further connection
The number of PPPoE sessions on the card
attempts will be rejected.
has reached the configured maximum.

Card session limit threshold ([unsigned int]

sessions) reached. Maximum: [unsigned
The number of PPPoE sessions on the card
int] sessions.
has exceeded the configured threshold.
Circuit ID [chars] and Remote ID [chars]
[chars]session limit ([unsigned int]
sessions) threshold maximum reached.
Further connection attempts will be
rejected.

The number of PPPoE sessions on a

particular Circuit ID and Remote ID has
reached the maximum.

Circuit ID [chars] and Remote ID [chars]

session limit ([unsigned int] sessions)
threshold reached. Maximum: [unsigned
int] sessions.

The number of PPPoE sessions on a

particular Circuit ID and Remote ID has
exceeded the configured threshold.

Circuit ID [chars] session limit ([unsigned

int] sessions) threshold maximum reached. The number of PPPoE sessions on a
Further connection attempts will be
particular Circuit ID has reached the
rejected.
configured maximum.

Circuit ID [chars] session limit ([unsigned

The number of PPPoE sessions on a
int] sessions) threshold reached. Maximum: particular Circuit ID has exceeded the
[unsigned int] sessions.
configured threshold.
Inner vlan ([unsigned int]) on access
interface <<CH[hex]>> session limit
([unsigned int] sessions) threshold
reached. Further connection attempts will
be rejected.

The number of PPPoE sessions for a

particular Inner VLAN on the given access
interface has reached the configured
maximum.

Inner vlan ([unsigned int]) on access

interface <<CH[hex]>> session limit
([unsigned int] sessions) threshold
reached. Maximum: [unsigned int]
sessions.

The number of PPPoE sessions for a

particular Inner VLAN on the given access
interface has exceeded the configured
threshold.

MAC address [chars] on access interface

<<CH[hex]>> session limit maximum
([unsigned int] sessions) reached. Further
connection attempts will be rejected.

The number of PPPoE sessions from a

particular MAC address on the given access
interface has reached the configured
maximum.

MAC address [chars] on access interface

<<CH[hex]>> session limit threshold
([unsigned int] sessions) reached.
Maximum: [unsigned int] sessions.

The number of PPPoE sessions from a

particular MAC address on the given access
interface has exceeded the configured
threshold.

MAC-IWF address [chars] on access

interface <<CH[hex]>> session limit
maximum ([unsigned int] sessions)
reached. Further connection attempts will
be rejected.

The number of IWF PPPoE sessions from a

particular MAC address on the given access
interface has reached the configured
maximum.

MAC-IWF address [chars] on access

interface <<CH[hex]>> session limit
threshold ([unsigned int] sessions)
reached. Maximum: [unsigned int]
sessions.

The number of IWF PPPoE sessions from a

particular MAC address on the given access
interface has exceeded the configured
threshold.

MAC-IWF address [chars] session limit

maximum ([unsigned int] sessions)
reached. Further connection attempts will
be rejected.

The number of IWF PPPoE sessions from a

particular MAC address has reached the
configured maximum.

MAC-IWF address [chars] session limit

threshold ([unsigned int] sessions)
reached. Maximum: [unsigned int]
sessions.

The number of IWF PPPoE sessions from a

particular MAC address has exceeded the
configured threshold.

MAC address [chars] session limit

maximum ([unsigned int] sessions)
reached. Further connection attempts will
be rejected.

The number of PPPoE sessions from a

particular MAC address has reached the
configured maximum.

MAC address [chars] session limit threshold The number of PPPoE sessions from a
([unsigned int] sessions) reached.
particular MAC address has exceeded the
Maximum: [unsigned int] sessions.
configured threshold.
Outer vlan ([unsigned int]) on access
interface <<CH[hex]>> session limit
([unsigned int] sessions) threshold
reached. Further connection attempts will
be rejected.

The number of PPPoE sessions for a

particular Outer VLAN on the given access
interface has reached the configured
maximum.

Outer vlan ([unsigned int]) on access

interface <<CH[hex]>> session limit
([unsigned int] sessions) threshold
reached. Maximum: [unsigned int]
sessions.

The number of PPPoE sessions for a

particular Outer VLAN on the given access
interface has exceeded the configured
threshold.

Remote ID [chars] session limit ([unsigned

int] sessions) threshold maximum reached. The number of PPPoE sessions on a
Further connection attempts will be
particular Remote ID has reached the
rejected.
configured maximum.

Remote ID [chars] session limit ([unsigned The number of PPPoE sessions on a

int] sessions) threshold reached. Maximum: particular Remote ID has exceeded the
[unsigned int] sessions.
configured threshold.
Vlan ([unsigned int], [unsigned int]) on
access interface <<CH[hex]>> session
limit ([unsigned int] sessions) threshold
reached. Further connection attempts will
be rejected.

The number of PPPoE sessions for a

particular VLAN on the given access
interface has reached the configured
maximum.

Vlan ([unsigned int], [unsigned int]) on

access interface <<CH[hex]>> session
limit ([unsigned int] sessions) threshold
reached. Maximum: [unsigned int]
sessions.

The number of PPPoE sessions for a

particular VLAN on the given access
interface has exceeded the configured
threshold.

Error destroying '[chars]' connection:

[chars]

During process termination PPPoE MA failed

to destroy a connection to a service
provided by another process. This is an
internal error.

Error destroying event queue for '[chars]':

[chars]

During process termination PPPoE MA failed

to destroy an event queue. The process will
terminate regardless so there should be no
lasting problems.

Access interface <<CH[hex]>> session

The number of PPPoE sessions on the
limit maximum ([unsigned int] sessions) no access interface is no longer exceeding the
longer reached.
configured maximum.

Access interface <<CH[hex]>> session

The number of PPPoE sessions on the
limit threshold ([unsigned int] sessions) no access interface is no longer exceeding the
longer reached.
configured threshold.

The number of PPPoE sessions on the card

Card session limit maximum ([unsigned int] is no longer exceeding the configured
sessions) no longer reached.
maximum.

The number of PPPoE sessions on the card

Card session limit threshold ([unsigned int] is no longer exceeding the configured
sessions) no longer reached.
threshold.

Circuit ID [chars] and Remote ID [chars]

[chars]session limit ([unsigned int]
sessions) threshold maximum no longer
reached.

The number of PPPoE sessions on a

particular Circuit ID and Remote ID is no
longer exceeding the maximum.

Circuit ID [chars] and Remote ID [chars]

session limit ([unsigned int] sessions)
threshold no longer reached.

The number of PPPoE sessions on a

particular Circuit ID and Remote ID is no
longer exceeding the configured threshold.

The number of PPPoE sessions on a

Circuit ID [chars] session limit ([unsigned
particular Circuit ID is no longer exceeding
int] sessions) maximum no longer reached. the configured maximum.

The number of PPPoE sessions on a

Circuit ID [chars] session limit ([unsigned
particular Circuit ID is no longer exceeding
int] sessions) threshold no longer reached. the configured threshold.

Inner vlan ([unsigned int]) on access

interface <<CH[hex]>> session limit
([unsigned int] sessions) maximum no
longer reached.

The number of PPPoE sessions for a

particular Inner VLAN on the given access
interface iss no longer exceeding the
configured maximum.

Inner vlan ([unsigned int]) on access

interface <<CH[hex]>> session limit
([unsigned int] sessions) threshold no
longer reached.

The number of PPPoE sessions for a

particular Inner VLAN on the given access
interface is no longer exceeding the
configured threshold.

MAC address [chars] on access interface

<<CH[hex]>> session limit maximum
([unsigned int] sessions) no longer
reached.

The number of PPPoE sessions from a

particular MAC address on the given access
interface is no longer exceeding the
configured maximum.

MAC address [chars] on access interface

<<CH[hex]>> session limit threshold
([unsigned int] sessions) no longer
reached.

The number of PPPoE sessions from a

particular MAC address on the given access
interface is no longer exceeding the
configured threshold.

MAC-IWF address [chars] on access

interface <<CH[hex]>> session limit
maximum ([unsigned int] sessions) no
longer reached.

The number of IWF PPPoE sessions from a

particular MAC address on the given access
interface is no longer exceeding the
configured maximum.

MAC-IWF address [chars] on access

interface <<CH[hex]>> session limit
threshold ([unsigned int] sessions) no
longer reached.

The number of IWF PPPoE sessions from a

particular MAC address on the given access
interface is no longer exceeding the
configured threshold.

MAC-IWF address [chars] session limit

maximum ([unsigned int] sessions) no
longer reached.

The number of IWF PPPoE sessions from a

particular MAC address is no longer
exceeding the configured maximum.

MAC-IWF address [chars] session limit

threshold ([unsigned int] sessions) no
longer reached.

The number of IWF PPPoE sessions from a

particular MAC address is no longer
exceeding the configured threshold.

MAC address [chars] session limit

maximum ([unsigned int] sessions) no
longer reached.

The number of PPPoE sessions from a

particular MAC address is no longer the
configured maximum.

MAC address [chars] session limit threshold The number of PPPoE sessions from a
([unsigned int] sessions) no longer
particular MAC address has exceeded the
reached.
configured threshold.

Outer vlan ([unsigned int]) on access

interface <<CH[hex]>> session limit
([unsigned int] sessions) maximum no
longer reached.

The number of PPPoE sessions for a

particular Outer VLAN on the given access
interface is no longer exceeding the
configured maximum.

Outer vlan ([unsigned int]) on access

interface <<CH[hex]>> session limit
([unsigned int] sessions) threshold no
longer reached.

The number of PPPoE sessions for a

particular Outer VLAN on the given access
interface is no longer exceeding the
configured threshold.

The number of PPPoE sessions on a

Remote ID [chars] session limit ([unsigned particular Remote ID is no longer
int] sessions) maximum no longer reached. exceeding the configured maximum.

The number of PPPoE sessions on a

Remote ID [chars] session limit ([unsigned particular Remote ID is no longer
int] sessions) threshold no longer reached. exceeding the configured threshold.

Vlan ([unsigned int], [unsigned int]) on

The number of PPPoE sessions for a
access interface <<CH[hex]>> session
particular VLAN on the given access
limit ([unsigned int] sessions) maximum no interface iss no longer exceeding the
longer reached.
configured maximum.

Vlan ([unsigned int], [unsigned int]) on

The number of PPPoE sessions for a
access interface <<CH[hex]>> session
particular VLAN on the given access
limit ([unsigned int] sessions) threshold no interface is no longer exceeding the
longer reached.
configured threshold.

Failed to initialze Subscriber Util: [chars]

This syslog is printed when Subscriber Util

or its clients fail to initialize necessary data
structures and memories. If the error
originates from the system call the error
message is also printed. The process
cannot proceed without this module
initialization.

Failed to initialze Subscriber util: [chars]

This syslog is printed when RwString

Manager or its clients fail to initialize
necessary data structures and memories. If
the error originates from the system call
the error message is also printed. The
process cannot proceed without this
module initialization.

Subscriber Infra Flow control encounterd

unexpected error :[hex][[chars]] context:
[[chars]]

Subcriber Session Flow control Infra init

encounterd unexpected error, so the
sesison flow control feature is not enabled.

Failed to initialize [chars] :[chars]

This is a non-fatal error in initializing

tracing buffer and can happen when the
router is low on memory. It should not
affect the functioning of the router, but
trace messages may not be logged.

Failed to initialize [chars] :[chars]

This is a non-fatal error in initializing

tracing buffer and can happen when the
router is low on memory. It should not
affect the functioning of the router, but
trace messages may not be logged.

Failed to shutdown [chars] :[chars]

This is a non-fatal error in closing tracing

buffer and can happen when the router is
low on memory. It should not affect the
functioning of the router, but trace
messages may not be logged.

Failed to shutdown [chars] :[chars]

This is a non-fatal error in closing tracing

buffer and can happen when the router is
low on memory. It should not affect the
functioning of the router, but trace
messages may not be logged.

Subscriber Infra is [chars]ready. Reason:

[[chars]].

Subcriber Session Flow control is enabled

or disabled. Because Subcriber
Infrastructure become is ready or not
ready. i.e, system recovered from or
reached to critical state or BNG infra
strucute process is restarted, hence new
subscriber sessions creation is enabled or
disabled.

Features configured under the dynamic

template are not supported for this node,
dynamic-template '[chars]' has
so this feature will not be applied for
unsupported configuration '[chars]' for this subscribers hosting on this will not have
node
this feature configuration.

[chars]

An unexpected internal error occurred in

the template manager subsystem.

Failed to initialize '[chars]' when enabling

VPDN feature, [hex]:[chars].

When 'vpdn' configuration is first added,

the VPDN CALL infra initializes in client
processes, namely PPP-MA. Something has
failed in this process and may prevent
VPDN from functioning.

An essential part of the VPDN CALL infra

Failed to initialize '[chars]' when initializing has failed to initialize in a client process
VPDN feature, [hex]:[chars].
and may prevent VPDN from functioning.

An IPC notification was received that

Received IPC error for '[chars]' notificaton, indicates an error. 1 or more sessions may
[hex]:[chars].
not establish or may be torn down.

Failed to send IPC message length

[unsigned int], [hex]:[chars].

A VPDN CALL message failed to be sent to

VPDN MGR. 1 or more sessions may not
establish or may be torn down.

A VPDN CALL's Subscriber Attribute

Failed to update SADB attribute '[chars]' for Database parameters were not updated.
user '[chars]' (sub_label:[hex] sub_ifh:
This may affect accounting and show
[hex]), [hex]:[chars].
commands.
When VPDN Manager (vpdn_mgr) is either
the active process or RPFO occurs, the
process initializes active-only services.
Failed to initialize '[chars]' at active, [hex]: Something has failed in this proceedure
[chars].
and may prevent VPDN from functioning.
Failed to receive event from [chars] EVM,
[hex]:[chars].

The event processing infra has returned a

fatal error.

Failed to initialize '[chars]', [hex]:[chars].

When 'vpdn' configuration is first added,

the VPDN Manager (vpdn_mgr) process
starts and initializes. Something has failed
in this proceedure and may prevent VPDN
from functioning.

Failed at '[chars]' during shutdown, [hex]:

[chars].

When 'vpdn' configuration is removed, the

VPDN Manager (vpdn_mgr) process will
shutdown and exit. Something has failed in
this proceedure and may prevent VPDN
from functioning later or releasing
resources.

Failed to alloc ([unsigned int] hdr) +

([unsigned int] items)*([unsigned int]
bytes) = ([unsigned int] total bytes) for
'[chars]', errno [dec]:[chars].

The VPDN CALL infra has failed to allocate

memory. This may be due to low memory
conditions on this particular RP/LC, or this
client may be using more memory than it is
allowed.

Failed to uninitialize '[chars]' when

disabling VPDN feature, [hex]:[chars].

When 'vpdn' configuration is removed, the

VPDN CALL infra uninitializes in client
processes, namely PPP-MA. Something has
failed in this process any may contribute to
leaked resources. In some cases, this
warning message may be harmless.

Failed to uninitialize '[chars]' when

uninitializing VPDN feature, [hex]:[chars].

Part of the VPDN CALL infra has failed to

uninitialize and may contribute to leaked
resources. In some cases, this warning
message may be harmless.

Failed to disconnect IPC, [hex]:[chars].

The VPDN CALL IPC failed to disconnect as

a result of configuration or an internal error.
In some cases, this warning message may
be harmless.

Failed to process TLV type [unsigned int]

length [unsigned int].

Messages are exchanged between the

VPDN Manager (vpdn_mgr) process and the
client (e.g. ppp_ma). An error has occured
here and session state may be out of sync.

Failed to ADD session dataplane

programming for <<CH[hex]>> on
<<CH[hex]>> (Tunnel/Session Local:
[unsigned int]/[unsigned int] Remote:
[unsigned int]/[unsigned int]), [hex]:
[chars].

Failed to program session dataplane in

L2FIB.

The VPDN MGR failed to program the

dataplane for 1 or more sessions. These
sessions must be distributed from VPDN
MGR to all instances of L2FIB on all nodes.
This failure may affect the establishment or
Failed to send batch of [unsigned int] bytes tear-down of 1 or more sessions. In the
containing [unsigned int] sessions, [hex]:
case of tear-down, these resources may be
[chars].
leaked.

Failed to DELETE session dataplane

programming for <<CH[hex]>> on
<<CH[hex]>>, [hex]:[chars].

Failed to DELETE session dataplane from

L2FIB. Resources may be leaked for this
session.

Failed to '[chars]' for socket app data for

user '[chars]' (sub_label:[hex] sub_ifh:
[hex]).

VPDN MGR failed process internal

messages. This may be due to low memory
conditions.

Failed to connect to protocol for user

'[chars]' (sub_label:[hex] sub_ifh:[hex]).

VPDN application failed to connect to

procotol socket. This may be due to low
memory conditions or an invalid argument.

Failed to '[chars]' for NVPairs for user

'[chars]' (sub_label:[hex] sub_ifh:[hex]),
[unsigned int].

VPDN MGR failed process internal

messages. This may be due to low memory
conditions.

Failed to '[chars]' for NVPair attribute

VPDN MGR failed process internal
'[unsigned int]' for user '[chars]' (sub_label: messages. This may be due to low memory
[hex] sub_ifh:[hex]).
conditions.
Failed to '[chars]' for socket options for
user '[chars]' (sub_label:[hex] sub_ifh:
[hex]), [unsigned int].

VPDN MGR failed process internal

messages. This may be due to low memory
conditions.

Failed to alloc ([unsigned int] hdr) +

([unsigned int] items)*([unsigned int]
bytes) = ([unsigned int] total bytes) for
'[chars]', errno [dec]:[chars].

The VPDN MGR process has failed to

allocate memory. This may be due to low
memory conditions on this particular RP, or
VPDN Manager may be user more memory
than it is allowed.

Failed to alloc from chunk '[chars]', [dec]:

[chars].

The VPDN MGR process has failed to

allocate memory. This may be due to low
memory conditions on this particular RP, or
VPDN Manager may be user more memory
than it is allowed.

L2TP session id space configuration is

incompatible in the system. It is configured
hierarchical, while only flat can be
supported for the system.

L2TP session id space configuration is

incompatible in the system. This may
prevent new sessions from coming up .
Also , existing sessions may be affected.

[chars]

A VPDN session has been terminated due

to authentication-related error

[chars]

A VPDN session has been terminated due

to authorization-related error

[chars]

An LNS peer is added to or remove from

dead cache

[chars]

A VPDN session has been terminated due

to session-specific errors encountered in
local or remote VPDN or L2TP protocol
processing

[chars]

A VPDN session has been terminated due

to errors encountered by the L2TP tunnel
that contains the affected session

[chars]

A VPDN session has been terminated. The

category of the termination event is
unknown

[chars]

A VPDN session has been terminated due

to user action such as user inactivity has
exceeded the configured idle time or user
has hung up the call.

[chars]: rc [hex] ([chars])

The backend library has either failed a

function that expected to succeed, or has
got into an inconsistent state.

[chars] for pathname [chars]: rc [hex]

([chars])

The backend library has either failed a

function that expected to succeed, or has
got into an inconsistent state.

Invalid arguments to [chars]

Invalid arguments were supplied to a

backend function

Invalid arguments to [chars] for path

[chars]

Invalid arguments were supplied to a

backend function

An ipaddress was passed in with '[chars]'

but a uint was expected. The value passed The backend library has detected a
was '[chars]'; backend converted this to
mismatch between the actual and parsed
'[chars]'
values of a node.

A [chars] argument was not in a valid

format. The value passed was '[chars]';
backend converted this to '[chars]'

The backend library has detected a

mismatch between the actual and parsed
values of a node.

[chars]: rc [hex]

The client library has either failed a

function that expected to succeed, or has
got into an inconsistent state.

An internal error has occurred in the bag

The bag infrastructure has encountered an library. Some management functions may
error. [chars]
not operate correctly.

[chars] : [chars] - Error:[chars]

There was an internal error during garbage

collection.

ixdb state recovered from interrupted

add/remove operation.

The low level ixdb database has recovered

after a process restart. Upper layers must
recover from a potentially incomplete bulk
operation as well as any application data
inconsistency within ixdb. Ixdb only
recovers its own state.

The config size([dec] operations) exceeds

critical mem limits, the config request
requires ([dec] kbytes) of mem Wdsysmon
mem state([dec]) total node free
memory([dec]). Split the config in to
smaller chunks and reattempt the config to
avoid config failures

The message to the user to indicate that

the requested config size excceds the
critical system memory limits and the
config request will be allowed to proceed

The config size([dec] operations) exceeds

critical mem limits, the config request
requires ([dec] kbytes) of mem Wdsysmon
mem state([dec]) total node free
memory([dec]). Split the config in to
smaller chunks and reattempt the config to
avoid config failures

The message to the user to indicate that

the requested config size excceds the
critical system memory limits and the
config request will be allowed to proceed

The config size([dec] operations) exceeds

high watermark Requires ([dec] kbytes) of The message to the user to indicate that
memory. Wdsysmon mem state([dec]) total the requested config size excceds the high
node free memory([dec])
end of the system memory limits
The config size([dec] operations) exceeds
high watermark Requires ([dec] kbytes) of The message to the user to indicate that
memory. Wdsysmon mem state([dec]) total the requested config size excceds the high
node free memory([dec])
end of the system memory limits

An apply function failed while a verifier was

[unsigned int] out of [unsigned int] apply
scanning SysDB (e.g. after restarting), so
callbacks failed (first error: [chars]), system the operational state of the system may be
may now be in an inconsistent state.
inconsistent with the running configuration.

An apply function failed while a verifier was

[unsigned int] out of [unsigned int] apply
scanning SysDB (e.g. after restarting), so
callbacks failed (first error: [chars]), system the operational state of the system may be
may now be in an inconsistent state.
inconsistent with the running configuration.

Failed to register block [dec] errors cerr_register_dll returned [chars]

The client library has failed to register

SysDB's error code (cerrno) definitions.

Failed to register block [dec] errors cerr_register_dll returned [chars]

The client library has failed to register

SysDB's error code (cerrno) definitions.

The config size([dec] operations) exceeds

low watermark Requires ([dec] kbytes) of
The message to the user to indicate that
memory. Wdsysmon mem state([dec]) total the requested config size excceds the low
node free memory([dec])
end of the system memory limits

The config size([dec] operations) exceeds

low watermark Requires ([dec] kbytes) of
The message to the user to indicate that
memory. Wdsysmon mem state([dec]) total the requested config size excceds the low
node free memory([dec])
end of the system memory limits

SysDB client library received an EDM 'BIND'

message not intended for it. Most probable The SysDB client library was unable to
cause of this error is that some other EDM complete an EDM 'BIND' request as the
has registered with the same LWM channel EDM registration information sent with the
name as this EDM.
message was invalid for the EDM.

SysDB client library received an EDM 'BIND'

message not intended for it. Most probable The SysDB client library was unable to
cause of this error is that some other EDM complete an EDM 'BIND' request as the
has registered with the same LWM channel EDM registration information sent with the
name as this EDM.
message was invalid for the EDM.

[chars]: rc [hex] ([chars])

The client library has either failed a

function that expected to succeed, or has
got into an inconsistent state.

[chars]: rc [hex] ([chars])

The client library has either failed a

function that expected to succeed, or has
got into an inconsistent state.

Failed to [chars] [chars]. Error [dec]

([chars])

The client library has either failed to aquire

or release a lock.

Failed to [chars] [chars]. Error [dec]

([chars])

The client library has either failed to aquire

or release a lock.

Failed to [chars] [chars]. Error [dec]

([chars]). Retrying

The client library has either failed to aquire

or release a lock.

An attempt was made to register a multiple

verifier with a default function on path
'[chars]' which already has a default
provider.

Another process has already registered a

default provider function on this path. It is
not possible to have multiple default
providers.

An attempt was made to register a multiple

verifier with a default function on path
'[chars]' which already has a default
provider.

Another process has already registered a

default provider function on this path. It is
not possible to have multiple default
providers.

Failed to pick up a message from the

The SysDB client library has failed to pick
server. Client connid: [dec], server connid: up a message from the server after
[dec]. Error: [hex] ([chars]).
receiving an async pulse.

Failed to pick up a message from the

The SysDB client library has failed to pick
server. Client connid: [dec], server connid: up a message from the server after
[dec]. Error: [hex] ([chars]).
receiving an async pulse.

Failed to reconnect to SysDB server and re- The client library has failed to reconnect to
register: rc [hex] ([chars])
the SysDB server.

Failed to reconnect to SysDB server and re- The client library has failed to reconnect to
register: rc [hex] ([chars])
the SysDB server.

Maximum number of bind referrals hit

attempting to connect to path [chars].

An internal library error has caused a

connection attempt from a client to SysDB
to fail.

Maximum number of bind referrals hit

attempting to connect to path [chars].

An internal library error has caused a

connection attempt from a client to SysDB
to fail.

If an EDM registers or reregisters on a path

on which items already exist (and
SYSDB_REGISTRATION_OPTION_SCAN has
been specified), then those items have
Failed to restore items after EDM
been deleted but not all restored after the
registration on [chars], system may now be EDM registration, so the system may now
in an inconsistent state.
be in an inconsistent state.

If an EDM registers or reregisters on a path

on which items already exist (and
SYSDB_REGISTRATION_OPTION_SCAN has
been specified), then those items have
Failed to restore items after EDM
been deleted but not all restored after the
registration on [chars], system may now be EDM registration, so the system may now
in an inconsistent state.
be in an inconsistent state.

Unable to send a LWM message due to a

non-connection-related error ([dec]).

The SysDB client library has failed to send

a LWM message to the server, due to
receiving an unexpected non-connectionrelated error in sending the message.

Unable to send a LWM message due to a

non-connection-related error ([dec]).

The SysDB client library has failed to send

a LWM message to the server, due to
receiving an unexpected non-connectionrelated error in sending the message.

SysDB path '[chars]' is deprecated

An operation has been attempted on a part

of the SysDB namespace that should no
longer be used.

Message #[hex] state:[hex], destined for

[chars], error waiting rinfo. so far [dec] of
[dec] expected responses: [chars]. Check
for potential transport issues within the
system.

A request error due to gsp error during

SYSDB MC waited the expected number of
replies. Then SYSDB MC would take
recovery process

[chars]: rc [hex] ([chars])

The server has either failed a function that

expected to succeed, or has got into an
inconsistent state.

[chars]

The server has got into an inconsistent

state.

SysDB path '[chars]' is invalid

An operation has been attempted on a part

of the SysDB namespace that should not
be used.

Missing node down notification from node

[chars]

No node down notification was received

from the underlying infrastructure for a
recent node reload.

Multi-node access from transaction will be

non-atomic (transaction node [dec]:[dec],
accessing node [dec]:[dec], by [chars])

An application tried to use a transaction to

access multiple nodes; this is not
supported currently.

[chars] ('[chars]' from '[chars]') ([chars])

A pathname was used for a SysDB

operation from which the destination node
could not be parsed.

There was a mismatch between the

A incompatible version of a message was messaging protocol version used by the
received from process id [dec], node [dec] SysDB MC and the SysDB MS.

This process is restarting, as ([chars]) is

failing. [chars] ([chars]).

The SysDB server is unable to function due

to a problem with one of its modules. The
only hope of recovery is to restart. If the
problem persists, the card will be
automatically reloaded.

Message #[hex] state:[hex], gid([unsigned

int]), destined for [chars], timed out having
received [unsigned int] of [unsigned int]
expected responses: returning [chars] to
client [chars]. Check for potential transport
issues within the system, or deadlocked
A request timed out before SysDB MC
SysDB processes.
received the expected number of replies

Message #[hex] state:[hex], gid([unsigned

int]), destined for [chars], timed out
waiting rinfo. so far [unsigned int] of
[unsigned int] expected responses:
returning [chars] to client [chars]. Check
for potential transport issues within the
A request timed out before SysDB MC
system.
received the expected number of replies

Attempted multi-node access from

transaction was prevented (attempted to
access multi-cast group [dec])

A client attempted to use an unsupported

distributed transaction.

We are receiving messages of a type that

we did not expect. This should not cause
An unexpected([chars]) message type was failures of any kind, but probably does
received: [hex]: sender gid([unsigned int]) indicate an error in another part of the
nid([hex]) pid ([unsigned int])
system.

Received unexpected multiple responses

for message of type [hex]

The SysDB Medusa process received

multiple responses for a message type for
which only a single response was expected.

Encountered unexpected [chars]: [hex]

The server has come across an unexpected

value for the specified parameter.

An attempt was made to access SysDB

path '[chars]'. This resolves to the [chars] An application has tried to access a plane
plane and cannot be accessed on this card of SysDB data that does not exist on this
type.
node.
Unable to respond back to client jid: [dec]
nid : [dec]. This will be reported as an SMC An internal error left the msg tag to be an
timeout by the sysdb_mc originating the
invalid one. Causing the request to be
request
timedout.

An Invalid TAG was dequeued rc([hex]),

tag([hex]), len([hex])

We are dequeuing an invalidly TAGGED

message for transmission This should not
cause failures of any kind, but probably
does indicate an error in another part of
the system.

We are posting zero sized messages that

A zero BYTE message was
we did not expect. This should not cause
posted,type([dec]),flags([hex]),msg_id([hex failures of any kind, but probably does
]) event_msg_id([hex]), client_connid([dec]) indicate an error in another part of the
server_connid([dec])
system.

EDM Manager jid: [dec] nid: [dec] response A Client is responding with a very huge
too big, size: [dec]
data, it should split the response.

[chars]: rc [hex] ([chars])

The SysDB server has either failed a

function that expected to succeed, or has
got into an inconsistent state.

Failed to [chars] [chars]. Error [dec]

([chars])

The SysDB server has either failed to

acquire or release a lock.

Missing node down notification from node

[chars]

No node down notification was received

from the underlying infrastructure for a
recent node reload.

There was a mismatch between the

A incompatible version of a message was messaging protocol version used by the
received from process id [dec], node [dec] SysDB MC and the SysDB server.

Reg from [dec]/[dec]/[dec] already exists

for connid [dec] and reg_handle [dec]

Sysdb is attempting to add a registration

that already exists in its registration
context. This will cause a sysdb server
restart.

Reg from [dec]/[dec]/[dec] already exists

for msgid [dec]

Sysdb is attempting to add a registration

that already exists in its secondary
registration context. This will cause a sysdb
server restart.

Sysdb is attempting to del a registration

Delete of Reg from [dec]/[dec]/[dec] exists that does not exist in its secondary
for msgid [dec] fails
registration context.

The SysDB server is unable to function due

to a problem with a piece of infrastructure.
Not able to send message out, as an
The only hope of recovery is to restart. If
essential piece of infrastructure ([chars]) is the problem persists, the card will be
failing. [chars] ([chars]).
automatically reloaded.

This process is restarting, as an essential

piece of infrastructure ([chars]) is failing.
[chars] ([chars]).

The SysDB server is unable to function due

to a problem with a piece of infrastructure.
The only hope of recovery is to restart. If
the problem persists, the card will be
automatically reloaded.

Sending [chars] via

group_sendv_memberset failed [msg_size
[unsigned int]]: [hex] ([chars])

The SysDB server failed to send a message

to the SysDB Medusa Client

We are receiving messages of a type that

we did not expect. This should not cause
An unexpected([chars]) message type was failures of any kind, but probably does
received: [hex]: sender gid([unsigned int]) indicate an error in another part of the
nid([hex]) pid ([unsigned int])
system.

Encountered unexpected [chars]: [hex]

The SysDB server came across an

unexpected value for the specified
parameter.

malloc of %zd bytes failed

A SysDB server process failed on malloc

certain number of bytes.

[Sysdbcon] Could not bind to SysDB:

[chars]

Sysdbcon was unable to bind to the root of

SysDB. It is possible that there is a problem
with SysDB.

[Sysdbcon] SysDB returned unrecognised

datatype ([unsigned int])

The datatype returned by SysDB does not

match any of those expected by Sysdbcon.
This is probably because the type is
missing in Sysdbcon.

The packed tuple returned from SysDB is in

[Sysdbcon] Unable to extract format string some way corrupt. The format string it
from packed tuple
contains could not be read.

[Sysdbcon] Unable to read from command An error occurred during a read operation
file
from the instruction file.

[Sysdbcon] An internal error has occurred

The code has performed an action which

should not be possible.

[Sysdbcon] The specified command file

([chars]) could not be opened

The instruction file specified when

Sysdbcon was started cannot be found. The
most probable reason is that an incorrect
name was supplied.

[Sysdbcon] Unable to read in data for

packed tuple

An error occurred while preparing to read

instructions from the command line.

[Sysdbcon] Unable to create packed tuple

An error occurred creating a packed tuple.

An error occurred during a read operation

[Sysdbcon] No data for packed tuple in file from the instruction file.

[Sysdbcon] Unable to initialize the

command line reader

An error occurred while preparing to read

instructions from the command line.

The packed tuple returned from SysDB is in

some way corrupt. The data it contains
[Sysdbcon] Unable to unpack packed tuple could not be read.

Process is exiting, thread ID: ([dec])

A thread of SysDB server or medusa

process has exited for some critical reason
and will be restarted.

The SysDB replicator module has been

informed that it may have been out of sync
when taking over as the new active server.
A possible configuration inconsistency has The other replica nodes will sync up, but it
been detected. Please check recent
is possible that a recent configuration
configuration changes and verify that
change may have been partially or
configuration is consistent with binary files. completely lost.

[Sysdbcon] While aborting a bulk operation An error occurred invoking a SysDB

the following error occurred:\n[chars]
function. The details are in the error string.

[Sysdbcon] While aborting a transaction

the following error occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

The user entered integer in unrecognized

[Sysdbcon] Warning: bad integer format or format or out of range of current integer
integer value is out of range.
data type.

[Sysdbcon] Badly formatted command

An unescaped ''' character was found part

way through a token in a command string.

[Sysdbcon] Warning: now bound to a nonexistent node.

The user bound to a node which does not

exist. This is a warning only - this action is
perfectly legal.

[Sysdbcon] While getting the number of

operations in the bulk the following error
occurred:\n[chars]

An error occurred invoking a SysDB

function. This could be because the
operation does not exist. The details are in
the error string.

[Sysdbcon] While adding deletes to the

bulk buffer the following error
occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] While adding diffs to the bulk

the following error occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] While performing a bulk regular

expression delete the following error
An error occurred invoking a SysDB
occurred:\n[chars]
function. The details are in the error string.

[Sysdbcon] While merging files the

following error occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] While removing deletes to the

bulk buffer the following error
occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] While committing a transaction An error occurred invoking a SysDB

the following error occurred:\n[chars]
function. The details are in the error string.

[Sysdbcon] While copying item [chars] to

[chars] the following error
occurred:\n[chars]

An error occurred invoking a SysDB

function. This could be because the item to
copy does not exist. The details are in the
error string.

An error occurred invoking a SysDB

function. This could be because the item to
[Sysdbcon] While creating item [chars] the create already exists. The details are in the
following error occurred:\n[chars]
error string.

[Sysdbcon] While executing the find data

request the following error
occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] While executing the datalist

request the following error
occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] Unrecognised datatype

([chars])

A datatype other than one of those

supported was supplied.

An error occurred invoking a SysDB

function. This could be because the item
[Sysdbcon] While deleting item [chars] the does not exist. The details are in the error
following error occurred:\n[chars]
string.

[Sysdbcon] While generating EDM

notifications the following error
occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] While ending a bulk operation

the following error occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] While executing the errors list

request the following error
occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] Unrecognised notification event A notification event other than one of those
([chars])
supported was supplied.

[Sysdbcon] While executing the event find

request the following error
An error occurred invoking a SysDB
occurred:\n[chars]
function. The details are in the error string.

[Sysdbcon] Excess tokens in command

string

There were more tokens entered as part of

the command string than are required for
the command.

[Sysdbcon] While restoring items from a

file the following error occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] While saving items to a file the An error occurred invoking a SysDB
following error occurred:\n[chars]
function. The details are in the error string.

[Sysdbcon] While executing the find

request the following error
occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] While performing

operation \'[chars]\' the following error
occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

An error occurred invoking a SysDB

function. This could be because the item to
[Sysdbcon] While fetching item [chars] the fetch does not exist. The details are in the
following error occurred:\n[chars]
error string.

An error occurred invoking a SysDB

[Sysdbcon] While fetching item's
function. This could be because the items
inheritance from path [chars] the following to fetch do not exist. The details are in the
error occurred:\n[chars]
error string.

An error occurred invoking a SysDB

[Sysdbcon] While fetching items from path function. This could be because the items
[chars] the following error
to fetch do not exist. The details are in the
occurred:\n[chars]
error string.

[Sysdbcon] While executing the iterate

request the following error
occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] While executing the list request An error occurred invoking a SysDB
the following error occurred:\n[chars]
function. The details are in the error string.

[Sysdbcon] Mismatched quotes in

command

A quoted token was not terminated with a

quote character.

[Sysdbcon] Missing notification event

The command entered requires a

notification event type and one was not
supplied.

[Sysdbcon] Missing file name

The command entered requires an file

name and one was not supplied.

[Sysdbcon] Missing item name

The command entered requires an item

name and one was not supplied.

[Sysdbcon] Missing item type

The command entered requires an item

type and one was not supplied.

[Sysdbcon] Missing item value

The command entered requires an item

value and one was not supplied.

When combining the path supplied with the

[Sysdbcon] Unable to create full path from path Sysdbcon is currently bound to an
path supplied\nCurrent dir: [chars]\nPath
error occurred. This could be because the
supplied [chars]
path created would be invalid.

[Sysdbcon] Format string contains illegal

character ([char])

The packed tuple format string should only

contain combinations of '%', 'd', 'ld' and 's'.
A character other than one of these was
found in the string.

[Sysdbcon] While getting a read lock the

following error occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] While binding to [chars] the

following error occurred:\n[chars]

An error occurred invoking a SysDB

function. This could be because the path
supplied is invalid. The details are in the
error string.

[Sysdbcon] While removing operation on

[chars] the following error
occurred:\n[chars]

An error occurred invoking a SysDB

function. This could be because the
operation does not exist. The details are in
the error string.

[Sysdbcon] While setting item [chars] the

following error occurred:\n[chars]

An error occurred invoking a SysDB

function. This could be because the item
does not exist or has the wrong type. The
details are in the error string.

[Sysdbcon] While starting a bulk operation An error occurred invoking a SysDB

the following error occurred:\n[chars]
function. The details are in the error string.

An error occurred invoking a SysDB

function. This could be because the
[Sysdbcon] While starting a transaction the timeout time was not correctly entered.
following error occurred:\n[chars]
The details are in the error string.

[Sysdbcon] Unrecognised command. Type

help or ? for a list of available commands

The first token in a command string was

not a recognised Sysdbcon command.

[Sysdbcon] While releasing a lock the

following error occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] Verification failed on item

[chars] for the following reason\n[chars]

An error occurred invoking a SysDB

function. This could be because the item
does not exist or has the wrong type. Or
because the verifier did not allow the
change. The details are in the error string.

[Sysdbcon] While resuming verification the An error occurred invoking a SysDB

following error occurred:\n[chars]
function. The details are in the error string.

[Sysdbcon] While suspending verification

the following error occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

[Sysdbcon] While getting a write lock the

following error occurred:\n[chars]

An error occurred invoking a SysDB

function. The details are in the error string.

Process '[chars]' (jid [dec], node [chars])

failed to pick up notification event within
A notification event sent by the SysDB
the timeout period ([unsigned int] seconds) server timed out.

EDM request for '[chars]' from '[chars]' (jid

[dec], node [chars]). No response from
'[chars]' (jid [dec], node [chars]) within the A timeout occured whilst processing a
timeout period ([unsigned int] seconds)
request.

[chars] (jid [dec]) wrote to the

configuration namespace (item: /[chars]).
Illegal modification of configuration is not
allowed.

A non-management client illegally modified

part of the system configuration.

A SysDB server process was unable to

update a per-client statistics counter for
one of its clients. This is an unexpected
[chars]: client name: [chars], jid: [dec], nid: condition, though has no effect on router
[dec], counter: [hex]
operation.

SysDB usage statistics for [chars] (jid:

[dec], nid: [dec]) and [chars] (jid: [dec],
nid: [dec]) have been unexpectedly
combined and should be treated as
inaccurate

The per-client usage statistics for the

SysDB clients identified in the message
have been combined, when they should be
stored separately. The statistics for these
processes should be treated as inaccurate.
This is an unexpected condition, though
has no effect on router operation.

[chars]: rc [hex] ([chars])

The server detected an error with one of its

clients.

[chars]: rc [hex] ([chars])

The server has either failed a function that

expected to succeed, or has got into an
inconsistent state.

[chars] attempted an item get on a subtree A process, likely to be a show command, is

path ([chars]). Item gets should only be
attempting to access a sysdb item with an
attempted on items, with no trailing '/'
incorrect path string.

Failed to [chars] [chars]. Error [dec]

([chars])

The server has either failed to aquire or

release a lock.

SysDB ltrace init failed. Error initialising

[[chars]] trace buffer. Error returned by
ltrace initialisation: [chars]

The ltrace buffer could not be initialised

No completion notification received for

update message [unsigned int]

The SysDB replicator module on the active

server did not receive a callback from the
transport library. The request will be
allowed to continue without the replication
acknowledgement. If any replicas have not
received the update, they will resync on
the next update.

Failed to send reply to client jid [unsigned The server failed to reply to a client
int] tid [unsigned int] node [chars]: rc [hex] request. A likely reason for this is that the
([chars])
process in question has exited.

[chars]: rc [hex] ([chars])

An unexpected error occurred during

initialisation of the replicator module.

The SysDB server failed to send an

asynchronous message to a SysDB client. A
[chars] to process '[chars]' (jid [dec], node likely reason for this is that the process in
[chars]): errno: [dec] ([chars])
question has exited.

A SysDB server process has performed a

Process is shutting down, rc [hex] ([chars]) graceful shutdown and will be restarted.

Startup request for '[chars]' from '[chars]'

(jid [dec]) failed for a process on a slow
starting node

A startup request failed during the second

round of callbacks.

Incorrect arguments: Usage: [chars] <l|s|

a> [svr_threads] l = local-plane; s =
shared-plane; a = admin-plane Maximum
number of threads is [dec].

Incorrect command line parameters were

passed to the sysdb server, and so it failed
to start.

[chars]: rc [hex]

The client library has either failed a

function that expected to succeed, or has
got into an inconsistent state.

Failed to [chars] [chars]. Error [dec]

The client library has either failed to aquire

or release a lock.

[chars]: rc [hex] ([chars])

The client library has either failed a

function that expected to succeed, or has
got into an inconsistent state.

The client library was unable to convert the

NodeID to string conversion failed for node specified node ID into a node description
id [dec] (rc [hex] - [chars])
string.

Failed to [chars] [chars]. Error [dec]

The client library has either failed to aquire

or release a lock.

Recommended Action

TAC Details

Check the error string and collect required

information listed below.
--

Check the error string and try to restart the

mibd_interface process with the command
<CmdBold>process restart mibd_interface
<NoCmdBold> If this does not correct the
problem, collect the required information
listed below.
--

None

--

The use of Access Control List compression

library is restricted to Packet Filtering
Execution Agent (pfilter_ea) only. This error
message does not impact the functioning
of the system. To find out why the issue
has occurred, please note down the name
of the offending process.
--

Check the error string and collect required

information
--

None

--

None

The caching consumes memory so could be

the cause of the memory exhaustion,
pushing an already depleted box over the
edge. Reducing the memory consumption
on the node is the only fix.

Abort the configuration operation and

restart the parser server.

This should never happen. The

recommended action should fix the
problem, but there must be a bug
somewhere for this to happen. Report this
to Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Collect the requested show tech-support

info and forward it to development
engineering team

--

Specify an access list that does not specify

any object group in any of its entries.
--

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

Please get the information specified under

the component required_info and call your
Cisco technical support representative and
provide the the gathered information with
this error message text. If the message
recurs, copy the error message exactly as it For the access-lists configured or show
appears on the console or in the system
commands and other details, please refer
log, call your Cisco technical support
to the COLTS page through the following
representative and provide the
link:
representative with the gathered
http://zed.cisco.com/confluence/display/GS
information.
RTR/ACL+XR

Please get the information specified under

the component required_info and call your
Cisco technical support representative and
provide the representative with the
gathered information with this error
message text. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
http://zed.cisco.com/confluence/display/GS
RTR/ACL+XR

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Possible causes of failure are the mutex is

corrupted, has not been initialised or is
being accessed recursively (this is not
allwowed). All of these are bugs in the
process that is using the ACL library, and
not in the ACL library. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

None

--

This message may occur during process

initialization. Please try restarting the
process that issued this error message with
the command. <CmdBold>process restart
<process_name> location <node
id><NoCmdBold>. Process name should
be printed in the message already.

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
http://zed.cisco.com/confluence/display/GS
RTR/ACL+XR

This message may occur during process

initialization. Please try restarting the
process that issued this error message with
the command. <CmdBold>process restart
<process_name> location <node
id><NoCmdBold>. Process name should
be printed in the message already.

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
http://zed.cisco.com/confluence/display/GS
RTR/ACL+XR

This message may occur during process

initialization. Please try restarting the
process that issued this error message with
the command. <CmdBold>process restart
<process_name> location <node
id><NoCmdBold>. Process name should
be printed in the message already.

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
http://zed.cisco.com/confluence/display/GS
RTR/ACL+XR

This message may occur during process

initialization. Please try restarting the
process that issued this error message with
the command. <CmdBold>process restart
<process_name> location <node
id><NoCmdBold>. Process name should
be printed in the message already.

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
http://zed.cisco.com/confluence/display/GS
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
Please try simplifying the configuration for to the COLTS page through the following
this equipment. If problem persists even
link:
with simplified configuration, contact Cisco http://zed.cisco.com/confluence/display/GS
TAC.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
Please try simplifying the configuration for to the COLTS page through the following
this equipment. If problem persists even
link:
with simplified configuration, contact Cisco http://zed.cisco.com/confluence/display/GS
TAC.
RTR/ACL+XR

Please try restarting the process that

issued this error message with the
command. <CmdBold>process restart
<process_name> location <node
id><NoCmdBold>. Process name should
be printed in the message already.

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
http://zed.cisco.com/confluence/display/GS
RTR/ACL+XR

Please try restarting the process that

issued this error message with the
command. <CmdBold>process restart
<process_name> location <node
id><NoCmdBold>. Process name should
be printed in the message already.

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
http://zed.cisco.com/confluence/display/GS
RTR/ACL+XR

This message may occur during process

initialization. Please try restarting the
process that issued this error message with
the command. <CmdBold>process restart
<process_name> location
<location><NoCmdBold>. Process name
should be printed in the message already.

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
http://zed.cisco.com/confluence/display/GS
RTR/ACL+XR

Collect the requested show tech-support

info and forward it to development
engineering team

--

Specify an access list that does not specify

any object group in any of its entries.
--

No action is required.

--

No action is required.

--

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

For the access-lists configured or show

commands and other details, please refer
to the COLTS page through the following
link:
This is information only message, no action http://zed.cisco.com/confluence/display/GS
required No action is required.
RTR/ACL+XR

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

If this message recurs, copy the System

Message exactly as it appears on the
console or in the system log, enter the
<CmdBold>show process
li_mgr<NoCmdBold> command and, if the
line card was reloaded, collect
<CmdBold>show context<NoCmdBold>
output, contact Cisco technical support
representative, and provide the
representative with the required_info.

Try to resolve the issue by restarting the

netio process. 'process restart netio
location <>'. If the issue is still not
resolved enable the debugs as mentioned
in the following wiki page: http://wikieng.cisco.com/engwiki/IOX_25LI_25PI

None

--

Allow OBJ Manager to restart. If the

problem persists, contact Cisco support.

None.

Allow OBJ Manager to restart. You can

further remove and re-add 'object group'
configuration. If the problem persists,
contact Cisco support.

None.

If the action suggested in the error

message does not help, try exiting and reentering the config mode. If this doesn't
This is an error related to cli parsing. The
help try restarting parser_server via cli
collected information is for internal
'process restart parser_server'. Contact TAC diagnosis. Raise a DDTS and attach all the
if the problem persist, with required_info.
needed information to the DDTS.
This is an error related to memory
Either reduce the configuration applied on allocation. The collected information is
this node or increase its memory. If the
used for diagnosis purpose. Raise a DDTS
error is persistent, contact TAC with
and attach all the needed information to
required_info.
the DDTS.

None.

--

Try exiting and re-entering the config

mode. If this doesn't help try restarting
parser_server.

--

None.

--

Contact TAC with required_info, which will

be only used for internal diagnosis
purpose.

This is an internal error related to getting

application name. The collected
information is for internal diagnosis. Raise
a DDTS and attach all the needed
information to the DDTS.

This is an internal error. The collected

Collect required_info and contact TAC, and information is for internal diagnosis. Raise
the collected information is only used for
a DDTS and attach all the needed
internal diagnosis.
information to the DDTS.

None

--

Ensure the targeted line card is properly

seated in the specified slot. If the line card
is properly seated, ensure the correct slot
was indicated in the command-line
interface. If the line card is well-seated and
the correct slot was specified, copy the
error message exactly as it appears on the
screen as well as the output of show techsupport and paste the output into a
separate file. Contact your technical
Report this to Engineering. Use Topic to
support representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Copy the error message exactly as it

appears on the screen and gather the
output of show tech-support and any other
relevant information. Contact your
Report this to Engineering. Use Topic to
technical support representative with the search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Copy the error message exactly as it

appears on the screen and gather the
output of show tech-support and any other
relevant information. Contact your
Report this to Engineering. Use Topic to
technical support representative with the search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Re-seat the card and retry the test. If the

same result occurs after reseating the card
and retrying the test, copy the error
message exactly as it appears on the
screen and gather the output of show techsupport and any other relevant
information. Contact your technical support Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Re-seat the card and retry the test. If the

same result occurs after reseating the card
and retrying the test, copy the error
message exactly as it appears on the
screen and gather the output of show techsupport and any other relevant
information. Contact your technical support Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Copy the error message exactly as it

appears on the screen and gather the
output of show tech-support and any other
relevant information. Contact your
Report this to Engineering. Use Topic to
technical support representative with the search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Ensure the line card is firmly in the slot,

reseat if necessary, and attempt to run the
test again if the line card is not seated
properly in the slot. If the line card was
properly seated in the slot, copy the error
message exactly as it appears on the
console, gather the output of show techsupport, and contact your Cisco technical Report this to Engineering. Use Topic to
support representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Copy the error message exactly as it

appears on the screen and gather the
output of show tech-support and any other
relevant information. Contact your
Report this to Engineering. Use Topic to
technical support representative with the search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.
Nothing. The specific health monitoring
test cannot be disabled by design. The
system is working properly.

--

The system is working properly and no user

action is required. If you want to run the
specified diagnostic test, either wait for the
current diagnostic test to finish and then
run the test, or stop the current test and
run the new test.
-Nothing. The specific health monitoring
interval is not user-configurable by design
so nothing can be done to change the
interval.

--

Ensure that the specified device number

(1-based) exists and is valid.

--

The system is working properly and no user

action is required. If you want to specify a
smaller testing interval, the warning
message text provides the lowest possible
configurable interval for the specified
monitoring interval.
--

Ensure the specified port number exists

and that the correct port number is being
specified.

--

Ensure the specified test ID number is

supported by the line card. The list of
available tests and their associated test IDs
can be retrieved using 'show diagnostic
content'.
--

The system is working properly and no user

action is required. If you want the
requested test to be a health monitoring
test, enable health monitoring and ensure
your test is enabled as a health monitoring
test.
-If you want the scheduling tests to be
removed, do nothing. If you want the
scheduled tests to still be run, reconfigure
the scheduled tests.

--

Nothing. The system is working properly

and the specified test cannot be configured
as a health monitoring test.
-This message does not indicate any
problem with the system. The test cannot
be run because it is not supported on this
chassis configuration. No further action is
required.

--

This behavior is consistent with the user

configuration and no action needs to be
taken. If you want to run bootup
diagnostics, enable bootup diagnostics by
using the diagnostic bootup command.

--

Nothing. This is an informational message

stating that the line card passed the
diagnostic tests.

--

Nothing. This is an informational message

stating that diagnostic testing has been
stopped. If you want the test to run to
completion, rerun the test.

--

None.

--

None. This is an informational message.

--

In some cases on some platforms, a Field

Diagnostic image needs to be loaded onto
the line card if you want to run the test. If
applicable, download a Field Diagnostic
image onto the line card. In other cases,
the test is simply not available. This
message is an informational and does not
require user action.
-Nothing. This is an informational message
and the system is working properly.

--

Nothing. This is an informational message

and the system is working properly.

--

Check the results and proceed accordingly.

This is an information message only to
indicate that Diagnostic testing is
complete. The router is working properly
and no action is needed based on this
message.
-Nothing. The diagnostic test is being run as
configured and the system is working
properly.
-If you do not want the test to run, do
nothing. If you want the test to run,
schedule the test or run the test manually. --

If you want the scheduling tests to be

removed, do nothing. If you want the
scheduled tests to still be run, reconfigure
the scheduled tests.

--

Nothing. This is an informational message

and the system should be working properly. --

This is an informational message indicating

that Field Diagnostic testing has completed
successfully. The system is working
properly and no action is required based on
this error message.
-Nothing. This is an informational message
and the system should be working properly. -Nothing. Although the test cannot be run,
this message does not indicate a problem. -Nothing. The test cannot be run but the
system is working properly.

--

Nothing. The test cannot be run but the

system is working properly.

--

Another software component will attempt

to fix the problem or may give additional
error messages. Please check Bug
Navigator
( https://tools.cisco.com/bugsearch?
referring_site=btk ) to search for any bugs
in this area. If the error messages continue,
copy all error messages exactly as they
appear on the screen and gather any
relevant information about the
circumstances. Also collect the information
from the 'show logging' and 'show tech
diagnostics' commands. Contact your
technical support representative with the
gathered information.

Please see
http://zed.cisco.com/confluence/display/GS
RTR/CRS-1+Diagnostic Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Check the log ('show logging') to see if any

processes have restarted or to determine if
there are any other related error messages.
Also, please check Bug Navigator
( https://tools.cisco.com/bugsearch?
referring_site=btk ) to search for any bugs
in this area or of any processes found to
have restarted. Copy the error message
exactly as it appears on the screen and
gather any relevant information about the Please see
circumstances. Also collect the information http://zed.cisco.com/confluence/display/GS
from the 'show logging' and 'show tech
RTR/CRS-1+Diagnostic Report this to
diagnostics' commands. Contact your
Engineering. Use Topic to search for a
technical support representative with the similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Check the log ('show logging') to determine

if there are any other related error
messages. Also, please check Bug
Navigator
( https://tools.cisco.com/bugsearch?
referring_site=btk ) to search for any bugs
in this area. Copy the error message
exactly as it appears on the screen and
gather any relevant information about the Please see
circumstances. Also collect the information http://zed.cisco.com/confluence/display/GS
from 'show logging' and 'show tech
RTR/CRS-1+Diagnostic Report this to
diagnostics' commands. Contact your
Engineering. Use Topic to search for a
technical support representative with the similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Normally this message type indicates a

transient error, and even though it will
cause the process to be terminated, the
problem will usually be remedied once the
emitting process is restarted. If the error
keeps occuring frequently then copy the
error message exactly as it appears on the
screen and gather any relevant information
about the circumstances. Contact your
technical support representative with the
gathered information.
--

Normally this message type indicates a

transient error, and even though it will
cause the process to be terminated, the
problem will usually be remedied once the
emitting process is restarted. If the error
keeps occuring frequently then copy the
error message exactly as it appears on the
screen and gather any relevant information
about the circumstances. Contact your
Report this to Engineering. Use Topic to
technical support representative with the search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Check the log ('show logging') to determine

if there are any other related error
messages. Also, please check Bug
Navigator
( https://tools.cisco.com/bugsearch?
referring_site=btk ) to search for any bugs
in this area. If the error continues, copy the
error message exactly as it appears on the
screen and gather any relevant information Please see
about the circumstances. Also collect the
http://zed.cisco.com/confluence/display/GS
information from 'show logging' and 'show RTR/CRS-1+Diagnostic Report this to
tech diagnostics' commands. Contact your Engineering. Use Topic to search for a
technical support representative with the similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Check the log ('show logging') to determine

if there are any other related error
messages. Also, please check Bug
Navigator
( https://tools.cisco.com/bugsearch?
referring_site=btk ) to search for any bugs
in this area. If the error continues, copy the
error message exactly as it appears on the
screen and gather any relevant information Please see
about the circumstances. Also collect the
http://zed.cisco.com/confluence/display/GS
information from the 'show logging' and
RTR/CRS-1+Diagnostic Report this to
'show tech diagnostics' commands. Contact Engineering. Use Topic to search for a
your technical support representative with similar DDTS. If you find none, write a
the gathered information.
DDTS for this problem.

Check the log ('show logging') to determine

if there are any other related error
messages. Also, please check Bug
Navigator
( https://tools.cisco.com/bugsearch?
referring_site=btk ) to search for any bugs
in this area. if the error continues, copy the
error message exactly as it appears on the
screen and gather any relevant information Please see
about the circumstances. Also collect the
http://zed.cisco.com/confluence/display/GS
information from 'show logging' and 'show RTR/CRS-1+Diagnostic Report this to
tech diagnostics' commands. Contact your Engineering. Use Topic to search for a
technical support representative with the similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Check the log ('show logging') to determine

if there are any other related error
messages. Also, please check Bug
Navigator
( https://tools.cisco.com/bugsearch?
referring_site=btk ) to search for any bugs
in this area. Copy the error message
exactly as it appears on the screen and
gather any relevant information about the Please see
circumstances. Also collect the information http://zed.cisco.com/confluence/display/GS
from 'show logging' and 'show tech
RTR/CRS-1+Diagnostic Report this to
diagnostics' commands. Contact your
Engineering. Use Topic to search for a
technical support representative with the similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Check the log ('show logging') to determine

if there are any other related error
messages. Also, please check Bug
Navigator
( https://tools.cisco.com/bugsearch?
referring_site=btk ) to search for any bugs
in this area. If the error continues, copy the
error message exactly as it appears on the
screen and gather any relevant information Please see
about the circumstances. Also collect the
http://zed.cisco.com/confluence/display/GS
information from 'show logging' and 'show RTR/CRS-1+Diagnostic Report this to
tech diagnostics' commands. Contact your Engineering. Use Topic to search for a
technical support representative with the similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.
Copy the error message exactly as it
appears on the screen and gather any
relevant information about the
circumstances. Contact your technical
support representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the screen and gather any
relevant information about the
circumstances. Contact your technical
support representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Take note of the message, to see if it may

explain a later test failure or similar.

--

Take note of the message, to see if it may

explain a later test failure or similar.

--

1) Get the output from the following

commands: admin show logging admin
show control fabric trace fsdb-server fsdball location <dsc node> admin show
diagnostic result location <node that
printed out this msg> detail admin show
diagnostic trace error location all admin
show diagnostic trace message location all
2) shut down the identified faulty plane in
admin configuration: controller fabric plane
<> shutdown Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
--

Collect the console error messages exactly

as it appears on the console and call cisco
support engineers with the gathered
information.

Diagnostic software will take appropriate

action on failure. Please check the
explanation for more info. and if it recurs
again after reset please repair or replace
the failing unit under test.

Collect the console error messages exactly

as it appears on the console and call cisco
support engineers with the gathered
information.
--

Collect the console error messages exactly

as it appears on the console and call cisco After successfully isolating the problem to a
support engineers with the gathered
single link and/or asic, please repair or
information.
replace the failing unit under test.

This console error messages has been

logged as part of analysis during combined
unicast and multicast fabric diagnostic ping
test as part of the fault isolation mode
(FIM).If the issue is persistent or recurs
please replace or repair the affected node.
Please note: 1) It maybe caused by Source
node failure, destination node failure, or
multiple fabric planes failure. 2) It could be
single node or multinode unicast and/or
multicast failure. 3) It could be consecutive
unicast and/or multicast or cumulative
failure. 4) It's advisable to configure the
ANR provided as part of combined fabric
unicast and multicast diagnostic test for
safer side. 5) The fabric diagnostic and
Collect the console error messages exactly fabric multicast tests are no more in use.
as it appears on the console and call cisco User dont need to configure it explicitely to
support engineers with the gathered
avoid overlap it with the existing combined
information.
fabric unicast and multicast diagnostic test.

Collect the console error messages exactly

as it appears on the console and call cisco Check the devices under test is present or
support engineers with the gathered
not, if its present and issue recurs then
information.
please replace the unit under test.

Collect the console error messages exactly

as it appears on the console and call cisco
support engineers with the gathered
information.
--

Collect the console error messages exactly

as it appears on the console and call cisco
support engineers with the gathered
information.

Diagnostic software will take appropriate

action on failure. Please check the
explanation for more details. Try reseating
the affected node upon failure and if it
recurs please replace or repair the node.

Nothing. Reporting normal progress of

diagnostics.

--

Collect the console error messages exactly

as it appears on the console and call cisco
support engineers with the gathered
information.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

This might be a recovery action from a

fault. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
overall system. If there are failures here
Collect all the event logs and the output of then other processes may also exhibit
the following command executed from the similar problems. Report this to
CLI of the active RP: 'show process
Engineering. Use Topic to search for a
ccsq_mgr' Also, collect the fabric snapshot: similar DDTS. If you find none, write a
'show fabric-snapshot file <> loc <>'
DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If it is possible to isolate the trigger point

for the sn link error, collect all the
necessary condition that caused the error.
If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Run diags on the board. If this error is seen

consistently, it is recommended to reload
the MSC to avoid inconsistent behavior
because of the link error

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card.

This error is an correctable error. There are

no side effects. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card

Run diags on the board and contact TAC

support. If it is possible to isolate the
trigger point for the read failure, collect all
the necessary condition that caused the
error. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Read errors are reported asynchronously to

the driver. By the time the error is
processed by the driver the returned value
is already used. It is recommended to
reload the MSC to avoid inconsistent
behavior because of the read failure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Unlikely we see this message. This error

message indicates debug infra initialization
went wrong during system bootup. No
other action is required. Otherwise, Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

The Proxy will recover by restarting. Verify Refer to the description in field for this
that the fabric proxy process will recover
error. Check the fabric proxy behavior is
following action by the FM. If the message consistent with the FM guidelines defined
recurs, copy the error message exactly as it for this error type. This error isn't normally
appears on the console or in the system
persistent and should recover due to the
log, call your Cisco technical support
action taken by the fault management
representative and provide the
entity. Report this to Engineering. Use Topic
representative with the gathered
to search for a similar DDTS. If you find
information.
none, write a DDTS for this problem.

The Proxy will recover by restarting. Verify

that the driver will recover following action
by the FM. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Refer to the description in field for this

error. Check the fabric proxy behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

The Proxy will recover by restarting. Verify Refer to the description in field for this
that the fabric proxy process will recover
error. Check the fabric proxy behavior is
following action by the FM. If the message consistent with the FM guidelines defined
recurs, copy the error message exactly as it for this error type. This error isn't normally
appears on the console or in the system
persistent and should recover due to the
log, call your Cisco technical support
action taken by the fault management
representative and provide the
entity. Report this to Engineering. Use Topic
representative with the gathered
to search for a similar DDTS. If you find
information.
none, write a DDTS for this problem.

The Proxy will recover by restarting. Verify Refer to the description in field for this
that the fabric proxy process will recover
error. Check the fabric proxy behavior is
following action by the FM. If the message consistent with the FM guidelines defined
recurs, copy the error message exactly as it for this error type. This error isn't normally
appears on the console or in the system
persistent and should recover due to the
log, call your Cisco technical support
action taken by the fault management
representative and provide the
entity. Report this to Engineering. Use Topic
representative with the gathered
to search for a similar DDTS. If you find
information.
none, write a DDTS for this problem.

The Proxy will recover by restarting. Verify Refer to the description in field for this
that the fabric proxy process will recover
error. Check the fabric proxy behavior is
following action by the FM. If the message consistent with the FM guidelines defined
recurs, copy the error message exactly as it for this error type. This error isn't normally
appears on the console or in the system
persistent and should recover due to the
log, call your Cisco technical support
action taken by the fault management
representative and provide the
entity. Report this to Engineering. Use Topic
representative with the gathered
to search for a similar DDTS. If you find
information.
none, write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If problem either persists (following a

process restart) then Copy the error
message exactly as it appears on the
console or in the system log, call your
Search the event logs for the failure.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the problem is experienced only by this

process in the system, restart the fabric
server process by executing the following
command at the CLI of the active RP:
process restart fab_svr location <loc> If
problem either persists (following a process
restart) or also noticed on other processes
then Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for the failure.

Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the problem is experienced only by this

process in the system, restart the fabric
server process by executing the following
command at the CLI of the active RP:
process restart fab_svr location <loc> If
problem either persists (following a process
restart) or also noticed on other processes
then Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for the failure.

Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If problem either persists (following a

process restart) then Copy the error
message exactly as it appears on the
console or in the system log, call your
Search the event logs for the failure.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the problem is experienced only by this

process in the system, restart the fabric
server process by executing the following
command at the CLI of the active RP:
process restart fab_svr location <loc> If
problem either persists (following a process
restart) or also noticed on other processes
then Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for the failure.

Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the problem is experienced only by this

process in the system, restart the fabric
server process by executing the following
command at the CLI of the active RP:
process restart fab_svr location <loc> If
problem either persists (following a process
restart) or also noticed on other processes
then Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for the failure.

Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If problem either persists (following a

process restart) then Copy the error
message exactly as it appears on the
console or in the system log, call your
Search the event logs for the failure.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

If the problem is experienced only by this

process in the system, restart the fabric
server process by executing the following
command at the CLI of the active RP:
process restart fab_svr location <loc> If
problem either persists (following a process
restart) or also noticed on other processes
then Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for the failure.

Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the problem is experienced only by this

process in the system, restart the fabric
server process by executing the following
command at the CLI of the active RP:
process restart fab_svr location <loc> If
problem either persists (following a process
restart) or also noticed on other processes
then Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for the failure.

Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

Search the event logs to isolate the failure.
message exactly as it appears on the
If this problem persists then it is indicative
console or in the system log, call your
of a software bug. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information..
DDTS for this problem.

The prp3_fabric_driver process has

detected fabric FPGA errors at a rate which
warrants reseting the ASICs. When this
If the system has not failed over
condition occurs the device driver calls on
automatically and a redundant route
the Platform Manager to reset ASICs. This
processor card has been configured: 1 error indicates that the Platform Manager
force a failover with the following
failed to reset the ASICs. If an automatic
command in admin mode: 'redundancy
fail over has not occured the system is
switchover' 2 - reload the route processor unable to recover by itself. Operator
card that failed with the following
intervention is required to put the route
command in admin mode: 'reload location processor in an operational state. If a
RP/0/x/CPU0 ' where x is the slot of route
redundant Route Processor card has been
processor that generated the error. If no
configured, an operator initiated failover is
redundant RP is configured you will need to recommended. The procedure will not be
reboot the router by issuing the reload
service interrupting. If a redundant Route
command. Call your Cisco technical
Processor is not configured, the card will
support representative and provide the
need to be reloaded and the entire router
gathered information. Copy the error
will reboot. Persistent hardware faults such
message exactly as it appears on the
as the one that resulted in this error are
console or in the system log, call your
usually caused by hardware defects. The
Cisco technical support representative and failure of the Platform Manager to reset the
provide the representative with the
ASICs may also indicate a software
gathered information.
problem.

If a redundant route processor card has

been configured: 1 - force a failover with
the following command in admin mode:
'redundancy switchover' 2 - reload the
route processor card that failed with the
following command in admin mode: 'reload
location RP/0/x/CPU0' where x is the slot of
route processor that generated the error. If
no redundant RP is configured, you will
need to reboot the router by issuing the
reload command. If the error recurs call
your Cisco technical support representative
and provide the gathered information.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message indicates a failure of the

PRP fabric driver component. This class of
error is most likely caused by a hardware
failure. If the error is caused by hardware
failure, the route processor card will have
to be replaced.

If a redundant route processor card has

been configured: 1 - force a failover with
the following command in admin mode:
'redundancy switchover' 2 - reload the
route processor card that failed with the
following command in admin mode: 'reload
location RP/0/x/CPU0' where x is the slot of
route processor that generated the error. If
no redundant RP is configured, you will
need to reboot the router by issuing the
reload command. If the error recurs call
your Cisco technical support representative
and provide the gathered information.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message indicates a failure of the

PRP fabric queue driver component. This
class of error is most likely caused by a
hardware failure. If the error is caused by
hardware failure, the route processor card
will have to be replaced.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If a redundant route processor card has

been configured: 1 - force a failover with
the following command in admin mode:
'redundancy switchover' 2 - reload the
route processor card that failed with the
following command in admin mode: 'reload
location RP/0/x/CPU0' where x is the slot of
route processor that generated the error. If
no redundant RP is configured, you will
need to reboot the router by issuing the
reload command. If the error recurs call
your Cisco technical support representative
and provide the gathered information.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message indicates a failure of the

PRP fabric queue driver component. This
class of error is most likely caused by a
hardware failure. If the error is caused by
hardware failure, the route processor card
will have to be replaced. See EDCS-306371
chapter 6 for details.

If a redundant route processor card has

been configured: 1 - force a failover with
the following command in admin mode:
'redundancy switchover' 2 - reload the
route processor card that failed with the
following command in admin mode: 'reload
location RP/0/x/CPU0' where x is the slot of
route processor that generated the error. If
no redundant RP is configured, you will
need to reboot the router by issuing the
reload command. If the error recurs call
your Cisco technical support representative
and provide the gathered information.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message indicates a failure of the

PRP fabric queue driver component. This
class of error is most likely caused by a
hardware failure. If the error is caused by
hardware failure, the route processor card
will have to be replaced.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If a redundant route processor card has

been configured: 1 - force a failover with
the following command in admin mode:
'redundancy switchover' 2 - reload the
route processor card that failed with the
following command in admin mode: 'reload
location RP/0/x/CPU0' where x is the slot of
route processor that generated the error. If
no redundant RP is configured, you will
need to reboot the router by issuing the
reload command. If the error recurs call
your Cisco technical support representative
and provide the gathered information.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message indicates a failure of the

PRP fabric driver component. This class of
error is most likely caused by a system
error or a system reource deletion.

If the error recurs very frequently call your

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

The problem can happen with invalid

Stream ID encoded in the packet's header
by the sender. The problem can happen
from wrong hardware configuration on the
destination card to receive the error. But
the error should occur on boot up time for
most, if not all, clients. If the error is
caused by hardware failure, the route
processor card will have to be replaced.

If the error recurs very frequently call your

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

If the sender of the pkt indeed sent out a

packet with an invalid start offset, there
should be errors from the TFIA ASIC on the
sender's card. It can also happen that the
wrong hardware configuration on the
destination card to receive the error. But
the error should occur on boot up time for
most, if not all, clients. If the error is
caused by hardware failure, the route
processor card will have to be replaced.

The prp3_fabric_driver process should be

able to detect the error and decide to reset
fabric FPGA if necessary. If the error is
persistent, and router traffic is affected,
and if the system has not failed over
automatically and a redundant route
processor card has been configured: 1 force a failover with the following
command in admin mode 'redundancy
switchover' 2 - reload the route processor
card that failed with the following
command in admin mode 'reload location
RP/0/x/CPU0 ' where x is the slot of route
processor that generated the error. If no
redundant RP is configured you will need to
reboot the router by issuing the reload
command. Call your Cisco technical
support representative and provide the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The fabric FPGA detects a hardware error

on a packet received from the fabric. The
prp3_fabric_driver process should be able
to recovery from this by doing Hummer
FPGA reset or Hummer port reset. If this
error persists, and it is affecting router
operation, the router operator intervention
is required to put the route processor in an
operational state. If a redundant Route
Processor card has been configured, an
operator initiated failover is recommended.
The procedure will not be service
interrupting. If a redundant Route Processor
is not configured, the card will need to be
reloaded and the entire router will reboot.
Persistent hardware faults such as the one
that resulted in this error are usually
caused by hardware defects. The failure of
the Platform Manager to reset the ASICs
may also indicate a software problem.

Try restarting the process where the error

message was found. Otherwise, try the
following: If a redundant route processor
card has been configured: 1 - force a
failover with the following command in
admin mode: 'redundancy switchover' 2 reload the route processor card that failed
with the following command in admin
mode: 'reload location RP/0/x/CPU0' where
x is the slot of route processor that
generated the error. If no redundant RP is
configured, you will need to reboot the
router by issuing the reload command. If
the error recurs call your Cisco technical
support representative and provide the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The error message indicates a failure of the

PRP fabric queue driver component. This
class of error is most likely caused by a
hardware failure. If the error is caused by
hardware failure, the route processor card
will have to be replaced.

If a redundant route processor card has

been configured: 1 - force a failover with
the following command in admin mode:
'redundancy switchover' 2 - reload the
route processor card that failed with the
following command in admin mode: 'reload
location RP/0/x/CPU0' where x is the slot of
route processor that generated the error. If
no redundant RP is configured, you will
need to reboot the router by issuing the
reload command. If the error recurs call
your Cisco technical support representative
and provide the gathered information.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message indicates a failure of the

PRP fabric queue driver component. This
class of error is most likely caused by a
hardware failure. If the error is caused by
hardware failure, the route processor card
will have to be replaced.

Try restarting the process where the error

message was found. Otherwise, try the
following: If a redundant route processor
card has been configured: 1 - force a
failover with the following command in
admin mode: 'redundancy switchover' 2 reload the route processor card that failed
with the following command in admin
mode: 'reload location RP/0/x/CPU0' where
x is the slot of route processor that
generated the error. If no redundant RP is
configured, you will need to reboot the
router by issuing the reload command. If
the error recurs call your Cisco technical
support representative and provide the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The error message indicates a failure of the

PRP fabric queue driver component. This
class of error is most likely caused by a
hardware failure.

Try restarting the process where the error

message was found. Otherwise, try the
following: If a redundant route processor
card has been configured: 1 - force a
failover with the following command in
admin mode: 'redundancy switchover' 2 reload the route processor card that failed
with the following command in admin
mode: 'reload location RP/0/x/CPU0' where
x is the slot of route processor that
generated the error. If no redundant RP is
configured, you will need to reboot the
router by issuing the reload command. If
the error recurs call your Cisco technical
support representative and provide the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The error message indicates a failure of the

PRP fabric queue driver component. This
class of error is most likely caused by a
hardware failure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This is most likely an issue with the client

freeing packet buffers to cause the packet
processing code unable to reuse the packet
buffers

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Failure to open shared memory window.

Wait for retries and if you still see failures,
collect requested information.

The error is likely a software bug in tofab

packet error or process restart handling.
Copy the error message exactly as it
appears and report it to your Cisco
technical representative together with the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Refer to explanation for more detail. The

issue is likely due to a software bug in
handling tofab packet resources during an
error condition or process restart.

The slot should be reloaded to correct the

problem, if not done already by sysldr.
Copy the error message exactly as it
appears and report it to your Cisco
technical representative together with the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Refer to explanation for more detail. This

error is indicating a problem with one
linecard. Since the multicast queue is being
blocked as well, then other linecards are
affected. To alleviate this, sysldr is notified
of the problem slot, and sysldr decides to
reload the linecard. Investigate linecard
traces to hopefully determine linecard
problem. Configure 'service sysldr fabricping warn' to investigate the issue without
sylsdr reloading the linecard.

Copy the error message exactly as it

appears and report it to your Cisco
technical representative together with the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Refer to explanation for more detail. The

issue is likely due to a software bug in
handling tofab packet resources during an
error condition or process restart.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

This is information and does not require

any correction.

--

This is informational and does not require

any correction.

--

This is debug-level informational and does

not require any correction.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

ASIC Error library initialization is a very
message exactly as it appears on the
basic and fundamental software
console or in the system log, call your
infrastructure to allow users to record and
Cisco technical support representative and display the errors received by the driver.
provide the representative with the
There is likely other systems issues on the
gathered information.
board to lead to this.

If the message recurs, copy the error

message exactly as it appears on the
GASPP initialization is a very basic and
console or in the system log, call your
fundamental software infrastructure to
Cisco technical support representative and allow users to peek and poke the registers
provide the representative with the
inside a device. There is likely other
gathered information.
systems issues on the board to lead to this.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
There is likely a software issue for not
Cisco technical support representative and handling the unknown error. It is also
provide the representative with the
possible the unknown error is due to a
gathered information.
hardware issue.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
It is likely an issue with dirty optics in the
gathered information.
cable/connectors.

Determine: [a] If the LOS error is

continuous on the same sets of links/pod
channels [b] If there was an OIR of fabric
card on the receive end [c] If there was an
OIR of optical cable connecting to the POD
at either the transmit or receive end [d] If
there was an optical cable cut connecting
the POD LOS would be continuous if a link
If the message recurs, copy the error
without a valid receive end is wrongly
message exactly as it appears on the
configured by software. LOS happens
console or in the system log, call your
without any physical changes in the POD or
Cisco technical support representative and optical cable, then it can be either the
provide the representative with the
optical cable has gone bad, or the POD
gathered information.
channel has a hardware malfunction.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Determine: [a] If the LOS error is
provide the representative with the
continuous on the same sets of links/pod
gathered information.
channels [b] The trigger for the error

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
There is likely a software issue for not
Cisco technical support representative and handling the unknown error. It is also
provide the representative with the
possible the unknown error is due to a
gathered information.
hardware issue.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
There is likely a software issue for not
Cisco technical support representative and handling the unknown error. It is also
provide the representative with the
possible the unknown error is due to a
gathered information.
hardware issue.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
There is likely a software issue for not
Cisco technical support representative and handling the unknown error. It is also
provide the representative with the
possible the unknown error is due to a
gathered information.
hardware issue.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
There is likely a software issue for not
Cisco technical support representative and handling the unknown error. It is also
provide the representative with the
possible the unknown error is due to a
gathered information.
hardware issue.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

ASIC Error library initialization is a very
message exactly as it appears on the
basic and fundamental software
console or in the system log, call your
infrastructure to allow users to record and
Cisco technical support representative and display the errors received by the driver.
provide the representative with the
There is likely other systems issues on the
gathered information.
board to lead to this.

If the message recurs, copy the error

message exactly as it appears on the
GASPP initialization is a very basic and
console or in the system log, call your
fundamental software infrastructure to
Cisco technical support representative and allow users to peek and poke the registers
provide the representative with the
inside a device. There is likely other
gathered information.
systems issues on the board to lead to this.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
There is likely a software issue for not
Cisco technical support representative and handling the unknown error. It is also
provide the representative with the
possible the unknown error is due to a
gathered information.
hardware issue.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
It is likely an issue with dirty optics in the
gathered information.
cable/connectors.

Determine: [a] If the LOS error is

continuous on the same sets of links/pod
channels [b] If there was an OIR of fabric
card on the receive end [c] If there was an
OIR of optical cable connecting to the POD
at either the transmit or receive end [d] If
there was an optical cable cut connecting
the POD LOS would be continuous if a link
If the message recurs, copy the error
without a valid receive end is wrongly
message exactly as it appears on the
configured by software. LOS happens
console or in the system log, call your
without any physical changes in the POD or
Cisco technical support representative and optical cable, then it can be either the
provide the representative with the
optical cable has gone bad, or the POD
gathered information.
channel has a hardware malfunction.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This is likely a hardware problem. If the
provide the representative with the
error persists, power off the fabric card for
gathered information.
replacement.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Determine: [a] If the LOS error is
provide the representative with the
continuous on the same sets of links/pod
gathered information.
channels [b] The trigger for the error

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
There is likely a software issue for not
Cisco technical support representative and handling the unknown error. It is also
provide the representative with the
possible the unknown error is due to a
gathered information.
hardware issue.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
There is likely a software issue for not
Cisco technical support representative and handling the unknown error. It is also
provide the representative with the
possible the unknown error is due to a
gathered information.
hardware issue.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
There is likely a software issue for not
Cisco technical support representative and handling the unknown error. It is also
provide the representative with the
possible the unknown error is due to a
gathered information.
hardware issue.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
There is likely a software issue for not
Cisco technical support representative and handling the unknown error. It is also
provide the representative with the
possible the unknown error is due to a
gathered information.
hardware issue.

An error occured while the sfe_drvr (fabric

asic driver) was initializing it's internal
state. This should be a transitory error. The
sfe_drvr process gets respawned
If the message recurs, copy the error
automatically by sysmgr. If the proecess
message exactly as it appears on the
does not get respawned automatically, try
console or in the system log, call your
restarting this process (sfe_drvr) manually.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration.
If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If this condition is noticed for every access Verify that the address location being
to the ASIC, then the ASIC is possibly
accessed is valid for this ASIC. Also, verify
wedged. Resetting the ASIC or reloading
if the first failed access is to a register that
the fabric card will help to recover from this is contained in a block which is still in the
condition. Copy the error message exactly logic reset state. Also, verify that the fabric
as it appears on the console or in the
PLD rev is 0x1c or above. If the PLD rev is
system log, call your Cisco technical
below 0x1c, update the PLD image. Report
support representative and provide the
this to Engineering. Use Topic to search for
representative with the gathered
a similar DDTS. If you find none, write a
information.
DDTS for this problem.

An error occured while the sfe_drvr (fabric

asic driver) was initializing it's internal
state. This should be a transitory error. The
sfe_drvr process gets respawned
If the message recurs, copy the error
automatically by sysmgr. If the proecess
message exactly as it appears on the
does not get respawned automatically, try
console or in the system log, call your
restarting this process (sfe_drvr_lite)
Cisco technical support representative and manually. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.
No action is required.

This is a run-time error probably caused by

resource constraints

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

None.

An error occured while the sfe_drvr (fabric

asic driver) was initializing it's shared
memory state. The sfe_drvr process should
exit with error, and respawned
If the message recurs, copy the error
automatically by sysmgr. If the process
message exactly as it appears on the
does not get respawned automatically, try
console or in the system log, call your
restarting this process (sfe_drvr) manually.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
Verify the voltage levels from all the
console or in the system log, call your
voltage controllers and check that the
Cisco technical support representative and board is properly seated in the chassis.
provide the representative with the
Also, verify that the controls from the SP
gathered information.
are enabled to power the board.

If the message recurs, copy the error

message exactly as it appears on the
Verify the voltage levels from all the
console or in the system log, call your
voltage controllers and check that the
Cisco technical support representative and board is properly seated in the chassis.
provide the representative with the
Also, verify that the controls from the SP
gathered information.
are enabled to power the board.

If the message recurs, copy the error

message exactly as it appears on the
Verify the voltage levels from all the
console or in the system log, call your
voltage controllers and check that the
Cisco technical support representative and board is properly seated in the chassis.
provide the representative with the
Also, verify that the controls from the SP
gathered information.
are enabled to power the board.

If the message recurs, copy the error

message exactly as it appears on the
Verify the voltage levels from all the
console or in the system log, call your
voltage controllers and check that the
Cisco technical support representative and board is properly seated in the chassis.
provide the representative with the
Also, verify that the controls from the SP
gathered information.
are enabled to power the board.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
If issue persists, Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect console logs. Copy the error

message exactly as it appears on the
console or in the system log, call your
Possible HW fault on board. Shutdown
Cisco technical support representative and affected plane associated with SM node.
provide the representative with the
Run diagnostics. Depending on results,
gathered information.
may need to RMA the node.

Collect console logs. Copy the error

message exactly as it appears on the
console or in the system log, call your
Possible HW fault on board. Shutdown
Cisco technical support representative and affected plane associated with SM node.
provide the representative with the
Run diagnostics. Depending on results,
gathered information.
may need to RMA the node.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
None.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
None.

Check the health of the sysmgr process on

the node. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

An error occurred while the sfe_drvr tries to

go to maintenance mode with a sysmgr
API. This can be a sysmgr issue. This also
be an OS level issues. Try manually
shutting down the card using CLI. Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

Check the health of the shelfmgr process

on the RP in its rack. If shelfmgr is healthy,
and the card cannot self reload, then
reload the card with the following
command in admin mode: 'hw shut loc
y/SMx/sp', where x is the SM module
number that generated the error, y is the
rack that it is in. If manual shutdown does
not work, or if the error recurs, call your
Cisco technical support representative and
provide the gathered information. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

An error occurred while the sfe_drvr tries to

connect shut down the fabric card with a
shelfmgr API. This can be shelfmgr was
restarting due to software install or
software error. This also be control
ethernet, QSM, or OS level issues. Try
manually shutting down the card using CLI.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

*RECUR*

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
overall system. If there are failures here
then other processes may also exhibit
similar problems. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the error is seen at steady state, software

will auto recover. Verify that the fabric is
stable. If fabric appears unstable, collected
fabric show tech.
None.

If the error is seen at steady state, software

will auto recover. Verify that the fabric is
stable. If fabric appears unstable, collected
fabric show tech.
None.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

No action is required.

As indicated, this message implies that the

ASIC is either not powered or is not \ reset
properly. The output of the above CLI will
help to verify if the voltages on \ the board
are within the expected range.

No action is required.

None.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
If issue persists, Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
If issue persists, Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
If issue persists, Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
If issue persists, Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
Ensure that the SPB has the necessary
gathered information.
hardware fix to support ASIC scan.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
Ensure that the SPB has the necessary
gathered information.
hardware fix to support ASIC scan.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.

If the message recurs, copy the error

message exactly as it appears on the
Verify the voltage levels & temperature on
console or in the system log, call your
all the voltage controllers and check that
Cisco technical support representative and the board is properly seated in the chassis.
provide the representative with the
Also, verify that the controls from the SP
gathered information.
are enabled to power the board.

If the message recurs, copy the error

message exactly as it appears on the
Verify the voltage levels & temperature on
console or in the system log, call your
all the voltage controllers and check that
Cisco technical support representative and the board is properly seated in the chassis.
provide the representative with the
Also, verify that the controls from the SP
gathered information.
are enabled to power the board.

Shut down the plane associated to this

fabric card, and upgrade the PLD Version of
this board. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Shut down the plane associated to this
representative with the gathered
fabric card, and request to get the fabric
information.
card PLD version upgraded.
Capture information as specified in the
required_info section. Restart sfe_drvr to
clear any out of sync issues.

Collect the required_info and contact fabric

team. Fabric wiki is located at
http://zed.cisco.com/confluence/display/GS
RTR/CRS+Fabric.

An error occured while the sfe_drvr (fabric

asic driver) was initializing it's internal
state. This should be a transitory error. The
sfe_drvr process gets respawned
If the message recurs, copy the error
automatically by sysmgr. If the proecess
message exactly as it appears on the
does not get respawned automatically, try
console or in the system log, call your
resuperstarting this process (sfe_drvr)
Cisco technical support representative and manually. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

An error occured while the sfe_drvr (fabric

asic driver) was initializing it's internal
state. This should be a transitory error. The
sfe_drvr process gets respawned
If the message recurs, copy the error
automatically by sysmgr. If the proecess
message exactly as it appears on the
does not get respawned automatically, try
console or in the system log, call your
resuperstarting this process (sfe_drvr)
Cisco technical support representative and manually. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

An error occured while the sfe_drvr (fabric

asic driver) was initializing it's internal
state. This should be a transitory error. The
sfe_drvr process gets respawned
If the message recurs, copy the error
automatically by sysmgr. If the proecess
message exactly as it appears on the
does not get respawned automatically, try
console or in the system log, call your
resuperstarting this process (sfe_drvr)
Cisco technical support representative and manually. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

No action is required.

None.

No action is required.

None.

No action is required.

None.

No action is required.

None.

None. software error handling will recover. None.

None. software error handling will recover. None.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
None.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Determine if there were any

Check if all the required fabric cards are UP communication error on gsp/ethernet on fdi
and running.
group.

Determine if there were any

Check if all the required fabric cards are UP communication error on gsp/ethernet on fdi
and running.
group.

Determine if there were any

Check if all the required fabric cards are UP communication error on gsp/ethernet on fdi
and running.
group.

Capture information as specified in the

required_info section. Restart sfe_drvr to
clear any out of sync issues.

Capture memory usage information on the

node on which this message was logged.
Collect the required_info and contact fabric
team. Fabric wiki is located at
http://zed.cisco.com/confluence/display/GS
RTR/CRS+Fabric.

Capture information as specified in the

required_info section. Restart sfe_drvr to
clear any out of sync issues. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration.

Capture memory usage information on the

node on which this message was logged.
Collect the required_info and contact fabric
team. Fabric wiki is located at
http://zed.cisco.com/confluence/display/GS
RTR/CRS+Fabric.

Capture information as specified in the

required_info section. Restart sfe_drvr to
clear any out of sync issues. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration.

Capture memory usage information on the

node on which this message was logged.
Collect the required_info and contact fabric
team. Fabric wiki is located at
http://zed.cisco.com/confluence/display/GS
RTR/CRS+Fabric.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and The most likely cause is a faulty POD
provide the representative with the
device; the card containing the POD may
gathered information.
need to be replaced.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and The most likely cause is a faulty POD
provide the representative with the
device; the card containing the POD may
gathered information.
need to be replaced.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and The most likely cause is a faulty POD
provide the representative with the
device; the card containing the POD may
gathered information.
need to be replaced.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Check the health of the shelfmgr process

on the dSC RP. If shelfmgr is healthy, and
the card does not reload after waiting for
minutes, reload the card with the following
command in admin mode: 'reload loc
0/SMx/sp', where x is the SM module
number that generated the error. If manual
reload does not work, or if the error recurs,
call your Cisco technical support
representative and provide the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

An error occurred while the sfe_drvr tries to

connect to shelfmgr on the dSC to reload
the card. This can be shelfmgr was
restarting due to software install or
software error. This also be control
ethernet, QSM, or OS level issues. This
should be a transitory error. If the card
does not get reloaded automatically, try
reloading the card using CLI. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.

Check the health of the shelfmgr process

on the dSC RP. If shelfmgr is healthy, and
the card cannot self reload, then reload the
card with the following command in admin
mode: 'reload loc y/SMx/sp', where x is the
SM module number that generated the
error, and y is the rack that it is in. If
manual reload does not work, or if the error
recurs, call your Cisco technical support
representative and provide the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

An error occurred while the sfe_drvr tries to

connect to shelfmgr on the dSC to reload
the card. This can be shelfmgr was
restarting due to software install or
software error. This also be control
ethernet, QSM, or OS level issues. This
should be a transitory error. If the card
does not get reloaded automatically, try
reloading the card using CLI. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Check the health of the shelfmgr process

on the dSC RP. If shelfmgr is healthy, and
the card cannot self reload, then reload the
card with the following command in admin
mode: 'reload loc y/SMx/sp', where x is the
SM module number that generated the
error, and y is the rack that it is in. If
manual reload does not work, or if the error
recurs, call your Cisco technical support
representative and provide the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

An error occurred while the sfe_drvr tries to

connect to shelfmgr on the dSC to reload
the card. This can be shelfmgr was
restarting due to software install or
software error. This also be control
ethernet, QSM, or OS level issues. This
should be a transitory error. If the card
does not get reloaded automatically, try
reloading the card using CLI. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Check the health of the shelfmgr process

on the dSC RP. If shelfmgr is healthy, and
the card cannot self reload, then reload the
card with the following command in admin
mode: 'reload loc y/SMx/sp', where x is the
SM module number that generated the
error, and y is the rack that it is in. If
manual reload does not work, or if the error
recurs, call your Cisco technical support
representative and provide the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

An error occurred while the sfe_drvr tries to

connect to shelfmgr on the dSC to reload
the card. This can be shelfmgr was
restarting due to software install or
software error. This also be control
ethernet, QSM, or OS level issues. This
should be a transitory error. If the card
does not get reloaded automatically, try
reloading the card using CLI. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None

No action is required.

None.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

No action is required.

This could be because of infra failure. If

issue persists, Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Determine if there were any

Check if all the required fabric cards are UP communication error on gsp/ethernet on fdi
and running.
group.

Determine if there were any

Check if all the required fabric cards are UP communication error on gsp/ethernet on fdi
and running.
group.

Determine if there were any

Check if all the required fabric cards are UP communication error on gsp/ethernet on fdi
and running.
group.

If the message recurs, copy the error

message exactly as it appears on the
For Error Node Keys - 0x1050016;
console or in the system log, call your
0x1050018; 0x105001A : This indicates a
Cisco technical support representative and hardware problem in Fabric ASIC and the
provide the representative with the
Fabric ASIC on this node needs to be
gathered information.
replaced.

If the message recurs, copy the error

message exactly as it appears on the
For Error Node Keys - 0x1050016;
console or in the system log, call your
0x1050018; 0x105001A : This indicates a
Cisco technical support representative and hardware problem in Fabric ASIC and the
provide the representative with the
Fabric ASIC on this node needs to be
gathered information.
replaced.

If the message recurs, copy the error

message exactly as it appears on the
For Error Node Keys - 0x1050016;
console or in the system log, call your
0x1050018; 0x105001A : This indicates a
Cisco technical support representative and hardware problem in Fabric ASIC and the
provide the representative with the
Fabric ASIC on this node needs to be
gathered information.
replaced.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This indicates a hardware problem in Fabric
provide the representative with the
ASIC and the Fabric ASIC on this node
gathered information.
needs to be replaced.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This indicates a hardware problem in Fabric
provide the representative with the
ASIC and the Fabric ASIC on this node
gathered information.
needs to be replaced.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This indicates a hardware problem in Fabric
provide the representative with the
ASIC and the Fabric ASIC on this node
gathered information.
needs to be replaced.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This indicates a hardware problem in Fabric
provide the representative with the
ASIC and the Fabric ASIC on this node
gathered information.
needs to be replaced.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
None.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
None.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
This indicates a link problem in receive side
console or in the system log, call your
or in the optics or in the trasmit side on the
Cisco technical support representative and upstream link. If this is an OOB link please
provide the representative with the
reseat the cards on both ends of the link
gathered information.
one by one to try to fix the issue.

If the message recurs, copy the error

message exactly as it appears on the
This indicates a link problem in receive side
console or in the system log, call your
or in the optics or in the trasmit side on the
Cisco technical support representative and upstream link. If this is an OOB link please
provide the representative with the
reseat the cards on both ends of the link
gathered information.
one by one to try to fix the issue.

No action is required.

None.

No action is required.

None.

Collect all the event and console logs. Copy

the error message exactly as it appears on
the console or in the system log, call your Possible HW fault on board. Shutdown
Cisco technical support representative and affected plane associated with SM node.
provide the representative with the
Run online diags. Depending on results,
gathered information.
may need to RMA the node.

Collect all the event and console logs. Copy

the error message exactly as it appears on
the console or in the system log, call your Possible HW fault on board. Shutdown
Cisco technical support representative and affected plane associated with SM node.
provide the representative with the
Run online diags. Depending on results,
gathered information.
may need to RMA the node.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Collect all the event logs and 'sh controller

fabric trace driver all location <location of
the node>' Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

None

No action is required.

None

No action is required.

None

No action is required.

None

None

None

None

None

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.
No action is required.

None

No action is required.

None

No action is required.

None.

No action is required.

None.

No action is required.

None.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.
No action is required.

None.

No action is required.

None.

No action is required.

This is not an error message. Indicates the

reason for ASICs being reset.

No action is required.

This is not an error message. Indicates the

reason for ASICs being reset.

No action is required.

This is not an error message. Indicates the

reason for ASICs being reset.

No action is required.

None.

No action is required.

None.

No action is required.

None.

No action is required.

None.

No action is required.

None.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
None.
No action is required.
None.

If this condition is noticed for every access

to the ASIC, then the ASIC is possibly
wedged. Resetting the ASIC or reloading
the fabric card will help to recover from this
condition. Driver automatically tries
recovering the ASIC via PON reset. Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If this condition is noticed for every access

to the ASIC, then the ASIC is possibly
wedged. Resetting the ASIC or reloading
the fabric card will help to recover from this
condition. Driver automatically tries
recovering the ASIC via PON reset. Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

None.

None.

None.

None.

None.

None.

None.

None.

No action is required.

This is not an error message. This just

indicates that previously reported health
monitoring error has been cleared.

Check the admin plane configuration to

ensure that it corresponds with the actual
physical topology of the system. If this
configuration looks correct then contact
support, otherwise correct the
configuration and the system should
recover.

As mentioned in the explanation, this

message is printed when FSDB server
cannot provide topology information to the
sfe drvr because of the missing admin
configuration.

Check the admin plane configuration to

ensure that it corresponds with the actual
physical topology of the system. If this
configuration looks correct then contact
support, otherwise correct the
configuration and the system should
recover.

As mentioned in the explanation, this

message is printed when FSDB server
cannot provide topology information to the
sfe drvr because of the missing admin
configuration.

Check the admin plane configuration to

ensure that it corresponds with the actual
physical topology of the system. If this
configuration looks correct then contact
support, otherwise correct the
configuration and the system should
recover.

As mentioned in the explanation, this

message is printed when FSDB server
cannot provide topology information to the
sfe drvr because of the missing admin
configuration.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Replace the chassis.

Verify the chassis type.

The fabric ASICs are not powered up and

If the message recurs, copy the error
hence the driver continues to wait. This
message exactly as it appears on the
could be due to an I2C issue on the board.
console or in the system log, call your
Check the voltages on the board. Report
Cisco technical support representative and this to Engineering. Use Topic to search for
provide the representative with the
a similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Check the health of the shelfmgr process

on the dSC RP. If shelfmgr is healthy, and
the card cannot self reload, then reload the
card with the following command in admin
mode: 'hw shut loc y/SMx/sp', where x is
the SM module number that generated the
error, y is the rack that it is in. If manual
shutdown does not work, or if the error
recurs, call your Cisco technical support
representative and provide the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

An error occurred while the

sfe_superstar_drvr/sfe_drvr tries to connect
shut down the fabric card with a shelfmgr
API. This can be because shelfmgr was
restarting due to software install or
software error. This also can be control
ethernet, QSM, or OS level issues.

No action is required.

Needs to be investigated from ees side.

Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error occured while the sfe_drvr (fabric

asic driver) was initializing it's internal
state. This should be a transitory error. The
sfe_drvr process gets respawned
If the message recurs, copy the error
automatically by sysmgr. If the proecess
message exactly as it appears on the
does not get respawned automatically, try
console or in the system log, call your
restarting this process (sfe_drvr) manually.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

No action is required.

Needs to be investigated from ees side.

Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Needs to be investigated from ees side.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

No action is required.

This is an error message. SFE driver team

needs to investigate. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Check EES state, and fgid_server state.

Restarting both fgid_server and sfe_drvr
Capture the output of the CLIs as specified processes might help in recovering from
in required_info and contact your Cisco
this error. Collect the required_info and
technical support representative. Once the contact fabric & EES teams. Fabric wiki is
required information is captured, a restart located at
of sfe_drvr process on the affected fabric
http://zed.cisco.com/confluence/display/GS
card, followed by a restart of fgid_server
RTR/CRS+Fabric. EES wiki is location at
process on the appropriate RP/DRP can be http://wiki-eng.cisco.com/engwiki/CRS-MCattempted to recover from this error.
EES-PROJECT

Capture information as specified in the

required_info section. Restart sfe_drvr to
clear any out of sync issues.

Capture memory usage information on the

node on which this message was logged.
Collect the required_info and contact fabric
team. Fabric wiki is located at
http://zed.cisco.com/confluence/display/GS
RTR/CRS+Fabric.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

There is no specific manual intervention

needed to be taken by the customer for
this message. As mentioned in the
explanation, SFE driver will try to recover
from this situation on its own. However, if
this message is being seen often, then
please capture the output of the CLIs
mentioned in the required_info, and
contact Cisco technical support
representative.

Check EES state, and fgid_server state.

Restarting both fgid_server and sfe_drvr
processes might help in recovering from
this error. Collect the required_info and
contact fabric & EES teams. Fabric wiki is
located at
http://zed.cisco.com/confluence/display/GS
RTR/CRS+Fabric. EES wiki is location at
http://wiki-eng.cisco.com/engwiki/CRS-MCEES-PROJECT

No action is required.

This indicates there is an issue with ltrace

infrastructure. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

No action is required.

This is not an error message. Indicates the

reason for ASICs being reset.

No action is required.

This is informational message. No action

required.

No action is required.

This is informational message; no action

required.

Check the EEPROM programming,

environmental condition and the type of
board that is inserted.

Check the EEPROM programming,

environmental condition and the type of
board that is inserted. Run diags and verify
i2c bus is working fine; Also we need to
check whether platform libraries are linked
properly.

No action is required.

This is not an error message. Indicates an

FDI request to reset the ASICs has been
received.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

*SUPPORT*

Search the event logs for events/errors

related to the failure reason. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

The System Manager process (sysmgr) will

automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. Verify that the
fabricq_mgr driver is up and running by
executing the following command at the
CLI of the active RP: 'show process
fabricq_mgr location <location>' If it is still
non-operational, enable the following
debugs of the fabricq_mgr driver process:
error Errors in the driver fatal Fatal errors
which cause driver to exit info All
informational events init Initialization
events and restart the driver by executing
the following command at the CLI of the
active RP: 'process restart fabricq_mgr
location <location>' If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. SysDB failures
are part of the overall system. If there are
failures here then other processes may also
exhibit similar problems. Pls decode the
traceback and see if there code/dll that is
reporting the error. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Examine logs to determine if the

fabricq_mgr process crashes and collect
relevant crash info. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Search the event logs for events/errors

related to the failure reason. Examine logs
to determine if the fabricq_mgr process
crashes and collect relevant crash info.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This could conceivably indicate hardware

problems, would need further investigation
from H/w PoV.. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This message is seen when CAI / CCI / RCC

DLL library returned an error code. Any
debugging information from DLL API library
will likely be useful. The output of the
syslog error messages will provide details
of problem Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This message is seen when CAI / CCI / RCC

DLL library returned an error code. Any
debugging information from DLL API library
will likely be useful. The output of the
syslog error messages will provide details
of problem Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This message is seen when CAI / RCC DLL

library returned an error code. Any
debugging information from DLL API library
will likely be useful. The output of the
syslog error messages will provide details
of problem Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This message is seen when CAI / RCC DLL

library returned an error code. Any
debugging information from DLL API library
will likely be useful. The output of the
syslog error messages will provide details
of problem Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This could conceivably indicate hardware

problems, need further investigation.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This could conceivably indicate hardware

problems, need further investigation.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check the logs to identify whether

hardware or software error. If the output
message indicated this is a hardware
access error, software will have
automatically taken action to recover from
the error. If harware access error does not
recur, no other action is required.
Otherwise, Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check the logs to identify whether

hardware or software error. If the output
message indicated this is a hardware
access error, software will have
automatically taken action to recover from
the error. If harware access error does not
recur, no other action is required.
Otherwise, Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

If the issue persists, Copy the error

message exactly as it appears on the
Search the event logs for events/errors
console or in the system log, call your
related to the failure reason. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

*SUPPORT*

These FCRAM errors are usually due to

hardware issue with the card. If FCRAM
error is observed, it is recommended to
shut down the card that reported the error
and observe the behaviour. This helps to
identify if the card is faulty one. If the
FCRAM error is seen consistent on the
reported card, then the hardware may
need to be RMAed.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

This indicates a bad hardware. It is

recommended to shut down the card that
If the message recurs, copy the error
reported the error and observe the
message exactly as it appears on the
behaviour. This helps to identify if the card
console or in the system log, call your
is faulty one. If the nodes comes up fine
Cisco technical support representative and after reload, watch for recurrence. If node
provide the representative with the
doesn't come-up or diags fails or seeing
gathered information.
BIST error recurrs, RMA the card.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Unlikely we see this message. This error

message indicates debug infra initialization
went wrong during system bootup. No
other action is required. Otherwise, Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Unlikely we see this message. This error

message indicates debug infra initialization
went wrong during system bootup. No
other action is required. Otherwise, Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Unlikely we see this message. This error

message indicates debug infra initialization
went wrong during system bootup. No
other action is required. Otherwise, Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Unlikely we see this message. This error

message indicates debug infra initialization
went wrong during system bootup. No
other action is required. Otherwise, Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This message is seen when the CCI ASIC

library has informed the FQM process that
an error occured while it was trying to
perform a DMA transfer. As such, any
debugging information regarding the state
will likely be useful when debugging this
problem. If the hardware error does not
stop and persist, it is likely the hardware
has become defective and the replacement
of the board is required. Otherwise, Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This message is seen when the CCI ASIC

library has informed the FQM process that
an error occured while it was trying to
perform a DMA transfer. As such, any
debugging information regarding the state
will likely be useful when debugging this
problem. If the hardware error does not
stop and persist, it is likely the hardware
has become defective and the replacement
of the board is required. Otherwise, Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

The System Manager process (sysmgr) will

automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. Verify that the
fabricq_mgr driver is up and running by
executing the following command at the
CLI of the active RP: 'admin show process
fabricq_mgr location <location>' If it is still
non-operational, enable the following
debugs of the fabricq_mgr driver process:
error Errors in the driver fatal Fatal errors
which cause driver to exit info All
informational events init Initialization
events and restart the driver by executing
the following command at the CLI of the
active RP: 'admin process restart
fabricq_mgr location <location>' If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

*SUPPORT*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

*SUPPORT*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

*SUPPORT*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

*SUPPORT*

Indicates that a cell had to be dropped in

the PCL block of the FabricQ ASIC because
the cell count from the cell header
mismatches with the cells that arrived for
the same packet. This can be caused by
Cell corruptions at any of the Fabric SM
cards or the Ingressq in the router. Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

*SUPPORT*

Cells had arrived in the PCL block of the

sponge asic from the Fabric Interface block
without 4 clocks apart which is an illegal
condition. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

*SUPPORT*

Indicates that during reassembly in the PCL

block of the Sponge ASIC, it was discovered
that one or more Unicast Packets were lost
elsewhere in the system. This could be a
sign of data loss in upstream of Sponge. So
review of error information from other
ASICs is recommded. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

*SUPPORT*

This indicates that a cell had to be dropped

in the PCL block of the FabricQ ASIC
because more cells arrived for a packet
than were expected. This can be caused by
Cell corruptions at any of the Fabric SM
cards or the Ingressq in the router. Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Run diags on the board. Refer to EDCSprovide the representative with the
300400 to find the reason and impact of
gathered information.
the interrupt see in the IOS message.

If these messages continue for more than 2

minutes, with incrementing uncorrectable
error (UCE) counters, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

*SUPPORT*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

*SUPPORT*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

*SUPPORT*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

*SUPPORT*

This could conceivably indicate hardware

problems, need further investigation.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

*SUPPORT*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the error persists, please contact TAC

suppport.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

*SUPPORT*

--

*SUPPORT*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the problem persists, Copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative
provide the representative with the
gathered information.

There was a problem programming one or

more interface queues within the Fabricq
asic. This can be caused by a low memory
situation, or can be caused by a problem in
communication between the driver process
and and the asic itself. Restarting the driver
might help, or at the worst case rebooting
the LC itself should solve the problems.

*SUPPORT*

--

If the problem persists, *SUPPORT*

--

No action is required.

--

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

In one of the persistent storage devices

(harddisk:/, disk0: etc.) on the DSC's RP
that was active at the time the message
was emitted, a file may have been created
under a directory called asic_snapshots/ for
this occurrence. The name is of the format
'sponge_debug_snapshot.node<rack>_<sl
og>_CPU0.<[first/latest]>' Collect that file
if present and save it to the case.
-*SUPPORT*

--

If these messages are recurring and/or

you're seeing other faults (such as traffic
loss) then contact your support agent.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

*SUPPORT*

--

This message is seen when the SQUID ASIC

If the issue persists, Copy the error
library has informed the FQM process that
message exactly as it appears on the
an error occured while it was trying to
console or in the system log, call your
perform a DMA transfer. As such, any
Cisco technical support representative and debugging information regarding the squid
provide the representative with the
state will likely be useful when debugging
gathered information.
this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
FDI encountered an internal software error.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
FDI encountered an internal software error.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Capture information as specified in the

required_info section. Restart
FSDB/appropriate driver (from whichever
process context this error message was
logged) to clean any 'out of sync' issues.

FDI encountered an internal software error.

Collect the required info and log a bug
against hfr-fabric.

Capture information as specified in the

required_info section. Restart
FSDB/appropriate driver (from whichever
process context this error message was
logged) to clear any 'out of sync' issues.

FDI encountered an internal software error.

Collect the required info and log a bug
against hfr-fabric.

No action required Copy the error message

exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

The process lpts_pa will attempt to recover

by restarting. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

The process lpts_pa will attempt to recover

by retrying the operation. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
The BCDL Consumer may need restarting if
gathered information.
the errors persist.

If the message recurs, copy the error

message exactly as it appears on the
The FGID BCDL consumer may need
console or in the system log, call your
restarting if the errors persist. Report this
Cisco technical support representative and to Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
The FGID BCDL consumer may need
console or in the system log, call your
restarting if the errors persist. Report this
Cisco technical support representative and to Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Whenever this happens, fgid_server will

dump a core file. No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Check the startup arguments passed to

FGID-DB. A default configuration will be
used if no parameters are passed. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Valid arguments are: server_id - A number
provide the representative with the
greater or equal to 0 and less than
gathered information.
maximum number of HFR racks supported

If the message recurs, copy the error

message exactly as it appears on the
If 'Initial Full Download is still in progress
console or in the system log, call your
for one/more clients' is seen it means after
Cisco technical support representative and a certain number of retries, some of the
provide the representative with the
clients haven't completed the Initial Full
gathered information.
Download.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
The FGID server may need restarting if the
console or in the system log, call your
errors persist. Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

None. If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and none. Report this to Engineering. Use Topic
provide the representative with the
to search for a similar DDTS. If you find
gathered information.
none, write a DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
(sysmgr) will automatically respawn the
fia_drvr process. If the error persists, the
FIA driver will be respawned a system-wide
pre-configured number of times. This preconfigured number along with a policy for
None. If the message recurs, copy the error the action to be taken following a threshold
message exactly as it appears on the
number of fia driver respawns is set as a
console or in the system log, call your
system configuration. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
(sysmgr) will automatically respawn the
fia_drvr process. If the error persists, the
FIA driver will be respawned a system-wide
pre-configured number of times. This preconfigured number along with a policy for
None. If the message recurs, copy the error the action to be taken following a threshold
message exactly as it appears on the
number of fia driver respawns is set as a
console or in the system log, call your
system configuration. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
(sysmgr) will automatically respawn the
The driver will escalate the error to the
fia_drvr process. If the error persists, the
Fault Management (FM) entity for further
FIA driver will be respawned a system-wide
action. Verify that the driver will recover
pre-configured number of times. This prefollowing action by the FM. If the message configured number along with a policy for
recurs, copy the error message exactly as it the action to be taken following a threshold
appears on the console or in the system
number of fia driver respawns is set as a
log, call your Cisco technical support
system configuration. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
(sysmgr) will automatically respawn the
The driver will escalate the error to the
fia_drvr process. If the error persists, the
Fault Management (FM) entity for further
FIA driver will be respawned a system-wide
action. Verify that the driver will recover
pre-configured number of times. This prefollowing action by the FM. If the message configured number along with a policy for
recurs, copy the error message exactly as it the action to be taken following a threshold
appears on the console or in the system
number of fia driver respawns is set as a
log, call your Cisco technical support
system configuration. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
(sysmgr) will automatically respawn the
The driver will escalate the error to the
fia_drvr process. If the error persists, the
Fault Management (FM) entity for further
FIA driver will be respawned a system-wide
action. Verify that the driver will recover
pre-configured number of times. This prefollowing action by the FM. If the message configured number along with a policy for
recurs, copy the error message exactly as it the action to be taken following a threshold
appears on the console or in the system
number of fia driver respawns is set as a
log, call your Cisco technical support
system configuration. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
(sysmgr) will automatically respawn the
The driver will escalate the error to the
fia_drvr process. If the error persists, the
Fault Management (FM) entity for further
FIA driver will be respawned a system-wide
action. Verify that the driver will recover
pre-configured number of times. This prefollowing action by the FM. If the message configured number along with a policy for
recurs, copy the error message exactly as it the action to be taken following a threshold
appears on the console or in the system
number of fia driver respawns is set as a
log, call your Cisco technical support
system configuration. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
(sysmgr) will automatically respawn the
The driver will escalate the error to the
fia_drvr process. If the error persists, the
Fault Management (FM) entity for further
FIA driver will be respawned a system-wide
action. Verify that the driver will recover
pre-configured number of times. This prefollowing action by the FM. If the message configured number along with a policy for
recurs, copy the error message exactly as it the action to be taken following a threshold
appears on the console or in the system
number of fia driver respawns is set as a
log, call your Cisco technical support
system configuration. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
(sysmgr) will automatically respawn the
The driver will escalate the error to the
fia_drvr process. If the error persists, the
Fault Management (FM) entity for further
FIA driver will be respawned a system-wide
action. Verify that the driver will recover
pre-configured number of times. This prefollowing action by the FM. If the message configured number along with a policy for
recurs, copy the error message exactly as it the action to be taken following a threshold
appears on the console or in the system
number of fia driver respawns is set as a
log, call your Cisco technical support
system configuration. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
(sysmgr) will automatically respawn the
fia_drvr process. If the error persists, the
FIA driver will be respawned a system-wide
Verify that the driver will recover following pre-configured number of times. This preaction by the FM. If the message recurs,
configured number along with a policy for
copy the error message exactly as it
the action to be taken following a threshold
appears on the console or in the system
number of fia driver respawns is set as a
log, call your Cisco technical support
system configuration. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
(sysmgr) will automatically respawn the
fia_drvr process. If the error persists, the
FIA driver will be respawned a system-wide
pre-configured number of times. This preconfigured number along with a policy for
None. If the message recurs, copy the error the action to be taken following a threshold
message exactly as it appears on the
number of fia driver respawns is set as a
console or in the system log, call your
system configuration. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
(sysmgr) will automatically respawn the
fia_drvr process. If the error persists, the
FIA driver will be respawned a system-wide
pre-configured number of times. This preconfigured number along with a policy for
None. If the message recurs, copy the error the action to be taken following a threshold
message exactly as it appears on the
number of fia driver respawns is set as a
console or in the system log, call your
system configuration. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
Collect all the event logs and the output of (sysmgr) will automatically respawn the
the following commands executed from the fia_drvr process. If the error persists, the
CLI of the active RP: 1. 'show process
FIA driver will be respawned a system-wide
fia_drvr location <loc>' 2. 'show controllers pre-configured number of times. This prefia trace all location <loc>' If the message configured number along with a policy for
recurs, copy the error message exactly as it the action to be taken following a threshold
appears on the console or in the system
number of fia driver respawns is set as a
log, call your Cisco technical support
system configuration. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

Refer to the description in field for this

error. Check the FIA driver behavior is
consistent with the FM guidelines defined
for this error type. This error isn't normally
persistent and should recover due to the
action taken by the fault management
entity. Should this error remains, despite
FM action, manually respawn the fia_drvr
process. The System Manager process
(sysmgr) will automatically respawn the
fia_drvr process. If the error persists, the
FIA driver will be respawned a system-wide
pre-configured number of times. This preconfigured number along with a policy for
None. If the message recurs, copy the error the action to be taken following a threshold
message exactly as it appears on the
number of fia driver respawns is set as a
console or in the system log, call your
system configuration. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Collect all the event logs and the output of

the following commands executed from the
CLI of the active RP: 1. 'show process
fia_drvr location <loc>' 2. Collect the
Broadcom ltraces: pkg/bin/fia_show_ltrace
-S If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and none. Report this to Engineering. Use Topic
provide the representative with the
to search for a similar DDTS. If you find
gathered information.
none, write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

The board would get reloaded. On reload of

board, run following commands from RSP
ksh to decode PCDS information pcds_decode -c FIA <.pcds file>
pcds_decode -c PFM_NODE <.pcds file>. If
users has auto reset option disabled in
admin config, then the board would not get
reloaded on its own. At this stage collect
the output of 'show asic-errors fia <inst>
all location <loc>'.

On reload of box, run following commands

from RSP ksh to decode PCDS information pcds_decode -c FIA pcds_decode -c
PFM_NODE .

This condition could be result of bad

seating of linecards or route processor
cards. Ensure cards are seated properly.
Wait a few minutes. If it doesn't recover,
This condition could occur due to broken
please reload the board using command
pins/components that connect into
'reload location <>'. If the message recurs, backplane. If hardware is inspected to be
copy the error message exactly as it
clean and no physical damage,
appears on the console or in the system
environmental factors like temperature
log, call your Cisco technical support
might be factor for this error. Wait and
representative and provide the
check if errors get resolved. If errors are
representative with the gathered
consistent, take actions like checking
information.
temperature of the box, if high address it.

This condition could be result of bad

seating of linecards or route processor
cards. Ensure cards are seated properly.
Wait a few minutes. If it doesn't recover,
This condition could occur due to broken
please reload the board using command
pins/components that connect into
'reload location <>'. If the message recurs, backplane. If hardware is inspected to be
copy the error message exactly as it
clean and no physical damage,
appears on the console or in the system
environmental factors like temperature
log, call your Cisco technical support
might be factor for this error. Wait and
representative and provide the
check if errors get resolved. If errors are
representative with the gathered
consistent, take actions like checking
information.
temperature of the box, if high address it.

This condition could be result of bad

seating of linecards or route processor
cards. Ensure cards are seated properly.
Wait a few minutes. If it doesn't recover,
This condition could occur due to broken
please reload the board using command
pins/components that connect into
'reload location <>'. If the message recurs, backplane. If hardware is inspected to be
copy the error message exactly as it
clean and no physical damage,
appears on the console or in the system
environmental factors like temperature
log, call your Cisco technical support
might be factor for this error. Wait and
representative and provide the
check if errors get resolved. If errors are
representative with the gathered
consistent, take actions like checking
information.
temperature of the box, if high address it.

This condition could be result of bad

seating of linecards or route processor
cards. Ensure cards are seated properly.
Wait a few minutes. If it doesn't recover,
This condition could occur due to broken
please reload the board using command
pins/components that connect into
'reload location <>'. If the message recurs, backplane. If hardware is inspected to be
copy the error message exactly as it
clean and no physical damage,
appears on the console or in the system
environmental factors like temperature
log, call your Cisco technical support
might be factor for this error. Wait and
representative and provide the
check if errors get resolved. If errors are
representative with the gathered
consistent, take actions like checking
information.
temperature of the box, if high address it.

Reboot the board. If the error persists,

contact TAC. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

Reboot the board. If the error persists,

contact TAC. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Wait and check if software handles the

fault by taking relevant recovery actions.
Examples of recovery actions include (re
init components, reload LC etc). If error
persists, then collection required info and
manually reload LC.,

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could be result of bad

seating of linecards, fabric cards or route
processor cards. Ensure cards are seated
properly. This condition could occur due to
broken pins/components that connect into
backplane. If hardware is inspected to be
clean and no physical damage,
environmental factors like temperature
might be factor for this error. Wait and
check if errors get resolved. If errors are
consistent, take actions like checking
temperature of the box, if high address it.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could be result of bad

seating of linecards, fabric cards or route
processor cards. Ensure cards are seated
properly. This condition could occur due to
broken pins/components that connect into
backplane. If hardware is inspected to be
clean and no physical damage,
environmental factors like temperature
might be factor for this error. Wait and
check if errors get resolved. If errors are
consistent, take actions like checking
temperature of the box, if high address it.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could be result of bad

seating of linecards, fabric cards or route
processor cards. Ensure cards are seated
properly. This condition could occur due to
broken pins/components that connect into
backplane. If hardware is inspected to be
clean and no physical damage,
environmental factors like temperature
might be factor for this error. Wait and
check if errors get resolved. If errors are
consistent, take actions like checking
temperature of the box, if high address it.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could be result of bad

seating of linecards, fabric cards or route
processor cards. Ensure cards are seated
properly. This condition could occur due to
broken pins/components that connect into
backplane. If hardware is inspected to be
clean and no physical damage,
environmental factors like temperature
might be factor for this error. Wait and
check if errors get resolved. If errors are
consistent, take actions like checking
temperature of the box, if high address it.

This condition could occur due to broken

pins/components/clock or ASIC init errors
Wait a few minutes. If it doesn't recover,
(either NPU or FIA init errors). If hardware is
please reload the board using command
inspected to be clean and no physical
'reload location <>'. If the message recurs, damage, environmental factors like
copy the error message exactly as it
temperature might be factor for this error.
appears on the console or in the system
Wait and check if errors get resolved. If
log, call your Cisco technical support
errors are consistent, take actions like
representative and provide the
checking temperature of the box, if high
representative with the gathered
address it. Check for any initialization
information.
errors.

This condition could occur due to broken

pins/components/clock or ASIC init errors
Wait a few minutes. If it doesn't recover,
(either NPU or FIA init errors). If hardware is
please reload the board using command
inspected to be clean and no physical
'reload location <>'. If the message recurs, damage, environmental factors like
copy the error message exactly as it
temperature might be factor for this error.
appears on the console or in the system
Wait and check if errors get resolved. If
log, call your Cisco technical support
errors are consistent, take actions like
representative and provide the
checking temperature of the box, if high
representative with the gathered
address it. Check for any initialization
information.
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could be result of bad

seating of linecards, fabric cards or route
processor cards. Ensure cards are seated
properly. This condition could occur due to
broken pins/components that connect into
backplane. If hardware is inspected to be
clean and no physical damage,
environmental factors like temperature
might be factor for this error. Wait and
check if errors get resolved. If errors are
consistent, take actions like checking
temperature of the box, if high address it.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could be result of bad

seating of linecards, fabric cards or route
processor cards. Ensure cards are seated
properly. This condition could occur due to
broken pins/components that connect into
backplane. If hardware is inspected to be
clean and no physical damage,
environmental factors like temperature
might be factor for this error. Wait and
check if errors get resolved. If errors are
consistent, take actions like checking
temperature of the box, if high address it.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could be result of bad

seating of linecards, fabric cards or route
processor cards. Ensure cards are seated
properly. This condition could occur due to
broken pins/components that connect into
backplane. If hardware is inspected to be
clean and no physical damage,
environmental factors like temperature
might be factor for this error. Wait and
check if errors get resolved. If errors are
consistent, take actions like checking
temperature of the box, if high address it.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could be result of bad

seating of linecards, fabric cards or route
processor cards. Ensure cards are seated
properly. This condition could occur due to
broken pins/components that connect into
backplane. If hardware is inspected to be
clean and no physical damage,
environmental factors like temperature
might be factor for this error. Wait and
check if errors get resolved. If errors are
consistent, take actions like checking
temperature of the box, if high address it.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could be result of bad

seating of linecards, fabric cards or route
processor cards. Ensure cards are seated
properly. This condition could occur due to
broken pins/components that connect into
backplane. If hardware is inspected to be
clean and no physical damage,
environmental factors like temperature
might be factor for this error. Wait and
check if errors get resolved. If errors are
consistent, take actions like checking
temperature of the box, if high address it.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could be result of bad

seating of linecards, fabric cards or route
processor cards. Ensure cards are seated
properly. This condition could occur due to
broken pins/components that connect into
backplane. If hardware is inspected to be
clean and no physical damage,
environmental factors like temperature
might be factor for this error. Wait and
check if errors get resolved. If errors are
consistent, take actions like checking
temperature of the box, if high address it.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could be result of bad

seating of linecards, fabric cards or route
processor cards. Ensure cards are seated
properly. This condition could occur due to
broken pins/components that connect into
backplane. If hardware is inspected to be
clean and no physical damage,
environmental factors like temperature
might be factor for this error.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could be result of bad

seating of linecards, fabric cards or route
processor cards. Ensure cards are seated
properly. This condition could occur due to
broken pins/components that connect into
backplane. If hardware is inspected to be
clean and no physical damage,
environmental factors like temperature
might be factor for this error. Wait and
check if errors get resolved. If errors are
consistent, take actions like checking
temperature of the box, if high address it.

Verify correct version of Punt/Bridge FPGA

is loaded. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Environmental factors like temperature

might cause this error. Wait and check if
errors get resolved. If errors are consistent,
take actions like checking temperature of
the box, if high address it.

Verify correct version of Punt/Bridge FPGA

is loaded. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Environmental factors like temperature

might cause this error. Wait and check if
errors get resolved. If errors are consistent,
take actions like checking temperature of
the box, if high address it.

Verify correct version of Punt/Bridge FPGA

is loaded. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Environmental factors like temperature

might cause this error. Wait and check if
errors get resolved. If errors are consistent,
take actions like checking temperature of
the box, if high address it.

Verify correct version of Punt/Bridge FPGA

is loaded. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Environmental factors like temperature

might cause this error. Wait and check if
errors get resolved. If errors are consistent,
take actions like checking temperature of
the box, if high address it.

Verify correct link serdes error Wait a few

minutes. If it doesn't recover, please reload
the board using command 'reload location
<>'. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Collect link status and link errors between

NP/MUX and FIA Environmental factors like
temperature might cause this error. Wait
and check if errors get resolved. If errors
are consistent, take actions like checking
temperature of the box, if high address it.

Verify correct link serdes error Wait a few

minutes. If it doesn't recover, please reload
the board using command 'reload location
<>'. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Environmental factors like temperature

might cause this error. Collect link status
and link errors between NP/MUX and FIA
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's ET module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's ET module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's ET module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's ET module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's ET module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's ET module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's ET module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's ET module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's ET module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's ET module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's ET module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's ET module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from NP into FIA. Check links
connecting FIA and NP are clean and in
working status. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from NP into FIA. Check links
connecting FIA and NP are clean and in
working status. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from NP into FIA. Check links
connecting FIA and NP are clean and in
working status. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

component/clock or ASIC init errors (either
NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

component/clock or ASIC init errors (either
NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

component/clock or ASIC init errors (either
NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

component/clock or ASIC init errors (either
NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from NP into FIA. Check links
connecting FIA and NP are clean and in
working status. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from NP into FIA. Check links
connecting FIA and NP are clean and in
working status. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from NP into FIA. Check links
connecting FIA and NP are clean and in
working status. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from NP into FIA. Check links
connecting FIA and NP are clean and in
working status. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from NP into FIA. Check links
connecting FIA and NP are clean and in
working status. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from NP into FIA. Check links
connecting FIA and NP are clean and in
working status. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's PW module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's PW module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's PW module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's PW module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's PW module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's PW module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition indicate malformation of

packet either in the upstream or during
transfer from FIA upstream modules to
FIA's PW module. Check/wait to see if the
condition is transient. Check for any ASIC
related errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia
check if memmory ASICs/components
associated with FIA are inited and
functioning.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. This condition could occur due
to broken pins/components/clock or ASIC
init errors (either NPU or FIA init errors). If
hardware is inspected to be clean and no
physical damage, environmental factors
like temperature might be factor for this
error. Wait and check if errors get resolved.
If errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.
--

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

pins/components/clock or ASIC init errors
(either NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

This condition could occur due to broken

component/clock or ASIC init errors (either
Wait a few minutes. If it doesn't recover,
NPU or FIA init errors). If hardware is
please reload the board using command
inspected to be clean and no physical
'reload location <>'. If the message recurs, damage, environmental factors like
copy the error message exactly as it
temperature might be factor for this error.
appears on the console or in the system
Wait and check if errors get resolved. If
log, call your Cisco technical support
errors are consistent, take actions like
representative and provide the
checking temperature of the box, if high
representative with the gathered
address it. Check for any initialization
information.
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

component/clock or ASIC init errors (either
NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

component/clock or ASIC init errors (either
NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This condition could occur due to broken

component/clock or ASIC init errors (either
NPU or FIA init errors). If hardware is
inspected to be clean and no physical
damage, environmental factors like
temperature might be factor for this error.
Wait and check if errors get resolved. If
errors are consistent, take actions like
checking temperature of the box, if high
address it. Check for any initialization
errors.

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Wait a few minutes. If it doesn't recover,

please reload the board using command
'reload location <>'. Make sure board is
seated properly. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Internal module error within FIA Asic. We

need to check if other kind of errors
occurred along with this error. Check asicerror logging using show asic-error fia

Check for other failures like online diags.

Reload the board to see if the error goes
away. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Environmental factors like temperature

might cause this error. Wait and check if
errors get resolved. If errors are consistent,
take actions like checking temperature of
the box, if high address it.

Check if board is reporting temperature

alarm. If not, it is due to Crossbar fabric
interface heatsink not being installed
properly. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Wait and check if errors get resolved. If

errors are consistent, take actions like
checking fan tray are functioning and are
running at right speed.

Check if board is reporting temperature

alarm. If not, it is due to Crossbar fabric
interface heatsink not being installed
properly. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Wait and check if errors get resolved. If

errors are consistent, take actions like
checking fan tray are functioning and are
running at right speed.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
This is most likely a software bug. Report
Cisco technical support representative and this to Engineering. Use Topic to search for
provide the representative with the
a similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
This is most likely a software bug. Report
Cisco technical support representative and this to Engineering. Use Topic to search for
provide the representative with the
a similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If there are other error reports about the

switch fabric (CSC/SFC) then wait atleast 3
minutes for corrective action. Otherwise,
run diagnostics for slot reporting error. If
the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

A hardware error. No ddts need be filed. If

the recovery is successful, this error can be
treated as transient error, else if the error
persists run diagnostics to determine the
source of failure. The error if persistent
indicates a hardware fault on the LC.

If there are other error reports about the

switch fabric (CSC/SFC) then wait atleast 3
minutes for corrective action. Otherwise,
run diagnostics for slot reporting error. If
the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

A hardware error. No ddts need be filed. If

the recovery is successful, this error can be
treated as transient error, else if the error
persists run diagnostics to determine the
source of failure. The error if persistent
indicates a hardware fault on the LC.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Collect the required information indicated

below. Also, run the field diags and the
health check. If the health check or diags
fail, then initiate the RMA process. Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The link will now be unusable and the

board upon which it is located may need to
be reloaded. If the condition persists, it
may indicate faulty hardware.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Restart the process using the CLI in exec

mode - process restart fiarsp If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This is an initialization error. Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Restart the process using the CLI in exec

mode - process restart fiarsp If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This is an initialization error. Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Verify that the fia_driver is up and running

by executing the following command at the
CLI of the active RP: 'show process
fia_driver location < >' If it is still nonoperational, enable the following debugs of
the FIA driver process: eio All EIO library
events error Errors in the driver fatal Fatal
errors which cause driver to exit info All
informational events init Initialization
events Restart the driver by executing the
following command at the CLI of the active
RP: process restart fia_driver loc <loc> If
the problem persists, this could be
indicative of a hardware failure and it is
recommended to run the field diagnostics
on the failing MSC.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
overall system. If there are failures here
then other processes may also exhibit
similar problems. If the health check or
diags fail, then initiate the RMA process.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Possible memory leak in the system or a

hardware malfunction or minimum memory
requirements not fulfilled. Ensure
Run the debug show commands, gather
recommended minimum memory is
data and contact tac. Also ensure the LC is present. Run Diagnostics to rule out or
populated with the minimum amount of
confirm hardware failure. Reload the LC
memory required for proper operation. If
using 'hw-module' command to clear out
the message recurs, copy the error
low memeory condition due to memory
message exactly as it appears on the
leak. also refer to: http://wwwinconsole or in the system log, call your
eng.cisco.com/Eng/OIBU/WWW/Q/India/me
Cisco technical support representative and mory/memory_CLI.txt and http://wwwinprovide the representative with the
eng.cisco.com/Eng/OIBU/WWW/Q/India/shm
gathered information.
win/shared_memory_window.html

Possible memory leak in the system or a

hardware malfunction or minimum memory
requirements not fulfilled. Ensure
Run the debug show commands, gather
recommended minimum memory is
data and contact tac. Also ensure the LC is present. Run Diagnostics to rule out or
populated with the minimum amount of
confirm hardware failure. Reload the LC
memory required for proper operation. If
using 'hw-module' command to clear out
the message recurs, copy the error
low memeory condition due to memory
message exactly as it appears on the
leak. also refer to: http://wwwinconsole or in the system log, call your
eng.cisco.com/Eng/OIBU/WWW/Q/India/me
Cisco technical support representative and mory/memory_CLI.txt and http://wwwinprovide the representative with the
eng.cisco.com/Eng/OIBU/WWW/Q/India/shm
gathered information.
win/shared_memory_window.html

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

The board on which the ASIC is located

may need to be reloaded. If the condition
persists, it may indicate faulty hardware.
Additional link information may be
collected to aid in the localization of the
problem. Firstly we need to identify the
affected links. The requires some
understanding of the connectivity of the
FIA to the fabric ASICs. Each MSC includes
Collect the required information indicated 2 FIA ASIC devices. Each of the FIA
below. Also, run the field diags and the
comprise of two transmit slices. Each slice
health check. If the health check or diags is partitioned into two UQuads with each of
fail, then initiate the RMA process. Copy
the UQuads providing support for four
the error message exactly as it appears on links. So, given a transmit slice number the
the console or in the system log, call your associated plane number may be
Cisco technical support representative and determined. From the plane number, the
provide the representative with the
state of the connected fabric links may be
gathered information.
monitored.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Please collect the information specified in

required_info section. Verify that the
fia_driver is up and running by executing
the following command at the CLI of the
active RP: 'show process fia_driver location
<loc>' If it is still non-operational, enable
the following debugs of the FIA driver
process: eio All EIO library events error
Errors in the driver fatal Fatal errors which
cause driver to exit info All informational
events init Initialization events Restart the
driver by executing the following command
at the CLI of the active RP: process restart
fia_driver loc <loc>

Search the event logs for events/errors

related to the shelfmgr. This could be a
timing issue between fia driver and
shelfmgr. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

If there are other error reports about the

switch fabric (CSC/SFC) then wait several
minutes for corrective action. Otherwise,
run diagnostics for slot reporting error. If
the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

A hardware error. No ddts need be filed. If

the recovery is successful, this error can be
treated as transient error, else if the error
persists run diagnostics to determine the
source of failure. The error if persistent
indicates a hardware fault on the LC.

If there are other error reports about the

switch fabric (CSC/SFC) then wait several
minutes for corrective action. Otherwise,
run diagnostics for slot reporting error.

A hardware error. No ddts need be filed. If

the recovery is successful, this error can be
treated as transient error, else if the error
persists run diagnostics to determine the
source of failure. The error if persistent
indicates a hardware fault on the LC.

Wait atleast 3 minutes for corrective action Hardware access issue, indicates a major
to occur. Look for error reports about the
failure on the LC, run diagnostics to narrow
switch fabric (CSC/SFC.)
down the source of error.

Wait several minutes for corrective action

to occur. Ignore repeats of this error while
corrective action is taking place. Look for
error reports about the switch fabric
(CSC/SFC.) If the cards are disabled, try the
following 1. Ensure firmware running on all
the cards are upto date. 2. Run field
diagnostics on the card that is facing
problem. 3. Take out the card and insert in
a new slot to check if problem persists.

A hardware error. No ddts need be filed. If

the recovery is successful, this error can be
treated as transient error, else if the error
persists run diagnostics to determine the
source of failure. The error if persistent
indicates a hardware fault on the LC.
Remove the LC and reinsert in another slot
in the chassis to rule out contact issues.

Wait atleast 3 minutes for corrective action

to occur. Ignore repeats of this error while
corrective action is taking place. Look for
error reports about the switch fabric
(CSC/SFC.) If errors persist, you can try
moving the card to another slot. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

A hardware error. No ddts need be filed. If

the recovery is successful, this error can be
treated as transient error, else if the error
persists run diagnostics to determine the
source of failure. The error if persistent
indicates a hardware fault on the LC.
Remove the LC and reinsert in another slot
in the chassis to rule out contact issues.

Restart the fiad process on the LC. If the

error persists, reload the LC using 'hwmodule' command.

An occasional alarm can be ignored but if

the frequency of this error increases, it
could indicate a problem with the OS kernel
of the card or a hardware problem. Please
run diagnostics. If no failure is detected log
a DDTS with the message and following
show commands. show processes fctl show
processes fiad location X/X/X show
controllers fia location X/X/X show
controllers fia register location X/X/X

None, this is a transient error and can be

safely ignored. However multiple
occurrences of this error indiactes a
software problem. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

A software bug in all probability. This

indicates an error in the software that is
queuing packets to the fabric interface
ASIC, typically the queing ASIC on the
c12000 or the packet is received from the
line card CPU with slot mask as zero in the
header. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Wait atleast 3 minutes for corrective action

to occur. Ignore repeats of this error while
corrective action is taking place. Look for
error reports about the switch fabric
(CSC/SFC.) If errors persist, you can try
moving the card to another slot. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

A hardware error. No ddts need be filed. If

the recovery is successful, this error can be
treated as transient error, if the error
persists run diagnostics to determine the
source of failure. The error if persistent
indicates a hardware fault on the LC.
Remove the LC and reinsert in another slot
in the chassis to rule out contact issues.

Wait atleast 3 minutes for corrective action

to occur. Ignore repeats of this error while
corrective action is taking place. Look for
error reports about the switch fabric
(CSC/SFC.) If errors persist, you can try
moving the card to another slot. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

A hardware error. No ddts need be filed. If

the recovery is successful, this error can be
treated as transient error, else if the error
persists, physically remove the LC from the
chassis and reseat in a different slot. If
failure still persists, run diagnostics.

Wait atleast 3 minutes for corrective action

to occur. Ignore repeats of this error while
corrective action is taking place. Look for
error reports about the switch fabric
(CSC/SFC.)

A software bug in all probability. This

message indicates an unhandled interrupt
has been enabled in the fabric interface
ASIC.Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Wait atleast 3 minutes for corrective action

to occur. Ignore repeats of this error while
corrective action is taking place. Look for
error reports about the switch fabric
(CSC/SFC.) If errors persist, you can try
moving the card to another slot. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

A hardware error. No ddts need be filed. If

the recovery is successful, this error can be
treated as transient error, else if the error
persists run diagnostics to determine the
source of failure. The error if persistent
indicates a hardware fault on the LC.
Remove the LC and reinsert in another slot
in the chassis to rule out contact issues.

Wait several minutes for corrective action

to occur. Ignore repeats of this error while
corrective action is taking place. Look for
error reports about the switch fabric
(CSC/SFC.) If the cards are disabled, try the
following 1. Ensure firmware running on all
the cards are upto date. 2. Run field
diagnostics on the card that is facing
problem. 3. Take out the card and insert in
a new slot to check if problem persists.

A hardware error. No ddts need be filed. If

the recovery is successful, this error can be
treated as transient error, else if the error
persists run diagnostics to determine the
source of failure. The error if persistent
indicates a hardware fault on the LC.
Remove the LC and reinsert in another slot
in the chassis to rule out contact issues.

No action is required.

Hardware corrective action has taken

place. No ddts need be filed.

No action is required.

Hardware corrective action has taken

place. No ddts need be filed.

None, this is a transient error and can be

safely ignored. However multiple
occurrences of this error indiactes a
software problem. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

A software bug in all probability. This

indicates an error in the software that is
queuing packets to the fabric interface
ASIC, typically the queing ASIC on the
c12000 or the packet is received from the
line card CPU with wrong slot mask in the
header. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Wait atleast 3 minutes for the corrective

action to occur. Ignore repeats of this error
while corrective action is taking place. Look
for error reports about the switch fabric
(CSC/SFC.)

A software bug in all probability. This

message indicates an unhandled interrupt
has been enabled in the fabric interface
ASIC.Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

The system will normally recover from this

error without intervention. If the frequency
with which this error is occurring increases
substantially, call your Cisco technical
support representative and provide the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

An occasional alarm can be ignored but if

the frequency of this error increases, it
could indicate a problem with the OS kernel
of the card. Restart the FIAD process using
the 'process restert' command. if the error
persists after a restart, reload the LC using
'hw-module' command.

The system will normally recover from this

error without intervention. If the frequency
with which this error is occurring increases
substantially, call your Cisco technical
support representative and provide the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

An occasional alarm can be ignored but if

the frequency of this error increases, it
could indicate a problem with the OS kernel
of the card. Restart the FIAD process using
the 'process restert' command. if the error
persists after a restart, reload the LC using
'hw-module' command.

The system will normally recover from this

error without intervention. If the frequency
with which this error is occurring increases
substantially, call your Cisco technical
support representative and provide the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

An occasional alarm can be ignored but if

the frequency of this error increases, it
could indicate a problem with the OS kernel
of the card.

The system will normally recover from this

error without intervention. If the frequency
with which this error is occurring increases
substantially, call your Cisco technical
support representative and provide the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

An occasional alarm can be ignored but if

the frequency of this error increases, it
could indicate a problem with the OS kernel
of the card.

Wait several minutes for corrective action

to occur. Ignore repeats of this error while
corrective action is taking place. Look for
error reports about the switch fabric
(CSC/SFC.)

A software bug in all probability. This

message indicates an unhandled interrupt
has been enabled in the fabric interface
ASIC.Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

A software bug in all probability. This

Wait atleast 3 minutes for corrective action message indicates an unhandled interrupt
to occur. Ignore repeats of this error while has been enabled in the fabric interface
corrective action is taking place. Look for
ASIC.Report this to Engineering. Use Topic
error reports about the switch fabric
to search for a similar DDTS. If you find
(CSC/SFC.)
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Report the error

This is an ENS library access error, the

caller process will take appropriate action
based on return error code, which could
result in process restart or reboot. No
action required from library side.

Report the error.

This ENS library error happened during

initialization, the caller process will restart
itself to recover. No action required from
library side.

Report the error

This is a Fabric FIA ENS library access error,

the caller process will take appropriate
action based on return error code, which
could result in process restart or reboot. No
action required from library side.

If there are other error reports about the

switch fabric (CSC/SFC) then wait several
minutes for corrective action. Otherwise,
run diagnostics for slot reporting error.

A hardware error. No ddts need be filed. If

the recovery is successful, this error can be
treated as transient error, else if the error
persists run diagnostics to determine the
source of failure. The error if persistent
indicates a hardware fault on the LC.

If the problem is seen only during failover

operations like CSC card change or a RP
Failover and all the nodes are running
without issues. No action required. If the
problem is continues check if there are
other error reports about the switch fabric
(CSC/SFC) then wait several minutes for
corrective action. Otherwise, run
diagnostics for slot reporting error.Collect
following data.

A hardware error. No ddts need be filed. If

the recovery is successful, this error can be
treated as transient error, else if the error
persists run diagnostics to determine the
source of failure. The error if persistent
indicates a hardware fault on the LC.

Verify that the fia_driver process is up and

running by executing the following
command at the CLI of the active RP: 'show
process fia_driver' If the high availability of
the FIA driver is not important, then this
message may be ignored. However, if this
functionality is necessary then restart the
FIA driver by issuing the following
command at the CLI of the active RP:
'process restart fia_driver' Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Driver operation should continue as

If the message recurs, copy the error
normal, with the exception that the 'show
message exactly as it appears on the
controllers fia' and 'clear controller fia'
console or in the system log, call your
commands will not be available. Report this
Cisco technical support representative and to Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Driver operation should continue as

If the message recurs, copy the error
normal, with the exception that the 'show
message exactly as it appears on the
controllers fia' and 'clear controller fia'
console or in the system log, call your
commands will not be available. Report this
Cisco technical support representative and to Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Replace with a later version of SIP-600.

A warning message generated when

software detect an unsupported SIP-600
card without a fishstick (FIA). This
unsupported card SIP-600 card may result
in FIA ASIC errors when CSC switch-over,
RP fail-over or fabric card OIR occurs, and
the router may behave abnormally as a
result.

If the message appears once and then

stops, there is no cause for concern. If it
persists or if fia_driver gets respawned by
sysmgr for not returning EOI, then this
could indicate a problem.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

--

If the card is currently not used in service,

reload using 'hw-module' command can
clear the error condition. If the card is
already in service this message may be
ignored.

Indicates that software failed to get time

stamp to link with statistics collected for
debugging purposes. This information will
be useful in diagnosing problems if any in
future. If a line card reload is impacting
service you may ignore the message.
Alternate debugging information is being
collected.

If the card is currently not used in service,

reload using 'hw-module' command can
clear the error condition. If the card is
already in service this message may be
ignored.

Indicates that software failed to get time

stamp to link with statistics collected for
debugging purposes. This information will
be useful in diagnising problems if any in
future. If a line card reload is impacting
service you may ignore the message.
Alternate debugging information is being
collected.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Search the event logs for events/errors

If the message recurs, copy the error
related to the failure reason. Memory
message exactly as it appears on the
allocation failures will happen if the the
console or in the system log, call your
router runs out of memory or memory leak
Cisco technical support representative and in this process or other processes. If there
provide the representative with the
are failures here then other processes may
gathered information.
also exhibit similar problems.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Reload the board. *SUPPORT*

This error message indicates that an

unrecoverable fatal s/w error was
encountered by the service card's
BCM1255 FIFO driver. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Collect all the event logs (show
logging) and the output of the following
command. 'admin show process fsdb_fadb
location <loc>' Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Event
management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Node ID
management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Collect all the event logs (show
logging) and the output of the following
command. 'admin show process fsdb_fadb
location <loc>' Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Node ID
management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Node ID
management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Collect all the event logs (show
logging) and the output of the following
command. 'admin show process fsdb_fadb
location <loc>' Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Node ID
management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Utility to get
respawn count is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Utility to get
respawn count is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Event
management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Sysdb is part
of overall system. If there are failures here,
Search the event logs for events/errors
then other processes may also exhibit
related to the failure reason. Sysdb is part similar problems. A re-attempt for sysdb
of overall system. If there are failures here, bind can be forced by restarting the
then other processes may also exhibit
fsdb_fadb process on the node of interest.
similar problems. A re-attempt for sysdb
Report this to Engineering. Use Topic to
bind can be forced by restarting the
search for a similar DDTS. If you find none,
fsdb_fadb process on the node of interest. write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Sysdb is part
of overall system. If there are failures here,
Search the event logs for events/errors
then other processes may also exhibit
related to the failure reason. Sysdb is part similar problems. Report this to
of overall system. If there are failures here, Engineering. Use Topic to search for a
then other processes may also exhibit
similar DDTS. If you find none, write a
similar problems.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Shared
Memory Management is part of overall
system. If there are failures here then other
processes may also exhibit similar
problems. Collect all the event logs (show
logging) and the output of the following
Search the event logs for events/errors
command. 'admin show process fsdb_fadb related to the failure reason. Shared
location <loc>' Copy the error message
Memory Management is part of overall
exactly as it appears on the console or in
system. If there are failures here then other
the system log, call your Cisco technical
processes may also exhibit similar
support representative and provide the
problems. Report this to Engineering. Use
representative with the gathered
Topic to search for a similar DDTS. If you
information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Shared
Memory Management and disk access is
part of overall system. If there are failures
here then other processes may also exhibit
similar problems. Collect all the event logs
(show logging) output of the following
command. 'admin show process fsdb_fadb
location <loc>' Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Shared
Memory Management is part of overall
system. If there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Shared
Memory Management and disk access is
part of overall system. If there are failures
here then other processes may also exhibit
similar problems. Collect all the event logs
(show logging) output of the following
command. 'admin show process fsdb_fadb
location <loc>' Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Shared
Memory Management is part of overall
system. If there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Shared
Memory Management is part of overall
system. If there are failures here then other
processes may also exhibit similar
problems. Collect all the event logs (show
logging) and the output of the following
Search the event logs for events/errors
command. 'admin show process fsdb_fadb related to the failure reason. Shared
location <loc>' Copy the error message
Memory Management is part of overall
exactly as it appears on the console or in
system. If there are failures here then other
the system log, call your Cisco technical
processes may also exhibit similar
support representative and provide the
problems. Report this to Engineering. Use
representative with the gathered
Topic to search for a similar DDTS. If you
information.
find none, write a DDTS for this problem.

If fabric links, fabric cards or fabric chassis

connecting to the rack are brought down
via CLI, then this is expected. If the
problem happens otherwise, Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

If this error message is seen when the

fabric connectivity to the rack is healthy
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If fabric links, fabric cards or fabric chassis

connecting to the dsc rack are brought
down via CLI, then this is expected. If the
problem happens otherwise, Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

If this error message is seen when the

fabric connectivity to the rack is healthy
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the fabric planes are brought down or the

S3->Sponge links are brought down
intentionally, then this is expected. If the
problem happens otherwise, Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

If this error message is seen when the

fabric boards are healthy and the links from
the fabric to the line-card are up, Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

Check the admin plane configuration to

ensure that it corresponds with the actual
physical topology of the system. If this
configuration looks correct then contact
support, otherwise correct the
configuration and the system should
recover. Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

As mentioned in the explanation, this

message is printed when FSDB server
detects inconsistency between the admin
configuration and the actual detected
hardware, if any other errors are not seen
on the system, this could be a FSDB
internal software error. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

This indicates a problem in config manager

or sysdb in the system that prevents the
startup config from being applied. Please
wait for a while to see if the config gets
applied, if conditions persists, Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Admin config getting applied can be

delayed due to problems in cfgmgr or
sysdb Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Ensure that fabric cards are installed in the

system. For multichassis systems ensure
that the fabric racks have booted and the
fabric cables are installed. Fabric can come
up late if the fabric rack or fabric cards are
booted up late. Wait for more time to see if Fabric can be down due to many reasons.
the fabric comes UP. For MC systems, check Most common cases include fabric rack or
if plane admin config exists on the router. If fabric cards not being booted up. In case of
not, configure the plane admin config. If
MC, missing plane admin config can cause
condition persists, Copy the error message this. Check for asic states, link states and
exactly as it appears on the console or in
barrier flow through ingressq, all fabric
the system log, call your Cisco technical
asics and sponges. Report this to
support representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Plane down is caused by too many

underlying fabric errors. To fix the problem
one must locate the cause of problems and
fix that. To find cause of the problem check
if the fabric asics and link ports are up,
barriers are flowing through all fabric asics
sponge and sprayer. Plane mcast_down is
caused by several reasons like sponge links
to S3's are down, a fabric group is not
reachable from S2's in the plane or
minimum no.(25/36) of links between S1
and S2 are not up. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Get the output from the following

commands: 'admin sh tech fabric fast-snap' --

This error can be caused by an attempt to

use the router with in a fabric configuration
that is not supported. For example, there
may be three or more linecard racks that
have dual-rack fabric cards installed.
Ensure that the correct racks are installed
in the router and that software displays the
correct rack numbers and rack types for
each rack. Ensure that the software fabric
configuration is correct. If these steps do
not find an error, restart fabric control
software on the rack that produced this
message, and on the rack sending the
illegal message. 'admin process restart
fsdb_server loc <loc>'. As restart process is
disruptive, save output of all the
commands mentioned in required_info
This is a serious control-plane error,
before restarting the process. If problem
indicating either a bad system
persists, Copy the error message exactly as configuration or control software failure. It
it appears on the console or in the system is not caused simply by mis-connecting
log, call your Cisco technical support
fabric cables between racks. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.
If the identified plane is not already shut,
shut down the plane in admin
configuration: controller fabric plane <>
shutdown Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

--

1) Get the output from the following

commands: 'sh controller fabric trace all'
on the dSC sh diagnostic result location
<this node> detail sh diagnostic trace
error location all sh diagnostic trace
message location all 2) shut down the
identified faulty plane in admin
configuration: controller fabric plane <>
shutdown 3) restart the process that is
seeing the issue Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

--

1) Get the output from the following

commands: 'sh controller fabric trace all'
on the dSC sh diagnostic result location
<this node> detail sh diagnostic trace
error location all sh diagnostic trace
message location all 2) shut down the
identified faulty plane in admin
configuration: controller fabric plane <>
shutdown 3) restart the process that is
seeing the issue Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

FSDB AIPC CLIENT encountered an internal

error. Search the event logs for
events/errors/AIPC related to the failure
reason. Also collect the log for the given
client process name Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Check that there is an instance of the

fsdb_aserver process running on one RP in
the system (currently this would always be
the dSC). Also check that each rack has an
instance of the fsdb_server process running
No action is necessary. If condition persists, in each active RP. High CPU usage in one
Copy the error message exactly as it
RP could cause this message if it caused
appears on the console or in the system
sufficient delay in sending response from
log, call your Cisco technical support
either fsdb_server or fsdb_aserver
representative and provide the
processes. Other possible causes are
representative with the gathered
control ethernet problems or GSP failures in
information.
the admin plane.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Thread
Management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This could be an intrermitten failure due to

faulty NVRAM. Retry after replacing faulty
NVRAM. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

This message is expected if a cable is

inserted or removed, or if a fabric card (or
chassis) to which the cable connects is
powered on or off, or rebooted. If a change
to DOWN is seen in other circumstances it
may be due to a hardware failure. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
Check the bundle port connection on the
gathered information.
OIM module. Clean the fiber connectors.

This message is expected if a cable is

inserted or removed, or if a fabric card (or
chassis) to which the cable connects is
powered on or off, or rebooted. If a change
to DOWN is seen in other circumstances it
may be due to a hardware failure. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
Check the bundle port connection on the
gathered information.
OIM module. Clean the fiber connectors.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software.
Event Management, Checkpoint
Management and SYSDB Management are
If the message recurs, copy the error
part of overall system. If there are failures
message exactly as it appears on the
here then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software.
Event Management, Checkpoint
Management and SYSDB Management are
If the message recurs, copy the error
part of overall system. If there are failures
message exactly as it appears on the
here then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software.
Event Management, Debug/Ltrace
Management and SYSDB Management are
If the message recurs, copy the error
part of overall system. If there are failures
message exactly as it appears on the
here then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software.
Event Management and SYSDB
If the message recurs, copy the error
Management are part of overall system. If
message exactly as it appears on the
there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs to isolate the failure.

Event Connection Manager failures are part
If the message recurs, copy the error
of the overall system. If there are failures
message exactly as it appears on the
here then other processes may also be
console or in the system log, call your
experiencing similar problems. Report this
Cisco technical support representative and to Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs to isolate the failure.

Event Connection Manager failures are part
If the message recurs, copy the error
of the overall system. If there are failures
message exactly as it appears on the
here then other processes may also be
console or in the system log, call your
experiencing similar problems. Report this
Cisco technical support representative and to Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs to isolate the failure.

Event Manager failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also be
console or in the system log, call your
experiencing similar problems. Report this
Cisco technical support representative and to Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software.
If the message recurs, copy the error
Nodeid Management is part of overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

FSDB encountered an internal software

error. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Each type of component that interfaces

with the switch fabric is described by a
definition file installed on the router. This
A failed or incomplete software upgrade
message appears if errors are detected
could cause this error. It could also be
while reading one of these files. Either the
caused by corruption of an existing
file has been overwritten or damaged in
definition file. Ensure that the definition file some way, or there is an incompatibility
is not damaged. If the problem persists, re- between the software version and the file
install the fabric control software.
version.

This clearly indicates an underlying

transport issue. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

--

As mentioned in the explanation, this

message is printed when for some reason
not all drivers and remote FSDBs have got
in touch with the local FSDB. This could be
Restarting FSDB process on any racks
caused by a problem with the underlying
suffering from traffic loss may help, if not, communications infrastructure, or
restart FSDBs on all racks might resolve the potentially a bad view within FSDB of the
issue. 'admin process restart fsdb_server
current system inventory. Restarting FSDB
location <loc>' Since 'restart process' is a on any racks suffering from traffic loss may
disruptive operation and all the previous
help, or potentially restarting on all racks.
state is lost, all the logs for the commands Also, ensure to check for drivers (sea,
mentioned in required_info should be
fabricq and ingressq) that are blocked as
saved. If problem persists, Copy the error this error could occur if the drivers are
message exactly as it appears on the
deadlocked. Also, check for possibility of
console or in the system log, call your
customer having old/bad hardware. Report
Cisco technical support representative and this to Engineering. Use Topic to search for
provide the representative with the
a similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

FSDB uses SYSDB services for verification

and notification of various events. This
failure is indicative of communication
If the message recurs, copy the error
failure between FSDB and SYSDB. Search
message exactly as it appears on the
the event logs for events/errors related to
console or in the system log, call your
the failure reason. SYSDB Management is
Cisco technical support representative and part of overall system. If there are failures
provide the representative with the
here then other processes may also exhibit
gathered information.
similar problems.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software.
If the message recurs, copy the error
SYSDB Management is part of overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

This message indicate that trap

notifications of the operational states of
planes and bundles would not occur. If
snmp managability is not enabled, this
message can be ignored. However, if this
functionality is necessary then restart the
process by issuing the following command
at the CLI of the active RP after collecting
all the output of all the specified
commands. 'admin process restart
fsdb_server/fsdb_aserver loc <loc>' Restart
fsdb_server if the bundle state traps are
Search the event logs for events/errors
missing else if plane state traps are
related to the failure reason. Event
missing restart fsdb_aserver. Copy the error Management is part of overall system. If
message exactly as it appears on the
there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software.
Event Management and SYSDB
If the message recurs, copy the error
Management are part of overall system. If
message exactly as it appears on the
there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

This message indicate that trap

notifications of the operational states of
planes and bundles would not occur. If
snmp managability is not enabled, this
message can be ignored. However, if this
functionality is necessary then restart the
process by issuing the following command
at the CLI of the active RP after collecting
all the output of all the specified
commands. 'admin process restart
fsdb_server/fsdb_aserver loc <loc>' Restart
fsdb_server if the bundle state traps are
Search the event logs for events/errors
missing else if plane state traps are
related to the failure reason. Event
missing restart fsdb_aserver. Copy the error Management is part of overall system. If
message exactly as it appears on the
there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Each type of component that interfaces

with the switch fabric is described by a
definition file installed on the router. This
applies to backplanes, fiber modules,
linecards (L3 cards), RPs and DRPs, as well
as fabric boards. A new definition file may
be needed when a board is revised. This
message indicates that the driver for a
If the hardware installed in the router has fabric component requires the use of a
changed, ensure that fabric control
definition file which could not be found.
software has been upgraded to the correct Most likely new hardware was installed
version. If the correct software has been
without first installing the software support
installed, report the problem to technical
for it. Otherwise, the necessary files could
support.
have been removed inadvertently.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Thread
Management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Thread
Management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This could be an intrermitten failure due to

faulty NVRAM. Retry after replacing faulty
NVRAM. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Use chassis with rack num 0 or 1

--

To fix the issue please reinsert the card and

make sure it seats well. If that doesn't help
than verify the integrity of mid-plane pins. --

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

FSDB encountered a minor fabric LED

software error. Check out the possibility of
bad or broken LEDs which would help
isolate if the problem lies with the fabric
software. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

FSDB encountered a minor internal

software error. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Thread
Management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Thread
Management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Thread
Management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Thread
Management is part of overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

To fix the issue please change the fabric

card or modify the admin config for this
plane

--

Try to unshut a plane. If it doesnt help, the Please ensure that minimum plane
only way out is to reload the router either requirements (2 for CRS-16, 1 for others) is
from the CLI or powercycle. If the problem met all the time. Unshutting a plane
persists, Copy the error message exactly as quickly might work, otherwise, reloading
it appears on the console or in the system the router through CLI or powercycle is the
log, call your Cisco technical support
only way out. Report this to Engineering.
representative and provide the
Use Topic to search for a similar DDTS. If
representative with the gathered
you find none, write a DDTS for this
information.
problem.

No action is required.

System is booting up without fabric, this is

possible if rommon variable
BOOT_WITHOUT_FABRIC is set to 1 in
rommon. Unset this variable for normal
bootup of system which requires fabric
chassis to boot up. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

This is an informational message that may

assist in troubleshooting fabric planes that
are not up.

No action is required.

This is an informational message that may

assist in troubleshooting fabric planes that
are not up.

No action is required.

This is an informational message that may

assist in troubleshooting fabric planes that
are not up.

No action is required.

This is an informational message that may

assist in troubleshooting fabric planes that
are not up.

This indicates a low-memory condition.

Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. SYSDB is part
of overall system. If there are failures here
then other processes may also exhibit
similar problems. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. SysDB failures
are part of the overall system. If there are
failures here then other processes may also
exhibit similar problems. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

There was a problem setting a value in

SysDB. It might be due to sysdb connection
problem. Search the event logs for
events/errors related to the failure reason.
If the message recurs, copy the error
SysDB failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

There was a problem setting a value in

SysDB. It might be due to sysdb connection
problem. Search the event logs for
events/errors related to the failure reason.
If the message recurs, copy the error
SysDB failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Debug facility
If the message recurs, copy the error
failures are part of the overall system. If
message exactly as it appears on the
there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Debug facility
If the message recurs, copy the error
failures are part of the overall system. If
message exactly as it appears on the
there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Group
communication failures are part of the
overall system. If there are failures here
then other processes may also exhibit
similar problems. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. The internal
software errors are basic infra software
errors (e.g., timer service error or system
call errors) If there are failures here then
other processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. SysDB failures
If the message recurs, copy the error
are part of the overall system. If there are
message exactly as it appears on the
failures here then other processes may also
console or in the system log, call your
exhibit similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. SysDB failures
If the message recurs, copy the error
are part of the overall system. If there are
message exactly as it appears on the
failures here then other processes may also
console or in the system log, call your
exhibit similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. sysmgr
If the message recurs, copy the error
failures are part of the overall system. If
message exactly as it appears on the
there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Restart Fabric statistics client manually if

the error is persistent.

Search the event logs for events/errors

related to the failure reason. Group
communication failures are part of the
overall system. If there are failures here
then other processes may also exhibit
similar problems. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

Search the event logs for events/errors

related to the failure reason. Debug facility
failures are part of the overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Restart Fabric statistics client manually if

the error is persistent.

Search the event logs for events/errors

related to the failure reason. Debug facility
failures are part of the overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Restart Fabric statistics client manually if

the error is persistent.

Search the event logs for events/errors

related to the failure reason. Debug facility
failures are part of the overall system. If
there are failures here then other
processes may also exhibit similar
problems. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Restart Fabric statistics client manually if

the error is persistent in a specific fabric
card. Restart Fabric statistics server
manually if the error is persistent in many
fabric cards.

Search the event logs for events/errors

related to the failure reason. Group
communication failures are part of the
overall system. If there are failures here
then other processes may also exhibit
similar problems. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. SysDB failures
If the message recurs, copy the error
are part of the overall system. If there are
message exactly as it appears on the
failures here then other processes may also
console or in the system log, call your
exhibit similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Debug facility
If the message recurs, copy the error
failures are part of the overall system. If
message exactly as it appears on the
there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Debug facility
If the message recurs, copy the error
failures are part of the overall system. If
message exactly as it appears on the
there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Event
If the message recurs, copy the error
Manager failures are part of the overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Group
communication failures are part of the
If the message recurs, copy the error
overall system. If there are failures here
message exactly as it appears on the
then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. The internal
software errors are basic infra software
If the message recurs, copy the error
errors (e.g., timer service error or system
message exactly as it appears on the
call errors) If there are failures here then
console or in the system log, call your
other processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

This indicates a low-memory condition.

Perform 'process restart <memory hog
process job id>' to recover. If the issue
persist, Reduce other system activity to
ease memory demands. If conditions
warrant, upgrade to a larger memory
configuration.

Search the event logs for events/errors

related to the failure reason. Memory
allocation failures will happen if the the
router runs out of memory or memory leak
in this process or other processes. If there
are failures here then other processes may
also exhibit similar problems.

Search the event logs for events/errors

related to the failure reason. SysDB failures
If the message recurs, copy the error
are part of the overall system. If there are
message exactly as it appears on the
failures here then other processes may also
console or in the system log, call your
exhibit similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. SysDB failures
If the message recurs, copy the error
are part of the overall system. If there are
message exactly as it appears on the
failures here then other processes may also
console or in the system log, call your
exhibit similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. sysmgr
If the message recurs, copy the error
failures are part of the overall system. If
message exactly as it appears on the
there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

If the error continues, user will need to

restart the process for recovery. 'process
restart fstats_server <location> '

Search the event logs for events/errors

related to the failure reason. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Ltrace usage
is common to overall system. If there are
Search the event logs for events/errors
failures here then other processes may also related to the failure reason. Ltrace usage
exhibit similar problems. Copy the error
is common to overall system. If there are
message exactly as it appears on the
failures here then other processes may also
console or in the system log, call your
exhibit similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Ltrace usage
is common to overall system. If there are
Search the event logs for events/errors
failures here then other processes may also related to the failure reason. Ltrace usage
exhibit similar problems. Copy the error
is common to overall system. If there are
message exactly as it appears on the
failures here then other processes may also
console or in the system log, call your
exhibit similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. Ltrace usage
is common to overall system. If there are
Search the event logs for events/errors
failures here then other processes may also related to the failure reason. Ltrace usage
exhibit similar problems. Copy the error
is common to overall system. If there are
message exactly as it appears on the
failures here then other processes may also
console or in the system log, call your
exhibit similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Open a case with TAC Support along with

this required information.

It is recommended to verify the device

functionality from additional available cli
and in case, discrepancies are found,
reload the MSC.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Run diags on the card If FCRAM BIST errors
provide the representative with the
are seen, reseating the DIMMs should fix
gathered information.
the problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Run diags on the card If FCRAM BIST errors
provide the representative with the
are seen, reseating the DIMMs should fix
gathered information.
the problem.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
overall system. If there are failures here
Collect all the event logs and the output of then other processes may also exhibit
the following command executed from the similar problems. Report this to
CLI of the active RP: 'show process
Engineering. Use Topic to search for a
ingressq' Also, collect the fabric snapshot: similar DDTS. If you find none, write a
'show fabric-snapshot file <> loc <>'
DDTS for this problem.

The System Manager process (sysmgr) will

automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. Verify that the
ingressq driver is up and running by
executing the following command at the
CLI of the active RP: 'show process ingressq
location < >' If it is still non-operational,
enable the following debugs of the ingressq
driver process: error Errors in the driver
fatal Fatal errors which cause driver to exit
info All informational events init
Initialization events and restart the driver
by executing the following command at the Search the event logs for events/errors
CLI of the active RP: 'process restart
related to the failure reason. Event
ingressq location < >' If the message
Manager and SYSDB failures are part of the
recurs, copy the error message exactly as it overall system. If there are failures here
appears on the console or in the system
then other processes may also exhibit
log, call your Cisco technical support
similar problems. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

If the error persists, please contact TAC

suppport.

Search the event logs for events/errors

related to the failure reason. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the error persists, please contact TAC

suppport.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

This might be a recovery action from a

fault. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card

This might be a recovery action from a

fault. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

This might be a recovery action from a

fault. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card

Check Fabric health and look for any

disconnects between the fabric stages.
Make sure that the fabric planes are up.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

'http://zed.cisco.com/confluence/display/GS
RTR/Ingressq+or+Sprayer+or+Spiller'
'http://zed.cisco.com/confluence/display/GS
RTR/CRS+Fabric'

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Run diags on the board. FCRAM has loose
provide the representative with the
DIMM connectors. Reseating them should
gathered information.
fix the problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Run diags on the card If FCRAM BIST errors
provide the representative with the
are seen, reseating the DIMMs should fix
gathered information.
the problem.

The System Manager process (sysmgr) will

automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. Verify that the
ingressq driver is up and running by
executing the following command at the
CLI of the active RP: 'show process ingressq
location < >' If it is still non-operational,
enable the following debugs of the ingressq
driver process: error Errors in the driver
fatal Fatal errors which cause driver to exit
info All informational events init
Initialization events and restart the driver
by executing the following command at the Search the event logs for events/errors
CLI of the active RP: 'process restart
related to the failure reason. Event
ingressq location < >' If the message
Manager and SYSDB failures are part of the
recurs, copy the error message exactly as it overall system. If there are failures here
appears on the console or in the system
then other processes may also exhibit
log, call your Cisco technical support
similar problems. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

The driver/client processes try to recover

from this error. If any discrepancies are
found in the device functionality, contact
TAC Support. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

'http://zed.cisco.com/confluence/display/GS
RTR/Ingressq+or+Sprayer+or+Spiller'

If it is possible to isolate the trigger point

for the sn link error, collect all the
necessary condition that caused the error.
If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Run diags on the board. If this error is seen

consistently, it is recommended to reload
the MSC to avoid inconsistent behavior
because of the link error

If it is possible to isolate the trigger point

for the sn link error, collect all the
necessary condition that caused the error.
If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Run diags on the board. If this error is seen

consistently, it is recommended to reload
the MSC to avoid inconsistent behavior
because of the link error

If it is possible to isolate the trigger point

for the sn link error, collect all the
necessary condition that caused the error.
If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Run diags on the board. If this error is seen

consistently, it is recommended to reload
the MSC to avoid inconsistent behavior
because of the link error

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No user action is required. Copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

The System Manager process (sysmgr) will

automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. Verify that the
ingressq driver is up and running by
executing the following command at the
CLI of the active RP: 'show process ingressq
location < >' If it is still non-operational,
enable the following debugs of the ingressq
driver process: asic error asic fatal asic info
and restart the driver by executing the
following command at the CLI of the active
RP: 'process restart ingressq location < >'
If the message recurs, copy the error
message exactly as it appears on the
Search the event logs for events/errors
console or in the system log, call your
related to the failure reason. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

The System Manager process (sysmgr) will

automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. Verify that the
ingressq driver is up and running by
executing the following command at the
CLI of the active RP: 'show process ingressq
location < >' If it is still non-operational,
enable the following debugs of the ingressq
driver process: asic error asic fatal asic info
and restart the driver by executing the
following command at the CLI of the active
RP: 'process restart ingressq location < >'
If the message recurs, copy the error
message exactly as it appears on the
Search the event logs for events/errors
console or in the system log, call your
related to the failure reason. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Verify that the ingressq driver is up and

running by executing the following
command at the CLI of the active RP: 'show
process ingressq location < >' If it is still
non-operational, enable the following
debugs of the ingressq driver process: asic
error asic fatal asic info and restart the
driver by executing the following command
at the CLI of the active RP: 'process restart
ingressq location < >' If the message
recurs, copy the error message exactly as it
appears on the console or in the system
Search the event logs for events/errors
log, call your Cisco technical support
related to the failure reason. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check 1)
http://zed.cisco.com/confluence/display/GS
RTR/Ingressq+or+Sprayer+or+Spiller 2)
http://zed.cisco.com/confluence/display/GS
RTR/CRS+Fabric before sending a mail to
crs-fabric-triages with
questions/clarifications.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check Fabric health and look for any

disconnects between the fabric stages.

If it is possible to isolate the trigger point

for the cdma failure, collect all the
necessary condition that caused the error.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

It is recommended to reload the MSC to

avoid inconsistent behavior due to the
cdma failure.

If it is possible to isolate the trigger point

for the cdma failure, collect all the
necessary condition that caused the error.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

It is recommended to reload the MSC to

avoid inconsistent behavior due to the
cdma failure.

If it is possible to isolate the trigger point

for the cdma failure, collect all the
necessary condition that caused the error.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

It is recommended to reload the MSC to

avoid inconsistent behavior due to the
cdma failure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upstream ASICs might have been

misconfigured or their is a problem in the
forwarding path. Please identify the source
of these packets, by corelating them to the
queue that they were sent to.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

If this error is seen consistently, it is

recommended to reload the MSC to avoid
inconsistent behavior because of the link
error. Also run diags on the board.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

If this error is seen consistently, it is

recommended to reload the MSC to avoid
inconsistent behavior because of the link
error. Also run diags on the board.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

If this error is seen consistently, it is

recommended to reload the MSC to avoid
inconsistent behavior because of the link
error. Also run diags on the board.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If the error persists, please contact TAC

suppport.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Run diags on the card

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Run diags on the card

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Run diags on the card

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Ingressq drops cells if their destination in

unreachable through the fabric. This can be
caused due to one of the following reasons:
1) The destination is not present but an
application is trying to send traffic to it. 2)
Ingressq is not programmed correctly for
the valid destination. If this error is seen
intermittently after OIR, Failover or any
other system change, please ignore the
drops. The system should recover after
hardware reprogramming. If this error is
seen continuously, it could be one of the
following problems: a) Plane Availablity for
a particular destination is not programmed
correctly. List of valid fabric destinations in
the system `admin>show contr fabricq
summary | include Destination` List of
destinations with non-zero plane
availability `show controller ingressq fabric
pla loc <>` If all the valid destinations
have non-zero pla, it could be problem b)
b) Packets are being sent to an invalid
If the message recurs, copy the error
destination. There is a bug in data plane
message exactly as it appears on the
software (ucode, aib, fib, routing protocols
console or in the system log, call your
etc.) If the LOP error rate is high(1000 cells
Cisco technical support representative and dropped in 1 min) a debug script is
provide the representative with the
spawned to take necessary logs. Collect
gathered information.
this log harddisk:/lop_debug_.log

Ingressq drops cells if their destination in

unreachable through the fabric. This can be
caused due to one of the following reasons:
1) The destination is not present but an
application is trying to send traffic to it. 2)
Ingressq is not programmed correctly for
the valid destination. If this error is seen
intermittently after OIR, Failover or any
other system change, please ignore the
drops. The system should recover after
hardware reprogramming. If this error is
seen continuously, it could be one of the
following problems: a) Plane Availablity for
a particular destination is not programmed
correctly. List of valid fabric destinations in
the system `admin>show contr fabricq
summary | include Destination` List of
destinations with non-zero plane
availability `show controller ingressq fabric
pla loc <>` If all the valid destinations
have non-zero pla, it could be problem b)
b) Packets are being sent to an invalid
If the message recurs, copy the error
destination. There is a bug in data plane
message exactly as it appears on the
software (ucode, aib, fib, routing protocols
console or in the system log, call your
etc.) If the LOP error rate is high(1000 cells
Cisco technical support representative and dropped in 1 min) a debug script is
provide the representative with the
spawned to take necessary logs. Collect
gathered information.
this log harddisk:/lop_debug_.log

Ingressq drops cells if their destination in

unreachable through the fabric. This can be
caused due to one of the following reasons:
1) The destination is not present but an
application is trying to send traffic to it. 2)
Ingressq is not programmed correctly for
the valid destination. If this error is seen
intermittently after OIR, Failover or any
other system change, please ignore the
drops. The system should recover after
hardware reprogramming. If this error is
seen continuously, it could be one of the
following problems: a) Plane Availablity for
a particular destination is not programmed
correctly. List of valid fabric destinations in
the system `admin>show contr fabricq
summary | include Destination` List of
destinations with non-zero plane
availability `show controller ingressq fabric
pla loc <>` If all the valid destinations
have non-zero pla, it could be problem b)
b) Packets are being sent to an invalid
If the message recurs, copy the error
destination. There is a bug in data plane
message exactly as it appears on the
software (ucode, aib, fib, routing protocols
console or in the system log, call your
etc.) If the LOP error rate is high(1000 cells
Cisco technical support representative and dropped in 1 min) a debug script is
provide the representative with the
spawned to take necessary logs. Collect
gathered information.
this log harddisk:/lop_debug_.log
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card.

This error is an correctable error. There are

no side effects. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card

No action is required.

None.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the card

Reduce the incoming packet rate to this

Isolate the cause of the oor condition.
MSC as under the OOR condition the QOS If Potential causes are: 1) Oversubscription:
the OOR is seen in non-oversubscribed
2) pps Rate 3) Reduction in Egress
case, contact TAC Reduce other system
bandwidth to fabric. 'show controller
activity to ease memory demands. If
ingressq fabric pla' 4) Fabric Backpressure
conditions warrant, upgrade to a larger
'show controller ingressq block ssm bpmem
memory configuration.
0 location '

Reduce the incoming packet rate to this

Isolate the cause of the oor condition.
MSC as under the OOR condition the QOS If Potential causes are: 1) Oversubscription:
the OOR is seen in non-oversubscribed
2) pps Rate 3) Reduction in Egress
case, contact TAC Reduce other system
bandwidth to fabric. 'show controller
activity to ease memory demands. If
ingressq fabric pla' 4) Fabric Backpressure
conditions warrant, upgrade to a larger
'show controller ingressq block ssm bpmem
memory configuration.
0 location '

Reduce the incoming packet rate to this

Isolate the cause of the oor condition.
MSC as under the OOR condition the QOS If Potential causes are: 1) Oversubscription:
the OOR is seen in non-oversubscribed
2) pps Rate 3) Reduction in Egress
case, contact TAC Reduce other system
bandwidth to fabric. 'show controller
activity to ease memory demands. If
ingressq fabric pla' 4) Fabric Backpressure
conditions warrant, upgrade to a larger
'show controller ingressq block ssm bpmem
memory configuration.
0 location '

If these fabric planes have not been

installed, please ignore this message. If
these fabric planes have been installed,
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If the error persists, please contact TAC

suppport.

--

If the error persists, please contact TAC

suppport.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No user action is required.

--

No user action is required. Copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

'http://zed.cisco.com/confluence/display/GS
RTR/Ingressq+or+Sprayer+or+Spiller'
'http://zed.cisco.com/confluence/display/GS
RTR/CRS+Fabric'

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Run diags on the board and contact TAC

support. If it is possible to isolate the
trigger point for the read failure, collect all
the necessary condition that caused the
error. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Read errors are reported asynchronously to

the driver. By the time the error is
processed by the driver the returned value
is already used. It is recommended to
reload the MSC to avoid inconsistent
behavior because of the read failure.

Run diags on the board and contact TAC

support. If it is possible to isolate the
trigger point for the read failure, collect all
the necessary condition that caused the
error. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Read errors are reported asynchronously to

the driver. By the time the error is
processed by the driver the returned value
is already used. It is recommended to
reload the MSC to avoid inconsistent
behavior because of the read failure.

Run diags on the board and contact TAC

support. If it is possible to isolate the
trigger point for the read failure, collect all
the necessary condition that caused the
error. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Read errors are reported asynchronously to

the driver. By the time the error is
processed by the driver the returned value
is already used. It is recommended to
reload the MSC to avoid inconsistent
behavior because of the read failure.

Run diags on the board and contact TAC

support. If it is possible to isolate the
trigger point for the set failure, collect all
the necessary condition that caused the
error. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the board.

Run diags on the board and contact TAC

support. If it is possible to isolate the
trigger point for the set failure, collect all
the necessary condition that caused the
error. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Run diags on the board.

The driver/client processes try to recover

from this error. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

It is recommended to verify the device

functionality from additional available cli
and in case discrepancies are found, reload
the MSC.

The driver/client processes try to recover

from this error. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

It is recommended to verify the device

functionality from additional available cli
and in case discrepancies are found, reload
the MSC.

The driver/client processes try to recover

from this error. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

It is recommended to verify the device

functionality from additional available cli
and in case discrepancies are found, reload
the MSC.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

'http://zed.cisco.com/confluence/display/GS
RTR/Ingressq+or+Sprayer+or+Spiller'

The System Manager process (sysmgr) will

automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. Verify that the
ingressq driver is up and running by
executing the following command at the
CLI of the active RP: 'show process ingressq
location < >' If it is still non-operational,
enable the following debugs of the ingressq
driver process: error Errors in the driver
fatal Fatal errors which cause driver to exit
info All informational events init
Initialization events and restart the driver
by executing the following command at the Search the event logs for events/errors
CLI of the active RP: 'process restart
related to the failure reason. Event
ingressq location < >' If the message
Manager and SYSDB failures are part of the
recurs, copy the error message exactly as it overall system. If there are failures here
appears on the console or in the system
then other processes may also exhibit
log, call your Cisco technical support
similar problems. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

The driver/client processes try to recover

from this error. If any discrepancies are
found in the device functionality, contact
TAC Support. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

It is recommended to verify the device

functionality from additional available cli
and in case, discrepancies are found,
reload the MSC.
'http://zed.cisco.com/confluence/display/GS
RTR/Ingressq+or+Sprayer+or+Spiller'
'http://zed.cisco.com/confluence/display/GS
RTR/CRS+Fabric'

Check for error logs from fsdb and ingressq

processes. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Check for error logs from the imdr process

to determine the exact cause of the abort.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.
--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. Event
Manager and SYSDB failures are part of the
overall system. If there are failures here
then other processes may also exhibit
similar problems. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is necessary.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

1. Verify the connectivity between the

client and the Ingressq process. 'show
controllers ingressq clients location <>'
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

The System Manager process (sysmgr) will

automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. Verify that the
ingressq driver is up and running by
executing the following command at the
CLI of the active RP: 'show process ingressq
location < >' If it is still non-operational,
enable the following debugs of the ingressq
driver process: error Errors in the driver
fatal Fatal errors which cause driver to exit
info All informational events init
Initialization events and restart the driver
by executing the following command at the Search the event logs for events/errors
CLI of the active RP: 'process restart
related to the failure reason. Event
ingressq location < >' If the message
Manager and SYSDB failures are part of the
recurs, copy the error message exactly as it overall system. If there are failures here
appears on the console or in the system
then other processes may also exhibit
log, call your Cisco technical support
similar problems. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

The System Manager process (sysmgr) will

automatically respawn this process, up to a
fixed number of times the error is
encountered, to recover. Verify that the
ingressq driver is up and running by
executing the following command at the
CLI of the active RP: 'show process ingressq
location < >' If it is still non-operational,
enable the following debugs of the ingressq
driver process: error Errors in the driver
fatal Fatal errors which cause driver to exit
info All informational events init
Initialization events and restart the driver
by executing the following command at the Search the event logs for events/errors
CLI of the active RP: 'process restart
related to the failure reason. Event
ingressq location < >' If the message
Manager and SYSDB failures are part of the
recurs, copy the error message exactly as it overall system. If there are failures here
appears on the console or in the system
then other processes may also exhibit
log, call your Cisco technical support
similar problems. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

The driver/client processes try to recover

from this error. If any discrepancies are
found in the device functionality, contact
TAC Support. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

It is recommended to verify the device

functionality from additional available cli
and in case, discrepancies are found,
reload the MSC.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Monitor the event messages. If the

message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Monitor the event messages. If the

message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Please provide the output of the following

commands on the node where the problem
occurred: ??? ??? To recover, reset the line
card

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki links: http://wikieng.cisco.com/engwiki/IOX_20FIB_20Conver

gence_20_28IFC_29
http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki links:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding http://wikieng.cisco.com/engwiki/IOX_20FIB_20Conver
gence_20_28IFC_29

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki links:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+MPLS+Forwarding
http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki link:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+MPLS+Forwarding
http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki link:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+MPLS+Forwarding
http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki links:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Reduce the number of Primary-Backup path Trouble-shooting wiki links:

combinations by removing protection for
http://zed.cisco.com/confluence/display/GS
some of the Primary Interfaces.
RTR/IP+LDP+FRR

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki link:

http://zed.cisco.com/confluence/display/GS
RTR/Platform+Manager

Please collect the logs mentioned in the

required_info and contact support team.

HAL Trouble-shooting wiki link:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki link:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding
http://zed.cisco.com/confluence/display/GS
RTR/C12000+MPLS+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki link:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+MPLS+Forwarding
http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki links:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+MPLS+Forwarding

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki links:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki links:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+MPLS+PBTS

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki link:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

HAL Trouble-shooting wiki link:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki links:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+Accounting
http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki links:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+Accounting
http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki links:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+Accounting
http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

The error message indicates a tunnel

creation or deletion error. This may impact
traffic flow through the tunnel. Restarting
tunnel EA process may help. Please collect
the requested info and pass it on to the
Engineering team for analysis. Troubleshooting wiki link:
http://zed.cisco.com/confluence/display/GS
RTR/C12000+L3VPN+Biscuit

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki link:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki links:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+IPv4+Forwarding

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Please collect the logs mentioned in the

required_info and contact support team.

This indicates a failure of Platform Manager

to lookup the given interface handle in it's
local database. If the error given is EAGAIN
(Resource temporarily unavailable) then
this means the function was called before
the shared memory had been initialised.
This is unexpected, but not fatal. Any other
error indicates something more seriously
wrong with Platform Manager (possibly an
inconsistancy in its internal database).
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem. Troubleshooting wiki link:
http://zed.cisco.com/confluence/display/GS
RTR/Platform+Manager

This error is probably the result of either a

lack of resource or a problem with the LWM
between HAL and the client. Restarting the
Restarting the affected client may solve the client would be expected to solve the
issue. If not, Copy the error message
problem. Alternatively a restart of FIB may
exactly as it appears on the console or in
correct the issue. Finally, a restart of the
the system log, call your Cisco technical
linecard itself may solve the problem.
support representative and provide the
Trouble-shooting wiki link:
representative with the gathered
http://zed.cisco.com/confluence/display/GS
information.
RTR/C12000+IPv4+Forwarding

This error is probably the result of either a

lack of resource or a problem with the LWM
between HAL and the client. Restarting the
Restarting the affected client may solve the client would be expected to solve the
issue. If not, Copy the error message
problem. Alternatively a restart of FIB may
exactly as it appears on the console or in
correct the issue. Finally, a restart of the
the system log, call your Cisco technical
linecard itself may solve the problem.
support representative and provide the
Trouble-shooting wiki link:
representative with the gathered
http://zed.cisco.com/confluence/display/GS
information.
RTR/C12000+IPv4+Forwarding

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Please reload each Engine 3 linecard using

the command: hw-module reload location
r/s/CPU0
--

Please reload the node using the command

hw-module reload location r/s/CPU0
-none

none

Please collect the logs mentioned in the

required_info and contact support team.

Trouble-shooting wiki link:

http://zed.cisco.com/confluence/display/GS
RTR/C12000+MPLS+Forwarding

Copy the error message exactly as it

appears on the console or in the system
log. Please capture the following
information on LC/Node where the problem
occurred and call your Cisco Technical
support - Console or system log
information - show l2vpn platform trace hal
all location <> - show l2vpn trace location
<>

This error indicates that a run time error

occurred while trying to access specified
field of specified object in the Platform
Independent SW Data Structures.
Workaround is LC Reload.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log. Along with the above, provide the
following information on LC/Node where
the problem occurred. Call your Cisco
Technical support - sh l2vpn platforms trace
hal all location <>, - sh l2vpn trace hal
This error indicates that a run time error
walker all location <loc>' - show l2vpn
occurred while trying to walk and update
trace location <>
dependent objects in the forwarding chain.

A runtime error occurred in GSR L2 FIB

module. The error means that the Engine 3
LC cannot be edge and core facing
Linecard Simultaneously. Configs have to
be reverted. If the error is still seen after
Revert the config wherever the same LC is that, collect the following - Console or
configured as both edge facing and core
system log information - Show running
facing card.
config
Revert the configs wherever the LC have
different types of encapsulation under
same bridge domain.

--

Copy the error message exactly as it

appears on the console or in the system
log. Along with above provide capture the
following information on LC/Node where
the problem occurred and call Cisco
Technical Support. - show l2vpn platforms
trace hal all location <>, - show l2vpn
platforms trace hal atom all location <>, show l2vpn trace location <> - show
running config

A runtime error occurred in GSR MPLS

module. This error means that the NHOP
that is configured is not able to be reached
and pseudowire will not come UP. Check if
the configuration regarding the nexthop
and OSPF/MPLS configuration is correct.
Else, collect the above outputs.

Copy the error message exactly as it

appears on the console or in the system
log, Call your Cisco Technical support.

A runtime error occurred while initialiaing

GSR Layer 2 VPN Hardware Abstraction
Layer (L2 HAL) module. The L2FIB process
would be killed and restarted again. If the
problem happens again, LC reload should
solve the issue. Otherwise, router reload.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log. Also, provide the captures of the
following on LC/Node where the issue is
seen and call Cisco Technical Support. console logs or system log - show running
config - show l2vpn platform trace hal all
location <>

This error indicates an internal L2HAL

problem that cannot find the parent of the
specified object. This could be service
impacting. Check if L2VPN is down because
of this. If yes, please collect the above
outputs.

Copy the error message exactly as it

appears on the console or in the system
log. provide the following captures on the
corresponding LC/Node and call your Cisco
Technical support. - show l2vpn platform
trace hal all location <> - show l2vpn trace
all location <>

This error indicates a runtime error in

initializing L2HAL Multicast QoS module. No
action is required as the retry will reinitialize the module. If it does not recover,
collect the above above traces.

Copy the error message exactly as it

appears on the console or in the system
log. Please capture the following
information on LC/Node where the problem
occurred and call Cisco Technical support. - This error indicates that a runtime error
Console or system log information - show occurred while operating on shared
l2vpn platform trace hal all location <>
memory window. Workaround is LC reload.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

please provide the following captures on

the corresponding LC/Node - show l2vpn
platform trace hal all location <> - show
l2vpn trace all location <>

This error indicates that an error has

occurred while initializing GSR Layer 2 VPN
Hardware Abstraction Layer (L2HAL)
module. No action is required as the retry
will re-initialize the module.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Please collect console logs and identify

both PD_UPDATE failure and FIB
PLATF_UPD_FAIL messge to correlate the
root cause of the failure. Recommende
action need to be driven as per the
'FORWARDING FIB PLATF_UPD_FAIL'
message.

Collect FIB CEF trace and C12000

forwarding trace using 1. show gsr
forwarding trace error loc 2. show cef trace
error loc

Please collect console logs and identify

both PD_UPDATE failure and FIB
PLATF_UPD_FAIL messge to correlate the
root cause of the failure. Recommende
action need to be driven as per the
'FORWARDING FIB PLATF_UPD_FAIL'
message.

Collect FIB CEF trace and C12000

forwarding trace using 1. show gsr
forwarding trace error loc 2. show cef trace
error loc

None

--

Remove and reconfigure the tunnel.

--

Remove and reconfigure the specified

tunnel.

--

Collect the Debugs. Restart tunnel GRE MA

process by executing the following
command. <CmdBold>process restart
The problem is with tunnel/gre module. TAC
tunl_gre_ma<NoCmdBold>
can contact BU for furher details.

Change the tunnel destination or change

the IP address on local interface.

--

Change the tunnel destination or change

the route for tunnel destination. So that the
tunnel destination address is reachable but
not over another tunnel.
-Please provide the output of the following
command: <CmdBold>show tech-support
tunnel-ip<NoCmdBold>

--

Either the box needs more memory, or

Check the box for processes with excessive there is a memory leak in some process in
memory in the location as seen in error
the system, or some process is hogging all
message.
the memory.

Shut and no shut the tunnel interface. If

the problem persists, remove and reconfigure the tunnel interface.

Hardware programming has failed in

Platform. Tunnel EA traces will have more
information about failure.

Please restarting IP Tunnel Execution Agent

with the command <CmdBold>process
restart ip_tunnel_ea location <node
id><NoCmdBold>. If the problem persists,
please contact Cisco TAC and provide this
message text as well as the information
specified in required_info section.
--

Please try restarting ip_tunnel_ea process

with the command <CmdBold>process
restart ip_tunnel_ea location <node
id><NoCmdBold>. If the problem persists,
please contact Cisco TAC and provide this
message text as well as the information
specified in required_info section.
--

Please try restarting the client process with

command <CmdBold>process restart
<process name> location <node
id><NoCmdBold>. Process name and
location are included in the message
already. If the problem persists, please
contact Cisco TAC and provide this
message text as well as the information
specified in required_info section.
--

Please contact Cisco TAC and provide this

message text as well as the information
specified in required_info section.

--

Please try restarting IP Tunnel Execution

Agent process with the command
<CmdBold>process restart ip_tunnel_ea
location <node id><NoCmdBold> If the
problem persists, please contact Cisco TAC
and provide this message text as well as
the information specified in required_info
section.
-Remove and reconfigure the tunnel which
is failed.

show tech-support pfi show tech-support

tunl_gre_ma location show ip trace ma all

Restart tunnel GRE MA process by

executing the following command.
<CmdBold>process restart
tunl_gre_ma<NoCmdBold>

show tech-support pfi show tech-support

tunl_gre_ma location show ip trace ma all

Please try restarting IP Tunnel Execution

Agent process with the command
<CmdBold>process restart ip_tunnel_ea
location <node id><NoCmdBold> If the
problem persists, please contact Cisco TAC
and provide this message text as well as
the information specified in required_info
section.
--

This failure occurs during process

initialization. Please try restarting the
process that printing this message with the
command <CmdBold>process restart
<process name> location <node
id><NoCmdBold> If the problem persists,
please contact Cisco TAC and provide this
message text as well as the information
specified in required_info section.
-Recommeded action is to disable the Keepalive on tunnel. If keep-alive is a must,
restart the process using following
command. <CmdBold>process restart
tunl_gre_ma<NoCmdBold>
--

Either remove Keep-alive or tunnel key

configuration on the corresponding tunnel. -Check the router for processes with
excessive memory in the location as seen
in the error message.

Either the box needs more memory, or

there is a memory leak in some process in
the system, or some process is hogging all
the memory.

Collect the folowing Debugs: show running

Collect debugging information, remove
configuration show tech pfi show tunnel ip
tunnel interface, re-create tunnel interface. trace ma all
Please collect the output of the following
Collect debugging information, remove
commands: show running configuration
tunnel interface, re-create tunnel interface. show tech pfi show ip trace ma all

Please try restarting ip_tunnel_ma process

with the command <CmdBold>process
restart ip_tunnel_ma<NoCmdBold> If the
problem persists, please contact Cisco TAC
and provide this message text as well as
the information specified in required_info
section.
--

Please contact Cisco TAC and provide this

message text as well as the information
specified in required_info section.

--

Please contact Cisco TAC and provide this

message text as well as the information
specified in required_info section.

--

The P2MP tunnel failed to program the

tunnel information updates. Please try
shutting down and turning on the tunnel
source interface with commands (in
interface config mode)
<CmdBold>shutdown<NoCmdBold> and
<CmdBold>no shutdown<NoCmdBold>. If
the problem persists after the above two
operations, please try restarting the IP
Tunnel Execution Agent process with the
command <CmdBold>process restart
ip_tunnel_ea location <node
id><NoCmdBold> If the problem persists
even after restarting process, please
contact Cisco TAC and provide this
message text as well as the information
specified in required_info section.
--

Modify source or destination address of the

tunnel that caused the conflict to make a
unique pair of source and destination that
does not exist on any other tunnel on the
box.
-Please contact Cisco TAC and provide this
message text as well as the information
specified in required_info section.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If the retry does not succeeded in some

time, remove and re-create the tunnel.

None.

Please contact Cisco TAC and provide this

message text as well as the information
specified in required_info section.

--

This error occurs during process

initialization. Please try restarting IP Tunnel
Execution Agent process with the
command <CmdBold>process restart
ip_tunnel_ea location <node
id><NoCmdBold> If the problem persists,
contact Cisco TAC and provide this
message text as well as the information
specified in required_info section.
--

No action is required.

None

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None.

Please try restarting IP Tunnel Execution

Agent process with the command
<CmdBold>process restart ip_tunnel_ea
location <node id><NoCmdBold>. If the
problem persists, please contact Cisco TAC
and provide this message text as well as
the information specified in required_info
section.
--

Reduce system scale. If the problem

persists even with reduced system scale,
please contact Cisco TAC.

None

An error may have occurred in the

hardware or lower layer processes. Invalid
packets are delivered to pbr_ea. Please
collect the information specified in
required_info section and contact Cisco
TAC.

None

Allow PBR EA to restart with the command

<CmdBold>process restart pbr_ea location
<node id><NoCmdBold> If the problem
persists, contact Cisco TAC.
None.

Allow the 'pbr_ea' process to restart with

the command <CmdBold>process restart
pbr_ea location <node id><NoCmdBold>.
If the problem persists, contact Cisco TAC. None.

Allow PBR EA to exit and validate with the

command <CmdBold>show process pbr_ea
location <node id><NoCmdBold>. If it
does not exit, use <CmdBold>process
restart pbr_ea location <node
id><NoCmdBold> to recover. If the
problem persists, contact Cisco TAC.
None.

Reduce system scale. If the problem

persists even with reduced system scale,
please contact Cisco TAC.

None

Allow PBR MA to restart with the command

<CmdBold>process restart pbr_ma
location <node id><NoCmdBold> If the
problem persists, contact Cisco TAC.
None.

Allow the 'pbr_ma' process to restart with

the command <CmdBold>process restart
pbr_ma location <node id><NoCmdBold>.
If the problem persists, contact Cisco TAC. None.

Allow PBR MA to exit and validate with the

command <CmdBold>show process
pbr_ma location <node id><NoCmdBold>.
If it does not exit, use <CmdBold>process
restart pbr_ma location <node
id><NoCmdBold> to recover. If the
problem persists, contact Cisco TAC.
None.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect the 'show cdm trace jid all' output

logs and contact TAC, if error persists.

--

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
An internal error - Report this to
Engineering. Use Topic to search for a
Collect system log information and forward similar DDTS. If you find none, write a
to technical support.
DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Determine why the process is running on

the destination node.

There are most likely duplicate copies of

the process running.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
cdm hit an internal assert because an
Cisco technical support representative and unexpected condition occurred. The assert
provide the representative with the
condition hit because some error condition
gathered information.
in code.

Restart the process. If error persists,

contact TAC with 'show cdm trace jid all'
logs.

Collect 'show cdm trace jid all' logs and file

ddts if error is seen multiple times. Please
refer the below wiki: http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/infra-cdm.html

Restart the process. If error persists,

contact TAC with 'show cdm trace jid all'
logs.

Collect 'show cdm trace jid all' logs and file

ddts if error is seen multiple times. Please
refer the below wiki: http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/infra-cdm.html

Tracing will not work properly. Process will

proceed running. Can restart the process to
overcome this issue. IF error
persists.Collect the error log with return
collect core dump of process and file ddts if
value and core dump of the process
error is seen multiple times

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Analyze the restart failure and take

appropriate recovery action.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
An internal error - Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
cdm hit an internal system error. Report
Cisco technical support representative and this to Engineering. Use Topic to search for
provide the representative with the
a similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
cdm hit an unexpected condition . Report
Cisco technical support representative and this to Engineering. Use Topic to search for
provide the representative with the
a similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

The CDM software will periodically try again Report this to Engineering. Use Topic to
to set up the index structure. So, in general search for a similar DDTS. If you find none,
no action is required.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

An internal development error - Report this

to Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Please collect console logs during the

crash, corefile and contact support.

Checkpoint code hit an internal assert

because an unexpected condition occurred.
Please collect console logs during the crash
and corefile. Please refer to the below link
before contacting [email protected]
http://wikicentral.cisco.com/display/NOSINF
RA/Defect+filing+guidelines+-+Checkpoint

The process shared segments are not

unlinked. Process will take care of unlinking
in other possible way. If the error is
reported 2-3 times more . Collect system
log and show tech-support and Contact
Collect system log and show tech-support.
TAC.
file ddts if error is seen multiple times.
Tracing will not work properly. Process will
proceed running. Can restart the process to
overcome this issue. IF error
persists.Collect the error log with return
collect core dump of process and file ddts if
value and core dump of the process
error is seen multiple times

Please collect console log of this message

and contact support.

An attempt to destroy a Mutex has failed,

decode the traceback and refer to the
below link before contacting [email protected]
http://wikicentral.cisco.com/display/NOSINF
RA/Defect+filing+guidelines+-+Checkpoint

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Analyze the restart failure and take

appropriate recovery action.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Process restart will resolve issue. Raw

segments are not being used so we can
ignore .

--

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Debug message only. No action required.

This message is to report state of process. --

Debug message only. No action required.

This message is to report state of process. --

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Chkpt uses single shared memory segment

per process to save all check pointed data.
In case of ISSU & iMDR, checkpont clients
need to decide whether chkpt need to
preserve this shared memory or delete it in
case there is a version change. When chkpt
init is called more than once from different
DLL within same process context, shared
Save the above error message. Note down memory reuse flag need to be consistent
the component ID from the above error
among all users within that process. If
message and open a DDTS against that
there is a conflict, it might lead to
component and attach this error message. unpredictable behavior in the component.

No action is required.

--

No action is required.

Informational message

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
An internal error - Report this to
Engineering. Use Topic to search for a
Collect system log information and forward similar DDTS. If you find none, write a
to technical support.
DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Determine why the process is running on

the destination node.

There are most likely duplicate copies of

the process running.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.
No action is required.
No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.
---

Collect system log information and copy

core file for offline analysis.
Communications debug (e.g. 'show tech
gsp') may also be useful.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Retry the operation . If error persits, Collect collect 'show tech-support ' and file ddts if
system log information and Contact TAC.
error is seen multiple times.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

None.

--

None.

--

Collect system log information if it appears

that this message is linked with failures in
functionality. Otherwise, the message can
be ignored.
--

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect system log information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

If this message is seen outside of an install

request, Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

This indicates a coding error in the

application that is using checkpoint. Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

The checkpointing software will periodically Report this to Engineering. Use Topic to
try again to set up the index structure. So, search for a similar DDTS. If you find none,
in general no action is required.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

An internal development error - Report this

to Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An internal error - Report this to

Engineering. Use Topic to search for a
Collect system log information. No action is similar DDTS. If you find none, write a
required.
DDTS for this problem.

No action is required.

An internal error - Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

An internal error - Report this to

Engineering. Use Topic to search for a
Collect system log information. No action is similar DDTS. If you find none, write a
required.
DDTS for this problem.
An internal error - Report this to
Engineering. Use Topic to search for a
Collect system log information. No action is similar DDTS. If you find none, write a
required.
DDTS for this problem.

Tcl script has thrown this message whose

filename is mentioned in the log. 1. If its a
customer written script, please get in touch
Please verify command(s) mentioned in tcl with customer to understand script. 2. If its
script prior to error message are working
a cisco provided script please verify if
fine (on router prompt). If issue is still seen command(s) in the script file which has
then please provide command details
resulted into this error message are
which has resulted into this error condition working fine on router prompt. 3. Contact
to technical support representative.
[email protected] for help.

Tcl script has thrown this message whose

filename is mentioned in the log. 1. If its a
customer written script, please get in touch
Please verify command(s) mentioned in tcl with customer to understand script. 2. If its
script prior to error message are working
a cisco provided script please verify if
fine (on router prompt). If issue is still seen command(s) in the script file which has
then please provide command details
resulted into this error message are
which has resulted into this error condition working fine on router prompt. 3. Contact
to technical support representative.
[email protected] for help.

Tcl script has thrown this message whose

filename is mentioned in the log. 1. If its a
customer written script, please get in touch
Please verify command(s) mentioned in tcl with customer to understand script. 2. If its
script prior to error message are working
a cisco provided script please verify if
fine (on router prompt). If issue is still seen command(s) in the script file which has
then please provide command details
resulted into this error message are
which has resulted into this error condition working fine on router prompt. 3. Contact
to technical support representative.
[email protected] for help.

Tcl script has thrown this message whose

filename is mentioned in the log. 1. If its a
customer written script, please get in touch
Please verify command(s) mentioned in tcl with customer to understand script. 2. If its
script prior to error message are working
a cisco provided script please verify if
fine (on router prompt). If issue is still seen command(s) in the script file which has
then please provide command details
resulted into this error message are
which has resulted into this error condition working fine on router prompt. 3. Contact
to technical support representative.
[email protected] for help.

Tcl script has thrown this message whose

filename is mentioned in the log. 1. If its a
customer written script, please get in touch
Please verify command(s) mentioned in tcl with customer to understand script. 2. If its
script prior to error message are working
a cisco provided script please verify if
fine (on router prompt). If issue is still seen command(s) in the script file which has
then please provide command details
resulted into this error message are
which has resulted into this error condition working fine on router prompt. 3. Contact
to technical support representative.
[email protected] for help.

Tcl script has thrown this message whose

filename is mentioned in the log. 1. If its a
customer written script, please get in touch
Please verify command(s) mentioned in tcl with customer to understand script. 2. If its
script prior to error message are working
a cisco provided script please verify if
fine (on router prompt). If issue is still seen command(s) in the script file which has
then please provide command details
resulted into this error message are
which has resulted into this error condition working fine on router prompt. 3. Contact
to technical support representative.
[email protected] for help.

Tcl script has thrown this message whose

filename is mentioned in the log. 1. If its a
customer written script, please get in touch
Please verify command(s) mentioned in tcl with customer to understand script. 2. If its
script prior to error message are working
a cisco provided script please verify if
fine (on router prompt). If issue is still seen command(s) in the script file which has
then please provide command details
resulted into this error message are
which has resulted into this error condition working fine on router prompt. 3. Contact
to technical support representative.
[email protected] for help.

Tcl script has thrown this message whose

filename is mentioned in the log. 1. If its a
customer written script, please get in touch
Please verify command(s) mentioned in tcl with customer to understand script. 2. If its
script prior to error message are working
a cisco provided script please verify if
fine (on router prompt). If issue is still seen command(s) in the script file which has
then please provide command details
resulted into this error message are
which has resulted into this error condition working fine on router prompt. 3. Contact
to technical support representative.
[email protected] for help.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

The command 'show watchdog trace' will

display additional information about the
potential CPU hog. If the hog is persistant,
contact technical support. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

The command 'show watchdog trace' will

display additional information about the
potential CPU hog. If the hog is persistant,
contact technical support. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

The command 'show watchdog trace' will

display additional information about the
potential CPU hog. If the hog is persistant,
contact technical support. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

The command 'show watchdog trace' will

display additional information about the
potential CPU hog. If the hog is persistant,
contact technical support. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

The indicated disk device may be running

out of space. Determine if there are
unneeded files on the disk.

--

The indicated disk device may be running

out of space. Determine if there are
unneeded files on the disk.

--

The indicated disk device may be running

out of space. Determine if there are
unneeded files on the disk.

--

The indicated disk device may be running

out of space. Determine if there are
unneeded files on the disk.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Collect all logs, especially those from

resmon. Also collect output from 'show
watchdog trace'. Forward the messages to
technical support.
-Collect all logs, especially those from
wdsysmon. Also collect output from 'show
watchdog trace'. Forward the messages to
technical support.
-The indicated disk device may be running
out of space. Determine if there are
unneeded files on the disk.

--

The indicated disk device may be running

out of space. Determine if there are
unneeded files on the disk.

--

The indicated disk device may be running

out of space. Determine if there are
unneeded files on the disk.

--

The indicated disk device may be running

out of space. Determine if there are
unneeded files on the disk.

--

Collect all logs, especially those from

wdsysmon. Also collect output from 'show
watchdog trace'. Forward the messages to
technical support.
-Collect all logs, especially those from
resmon. Also collect output from 'show
watchdog trace'. Forward the messages to
technical support.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Investigate memory usage on this node. It

may be necessary to unconfigure some
applications or move them to a different
node. In the case of memory leaks,
technical support may need to be
contacted.
-Investigate memory usage on this node. It
may be necessary to unconfigure some
applications or move them to a different
node. In the case of memory leaks,
technical support may need to be
contacted.
--

The system will collect data about the

process before it is killed. Collect this data
and forward it to technical support. Most
likely, there is a memory leak in the
process.
-The system will collect data about the
process before it is killed. Collect this data
and forward it to technical support. Most
likely, there is a memory leak in the
process.
-If the free memory state is Severe or
Critical, investigate memory usage on this
node. It may be necessary to unconfigure
some applications or move them to a
different node. In the case of memory
leaks, technical support may need to be
contacted.
-If the free memory state is Severe or
Critical, investigate memory usage on this
node. It may be necessary to unconfigure
some applications or move them to a
different node. In the case of memory
leaks, technical support may need to be
contacted.
--

Collect system log information. Contact

technical support if the problem is not a
misconfiguration.

--

Collect system log information. Contact

technical support if the problem is not a
misconfiguration.

--

Collect the data from the following

messages and attempt to determine what
is driving memory usage. Forward the
messages to technical support.

--

Collect the data from the following

messages and attempt to determine what
is driving memory usage. Forward the
messages to technical support.

--

Collect system log information. Contact

technical support if the problem is not a
misconfiguration.

--

Collect system log information. Contact

technical support if the problem is not a
misconfiguration.

--

Collect the data from the following

messages and attempt to determine what
is driving memory usage. Forward the
messages to technical support.

--

Collect the data from the following

messages and attempt to determine what
is driving memory usage. Forward the
messages to technical support.

--

The debugging information collected when

an event manager stopped sending
heartbeats should be examined and
provided to technical support for analysis. -The debugging information collected when
an event manager stopped sending
heartbeats should be examined and
provided to technical support for analysis. -Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Wdsysmon has detected that an event

manager is no longer sending keepalive
heartbeats. The message provides
information about where the event
manager was created. A debug script will
run and collect information about the
process and the state of the router. The
output will be in a directory
[/disk1:|/disk0:|/bootflash:|/tmp]/resmon_de
bug/debug.*
--

Wdsysmon has detected that an event

manager is no longer sending keepalive
heartbeats. The message provides
information about where the event
manager was created. A debug script will
run and collect information about the
process and the state of the router. The
output will be in a directory
[/disk1:|/disk0:|/bootflash:|/tmp]/wdsysmon
_debug/debug.*
-The debugging information collected when
the event manager stopped sending
heartbeats should be examined and
provided to technical support for analysis. -The debugging information collected when
the event manager stopped sending
heartbeats should be examined and
provided to technical support for analysis. -The debugging information collected when
the event manager stopped sending
heartbeats should be examined and
provided to technical support for analysis. -The debugging information collected when
the event manager stopped sending
heartbeats should be examined and
provided to technical support for analysis. --

Check the system status, including the

saved log for evidence of a high priority
cpu hog.

--

Check the system status, including the

saved log for evidence of a high priority
cpu hog.

--

Check the system status, including the

saved log for evidence of a high priority
cpu hog.

--

Check the system status, including the

saved log for evidence of a high priority
cpu hog.

--

Check the system status, including the

saved log for evidence of a high priority
cpu hog.

--

Check the system status, including the

saved log for evidence of a high priority
cpu hog.

--

The command 'show watchdog trace' will

display additional information about the
potential CPU hog. If the hog is persistant,
contact technical support. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

The command 'show watchdog trace' will

display additional information about the
potential CPU hog. If the hog is persistant,
contact technical support. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
-The indicated disk device may be running
out of space. Determine if there are
unneeded files on the disk.

--

The indicated disk device may be running

out of space. Determine if there are
unneeded files on the disk.

--

If the disk is used for critical tasks, monitor

the disk usage and take corrective action. --

If the disk is used for critical tasks, monitor

the disk usage and take corrective action. -Examine the dump information for possible
root-cause for a previous reset. Use the
wd_test utility.
-Examine the dump information for possible
root-cause for a previous reset. Use the
wd_test utility.
-The command 'show watchdog trace' will
display additional information about the
process. Forward this information to
technical support.

--

The command 'show watchdog trace' will

display additional information about the
process. Forward this information to
technical support.

--

The command 'show watchdog trace' will

display additional information about the
potential CPU hog. If the hog is persistant,
contact technical support. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

The command 'show watchdog trace' will

display additional information about the
potential CPU hog. If the hog is persistant,
contact technical support. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
-Re-configure this node with more physical
memory

--

Re-configure this node with more physical

memory

--

The system is critically short of memory.

Automatic recovery will attempt to stabilize
the system, but there is either a memory
leak or a misconfiguration. Both require
operator intervention.
--

The system is critically short of memory.

Automatic recovery will attempt to stabilize
the system, but there is either a memory
leak or a misconfiguration. Both require
operator intervention.
--

The system is critically short of memory.

Automatic recovery will attempt to stabilize
the system, but there is either a memory
leak or a misconfiguration. Both require
operator intervention.
--

The system is critically short of memory.

Automatic recovery will attempt to stabilize
the system, but there is either a memory
leak or a misconfiguration. Both require
operator intervention.
-The system is critically short of memory.
Automatic recovery will attempt to stabilize
the system, but there is either a memory
leak or a misconfiguration. Both require
operator intervention.
-The system is critically short of memory.
Automatic recovery will attempt to stabilize
the system, but there is either a memory
leak or a misconfiguration. Both require
operator intervention.
--

Collect all logs, especially those from

wdsysmon. Also collect output from 'show
watchdog trace'. Forward the messages to
technical support.
--

Collect all logs, especially those from

resmon. Also collect output from 'show
watchdog trace'. Forward the messages to
technical support.
--

Collect system log information. Contact

technical support if the problem is not a
misconfiguration.

--

Collect system log information. Contact

technical support if the problem is not a
misconfiguration.

--

Collect the data from the following

messages and attempt to determine what
is driving memory usage. Forward the
messages to technical support.

--

Collect the data from the following

messages and attempt to determine what
is driving memory usage. Forward the
messages to technical support.

--

Collect system log information. Contact

technical support if the problem is not a
misconfiguration.

--

Collect system log information. Contact

technical support if the problem is not a
misconfiguration.

--

Collect the data from the following

messages and attempt to determine what
is driving memory usage. Forward the
messages to technical support.

--

Collect the data from the following

messages and attempt to determine what
is driving memory usage. Forward the
messages to technical support.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Here Shelf Manager should receive a

critical alarm from HA Health Monitor for
this error. The node should be reset by
Shelf Manager. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If problem persist, it indicates the bad hw

in the system. Please contact TAC for fault
isolation. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
--

The System Manager process (sysmgr) will

automatically respawn this process, up to a
fixed number of times when this error is
encountered, to recover. Execute 'show
process hm location <>' to verify that the
process is up and running. If it is still nonoperational, try doing 'process restart hm
location <>' If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Search the event logs for events/errors

related to the failure reason Checkpointing
and Server failures are part of the overall
system. If there are failures here then other
processes maybe complaining as well.

No action is required because HA Health

Monitor will retry Fabric ping again

--

No action is required because HA Health

Monitor will retry Fabric ping again

--

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Contact support.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

For some reason, memory allocation failed.

Probably the system is in low mem
If the message recurs, copy the error
condition. System can recover from low
message exactly as it appears on the
memory if the held memory is freed. If the
console or in the system log, call your
problem persists,Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem..

Contact TAC with required info

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Contact TAC.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect the console log, perform the

recovery action describes below.

Collect console log and the following

information. - show platform summary
Recovery Action: do 'process restart
invmgr', if the issue still exists, do 'hwmodule location reload' from the admin
mode. if the above recovery actions can
not resolve the issue, Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

For some reason, Registration of DLL failed.

Must be a problem in LRD library.Report
this to Engineering. Use Topic to search for
Try restarting the process to recover. If the a similar DDTS. If you find none, write a
issue is still seen contact TAC.
DDTS for this problem.

Contact TAC with required info

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Contact support.

*ddts*

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Contact support.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Contact support.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Contact support.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Contact TAC with required info

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Collect system log information.

If the error message indicate 'UnKnown

card type', Collect the console log and the
following information - show diag eeprominfo - show diag eeprom-info raw while
indicates the nodieid detected with
'unknown card type' Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Verify the card type in the slot being

configured as primary for the SDR. If not a
DRP or RP card, please replace with valid
card type.

It is allowed to configure non-RP/non-DRP

node as primary for the SDR. If this
WARNING is seen please verify the card
type in the slot being configured as primary
for the SDR.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

None.

--

None.

--

It is allowed to add an unpaired DRP to an

Debug message only. No action is required. SDR.

If any of these messages recur, call your

technical support representative for
assistance.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

If any of these messages recur, call your

technical support representative for
assistance.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

Contact support.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

If any of these messages recur, call your

technical support representative for
assistance.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

If any of these messages recur, call your

technical support representative for
assistance.

API to register node state change failed. If

the problem persists,Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. Please collect traces
mentioned in http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

Make sure that the event chosen is the

right one.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

If any of these messages recur, call your

technical support representative for
assistance.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

If any of these messages recur, call your

technical support representative for
assistance.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

If any of these messages recur, call your

technical support representative for
assistance.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

If any of these messages recur, call your

technical support representative for
assistance.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

If any of these messages recur, call your

technical support representative for
assistance.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

If any of these messages recur, call your

technical support representative for
assistance.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

For some reason, memory allocation failed.

Probably the system is in low mem
condition. System can recover from low
memory if the held memory is freed. If the
problem persists, Please collect traces
If the message recurs, copy the error
mentioned in http://wwwinmessage exactly as it appears on the
eng.cisco.com/Eng/OIBU/WWW/sprsgconsole or in the system log, call your
triage/material/ha-lrd.html Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.
Contact support.

*ddts*

Contact support.

*ddts*

Contact support.

*ddts*

If any of these messages recur, call your

technical support representative for
assistance.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

If any of these messages recur, call your

technical support representative for
assistance.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwineng.cisco.com/Eng/OIBU/WWW/sprsgtriage/material/ha-lrd.html

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwinMake sure that the debug option chosen is eng.cisco.com/Eng/OIBU/WWW/sprsgthe right one.
triage/material/ha-lrd.html

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please
collect the traces mention in the wiki link
http://wwwinMake sure the value of lr ID is in the correct eng.cisco.com/Eng/OIBU/WWW/sprsgrange.
triage/material/ha-lrd.html
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Make sure the dSDRSC is up.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect system log information, show
Cisco technical support representative and platform in admin mode, show run in admin
provide the representative with the
mode, /tmp/lrd.log file from the node on
gathered information.
which the message is seen and contact DE.
Please collect the traces mention in the
If the message recurs, copy the error
wiki link http://wwwinmessage exactly as it appears on the
eng.cisco.com/Eng/OIBU/WWW/sprsgconsole or in the system log, call your
triage/material/ha-lrd.html Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Contact TAC.

The management node that has come up

late may need to be used. If it is needed
then run the command - 'placement
reoptimize'. This ensures that processes
are placed on the new management node
for optimal performance.

Collect the function name and traceback

Report this to Engineering. Use Topic to
information and forward to your next level search for a similar DDTS. If you find none,
of technical support. No action is required. write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Report this to Engineering. Use Topic to
Collect system log information. No action is search for a similar DDTS. If you find none,
required.
write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Since such an error indicates an

initialization failure, it is suggested that the
'show logging' is collected and double
checked that these errors are existing
there. Also process restart of redstatsd
process is suggested to see if that would
help in overcoming these initialization
issues.
--

Since such an error indicates an

initialization failure, it is suggested that the
'show logging' is collected and double
checked that these errors are existing
there. Also process restart of redstatsd
process is suggested to see if that would
help in overcoming these initialization
issues.

Collect the 'show redundancy statistics

trace'. The console log errors have
corresponding traces as well. Pass on the
console log errors corresponding to the
redstatsd proces and the ltraces to the DE
to analyze the issue further.

Collect the function name and traceback

Report this to Engineering. Use Topic to
information and forward to your next level search for a similar DDTS. If you find none,
of technical support. No action is required. write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This means failure in shared memory init or

mmap. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem..

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A system call for sysdb might have failed. If

sysdb system calls are failing only for this
component, then this issue should be
triaged by critical-mon component. If
similar issues are seen with other
components too, then this issue should be
triaged by sysdb component.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Currently the equivalent is not

implemented in IOS-XR, only in the admin
plane. This needs to be fixed ASAP. This is
an internal software inconsistency. Reboot
or restart is not expected to fix this
problem. Force co-location of all services to
the nodes advertising the service until a
more robust fix is made available. Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

Check the backbone interfaces.

--

No action is required.

--

No action is required.

--

If the state change was unexpected,

confirm the configuration settings for the
interface.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The number in brackets is the return code

from one of the
ipv4_rib_batch_buffer_TYPE() functions.

sysmgr will try to restart the RGMGR

process. If it cannot be restarted it is a fatal
condition. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information. *REDUCE*
--

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration.. The number in brackets is the return code
Restart the RGMGR process. *RECUR*
from 'ipv4_rib_batch_buffer_send'

If the message recurs, copy the error

See
message exactly as it appears on the
http://enwiki.cisco.com/SlaInfrastructure for
console or in the system log, call your
SLA debugging details. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

See
message exactly as it appears on the
http://enwiki.cisco.com/SlaInfrastructure for
console or in the system log, call your
SLA debugging details. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

This indicates a low-memory condition.

Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.
The Client Library will attempt to resync
itself with the Profile Manager or an
See
immmediate resync can be attempted by http://enwiki.cisco.com/SlaInfrastructure for
reconfiguring the profile.
SLA debugging details.

This indicates a low-memory condition.

Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.
To resume normal operation, reconfigure
the profile and the SLA Client Library will
See
resync itself with the Profile Manager and http://enwiki.cisco.com/SlaInfrastructure for
setup the operations.
SLA debugging details.

This indicates a low-memory condition.

Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.
The Client Library will attempt to resync
itself with the Profile Manager or an
See
immmediate resync can be attempted by http://enwiki.cisco.com/SlaInfrastructure for
reconfiguring the profile.
SLA debugging details.

This indicates a low-memory condition.

Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.
The Client Library will attempt to resync
itself with the Profile Manager or an
See
immmediate resync can be attempted by http://enwiki.cisco.com/SlaInfrastructure for
reconfiguring the profile.
SLA debugging details.

If the message recurs, copy the error

See
message exactly as it appears on the
http://enwiki.cisco.com/SlaInfrastructure for
console or in the system log, call your
SLA debugging details. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

See
message exactly as it appears on the
http://enwiki.cisco.com/SlaInfrastructure for
console or in the system log, call your
SLA debugging details. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

See
message exactly as it appears on the
http://enwiki.cisco.com/SlaInfrastructure for
console or in the system log, call your
SLA debugging details. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

The system may recover automatically. If

the problem persists, it may be possible to
recover by restarting the protocol process
on the affected node.

This indicates a system problem with interthread LWM messaging. See

http://enwiki.cisco.com/SlaInfrastructure for
SLA debugging details.

If unexpected behaviour is seen, the

system may be recovered by restarting the
protocol process on the affected node. If
the problem persists, Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

If the error string indicates an attempt to

acquire a mutex when already held, or
release a mutex when not held, then this
indicates a bug. Please capture all the info
and pass it to Engineering. Otherwise, this
likely indicates a system problem. See
http://enwiki.cisco.com/SlaInfrastructure for
SLA debugging details.

Manually clear the on demand operation

via a manageability view (CLI, XML etc). If
the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and See
provide the representative with the
http://enwiki.cisco.com/SlaInfrastructure for
gathered information.
SLA debugging details.

If the message recurs, copy the error

See
message exactly as it appears on the
http://enwiki.cisco.com/SlaInfrastructure for
console or in the system log, call your
SLA debugging details. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.
This indicates a system problem with
The system may recover automatically. If
sending a pulse from one thread to another
the problem persists, it may be possible to (or to itself). See
recover by restarting the protocol process http://enwiki.cisco.com/SlaInfrastructure for
on the affected node.
SLA debugging details.

No further action is needed. However, if

the problem persists, it may be possible to
recover by restarting the protocol process
on the affected node.

This likely indicates a system problem such

as low memory. See
http://enwiki.cisco.com/SlaInfrastructure for
SLA debugging details.

The system may recover automatically. If

the problem persists, check for network
connectivity problems. The problem can be
avoided by using shorter probes.
--

If configuration fails to apply, recommitting

it should correct the issue. If the message
recurs, copy the error message exactly as it See
appears on the console or in the system
http://enwiki.cisco.com/SlaInfrastructure for
log, call your Cisco technical support
SLA debugging details. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

See
http://enwiki.cisco.com/SlaInfrastructure for
SLA debugging details. Report this to
If unexpected behaviour is seen, it may be Engineering. Use Topic to search for a
possible to recover by restarting the
similar DDTS. If you find none, write a
protocol process on the affected node.
DDTS for this problem.

Reconfigure the profile to remove or

change the invalid configuration such that
it becomes valid.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

The Client Library will attempt to resync

itself with the Profile Manager or an
immmediate resync can be attempted by
reconfiguring the profile when there are no
process restart events occuring. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
See
representative with the gathered
http://enwiki.cisco.com/SlaInfrastructure for
information.
SLA debugging details.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Check NVRAM filesystem. Copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Check NVRAM filesystem. Copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Reduce size of boot variable. e.g., remove

extra boot system commands, and try
again. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

'NULL pointer passed to the function which

processes file path of PIE.' 'Retry the
'Retry the 'show' command or 'install'
operation.' 'If the error is encountered even
operation.' 'Even after few tries,if the error after couple of tries,' 'restart the 'instdir'
is seen, ' 'restart the 'instdir' process from process to free any unused stack.' 'If the
exec mode and retry the operation.'
error is still seen collect 'show tech install'
'Contact TAC if not resolved.'
and 'show memory'' 'raise a DDTS.'

This indicates insufficient space on the

reporting node's persistent boot device.
This may be a temporary condition caused
by an accumulation of old core files and
files created by users. If so, then locate and
remove all such files on the device and
reload the node. The problem may also be
due to a non-critical process that is
continually crashing and generating fresh
core files. Check 'show context' and the log
to see if there are any such processes and
work to resolve the root problem before
cleaning and reloading. The problem may
also simply be that the device cannot
support the requests of the user.
Specifically, the combination of
configurations that are set and the number
of packages on the device may exceed the
This indicates a low resource condition.
space available on the device. Check for
Remove non-critical files, such as core files old, inactive packages that can be safely
and user-created files, and reload the node removed. Also check for SMUs which have
to re-sync its files. If problem persists, Copy been superceded by other SMUs, but that
the error message exactly as it appears on are still active and try to deactivate them.
the console or in the system log, call your This will remove them from managed
Cisco technical support representative and nodes (e.g., LCs) where they are active as
provide the representative with the
well as making them inactive, and hence
gathered information.
candidates for removal.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Wait for the dSDRSC to become available. If

this node is supposed to become the
dSDRSC then it is missing software that it
requires to operate in which case the node
should be moved into the Owner SDR and
then recarved into a separate SDR.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The operation, error value and the error

string should be examined to determine
what may have caused insthelper to exit.
Using these three information to diagnose
the cause.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the node does not come up then this

node will not be usable and will be
reloaded automatically to recover. If it does
not recover, then the missing package
should be added to the router using 'install
add' in admin mode so that it is available
to be synced, or alternatively the missing
package can be removed from the router
using 'install remove' in admin mode so
that it is not required to be synced. If the
node does come up as the dSDRSC then
check the packages present on the
SDR/router using 'show install package all
brief' and add any missing packages to the
SDR/router as required.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Find out which files/directories can be

removed from the disk (ex: disk0:, disk1:,
bootflash:), and remove them by either
attaching to that node or removing them
over qnet. Restart insthelper if needed.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check to see if the install device displayed

in this ios_msg is available on this node. If
not, add in a new device that matches the
install device as dSC. If the device is a
brand new device, format once prior to
using it. If the required install device is
actually available, but did not become
ready, why the device did not become
ready will need to be tracked down. It's
possible that formatting an unavailable
device may restore its functionality. If an
aux port is available, a format can be
performed with the command
flash_command format where is the 'install
device' mentioned above. This should be
followed by reloading the affected node to
try using it. The latest software will
automatically try formatting bootflash for
managed nodes, and a message should be
sent to that effect.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Find out which files/directories can be

removed from the disk (ex: disk0:, disk1:,
bootflash:), and remove them by either
attaching to that node or removing them
over qnet.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

This indicates a low memory condition.

Reduce other system activity to ease
Memory on the box must be running low memory demands. If conditions warrant,
are there services that can be stopped, or
upgrade to a larger memory configuration. can more memory be added?

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The likely reason for this warning message

is that the node is running software from
memory as the preferred persistent device
may be corrupt or unavailable. Please
check the logs for messages about flash
devices (e.g. bootflash:) on the node. Look
for messages relating to crruption,
unreadable, unwritable etc. Formatting the
persistent device used by the node may
clear the problem if the device is present.
The node will need to be reloaded for the
change to take effect. For example, for
managed nodes such as SPs and LCs, try:
'format bootflash: ' followed by 'process
restart insthelper '. The node should reload
on its own if the problem is fixed by
formatting, otherwise the message will
come back and the card will need factory
repair.'

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The likely reason for this warning message

is that the node is running software from
memory as the preferred persistent device
may be corrupt or unavailable. Please
check the logs for messages about flash
devices (e.g. bootflash:) on the node. Look
for messages relating to corruption,
unreadable, unwritable etc. Formatting the
persistent device used by the node may
clear the problem if the device is present.
The node will need to be reloaded for the
change to take effect. For example, for
managed nodes such as SPs and LCs, try:
'format bootflash: ' followed by 'process
restart insthelper '. The node should reload
on its own if the problem is fixed by
formatting, otherwise the message will
come back and the card will need factory
repair.'

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

User has booted a *second* membooted

composite on the system. The dSC is
already running - somewhere - and will not
tolerate another composite image being
booted elsewhere. insthelper has detected
this, and will halt further booting of the
node. It will need to be reloaded with the
correct image, usually an MBI.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

During turboboot, this message indicates

an effort to recover a corrupted device - or
possibly that a new FFS is now in use, and
the device *appears* corrupted. In a
steady-state system, it means the device
became corrupted, and insthelper is now
trying to recover it for regular use.

No action needed.

--

The node will pause and then reboot to

obtain the correct software. If the node
ends in ROMMON (as the config-register
was not set to auto-boot) then it is
recommended to simply set the configregister to autoboot and reset to boot the
correct software. unset BOOT sync confreg
0x2 reset
--

The node will reboot to obtain the correct

software. If the node ends in ROMMON (as
the config-register was not set to autoboot) then it is recommended to simply set
the config-register to autoboot and reset to
boot the correct software. unset BOOT sync
confreg 0x2 reset
--

No action is required.

--

The node will reboot to pick up the new

mbi. If the node ends in ROMMON (as the
config-register was not set to auto-boot)
then it is recommended to simply set the
config-register to autoboot and reset to
boot the correct MBI.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

--

No action is required.

--

No action is required.

A reload node installation has been

targetted at this node. The node should
reload and return with the new installed
software.

No action is required.

--

Collect insthelper traces from this reported

nodes using 'show install trace insthelper'.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.
No action is required.

--

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

--

No action is required.

Check that the LRd inventory is correct and

that SDS candidate nodes (heads of racks,
dLRSCs, the dSC, and their standbys) are
running.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

If this error condition persists then try to

check sysdb existence on this node.
Reloading the node may correct the
problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect insthelper traces from this reported

nodes using 'show install trace insthelper'.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

--

Contact support.

Coding error.

No action is required.

--

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action needed.

--

No action is required.

--

No action is required.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
-This indicates a low memory condition.
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Contact support.

Coding error.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

The software running on this node will be

inconsistent, and the system's stability will
be in question. The outcome of future
process restarts is undetermined, as they
may or may not cause the currently active
software to be restarted or the software
that was requested by the install. A reload
of this node should be performed to get the
software into a consistent state. Report this
to Engineering. Use Topic to search for a
Execute the command 'hw-module location similar DDTS. If you find none, write a
<location> reload' for the specified node. DDTS for this problem.

After the installation check that the router's

configuration is complete. Reconfigure if
necessary.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

In the case where we are unable to send

out a full update of state files to remote
nodes, reload the dSC to allow the
synchronization to retry. It is recommended
that the router have a standby RP to
prevent chassis reload during this process
and minimize any impact on service. In the
case where the dSC was unable to
download more recent files from a remote
node, reload both the dSC and the node in
question to allow the synchronization to
retry. Again, a standby RP to failover to
would be desirable to prevent the chassis
from reloading. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

--

No action is required..

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Insthelper failed to respond to instdir.

Instdir will notice this and after a timeout
attempt to re-retrieve the response from
insthelper. If this recovery works, then
there will be no problem. If the recovery
doesn't work then the standard install
output will inform the user of the failure,
and appropriate action should be taken.
Please obtain the file generated by show
tech-support install file. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem..

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A message type received by insthelper was

of an unknown type. This either indicates a
message / memory corruption or a coding
error. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Repeat the operation. Consult the releasenotes if applicable.

-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

User error. The user has requested a reload

installation on a membooted management
node. Please note this error should only be
outputted in the development environment
Either diskboot, or don't target installation (Customers are always expected to be disk
to a management node when membooted. booted).

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

The software running on the dSC node will

be inconsistent. Reloading the entire router
Execute the command 'hw-module location should return the software to the
<location> reload' for the specified node. committed state.

No action is required.

--

Check system consistency using 'install

verify'. If incorrect behavior is seen then
restart processes impacted by the install on
the inconsistent nodes (use 'show install
log <install ID> detail' for a list of
impacted processes). If incorrect behavior
continues to be seen then reload the
inconsistent nodes. Collect diagnostic
information about the failure using the
specific command and pass it to your TAC
representative. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
--

Check system consistency using 'install

verify'. If incorrect behavior is seen then
restart processes impacted by the install on
the inconsistent nodes (use 'show install
log <install ID> detail' for a list of
impacted processes). If incorrect behavior
continues to be seen then reload the
inconsistent nodes. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

Check system consistency using 'install

verify'. If incorrect behavior is seen then
restart processes impacted by the install on
the inconsistent nodes (use 'show install
log <install ID> detail' for a list of
impacted processes). If incorrect behavior
continues to be seen then reload the
inconsistent nodes. Collect diagnostic
information about the failure using the
specific command and pass it to your TAC
representative. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
--

Check system consistency using the admin

command 'install verify'. If incorrect
behavior is seen then reload the
inconsistent nodes using 'hw-module
location <location> reload'. Collect
diagnoistc information about the failure
using the admin command 'show techsupport install file <file>' and pass it to
TAC representative.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Collect '(admin)#show tech-support install'

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

Collect '(admin)#show tech-support install'

Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

Something must have happened such that

the previous installation was not completed
successfully. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

No action is required.

Something must have happened such that

the install add operation was not
completed successfully. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

--

Contact support.

Coding error.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Please obtain the file generated by show

tech-support install file. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Please obtain the file generated by show

tech-support install file. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Do '(admin) install attach <install_id>',

then answer the question.

--

Check system consistency using 'install

verify'. Reattempt the install operation. If
the problem persists collect diagnostic
information about the failure using the
specific command and pass it to your TAC
representative. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

--

Check system consistency using 'install

verify'. Reattempt the install operation.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Check system consistency using 'install

verify'. Reattempt the install operation. If
the problem persists collect diagnostic
information about the failure using the
specific command and pass it to your TAC
representative. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

--

Steps to correct the error are provided in

'show install log <install ID> detail'. Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

Check system consistency using 'install

verify'. If the problem persists collect
diagnostic information about the failure
using the specific command and pass it to
your TAC representative. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

Check system consistency using 'install

verify'. If the problem persists collect
diagnostic information about the failure
using the specific command and pass it to
your TAC representative. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

Check system consistency using 'install

verify'. If the problem persists collect
diagnostic information about the failure
using the specific command and pass it to
your TAC representative. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect '(admin)#show tech-support install'

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

Collect '(admin)#show tech-support install'

Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

The reload event of SPA should be

investigated after the ISSU operation if it
was not triggered by user using 'hwmodule location <node> reload' command.

The error indicates that the reported SPA is

not ISSU supported. It would be
automatically powered-up after ISSU
operation is complete. No action is
required.

The error indicates that the reported SPA is

The reload event of SPA should be
not ISSU supported. It would be
investigated after the ISSU operation if it
automatically powered-up after ISSU
was not triggered by user using 'hwoperation is complete. No action is
module location <node> reload' command. required.

Collect 'show-tech spa location

<spa_location>' for this problem. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Collect 'show-tech spa location ' for this

problem. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Collect 'show-tech spa location

<spa_location>' for this problem. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Collect 'show-tech spa location ' for this

problem. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

This indicates a low memory condition.

Once the memory condition has been
rectified, run the install operation again.
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -This indicates a low memory condition.
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

--

No action is required.

--

Verify that the system is operating as

expected. Use 'system verify' to help
validate the system. Use 'install verify' to
validate the install sub-system. If the
system is operating as expected then
execute the 'install commit' command to
commit the active software so that it is
used if the system reboots.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

Reload each node in the list manually from

admin mode.
--

Do 'install resume' in admin mode,

whenever ready.

--

No action is required.

--

Details of the possibly unexpected

behavior are provided in 'show install log
<install ID> detail'. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

No action is required.

--

Debug message only. No action is required. --

Debug message only. No action is required. --

No action is required.

--

No action is required.

--

No action is required.

--

Clear some of the install history logs from

previous upgrade scenarios. Use (admin)
'show install log' to determine which logs
are from previous upgrade scenarios, and
then use the command (admin) 'clear
install log-history oldest <>' to delete the
oldest sets of logs. If this message is still
seen after the clear operation, then more
logs must be deleted.

--

No action is required.

Check lrd ltrace to see why the API call

returns EAGAIN. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

Retry the operation. Copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

Retry the operation. Copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

Debug message only. No action is required. --

No action is required.

Install infrastructure will detect reload and

take recovery action during ISSU/iMDR. The
reason for reload of the service processor
should be investigated separately.

No action is required.

Install infrastructure will detect reload and

take recovery action during ISSU/iMDR. The
reason for reload of the service processor
should be investigated separately.

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

Unfreeze the ISSU state machine using run

ismdbg -T or clear the freezing using run
ismdbg -C.
--

No action is required.

--

No action is required.

--

No action is required.

--

Either follow the command given, or attach

to the operation synchronously for further
details.
--

Either follow the command given, or attach

to the operation synchronously for further
details.
--

No action is required.

--

No action is required.

--

No action is required.

--

Repeat the operation. Consult the releasenotes if applicable.

-Repeat the operation. Consult the releasenotes if applicable.
-Repeat the operation. Consult the releasenotes if applicable.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Use the syslogs for success/failure of the

operation.

--

Contact support.

Coding error.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Please obtain the file generated by show

tech-support install file. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

The client must delete the request in order

for it to be removed.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. Run 'install verify repair' on RP
and DRP nodes.
--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. Run 'install verify repair' on
the source node.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. Run 'install verify repair' on RP
and DRP nodes.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

This indicates a low memory condition.

Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Contact support.

Coding error.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.'
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

To be filled in later

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Upgrade to the latest version of the

package or of the Install tools

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Upgrade to the latest version of the

package or of the Install tools

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Restart the process to let it attempt to

recover from this initialisation failure.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Restart the process to let it attempt to

recover from this initialisation failure.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Restart the process to let it attempt to

recover from this initialisation failure.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Restart the process to let it attempt to

recover from this initialisation failure.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Restart the process to let it attempt to

recover from this initialisation failure.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Restart the process to let it attempt to

recover from this initialisation failure.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

It may help to restart the process issuing

the message. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

It may help to restart the process issuing

the message. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

It may help to restart the process issuing

the message. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

It may help to restart the process issuing

the message. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Reduce other system activity to ease

Memory on the box must be running low memory demands. If conditions warrant,
are there services that can be stopped, or
upgrade to a larger memory configuration. can more memory be added?
Reduce other system activity to ease
Memory on the box must be running low memory demands. If conditions warrant,
are there services that can be stopped, or
upgrade to a larger memory configuration. can more memory be added?
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Has the correct set of operations been

carried out? Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Has the correct set of operations been

carried out? Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

It may help to restart the process issuing

this message. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

It may help to restart the process issuing

this message. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.'
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.'
write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.'

This may be the precursor to some other

problem, but on its own it is not a bug.'

No action is required.'

This may be the precursor to some other

problem, but on its own it is not a bug.'

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Coding error.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

'Try restarting the 'instdir' process to

recover. ' 'From exec mode - 'process
restart instdir'' 'If the issue is still seen
contact TAC.'

'Internal pthread call returned error.'

'Restart the 'instdir' process and retry.' 'If it
doesn't solve the issue, raise a DDTS' 'with
'show tech install' output.'

'Traces will not function properly. It is safer

to ' 'recover by restarting 'instdir'
process;instead of ' 'ignoring this error.
Restoring the traces helps in ' 'debugging
any future issues. ' 'For restarting; from
exec mode - 'process restart instdir'' 'If
restarting the process doesn't resolve this
error,' 'contact TAC.'

'Trace initialisation failed. Not critical for

install ' 'infrastructure. But will be
problematic for ' 'debugging and
information collection in later stage.'
'Restart the 'instdir' process and check for
errors.' 'If restart doesn't solve the issue
raise a DDTS' 'with 'show tech install'
traces'

Try to re-acquire the pie files from the cisco

respository referred to you. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Check if the pie being installed is

truncated/corrupted. If problem persists,
Collect info as per the checklist given at
http://wikicentral.cisco.com/display/GROUP/
Bug+raising+and+Forwarding+criteria

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

*SUPPORT*

*DDTS*

*SUPPORT*

The ignore commit ldpath file is used at

boot time to determine what installed
software should be booted. The current
logic for this file is if the file is present then
the non-committed loadpath is used (the
active loadpath before the node reloaded),
and if the file is not present then the
committed loadpath is used. This is used
for installations that require node reloads,
to enable a temporary loadpath to persist
across node reloads. This failure to delete
the ignore commit ldpath file, means that
at the next node reload the non-committed
loadpath will again be used, instead of
reverting to the committed loadpath.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Retry the command.If it fails, retry the

command after restarting the 'instdir'
process. Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Try the steps in recommended action. If it

does not help, Please collect info according
to the checklist given at
http://wikicentral.cisco.com/display/GROUP/
Bug+raising+and+Forwarding+criteria

*NONE*

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Upgrade to latest OS release. Check for

unsupported hardware.

Hardware, packaging or coding error.

Upgrade to latest OS release. Check for

unsupported hardware.

Hardware, packaging or coding error.

This indicates a low memory condition.

Reduce other system activity to ease
Memory on the box must be running low memory demands. If conditions warrant,
are there services that can be stopped, or
upgrade to a larger memory configuration. can more memory be added?
This indicates a low memory condition.
Reduce other system activity to ease
Memory on the box must be running low memory demands. If conditions warrant,
are there services that can be stopped, or
upgrade to a larger memory configuration. can more memory be added?
This indicates a low memory condition.
Reduce other system activity to ease
Memory on the box must be running low memory demands. If conditions warrant,
are there services that can be stopped, or
upgrade to a larger memory configuration. can more memory be added?
This indicates a low memory condition.
Reduce other system activity to ease
Memory on the box must be running low memory demands. If conditions warrant,
are there services that can be stopped, or
upgrade to a larger memory configuration. can more memory be added?
This indicates a low memory condition.
Reduce other system activity to ease
Memory on the box must be running low memory demands. If conditions warrant,
are there services that can be stopped, or
upgrade to a larger memory configuration. can more memory be added?
This indicates a low memory condition.
Reduce other system activity to ease
Memory on the box must be running low memory demands. If conditions warrant,
are there services that can be stopped, or
upgrade to a larger memory configuration. can more memory be added?
This indicates a low memory condition.
Reduce other system activity to ease
Memory on the box must be running low memory demands. If conditions warrant,
are there services that can be stopped, or
upgrade to a larger memory configuration. can more memory be added?

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check for existence of the file as well as

the health of the device that the file
resides on. Very unlikely case, yet possible,
is the lack of system resources. Check CPU
usage as well as memory usage.

Upgrade to latest OS release. Check for

unsupported hardware.

Hardware, packaging or coding error.

Upgrade to latest OS release. Check for

unsupported hardware.

Hardware, packaging or coding error.

Upgrade to latest OS release. Check for

unsupported hardware.

Hardware, packaging or coding error.

Upgrade to latest OS release. Check for

unsupported hardware.

Hardware, packaging or coding error.

Upgrade to latest OS release. Check for

unsupported hardware.

Hardware, packaging or coding error.

Upgrade to latest OS release. Check for

unsupported hardware.

Hardware, packaging or coding error.

Upgrade to latest OS release. Check for

unsupported hardware.

Hardware, packaging or coding error.

'Attempt to repair the file using 'install

verify repair'; this is the ' 'least impactful
operation. In case repair fails, if possible, '
''install remove' the package associated
with the file and 'install add'' 'the pie
containing the package. If the file is still
corrupt ' 'use a pre-prepared backup disk (if
available) to revert to a previously' 'known 'If the issue persists even after trying the
good software, or failover to standby
recommended steps, raise DDTS' 'with
nodes. ' 'If the corruption is still seen,
'show tech install'.If possible provide the
contact TAC.'
corrupt file.'

First attempt to repair the file using 'install

verify repair', this is this least impactful
operation. If that is unable to repair the file
then if possible 'install remove' the
package associated with the file and then
'install add' the pie containing the package.
If the file is still corrupt then use a preprepared backup disk if available to revert
to a previously known good set of software,
or failover to standby nodes to start using Collect (admin) install tech-support file
their set of software files.
information for further diagnostics.
This indicates a low memory condition.
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -'Memory allocation failure. ' 'Retry the
'Restart the 'instdir' process from the exec operation after restarting 'instdir' process. '
prompt and retry the operation.' 'From exec 'If the issue is still seen after couple of tries
prompt - 'process restart instdir'.' 'If the
please raise DDTS' 'with 'show memory'
issue is still seen contact TAC.'
and 'show tech install'.'

No action is required.

Check lrd ltrace to see why the API call

returns EAGAIN. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

No action is required.

Check lrd ltrace to see why the API call

returns EAGAIN. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Package index file is out-of-sync with

installed packages. The index file will be
repaired.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Package index file is out-of-sync with

installed packages. The index file will be
repaired.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package, or upgrade the install
infrastructure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package, or upgrade the install
infrastructure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package, or upgrade the install
infrastructure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package, or upgrade the install
infrastructure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Repeat the operation after waiting for a

while, or copy the file via tftp to the
router's disk using the copy tftp: command,
then install the local file.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Repeat the operation after waiting for a

while, or copy the file via tftp to the
router's disk using the copy tftp: command,
then install the local file.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Try to re-acquire the pie files from the cisco

respository referred to you. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Check if the pie being installed is

truncated/corrupted. If problem persists,
Collect info as per the checklist given at
http://wikicentral.cisco.com/display/GROUP/
Bug+raising+and+Forwarding+criteria

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package, or upgrade the install
infrastructure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package, or upgrade the install
infrastructure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Format device and re-install packages.

Package index file is out-of-sync with

installed packages.

Format device and re-install packages.

Package index file is out-of-sync with

installed packages.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

A non-critical memory allocation failed (eg.

allocating space for memory failures).
There may be cosmetic errors but the
installation will proceed as expected.

No action is required.

A non-critical memory allocation failed (eg.

allocating space for memory failures).
There may be cosmetic errors but the
installation will proceed as expected.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package, or upgrade the install
infrastructure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package, or upgrade the install
infrastructure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check whether the PIE file is part of an

officially supported release or SMU.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check whether the PIE file is part of an

officially supported release or SMU.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check whether the PIE file is part of an

officially supported release or SMU.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check whether the PIE file is part of an

officially supported release or SMU.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package, or upgrade the install
infrastructure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package, or upgrade the install
infrastructure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Retry the command.If it fails, retry the

command after restarting the 'instdir'
process. Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Try the steps in recommended action. If it

does not help, Please collect info according
to the checklist given at
http://wikicentral.cisco.com/display/GROUP/
Bug+raising+and+Forwarding+criteria

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package, or upgrade the install
infrastructure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package, or upgrade the install
infrastructure.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Upgrade to the latest version of the

package.

Upgrade to latest OS release. Check for

unsupported hardware.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Upgrade to latest OS release. Check for

unsupported hardware.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

'The node will restart automatically and try

to boot-up.' 'If the node doesn't recover
after reload contact TAC with 'show tech
install'' 'and console logs.'

'Node will reload automatically to

recover.Collect the console logs for the '
'failure node and 'show tech install' '
'Contact DE with the logs.'

'The node will restart automatically and try

to boot-up.' 'If the node doesn't recover
after reload contact TAC with 'show tech
install'' 'and console logs.'

'Node will reload automatically to

recover.Collect the console logs for the '
'failure node and 'show tech install' '
'Contact DE with the logs.'

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Collect the following traces for the failing

node: - 'show install trace pkg' - 'show
install trace sds' Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

--

No action is required.

--

No action is required.

--

Collect insthelper traces from the reported

nodes using 'show install trace insthelper'.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

*DDTS

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

To be filled in later

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Replace the disk with one that has a great

capacity.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This means that TURBOBOOT was set, but

the selected install device is unavailable
for use. The TURBOBOOT setting is cleared
and the node is reset. Check the status of
device, repair and replace if necessary
before proceeding to TURBOBOOT again.

'Membooted system is not advisable.

Diskboot the system by reloading the'
'system with the TURBOBOOT rommon
variable set to 'on'.'

'The TURBOBOOT rommon variable was not

set to 'on',hence system has ' 'membooted.
Set the TURBOBOOT variable to 'on' to
prepare the system for' 'diskboot.'

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Boot environment variables cannot be

reset.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Verify that the disk is inserted correctly and

that it is not corrupt. Replace the disk if
necessary.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This means that the TURBOBOOT setting

had the flags to both CLEAN and FORMAT
the device. This setting is ignored and no
device initialization will be performed.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The TURBOBOOT setting in ROMMON had

more than one disk option set. This will
cause turboboot to abort. The operation
will have to be retried with correct settings.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

--

--

--

--

--

--

--

--

Restart the affected process. If the

message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

The affected process will not have received

the notification of the selected version
change and may continue to use the
incorrect version of a communication
protocol. The feature provided by the
process is likely to be affected. Report this
to Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

--

--

--

--

If there are no errors indicating a failure to

handle the notification, a failure to respond
If the message recurs, copy the error
to it should not itself cause any operational
message exactly as it appears on the
problems. However, this may indicate a
console or in the system log, call your
defect in the software. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.
--

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

At least one communication protocol may

be unable to operate correctly, affecting
one or more features. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

At least one communication protocol may

be unable to operate correctly, affecting
one or more features. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and if ANCP process is
able to initialize and come up successfully
after restart, then there is no need to take
any action. Otherwise if the message's
error code indicates that the failure was
due to lack of memory, then take the
following action. Reduce other system
activity to ease memory demands. If
conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message gives details about what

part of the initialization failed and the error
code should give the reason why. The most
likely cause is a memory allocation failure
or failure in checkpoint or ancp process.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and if ANCP process is
able to initialize and come up successfully
after restart, then there is no need to take
any action. Otherwise if the message's
error code indicates that the failure was
due to lack of memory, then take the
following action. Reduce other system
activity to ease memory demands. If
conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error code should give the reason why.

The most likely cause is a memory
allocation failure. Otherwise this problem is
either due to a software error in ancp or in
ifmgr or ifmgr not available. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

The process will attempt to recover from

this situation by retrying. If this message is
not seen again and if rate is getting
updated after sometime (few tens of
seconds), then there is no need to take any
action. Otherwise if the message's error
code indicates that the failure was due to
lack of memory, then take the following
action. Reduce other system activity to
ease memory demands. If conditions
warrant, upgrade to a larger memory
configuration. If the problem was not
caused by memory allocation and it hasn't
been corrected by subsequence restarts
then take the following action. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The error code should give the reason why.

The most likely cause is a memory
allocation failure. Otherwise this problem is
either due to a software error in ancp or in
ifmgr or ifmgr not available Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and if ANCP process is
able to initialize and come up successfully
after restart, then there is no need to take
any action. Otherwise if the message's
error code indicates that the failure was
due to lack of memory, then take the
following action. Reduce other system
activity to ease memory demands. If
conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the error was the result of a get operation

for a port down event, perhaps a port up
was never received or a clear operation
was performed on an unconfigured ANCP
port circuit. If the message's error code
indicates that the failure was due to lack of
memory, then take the following action.
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.
If the problem was not caused by memory
allocation, look to see if there are other
system messages which can provide more
clues to the problem. If there are no other
messages, please take the following action.
Copy the error message exactly as it
The error is most likely due to memory
appears on the console or in the system
allocation issue or an error in the ANCP
log, call your Cisco technical support
software. If the problem is not due to
representative and provide the
memory, Report this to Engineering. Use
representative with the gathered
Topic to search for a similar DDTS. If you
information.
find none, write a DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and if ANCP process is
able to initialize and come up successfully
after restart, then there is no need to take
any action. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

The error message gives details about what

part of the initialization failed and the error
code should give the reason why. The most
likely cause is a failure in sysmgr or ancp
process.

Check to see if the tcp process had

restarted. If it has, no further action is
needed. The remote ANCP clients should
restart the connection. The rates for any
configured ports previously in UP state will
go to DOWN state but their published rates
will remain the same. If the tcp process
hadn't restarted, then from the CLI, try to
clear the ancp neighbor. The adjacency
would be re-established and packet send
should be successful henceforth. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

The error code should give the reason why.

The most likely cause is a TCP restart.
Otherwise if this problem is either due to a
software error in ancp or in TCP or if packet
send is failing even after clear neighbor,
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and if ANCP process is
able to initialize and come up successfully
after restart, then there is no need to take
any action. Otherwise if the message's
error code indicates that the failure was
due to lack of memory, then take the
following action. Reduce other system
activity to ease memory demands. If
conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message gives details about what

part of the initialization failed and the error
code should give the reason why. The most
likely cause is a memory allocation failure
or software failure in tcp or ancp process.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and if ANCP process is
able to initialize and come up successfully
after restart, then there is no need to take
any action. Otherwise if the message's
error code indicates that the failure was
due to lack of memory, then take the
following action. Reduce other system
activity to ease memory demands. If
conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error code should give the reason why.

The most likely cause is a memory
allocation failure. Otherwise this problem is
either due to a software error in ancp or in
sysdb or sysdb not available. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Get memory used and amount budgeted
Cisco technical support representative and by running 'run show_processes -m -h -t'.
provide the representative with the
The 'Dyn-Limit' column is the amount
gathered information.
budgetted.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Get memory used and amount budgeted
Cisco technical support representative and by running 'run show_processes -m -h -t'.
provide the representative with the
The 'Dyn-Limit' column is the amount
gathered information.
budgetted.

Test the connectivity by pinging the remote

ip address. If this fails, determine what is
causing the network outage. If it is
successful, check the state, and
configuration of ANCP client at the remote
site. Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.
--

No action is required.

--

First, determine if the problem is

persistent. If it is, perhaps the router is
communicating with a non-conforming or
mis-behaving ANCP client. ANCP's detail
summary statistics will show the number of
occurrences and what was invalid in the
packet. If the packet was received on an
existing adjacency, the drop statistics will
reveal which adjacency the drop occurred
on. Details error logs can also be found in
ancp neighbor trace. If the device is
identified, restart or remove it from the
network. If a device is not identified, Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information..
--

The ANCP protocol is written to handle such

events by discarding the packet. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
-Get memory used and amount budgeted
by running 'run show_processes -m -h -t'.
No action needed since memory is back in The 'Dyn-Limit' column is the amount
the safe zone.
budgetted.

The configuration on the remote ANCP

client should be evaluated for duplicate
port circuit names on remote ANCP client
devices.

--

The configuration on the remote ANCP

client should be evaluated for duplicate
port circuit names on remote ANCP client
devices.

--

In this case the process would restart and

will recover by itself. If the issue is seen
repeatedly Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

An error has occurred in the ARP GMP

event loop. This may be caused by a lack
of system resources. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the ARP GMP fails to start up it is likely

that a service on IOSXR which it is using is
unavailable. Check the contents of the
error message, this should indicate the
Try restarting the ARP GMP process. If the appropriate service and nature of the
issue is seen repeatedly Copy the error
failure. If the service has any show
message exactly as it appears on the
commands or show trace commands, use
console or in the system log, call your
them to further isolate the problem. Report
Cisco technical support representative and this to Engineering. Use Topic to search for
provide the representative with the
a similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Reconfigure the static ARP entry or the

conflicting interface IP address. If this does
not help then do the following. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The error is due to a misconfiguration of

the static arp entry. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

As there is a retry mechanism in place the

process may recover by itself. If the issue is
seen repeatedly Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

ARP failed to initialise the Comms module

and is retrying. If the message stops then
the operation has succeeded on a
subsequent attempt. If the message
persists, it is likely to be a problem with the
AIPC or DS infrastructure. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Restart the ARP process. If this does not

resolve the problem then do the following.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

ARP has failed to open and initialize the

specified DLL. This may be a file system
failure. Check that the file is exists and is
present in the package. If these steps
doesn't solve the issue then Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem..

Please check for possible memory leaks

using the following commands: - show
memory start - perform the operation Please check if there are any memory
show memory end - check if there is any
leaks. If the issue is seen repeatedly
increase in memory using 'show memory
Reduce other system activity to ease
compare' Report this to Engineering. Use
memory demands. If conditions warrant,
Topic to search for a similar DDTS. If you
upgrade to a larger memory configuration. find none, write a DDTS for this problem..

The error could be due to a

misconfiguration of the given client. Rarely
this configuration may be intended - such
as for VRRP interface-ownership
Ensure that the configuration is correct for configuration. Report this to Engineering.
the client in question. The client has
Use Topic to search for a similar DDTS. If
configured the same IP address as one of
you find none, write a DDTS for this
the interface IP addresses.
problem.

The process would recover by itself as

there is a retry mechanism.

ARP failed to resync with its clients and is

retrying. If the message stops then the
operation has succeeded on a subsequent
attempt. If the message persists, it is likely
to be a problem with the GSP transport.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Please collect the output of show techsupport arp. If the issue is seen repeatedly
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

It is likely that the service to which the

error message refers is unavailable. If the
service has any show commands or show
trace commands, use them to further
isolate the problem. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If ARP fails to start up it is likely that a

service on IOSXR which ARP is using is
unavailable. Check the contents of the
Please collect the output of show techerror message, this should indicate the
support arp. If the issue is seen repeatedly appropriate service and nature of the
Copy the error message exactly as it
failure. If the service has any show
appears on the console or in the system
commands or show trace commands, use
log, call your Cisco technical support
them to further isolate the problem. Report
representative and provide the
this to Engineering. Use Topic to search for
representative with the gathered
a similar DDTS. If you find none, write a
information.
DDTS for this problem.

Restarting the process may fix the issue.

Please collect the output of show techsupport arp. If the issue is seen repeatedly
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

It is likely that a service on IOSXR which

ARP is using is unavailable. Check the
contents of the error message, this should
indicate the appropriate service and nature
of the failure. If the service has any show
commands or show trace commands, use
them to further isolate the problem. Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

The process may recover by itself as there

is a retry mechanism. If the issue is seen
repeatedly Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

ARP failed to attach interfaces to SPIO and

is retrying. If the message stops then the
operation has succeeded on a subsequent
attempt. If the message persists, it is likely
to be a problem with the SPIO platform
layer. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Restarting the process may fix the issue. If

the issue is seen repeatedly Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

ARP has failed to create the threads it

requires to operate. This is most likely a
system resource problem. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

In this case the process would recover by

itself. If the issue is seen repeatedly Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

An error has occurred in the specified event

loop. This may be caused by a lack of
system resources. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Change the interface IP address of one of

the two devices.

The error is due to the same ipv4 address

configuration at the peer. Please make sure
they are different. If the addresses are
unique and still an issue is seen then
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Change the interface MAC address of one

of the two devices.

The error is due to the same MAC address

configuration at the peer. Please make sure
they are different. If the MAC addresses are
unique and the issue is still seen then
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem..

Please check the configuration of the

participating devices.

No action required

Configure the MAC address so that it does

not have all the bits set.

No action required

If message appears only once, then no

action is required. Packets will be
retransmitted and system should recover
automatically. If message appears
continuously, then it could indicate a
problem with the control-ethernet. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Collect the required info. Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If message appears only once, then no

action is required. Packets will be
retransmitted and system should recover
automatically. If message appears
continuously, then it could indicate a
problem with the control-ethernet. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Collecte the required info. Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If message appears only once, then no

action is required. Packets will be
retransmitted and system should recover
automatically. If message appears
continuously, then it could indicate a
problem with the control-ethernet. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Collect the required info. Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If message appears only once, then no

action is required. Packets will be
retransmitted and system should recover
automatically. If message appears
continuously, then it could indicate a
problem with the control-ethernet. Please
restart eth_server process. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
Collect the required info. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

The error status can provide better clue.

Use 'show process eth_serv location
0/RSPx/CPU0' to verify if the process is still
If the message appears only once, then no up and running and use 'process restart
action is required. Packets will be
eth_serv location 0/RSPx/CPU0' to restart
retransmitted and system should recover eth_server process if necessary. Report this
automatically. If message appears
to Engineering. Use Topic to search for a
continuously, then it could indicate a
similar DDTS. If you find none, write a
problem with the control-ethernet.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

The system will try again. No action is

required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

The CE-TFTP server process will exit and

respawn itself. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Check if the file being requested exists and

has the correct read-write permissions.
-Check the path of file specified for
download.Also make sure the entire
pathname of the file is provided.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Check the filename given for download.

Also please give the entire pathname of
the file to be provided,relative to the TFTP
home directory.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

This indicates a low-memory condition.

Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.
If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Collect the required info. Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

No action is required.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Collect the required info. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

No action is required.

--

Check if the file being requested exists,

and has the correct read-write permissions. None.

This is an informational message. No action

is required.
--

None.

None.

This is an informational message. No action

is required.
--

None.

None.

This is an informational message. No action

is required.
-None.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

System will retry to start the process and

no user intervention required. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Revisit the configuration. Make sure that a

valid address/prefix range is configured for
the subnet. Do not include broadcast
address in address range configuration.
--

Add more address ranges for the specified

pool. For details regarding related
configurations, please refer 'Address Pool
Service Commands' chapter in Cisco IOS
XR software configuration guide.
--

Add more pools or address ranges for

allocation. For details regarding related
configurations, please refer 'Address Pool
Service Commands' chapter in Cisco IOS
XR software configuration guide.

--

No action is required.

--

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show techsupport<noCmdBold> command 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
<CmdBold>show techsupport<noCmdBold> output, call your
Cisco technical support representative and
provide the representative with the
gathered information.

If the issue persists and hinders any

functionality, please report Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show techsupport<noCmdBold> command 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
<CmdBold>show techsupport<noCmdBold> output, call your
Cisco technical support representative and
provide the representative with the
gathered information.

If the issue repeats Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show techsupport<noCmdBold> command 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
<CmdBold>show techsupport<noCmdBold> output, call your
Cisco technical support representative and
provide the representative with the
gathered information.

If the issue repeats Report this to

Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

If the problem cannot be resolved based on

the error message Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

This indicates a low-memory condition.

Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.

If the problem persists, please report

Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

If the problem cannot be resolved based on

the error message Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

This requires valid Default Gateway must

be configured under dhcp server
profile/class or pool. dhcp ipv4 profile TEST
server default-router 101.101.101.101 or
under class clase TEST_CLASS defaultIt is a misconfig. So please configure valid
router 101.101.101.101
Default Gateway.

Retry

If the issue persists, please report Report

this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Restart the dhcpv6d process Reduce other

system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration.
-Restart the dhcpv6d process Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

No action is required.

--

No action is required.

--

Find who sent this message

--

Find who sent this message

--

Please note down the stage at which this

error message is seen i.e during boot or
later stages.Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Check if the issue goes after proc restart. If

the issue persists, It indicates an internal
software inconsistency. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. For more info on
DNS, please check
http://wikicentral.cisco.com/display/PROJEC
T/IOS+XR+IP+DOMAIN+%28DNS%29

Such error are not expected. If the issue is

seen continously even after proc restart, It
The error should go away with process
indicates an internal software
restart domain_services loc all. If the error inconsistency. Report this to Engineering.
persists Copy the error message exactly as Use Topic to search for a similar DDTS. If
it appears on the console or in the system you find none, write a DDTS for this
log, call your Cisco technical support
problem. For more info on DNS, please
representative and provide the
check
representative with the gathered
http://wikicentral.cisco.com/display/PROJEC
information.
T/IOS+XR+IP+DOMAIN+%28DNS%29

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check if the issue goes after proc restart. If

the issue persists, It indicates an internal
software inconsistency. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. For more info on
DNS, please check
http://wikicentral.cisco.com/display/PROJEC
T/IOS+XR+IP+DOMAIN+%28DNS%29

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check if the issue goes after proc restart. If

the issue persists, It indicates an internal
software inconsistency. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. For more info on
DNS, please check
http://wikicentral.cisco.com/display/PROJEC
T/IOS+XR+IP+DOMAIN+%28DNS%29

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check if the issue goes after proc restart. If

the issue persists, It indicates an internal
software inconsistency. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. For more info on
DNS, please check
http://wikicentral.cisco.com/display/PROJEC
T/IOS+XR+IP+DOMAIN+%28DNS%29

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check if the issue goes after proc restart. If

the issue persists, It indicates an internal
software inconsistency. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. For more info on
DNS, please check
http://wikicentral.cisco.com/display/PROJEC
T/IOS+XR+IP+DOMAIN+%28DNS%29

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check if the issue goes after proc restart. If

the issue persists, It indicates an internal
software inconsistency. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. For more info on
DNS, please check
http://wikicentral.cisco.com/display/PROJEC
T/IOS+XR+IP+DOMAIN+%28DNS%29

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check if the issue goes after proc restart. If

the issue persists, It indicates an internal
software inconsistency. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. For more info on
DNS, please check
http://wikicentral.cisco.com/display/PROJEC
T/IOS+XR+IP+DOMAIN+%28DNS%29

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check if the issue goes after proc restart. If

the issue persists, It indicates an internal
software inconsistency. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. For more info on
DNS, please check
http://wikicentral.cisco.com/display/PROJEC
T/IOS+XR+IP+DOMAIN+%28DNS%29

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check if the issue goes after proc restart. If

the issue persists, It indicates an internal
software inconsistency. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. For more info on
DNS, please check
http://wikicentral.cisco.com/display/PROJEC
T/IOS+XR+IP+DOMAIN+%28DNS%29

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check if the issue goes after proc restart. If

the issue persists, It indicates an internal
software inconsistency. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. For more info on
DNS, please check
http://wikicentral.cisco.com/display/PROJEC
T/IOS+XR+IP+DOMAIN+%28DNS%29

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check if the issue goes after proc restart. If

the issue persists, It indicates an internal
software inconsistency. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. For more info on
DNS, please check
http://wikicentral.cisco.com/display/PROJEC
T/IOS+XR+IP+DOMAIN+%28DNS%29

No action is required.

--

No action is required.

--

No action is required.

--

Debug message only. No action is required. --

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This failure is caused by a failure with the

pthread library. Please refer to the support
material or wiki for this service.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This failure is caused by a failure with the

Event Manager library. Please refer to the
support material or wiki for this service.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This failure is caused by a failure with the

Event Manager library. Please refer to the
support material or wiki for this service.

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This failure is caused by a failure with the

Event Manager library. Please refer to the
support material or wiki for this service.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This failure is likely to be caused by a

failure in GSP. Please refer to the support
material or wiki for this service.

Reduce the number of virtual routers on

this interface (or the parent if it is a subinterface)

More than the maximum supported

number of MAC address filters has been
installed for this interface meaning traffic
to some virtual IP addresses will be
dropped. Check that the HSRP/VRRP
configuration is within the supported scale
range for this interface type. Alternatively,
other protocols may be also installing MAC
address filters: use the show commands for
the underlying interface type to investigate
if any are present and then check whether
the combination of protocols has exceeded
the MAC filter supported scale for this
interface type. Note that the maximum
number of supported MAC address filters
for an interface varies depending on the
interface type and for sub-interfaces the
limit is per parent interface. For HSRP/VRRP
support information please see http://wikieng.cisco.com/engwiki/HSRP_2fVRRP

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

If HSRP/VRRP does not restart and

automatically recover, do the following.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

If HSRP/VRRP fails to start up it is likely that

a service on IOSXR which it is using is
unavailable. Check the contents of the
error message, this should indicate the
appropriate service and nature of the
failure. If the service has any show
commands or show trace commands, use
them to further isolate the problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears, and report it to your technical
support representative.

--

Copy the error message exactly as it

appears, and report it to your technical
support representative.

--

Copy the error message exactly as it

appears, and report it to your technical
support representative.

--

Copy the error message exactly as it

appears, and report it to your technical
support representative.

--

Copy the error message exactly as it

appears, and report it to your technical
support representative.

--

Copy the error message exactly as it

appears, and report it to your technical
support representative.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
-Debug message only. No action is required. --

Check the configuration to confirm the

configuration is intentional. Remove any
misconfiguration. If that does not work
contact Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The message displayed to inform user that

addresses configured in a pool are reached
threshold limit and check whether it is
intentional configuration or not. If not,
please remove the extra configuration.
Please contact [email protected] for any additional help.

Consider combining multiple ranges into

one.If that does not work contact Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The message displayed to inform user that

addresses configured for addresses in a
pool are reached threshold limit and check
whether it is intentional configuration or
not. If not, please remove the extra
configuration. Please contact [email protected] for any additional help.

Restarting the process might help in

recovering from error.

Memory corruption has happened in the

process space.

Contact support.

IP ARM consumer library initialization failed

due to some system initialization function
returning error. Possible resource shortage
or coding error.

Contact support.

IP ARM client address registration failed

due to invalid paramters. This could
potentially cause some traffic loss.

Restarting the process might help in

recovering from error.

Memory on the box must be running low are there services that can be stopped, or
can more memory be added?

Report this to Engineering. Use Topic to

Get the output of show tech-support, show search for a similar DDTS. If you find none,
arm [ipv4/ipv6] trace, running coredump of write a DDTS for this problem. If
the process. Unconfiguring, reconfiguring unconfiguring, reconfiguring the interface
the interface may help in recovering the
doesn't help, the process restart might help
from error.
to recover from this error.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Get the output of show tech-support, show

arm [ipv4/ipv6] trace, running coredump of
the process. Unconfiguring, reconfiguring
the interface may help in recovering the
from error.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. If
unconfiguring, reconfiguring the interface
doesn't help, the process restart might help
to recover from this error.

Reconfigure the IP addresses that share the

common network portion specified.
--

Collect the output of show tech-support,

show arm [ipv4/ipv6] trace and the steps
that lead to this behavior.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. The process
might have to be restarted to avoid any
unexpected behavior and to sanitize the
database.

Change the mhost ipv4 default-interface

configuration to some other physical or
Report this to Engineering. Use Topic to
virtual interface. Collect the output of show search for a similar DDTS. If you find none,
tech-support, show arm ipv4 trace
write a DDTS for this problem.

Get the output of show tech-support, show

arm [ipv4/ipv6] trace, running coredump of
the process. Unconfiguring, reconfiguring
the interface may help in recovering the
from error.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. If
unconfiguring, reconfiguring the interface
doesn't help, the process restart might help
to recover from this error.

Reconfigure one of the IP unnumbered

interfaces so that the unnumbered
interface does not reference another
unnumbered interface.

--

Change the mhost ipv4 default-interface

configuration to some other physical or
virtual interface.

--

None. This is an informational message

indicating a return to a correct consistent
configuration.

--

None. This is an informational message to

tell user that router id configure CLI has
been deprecated.

--

Ensure that a global router id has been

configured and that the configured
interface has a primary IPv4 address and is
UP (a loopback interface is strongly
recommended), or that the configured IPv4
address exists on an interface that is UP.
-None. This is an informational message
indicating a return to a correct consistent
configuration.

--

If the problem persists get the output of

show processes, show sysdb trace, show
sysdb trace clientlib job <jid of
ip[v4/v6]_arm>, show arm [ipv4/ipv6] trace Report this to Engineering. Use Topic to
from the location the error message comes search for a similar DDTS. If you find none,
from.
write a DDTS for this problem.

Report this to Engineering. Use Topic to

Collect the output of show tech-support,
search for a similar DDTS. If you find none,
show processes, show arm [ipv4/ipv6] trace write a DDTS for this problem.

If the msg is not seen multiple times, it can

be assumed that the process has
recovered. If the process cannot recover
from this error, it may not be able to run.
Then it is a fatal error. Collect the output of
show tech-support, show arm [ipv4/ipv6]
trace.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. A failover
may have to be triggered to recover if
fatal.

Monitor the affected node to see whether

any processses are blocked.

This message indicates that there is delay

in programming the FIB or platform. Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

The update will be replayed to the platform This message indicates that a hardware or
code and may succeed on a subsequent
software fault occured while programming
attempt. If not then the system will be left the platform code. If it is seen once then
in an inconsistant state and this interface the problem was likely to be transitory and
may not function normally. If the message has been fixed by a subsequent retry. If the
recurs, copy the error message exactly as it message is seen repeatedly then it
appears on the console or in the system
probably indicates that there is an
log, call your Cisco technical support
underlying problem with the platform code.
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

The update will be replayed to the platform

code and may succeed on a subsequent
attempt. If not then the system will be left
in an inconsistant state and the affected
interfaces may not function normally. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This message indicates that a hardware or

software fault occured while programming
the platform code. If it is seen once then
the problem was likely to be transitory and
has been fixed by a subsequent retry. If the
message is seen repeatedly then it
probably indicates that there is an
underlying problem with the platform code.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action.If does not recover
contact Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information..
write a DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise check
whether the error code contained in the
message indicates that there was a failure
to allocate the necessary memory and take
the following action. Reduce other system
activity to ease memory demands. If
conditions warrant, upgrade to a larger
memory configuration. If resource
allocation was not the problem and it
hasn't been fixed by a subsequent restart
then take the following action. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The error message gives details about what

part of the initialisation failed and the error
code should give the reason why. The most
likely cause is a memory allocation failure.
Otherwise this problem is either due to a
software error in ipv4_io or in one of the
services that it uses. Other services may
generate their own error messages and
these may provide a clue as to what has
gone wrong. The ipv4 ltrace buffer and the
debug output contain details of the
initialisation process and will indicate which
stage of initialisation failed. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action.If does not recover
contact Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error is encounterd because of failure

in binding to SysDB. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action.If does not recover
contact Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information..

The error is encounterd because of IPv4ma

failed in registering notifiee with sysDB.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action.If does not recover
contact Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information..
write a DDTS for this problem.
None required if NTP process restarts and
recovers.

--

None required if NTP process restarts and

recovers.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check the internal battery-powered clock

(which is called calendar) hardware in
active RP. Pass the code error and point of
error to DE who takes the component.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Check the internal clock hardware in active

RP. Pass the error number and failed
process to DE who takes care the
component.

Reduce the memory usage. If the problem

still occurs, contact TACS/SUPPORTS and
pass the memory usage, ltrace, and
configuration of NTP to them such as show memory - show ntp trace ... - show
running-config

Collect the information and pass it to DE.

Try to reset the drift value by

<CmdBold>ntp reset drift<NoCmdBold>. If
this message recurs after resetting the drift
value, see <CmdBold>show ntp
associations<NoCmdBold>, correct
information for all the peers, contact your
Cisco Technical support, and provide the
representative with the gathered
information.

Some platform does not have a good clock

(ex. CSCsu85884). Try to find the bad clock
source and stop to use it as an NTP server,
i.e. no ntp master etc.

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

If SYNC_LOSS because 'The clock was

Some platform does not have a good clock
stepped and needs to be resynced' keeps (ex. CSCsu85884). Try to find the bad clock
occuring constantly during time, try to exec source and stop to use it as an NTP server,
<CmdBold>ntp reset drift<NoCmdBold>. i.e. no ntp master etc.

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The user attempted to run a show

command which required that ipv4_io to
obtain information from the external data
manager noted and decode it for output to
the console. While the data block (bag) was
obtained correctly, it did not decode
correctly.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A process has requested information from

ipv4_io by attempting to read its external
data manager. In the process of fulfilling
the request for data, ipv4_io has attempted
to encode the indicated data and failed.

Collect the output of show tech-support,

show ipv4 ma trace location <> when this
message is seen. Identify if possible which
manageability requests triggers this
message. Most likely it would be one of the
show ipv4 CLIs.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Failed to connect to SysDB while starting

the indicated subsystem. This generally
can only occur when process is starting up.

If the problem persists get the output of

show processes, show sysdb trace edm,
show sysdb trace clientlib job <jid of
ipv4_ma>. If multiple instances of ipv4_ma
are seen running or trying to run (this can
be due to a bug in some other area of the
system), make sure that only one instance
is allowed by killing the other one.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The ipv4_io process failed while attempting

to register its external data manager data
blocks with SysDB. This will generally only
occur while ipv4_io is starting up.

If the problem persists get the output of

show processes, show sysdb trace edm,
show sysdb trace clientlib job <jid of
ipv4_ma>. If multiple instances of ipv4_ma
are seen running or trying to run

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

The operation specified in the message

failed due to a memory allocation failure. If
Reduce other system activity to ease
this problem occurred in response to
memory demands. If conditions warrant,
configuration then that config should be
upgrade to a larger memory configuration. removed and reapplied. If there are further
When the memory shortage is resolved
issues then restarting the ipv4_io process
retry the operation.
may fix the issue.

IPV4 IO could not update option registry

information consistently across all of its
instances. This could result in unexpected
behavior with respect to some option
packets. Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.
IPv4 IO could not register with the PA for
handling a particular ICMP type locally.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This problem might be a symptom of an

error with the PA process itself. The output
of show processes will show whether this
process is blocked or not running for some
reason.

IPV4 IO could not get a valid handle for its

Reduce other system activity to ease
connection to the PA. This probably
memory demands. If conditions warrant,
indicates that the system is low on
upgrade to a larger memory configuration. memory.

The process will attempt to rectify this

situation by restarting. If this message is
not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise check
whether the error code contained in the
message indicates that there was a failure
to allocate the necessary memory and take
the following action. Reduce other system
activity to ease memory demands. If
conditions warrant, upgrade to a larger
memory configuration. If resource
allocation was not the problem and it
hasn't been fixed by a subsequent restart
then take the following action. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The error message gives details about

exactly what has gone wrong and the error
code should give the reason why. One
possible cause is a memory allocation
failure. Otherwise this problem is either
due to a software error in ipv4_io or in one
of the services that it uses. Other services
may generate their own error messages
and these may provide a clue as to what
has gone wrong. The ipv4 ltrace buffer and
the debug output contain details of what
the process was doing up to and including
the time of the failure. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

This message indicates that the ipv4_io

This message is mostly informational and
process has received a message type that there is no action that can be taken in
it wasn't expecting. This message has been response. If this message is seen alongside
ignored and no further action needs to be some other problem then it may shed some
taken. The message may have been sent to light on that problem. If this message is
this process by mistake or if any installs
seen during an install then it may be that
have taken place there may be a version
there is a temporary version mismatch that
mismatch between the server and a client. will be resolved once the install is
On its own this message does not indicate complete. If it is seen after an install then it
a problem. If other problems are seen then indicates that the system has been left in
include this error in the report.
an incompatible state.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise check
whether the error code contained in the
message indicates that there was a failure
to allocate the necessary memory and take
the following action. Reduce other system
activity to ease memory demands. If
conditions warrant, upgrade to a larger
memory configuration. If resource
allocation was not the problem and it
hasn't been fixed by a subsequent restart
then take the following action. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The error message gives details about what

part of the initialisation failed and the error
code should give the reason why. The most
likely cause is a memory allocation failure.
Otherwise this problem is either due to a
software error in ipv4_io or in one of the
services that it uses. Other services may
generate their own error messages and
these may provide a clue as to what has
gone wrong. The ipv4 ltrace buffer and the
debug output contain details of the
initialisation process and will indicate which
stage of initialisation failed. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

shut/unshut of the interface will trigger

Please refer the following link for more
leave/join respectively. This can be done to information:
retry the group join. Note any previous
http://zed.cisco.com/confluence/display/SP
errors related to multicast
RSG/IP+Infra+Triage

Collect the output of show tech-support,

show ipv4 ma trace, debug ipv4 ma error,
debug im errors, debug im api calls job <>, IPv4 MA process is unable to setup
debug im api errors job <> from the
correctly Forwarder interface. The error is
location the error message comes from.
mentioned in parenthesis.

Collect the output of show tech-support,

show processes, show ipv4 ma trace,
debug event-manager attach job <> from
the location the error message comes from.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
Please refer the following link for more
representative and provide the
information:
representative with the gathered
http://zed.cisco.com/confluence/display/SP
information.
RSG/IP+Infra+Triage

Collect the output of show tech-support,

show processes, show ipv4 ma trace,
debug event-manager attach job <> from
the location the error message comes from.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
Please refer the following link for more
representative and provide the
information:
representative with the gathered
http://zed.cisco.com/confluence/display/SP
information.
RSG/IP+Infra+Triage

Collect the output of show tech-support,

show processes, show ipv4 ma trace from
the location the error message comes from.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
Please refer the following link for more
representative and provide the
information:
representative with the gathered
http://zed.cisco.com/confluence/display/SP
information.
RSG/IP+Infra+Triage

Collect the output of show tech-support,

show ipv4 ma trace, debug ipv4 ma error
from the location the error message comes
from. Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

IPv4 MA process is unable to get the name

of forwarder interface (hidden from the
user). The error is mentioned in
parenthesis. If the error message persists,
try restarting ipv4 ma. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

shut/unshut of the interface will trigger

leave/join respectively. Do as appropriate
to recover. Collect the output of show techsupport, show ipv4 ma trace, show ipv4
trace, debug ipv4 ma mhost from the
location the error message comes from.
Note any previous errors related to
multicast membership. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

If the problem persists get the output of

show tech-support, show processes, show
sysdb trace, show sysdb trace clientlib job
<jid of ipv4_ma>, show ipv4 ma trace
location <> from the location the error
message comes from.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

If the problem persists get the output of

show processes, show sysdb trace, show
sysdb trace clientlib job <jid of ipv4_ma>,
show ipv4 ma trace location <>, debug
sysdb notification job <jid of ipv4_ma>
from the location the error message comes
from.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

If the problem persists get the output of

show processes, show sysdb trace, show
sysdb trace clientlib job <jid of ipv4_ma>,
show ipv4 ma trace location <>, debug
sysdb verification job <jid of ipv4_ma>
from the location the error message comes
from.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Adjust the lower layer mtu such that

atleast 68 bytes is available to IPv4. If the
lower layer mtu is big enough collect the
output of show tech-support, show ipv4 ma
trace, show im trace, show im chains, show
ipv4 interface for the interface for which
the above error is seen. Try
unconfiguring/reconfiguring the interface if
the lower layer mtu is big enough and still
the error is seen.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.. The newly
proposed MTU bytes for an interface is
lower than 68 bytes. Please refer the
following link for more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

IPv4 MA restarts in an attempt to recover

from this situation, config should get
applied on this new interface successfully.
No further action should be necessary. If
errors are observed, trying to unconfigure
and reconfigure the interface in problem
would help. If that does not and IPv4 MA
related errors are still observed please
gather the necessary information as
mentioned in required info Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

IPv4 MA has missed the delete from both

Sysdb and Interface manager here. It
should be able to resync after it restarts, if
problems are noted even after restart,
please capture the traces in required info
as soon as possible. The reason for missing
the delete could be because of IPv4 MA
blocked on something at a earlier time
when delete was done, or a bug in the
servers not sending MA the delete.

Choose IPv4 MTU value lesser than the

LINK payload value

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

The user can take corrective action before

the commit if it is not intended to remove
the current configured primary address.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Report this to Engineering. Use Topic to

The problem is normally recovered by the search for a similar DDTS. If you find none,
IPV4-MA component. If the message recurs, write a DDTS for this problem. IPV4 MA get
copy the error message exactly as it
the local obtained ifhandle, which is the
appears on the console or in the system
one handled in IM for active nfns. If the
log, call your Cisco technical support
nfns are delete nfns, then IPV4 MA get the
representative and provide the
ifhandles from our own local local database
representative with the gathered
first and overwrite the IM obtained
information.
ifhandles with our own.

The error message gives details about what

part of the initialisation failed and the error
code should give the reason why. The most
likely cause is a memory allocation failure.
Otherwise this problem is either due to a
software error in ipv4_io or in one of the
services that it uses. Other services may
generate their own error messages and
these may provide a clue as to what has
gone wrong. Report this to Engineering.
Collect the output of show tech-support,
Use Topic to search for a similar DDTS. If
show processes, show ipv4 ma trace from you find none, write a DDTS for this
the location the error message comes from. problem.

Collect the output of show tech-support,

show ipv4 ma trace, debug imp dpc, debug
ipv4 events, debug im api job <> from the
location the error message comes from.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Collect the output of show tech-support,

show processes, show ipv4 ma trace, show
lwm from the location the error message
comes from. If this message is seen
repeatedly, capture the output of debug
event-manager dispatch job <>. This
debug captures almost all the IPCs
received by ipv4 ma and hence it may slow
down the process and take up the related
resources. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma may fix the issue.

Note any previous errors related to

multicast membership. Please refer the
following link for more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma and sysdb may fix the

issue.

The IPV6 MA process failed to initialize its

configuration sub-system. This can only
happen when the process is starting up.
Please refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma may fix the issue.

The IPV6 MA process failed to initialize its

event conn mgr infra. This can only happen
when the process is starting up. Please
refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

The process would recover itself from this

error by itself as there is recovery
mechanism. If the error is still seen
restarting ipv6_ma may fix the issue.

The IPV6_MA process failed to create the

event manager. Please refer the following
link for more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma may fix this issue.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma may fix the issue.

Note any previous errors related to

multicast membership. Please refer the
following link for more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma may fix the issue.

The IPV6 MA process failed to initialize

callback handlers. This can only happen
when the process is starting up. Please
refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma may fix the issue.

Failed to connect to SysDB while starting

the indicated subsystem. This generally
can only occur when process is starting up.
Please refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma may fix the issue.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma may fix the issue.

The IPV6 MA process failed to initialize the

interface database. This can only happen
when the process is starting up. Please
refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma may fix the issue.

The IPV6 MA process failed to initialize its

debug support.This can only happen when
the process is starting up. Please refer the
following link for more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma may fix the issue.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

IPv6 MA restarts in an attempt to recover

from this situation, config should get
applied on this new interface successfully.
No further action should be necessary. If
errors are observed, trying to unconfigure
and reconfigure the interface in problem
would help.

IPv6 MA has missed the delete from both

Sysdb and Interface manager here. It
should be able to resync after it restarts, if
problems are noted even after restart,
please capture the traces in required info
as soon as possible. The reason for missing
the delete could be because of IPv6 MA
blocked on something at a earlier time
when delete was done, or a bug in the
servers not sending MA the delete. Please
refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Adjust the lower layer mtu such that

atleast 1280 bytes is available to ipv6.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Choose IPv6 MTU value lesser than the

LINK MTU value

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

None of the traces can be saved in this

case. If tracing is very much important to
be collected then restarting of ipv6_io may
fix this issue.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting IM may fix the issue.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma may fix the issue.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_ma may fix the issue.

The IPV6 MA process failed to initialize its

timers. This can only happen when the
process is starting up. Please refer the
following link for more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting IM may fix the issue.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Execute show ipv6 interface to see if the

duplicate address detected earlier is now
cleared.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

The error message gives details about what

part of the initialization failed and the error
The process will attempt to recover from
code should give the reason why. Please
this situation by restarting. If this message refer the following link for more
is not seen again and no other adverse
information:
effects are observed then there is no need http://zed.cisco.com/confluence/display/SP
to take any action.
RSG/IP+Infra+Triage

Unconfigured the duplicated address and

reconfigure with a correct one. If the
address is a Link Local address, perform a
'shut' and then 'no shut' on the interface.

--

'show adjacency ipv6 [location node-id]'

and 'show ipv6 neighbor [location node-id]
commands. Entries in AIB should match
with ND's. If the etries don't match then
the router may not function correctly or
efficiently. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
To recover from the error, either the aib
representative with the gathered
and/or the ipv6_nd processes must be
information.
restarted.

If the message recurs, copy the error

message exactly as it appears on the
Determine if the aib process is running or it
console or in the system log, call your
is being blocked by some other process.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Use 'show memory summary [location

<node-id>]' command to determine the
state of the system memory. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration.
--

Use 'show proc pfi_ifh_server [location

node-id]' to find out the state of the IFH
server process. Also, use 'show proc
blocked [loc node-id' to determine if the
pfi_ifh_server process is being blocked. If
the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
Determine if the ifmgr process is running or
console or in the system log, call your
it is being blocked by some other process.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Configure minimum and maximum RA

interval within the permitted range.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

ND cache limit will be hit under two

situations: 1) Total number of complete
neighbor entries exceeds the configured
Configure a larger cache limit on the
cache limit under the interface shown. 2)
interface. Use 'ipv6 nd cache-limit <new
Total number of either incomplete protocol
value>' under interface config mode. The or glean entry requests exceeds allowed
following information would be helpful
cache limit respectively. Allowed cache
when the issue is seen: show ipv6 interface limit for either type of incomplete entries
<interface-name> show ipv6 neighbor
equals to half of unused cache under the
<interface-name>
interface shown.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

This generally indicates a low memory

condition. Reduce other system activity to
ease memory demands. If conditions
warrant, upgrade to a larger memory
configuration.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Restarting ipv6_io may fix the issue.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting the process may fix the issue.

This should not happen.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The user executed the indicated show

command which required that ipv6_io
attach to SysDB to obtain some information
for display. The connection to SysDB failed.
Please refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting IM may fix the issue.

Please refer the following link for more

information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

This usually happens at startup. The

process would usually restart and recover.
If the problem continues, restarting ipv6_io
may fix the issue.

This can happen only at startup. Process

should restart and recover. Please refer the
following link for more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

This happens during startup. No traces

could be saved if this error condition
None of the traces can be saved in this
occurs. Please refer the following link for
case. If tracing is very much important to more information:
be collected then restarting of ipv6_io may http://zed.cisco.com/confluence/display/SP
fix this issue.
RSG/IP+Infra+Triage

Check if there are any possible memory

leaks.

IPV6 IO could not get a valid handle for its

connection to the PA. This might be
because the system is low on memory.
Please refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting packet manager process and

then ipv6_io may fix the issue.

The IPv6 IO process failed to connect to the

packet manager. Please refer the following
link for more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting the process may fix the issue.

IPv6_IO attempted to write a packet to the

transport layer and failed. Please refer the
following link for more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Wait for sometime till the process comes

up and even after that if the error is seen
restart ipv6_ea. This may fix the issue.

Failed to connect to SysDB while starting

the indicated subsystem. This generally
can only occur when process is starting up.
Please refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_io may fix the issue.

Could not connect to SysDB. tac_details:

Please refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_io may fix the issue.

The IPv6 IO process failed to create a

connection to a server. Please refer the
following link for more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

IPv6 IO could not register with the PA for

handling a particular ICMP6 type locally.
This might be because the connection to
the PA is not available. Please refer the
following link for more information:
Restarting lpts_pa and then ipv6_io may fix http://zed.cisco.com/confluence/display/SP
this issue.
RSG/IP+Infra+Triage

IPv6 IO could not register with PA for

handling a particular ICMP6 type locally.
This might be because of some problem
with the LPTS/PA. Please refer the following
link for more information:
Restarting lpts_pa and then ipv6_io may fix http://zed.cisco.com/confluence/display/SP
this issue.
RSG/IP+Infra+Triage

Restarting the process may fix the issue.

Could not create the indicated tuple in

SysDB. Please refer the following link for
more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

If the error is seen only once it can be

ignored and if it seen consistently then
restarting of ipv6_ea may help.

IP received a packet with invalid format

header. This packet will be dropped. Note
the event which triggered this error. Please
refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restart sysdb process and try the CLI

again.

The user attempted to run a show

command which required that ipv6_io to
obtain information from the external data
manager noted and decode it for output to
the console. While the data block (bag) was
obtained correctly, it did not decode
correctly. Please refer the following link for
more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

A process has requested information from

ipv6_io by attempting to read its external
data manager. In the process of fulfilling
the request for data, ipv6_io has attempted
to encode the indicated data and failed.
Please refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
Restarting sysdb process may fix the issue. RSG/IP+Infra+Triage

Restarting ipv6_io may fix the issue.

The ipv6_io process failed to register its

external data manager when starting up.
Please refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Based on the error indicated, investigate

the source of the and links for packet
corruption or other errors.

IPV6_IO discarded a packet due to the

indicated error. Please refer the following
link for more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Try resending the packets again.

IPv6_IO could not write the packet specific

features. Please refer the following link for
more information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

Restarting ipv6_io may fix the issue.

The ipv6 io process failed to create shared

memory object for ipv6 traffic statistics.
Please refer the following link for more
information:
http://zed.cisco.com/confluence/display/SP
RSG/IP+Infra+Triage

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The most likely cause is a memory

allocation failure. Otherwise this problem is
due to a software error in l2snoop Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message gives details about what

part of the initialization failed and the error
code should give the reason why. The most
likely cause is a memory allocation failure.
Otherwise this problem is either due to a
software error in l2snoop or in one of the
services that it uses. Other services may
generate their own error messages and
these may provide a clue as to what has
gone wrong. the debug output contain
details of the initialisation process and will
indicate which stage of initialisation failed.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, contact your Cisco technical support
representative, and provide the
representative with the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

The possible cause could be a memory

allocation failure. Otherwise this problem is
due to a software error in l2snoop or
ipv4_io/ipv6_io is not ready somehow or
blocked on some processes.

In the problem recurs, reduce other system

activity to ease memory demands. If
conditions warrant, upgrade to a larger
memory configuration. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration.

L2Snoop process will retry to get more

memory if possible otherwise process will
exit with error and get restarted by sysmgr.
no further action is needed to recover from
the situation. If memory is repeatedly
exhausted, then more memory needs to be
freed from other areas of the system or
more memory is needed.

The process will attempt to recover from

this situation by restarting or retrying. If
this message is not seen again and no
other adverse effects are observed then
there is no need to take any action.
Otherwise if the message's error code
indicates that the failure was due to lack of
memory, then take the following action.
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.
If the problem was not caused by memory
allocation and it hasn't been corrected by
subsequence restarts then take the
following action. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

The error code should give the reason why.

The most likely cause is a memory
allocation failure. Otherwise this problem is
either due to a software error in l2snoop or
in sysmgr or sysmgr not available Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, contact your Cisco technical support
representative, and provide the
representative with the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Most likely the netio/ipv4_io/ipv6_io is not

ready somhow or blocked on some
processes.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
The most likely cause is a memory
memory configuration.
allocation failure.

The process will attempt to recover from

this situation by restarting or retrying. If
this message is not seen again and no
other adverse effects are observed then
there is no need to take any action.
Otherwise if the message's error code
indicates that the failure was due to lack of
memory, then take the following action.
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.
If the problem was not caused by memory
allocation and it hasn't been corrected by
subsequence restarts then take the
following action. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
The most likely cause is internal failure
representative with the gathered
during registration. Please collect the
information.
debug info in the required_info section.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
The most likely cause is a memory
memory configuration.
allocation failure.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The most likely cause is a memory

allocation failure or rsi agent is not
available. Otherwise this problem is due to
a software error in l2snoop.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error code should give the reason why.

The most likely cause is a memory
allocation failure. Otherwise this problem is
either due to a software error in l2snoop or
in sysdb or sysdb not available Report this
to Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

This indicates a problem with sysdb. Do the

following action. Copy the error message
exactly as it appears on the console or in
the system log. Issue the <CmdBold>show
pim trace sysdb error<noCmdBold>
command 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 <CmdBold>show pim trace sysdb
error<noCmdBold> output, call your Cisco
technical support representative and
provide the representative with the
gathered information. If the error is seen
only once/twice while some sysdb
processes crashed or were restarted, this
might be related to that and could be
considered transitory. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
This should be seen in restart scenarios. If
log, call your Cisco technical support
it is seen otherwise, do the following
representative and provide the
action. Report this to Engineering. Use
representative with the gathered
Topic to search for a similar DDTS. If you
information.
find none, write a DDTS for this problem.

This indicates a problem with publishing

BGP convergence via sysdb. If the errors
are seen continuously and you see
problems with BGP covergence, do the
following action. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information. If the error is seen only
once/twice while some sysdb processes
crashed or were restarted, this might be
related to that and could be considered
transitory.

This should be seen in restart scenarios. If

it is seen otherwise, do the following
action. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

This indicates a problem with getting the

helper address. If the errors are seen
continuously and you see problems with
the helper address, do the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. If the error is seen only
once/twice while some sysdb processes
crashed or were restarted, this might be
related to that. If you don't see any issue
with the helper address thereafter, it is a
transitory problem.

This should be seen in restart scenarios. If

it is seen otherwise, do the following
action. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

This can happen while 'packet' process is

restarting and a couple of instances of the
message can be ignored in that case. If
there is no restart and problems are being
seen with the router not being able to send
ICMP errors, do the following action. Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

If these messages are seen persistently,

contact the development team and do the
following action. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

This error message is seen when the

transport is sending packets received from
the applications(routing protocols). It might
indicate a problem in the application or
with the packet getting corrupted. If a
routing protocol is having problems coming
up or working properly, the errors are
Do the following action. Copy the error
probably for that protocol's control-plane
message exactly as it appears on the
packets. Contact the development team
console or in the system log, call your
and do the following action. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

This error message is seen when the

transport is sending packets received from
the applications(routing protocols). It might
indicate a problem in the application or
with the packet getting corrupted. If a
routing protocol is having problems coming
up or working properly, the errors are
Do the following action. Copy the error
probably for that protocol's control-plane
message exactly as it appears on the
packets. Contact the development team
console or in the system log, call your
and do the following action. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

This could happen if there is a problem

with packet shared memory on the node.
The transport would restart in this
situation, if it restarts once or twice and
then recovers, then it could be a transient
problem and no action is required. If the
transport keeps restarting, do the following
action. Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The transports need to open shared

memory based (xipc)queues with netio and
the network-layer processes to be able to
send/receive protocol packets. Since, it
can't do much work without those, it
restarts. If the transports keep restarting, it
indicates some persistent problem with the
packet shared memory. Contact the
development team and do the following
action. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

These messages are related to transport

initialization and so should be seen at
bootup/OIR/MDR events. Since, the
transports are needed for routing protocol
packets to be sent out/received, these
Transport processes might restart due to
could affect the neighbor adjacencies or
this initialization failure. If this error
cause those to come up late. A thing to
message is seen just once when multiple
check for is the time at which the transport
processes restart, then it can be considered became stable, i.e., stopped restarting. The
transient and ignored. If the message is
initialization would generally fail for a lower
seen multiple times and the transport has layer like Interface manager(ifmgr) or
restarted too many times, do the following packet-manager(packet) or network-layer
action. Copy the error message exactly as process problems, so, check for health of
it appears on the console or in the system those. If the transport(s) keep restarting,
log, call your Cisco technical support
do the following action. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The returned error provides the type of the

error. Based on the error type, the source
of the error could be identified. Report this
to Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Determine the state of the packet manager
Cisco technical support representative and process. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
If the problem persists, it is an indication of
console or in the system log, call your
a potential buffer leak. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
Determine if either the ipv6_io or the netio
console or in the system log, call your
process is operational. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.
The returned error provides the type of the
error. Based on the error type, the source Determine the source of the error based on
of the error could be identified.
the error type.

If the message recurs, copy the error

Determine the state of the GSP and
message exactly as it appears on the
whether the the GSP process being blocked
console or in the system log, call your
by some other process. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Determine if the netio process is
provide the representative with the
operational and if it is blocked by some
gathered information.
other process.

If the message recurs, copy the error

message exactly as it appears on the
Determine if either the ipv6_io or the netio
console or in the system log, call your
process is not operational. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Use 'show memory summary [location

<node-id>]' command to determine the
state of the system memory. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
Determine if sufficient memory is available
memory configuration.
or not.

If the message recurs, copy the error

message exactly as it appears on the
Determine if either the ipv6_io or the netio
console or in the system log, call your
process is operational. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.
'Adding the following command under
router lisp will likely ' 'provide a
workaround. <CmdBold>address-family
{ipv4|ipv6} unicast ' 'map-request-source
<LOCAL ADDRESS><noCmdBold>.'

--

'If LISP process dies, it will attempt to

recover from this situation by ' 'restarting.'
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

'Check the network connectivity and

routing ' 'configuration within the LISP site
and re-establish ' 'a route to destinations
covered by the configured ' 'EID prefix.'
--

'Issue the <CmdBold>show {ipv4 | ipv6}

lisp database' '<noCmdBold> command
and look for routing ' 'locators marked as
<CmdBold>missing<noCmdBold>. '
'Configure the missing routing locators for
the ' 'remaining local EID prefixes. If a
routing locator' 'must not be used for
inbound traffic to a local ' 'EID prefix then a
priority of 255 can be ' 'specified.'
-'Use the <CmdBold>show lisp {ipv4 |
ipv6} ' '[instance-id <iid>] routeimport<noCmdBold> ' 'command to
inspect the RIB routes that have been '
'imported by LISP. Modify the LISP route
import ' 'configuration to either import
fewer routes or to ' 'increase the imported
route limit.'

--

'Issue the <CmdBold>show lisp {ipv4 |

ipv6} database' '<noCmdBold> command
on both this xTR and the other ' 'site xTR
that sent us the map reply to locate the '
'mis-configuration. Add or remove locators
in the ' 'config of one or both xTRs to make
them have the ' 'same list of configured
locators.'
-'Deconfigure the RLOC, or move it to
another xTR at ' 'the site which does not
have this platform limitation.'

--

'Contact the operator of the ITR that is

issuing ' 'the Map-Requests so that they
can fix the problem ' 'by upgrading their
system.'

--

'Load the Cisco IOS XR Security Package.'

--

If this is seen even with less config, it

probably indicates a memory leak. You
should see wdsysmon messages about
some processes hogging memory in that
case. The Multicast Port Arbitrator
consumer library can't do proper error
The system is running low on memory, if
recovery from malloc failures, so, if after
there is lots of config/routes, try reducing recovering from the low memory you see
it. If there isn't too much config, then check some mhost related problem, you would
if there are possible memory leaks of the
have to restart the process the error
concerned process.
message is seen for.

MPA needs to update its

consumers(ipv[46]_ma) on LCs to setup
mac filters for multicast groups. On a
consumer restart, it triggers a redownload,
if it fails, the MPA restarts (that is the error
Do the following action. Copy the error
recovery mechanism). If there are multiple
message exactly as it appears on the
MPA restarts, contact the development
console or in the system log, call your
team and do the following action. Report
Cisco technical support representative and this to Engineering. Use Topic to search for
provide the representative with the
a similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

The system is running low on memory, if

there is lots of config/routes, try reducing
it. Do the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If there isn't too
much config, then do the following action
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

If this is seen even with less config, it

probably indicates a memory leak. You
should see wdsysmon messages about
some processes hogging memory in that
case. The Multicast Port Arbitrator can't do
proper error recovery from malloc failures,
so, if after recovering from the low memory
you see some mhost related problem, you
would have to restart ipv[46]_mpa.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

There was a problem sending a GSP

message to a certain node. Check if the
node is fine and do fabric_pings to it. Also,
check for processes being blocked on the
LC. If all of that doesn't lead anywhere, do
the following action. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Do the following action.Copy the error

There is an internal mutex problem in the
message exactly as it appears on the
MPA. Please get the coredump for the
console or in the system log, call your
process and the traces. Do the following
Cisco technical support representative and action. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

This would affect the normal processing of

the MPA and hence the mutlicast host
Do the following action. Copy the error
functionality. Get the coredump for the
message exactly as it appears on the
ipv[46]_mpa process the error is seen for,
console or in the system log, call your
contact the DE team and do the following
Cisco technical support representative and action. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

There was an internal problem with the

radix tree inside MPA. This should happen
only under low memory conditions or a
software defect. Please get the running
core dump of the process and do the
following action. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Do the following action. Copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

An internal error happened while deleting a

MPA client on a certain node. The process
is restarted, as this is considered an
unrecoverable condition. Do the following
action. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

If the indicated error is about low memory,

do the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. Else, do the
following action.Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

While attempting to initialize, a system

service failed. This could happen due to
some underlying service having problems
or not initialized. Do the following action.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

None

--

gathered information. Copy the error

message exactly as it appears on the
console or in the system log. Issue the
<CmdBold>show pim trace
mldp<noCmdBold> command 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
<CmdBold>show pim trace
mldp<noCmdBold> output, call your Cisco
technical support representative and
provide the representative with the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log. Issue the
<CmdBold>show buffers<noCmdBold>
command 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 <CmdBold>show
This error is likely to occur during an ENS or
buffers<noCmdBold> output, call your
NRS operation. An error occured while
Cisco technical support representative and reading requests from the pim bgp
provide the representative with the
consumer or while processing a write
gathered information. If the message
request. Check the stacks and the buffers
recurs, copy the error message exactly as it in the tech-support. Please collect the mlib
appears on the console or in the system
and pim mldp traces for further
log, call your Cisco technical support
investigation. Report this to Engineering.
representative and provide the
Use Topic to search for a similar DDTS. If
representative with the gathered
you find none, write a DDTS for this
information.
problem.

gathered information. Copy the error

message exactly as it appears on the
console or in the system log. Issue the
<CmdBold>show pim trace
mldp<noCmdBold> command 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
<CmdBold>show pim trace
mldp<noCmdBold> output, call your Cisco
technical support representative and
provide the representative with the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log. Issue the
<CmdBold>show buffers<noCmdBold>
command 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 <CmdBold>show
buffers<noCmdBold> output, call your
Cisco technical support representative and
provide the representative with the
gathered information. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.
--

This will cause the netio process to restart

and retry again.

This message indicates a possible coding

error that causes ipv4 io shared memory
mapping to fail in proto npmb library.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Please collect the logs mentioned in the

required_info and contact support team.

Error message in preroute manager

process. Pre-route Troubleshooting wiki
link:
http://zed.cisco.com/confluence/display/GS
RTR/C12000++preroute

Please collect the logs mentioned in the

required_info and contact support team.

Error message in preroute manager

process. Pre-route Troubleshooting wiki
link:
http://zed.cisco.com/confluence/display/GS
RTR/C12000++preroute

Please collect the logs mentioned in the

required_info and contact support team.

Error message in preroute manager

process. Pre-route Troubleshooting wiki
link:
http://zed.cisco.com/confluence/display/GS
RTR/C12000++preroute

Please collect the logs mentioned in the

required_info and contact support team.

Internal error message in preroute

manager. Collect console logs. Pre-route
Troubleshooting wiki link:
http://zed.cisco.com/confluence/display/GS
RTR/C12000++preroute

Please collect the logs mentioned in the

required_info and contact support team.

Error message in preroute manager

process. Pre-route Troubleshooting wiki
link:
http://zed.cisco.com/confluence/display/GS
RTR/C12000++preroute

Please collect the logs mentioned in the

required_info and contact support team.

Error message in preroute manager

process. Pre-route Troubleshooting wiki
link:
http://zed.cisco.com/confluence/display/GS
RTR/C12000++preroute

Please collect the logs mentioned in the

required_info and contact support team.

Informational message in preroute

manager process. Pre-route
Troubleshooting wiki link:
http://zed.cisco.com/confluence/display/GS
RTR/C12000++preroute

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The most likely cause is a memory

allocation failure. Otherwise this problem is
due to a software error in raw
http://wikicentral.cisco.com/display/GROUP/
Netinfra-Required-Triaging-Information
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message gives details about what

part of the initialization failed and the error
code should give the reason why. The most
likely cause is a memory allocation failure.
Otherwise this problem is either due to a
software error in raw or in one of the
services that it uses. Other services may
generate their own error messages and
these may provide a clue as to what has
gone wrong. the debug output contain
details of the initialisation process and will
indicate which stage of initialisation failed.
http://wikicentral.cisco.com/display/GROUP/
Netinfra-Required-Triaging-Information
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, contact your Cisco technical support
representative, and provide the
representative with the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

The possible cause could be a memory

allocation failure. Otherwise this problem is
due to a software error in raw or
ipv4_io/ipv6_io is not ready somehow or
blocked on some processes.
http://wikicentral.cisco.com/display/GROUP/
Netinfra-Required-Triaging-Information

Raw process will retry to get more memory

if possible otherwise process will exit with
error and get restarted by sysmgr. no
In the problem recurs, reduce other system further action is needed to recover from
activity to ease memory demands. If
the situation. If memory is repeatedly
conditions warrant, upgrade to a larger
exhausted, then more memory needs to be
memory configuration. Reduce other
freed from other areas of the system or
system activity to ease memory demands. more memory is needed.
If conditions warrant, upgrade to a larger
http://wikicentral.cisco.com/display/GROUP/
memory configuration.
Netinfra-Required-Triaging-Information

Copy the error message exactly as it

appears on the console or in the system
log, contact your Cisco technical support
representative, and provide the
representative with the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Most likely the netio/ipv4_io/ipv6_io is not

ready somhow or blocked on some
processes.
http://wikicentral.cisco.com/display/GROUP/
Netinfra-Required-Triaging-Information

The process will attempt to recover from

this situation by restarting or retrying. If
this message is not seen again and no
other adverse effects are observed then
there is no need to take any action.
Otherwise if the message's error code
indicates that the failure was due to lack of
memory, then take the following action.
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.
If the problem was not caused by memory
allocation and it hasn't been corrected by
subsequence restarts then take the
following action. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
http://wikicentral.cisco.com/display/GROUP/
information.
Netinfra-Required-Triaging-Information

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration.

The most likely cause is a memory

allocation failure.
http://wikicentral.cisco.com/display/GROUP/
Netinfra-Required-Triaging-Information

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The most likely cause is a memory

allocation failure or rsi agent is not
available. Otherwise this problem is due to
a software error in raw.
http://wikicentral.cisco.com/display/GROUP/
Netinfra-Required-Triaging-Information

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration.

The most likely cause is a memory

allocation failure.
http://wikicentral.cisco.com/display/GROUP/
Netinfra-Required-Triaging-Information

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error code should give the reason why.

The most likely cause is a memory
allocation failure. Otherwise this problem is
either due to a software error in raw or in
sysdb or sysdb not available
http://wikicentral.cisco.com/display/GROUP/
Netinfra-Required-Triaging-Information
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'No action is required.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

No action is required.

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
The SysDB Server may need restarting if
gathered information.
the problem persists.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.
'No action is required.'

---

Check that the configured VTY pool(s) can

satisfy this rlogin request based on which
VTYs are currently in use. This can be
checked with 'show users', and looking at
the VTY pool configuration. If the
configuration appears to be consistent then Restarting devc-vty is likely to solve the
try to rlogin with debug rlogin detail on;
problem. Otherwise please contact q-ttythis might indicate where the problem lies. dev with details.
'No action is required.'

--

'No action is required.'

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Reduce other system activity to ease

Memory on the box must be running low memory demands. If conditions warrant,
are there services that can be stopped, or
upgrade to a larger memory configuration. can more memory be added.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.
No action is required.

---

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message gives details about what

part of the initialization failed and the error
code should give the reason why. The most
likely cause is a memory allocation failure.
Otherwise this problem is either due to a
software error in sctp or in one of the
services that it uses. Other services may
generate their own error messages and
these may provide a clue as to what has
gone wrong. the debug output contain
details of the initialisation process and will
indicate which stage of initialisation failed.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears, and report it to your technical
support representative.

While attempting to initialize SMIAP, a

system service failed. The error is indicated
in parenthesis. Check for resource
shortages or blocked processes. The
troubleshooting tips in the following wiki
may be useful: http://wikieng.cisco.com/engwiki/IP_20ARM

Copy the error message exactly as it

appears, and report it to your technical
support representative

Copy the error message exactly as it

appears, and report it to your technical
support representative.

IP address on the management interface

specified is conflicting with the virtual IP
address which is an IP address in the
management interface's network. If the
Either change the virtual IP address to
issue is still seen even after changing the
some other IP address on the management IP address then Report this to Engineering.
interface's network or change the
Use Topic to search for a similar DDTS. If
conflicting IP address on the specified
you find none, write a DDTS for this
management interface.
problem..

If the message is for a management

interface which doesn't exist anymore, e.g.,
due to a failover, this error can be simply
ignored. If it is for an interface which is
active, it indicates inconsistent state in
If the message is for a management
ipv4_smiap, restarting the process might
interface which doesn't exist anymore, e.g., help. If the issue is still seen then Report
due to a failover, this error can be simply
this to Engineering. Use Topic to search for
ignored. If it is for an interface which is
a similar DDTS. If you find none, write a
active, contact technical support.
DDTS for this problem..

Change the IP address on the management

interface or the virtual IP address so that
they are in the same network and are not
the same.

The virtual IP address configured is in a

different network from the management
port specified (for active or standby RP). It
should be in the same network for the
virtual IP address to function properly.

Copy the error message exactly as it

appears, and report it to your technical
support representative

The sysmgr signals are used for orderly

bootup and FO. If the signal fails, you might
see increase in bootup or FO time.
However, this shouldn't affect normal
functionality for SMIAP. If it effects the
functionality of SMIAP then Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem..

IP address on the management interface

specified is conflicting with the virtual IP
address which is an IP address in the
management interface's network. If the
Either change the virtual IP address to
issue is still seen even after changing the
some other IP address on the management IP address then Report this to Engineering.
interface's network or change the
Use Topic to search for a similar DDTS. If
conflicting IP address on the specified
you find none, write a DDTS for this
management interface.
problem..

The information in required_info to be

collected and engineering team to be
notified. Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This problem indicates some instability in

the system, When it happens, running
core-dump of the process identified by the
pid in the above message should be taken
and engineering team should be notified.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If not seen during a process restart of tcp,

please collect the required information.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This problem indicates a potential bug in

the socket library. When it happens,
running core-dump of the process
identified by the pid in the above message
should be taken and engineering team
should be notified. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This problem indicates a potential issue in

the system. When it happens, running
core-dump of the process identified by the
Job ID in the above message should be
taken and engineering team should be
notified. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

The process will try to recover by closing

the session. The required_info has to be
collected. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This problem indicates a potential bug in

the socket library. When it happens,
running core-dump of the process
identified by the pid in the above message
should be taken and engineering team
should be notified. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

The information in required_info to be

collected. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This problem indicates that the number of

applications using the ASYNC sockets has
exceeded the supported limit. Report this
to Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

The information in required_info to be

collected and engineering team to be
notified. Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This problem indicates some instability in

the system, When it happens, running
core-dump of the process identified by the
pid in the above message should be taken
and engineering team should be notified.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

The information in required_info to be

collected and engineering team to be
notified. Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This problem indicates a potential issue in

the system. When it happens, running
core-dump of the process identified by the
pid in the above message should be taken
and engineering team should be notified.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

When this message is seen, the

information in required_info have to be
collected and the engineering team to be
notified. Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This problem indicates a potential bug in

OS Resource Manager code. When it
happens, running core-dump of the process
identified by the pid in the above message
should be taken and engineering team
should be notified. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

This is an informational message and no

action required. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This problem is only informational. No

further steps need to be taken.

The condition may be temporary, but if it

persists, please collect the necessary
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This problem indicates a potential bug in

the socket library. When it happens,
running core-dump of the process
identified by the pid in the above message
should be taken and engineering team
should be notified. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

The transport process will try to recover

from this by retrying/ restarting. If the
messages are not seen again, the problem
was transitory and has been recovered.
There is no need to take any action. If the
messages come continuously, take the
following action. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This problem indicates a very low-level

problem with the debugging infrastructure
and most probably indicates a bug in the
process using the debugs or the debug
infrastructure itself. Get a running
coredump of the process. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

The transport process will try to recover

from this by retrying/ restarting. If the
messages are not seen again, the problem
was transitory and has been recovered.
There is no need to take any action. If the
messages come continuously, take the
following action. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This problem indicates a very low-level

problem with the debugging infrastructure
and most probably indicates a bug in the
process using the debugs or the debug
infrastructure itself. Get a running
coredump of the process. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the error message indicates low memory,

do the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. For any other
errors, do the following action. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

This indicates a very low level problem,

and could be something that is being seen
for other processes as well. If it is, then it
should be looked at as a system level
problem and followed up with OS folks. If
not, contact the relevant development
team. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

When this message is seen, the

information in required_info have to be
collected and the engineering team to be
notified. Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This problem indicates a potential bug in

OS Resource Manager code or socket code.
When it happens, running core-dump of the
process identified by the pid in the above
message should be taken and engineering
team should be notified. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Restart the HSRP process. Reduce other

system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

A HSRP generated notification has failed,

so it may be that the connection to the
System database has failed. Alternatively
there may be a shortage of memory.

Check to see if there are any other errors

on the system which may indicate a
general service-related problem and restart
those services. If the problem is isolated
then restart HSRP. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
There may be a fault in the connection to
representative with the gathered
IM. Use IM show or trace commands to
information.
further isolate the problem.

Retry the configuration on the interface. If

this still fails then do the following. Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and The HSRP UDP socket connection is
provide the representative with the
unavailable. Use UDP show or trace
gathered information.
commands to further isolate the problem.

Retry the configuration on the interface. If

this still fails then do the following. Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

There may be a connection fault to the IM

attribute library. Use IM attribute show or
trace commands to further isolate the
problem.

More than the maximum supported

number of MAC address filters has been
installed for this interface meaning traffic
to some virtual IP addresses will be
dropped. Check that the HSRP
configuration is within the supported scale
range for this interface type. Alternatively,
other protocols may be also installing MAC
address filters: use the show commands for
the underlying interface type to investigate
if any are present and then check whether
the combination of protocols has exceeded
the MAC filter supported scale for this
interface type. Note that the maximum
number of supported MAC address filters
for an interface varies depending on the
interface type and for sub-interfaces the
Reduce the number of HSRP groups on this limit is per parent interface. For HSRP
interface (or the parent if it is a subsupport information please see http://wikiinterface)
eng.cisco.com/engwiki/HSRP_2fVRRP

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

Restart the HSRP process. Copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

It is likely that a service on IOSXR which

HSRP is using is unavailable. Check the
contents of the error message, this should
indicate the appropriate service and nature
of the failure. If the service has any show
commands or show trace commands, use
them to further isolate the problem.

Check the authentication settings on the

local device and the peer device(s)

--

Check the virtual IP address configuration

on the local device and the peer device(s)

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If HSRP does not restart and automatically

recover, do the following. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

If HSRP fails to start up it is likely that a

service on IOSXR which HSRP is using is
unavailable. Check the contents of the
error message, this should indicate the
appropriate service and nature of the
failure. If the service has any show
commands or show trace commands, use
them to further isolate the problem.

Check the HSRP configuration for this

group on the peer device(s). Both HSRP
groups must be operating in the same
mode: either standard or slave.

--

Change the holdtime to be greater than

twice the hellotime.

--

Ensure that ICMP redirects are disabled on

this interface.
--

Try to avoid using HSRP secondary

addresses when HSRP filtered ICMP
redirects are enabled.

--

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Refer
http://wikicentral.cisco.com/display/GROUP/
TCP+Stateful+SwitchOve r+%28SSO%29
and do initial triaging. Contact xrtransports-dev for more details

Check which NSR client was not ready and

if required collect relevant logs for that
process. Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Refer
http://wikicentral.cisco.com/display/GROUP/
TCP+Stateful+SwitchOve r+%28SSO%29
and do initial triaging. Contact xrtransports-dev for more details

The process may attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message gives details about what

part of the initialization failed and the error
code should give the reason why. The most
likely cause is a memory allocation failure.
Otherwise this problem is either due to a
software error in tcp or in one of the
services that it uses. Other services may
generate their own error messages and
these may provide a clue as to what has
gone wrong. the debug output contain
details of the initialisation process and will
indicate which stage of initialisation failed.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

This may be due to a very basic problem

with the communications infrastructure
between the TCP stacks running on
different nodes. Please collect the following
information and restart the standby TCP
process.

Refer
http://wikicentral.cisco.com/display/GROUP/
TCP+Stateful+SwitchOve r+%28SSO%29
and do initial triaging. Contact xrtransports-dev for more details

Understand why NSR failed and take the

necessary steps such as collecting core file,
traces etc. Copy the error message exactly
as it appears on the console or in the
Refer
system log, call your Cisco technical
http://wikicentral.cisco.com/display/GROUP/
support representative and provide the
TCP+Stateful+SwitchOve r+%28SSO%29
representative with the gathered
and do initial triaging. Contact xrinformation.
transports-dev for more details

Understand why standby is not healthy and

take the necessary steps such as collecting
core file, traces etc. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
-Check the configuration on both ends and
make sure that the password or
authentication information is identical.

contact xr-tranports-dev for more details

Identify the application that owns the

affected socket and try to examine its
traces and debugs. If the problem persists,
collect the output of show commands,
traces and running coredumps of the
application as well as TCP.
contact xr-tranports-dev for more details

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The most likely cause is a memory

allocation failure. Otherwise this problem is
due to a software error in tcp Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Change the keychain configuration to not

have a key-id greater than 63. No need to
re-configure it under BGP or to clear BGP
neighbors.

contact xr-tranports-dev for more details

Check the configuration of the peer

specified and reconfigure it so that its
keychain only has cryptographic algorithms
supported by IOS-XR.
contact xr-tranports-dev for more details

Check the keychain to see if it has any

active keys. Sometimes, this error might
come if there is no overlap between the
send-keys. In that case, if keychain shows
that there is an active key, then this error
can be ignored. Else, change the
configuration to have an active send-key. If
there is an active key and you still see the
error, that indicates that there is some
configuration problem with the active sendkey. Correct that and if that doesn't work,
contact Copy the error message exactly as
it appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information..
contact xr-tranports-dev for more details

Check the keychain to see if it has any

active keys. Sometimes, this error might
come if there is no overlap between the
send-keys. In that case, if keychain shows
that there is an active key, then this error
can be ignored. Else, change the
configuration to have an active send-key.

contact xr-tranports-dev for more details

Currently we only support SHA1-12 and

MD5-16 with TCP EA. Other MAC algorithms
won't work. IOS-XR doesn't have support
for AES-12 which is mentioned in the EA
draft. MD5-16 is supported so that we allow
Check the MAC algorithms supported with two kinds of cryptographic algorithms and
TCP Enhanced Authentication by IOS-XR
for testing with key-rollover to a different
and modify the MAC algorithm accordingly. algorithm.

The process will attempt to recover from

this situation by restarting or retrying. If
this message is not seen again and no
other adverse effects are observed then
there is no need to take any action.
Otherwise if the message's error code
indicates that the failure was due to lack of
memory, then take the following action.
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.
If the problem was not caused by memory
allocation and it hasn't been corrected by
subsequence restarts then take the
following action. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

The error code should give the reason why.

The most likely cause is a memory
allocation failure. Otherwise this problem is
either due to a software error in tcp or in
ifmgr or ifmgr not available Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message gives details about what

part of the initialization failed and the error
code should give the reason why. The most
likely cause is a memory allocation failure.
Otherwise this problem is either due to a
software error in tcp or in one of the
services that it uses. Other services may
generate their own error messages and
these may provide a clue as to what has
gone wrong. the debug output contain
details of the initialisation process and will
indicate which stage of initialisation failed.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Identify the application that owns the

affected socket and try to examine its
traces and debugs. If the problem persists,
collect the output of show commands,
traces and running coredumps of the
application as well as TCP.
contact xr-tranports-dev for more details

In the problem recurs, reduce other system

activity to ease memory demands. If
conditions warrant, upgrade to a larger
memory configuration. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration.

Tcp process will retry to get more memory

if possible otherwise process will exit with
error and get restarted by sysmgr. no
further action is needed to recover from
the situation. If memory is repeatedly
exhausted, then more memory needs to be
freed from other areas of the system or
more memory is needed.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
The most likely cause is a memory
memory configuration.
allocation failure.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
The most likely cause is a memory
memory configuration.
allocation failure.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error code should give the reason why.

The most likely cause is a memory
allocation failure. Otherwise this problem is
either due to a software error in tcp or in
sysdb or sysdb not available. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
The SysDB Server may need restarting if
gathered information.
the problem persists.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Please send the following infomation: 'show

interface' for the interface in question.

*SH_TECH*

--

*SH_TECH*

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Please send the following information:

'show proc ipv4_rib'; 'show tech-support
rib' for ipv4/ipv6, whichever was used.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Please send the following infomation: 'show

interface' for the interface in question. can
you ping the interface? does telnet work
without the source interface specified?

*SH_TECH*

--

*SH_TECH*

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. The router can continue to be
used.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question can you ping the
interface? does telnet work if you try
again?

*SH_TECH*

--

*SH_TECH*

--

No action is required.

--

No action is required.

--

No action is required.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question can you ping the
interface? does telnet work if you try
again?

*SH_TECH*

--

No action is required.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question Is interface up? Does
telnet work if you try again?

No action is required.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question Can you ping the
interface? Does telnet work if you try
again?

*SH_TECH*

--

*SH_TECH*

--

*SH_TECH*

--

*SH_TECH*
*SH_TECH*

---

No action is required.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question can you ping the
interface? does telnet work if you try
again?

No action is required.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question can you ping the
interface? does telnet work if you try
again?

No action is required.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question can you ping the
interface? does telnet work if you try
again?

No action is required.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question can you ping the
interface? does telnet work if you try
again?

No action is required.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question can you ping the
interface? does telnet work if you try
again?

No action is required.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question can you ping the
interface? does telnet work if you try
again?

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. The router can continue to be
used.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question can you ping the
interface? does telnet work if you try
again?

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. The router can continue to be
used.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question can you ping the
interface? does telnet work if you try
again?

Copy the error message exactly as it

appears, and report it to your technical
support representative.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Please check the IP address of the peer. If it

is not a trusted or known address, it could
be a DoS attack. Please take steps to install
appropriate ACLs or use MPP to avert the
DoS attacks.
--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Check that the configured VTY pool(s) can

satisfy this telnet request based on which
VTYs are currently in use. This can be
checked with 'show users', and looking at
the VTY pool configuration. If the
configuration appears to be consistent then Restarting devc-vty is likely to solve the
try to telnet with debug telnet detailed on; problem. Otherwise please contact q-ttythis might indicate where the problem lies. dev with details.
'Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and The server may need restarting if the error
provide the representative with the
persists. The numerical error code is an
gathered information.
'errno' value.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and The server may need restarting if the error
provide the representative with the
persists. The numerical error code is an
gathered information.
'errno' value.
Reduce other system activity to ease
Memory on the box must be running low memory demands. If conditions warrant,
are there services that can be stopped, or
upgrade to a larger memory configuration. can more memory be added.

No action is required.

--

'Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.'

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
The SysDB Server may need restarting if
gathered information.
the problem persists.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

'No action is required.'

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. The router can continue to be
used.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question can you ping the
interface? does telnet work if you try
again?

Copy the error message exactly as it

appears, and report it to your technical
support representative.

--

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. The router can continue to be
used.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. The router can continue to be
used.

Please send the following information:

'show proc tcp' 'show interface' for the
interface in question can you ping the
interface? does telnet work if you try
again?

Internal error. Restart telnetd process to

overcome.

collect debug telnetd logs

It is just a debug log to indicate mapping to

stats failed. Can restart telnetd session for
mapping stats.
collect debug telnetd logs
Internal error. Process will retry the
operation.

collect debug telnetd logs

Internal error. Restart telnetd process to

overcome.

collect debug telnetd logs

No action is required.

--

No action is required.

--

Please get the information specified under

the component required_info and call your
Cisco technical support representative and
provide the gathered information with this
error message text. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
This is a warning message and need to
information.
verify the dscp configuration.

tftp_fs process retries for default number of

times before timing out and aborting the
write to tftp when it is not able to reach the
tftp server. Please check the following
options to recover from this situation 1>
Connectivity to the remote tftp server. If ip
connectivity isnot present tftp_fs wont be
able to write 2> The number of retries in
tftp_fs is configurable. The user can
attempt to increase the number of retries
and retry the command 3> If the above
two options dont help, please please save
the file to the disk on the router, compress
it and then transfer the file to tftp server. If
none of the options help Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Some of the clients dont handle the error

returned by tftp_fs and continue to write.
This leads to the blockage on tftp_fs. In an
attempt to avoid long blockages when
tftp_fs is having connectivity problems with
the tftp server, it stops writing after it
detects lot of failures in its writes and
prints this ios-msg in the end. Report this
to Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Some of the tftp_fs clients will be taking lot

of gap between writes. If this message
appears, retry the transfer after storing the
if this problem persists, save the file to disk disk. Report this to Engineering. Use Topic
first and then transfer the saved file via
to search for a similar DDTS. If you find
tftp.
none, write a DDTS for this problem.

The arguments supplied to tts are most

probably wrong. Check the arguments.

Contact xr-transports-dev for more details

Check the stacktrace, analyze TCP stats,

etc.

Contact xr-transports-dev for more details

The arguments supplied to tts commands

are most probably wrong. Check the
arguments. Or the sequence of operations
could be wrong.
Contact xr-transports-dev for more details
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

None

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The most likely cause is a memory

allocation failure. Otherwise this problem is
due to a software error in udp Report this
to Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error message gives details about what

part of the initialization failed and the error
code should give the reason why. The most
likely cause is a memory allocation failure.
Otherwise this problem is either due to a
software error in udp or in one of the
services that it uses. Other services may
generate their own error messages and
these may provide a clue as to what has
gone wrong. the debug output contain
details of the initialisation process and will
indicate which stage of initialisation failed.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, contact your Cisco technical support
representative, and provide the
representative with the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

The possible cause could be a memory

allocation failure. Otherwise this problem is
due to a software error in udp or
ipv4_io/ipv6_io is not ready somehow or
blocked on some processes.

In the problem recurs, reduce other system

activity to ease memory demands. If
conditions warrant, upgrade to a larger
memory configuration. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration.

Udp process will retry to get more memory

if possible otherwise process will exit with
error and get restarted by sysmgr. no
further action is needed to recover from
the situation. If memory is repeatedly
exhausted, then more memory needs to be
freed from other areas of the system or
more memory is needed.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
The most likely cause is a memory
memory configuration.
allocation failure.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The most likely cause is a memory

allocation failure or rsi agent is not
available. Otherwise this problem is due to
a software error in udp.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
The most likely cause is a memory
memory configuration.
allocation failure.

The process will attempt to recover from

this situation by restarting. If this message
is not seen again and no other adverse
effects are observed then there is no need
to take any action. Otherwise if the
message's error code indicates that the
failure was due to lack of memory, then
take the following action. Reduce other
system activity to ease memory demands.
If conditions warrant, upgrade to a larger
memory configuration. If the problem was
not caused by memory allocation and it
hasn't been corrected by subsequence
restarts then take the following action.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The error code should give the reason why.

The likely cause is a memory allocation
failure, Otherwise this problem is either
due to a software error in udp or in sysdb
or sysdb not available Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Retry the configuration on this interface. If

this still fails then do the following. Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

It is likely that there is a fault in the

connection to either IM or sysdb. Use IM
and sysdb show or trace commands to
further isolate the problem.

Reduce the number of virtual routers on

this interface (or the parent if it is a subinterface)

More than the maximum supported

number of MAC address filters has been
installed for this interface meaning traffic
to some virtual IP addresses will be
dropped. Check that the VRRP
configuration is within the supported scale
range for this interface type. Alternatively,
other protocols may be also installing MAC
address filters: use the show commands for
the underlying interface type to investigate
if any are present and then check whether
the combination of protocols has exceeded
the MAC filter supported scale for this
interface type. Note that the maximum
number of supported MAC address filters
for an interface varies depending on the
interface type and for sub-interfaces the
limit is per parent interface. For VRRP
support information please see http://wikieng.cisco.com/engwiki/HSRP_2fVRRP

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

Check the authentication settings on the

local device and the peer device(s)

--

Reconfigure the VRRP group with the

correct remote IP address using the
command 'vrrp <vrid> bfd fast-detect
<remote-ip>'

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If VRRP does not restart and automatically

recover, do the following. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

If VRRP fails to start up it is likely that a

service on IOSXR which VRRP is using is
unavailable. Check the contents of the
error message, this should indicate the
appropriate service and nature of the
failure. If the service has any show
commands or show trace commands, use
them to further isolate the problem.

Restart the VRRP process. Copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

It is likely that a service on IOSXR which

VRRP is using is unavailable. Check the
contents of the error message, this should
indicate the appropriate service and nature
of the failure. If the service has any show
commands or show trace commands, use
them to further isolate the problem.

No action is required.

--

Check the VRRP configuration for this VRID

on the peer device(s). Both VRRP virtual
routers must be operating in the same
mode: either regular or slave.
-No action is required.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Error message for Eagle Driver.

The Fault Manager will reset the linecard if

the error recovery failed, search through
the event logs, if there is no any message
indicating that the Fault Manager resets the Search the event logs for events/errors
linecard, try to do a manually reset with
related to the Fault Manager, the PLIM soft
CLI: 'hw-module location 0/x/cpu0 reload' If error recovery could be caused by the error
the message recurs, copy the error
on the other ASIC. If the error happens
message exactly as it appears on the
every time after linecard reload, this may
console or in the system log, call your
indicate a hard error with the linecard. For
Cisco technical support representative and more details regarding the engine-3 POS
provide the representative with the
linecard PLIM driver, please refer to EDCSgathered information.
264772

The System Manager process (sysmgr) will

automatically respawn this process, up to a
fixed number of times when this error is
encountered, to recover. Execute 'show
process e48_plim_oc3 location 0/x/cpu0' to
verify that the process is up and running. If
it is still non-operational, try doing 'process
restart e48_plim_oc3 location 0/x/cpu0'. If
the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Search the event logs for events/errors

related to the failure reason PLIM driver
errors generally point to system issues.
There may be other processes complaining
as well in this case. For more details
regarding the engine-3 POS linecard PLIM
driver, please refer to EDCS-264772

Execute 'show int pos 0/x/0/x' while the

traffic is running on the interface to confirm
if the counter is still working, if not, restart
PLIM driver with CLI: 'process restart
e48_plim_oc3 location 0/x/cpu0' If the
message recurs, copy the error message
This errors generally point to system
exactly as it appears on the console or in
issues. There may be other processes
the system log, call your Cisco technical
complaining as well if the issue keeps
support representative and provide the
happening. For more details regarding the
representative with the gathered
engine-3 POS linecard PLIM driver, please
information.
refer to EDCS-264772

This error has no effect on any feature

except that debug information cannot be
turned on by CLI 'debug plim location
0/x/CPU0'. Restarting the process with CLI:
'process restart e48_plim_oc3 location
0/x/CPU0' may resolve the problem.
--

Recommended action is to repair the

source of the alarm.

--

*SUPPORT*

Failed to send a message between the

TREX (service linecard's switching FPGA)
driver client and the TREX driver server.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

*SUPPORT*

This error message indicates that an

unrecoverable fatal error was encountered
by the service linecard's switching FPGA
(TREX), which resulted in linecard reload. If
the failure is persistent replace the
linecard. If that doesn't help, Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

*SUPPORT*

This error message indicates that an

unrecoverable fatal s/w error was
encountered by the service linecard's
switching FPGA (TREX) driver. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the problem persists reload the linecard.

If that doesn't help, Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

This error message indicates that board PLL

lock failure was detected by the service
linecard's switching FPGA (TREX) driver.
Replace the linecard. If that doesn't help,
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the error message appears rapidly, or if it

persists, reload linecard. If that doesn't
help, Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This error message indicates that a nonfatal error was encountered by the service
linecard's switching FPGA (TREX). If the
failure is persistent, replace the linecard. If
that doesn't help, Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

This error message indicates that the

service linecard's switching FPGA(TREX)
driver detected that at least one of the
If the problem persists reload the linecard. TREX FPGA interfaces is in unlock state.
If that doesn't help, Copy the error
This may be an internal TREX error or an
message exactly as it appears on the
external TREX error. Replace the linecard. If
console or in the system log, call your
that doesn't help, Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

*NONE*

--

*NONE*

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
Error message for ut2 Driver.

*SUPPORT*

This error message indicates that an

unrecoverable fatal error was encountered
by the service linecard's I/O FPGA (XENA),
which resulted in linecard reload. If the
failure is persistent, replace the linecard. If
that doesn't help, Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

*SUPPORT*

This error message indicates that an

unrecoverable fatal s/w error was
encountered by the service linecard's I/O
FPGA (XENA) driver. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Physically remove the Daughter board from

the service card.
--

*NONE*

--

No action is required.

This message indicates an Rx fault

occurred on the given interface. If this is
due to a HW fault, the interface should
recover. If this is due to an external reason
(fiber cut, far end down) it will recover
when the problem is fixed. sh controller
tengig <> sh plim xge-plim trace state <>

This message is printed when Other

Sequence Ordered Set Interrupt is
triggered. The Other Sequene Order set
received can be caused by intentionally,
bad link or underlying PCS/PMD logic
malfunction. The probability of bad link is
extremely low. underlying PCS/PMD logic
malfunction should be able to caught by
Suggest running diags to determine which probing these two hardware components.
part of the Rx path is broken and
sh controller tengig <> sh plim xge-plim
potentially RMA to replace the bad
trace state <> sh controllers plim asic pla
hardware.
trace <>
No action is required.

Should recover. If not, this usually indicates

a system wide issue.

No action is required.

Throw out the PLIM

Try to shut/no shut the port. If the MAC

does not get enabled, then A physical OIR
of the Xenpak device will be needed. Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

This message indicates that the XGXS

failed to syncronize its lanes. Software
attempted to recover the syncronization by
reseting the XGXS Rx lanes. The reset's
failed so the MAC got disabled. Try a
shut/no shut on the interface in question. If
this still fails, a physical OIR of the Xenpak
on the failed port is needed. sh interface
<> sh diag sh controller tengig <>

This message indicates that the XGXS

Try to shut/no shut the port. If the MAC
failed to syncronize its lanes. Software
does not get enabled, then A physical OIR attempted to recover the syncronization by
of the Xenpak device will be needed. Copy reseting the XGXS Tx lanes. The reset's
the error message exactly as it appears on failed so the MAC got disabled. Try a
the console or in the system log, call your shut/no shut on the interface in question. If
Cisco technical support representative and this still fails, a physical OIR of the Xenpak
provide the representative with the
on the failed port is needed. sh interface
gathered information.
<> sh diag sh controller tengig <>
This message indicates an XFP was
inserted in the given interface and it failed
to power on due to a hardware fault.
Verify the XFP is supported in the hardware Replace this XFP with a Cisco supported
manuals and is inserted correctly.
XFP.

1. Remove the Xenpak and check if it is

Cisco qualified Xenpak. 2. If it is Cisco
qualified Xenpak, check DWDM Xenpak
placement rule.

This message indicates that the hardware

has generated an interrupt that signals
that the OIM has been physically inserted
in a port, which violates OIM rule. 'unknown
Xenpak' indicates un-identified Xenpak
type, which is not a MSA compliance
Xenpak type or a Cisco DWDM Xenpak.
'DWDM Xenpak rule violation' indicates
Cisco DWDM Xenpak placement rule
violation. Here is Cisco DWDM Xenpak
placement rule. 1. The recommanded slot
for DWDM Xenpaks are 0,2,4,6. 2. If DWDM
Xenpak presents, no more than 4 Xenpaks
can be powered on. 3. Adjacent slots to
DWDM Xenpak should be empty, or not
powered on.

Check if the process 'shelfmgr' is up and

running on the RP. Try to reload the LC to
see if that helps. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This message indicates that the driver

process was unable to get a MAC address
from shelfmgr for the interface. Please
collect the output of sh interface <> sh
diag The MAC address eeprom on the RP
might be corrupted or not programmed
correctly. Reprogram the mac address
eeprom if that is the case.

No action is required.

This message indicates an Rx loss or LF

occurred on the given interface. If this is
due to a HW fault, the interface should
recover. If this is due to an external reason
(fiber cut, far end down) it will recover
when the problem is fixed. sh controller
tengig <> sh plim xge-plim trace state <>

No action is required.

This message indicates a remote fault

occurred on the given interface. This is
normally due to a far end local fault. When
the far end fixes its issue the interface
should recover and come back up. sh
controller tengig <> sh plim xge-plim trace
state <>

No action is required.

Informational message for plim_8p_10ge

driver.

No action is required.

This messages indicates that the hardware

has generated an interrupt that signals
that the OIM has been physically
inserted/removed for the specified port at
the given location. If this error message is
seen when a physical OIM OIR hasn't
occurred, this may indicate a hardware
problem or a software bug, please gather
the output of the 'show controllers all'
command, and contact the s/w and
hardware developers.

Verify the Xenpak is supported in the

hardware manuals

This message indicates an unsupported

Xenpak was inserted in the given interface.
Replace this Xenpak with a Cisco supported
Xenpak.

This message indicates an unsupported

XFP was inserted in the given interface.
Verify the XFP is supported in the hardware Replace this XFP with a Cisco supported
manuals
XFP.

No action is required.

This message indicates an XFP was

inserted in the given interface and there
was a failure in reading the EEPROM. Retry
is attemped.

Do a restart of cmn_acct_svr process by

using the command ' process restart
cmn_acct_svr location <loc> '

Try doing a restart of cmn_acct_svr process

by using the command ' process restart
cmn_acct_svr location '. If the problem is
not solved contact the DE.

A software internal error. The acct_svr

process will be restarted, and the system
will most likely recover without negative
impact, unless the error persists. Report
this to Engineering. Use Topic to search for
The process will be restarted automatically a similar DDTS. If you find none, write a
to recover.
DDTS for this problem.

The process acct_svr will automatically be

restarted to recover.

A software internal error. The acct_svr

process will be restarted, and the system
will most likely recover without negative
impact, unless the error persists. Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

show accounting trace location X/X/X

A software internal error. The acct_svr

process will be restarted, and the system
will most likely recover without negative
impact, unless the error persists.

show accounting trace location X/X/X

A software internal error. The acct_svr

process will be restarted, and the system
will most likely recover without negative
impact, unless the error persists.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

No action is required.

A software internal condition is detected.

There will most likely be no negative
impact to the system, unless the usage
above the threshold condition persist for a
long period of time. In that case, please
turn on 'debug accounting stats location
X/X/X' and collect the debug information.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required.

The flow report uses the forwarding asic

clock which may be slightly off from the
system clock.To correct the timestamp, the
HFA clock delta is retrieved and on failure,
the previously recorded delta is used. This
log is printed out after so many
consecutive failures to retrieve the clock
delta,which may lead to skewed
timestamps in the flow report. There will
most likely be no negative impact to the
system, unless the error persists for long.
In that case,collect the 'show accounting
trace location X/X/X' logs. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

No action is required.

A software internal condition is detected.

There will most likely be no negative
impact to the system, unless the usage
above the threshold condition persist for a
long period of time. In that case, please
turn on 'debug accounting stats location
X/X/X' and collect the debug information.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

A software internal condition is detected.

There will most likely be no negative
impact to the system, unless the usage
above the threshold condition persist for a
long period of time. In that case, please
turn on 'debug accounting stats location
X/X/X' and collect the debug information.
Please also attach to the LC and copy the
file /tmp/rx_cam_fifo_dump or
/tmp/tx_cam_fifo_dump. Also collect the
follow data on the router: show controllers
pse ingress precam interface location <>
show controllers pse ingress precam
If the message recurs, copy the error
hardware 2 index <> location <>
message exactly as it appears on the
show_wahoo -s [rx|tx] -r nfc or show_alpha
console or in the system log, call your
-s [rx|tx] -r nfc Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

Reload of LC will be workaround. If the

message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Tcam carving can be inconsistent with the

configured values. Reload LC is the work
around.

This error indicates that the HFA Alpha

driver detected a service impacting
condition. This does not mean the ASIC HW
is at fault always. The message will inform
the severity. Please capture the following
infomation on the node/lc where the
problem occurred: - alpha_phb_dump_slot_
- show_alpha -s tx -R cpu - show_alpha -s tx
-R ppc - show_alpha -s rx -R cpu show_alpha -s rx -R ppc Execute 'show
process hfa_main location 0/x/cpu0' to
The System Manager process (sysmgr) will verify that the process is up and running. If
automatically respawn this process, up to a it is still non-operational, try doing 'process
fixed number of times when this error is
restart hfa_main location 0/x/cpu0'.
encountered, to recover. If the message
Reloading the line card where the problem
recurs, copy the error message exactly as it is seen using 'hw-module location reload' in
appears on the console or in the system
admin mode will recover in most of the
log, call your Cisco technical support
cases else reload the router. Report this to
representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

Non service impacting condition is

detected for HFA Alpha driver. If the error is
If the message recurs, copy the error
too persistent then Report this to
message exactly as it appears on the
Engineering. Use Topic to search for a
console or in the system log, call your
similar DDTS. If you find none, write a
Cisco technical support representative and DDTS for this problem.. Please capture all
provide the representative with the
the console messages and the output of
gathered information.
show log | incl hfa_main

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Please refer to the following link.

http://zed.cisco.com/confluence/display/GS
RTR/Debugging+Thread_20+Count+preca This message can be ignored if there is no
m1_profile_drop_count
service impact in forwarding packets.

By default, the message logging is ON. If

there is no multicast configuration and if
the node is recieving the multicast
1.Check the multicast configuration. . 2.If traffic,the messages can be ignored and
the configuration is proper,try clear mfib
can be disabled by the following command
database location <LC where the msgs are on LC Command: show_alpha -k off Enable
seen> 3.If the issue is still seen,Reload the once multicast is again configured:
LC.
Command: show_alpha -k on

None.

Informational message for HFA Alpha

driver. It indicates that the alpha PSE on
the line card where the message is
reported from doesn't support 7 Tuple L4
LBA.

Informational message for HFA Alpha

driver. It indicates that the alpha version
used on the line card where the message is
Debug message only. No action is required. reported from is not supported or old.

Debug message only. No action is required. -Non service impaction condition is

detected for HFA Alpha driver. If the error is
too persistent then Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
Debug message only. No action is required. DDTS for this problem.

Non service impacting condition detected

for HFA Alpha driver. If the error is too
persistent then Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.. Please capture all the console
messages and the output of show log | incl
Debug message only. No action is required. hfa_main
An error would be reported to the client
application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

An error would be reported to the client

application which should handle this
condition appropriately. *None*

--

An error would be reported to the client

application which should handle this
condition appropriately. *None*

--

An error would be reported to the client

application which should handle this
condition appropriately. *None*

--

An error would be reported to the client

application which should handle this
condition appropriately. *None*

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

No action is required.

--

No action is required.

--

Run the board diagnostics.

This is a message in the Asic Scan Server

to indicate that it has triggerred a critical
alarm and will result in node bringdown.
Look at the cause string in errmsg.

No action is required.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Check if the interface or pvc exists and

retry the operation. Collect required_info.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Possible mismatch in the databases of IM,

atm_ilmi & sysdb.
http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

Action to be taken based on the error

message. In case of initilization/registration
failures. Restart the atm_ilmi process for
recovering. Check memmory conditions in
case of memory related msg. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

This failure can happen mainly during the

initialization or due to low memory on the
node. The message itself will be quite
explanatory.
http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration.
process restart of atm_ilmi. If that does not
recover spa/plim reload.

This error should not happen. The config

apply will fail.
http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Check memory conditions on the node.

Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.

Memory conditions on the node must be

checked. There could be processes
consuming more than ideal amount of
memory.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

http://enwiki.cisco.com/InterfaceManager/Tr
oubleShooting/Data#Network_I.2FO_.28Net
IO.29_-_SW

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

http://enwiki.cisco.com/InterfaceManager/Tr
oubleShooting/Data#Network_I.2FO_.28Net
IO.29_-_SW

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

http://enwiki.cisco.com/InterfaceManager/Tr
oubleShooting/Data#Network_I.2FO_.28Net
IO.29_-_SW

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

http://enwiki.cisco.com/InterfaceManager/Tr
oubleShooting/Data#Network_I.2FO_.28Net
IO.29_-_SW

Memory on the box must be running low Reduce other system activity to ease
unnecessary services or programs should
memory demands. If conditions warrant,
be stopped, or more memory should be
upgrade to a larger memory configuration. added.
Check why the rules file has been modified.
The specified line number will give a clue atm_netio.rules file's parsing got failed
for failed parsing.
because it was wrongly modified.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

atm_netio.rules files can't be located. This

should not happen, a check should be
made in the entire directory.

This happens to be a rare case, if the

message persists across every recreate,
No debugging of this component will be
the memory conditions should be checked available, but it should otherwise function
at the node
properly.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. restart the atm_oam process.

Error can happen while registering with IM

or because of the mismatch in IM and atm
Databases
http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. atm_oam is not the owner of
anything. Process restart of atm_oam will
recover the issue

http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

This error occurs during the

verification/apply of a particular
configuration in the OAM. This syslog
printed only when the err_msg is not
allocated by the sysdb. So, basically this
Reduce other system activity to ease
syslog will give information why config
memory demands. If conditions warrant,
apply/verify failed
upgrade to a larger memory configuration. http://zed.cisco.com/confluence/display/GS
Error in the config that is being committed. RTR/C12000+SPA+ATM
Check the configuartion and change it
http://zed.cisco.com/confluence/display/GS
according to the error.
RTR/PI+L2+ATM

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information. retry the commit
operation of the failed tuple based on the
error message

Not able to set a value in sysdb. This might

be because of a connection problem with
the sysdb. Action to be taken based on the
error message. In worst case restart the
atm_vcm process
http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

Failure during initialization of atm_rm dll.

Will not be able to checkpoint or debug.
http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
Restart the atm_vcm process. Initialization http://zed.cisco.com/confluence/display/GS
failure will lead to lot of other errors.
RTR/PI+L2+ATM
Either the box needs more memory, or
there is a memory leak in some process in
the system, or some process is hogging all
the memory.
Check for memory conditions in the
http://zed.cisco.com/confluence/display/GS
system. LC reload alone can recover from RTR/C12000+SPA+ATM
this situation. All info to be collected before http://zed.cisco.com/confluence/display/GS
the reload.
RTR/PI+L2+ATM

If the configuration of the vc-class exists

under the main-int, that will be inherited to
all the vcs under it. Check the new
check vc class configuration on interface If configuration that is being applied and
there are vcs you want specific QoS values make sure there are no conflicts.
for under the main interface, try
http://zed.cisco.com/confluence/display/GS
configuring QoS on these vcs before
RTR/C12000+SPA+ATM
applying class to the interface in order to
http://zed.cisco.com/confluence/display/GS
stop unwanted inheritance.
RTR/PI+L2+ATM

Check memory conditions on the node.

A very corner case when the component

itself fails to initialize. This could be an
internal error like event manager creation
failure. Contact DE, with the logs
mentioned.

This happens to be a rare case, if the

message persists across every recreate
memory conditions to be checked on the
node.

No debugging of this component will be

available, but it should otherwise function
properly. Check if some process is
consuming high amount of memory.
Following commands will be helpful: sh
process mem <> sh memory summary <>

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. If the error is during the
initialization, restart the process.

http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
http://zed.cisco.com/confluence/display/GS
representative with the gathered
RTR/C12000+SPA+ATM
information. Collect the required_info, if the http://zed.cisco.com/confluence/display/GS
message persists across multiple recreates. RTR/PI+L2+ATM
A shortage of memory could possibly result
in this error. Check how much memory is
Reduce other system activity to ease
available at the location where the error
memory demands. If conditions warrant,
was reported
upgrade to a larger memory configuration. http://zed.cisco.com/confluence/display/GS
LC reload alone will recover the situation. RTR/C12000+SPA+ATM
All information to be collected before the
http://zed.cisco.com/confluence/display/GS
reload
RTR/PI+L2+ATM
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. Collect required info and
contact TAC.

There is some issue re-establishing

connection to the packet server.
http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. restart the atm_socket
process.

If this failure happens, atm_socket will not

recieve or send any control packets
resulting in the loss of those packets. This
may lead to interfaces going dowm
http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

Copy the message as it appears exactly on

the console or system log. Run diagnostics
If the message recurs, copy the error
on the line card and monitor the recurrence
message exactly as it appears on the
of the errors. If the errors are persistent,
console or in the system log, call your
replace the hardware or Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

No action is required.

This is just a debug message.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. Either caps addition or
removal failed. Depending on the failure,
reapply the configuration.

Error occured while trying to update

IM(Interface Manager) with the info we
have. Error with the IM(Interface Manager).
http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. Most of the errors are because
of low memory. Others are not very critical.
LC reload will resolve the low memory
condition. Information to be collected
before the reload

This error majorly happen when there is

low memory on the LC. LC reload alone can
resolve this issue.
http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

We will not be able to apply any config if

this error occurs. Process restart might
recover the issue. Decision to be taken
based on the error message Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.
Restart the atm_vcm process to recover
http://zed.cisco.com/confluence/display/GS
Reduce other system activity to ease
RTR/C12000+SPA+ATM
memory demands. If conditions warrant,
http://zed.cisco.com/confluence/display/GS
upgrade to a larger memory configuration. RTR/PI+L2+ATM
This is a corner case and should not occur
multiple times. Collect required info if it
persists.

While registering verification with SysDB

for CTT config commands, the connection
with SysDB couldn't succeed.

Collect required info and contact TAC.

The CTT manager singal handler process

detecte a segmentation fault.
http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

No action required.

A notification that Connection Traffic Table

manager is going to be started.

No action required.

While cell packing, the PCI is converted to

VPI and VCI. This is just an info for the PCI
value.
http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

No action required.

The message provides an info that the

method under the argument has been hit.

No action required.

http://zed.cisco.com/confluence/display/GS
RTR/C12000+SPA+ATM
http://zed.cisco.com/confluence/display/GS
RTR/PI+L2+ATM

GSR SPA Driver encountered an error while

bringing up the SPA devices. This indicates
Copy the error message exactly as it
some fatal issue with the spa device.
appears on the console or in the system
Identify the trigger and collect the console
log. If you cannot determine the nature of logs. If the problem cannot be resolved
the error from the error message text, call from the error message Report this to
your Cisco technical support representative Engineering. Use Topic to search for a
and provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Such failures are not expected under

normal scenario and the only information
to go on will be in the message displayed
and the console logs during the problem. In
Copy the error message exactly as it
these kind of problems, the trigger for the
appears on the console or in the system
problem should be identified. If the
log. If you cannot determine the nature of problem cannot be resolved based on the
the error from the error message text, call error message Report this to Engineering.
your Cisco technical support representative Use Topic to search for a similar DDTS. If
and provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

Such failures are not expected under

normal scenario and the only information
to go on will be in the message displayed
and the console logs during the problem. In
Copy the error message exactly as it
these kind of problems, the trigger for the
appears on the console or in the system
problem should be identified. If the
log. If you cannot determine the nature of problem cannot be resolved based on the
the error from the error message text, call error message Report this to Engineering.
your Cisco technical support representative Use Topic to search for a similar DDTS. If
and provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

GSR SPA Driver encountered an error while

initializing the SPA device. This indicates
Copy the error message exactly as it
some fatal issue with the spa device.
appears on the console or in the system
Identify the trigger and collect the console
log. If you cannot determine the nature of logs. If the problem cannot be resolved
the error from the error message text, call from the error message Report this to
your Cisco technical support representative Engineering. Use Topic to search for a
and provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Such failures are not expected under

normal scenario and the only information
to go on will be in the message displayed
and the console logs during the problem. In
Copy the error message exactly as it
these kind of problems, the exact trigger
appears on the console or in the system
for the problem should be identified. If the
log. If you cannot determine the nature of problem cannot be resolved based on the
the error from the error message text, call error message Report this to Engineering.
your Cisco technical support representative Use Topic to search for a similar DDTS. If
and provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

Such failures are not expected under

normal scenario and the only information
to go on will be in the message displayed
and the console logs during the problem. In
Copy the error message exactly as it
these kind of problems, the trigger for the
appears on the console or in the system
problem should be identified. If the
log. If you cannot determine the nature of problem cannot be resolved based on the
the error from the error message text, call error message Report this to Engineering.
your Cisco technical support representative Use Topic to search for a similar DDTS. If
and provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show techsupport atm <noCmdBold> command 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
<CmdBold>show tech-support atm
<noCmdBold> output, call your Cisco
technical support representative and
provide the representative with the
gathered information. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
This error indicates that the ATM driver is
representative and provide the
not able to initialize properly. Collect above
representative with the gathered
show tech when this message is seen on
information.
the node.

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show techsupport atm <noCmdBold> command 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
<CmdBold>show tech-support atm
<noCmdBold> output, call your Cisco
technical support representative and
provide the representative with the
gathered information. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
This run time error indicates that the ATM
log, call your Cisco technical support
driver is failed to load PAL library. Either
representative and provide the
SPA/LC reload may resolve the issue.
representative with the gathered
Collect above show tech when this
information.
message is seen on the node.

Such failures are not expected under

normal scenario and the only information
to go on will be in the message displayed
and the console logs during the problem.
This error mainly indicates some hardware
Copy the error message exactly as it
issue with cpk device. In these kind of
appears on the console or in the system
problems, the trigger for the problem
log. If you cannot determine the nature of should be identified. If the problem cannot
the error from the error message text, call be resolved based on the error message
your Cisco technical support representative Report this to Engineering. Use Topic to
and provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, and mail this message to your Cisco
technical support representative and
provide the representative with the
gathered information.

Such failures are not expected under

normal scenario and the only information
to go on will be in the message displayed
and the console logs during the problem. In
these kind of problems, the trigger for the
problem should be identified. If the
problem cannot be resolved based on the
error message Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

None

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the system message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the system message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

No action required if the message is

displayed just few times. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.
--

Use the 'show auto-ip-ring' or 'show run'

command on both devices to view the
configured Auto-IP address. If the two
devices show duplicate Auto-IP addresses,
then the configured Auto-IP address on any
of the peer devices needs to be changed or
deleted.
--

Use the 'show auto-ip-ring' or 'show run'

command on both devices to view the IP
address of the ring ports and the
advertised/received Auto-IP priorities. If the
Auto-IP priority is both 2 or both 0, then try
change the wire connection (that is, switch
the two ring ports on one ring device) if
necessary. If the Auto-IP priority is both 1,
then Auto-IP negotiation can be started by
configuring an IP address manually on any
of the peer devices.
--

Perform below steps and see if error goes

away: 1) SPA process restart by executing
CLI: 'process restart <spa_process_id>
location <> 2) Netio process restart by
executin CLI: 'process restart netion
location <>' 3) SPA reload by executing
CLI: 'hw-module subslot <> reload'

Please check if IM working properly or not

by executing CLI 'sh process ifmgr location
<>'. Also do 'sh netio chains ' to check
similar interface(s) to see if 'b_shim' caps
have been successfully added
before.Suggested steps would be to do
spa/netio process restart and spa reload.If
this doesn't help, collect below logs/traces:

Perform below steps and see if error goes

away: 1) SPA process restart by executing
CLI: 'process restart <spa_process_id>
location <> 2) Netio process restart by
executin CLI: 'process restart netion
location <>' 3) SPA reload by executing
CLI: 'hw-module subslot <> reload'

This error is specific to Multilink and MLPPP.

It will be thrown while updating shim data
in Netio. Suggested steps would be to do
spa/netio process restart and spa
reload.Also check if IM process is working
fine or not by executing CLI 'sh process
ifmgr location <>'

Perform below steps and see if error goes

away: 1) SPA process restart by executing
CLI: 'process restart <spa_process_id>
location <> 2) SPA reload by executing CLI:
'hw-module subslot <> reload'

This is a software error seen during SPA

and b-shim connection initialisation
failure.Check if SPA process restart or SPA
reload resolves the error.

Check if IM is working fine or not by

executing CLI 'sh process ifmgr location
<>'. Try performing IM process restart by
executing CLI 'process restart ifmgr
location <>'.

This is software error when binding to IM

gets fail. Please check if IM is working fine
or not.Try performing IM process restart.

Check if IM is working fine or not by

executing CLI 'sh process ifmgr location
<>'. Try performing IM process restart by
executing CLI 'process restart ifmgr
location <>'.

This is software error when binding to IM

gets fail. Please check if IM is working fine
or not.Try performing IM process restart.

Check if IM is working fine or not by

executing CLI 'sh process ifmgr location
<>'. Try performing IM process restart by
executing CLI 'process restart ifmgr
location <>'.

This is software error when binding to IM

gets fail. Please check if IM is working fine
or not.Try performing IM process restart.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software.
Event Management, SYSDB Management
If the message recurs, copy the error
are part of overall system. If there are
message exactly as it appears on the
failures here then other processes may also
console or in the system log, call your
exhibit similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software
If the message recurs, copy the error
or CPU controller interface. If there are
message exactly as it appears on the
failures here then other processes may also
console or in the system log, call your
exhibit similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software.
Event Management, Debug/Ltrace
Management and SYSDB Management are
If the message recurs, copy the error
part of overall system. If there are failures
message exactly as it appears on the
here then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs to isolate the failure.

Event Connection Manager failures are part
If the message recurs, copy the error
of the overall system. If there are failures
message exactly as it appears on the
here then other processes may also be
console or in the system log, call your
experiencing similar problems. Report this
Cisco technical support representative and to Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

Search the event logs to isolate the failure.

Event Connection Manager failures are part
If the message recurs, copy the error
of the overall system. If there are failures
message exactly as it appears on the
here then other processes may also be
console or in the system log, call your
experiencing similar problems. Report this
Cisco technical support representative and to Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

BFD Agent encountered an internal

software error. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software
If the message recurs, copy the error
and Kernel pthread API are part of overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software.
Event Management, Debug/Ltrace
Management and SYSDB Management are
If the message recurs, copy the error
part of overall system. If there are failures
message exactly as it appears on the
here then other processes may also exhibit
console or in the system log, call your
similar problems. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.
This indicates a low-memory condition.
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

BFD Agent uses SYSDB services for

verification and notification of various
events. This failure is indicative of
communication failure between BFD Agent
If the message recurs, copy the error
and SYSDB. Search the event logs for
message exactly as it appears on the
events/errors related to the failure reason.
console or in the system log, call your
SYSDB Management is part of overall
Cisco technical support representative and system. If there are failures here then other
provide the representative with the
processes may also exhibit similar
gathered information.
problems.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software.
If the message recurs, copy the error
SYSDB Management is part of overall
message exactly as it appears on the
system. If there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.

Search the event logs for events/errors

related to the failure reason. This could be
due to a problem in infrastructure software.
Event Management and SYSDB
If the message recurs, copy the error
Management are part of overall system. If
message exactly as it appears on the
there are failures here then other
console or in the system log, call your
processes may also exhibit similar
Cisco technical support representative and problems. Report this to Engineering. Use
provide the representative with the
Topic to search for a similar DDTS. If you
gathered information.
find none, write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Search the event logs for events/errors

related to the failure reason. SYSDB is part
of overall system. If there are failures here
then other processes may also exhibit
similar problems. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Recreate the BFD session and reconfigure

echo source address for it.

If issue persists, collect following

information. - 'show tech-support routing
bfd'. - 'show tech-support'

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Collect the following information, - 'show

tech-support routing bfd'. - 'show techsupport cef'. - 'show tech-support' Analyze
or pass the obtained information to IOS-XR
BU for analysis.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

If PROT_SERVER_INIT_SUCCESS message
has been logged and
PROT_BFD_SESSION_DOWN_LOST message
has not been logged, then there is no
issue. If PROT_SERVER_INIT_SUCCESS
message has not been logged, then BFD is
still not able to complete protect server
initialization. Follow further steps described
in 'tac_details' section for this message. If
PROT_BFD_SESSION_DOWN_LOST message
has been logged, then also follow the steps
described in 'tac_details' of
PROT_BFD_SESSION_DOWN_MESSAGE_LOS
T message. Obtain 'show tech-support
routing bfd'. Obtain 'show tech-support pfi'.
Obtain 'show tech-support gsp'. Analyze or
pass the obtained information to IOS-XR BU
for analysis.

Recreate the BFD session and reconfigure

echo source address for it.

If issue persists, collect following

information. - 'show tech-support routing
bfd'. - 'show tech-support'

No action is required.

--

No action is required.

--

Limit the number of new BFD sessions for

the linecard.

--

No action is required.

--

Either configure new BFD multipath

linecards or limit the number of new BFD
sessions for the multipath-configured
linecards.

--

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

If issue persists, collect following

information. - 'show tech-support routing
bfd'. - 'show tech-support' - 'show dll' for
the BFD process on the node which
displayed this message.

Determine if the forwarding path to the

neighbor has gone down.

If issue persists, collect following

information. - 'show tech-support routing
bfd'. - 'show tech-support'

Determine if the forwarding path to the

neighbor is UP.

--

No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

Remove other BFD sessions to free

resources for this session

--

No action is required.

--

If this behavior is not desired, it should be

disabled by the following BFD
configuration. (config)#no bfd dampening
bundle-member l3-only-mode

--

No action is required.

--

No action is required.

--

- For multipath sessions verify if mulipath

configured on one of the LCs. - Verify PPS
availablity on the LCs Copy the error
message exactly as it appears on the
console or in the system log. Issue the
<CmdBold>show bfd
summary<noCmdBold> command 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
<CmdBold>show bfd
summary<noCmdBold> output, call your
Cisco technical support representative and
provide the representative with the
gathered information.

If issue persists, collect following

information on both the peers. - 'show
tech-support routing bfd'. - 'show techsupport' If the session is bundle session
then collect the following on both peers, 'show tech bundle'

No action is required.

--

Check the applications peering status.

Check the 'show bfd client history' and

verify if the application has removed the
session, then contact the application
owners, otherwise collect the following
information on both the peers. - 'show
tech-support routing bfd'. - 'show techsupport' If the session is bundle session
then collect the following on both peers, 'show tech bundle'

Determine if the forwarding path to the

neighbor has gone down.
No action is required.

If issue persists, collect following

information on both the peers. - 'show
tech-support routing bfd'. - 'show techsupport' If the session is bundle session
then collect the following on both peers, 'show tech bundle'
--

No action is required.

--

'The trouble shooting TWIKI link for BGP-AD

is following. '
'http://twiki.cisco.com:82/Teams/IOS_XR/Tro
'Please remove l2vpn config and wait for 30 ubleshootingBGPADVPLS '
minutes until the zombie ' 'pool is cleared 'http://twiki.cisco.com:82/Teams/IOS_XR/Tro
and put back the config. '
ubleshootingBGPADVPWS '

This failure is not critical and the code will

If the message recurs, copy the error
continue if the error happens. But it does
message exactly as it appears on the
suggest a problem with the cerrno
console or in the system log, call your
infrastructure Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem..

This failure is not critical and the code will

If the message recurs, copy the error
continue if the error happens. But it does
message exactly as it appears on the
suggest a problem with the cerrno
console or in the system log, call your
infrastructure Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem..

This failure is not critical and the code will

If the message recurs, copy the error
continue if the error happens. But it does
message exactly as it appears on the
suggest a problem with the cerrno
console or in the system log, call your
infrastructure Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem..

This failure is not critical and the code will

If the message recurs, copy the error
continue if the error happens. But it does
message exactly as it appears on the
suggest a problem with the cerrno
console or in the system log, call your
infrastructure Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem..

This failure is not critical and the code will

continue if the error happens. But there
can be issues in the calling client because
If the message recurs, copy the error
the DLL is not registered correctly. It does
message exactly as it appears on the
suggest a problem with the cerrno
console or in the system log, call your
infrastructure Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem..

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Such failures are not expected during the

DLL Init and may impact the normal
process functionality. A manual restart of
the process may be triggered as a
workaround and if the issue recurs Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem. The problem
can occur due to one the 2 following
If the message recurs, copy the error
reasons 1. Adjacency process in not
message exactly as it appears on the
working as expected 2. registration with
console or in the system log, call your
debugger has failed 3. registration with
Cisco technical support representative and event manager has failed Please collect
provide the representative with the
following information show process location
gathered information.
show memory location

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

This failure is not expected and the only

information to go on will be in the message
displayed. It is likely that there is a low
memory condition, check for high memory
If the message recurs, copy the error
(particularly shared memory) consumption.
message exactly as it appears on the
If the problem cannot be resolved based on
console or in the system log, call your
the error message or by reducing memory
Cisco technical support representative and usage Report this to Engineering. Use Topic
provide the representative with the
to search for a similar DDTS. If you find
gathered information.
none, write a DDTS for this problem..

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This failure is not critical and the

functionality will not be impacted.But this
error will impact the debuggability and
manual restart of the process may be
triggered as a workaround and if the issue
recurs Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

This failure is not expected and the only

information to go on will be in the message
displayed. It is likely that there is a low
memory condition, check for high memory
If the message recurs, copy the error
(particularly shared memory) consumption.
message exactly as it appears on the
If the problem cannot be resolved based on
console or in the system log, call your
the error message or by reducing memory
Cisco technical support representative and usage Report this to Engineering. Use Topic
provide the representative with the
to search for a similar DDTS. If you find
gathered information.
none, write a DDTS for this problem..

This failure is not expected and the only

information to go on will be in the message
displayed. It is likely that there is a low
memory condition, check for high memory
If the message recurs, copy the error
(particularly shared memory) consumption.
message exactly as it appears on the
If the problem cannot be resolved based on
console or in the system log, call your
the error message or by reducing memory
Cisco technical support representative and usage Report this to Engineering. Use Topic
provide the representative with the
to search for a similar DDTS. If you find
gathered information.
none, write a DDTS for this problem..

This failure is not expected and the only

information to go on will be in the message
displayed. It is likely that there is a low
memory condition, check for high memory
If the message recurs, copy the error
(particularly shared memory) consumption.
message exactly as it appears on the
If the problem cannot be resolved based on
console or in the system log, call your
the error message or by reducing memory
Cisco technical support representative and usage Report this to Engineering. Use Topic
provide the representative with the
to search for a similar DDTS. If you find
gathered information.
none, write a DDTS for this problem..

This failure is not expected and the only

information to go on will be in the message
displayed. It is likely that there is a low
memory condition, check for high memory
If the message recurs, copy the error
(particularly shared memory) consumption.
message exactly as it appears on the
If the problem cannot be resolved based on
console or in the system log, call your
the error message or by reducing memory
Cisco technical support representative and usage Report this to Engineering. Use Topic
provide the representative with the
to search for a similar DDTS. If you find
gathered information.
none, write a DDTS for this problem..

Check the VT topology definition file to

ensure a Host MAC Address is specified.
Check the LRd stub library and VT IO code
to see if there is a bug in accessing the
defined value.
None.

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
If the message recurs, copy the error
search for a similar DDTS. If you find none,
message exactly as it appears on the
write a DDTS for this problem. Please
console or in the system log, call your
collect following information show process
Cisco technical support representative and location show memory location show dll
provide the representative with the
show dll jobid location show dll jobid
gathered information.
location

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
If the message recurs, copy the error
search for a similar DDTS. If you find none,
message exactly as it appears on the
write a DDTS for this problem. Please
console or in the system log, call your
collect following information show process
Cisco technical support representative and location show memory location show dll
provide the representative with the
show dll jobid location show dll jobid
gathered information.
location

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

This error indicates that the Bundle

encounterd an platform infra error
condition from which it cannot directly
recover and need to either retry or exit.
If the message recurs, copy the error
Critical resource, data structures or internal
message exactly as it appears on the
ASIC configuration may not be available to
console or in the system log, call your
perform required operation Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

No action is required.

Informational message for Bundle Mgr.

The operation will be retried automatically

and thus no action should be required. If
the problem persists the
ERR_OP_RETRY_THRESHOLD message will
be seen within 30 minutes. If this occurs,
restarting the Bundle Manager Distrib
process on the dSDRSC (process restart
bundlemgr_distrib) may resolve the issue.
If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

A DDTS should be raised with all IM and

bundle tech support information as
specified above attached. The operation
will be retried automatically and thus no
action should be required. If the 'exceeded
maximum number of retries' message is
seen within 30 minutes, the problem
persists. In this case Restarting the Bundle
Manager Distrib process on the dSDRSC
(process restart bundlemgr_distrib) may
then resolve this issue.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Delete and recreate the bundles or subinterfaces. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

This error message may indicate a memory

corruption, or a bug in the IM or bundle
code. A DDTS should be raised with all IM
and bundle tech support information as
specified above attached. Deleting and
recreating the interfaces impacted should
resolve the issue.

Verify that bundle parameters and bundle

membership are as expected. Copy the
error message exactly as it appears on the
console or in the system log. Issue the
<CmdBold>show interface<noCmdBold>
command 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 <CmdBold>show
interface<noCmdBold> output, call your
Cisco technical support representative and
provide the representative with the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log. Issue the
<CmdBold>show bundle<noCmdBold>
command 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 <CmdBold>show
bundle<noCmdBold> output, call your
Cisco technical support representative and
provide the representative with the
gathered information. If the data is as
expected in the output of both commands
then no further action is required,
otherwise unconfigure and reconfigure any
missing parameters.

Some checkpoint data could not be

recovered. The configuration will still exist
in SysDB so the best course of action is to
remove any affected bundle-related
configuration and then re-add it.

Shut and no-shut the member interface

may clear the condition. If the error
persists, manually shutting the member
interface will prevent any QoS breaches.

This message indicates a problem with the

interface driver which maintains the
member interface. This error may result in
the brute-force switchover functionality not
working correctly for mLACP as the DHD
will not realise that the link is not suitable
for aggregation.

If the message recurs, copy the error

It is difficult to know what could cause this
message exactly as it appears on the
error, other than an OS problem. Possibly a
console or in the system log, call your
shortage of memory could result in this
Cisco technical support representative and failure. Ask the customer to check how
provide the representative with the
much memory is available at the location
gathered information.
where the error was reported.

Restart the Bundle Manager process that

reported the error. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Once the underlying error condition has

cleared the system will recover, but once in
slow retry mode this will take up to half an
hour. Restarting the Bundle Manager
process that reported the error would bring
the link bundling infrastructure processes
back in step earlier if required.

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show gsp
groups<noCmdBold> command 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
<CmdBold>show gsp
groups<noCmdBold> output, call your
Cisco technical support representative and The problem is most likely with the GSP
provide the representative with the
infrastructure. Restarting the local GSP
gathered information.
process may help.

The failure to report the error back to IIR

suggests a problem in the connection to
IIR. This may have been a transient
problem, but restarting ifmgr and/or the
bundlemgr_ea process on the location of
the error might be necessary. The error that
should have been reported also needs to
be dealt with. This error may have come
from some lower layer platform
A member add or remove operation failed
component, possibly a resource allocation in the EA, most likely in one of the platform
error. If the error code provides some
drivers the EA calls. The EA was unable to
information as to the failure then take
report the error back to the MA via IIR, so
action appropriate to the error. If the error the event may have gone through. The
code is not specific then take action
recommended actions are intended to try
according to whether the event was a link to get the MA and EA back in step. The
activation or a link deactivation/deletion.
output of the 'show bundle' and 'show iir
For activation problems unconfigure and
interfaces' commands will show what state
reconfigure the member link - if this fails
IIR and bundlemgr think the bundle
try restarting the bundlemgr_ea process
membership is in, so will give some idea of
after unconfiguring the member link. For
whether the failure was actually reported
deactivation/deletion failures try restarting back up to the bundlemgr MA. 'show
the improxy process to trigger a complete bundle ea members' will show the state
resync by the bundlemgr EA.
that the EA holds.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

This process believes that there are no

aggregatable links, but this link is marked
as attached. This will cause problems with
bandwidth calculations. This can happen if
an error occurs during attaching/detaching
of members via Interface Manager. When
If the message recurs, copy the error
the Selection Logic runs again, if the
message exactly as it appears on the
Interface Manager problem clears up then
console or in the system log, call your
this problem should disappear. The
Cisco technical support representative and Selection Logic can be made to run again
provide the representative with the
by configuring a small change (eg. change
gathered information.
a link's priority).
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. None.

Restart the snmp process reporting the

error. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

If errors occur when re-initialising the

dot3ad MIB DLL, restarting the SNMP agent
process should resolve this problem.
Otherwise there is no need to take further
action. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Restart the snmp process reporting the

error. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Restarting the SNMP agent process should

resolve this problem. If not, there could be
a SysDB or Interface Manager connectivity
problem. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

If the error message indicates the failure is This failure is not expected. If the problem
low memory condition, reduce other
cannot be resolved based on the error
system activity to ease memory demands. message Report this to Engineering. Use
If conditions warrant, upgrade to a larger
Topic to search for a similar DDTS. If you
memory configuration. Otherwise, Copy the find none, write a DDTS for this problem..
error message exactly as it appears on the Check on the status of the SysDB process
console or in the system log, call your
and check for low memory condition. If the
Cisco technical support representative and cause of the underlying problem can be
provide the representative with the
fixed then removing and readding the
gathered information.
bundle configuration may fix this problem.

Check that the item(s) still exist. Make a

minor change to the settings of the object
experiencing the problem. This will trigger
another attempt to send an update. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Once the underlying error condition has

cleared the system will recover, but once in
slow retry mode this will take up to half an
hour. Restarting the Bundle Manager
process that reported the error would bring
the link bundling infrastructure processes
back in step earlier if required.

It is expected that restarting the process

will fix this problem. This is done
automatically so no action should be
required. If the problem recurs, then there
is a problem in packet manager. A drastic
solution would be to reload the linecard.

It is likely that this is a general problem

and the cause of the problem is unrelated
to Bundle Manager. The Bundle Manager
process will have restarted and so will try
to reconnect to Pakman. This should be
sufficient to fix the problem. If not, there is
little else that can be done by Bundle
Manager.

message exactly as it appears on the

console or in the system log. Issue the
<CmdBold>show bundle <bundle
name><noCmdBold> command 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
<CmdBold>show bundle <bundle
name><noCmdBold> output, call your
Cisco technical support representative and
provide the representative with the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log. Issue the
<CmdBold>show adjacency <bundle
name> detail hardware location <loc of
error><noCmdBold> command 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
<CmdBold>show adjacency <bundle
The checkpoint data for a bundle could not
name> detail hardware location <loc of
be recovered. The configuration will still
error><noCmdBold> output, call your
exist in SysDB and the interface itself may
Cisco technical support representative and still exist in Interface Manager and NetIO,
provide the representative with the
so the effect could be little more than a few
gathered information. If the bundle appears route flaps. On the other hand the interface
correctly in the output of all three
could be permanently lost, in which case
commands then no further action is
the best course of action is to remove the
required, otherwise unconfigure and
configuration for the interface and then rereconfigure the bundle.
add it.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

In all probability the checkpoint tables for

the process are badly corrupted in some
way that could not be remedied by
destroying and recreating them. It would
be worth asking the customer to attempt
some small change to their configuration,
such as creating a new bundle, in order to
see how bad the problem is. If the same
error message appears when doing the
test, the best remedy would be to delete
the checkpoint data and restart the process
that reported the error. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem. Depending on the
process the checkpoint data can be deleted
with one of the following commands: run
rm /tmp/chkpt_bundlemgr_distrib* run rm
/tmp/chkpt_bundlemgr_local* run rm
/tmp/chkpt_bundlemgr_adj*

It is most likely that restarting the process

will resolve this problem. If this problem
recurs and the customer contacts the TAC
then the first suggestion would be to delete
the checkpoint data and restart the process
that reported the error. If this fails a more
drastic solution would be to reboot the
node. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.
If the message recurs, copy the error
Depending on the process the checkpoint
message exactly as it appears on the
data can be deleted with one of the
console or in the system log, call your
following commands: run rm
Cisco technical support representative and /tmp/chkpt_bundlemgr_distrib* run rm
provide the representative with the
/tmp/chkpt_bundlemgr_local* run rm
gathered information.
/tmp/chkpt_bundlemgr_adj*

As described above, bundlemgr failed to

replicate the bundle to the specified
interface location(s). This is likely to be the
result of hardware resource exhaustion,
although software error cannot be ruled
out. Check how many physical interfaces
and VLANs are present on the LC(s), and
check how many VLANs are configured on
the bundle. If the two combined exceed the
capacity of the LC then this is the problem
and the number of VLANs must be reduced.
Determine whether the hardware resources Otherwise the error should be investigated
for the LC(s) have been oversubscribed,
by seeing which EA failed the download e.g. more VLANs on the LC(s) and on the
IMP traces should have this information.
bundle that the LC(s) can support. If this is NB: the full list of nodes to which
the case, reduce the number of allocated
replication failed will be present in the
VLANs. Then remove the member
bundlemgr_distrib trace (part of show techconfiguration and reapply.
support bundles).

The EA has tried a number of times to

resynchronise with the IIR component
(which gives details of bundle members)
but has failed. This probably indicates an
If the message recurs, copy the error
inconsistency with one of the downstream
message exactly as it appears on the
component (Platform Manager, uIDB
console or in the system log, call your
Manager, the Sponge or Sprayer drivers or
Cisco technical support representative and the PLA driver). Restarting these processes
provide the representative with the
may help if these problems persist after
gathered information.
the restart of the EA.

The EA was trying to resynchronise with

the IIR component (which gives details of
bundle members) but was unable to set up
the necessary timers or a similar problem.
Restarting the EA should help, but if there
is an inconsistency with one of the
downstream components (Platform
If the message recurs, copy the error
Manager, uIDB Manager, the Sponge or
message exactly as it appears on the
Sprayer drivers or the PLA driver) then
console or in the system log, call your
further retries may be necessary.
Cisco technical support representative and Restarting these processes may help if
provide the representative with the
these problems persist after the restart of
gathered information.
the EA.

If the message referred to a global error

then check that the process has restarted
successfully. If the message referred to a
bundle or bundle member then check that
the object is still configured and still exists.
Make a minor change to the settings of the
object experiencing the problem. This will
trigger another attempt to send an update.
If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

Restarting the Bundle Manager process

that reported the error will bring the two
processes back in step and should resolve
the problem.

Check that other processes are not

It is likely that that cause of the problem is
reporting similar communication errors, as unrelated to Bundle Manager, but a general
this is likely to be a general communication communication problem. The Bundle
problem. The Bundle Manager process has Manager process will have restarted and so
exited and will be restarted, so no action is will try to create the GSP group again, so if
needed, though unless the communication the communication problems can be found
problem is resolved the process will still not and resolved then Bundle Manager should
be able to startup.
recover.

These retries are required on delete

operations, but not on creates, so the
effect will be left over data of some sort in
one or more of the downstream
components (Platform Manager, uIDB
Manager, the Sponge or Sprayer drivers or
If the message recurs, copy the error
the PLA driver). This may be harmless, but
message exactly as it appears on the
if further problems are observed,
console or in the system log, call your
particularly with creating new bundles,
Cisco technical support representative and then restarting the downstream processes
provide the representative with the
may be necessary. As a last resort, reload
gathered information.
the linecard to reset the hardware.

Check that other processes are not

reporting communication errors, as this is
likely to be a general communication
problem. The Bundle Manager process has
exited and will be restarted, so no action is
needed, though unless the root problem is
resolved the process will still not be able to
startup.

It is likely that that cause of the problem is

unrelated to Bundle Manager, but a general
communication problem. The Bundle
Manager process will have restarted and so
will try to initialize the Protect module
again, so if the source of the problem can
be found and resolved then Bundle
Manager should recover.

The Bundle Manager process has exited

and will be restarted, so no action is
needed. Check that the board (EEPROM
etc.) is correctly programmed since this is
the source of the MAC address information
and therefore one possible cause of the
problem.

It is likely that that cause of the problem is

unrelated to Bundle Manager, but a general
MAC address generation problem. The
Bundle Manager process will have restarted
and so will try to query the MAC address
again, so if the problems can be found and
resolved then Bundle Manager should
recover.

This error message may indicate a bug in

the IM or bundle code. A DDTS should be
raised with all IM and bundle tech support
information as specified above attached.
Deleting and recreating the interfaces
Delete and recreate the subinterface. If the impacted should resolve any ongoing issue.
message recurs, copy the error message
Note that due to rate-limiting of messages,
exactly as it appears on the console or in
some subinterfaces may be affected
the system log, call your Cisco technical
without an associated error message, so it
support representative and provide the
is recommended to delete and recreate all
representative with the gathered
subinterfaces on the affected bundle(s) to
information.
avoid any possible problems.

One possible cause of this problem is the

termination of the System Manager process
Check on the status of the sysmgr process during this process' initialisation. Use 'show
on the node from which the error was
process sysmgr', specifying the appropriate
reported. If the message recurs, copy the location, to determine whether this is the
error message exactly as it appears on the case. If System Manager has not restarted,
console or in the system log, call your
and the problem persists, Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

The Bundle Manager process will select a

new address automatically, so no further
action is needed to resolve this error.

Such an error indicates either a logic error

in the bundle manager code, or a general
MAC address generation problem.

The database entry is required for setting

up both periodic and rate-limiting timers. If
Reduce other system activity to ease
the entry cannot be created, the member
memory demands. If conditions warrant,
will be unable to transmit regular LACPDUs
upgrade to a larger memory configuration. and rate-limiting will not function correctly.

Timer creation failures can lead to bundle

Reduce other system activity to ease
member link flaps, and potentially to
memory demands. If conditions warrant,
bundle flaps, as periodic LACP updates will
upgrade to a larger memory configuration. not be sent out for the given interface.

As described above, bundlemgr failed to

unreplicate the bundle from the specified
location(s). This may be because the IM
server is unavailable, or the linecard has
been OIRed at the specified location(s).
If the message recurs, copy the error
Restarting the interface manager (ifmgr)
message exactly as it appears on the
process on the RP should get the system
console or in the system log, call your
back into the correct state. NB: the full list
Cisco technical support representative and of nodes to which replication failed will be
provide the representative with the
present in the bundlemgr_distrib trace
gathered information.
(part of show tech-support bundles).

Ensure the encapsulation on the interface

does not use any of the 'complex' matching This error indicates a possible
criteria.
misconfiguration.
This is most likely a misconfiguration; if the
same max-active links value is in use on
Check the maximum active links settings
both ends of the bundle, then this indicates
on both ends of the bundle and ensure that a problem in the handling of the link order
the same value is in use.
signaling feature.

Shut and no-shut the bundle interface may

clear the condition. If the error persists,
shutting down all member interfaces and
This message most likely indicates a
the bringing them up individually may clear problem with the partner system's
the condition.
allocation of Link Ordering Numbers.

This error probably indicates that LRd has

failed to send a notification for the
indicated node when it was OIR'd, or that
this error message was not received by
bundlemgr. Any issues arising from this will
If the message recurs, copy the error
have been cleared by the time this error
message exactly as it appears on the
message is seen, though they may have
console or in the system log, call your
been causing problem (such as packet loss,
Cisco technical support representative and or link attachment errors) before this point.
provide the representative with the
The logs indicated above should help to
gathered information.
pinpoint the cause of the failure.

Correct the misconfiguration.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This failure is not expected and the only

information to go on will be in the message
displayed. A failure to change thread
priority typically represents an underlying
OS issue. If the problem cannot be resolved
based on the error message Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If actor churn has been declared and the

link is not marked as Standby, check that
the configuration for the link allows it to
aggregate, and fix as appropriate. Check
for misconfigurations between the two
ends of the link which is reporting churn.
The output of the <CmdBold>show
bundle<noCmdBold> command may help
identify the problem.

If the member is not in Standby state, then

a declaration of actor churn is likely to be
due to a configuration error. The output of
show bundle for the bundle the link is a
member of on either the local end or the
peer should explain the reason for the link
being in actor churn state.

No action is required; however, the bundle This message is just an indication of a

will remain inoperative until the
misconfiguration, there is no issue with the
configuration incompatibility is cleared.
code.

If adding and removing the bundle as

described above was not successful, try
If there is no other feature that is short of restarting the Bundle Manager process on
MAC addresses, no action is required.
the dSDRSC (process restart
Otherwise, try adding and deleting an
bundlemgr_distrib), followed by the MAC
additional Bundle-Ether interface (with no Allocation Server process on the dSC
members). Copy the error message exactly (process restart ema_server) at least a few
as it appears on the console or in the
seconds later. Either of these steps may
system log, call your Cisco technical
help resolve the problem. Report this to
support representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

The bundlemgr_local process is not picking

up packets queued for processing. This is
most likely caused by the main thread of
the bundlemgr_local process becoming
If this message appears more than once,
blocked on external infrastructure. If the
the bundlemgr_local process should be
main thread is not blocked, this suggests a
restarted to try to recover the situation. An bug in the queue processing code, either in
occasional message of this type will be
bundlemgr_local or in the queue
harmless.
infrastructure.

This message indicates one of two

possibilities. Either LACPDUs sent by this
device have been dropped before delivery
on the partner, or the partner device is
unable to process incoming LACPDUs in a
timely fashion. Check packet counters on
both devices for drops, and for rate limited
LACPDUs on the partner device (using
<CmdBold>show lacp
counters<noCmdBold> if it is an XR
device). Check also for high CPU load on
the partner device.

The warning suggests that one or more

outgoing LACPDUs have been dropped, and
drops may be continuing. The packet loss
could be specific to LACPDUs or applicable
to all traffic on the link. Alternatively CPU
load on the partner device could be high
causing excessive latency in processing
incoming packets on that device. Standard
techniques for investigating packet loss
and CPU load should be employed.

The warning suggests that one or more

incoming LACPDUs have been dropped, but
as it is generated when a LACPDU is
This message indicates that a gap in
actually received, this indicates either
incoming LACPDUs has been detected,
partial packet loss (which may be ongoing)
possibly as the result of packet loss or rate or total connectivity loss that has now been
limiting of incoming LACPDUs. Check
recovered. The packet loss could be
packet counters on both devices for drops, specific to LACPDUs or applicable to all
and for locally rate limited LACPDUs using traffic on the link. Standard techniques for
<CmdBold>show lacp
investigating packet loss should be
counters<noCmdBold>.
employed.

The warning suggests that one or more

outgoing LACPDUs have been dropped, but
This message indicates that a gap in
as it is generated when a LACPDU is
incoming LACPDUs has been detected by
actually received, this indicates either
the partner device, possibly as the result of partial packet loss (which may be ongoing)
packet loss or rate limiting of incoming
or total connectivity loss that has now been
LACPDUs. Check packet counters on both recovered. The packet loss could be
devices for drops, and for rate limited
specific to LACPDUs or applicable to all
incoming LACPDUs on the partner device
traffic on the link. Standard techniques for
using <CmdBold>show lacp
investigating packet loss should be
counters<noCmdBold>.
employed.

To stop the member from being brought

down, rectify the inconsistency between
the BFD sessions of the two neighboring
routers within the specified time. EITHER,
configure BFD sessions per-member on
both routers OR remove the configuration
from both routers.

This message indicates an inconsistency in

the BFD session configuration on
neighboring routers.

Ensure that the bundle and its members

are configured correctly on the neighboring
router, and that all the interfaces are up.
Ensure that BFD is running on the member This message indicates that the BFD
interfaces on the neighboring router.
session has transitioned to DOWN state.

If this situation is not intended then either

reduce the minimum active link threshold This message is just an indication of a
or increase the maximum links permitted in misconfiguration, there is no issue with the
the bundle.
code.

Ensure that the ICCP Group is running as

expected.

This message indicates that an mLACP TLV

could not be read from the ICCP buffer. It
may be that the mLACP systems will
continue without any issue, but the sanity
of the systems should be confirmed, and
the error triaged by the ICCP team.

If the message indicates that the switch

could not be performed because the router
being switched to is already active, no
action is required - the command is
extraneous. If it indicates that the router
being switched to is currently down, action
must be taken to recover the bundle on
that router before retrying the command.
Otherwise, the message indicates a
configuration-based issue. Correct the
configuration before retrying the
command.

This message indicates that a CLI

command was issued when it was not
required or with configuration on the
bundle with which the CLI command is not
supported.

If the reason message indicates that the

failure is because the application is not in
the ICCP Group, ensure that mLACP is
configured for the ICCP Group on a peer
router. Otherwise, Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

If the application is not known in the ICCP

Group, then the failure is a
misconfiguration and is solved by
configuring mLACP for the ICCP Group on a
peer. Otherwise, the failure is due to too
many general ICCP connections and the
configuration should be checked to cut
down on the number of ICCP connections.

There is an issue with connection to the

core. This may be due to a
Ensure that the backbone interface is able misconfiguration of the backbone interface,
to carry traffic to the core.
or it may be a connection issue.
Ensure that the configuration (on both local This is a configuration error. The customer
and peer device) is as expected. The
needs to ensure that the configuration is
message indicates the initial area to check. fixed on either the local or the peer device.

If the alarm does not clear, ensure that the This is a configuration error. The customer
configuration (on both local and peer
needs to ensure that the configuration is
device) is as expected.
fixed on either the local or the peer device.

Check <CmdBold>show
mlacp<noCmdBold> after a short while to
see if the problem has cleared and all
expected items are present. If the problem
does not clear, ensure that the
This is a configuration error. The customer
configuration (on both local and peer
needs to ensure that the configuration is
device) is as expected.
fixed on either the local or the peer device.

There was an inconsistency in the mLACP

data that could not be resolved by a
resync. The only solution was to disconnect
the system. To re-establish the mLACP
Disable and re-enable mLACP on either the connection, the user must disable and relocal or the peer device.
enable mLACP for the given ICCP Group.

This is a configuration error. The customer

Ensure that the ROID of the bundle (on
needs to ensure that the ROID is the same
both local and peer device) is as expected. on both devices.

Remove the mLACP ICCP Group

configuration from both routers and apply
the correct configuration.

This is a configuration error. The customer

needs to ensure that the configuration is
fixed on either the local or the peer device.

If partner churn has been declared and the

link is not marked as Standby on the peer
router, check that the configuration for the
link allows it to aggregate, and fix as
appropriate. Check for misconfigurations
between the two ends of the link which is
reporting churn. The output of the
<CmdBold>show bundle<noCmdBold>
command may help identify the problem.

If the member is not in Standby state on

the peer, then a declaration of partner
churn is likely to be due to a configuration
error. The output of show bundle for the
bundle the link is a member of on either
the local end or the peer should explain the
reason for the link being in actor churn
state.

Correct the misconfiguration.

--

Nothing, this is not an error.

This message is entirely normal during link

state change events.

No action is required.

This message indicates that the BFD

session has transitioned to UP state.

Ensure that the bundle and its members

are configured correctly on the neighboring
router, and that all the interfaces are up.
Ensure that BFD is configured on the
This message indicates that the BFD
member interfaces on the neighboring
session has been configured on a perrouter.
member basis over a bundle.

No action is required; however, any link

that is incompatible will not be used in the
bundle. In order to make the link
compatible, refer to the reason given in the
message. Check the configured mode of
operation (LACP active/passive or disabled,
i.e. mode 'on') and bandwidth of all the
This message is just an indication of a
links within the bundle or the bundle
misconfiguration, there is no issue with the
configuration to resolve the incompatibility. code.

Remove the system id configuration, as it

has no effect when running mLACP.

This message indicates that the system id

configured on the bundle has been ignored
as the bundle is running mLACP.

No action is required.

This message indicates that the device has

changed its role with respect to the mLACP
bundle. This can be because of a local
change of state, or because the peer
device has changed state.

If the alarm is set, the user should ensure

that all peers have the same MAC address
for the bundle.

This is a configuration error. The customer

needs to ensure that all devices have the
same MAC address configured for the
specified bundle.

No action is required.

This message indicates that the bundle is

using a new device, or has stopped using
an old device, as an mLACP peer device.
This will be due to a change of state of the
original peer, or because the first peer has
become available. If a bundle moves from
one peer device to another, then two
messages will be output: the first indicating
that a device is no longer being used; the
second indicates the new device.

No action is required.

mLACP has successfully connected to a

foreign device.

No action is required.

mLACP has successfully disconnected from

a foreign device (or all devices).

Check that the configuration of all the

mLACP peer devices is consistent.

This message indicates that an mLACP

peer device is attempting to send port
priority requests when this device currently
does not handle local port priority changes
(the reason for this is specified in the
message). The most likely cause is due to
misconfiguration.

This message is a notification that there

may be a misconfiguration. The customer
If the alarm is set, the user should ensure needs to ensure that all devices have the
that all peers have the same system id for same system id configured for the specified
the ICCP Group.
ICCP Group.

Ensure no configuration is present on the

This message is just an indication of a
bundle that cannot be applied when acting misconfiguration, there is no issue with the
as a Satellite fabric uplink.
code.

No action is required.

This message indicates that there is no

more buffer space for storing capture
mLACP TLVs, so TLV capture has been
stopped.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

This failure is not expected and the only

information to go on will be in the message
displayed. It is likely that there is a low
memory condition, check for high memory
If the message recurs, copy the error
(particularly shared memory) consumption.
message exactly as it appears on the
If the problem cannot be resolved based on
console or in the system log, call your
the error message or by reducing memory
Cisco technical support representative and usage Report this to Engineering. Use Topic
provide the representative with the
to search for a similar DDTS. If you find
gathered information.
none, write a DDTS for this problem..
Check the VT topology definition file to
ensure a Host MAC Address is specified.
Check the LRd stub library and VT IO code
to see if there is a bug in accessing the
defined value.
None.
If any problems are seen, they may be
rectified by restarting the process using the A call to pird_db_attach_ecm() failed - this
'process restart' command.
is likely to indicate a system problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

The process should recover automatically.

It is suggested to collect 'show techsupport l2vpn' and to call Cisco TAC.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Please try to reload that particular SPA or

restart the SPA process associated with
that SPA. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Please check if IM working properly or not.

Also do 'sh netio chains ' to check similar
interface(s) to see if 'c_shim' caps have
been successfully added before. Report this
to Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Please try to reload that particular SPA or

restart the SPA process associated with
that SPA. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Please check if IM working properly or not.

Also do 'sh netio chains ' to check similar
interface(s) to see if 'c_shim' caps have
been successfully added before. Report this
to Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Please check '/pkg/rules/' on the Jacket

Please reload the corresponding Jacket
Card to see if 'c_shim.caps' is presented or
Card. Copy the error message exactly as it not. If the file is not presented, something
appears on the console or in the system
went wrong when packaging the software
log, call your Cisco technical support
or someone accidently removed the file. In
representative and provide the
this case, please reload the Jacket Card.
representative with the gathered
Otherwise, please collect error messages in
information.
the system log and file a bug.

Please check '/pkg/rules/' on the Jacket

Please reload the corresponding Jacket
Card to see if 'c_shim.caps' is presented or
Card. Copy the error message exactly as it not. If the file is not presented, something
appears on the console or in the system
went wrong when packaging the software
log, call your Cisco technical support
or someone accidently removed the file. In
representative and provide the
this case, please reload the Jacket Card.
representative with the gathered
Otherwise, please collect error messages in
information.
the system log and file a bug.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Ignore

None

Ignore

None

Ignore

--

Ignore

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The configuration is trying to create a FR

subinterface but the subinterface counter
has not been initialised. So there is no way
whether the subinterface limit has been
reached on the linecard or not.

Search the event logs for events/errors

related to the failure reason. Initialization
failures are part of the overall system. If
The failure should be handled by the
there are failures here then other
process that is loading the DLL. The calling processes maybe complaining as well. If
process should retry the initialization.
the DLL continually fails to load, try
Collect all debug information if the DLL is restarting the process that is loading the
continually failing: 'debug ccl ace error
ccl DLL. Report this to Engineering. Use
location 0/x/cpu0' 'debug ccl api detail
Topic to search for a similar DDTS. If you
location 0/x/cpu0'
find none, write a DDTS for this problem.

Try restarting CDP. If the message recurs,

copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

The message is the only thing to go on

here. It should indicate which connection
has failed. If this is not enough to recover
the situation, Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Try restarting CDP ('proc restart cdp

location <location>'). If the message
If this is seen persistently when CDP is
recurs, copy the error message exactly as it restarted, there is likely to be a problem
appears on the console or in the system
with the IM attributes library. Investigate
log, call your Cisco technical support
whether it has reported any errors. Report
representative and provide the
this to Engineering. Use Topic to search for
representative with the gathered
a similar DDTS. If you find none, write a
information.
DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

CDP has failed to add the CDP caps to the

interface. The message should give more
indication of what the error from ifmgr is.
Restarting ifmgr may help to recover the
situation. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

CDP has failed to remove the CDP caps to

the interface. The message should give
more indication of what the error from
ifmgr is. Restarting ifmgr may help to
recover the situation. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

CDP has failed to register with ifmgr for

interface MTU updates. The message
Perform 'cdp disable', 'cdp enable' on the should give more indication of what the
interface to try to recover. If the message error is. If the error is seen persistently
recurs, copy the error message exactly as it when CDP is disabled and then re-enabled
appears on the console or in the system
on the interface, then restarting CDP and
log, call your Cisco technical support
ifmgr may help to recover the situation.
representative and provide the
Otherwise Report this to Engineering. Use
representative with the gathered
Topic to search for a similar DDTS. If you
information.
find none, write a DDTS for this problem.

CDP has failed to register with ifmgr for

interface state updates. The message
Perform 'cdp disable', 'cdp enable' on the should give more indication of what the
interface to try to recover. If the message error is. If the error is seen persistently
recurs, copy the error message exactly as it when CDP is disabled and then re-enabled
appears on the console or in the system
on the interface, then restarting CDP and
log, call your Cisco technical support
ifmgr may help to recover the situation.
representative and provide the
Otherwise Report this to Engineering. Use
representative with the gathered
Topic to search for a similar DDTS. If you
information.
find none, write a DDTS for this problem.

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration.
Configuring 'cdp disable', 'cdp enable' on
the interface, or restarting CDP on the
affected node may recover the situation.

If the issue persists, collect the following

infomation, - Enable 'Debug cdp events'
and try to configure CDP again on the
interface and collect the CDP 'show
logging' information. - 'show cdp trace'

Try restarting CDP and the Statistics server

process on this node. proc restart cdp
location <node> proc restart statsd_server
location <node> If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

It is difficult to know what is likely to cause

this. Check that there is sufficient memory
available on this node. The output of the
message may help pinpoint where the
problem lies. If restarting the relevant
processes doesn't help and the message
doesn't point to another solution then
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Restarting CDP as the address consumer,

or the ipv4_ma as the address provider on
this node may rectify the problem. proc
restart cdp location <location of failure> or
proc restart ipv4_ma location <location of If the issue persists, collect the following
failure>
infomation, - 'show cdp trace'

Restarting CDP as the address consumer,

or the ipv4_ma as the address provider on
this node may rectify the problem. proc
restart cdp location <location of failure> or
proc restart ipv4_ma location <location of If the issue persists, collect the following
failure>
infomation, - 'show cdp trace'

Restarting CDP as the address consumer,

or the ipv6_ma as the address provider on
this node may rectify the problem. proc
restart cdp location <location of failure> or
proc restart ipv6_ma location <location of If the issue persists, collect the following
failure>
infomation, - 'show cdp trace'

Restarting CDP as the address consumer,

or the ipv6_ma as the address provider on
this node may rectify the problem. proc
restart cdp location <location of failure> or
proc restart ipv6_ma location <location of If the issue persists, collect the following
failure>
infomation, - 'show cdp trace'

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

Try restarting CDP and the Statistics server

process on this node. proc restart cdp
location <node> proc restart statsd_server
location <node> If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

It is difficult to know what is likely to cause

this. Check that there is sufficient memory
available on this node. The output of the
message may help pinpoint where the
problem lies. If restarting the relevant
processes doesn't help and the message
doesn't point to another solution then
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

This may indicate that resources on the

system are low. If not then the error
Perform 'cdp disable', 'cdp enable' on the message is the only thing to go on. If this
interface. If the message recurs, copy the isn't enough to resolve the situation then
error message exactly as it appears on the Report this to Engineering. Use Topic to
console or in the system log, call your
search for a similar DDTS. If you find none,
Cisco technical support representative and write a DDTS for this problem.. Also collect
provide the representative with the
the following information, - Enable 'debug
gathered information.
cdp packets' and collect the logs.
Configure the interfaces with the same
duplex (full or half).

--

It is difficult to see how this could ever

happen. The error message may give some
more clues as to what went wrong. It is
likely that CDP functionality will not
actually be affected, but this is hardware
dependent and not guaranteed. The first
thing to check is whether CDP packets are
being received by checking if any
neighbors are visible in 'show cdp
If CDP packet loss is seen then Copy the
neighbors location '. If they are then there
error message exactly as it appears on the is no need for further action. Otherwise try
console or in the system log, call your
'proc restart cdp location and Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.
CDP will try and continue to use the
previous CDP table.
--

Check the existing CDP neighbors for

bogus entries, CDP may be the victim of an
attempted DoS attack. The 'clear cdp table'
command can be used if CDP neighbor
entries need removing.
--

If there are no interfaces on this node with

a media type that CDP is expected to run
on then this could be a normal condition. If
it is expected that CDP should run on the
type of interfaces on this node then Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

There is no problem if CDP is not expected

to run on any of the interfaces on this
node. 'show platform' should help
determine what type of interface exists on
this node and whether it is supported by
CDP. If it is then it is likely that this is a bug
in the CDP code. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.. Also collect the
following information, - 'show cdp trace'

There is no problem if CDP is not expected

to run on any of the interfaces on this
node, though this is an unlikely situation as
the media module wouldn't be looking for
There are no media drivers for the
media drivers if it didn't recognise any
interfaces on this node. If CDP does not
media. 'show platform' should help
support the interface types on this node
determine what type of interface exists on
then this could be a normal situation
this node and whether it is supported by
Otherwise Copy the error message exactly CDP. If it is then it is likely that this is a bug
as it appears on the console or in the
in the CDP code. Report this to
system log, call your Cisco technical
Engineering. Use Topic to search for a
support representative and provide the
similar DDTS. If you find none, write a
representative with the gathered
DDTS for this problem.. Also collect the
information.
following information, - 'show cdp trace'

CDP will try to recover automatically. If the

message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

CDP should recover automatically. If the

message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Such failures are not expected and the only

information to go on will be in the message
displayed. It is possible that the problem
will not have any lasting consequences
since the CDP process is shutting down
anyway. If the problem is persistent, and
cannot be resolved based on the error
message Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

No action is required.

--

No action is required.

--

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. -Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. --

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information. - Restart the g_spa
process.

There could be an issue where we try to

delete the node of the AVL tree which is not
even existing. Restart g_spa to check if it
resolved the issue, else collect cem traces
given in required_info field.

If the message recurs, copy the error

message exactly as it appears on the
The message will show up as a result of
console or in the system log, call your
failure of one of the APIs belonging to
Cisco technical support representative and sysdb/evm or sysmgr. If the error persists
provide the representative with the
across various events of recreate, take the
gathered information.
required traces for CEM.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information. Collect the
If by some means, the component fails to
component logs, based on the message
initialize, please collect required info and
found.
contact DE.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information. - Restart the g_spa
A memory allocation failure case, the node
process. - Check for memory conditions in has detected low memory. Take corrective
the system.
action, restart g_spa process.

No Action required.

--

No Action required.

--

No Action required.

The info message shows that the

parameter(payload/dejitter) was not in
range.

No Action required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

An internal error was detected as a part of

CEMA component operation for one of the
SPA bays. This error will cause a process
restart. Possibly, there are insufficent
resources on the line card to allow for
proper operation of the SPA.

The mismatch can be service affecting in

certain cases. Please check if the entity
specified in the error log and all it's
children are functioning correctly. Contact
Cisco TAC for further assistance.

Since a configuration mismatch can be

service affecting, it is necessary to check
the entity specified in the error log and all
it's descendants for correct operation. For
instance, if this error was logged for a STS
path carrying DS1s, it is recommended to
check that STS path, DS1s, and every serial
interface configured on the DS1s, are
functioning correctly. Generally, any
problems detected as a part of these tests
can be corrected by manually reconfiguring
the affected entity. However, in a rare case,
it may be necessary to reload the SPA.

Check to see if the device on which the

feature has failed is performing correctly
for all necessary functionality.

Since a missing feature may indicate that a

necessary capability is not supported for
the device specified, it is necessary to
check to see if the device is working
properly per your requirements. If the
feature is necessary but unsupported
please upgrade to a device that supports
the feature or to a version of the current
device that provides the desired
functionality.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

An internal error was detected as a part of

CEMA component operation for one of the
SPA bays. This error may cause abnormal
operation for some of the SPA features.

If the error is the result of a configuration

change, remove and reapply the
configuration. If this does not work, or the
error was triggered by a change in the
network, the error may be cleared by
restarting the cfmd process on the node
where the error is occurring, or shutting
down and re-enabling any affected
interfaces.

This error is likely caused by a system

problem, such as running out of memory.

Unconfigure AIS generation on the service

or EFP, then reconfigure it. If the problem
persists, it may be possible to recover by
restarting the 'cfmd' process on the node
where the problem occurs.

This is caused by an error from the timer

wheel library. The library may also have
logged its own errors which give further
details.

Unconfigure CCM generation for this

service, commit the configuration, then
reconfigure it. If the problem persists, it
may be possible to recover by restarting
the 'cfmd' process on the node where the
problem occurs.

This is caused by an error from the timer

wheel library. The library may also have
logged its own errors which give further
details.

If the error is the result of a configuration

change, remove and reapply the
configuration. If this does not work, or the
error was the result of interface state
changes or an attempt to set/clear the RDI
bit, the error may be cleared by restarting
the cfmd process on the node where the
error is occurring, or shutting down and re- This error is likely caused by a system
enabling any affected interfaces.
problem, such as running out of memory.

If the error is the result of a configuration

change, remove and reapply the
configuration. If this does not work, the
error may be cleared by restarting the
cfmd process on the node where the error
is occurring, or shutting down and reenabling any affected interfaces.

This error is likely caused by a system

problem, such as running out of memory.

Attempt to resolve any memory issues

before attempting to solve this problem.
After system resource isses have been
resolved, issue 'process restart cgm' or
'process restart cfmd' on the affected node.
If the message recurs, copy the error
Apply failures should only be caused by
message exactly as it appears on the
memory exhaustion. Any other problem
console or in the system log, call your
indicates an issue with CFM internal state.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Restarting the CFM Daemon on the node

where the problem has occurred may help
to resynchronize the system state. This
error may occur as a result of memory
exhaustion; attempt to resolve any
memory issues before attempting to solve
this problem. After system resource isses
have been resolved, issue 'process restart
cfmd location <node>' If the message
recurs, copy the error message exactly as it This is likely to indicate either a memory
appears on the console or in the system
exhaustion issue or an inconsistency
log, call your Cisco technical support
between configuration and CFM internal
representative and provide the
state. Report this to Engineering. Use Topic
representative with the gathered
to search for a similar DDTS. If you find
information.
none, write a DDTS for this problem.

Removing and re-applying the

configuration responsible for the failed
operation may help to resynchronize
system state. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

This could indicate a problem in the Bridge

Domain or L2VPN infrastructure, SysDB,
PFI, or CFM-D. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

Restarting the CFM Daemon on the node

where the problem has occurred may help
to resynchronize the system state. This
error may occur as a result of memory
exhaustion; attempt to resolve any
memory issues before attempting to solve
this problem. After system resource isses
have been resolved, issue 'process restart
cfmd location <node>' If the message
recurs, copy the error message exactly as it This is likely to indicate either a memory
appears on the console or in the system
exhaustion issue or an inconsistency
log, call your Cisco technical support
between configuration and CFM internal
representative and provide the
state. Report this to Engineering. Use Topic
representative with the gathered
to search for a similar DDTS. If you find
information.
none, write a DDTS for this problem.

Restarting the CFM Daemon on the node

where the problem has occurred may help
to resynchronize the system state. This
error may occur as a result of memory
exhaustion; attempt to resolve any
memory issues before attempting to solve
this problem. After system resource isses
have been resolved, issue 'process restart
cfmd location <node>' If the message
recurs, copy the error message exactly as it This is likely to indicate either a memory
appears on the console or in the system
exhaustion issue or an inconsistency
log, call your Cisco technical support
between configuration and CFM internal
representative and provide the
state. Report this to Engineering. Use Topic
representative with the gathered
to search for a similar DDTS. If you find
information.
none, write a DDTS for this problem.

Restarting the CFM Daemon on the node

where the problem has occurred may help
to resynchronize the system state. This
error may occur as a result of memory
exhaustion; attempt to resolve any
memory issues before attempting to solve
this problem. After system resource isses
have been resolved, issue 'process restart
cfmd location <node>' If the message
recurs, copy the error message exactly as it This is likely to indicate either a memory
appears on the console or in the system
exhaustion issue or an inconsistency
log, call your Cisco technical support
between configuration and CFM internal
representative and provide the
state. Report this to Engineering. Use Topic
representative with the gathered
to search for a similar DDTS. If you find
information.
none, write a DDTS for this problem.

Restarting the CFM Daemon on the node

where the problem has occurred may help
to resynchronize the system state. This
error may occur as a result of memory
exhaustion; attempt to resolve any
memory issues before attempting to solve
this problem. After system resource isses
have been resolved, issue 'process restart
cfmd location <node>' If the message
recurs, copy the error message exactly as it This is likely to indicate either a memory
appears on the console or in the system
exhaustion issue or an inconsistency
log, call your Cisco technical support
between configuration and CFM internal
representative and provide the
state. Report this to Engineering. Use Topic
representative with the gathered
to search for a similar DDTS. If you find
information.
none, write a DDTS for this problem.

*SUPPORT*

The message indicates that a process has

developed an inconsistent internal state,
which may manifest itself in the form of
other problems. It is unlikely that transient
external problems would trigger this
message. Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

If additional problems are observed then

restarting the process may help to restore
the system to a consistent state. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

The message indicates either the

database, or a user of the database, has
developed an inconsistent state. This is not
expected, and probably indicates a bug.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

*SUPPORT*

The message indicates that the process

tried to release a lock that was not held, or
obtain a lock while it was already held. The
system will proceed on the assumption that
it is already in the desired state by the time
the error has been observed (the lock was
already held or not held as appropriate) so
should continue to function correctly, but
this problem is likely to indicate a
programming error. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Restarting cfmd or cfm_ea processes on

the affected node may help to update the
packet handling correctly. This error may
occur as a result of memory exhaustion;
attempt to resolve any memory issues
before attempting to solve this problem.
After system resource isses have been
resolved, issue 'process restart cfmd' on
the affected node. If that has no effect,
issue 'process restart cfm_ea' on the node
with the affected interfaces. If the message The error string should indicate if this is a
recurs, copy the error message exactly as it PI or PD problem. There is scope here for
appears on the console or in the system
problems between CFM processes and PFI
log, call your Cisco technical support
or CFM processes and PD processes. If the
representative and provide the
problem is resource related the user should
representative with the gathered
free up memory. If it is communication
information.
related, contact the relevant team.

Attempt to resolve any memory issues

before attempting to solve this problem.
After system resource isses have been
resolved, issue 'process restart cfmd' on
the affected node. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This error is likely to be caused by the

system running out of memory. If that does
not appear to be the cause of the problem,
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Restarting the CFM Daemon or Ethernet

Link OAM Daemon may help to
resynchronize the loopback state. This
error may occur as a result of memory
exhaustion; attempt to resolve any
memory issues before attempting to solve
this problem. After system resource isses
have been resolved, issue 'process restart
cfmd' and 'process restart elod' on the
node with the affect interfaces. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Wait until any situation which is putting

stress on system resources is resolved, and
then try to delete and re-apply the
encapsulation configuration. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
This error may be caused by the system
information.
running out of memory.

The process may recover after 60s. If the

problem persists, it may be possible to
recover by restarting the 'cfmd' process on
the node where the problem occurred.

This is caused by an error from the timer

wheel library. The library may also have
logged its own errors which give further
details.

If the error persists, it may be cleared by

restarting the cfmd process on the node
where the error is occurring.

This error is likely caused by a system

problem, such as running out of memory,
although it could indicate a problem in
CFM. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

If any problems are observed, then try

removing the debug filter using the 'no
debug ethernet cfm' command. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This could indicate a problem in CFM.

Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If any problems are observed, then check

the status of the l2fib and l2vpn processes
for any obvious errors. If necessary, try
restarting the process that encountered the
error using the 'process restart' command.
If the message recurs, copy the error
message exactly as it appears on the
This could indicate a problem in the L2FIB
console or in the system log, call your
or L2VPN infrastructure, or in CFM. Report
Cisco technical support representative and this to Engineering. Use Topic to search for
provide the representative with the
a similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If any problems are observed, then try

restarting the CFM Daemon using the
'process restart' command. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
This could indicate a problem in CFM.
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

If any problems are observed, then try

restarting the CFM Daemon using the
'process restart' command. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
This could indicate a problem in CFM.
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Wait until any situation which is putting

stress on system resources is resolved, and
then try to delete and re-apply the
configuration for the affected Maintenance
Points. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
This error is likely to be caused by the
gathered information.
system running out of memory.
This message indicates that CFM was
This indicates a low-memory condition.
unable to allocate enough memory for an
Reduce other system activity to ease
operation. Refer to the error message for
memory demands. If conditions warrant,
indication of how much memory was being
upgrade to a larger memory configuration. requested.
This indicates a low-memory condition.
Reduce other system activity to ease
This message indicates that CFM was
memory demands. If conditions warrant,
unable to allocate enough memory for an
upgrade to a larger memory configuration. operation.

The 'cfmd' process will restart after this

error is seen. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and This is caused by an error from
provide the representative with the
pakman/SPP - most likely this indicates a
gathered information.
bug.

Attempt to resolve any memory issues

before attempting to solve this problem.
After system resource isses have been
resolved, issue 'process restart cfmd' on
the affected node. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Wait until any situation which is putting

stress on system resources is resolved, and
then issue the 'process restart cfmd'
command to resynchronize the Interface
states within CFM. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
This error is likely to be caused by the
information.
system running out of memory.

Attempt to resolve any memory issues

before attempting to solve this problem.
After system resource isses have been
resolved, issue 'process restart cfmd' on
the affected node. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This error is likely to be caused by the

system running out of memory. If that does
not appear to be the cause of the problem,
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the error persists and the local MEP

continually reports the received signal as
starting and stopping, the problem may be
corrected by restarting the cfmd process on
the node where the problem is being
This error is likely caused by a system
reported.
problem, such as running out of memory.

No specific action is needed, though the

warning could be a sign of low memory
conditions. If other memory issues are
seen, resolve those first and then reapply
the configuration change.

The message indicates that CFM was

unable to allocate memory to delete a
batch of bridge domains from its internal
database. This should be a side effect of
low memory conditions or a transient
memory allocation issue, the root cause of
these problems should be investigated.
This is likely to be a system-wide issue
rather than a problem specific to CFM.

If the error persists, it may be cleared by

restarting the cfmd process on the node
where the error is occurring.

This error is likely caused by a system

problem, such as running out of memory.

Restarting the process may help to

resynchronize the system state. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This could indicate a problem in the

configuration infrastructure, or in CFM.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the error is the result of a configuration

change, remove and reapply the
configuration. If this does not work, or the
error was triggered by a change in the
network, the error may be cleared by
restarting the cfmd process on the node
where the error is occurring.

This error is likely caused by a system

problem, such as running out of memory.

To trigger a replay of information between

E-LMI and CFM, try restarting the CFM
Daemon using the 'process restart'
command. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
This error is likely caused by a system
gathered information.
problem, such as running out of memory.

Either configure a supported encapsulation

on the interface, without using the above
types of 'complex' matching criteria, or
deconfigure any CFM MPs on the interface. This error indicates a misconfiguration.

Modify either the interface encapsulation a

rewrite configuration, or the CFM
configuration, so as to remove the conflict.
For example, remove any MEP CoS
configuration, or remove any service 'tags'
configuration.
This error indicates a misconfiguration.
If the process in not running and it ought to
be (ie, there is CFM configuration
remaining), then remove all CFM
configuration, commit this change, then reapply the configuration.

The process can be restarted using the

'proc restart' command. Also, any change
to CFM configuration should trigger SysMgr
to restart the process.

The process will exit and will be restarted.

If the problem persists, Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The process failed to start successfully. This

may be due to errors from other
components in the system, so check the
log to ensure the rest of the system is
working correctly and resolve any other
problems, then restart the process.

If the error persists and peer MEPs

continually flap as a result, the problem
may be corrected by restarting the cfmd
process on the node where the problem is
being reported.

This error is likely caused by a system

problem, such as running out of memory.

If any problems are seen, they may be

rectified by restarting the process using the A call to event_block() failed - this is likely
'process restart' command.
to indicate a system problem.

CFM should continue to operate normally,

except for possible re-ordering of MIB index
values for any configured Domains and
Services. CFM will have tried to correct any
errors it encountered in the checkpoint
database. If additional problems with CFM
configuration are observed, then restarting
the CGM Global Manager may help to
resolve the problem. The CFM Global
Manager can be restarted by issuing
'process restart cgm' on the affected node.
If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

CFM should continue to operate normally,

except for possible re-ordering of MIB index
values for the affected items. CFM will have
tried to correct any errors it encountered in
the checkpoint database. If additional
problems with CFM configuration are
observed, then restarting the CGM Global
Manager may help to resolve the problem.
The CFM Global Manager can be restarted
by issuing 'process restart cgm' on the
affected node. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the error persists, the problem may be

corrected by restarting the cfmd process on
the node where the problem is being
This error is likely caused by a system
reported.
problem, such as running out of memory.

If the error persists, the problem may be

corrected by restarting the cfmd process on
the node where the problem is being
This error is likely caused by a system
reported.
problem, such as running out of memory.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
This is caused by an error from the offload
Cisco technical support representative and infrastructure. The infra may also have
provide the representative with the
logged its own errors or tracing which give
gathered information.
further details.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
This is caused by an error from the
Cisco technical support representative and Ethernet Packet Infra library. The library
provide the representative with the
may also have logged its own errors or
gathered information.
tracing which give further details.

None.

As the explanation suggests, this message

is the result of receiving an unexpected TLV
within the given packet type. This reflects
either a conflicting view of the IEEE/ITU
standards between this device and the
device sending the packet, or just an
implementation bug on the remote side.
This device will continue to operate
correctly and no interoperability issues
should be seen. That said, it will be useful
to get full details of the packets and pass
those on to the engineering team for
comments with regards to standards
compliance.

If the error persists, it may be cleared by

restarting the cfmd process on the node
where the error is occurring.

This error is likely caused by a problem in

SPIO or in the platform code for attaching
interfaces.

The creation of the local MEP can be retried

by unconfiguring CFM on the Satellite
Fabric Link and reconfiguring again.
--

The extra MEP in CFM manageability

commands can be ignored. If this is not
possible the delete should be retried by
bringing the Satellite Fabric Link up and
then removing it again. If this persists, then
try restarting the CFM Daemon using the
'process restart' command. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.
--

The extra MEP in CFM manageability

commands can be ignored. If this is not
possible the delete should be retried by
bringing the Satellite Fabric Link up and
then removing it again. If this persists, then
try restarting the CFM Daemon using the
'process restart' command. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.
--

If the error reason given at the end of the

message indicates that the SLM database
has reached its entry limit, then no more
new SLM sessions can be supported. The
system can support 16,000 SLM sessions in
progress simulataneously, this message
will be seen if more than that number are
being attempted (per linecard). This
message may also be seen if there are
inactive SLM sessions still stored in the
database, taking the total entries above
the limit. Any inactive session entries will
be cleared by the database within 5
minutes. To resolve the issue urgently, the
database may also be cleared by restarting
the cfmd process on the node where the
error is occurring. This action will result in
all existing test sessions reporting a small
number of lost packets. Otherwise, the
error reason will either indicate memory
exaustion on the LC, or some other
unexpected condition. If this error occurred
as a result of memory exhaustion; attempt
to resolve any memory issues before
attempting to solve this problem. As we
have failed to respond to an SLM, it may be
useful to restart the test from the source
device once the issue is resolved.

This error is likely either caused by the SLM

database reaching full capacity, or memory
allocation failures during database entry
creation or SLR packet creation.

Collect SPIO PI and PD traces along with

console logs. show spio trace cfm location
<> sh spio ifhcache cfm/elo ifhandle <>

--

This message ahould only relate to CCMs

If the message recurs, copy the error
recieved from offloaded peer MEPs. There
message exactly as it appears on the
are two cases where this message may be
console or in the system log, call your
seen; if the offload service has reset it's
Cisco technical support representative and counters unexpectedly, or if the first packet
provide the representative with the
sent from the offload service after a
gathered information.
counter reset is dropped.

None.

It is not expected that CCMs will be running

for long enough with errors for this
message to be seen. Should this message
be seen, then it most likely indicates a
problem with the provisioning of CFM.

The problem may resolve itself given

sufficient time, otherwise reduce other
system activity to ease memory and CPU
demands. If CFM still doesn't come up on
configured satellite links to these satellites,
collect the required information.

CFM-D was unable to connect to some

configured satellites, either because the
system has run out of memory, CFM-D was
unable to message the ICPE service, or
because the satellites in question have
stalled whilst negotiating with the host.

None.

--

None.

--

None.

--

None.

--

None.

--

Use CFM debugging ('debug ethernet cfm

packets') to determine from where the
problematic packets are originating. If the
packets are from a trusted source and are
expected, modify the configuration on that
host to reduce the number of organisationspecific or otherwise unknown TLVs
contained in the packet (ie TLVs not
defined in the CFM standard, IEEE
802.1ag).

This error could be seen if a peer host is

erroneously or maliciously sending CFM
PDUs with an excessive number of
unknown or organisation-specific TLVs.

None.

--

The user may continue to work without

access to DOT1AG MIB debug, elements of
the MIB will still be accessible & elements
of other MIBs will be unaffected. If the user
requires debug, or would rather have
debug available should further problems
arise, restarting the mibd_interface process
will prompt another attempt at debug
initialization which may succeed. Before
performing a process restart, the user
should evaluate the likelihood of a restart
resolving the problem. For example, if the
error message indicates an out of resource
condition, the user should look into and
resolve any memory issues on the device
before attempting the restart.
--

Continue working with the DOT1AG MIB

DLL without any the ability to query the
Dot1agCfmStackEntryTable, or restart the
mibd_interface process in an attempt to
clear the error. If the error message
indicates an out of resource condition
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration.

If the error persists this likely indicates a

programming error in either CFM or the
SNMP infrastructure. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Continue working with the DOT1AG MIB

DLL without any the ability to send traps
when events occur or restart the
mibd_interface process so that there is
another attempt to register for traps. If the
error message indicates an out of resource
condition Reduce other system activity to
ease memory demands. If conditions
warrant, upgrade to a larger memory
configuration.

This error message indicates a problem

with the SNMP trap registration
infrastructure and will require support from
the SNMP team. It is possible multiple
components are affected by a similar issue.
Explore whether other trap events are also
failing to occur. Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

*RECUR*

It is difficult to know what could cause this

error, other than an OS problem. Possibly a
shortage of memory could result in this
failure. Ask the customer to check how
much memory is available at the location
where the error was reported.

*RECUR*

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

*NONE*

This is an internal error that is causing

multiple notifications to be generated for a
single interface. This should never occur
and could have unpredictable results if the
batch is propogated further. At the moment
this is handled gracefully by the cHDLC EA
by ignoring all but the first notification. This
should be sufficient to continue without a
problem, but the underlying issue in IM
should be investigated. The message will
indicate what type of notification was
received in duplicate. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Please shut and no shut the problematic

interface or enable keepalives on the
interface to fix the problem.

This occurs when there is a communication

failure with Interface manager. If the
problem cannot be resolved by
recommended action, Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem..

The problem can be fixed by manually

starting the cHDLC Socket server process
on the affected node using the command
'process start chdlc_socket location
<location>'. The command 'show process
chdlc_socket location <location>' will
indicate the state of the process. Once the
socket server process is running, no further
action is required.

If the problem cannot be resolved by the

recommended action, based on the error
message Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

*RECUR*

It is difficult to know what could cause this

error, other than an OS problem. Possibly a
shortage of memory could result in this
failure. Ask the customer to check how
much memory is available at the location
where the error was reported.

*RECUR*

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

*RECUR*

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

*RECUR*

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

*RECUR*

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

*NONE*

This is an internal error that is causing

multiple notifications to be generated for a
single interface. This should never occur
and could have unpredictable results if the
batch is propagated further. This will be
handled gracefully by the cHDLC MA by
ignoring all but the first notification. This
should be sufficient to continue without a
problem, but the underlying issue in ifmgr
should be investigated. The output of the
message will indicate what type of
notification was received in duplicate.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

*RECUR*

It is difficult to know what could cause this

error, other than an OS problem. Possibly a
shortage of memory could result in this
failure. Ask the customer to check how
much memory is available at the location
where the error occured.

*RECUR*

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

It is expected that restarting the process

will fix this problem. This is done
automatically so no action should be
required. If the problem recurs, then there
is a problem in packet manager. A drastic
solution would be to reload the linecard.

It is likely that this is a general problem

and the cause of the problem is unrelated
to the cHDLC Socket process. It will have
restarted and so will try to reconnect to
Pakman. This should be sufficient to fix the
problem. If not, there is little else that can
be done by the Socket process.

*SUPPORT*

Such failures are not expected, but could

indicate that there is a problem with the
debugging infrastructure, or a low memory
condition. The error reported in the
message may indicate what the cause of
the problem is. Also check the state of
SysDB, whether the router has run out of
free memory, and if other processes are
having similar problems starting up.

*SUPPORT*

The encap callback function provided by

the network protocol is not available, so
the packet encapsulation failed and the
packet was dropped. A likely consequence
would be a ping failure or similar packet
loss. Investigate the state of the IM and
NetIO chains ('show im|netio chains
interface '). Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

*SUPPORT*

Such failures are not expected, but could

indicate that there is a problem with the
tracing infrastructure, or a low memory
condition. The error reported may give
some indication of what the cause of the
problem is. Also check whether the router
has run out of free memory, and if other
processes are suffering similar startup
problems.

This error indicates that the PM622 FPGA

Driver detected a fatal condition. This does
If the message recurs, copy the error
not mean the PLIM HW is in fault always;
message exactly as it appears on the
however, the PLIM might be reset. If the
console or in the system log, call your
error is persistent, replace the hardware or
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

*RECUR*

These messages do not mean a critical

event has occurred, Flow Control should
continue to operate as expected. Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

*RECUR*

These messages do not mean a critical

event has occurred, Flow Control should
continue to operate as expected. Report
this to Engineering. Use Topic to search for
a similar DDTS. If you find none, write a
DDTS for this problem.

*RECUR*

Something has gone wrong internally in

EFCM. Flow Control is most likely affected
by this error. It is also likely other
messaging errors will be displayed during
this condition. The SPA or Jacket process
will likely restart to clear this condition.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

*RECUR*

Something has gone wrong internally in

EFCM. Flow Control is most likely affected
by this error. It is also likely other
messaging errors will be displayed during
this condition. The SPA or Jacket process
will likely restart to clear this condition.
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

*RECUR*

Something has gone wrong internally in

EFCM. Boundary checking on internal
values failed. Flow Control on some
channels may be affected by this error.
Verify that the SPA interfaces are
configured correctly and have not
exceeded the maximum number of
interfaces permitted for this type of SPA.

If the error message suggests a GSP error,

this is a sign of a wider problem with internode communcation on the device - seek
assistance with debugging gsp and
communication issues. Gathering 'show
tech-support gsp' may assist your TAC
engineer with diagnosis. If the error
appears transient, restarting the process
which emitted this error message should
result in a full resync of all data. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Follow any known checkpoint memory

corruption diagnostic steps. Restarting the
process that emitted this error message
may clear the state. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

This message is usually harmless and the

system will recover. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
EXMEM clear of cross under a threshold

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
EXMEM declare of cross over a threshold

*SH_CMD show controllers pse qfp

infrastructure exmem statistics location <
> * *SH_CMD show controllers pse qfp 0
infrastructure memory ppe-address
location < > * *SH_CMD show controllers
pse qfp 0 statistics summary location < > *
*SH_CMD show controllers pse qfp 1
This error indicates that the CPP Infra SBS
statistics summary location < > * *SH_CMD detected a fatal condition. This does not
show controllers pse qfp infrastructure
mean the ASIC HW is in fault always. The
exmem statistics location < > *
message will inform the severity.

*SH_CMD show controllers pse qfp

infrastructure tcam resource-manager
usage location < > * *SH_CMD show
controllers pse qfp infrastructure tcam
resource-manager error parity location < >
* If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and This error indicates that the CPP TCAM RM
provide the representative with the
detected a fatal condition. The message
gathered information.
will inform the severity.

*SH_CMD show controllers pse qfp

infrastructure tcam resource-manager
usage location < > * *SH_CMD show
controllers pse qfp infrastructure tcam
resource-manager error parity location < >
* *SH_CMD debug controllers pse qfp tcam
resource-manager all job <> loc <>* If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This error indicates that the TCAM resource

manager failed to send a IPC message to
their clients. Collect above show
commands when this message is seen
repeatedly.

*SH_CMD show controllers pse qfp

infrastructure tcam resource-manager
Non fatal message for CPP TCAM RM. If the
usage location < > * *SH_CMD show
error persists then Report this to
controllers pse qfp infrastructure tcam
Engineering. Use Topic to search for a
resource-manager error parity location < > similar DDTS. If you find none, write a
*
DDTS for this problem.
No action is required.

Informational message from the CPP TCAM

RM.

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show
logging<noCmdBold> command 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
<CmdBold>show logging<noCmdBold>
output, call your Cisco technical support
representative and provide the
representative with the gathered
information.

CPP HA has completed microcode crash

dump, Please collect the crash dump file
which will be logged on the console along
with complete show logging and complete
running config.

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show
logging<noCmdBold> command 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
<CmdBold>show logging<noCmdBold>
output, call your Cisco technical support
representative and provide the
representative with the gathered
information.

CPP HA process have failed to initialize,

Please collect the info mentioned in the
recommended_action along with complete
running config.

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show
logging<noCmdBold> command 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
<CmdBold>show logging<noCmdBold>
output, call your Cisco technical support
representative and provide the
CPP HA had encountered faults, please
representative with the gathered
collect crash dump file if any along with
information.
complete show logging and running config

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show
logging<noCmdBold> command 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
<CmdBold>show logging<noCmdBold>
output, call your Cisco technical support
representative and provide the
CPP HA had encountered faults, please
representative with the gathered
collect crash dump file with complete show
information.
logging and running config

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show
logging<noCmdBold> command 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
<CmdBold>show logging<noCmdBold>
output, call your Cisco technical support
representative and provide the
CPP HA had encountered faults, please
representative with the gathered
collect crash dump file with complete show
information.
logging and running config

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show
logging<noCmdBold> command 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
<CmdBold>show logging<noCmdBold>
output, call your Cisco technical support
representative and provide the
representative with the gathered
information.

CPP HA process have failed to initialize,

Please collect the info mentioned in the
recommended_action along with complete
running config.

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show
logging<noCmdBold> command 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
<CmdBold>show logging<noCmdBold>
output, call your Cisco technical support
representative and provide the
CPP HA CDM is not running Please collect
representative with the gathered
the output of commands mentioned in
information.
recommeneded_action.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the error messages persist, please collect

the console log, software version, running
configuration (show running-config),
platform hardware inventory list (show
platform), diagnostic information of RP or
LC card in question (show diag
<location>), and report to it CISCO
engineering.

If this is caused by router's receiving of

malformed packets, the malformed packets
could be incidental or it could be malicious
like denial of service attack.

It may help to restart the VLAN EA process

on the affected node, with
<CmdBold>process restart vlan_ea
location [location]<noCmdBold>. Copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If this error occurred as a result of applying

configuration, try removing and reapplying
the configuration. If this does not work, it
may be necessary to reload the affected
linecard. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If this error occurred as a result of applying

configuration, try removing and reapplying
the configuration. If this does not work, it
may be necessary to reload the affected
linecard. Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

No action is required.

--

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This error indicates a failure to obtain an

item from SYSDB, process an event or
attribute initialisation.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This error indicates a failure to either start

PLIM driver, create event manager, unable
to open conn. via ECM, initialise
debugging, initialise EDM, bind to SYSDB or
obtain a nodeid.

If the system has run out of memory then

there will be many other tell-tale signs.
Lots of processes will be reporting similar
error messages. The output of 'show mem
Reduce other system activity (e.g. by
heap summary all' should indicate whether
killing non-essential processes) to ease
a single process is hogging all the memory.
memory demands. If conditions warrant,
Restarting this process may solve the
upgrade to a larger memory configuration. problem.

Copy the error message exactly as it

appears, and report it to your technical
support representative.

An error occured when trying to read the

tuple from sysdb. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

At the time of creating thread for dwdm

component , it has failed to get
event_block. It will be a corner case.
Collect the required info, given below.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

At the time of initialization of dwdm

component , Platform has failed to get
nodeid. It will be a corner case. Collect the
required info, given below.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

NONE

A forced maintenance activity implies that

there may be loss of traffic. A port should
not be put into maintenance state (unless
its absolutely necessary) if maintenance is This message is to indicate forced
disabled by the administrator. That status maintenance. Plesae check if it has not
can be checked using show interfaces CLI. been done manually by admin.

Do not change the transport admin state of

the port to maintenance unless absolutely
required.
This message is for information only.

It is just a notification.

This message is for information only.

None.

This message is for information only.

None.

This message is for information only.

None.

This message is for debug purpose only.

None.

This message is for debug purposes only.

Reconfigure all interfaces on the hypervisor

to be of the same driver type.
-If any problems are seen, they may be
rectified by restarting the spp process
using the 'process restart spp' command.

The plug-in's register_thyself() function

failed - this is likely to indicate a system
problem.

Verify that the card has at least the

minimum supported memory configuration.
Use the 'show memory' and 'show
processes memory location' commands to
identify what processes use the memory. If
memory usage for a process seems
abnormal, restarting the process using the
command 'process restart' could be a
workaround. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your Check for the total memory in the system
Cisco technical support representative and and its usage by processes. Raise a DDTS if
provide the representative with the
system has the minimum supported
gathered information.
memory for deployment of the image.

Reload the linecard. If the message recurs,

copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Reload the linecard. If the message recurs,

copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.
Reload the linecard. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Verify that the card has at least the

minimum supported memory configuration.
Use the 'show memory' and 'show
Check for the total memory in the system
processes memory location' commands to and its usage by processes. If the card has
identify what processes use the memory. If enough memory and the memory usage is
memory usage for a process seems
normal, open a ddts. Use the 'show shmwin
abnormal, restarting the process using the ' command to verify that the shared
command 'process restart' could be a
memory window exist on the specified
workaround.
card.

Reload the linecard. If the message recurs,

copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.
--

Reduce the multicast traffic rate sent to

this line card.

--

Reload the linecard. If the message recurs,

copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Reload the linecard. If the message recurs,

copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.
Reload the linecard. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.
Re-configure with different max-threshold
satisfying supported limit.

--

Re-configure with different min-threshold

satisfying supported limit.

--

Re-configure with different max-threshold

greater than current min-threshold.

--

Re-configure with different min-threshold

less than current max-threshold.

--

No action required.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Reduce the multicast traffic rate sent to

this line card.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.
Re-configure with different max-threshold
satisfying supported limit.

--

Re-configure with different min-threshold

satisfying supported limit.

--

Re-configure with different max-threshold

greater than current min-threshold.

--

Re-configure with different min-threshold

less than current max-threshold.

--

No action required.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Please contact the TAC representative for

hardware information on which this feature
is supported
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Pls get the information specified under the

component required_info and call your
Cisco technical support representative and
provide the representative with the
gathered information with this error
message text
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Pls get the information specified under the

component required_info and call your
Cisco technical support representative and
provide the representative with the
gathered information with this error
message text.
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Pls get the information specified under the

component required_info and call your
Cisco technical support representative and
provide the representative with the
gathered information with this error
message text
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Pls get the information specified under the

component required_info and call your
Cisco technical support representative and
provide the representative with the
gathered information with this error
message text
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Pls get the information specified under the

component required_info and call your
Cisco technical support representative and
provide the representative with the
gathered information with this error
message text
-Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Pls get the information specified under the

component required_info and call your
Cisco technical support representative and
provide the representative with the
gathered information with this error
message text
--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

A failure reason is included in the message.

If resources are unavailable, this is
expected. Otherwise a DDTS should be
filed. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

No action is required. If the message

recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Reduce other system activity to ease

Report this to Engineering. Use Topic to
memory demands. If conditions warrant,
search for a similar DDTS. If you find none,
upgrade to a larger memory configuration. write a DDTS for this problem.

Reduce other system activity to ease

Report this to Engineering. Use Topic to
memory demands. If conditions warrant,
search for a similar DDTS. If you find none,
upgrade to a larger memory configuration. write a DDTS for this problem.

Please check Plim ASIC and related driver

process status, Copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This situation may also happen when sharq

driver invokes the dll API of PLIM ASIC
driver and failed to retrieve the per port BP
map. No action will be taken at Egressq
side. Check process status of Plim ASIC
driver. Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem.

No action is required. Process will be

automatically restarted. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
Reseating of memory modules may fix this
representative and provide the
issue. Report this to Engineering. Use Topic
representative with the gathered
to search for a similar DDTS. If you find
information.
none, write a DDTS for this problem.

This situation may also happen, though

very unlikely, when deallocation of one or
more EgressQ queues occurs when a large
number of packets are still pending in
If this message appears more than once in those queues because of high traffic rate
response to the specific action taken or if
exceeding line rate. ASIC auto reset will be
the message indicates a large number of
invoked to recovery from the error
bytes (more than 10MB) in an unallocated condition if the packets stay in queue more
queue(s), Copy the error message exactly than 10 seconds. Line Card reload is
as it appears on the console or in the
triggered after 5 time asic reset to fix this
system log, call your Cisco technical
problem. If the problem still occur, Report
support representative and provide the
this to Engineering. Use Topic to search for
representative with the gathered
a similar DDTS. If you find none, write a
information.
DDTS for this problem.
No action is required. The driver will
perform asic recovery. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Watch for potential drop in the egress

traffic. If the router misbehaves or traffic is
dropped, please collect the information
from the following commands for the line
card that reported the error: show tech
show controller egressq trace all show
controller egressq interface all show
controller egressq port all show controller
egressq group all show controller egressq
queue all show qos ea trace all Call your
Cisco technical support representative and
provide the representative with the
gathered information.

In order for traffic to keep flowing while

upgrading from version X to version Y, the
same queue/group/ports must be used
throughout the process. The error is caused
by the fact that version Y did not maintain
the same mapping. The error could cause
packets to be misdirected for a short
period. But it could also cause a queue to
get stuck, which would be a more severe
problem requiring a line card reload.

The egress queueing asic's Host Processor

Interface (HPI) block is connected to the
linecard's CPU via PCI links. In rare
occasion, the HPI block and the PCI link
may experience temporary and transient
hardware error due to the hardware hitting
by high energy particles from nature's
background radidation. Such error is
reported as hardware access error and
software automatically takes action to
recover from it. Unlesss the hardware
becomes defective, the software recovery
action is sufficient and the error will stop
If the message indicated this is a hardware and won't repeat itself. For such case, no
access error, software will have
other action is required as the temporary
automatically taken action to recover from and transient error can be expected. If the
the error. If harware access error does not hardware error does not stop and persist, it
recur, no other action is required. If the
is likely the hardware has become
hardware access error persists or it is a
defective and the replacement of the board
software access error, copy the System
is required. Another reason for the access
Message exactly as it appears on the
error is due to a un-discovered software
console or in the system log, enter
bug where software makes un-supported
command 'show tech-support controller
access to the ASIC, like writing to a realegressq location <>', report the error to
only location or reading from a non-defined
your Cisco technical support representative location. Such case is reported as software
and provide the representative with the
access error and a DDTS needs to be raised
gathered information.
to have it fixed.

Sending packets to Q0 could potentially

cause egressq queue to get into stuck
state. The asic soft reset will be performed
when the queue stuck condition is
If this message appears more than once in detected. In general, this indicate some
short period, Copy the error message
kind of packet corruption or application
exactly as it appears on the console or in
level bug. To identify the culprit
the system log, call your Cisco technical
application, please file the Report this to
support representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem..

Asic soft reset will be performed once the

queue stuck condition is detected to fix this
problem. If this recovery (soft resets of
sharq) happens above certain threshold,
the LC will be reloaded. The current
By default, driver will perform the asic soft threshold for ASIC reset is 5 per day. In
reset after detecting queue stuck condition. case too many asic soft resetting occurs
If this message appears more than once in and cannot fix the problem, use backdoor
short period, Copy the error message
CLI 'sharq_exec' from LC to change the
exactly as it appears on the console or in
configuration to dump asic memory for
the system log, call your Cisco technical
further debugging. Otherwise reload the LC
support representative and provide the
and Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.
No action is required. The driver will
perform asic recovery. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.
No action is required. The linecard is
Reseating of memory modules may fix this
automatically reloaded. If the error
issue. Report this to Engineering. Use Topic
persists, replace the Modular Service Card to search for a similar DDTS. If you find
(MSC).
none, write a DDTS for this problem.

No action is required. It is a self healing

error. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

This situation may also happen, though

very unlikely, when deallocation of one or
more EgressQ queues occurs when a large
number of packets are still pending in
those queues because of high traffic rate
exceeding line rate. Line Card reload is
If this message appears more than once in necessary to fix this problem. If the
response to the specific action taken or if
messages cease to appear and do not
the message indicates a large number of
indicate a large number of buffers stuck in
bytes (more than 10MB) in an unallocated unallocated queues (say not more than
queue(s), Copy the error message exactly 10MB which is 1% of total buffering), it
as it appears on the console or in the
may not be necessary to reload the LC.
system log, call your Cisco technical
Otherwise reload the LC and Report this to
support representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

This situation may also happen, though

very unlikely, when deallocation of one or
more EgressQ queues occurs when a large
number of packets are still pending in
those queues because of high traffic rate
exceeding line rate. Line Card reload is
If this message appears more than once in necessary to fix this problem. If the
response to the specific action taken or if
messages cease to appear and do not
the message indicates a large number of
indicate a large number of buffers stuck in
bytes (more than 10MB) in an unallocated unallocated queues (say not more than
queue(s), Copy the error message exactly 10MB which is 1% of total buffering), it
as it appears on the console or in the
may not be necessary to reload the LC.
system log, call your Cisco technical
Otherwise reload the LC and Report this to
support representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.

No action is required.

Informational message for Egressq/Tor

Driver.

No action is required.

Informational message for Egressq/Sharq

Driver.

No action is required. Process will be

automatically restarted. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
Reseating of memory modules may fix this
representative and provide the
issue. Report this to Engineering. Use Topic
representative with the gathered
to search for a similar DDTS. If you find
information.
none, write a DDTS for this problem.

No action is required. The process retries

automatically. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

No action is required. The process will

automatically retry. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required. The process will

automatically retry. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

No action is required. The process retries

automatically. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

No action is required. Clients will

automatically retry to connect to Egressq. If
the message recurs, copy the error
message exactly as it appears on the
http://zed.cisco.com/confluence/display/GS
console or in the system log, call your
RTR/Egressq Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

No action is required. The process retries

automatically. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

http://zed.cisco.com/confluence/display/GS
RTR/Egressq Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

No action is required. The process will

automatically retry. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

http://zed.cisco.com/confluence/display/GS
RTR/Egressq Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

No action is required. The process will

automatically retry. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

http://zed.cisco.com/confluence/display/GS
RTR/Egressq Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

No action is required. The process retries

automatically. If the message recurs, copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

http://zed.cisco.com/confluence/display/GS
RTR/Egressq Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

http://zed.cisco.com/confluence/display/GS
RTR/Egressq Report this to Engineering.
Reduce other system activity to ease
Use Topic to search for a similar DDTS. If
memory demands. If conditions warrant,
you find none, write a DDTS for this
upgrade to a larger memory configuration. problem.

No action is required. The process will

automatically retry. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

http://zed.cisco.com/confluence/display/GS
RTR/Egressq Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
problem.

No action is required. Clients will

automatically retry to connect to Egressq. If
the message recurs, copy the error
message exactly as it appears on the
http://zed.cisco.com/confluence/display/GS
console or in the system log, call your
RTR/Egressq Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

Asic soft reset will be performed once the

queue stuck condition is detected to fix this
problem. If this recovery (soft resets of
sharq) happens above certain threshold,
the LC will be reloaded. The current
threshold for ASIC reset is 5 per day. For
By default, driver will perform the asic soft Sharq, in case too many asic soft resetting
reset after detecting queue stuck condition. occurs and cannot fix the problem, use
If this message appears more than once in backdoor CLI 'sharq_exec' from LC to
short period, Copy the error message
change the configuration to dump asic
exactly as it appears on the console or in
memory for further debugging. Otherwise
the system log, call your Cisco technical
reload the LC and Report this to
support representative and provide the
Engineering. Use Topic to search for a
representative with the gathered
similar DDTS. If you find none, write a
information.
DDTS for this problem.
If any problems are seen, they may be
rectified by restarting the process using the A call to pird_db_attach() failed - this is
'process restart' command.
likely to indicate a system problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.
If any problems are seen, they may be
rectified by restarting the process using the A call to event_block() failed - this is likely
'process restart' command.
to indicate a system problem.
If any problems are seen, they may be
rectified by removing the unsupported
configuration.

A configuration option was specified that is

unsupported by the PI Reference
Dataplane.

Consider restarting the ELMI process. If the

message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

A call to one of the AIPC APIs has failed in

an unexpected manner. The error code in
the error message should help identify
what the problem is.

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration..
*RECUR*.

A call to one of the Bag Client library APIs

has failed in an unexpected manner. The
error code in the error message should help
identify what the problem is.

In many cases, ELMI will recover by itself. If

it does not then restarting the process may
help. Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration..
*RECUR*.

A call to one of the Debug APIs has failed in

an unexpected manner. The error code in
the error message should help identify
what the problem is.

Consider restarting the ELMI process. If the

message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

A call to one of the SysDB APIs has failed in

an unexpected manner. The error code in
the error message should help identify
what the problem is.

In many cases, ELMI will recover by itself. If

it does not then restarting the process may
help. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information..

A call to one of the IM APIs has failed in an

unexpected manner. The error code in the
error message should help identify what
the problem is.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
A call to one of the LTrace APIs has failed in
Cisco technical support representative and an unexpected manner. The error code in
provide the representative with the
the error message should help identify
gathered information.
what the problem is.
Reduce other system activity to ease
memory demands. If conditions warrant,
upgrade to a larger memory configuration. This is a resource starvation problem.

Reduce other system activity to ease

memory demands. If conditions warrant,
upgrade to a larger memory configuration..
Consider restarting the ELMI process.
A call to one of the mgd_timer_TYPE
*RECUR*.
functions failed.

Reconfigure the interface's MTU to a larger This error indicates that the router is
value.
misconfigured.

Check that E-LMI is configured on the peer

device and that the link to the peer device
is functionining correctly. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information..
--

Check that E-LMI is configured on the peer

device and that the link to the peer device
is functionining correctly. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information..
--

Check that E-LMI is configured on the peer

device and that the link to the peer device
is functionining correctly. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
Check the value of the message type
representative and provide the
received against the Message Type Coding
representative with the gathered
table in the MEF Standard to see what
information..
report type was received.

Check that E-LMI is configured on the peer

device and that the link to the peer device
is functionining correctly. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Check the value of the protocol version
representative with the gathered
received against the version of the E-LMI
information..
implementation.

Check that E-LMI is configured on the peer

device and that the link to the peer device
is functionining correctly. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
Check the value of the report type received
representative and provide the
against the Report Type Coding table in the
representative with the gathered
MEF Standard to see what report type was
information..
received.

Check that E-LMI is configured on the peer

device and that the link to the peer device
is functionining correctly. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information..
--

Check the Polling Verification Timer value

configured is greater than the Polling Timer
value configured on the peer device. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information..

The E-LMI standard specifies that the

Polling Verification Timer (T392 in the MEF
16 standard) should be greater than the
Polling Timer (T391 in the MEF 16
standard). Make sure this is configured
correctly on both local and peer devices on
the UNI.

Consider restarting the ELMI process. If the

message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

A call to one of the SysDB APIs has failed in

an unexpected manner. The error code in
the error message should help identify
what the problem is.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
A call to one of the SysMgr APIs has failed
Cisco technical support representative and in an unexpected manner. The error code in
provide the representative with the
the error message should help identify
gathered information.
what the problem is.
There was an error calling wavl_init(). This
Reduce other system activity to ease
is highly unexpected, but may just be due
memory demands. If conditions warrant,
to severe memory starvation. If so, the
upgrade to a larger memory configuration.. error string in the message will indicate
*RECUR*
this.

Re-configure the subinterface to use a

different encapsulation. There may be
more subinterfaces with conflicting
encapsulation.

This error indicates that the router is

misconfigured.

Re-configure the subinterface to use a

subinterface number of 65535 or below.

This error indicates that the router is

misconfigured.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If configuration fails to apply, recommitting

it should correct the issue. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
This error is unexpected, and could indicate
console or in the system log, call your
a software bug. Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

Invalid configuration data is being applied.

This can happen if: The user configures an
interface to use a profile with OAM
functionality that is not supported on the
interface. In this case, the user should
either use a different profile or alter the
profile to suit the interface capabilities.
Check that all configuration is within the
This is existing configuration data for which
acceptable ranges for the current version the allowed values have changed. In this
of the software and the installed hardware. case, suggest alternative values that can
If the error persists, and all values are
be used. The data is corrupt. In this case,
within range, copy and save this message, gather the invalid configuration data,
and call your technical support
search for any similar issues, and open a
representative for assistance.
DDTS report.

Attempt to resolve any memory issues

before attempting to solve this problem.
After system resource isses have been
resolved, issue 'process restart' command
on the affected node. If the message
recurs, copy the error message exactly as it Apply failures should only be caused by
appears on the console or in the system
memory exhaustion. Any other problem
log, call your Cisco technical support
indicates an issue with ELO internal state.
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Read the error message, and attempt to

resolve any issue that may have caused it.
Restarting the Ethernet Link OAM Daemon
will then allow it to resynchronise with PFI
and cleanup the dangling caps. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Shutdown the port manually if it is still

desirable to bring it down. Otherwise, no
action is required. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

This error message indicates a

fundamental problem with retrieval of
platform capabilities on the linecard. These
capabilities should be readily available to
the ethernet_link_oam_daemon via a DLL
but it is possible that the platform code has
to look up specific interface properties that
may involve communicating with other
processes and could fail due to processes
This issue indicates that there was a
being blocked. Check for any obvious
problem retrieving interface capabilities for blocked processes such as ifmgr. The
a specific card. This may affect your
message itself is harmless. Any incorrectly
configuration. Attempt to remove and
verified configuration will not be acted
reapply any configuration changes you
upon by the system. If the problem
have made, if this fails call your technical persists, search for any similar issues, and
support representative for assistance.
open a DDTS report.

Un-configure and re-configure the

interface. If that does not resolve the
problem, restarting the process will cause a
retry of the initialisation. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.
--

Retry the Loopback operation. If the

message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Try restarting the Ethernet Link OAM

Daemon using the 'process restart'
command. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

This could indicate a problem in Ethernet

Link OAM or a more serious problem with
the LWM service on the node. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

*SUPPORT*

The message indicates that the process

tried to release a lock that was not held, or
obtain a lock while it was already held. The
system will proceed on the assumption that
it is already in the desired state by the time
the error has been observed (the lock was
already held or not held as appropriate) so
should continue to function correctly, but
this problem is likely to indicate a
programming error. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

Restart the Ethernet Link OAM daemon

process. This should cause a re-registration
with IM, ensuring the correct interfaces are
registered for notifications. If the message
recurs, copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

Try restarting the Ethernet Link OAM

Daemon using the 'process restart'
command. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

This could indicate a problem in Ethernet

Link OAM or a more serious problem with
the LWM service on the node. Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the error is the result of a configuration

change, remove and re-apply the
configuration. If this does not work the
error may be cleared by restarting the
ethernet_link_oam_daemon process on the
node where the error is occurring. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
This error is likely caused by a system
information.
problem, such as running out of memory.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Start slave Loopback mode before

attempting to stop it.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

Restart the Ethernet Link OAM Daemon on

the affected node. This will force a resync
of the state with PFI. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
Report this to Engineering. Use Topic to
representative with the gathered
search for a similar DDTS. If you find none,
information.
write a DDTS for this problem.

Resynchonrisation mechanisms should

ensure subsequent messages are correctly
sent. If the message recurs, copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

This problem is likely caused by another

process consuming too much CPU. This can
Identify any potential high CPU users, and either be a runaway process, or some other
reduce their impact. If the message recurs, event on the box causing a very high load.
copy the error message exactly as it
Identify the high CPU user, and reduce its
appears on the console or in the system
impact to allow the OAM Daemon to return
log, call your Cisco technical support
to sending its regular heartbeat messages.
representative and provide the
If the message appears when the system
representative with the gathered
load is not high, gather the required
information.
information and raise a DDTS.

None - this message is for information only

and does not indicate an error.
-This is an informational message regarding
Ensure that the configuration requirements the status of the OAM protocol, and does
on this interface match the configuration of not indicate any abnormal issues within the
the remote OAM peer.
software.

Ensure the remote OAM peer is correctly

configured and that the link is up.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

No specific IOS-XR action needs to be

performed.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

Restart the remote peer.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

Check the wiring between the two

interfaces.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

None. This is an informational message.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

Check that the remote peer is correctly

configured still. If it is, then a large number
of packets may be being dropped on the
link.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

None. This is an informational message.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

No specific IOS-XR action needs to be

performed.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

This is an informational message regarding

Retry the Loopback operation from this
the status of the OAM protocol, and does
peer once the remote loopback session on not indicate any abnormal issues within the
the remote peer has been terminated.
software.

Nothing need be done if the default values

are acceptable for the invalid parameters.
Otherwise, modify the profile to contain
only configuration that is supported for the
interfaces to which it is attached, or use an
alternate profile for this interface.

If this message is being generated when all

values appear to be in acceptable ranges,
gather the required information and raise a
DDTS.

Check the wiring of the specified interface.

By setting the mis-wiring action to 'log',
and using the packet debugging facility of
Ethernet Link OAM ('debug ethernet oam
packets'), the MAC addresses of the source
of packets can be used to identify where
the links are.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

Create the specified profile, or remove the

configuration associating the profile with
the interface.
--

No corrective action is required. This peer

has exited Loopback mode also, and the
link is now back to normal operational
status.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

No corrective action is required. This peer

has exited Loopback mode also, and the
link is now back to normal operational
status.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

No corrective action is required. This peer

has exited Loopback mode also, and the
link is now back to normal operational
status.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

No specific IOS-XR action needs to be

performed.

This is an informational message regarding

the status of the OAM protocol, and does
not indicate any abnormal issues within the
software.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

It is difficult to know what could cause this
message exactly as it appears on the
error, other than an OS problem. Possibly a
console or in the system log, call your
shortage of memory could result in this
Cisco technical support representative and failure. Ask the customer to check how
provide the representative with the
much memory is available at the location
gathered information.
where the error was reported.

Such failures are not expected and the only

If the message recurs, copy the error
information to go on will be in the message
message exactly as it appears on the
displayed. If the problem cannot be
console or in the system log, call your
resolved based on the error message
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

One possible cause of this problem is the

termination of the System Manager process
Check on the status of the sysmgr process during this process' initialization. Use 'show
on the node from which the error was
process sysmgr', specifying the appropriate
reported. If the message recurs, copy the location, to determine whether this is the
error message exactly as it appears on the case. If System Manager has not restarted,
console or in the system log, call your
and the problem persists, Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

*DDTS*

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
First ensure that the backplane is correctly search for a similar DDTS. If you find none,
programmed and reprogram if necessary. write a DDTS for this problem.

*DDTS*

Such failures are not expected and the only

information to go on will be in the message
displayed. If the problem cannot be
resolved based on the error message
Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the pool is exhausted and MAC address

configuraion is allowed, configure more
MAC addresses. Otherwise reduce scale.

If the requested amount from the client

looks reasonable (

This error indicates that an attempt to

allocate memory failed in EPI when called
back by the attributes library following a
This message will be seen as a result of a configuration change on an interface the
configuration change if the system is low
EPI client is interested in. EPI will fail to
on memory. Attempt to free up some
notify the client that it needs to regenerate
memory and reapply the configuration
packets with the new attribute information
change that caused this message to be
and so any packets the EPI client sends
displayed. If the problem persists, try
may be bogus. In order to get the correct
restarting the process using this library. If packets flowing again, some memory
this does not help, Copy the error message needs to be freed up and the attribute
exactly as it appears on the console or in
notification callback needs to be triggered
the system log, call your Cisco technical
again. The easiest way to do that is to
support representative and provide the
reapply the config that caused the error to
representative with the gathered
be displayed when some memory has been
information.
freed up.

The process using the library should deal

with this error by exiting and restarting in
an attempt to resolve the error condition. If
the process does not automatically restart,
a manual process restart may solve the
problem. In both automatic and manual
restart scenarios, the details of the error
string may help suggest possible
workarounds or recovery methods. For
example, a temporary 'resource not
available' condition may suggest other
system wide memory issues to be
investigated. If the problem persists, Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The process failed to start successfully. This

may be due to errors from other
components in the system, so check the
log to ensure the rest of the system is
working correctly and resolve any other
problems, then restart the process that is
using this library.

This message indicates that the EPI

database has incremented its per-interface
packet reference count past the maximum
This message is likely to indicate an
number of packets supported. This will
internal error in the process that means it mean the reference count is out of sync. If
is not freeing its old packet information
the EPI client process later frees enough
correctly. If the process is not restarted
packets, it may decrement the packet
then a future configuration change for the count to zero when it should be non-zero.
interface in question may not be reflected The result of this will be that EPI will not
in the generated packets. Try restarting the notify the client of any attribute changes,
process and, if the problem persists, Copy and so packet generation may be
the error message exactly as it appears on adversely affected. Restarting the process
the console or in the system log, call your which emitted this error message may
Cisco technical support representative and solve the problem, but there is likely to be
provide the representative with the
an internal programming error that needs
gathered information.
addressing as well

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

The edpl_ma process should be restarted

using the following command: - process
restart edpl_ma

The specified module tried to initialise but

came across an error. If restarts do not fix
this issue, Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.
Please see the internal troubleshooting
Wiki at
http://enwiki.cisco.com/EthernetOam/Edpl/T
roubleshooting for help.

The process is automatically restarted. If

the problem persists, Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

An internal error has occurred, for example

the database might be corrupt with an
expected node not existing in an AVL tree.
Please see the internal troubleshooting
Wiki at
http://enwiki.cisco.com/EthernetOam/Edpl/T
roubleshooting for help.

Memory could not be successfully allocated

upon the relevant call. This is likely
because none was available. If restarts do
The process is automatically restarted. If
not fix this issue, Report this to
the problem persists, Copy the error
Engineering. Use Topic to search for a
message exactly as it appears on the
similar DDTS. If you find none, write a
console or in the system log, call your
DDTS for this problem. Please see the
Cisco technical support representative and internal troubleshooting Wiki at
provide the representative with the
http://enwiki.cisco.com/EthernetOam/Edpl/T
gathered information.
roubleshooting for help.

The edpl_ma process should be restarted

using the following command: - process
restart edpl_ma

The call to sysdb_resume_apply failed

unexpectedly. If restarts do not fix this
issue, Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem. Please
see the internal troubleshooting Wiki at
http://enwiki.cisco.com/EthernetOam/Edpl/T
roubleshooting for help.

Either wait for the loopback session to

expire naturally or restart the edpl_ma
process using the following command: process restart edpl_ma To stop the session
manually, use the following command: ethernet loopback stop local interface
<name> id <id>

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem. Please see
the internal troubleshooting Wiki at
http://enwiki.cisco.com/EthernetOam/Edpl/T
roubleshooting for help.

The cleanup function in the database was

called with active interfaces still present.
These interfaces were deleted by the
cleanup function but this should not occur
in a clean exit. If restarts do not fix this
issue, Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
If any problems are seen, they may be
none, write a DDTS for this problem. Please
rectified by restarting the edpl_ma process see the internal troubleshooting Wiki at
using the following command: - process
http://enwiki.cisco.com/EthernetOam/Edpl/T
restart edpl_ma
roubleshooting for help.

The edpl_ma process should be restarted

using the following command: - process
restart edpl_ma

The call to sysdb_edm_get_resume or

sysdb_edm_set_resume failed
unexpectedly. If restarts do not fix this
issue, Report this to Engineering. Use Topic
to search for a similar DDTS. If you find
none, write a DDTS for this problem. Please
see the internal troubleshooting Wiki at
http://enwiki.cisco.com/EthernetOam/Edpl/T
roubleshooting for help.

A call to event_block() failed - this is likely

to indicate a system problem. If restarts do
not fix this issue, Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
If any problems are seen, they may be
DDTS for this problem. Please see the
rectified by restarting the edpl_ma process internal troubleshooting Wiki at
using the following command: - process
http://enwiki.cisco.com/EthernetOam/Edpl/T
restart edpl_ma
roubleshooting for help.

If this isn't due to a transient error, and a

process restart doesn't resolve the issue,
Either wait for the loopback session to stop Report this to Engineering. Use Topic to
as a result of the retries or attempt to stop search for a similar DDTS. If you find none,
it manually. If it doesn't stop, it may be
write a DDTS for this problem. Please see
rectified by restarting the edpl_ma process the internal troubleshooting Wiki at
using the following command: - process
http://enwiki.cisco.com/EthernetOam/Edpl/T
restart edpl_ma
roubleshooting for help.

If you need to start another session, either

wait for all active sessions to stop
naturally, or stop them manually. To stop a
session manually, use the following
command: - ethernet loopback stop local
interface <name> id <id>

The session ID counter has reached 2^32 1. The session IDs are not allowed to wrap.
Stopping all sessions will reset the session
ID counter to 1. Please see the internal
troubleshooting Wiki at
http://enwiki.cisco.com/EthernetOam/Edpl/T
roubleshooting for help.

Upon being called by PI to start the

sessions the user wants to run on the
platform during a resync, there was an
error where the session with the ID given
was not able to be start. If restarts do not
fix this issue, Report this to Engineering.
Use Topic to search for a similar DDTS. If
you find none, write a DDTS for this
If any problems are seen, they may be
problem. Please see the internal
rectified by restarting the edpl_ma process troubleshooting Wiki at
using the following command: - process
http://enwiki.cisco.com/EthernetOam/Edpl/T
restart edpl_ma
roubleshooting for help.

Upon being called by PI to stop the

sessions running on the platform, there
was an error where the session with the ID
given was not able to be stopped. If
restarts do not fix this issue, Report this to
Engineering. Use Topic to search for a
similar DDTS. If you find none, write a
If any problems are seen, they may be
DDTS for this problem. Please see the
rectified by restarting the edpl_ma process internal troubleshooting Wiki at
using the following command: - process
http://enwiki.cisco.com/EthernetOam/Edpl/T
restart edpl_ma
roubleshooting for help.

None.

None.

None.

None.

None.

None.

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show
logg<noCmdBold> command 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
<CmdBold>show logg<noCmdBold>
output, call your Cisco technical support
representative and provide the
representative with the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log. Issue the <CmdBold>show
ethernet driver trace<noCmdBold>
command 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 <CmdBold>show ethernet driver
trace<noCmdBold> output, call your Cisco
technical support representative and
provide the representative with the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

No action is required.

No debugging of this component will be

available, but it should otherwise function
properly.

The SPA driver has detected problem with

DWDM init routine. If the ports on the SPA
are not operating as expected, power down
and reseat the indicated SPA card. If the
error messages persists, copy the error
message exactly as it appears. Next
research and attempt to resolve the issue
using the SPA hardware troubleshooting
documentation as well as the tools and
utilities provided at
http://www.cisco.com/public/support/tac/to
ols.shtml. If you still require assistance,
open a case with the Technical Assistance
Center via the Internet at
http://www.cisco.com/cgibin/front.x/case_tools/caseOpen.pl or
contact your Cisco technical support
representative. Be sure to provide the the
information you have gathered and a 'show
tech-support' to your support
representative, or attach it to your case in
non-zipped, plain text format (.txt).

Collect the output of CLIs and contact

ether-spa-india. 1. 'show interfaces TenGigE
<>/<>/<>/<>' 2. 'show controller TenGigE
<>/<>/<>/<>' 3. 'show logging'

Reload SPA/LC. If the issue persists even

after reload collect the output of below CLIs If Reloading of SPA/LC doesn't solve the
and contact TAC. 1. 'show processes cpu
issue, collect the outputs of above CLIs
location <>/<>/<>' 2. 'show memory'
from customer and contact ether-spa-india.

Try Reseating the SPA if the problem

persists even after reseating collect the
output of CLIs and contact TAC. 1. 'show
interfaces TenGigE <>/<>/<>/<>' 2.
The SPA driver failed to initialize the PLL.
'show controller TenGigE <>/<>/<>/<>' 3. Collect the output of above CLIs from
'show logging'
customer and contact ether-spa-india.

If the problem is persistent, check the fiber

for faults. Try cleaning the fiber and
inserting it back. Please collect the below
information and contact TAC: 1. Was there
any configuration change on this interface
or its peer. 2. Is there any other known
trigger to this? 3. Collect the outputs for
the below CLIs: a) 'show inventory' b)
'show controllers <physical-interface>' c) Spurious occurrence of a particular
'show logging' d) Topology information 4.
interrupt. Gather the above information
What is the type of fiber used.
and contact ether-spa-india.

MAC Frame Corruption has occured. Try

below steps: 1. Try shut/no shut of the
interface. 2. Remove and re-insert the
transceiver on the same port. 3. Remove
and re-insert the transceiver on a different
port. 4. Remove and insert the transceiver
on different spa. If the issue still persists
collect the output of below CLIs and
contact TAC. 1. 'show inventory' 2. 'show
controllers <physical-interface>' 3. 'show
logging'

MAC Frame Corruption has occurred,

concerned port is in error state after
Maximum retries. Collect the below
information: 1. Details about transceiver
being used(PID, Vendor information). 2.
Topology details. 3. Output of 'show
running-config interface ' on interface and
from the peer interface. contact ether-spaindia with above details.

If the problem persists try reloading the

SPA. If reloading SPA doesn't fix the issue
try below steps: 1. Re-insert the SPA and
make sure it is seated properly. 2. If issue
still exists, try moving the card to a
different subslot or a differnet slot
altogether. 3. If problem continues to exist
after Step (2), replace SPA with a new one
or contact TAC.

MAC ECC errors have occured and autorecovery of the card has not corrected the
condition of SPA. If the problem persists
even after reload/re-inserting the SPA,
initiate RMA for the card and request
customer to try with another SPA card.

If this error continues to occur, move the

SPA to a different subslot or to a different
slot altogether. If the problem persists,
collect the output of 'show hw-mod sub
<>/<>/<> counters l2-tcam' and contact
TAC.

The error in SPA can occur either in MAC or

FUGU (Gila if it is a V1 SPA). If the error has
occured in the MAC and not resolved after
reseating the SPA, collect the below info
,contact ether-spa-india. 1. 'show logging'
2. 'show hw-module subslot <>/<>/<>
counters mac' 3. 'show hw-module subslot
<>/<>/<> errors mac' 4. 'show hw-module
subslot <>/<>/<> errors l2-tcam' 5. 'show
hw-module subslot <>/<>/<> counters l2tcam' 6. 'show hw-module subslot
<>/<>/<> registers mac' If the error has
occured in the FUGU (or Gila) and has not
resolved after reseating SPA or moving to
different slot, collect the below output,
contact ether-spa-india. 1. 'show logging' 2.
'show hw-module subslot <>/<>/<>
registers l2-tcam' 3. 'show hw-module
subslot <>/<>/<> counters l2-tcam' 4.
'show hw-module subslot <>/<>/<> errors
l2-tcam'

Collect the PID, Vendor Information of the

Transceiver from the CLI 'show controllers
TenGigE<>/<>/<>/<>' and contact TAC.

This error message indicates that the

hardware has generated an interrupt that
signals that an unsupported Transceiver
has been physically inserted for the
specified port at the given location. Collect
th PID and Vendor Information and check
below points: 1. Check in CCO page if
particular combination of SPA and
transceiver is supported. 2. Check in CCO
page if the Transceiver Module is Cisco
supported product a. If its a non-Cisco
product replace the transceiver. b. If the
transceiver is a Cisco product, get in touch
with q-spa-infra/ether-spa-india with above
details.

Copy the error message exactly as it

appears on the console or in the system
log. Call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log. Call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log. Issue the
<CmdBold>*param*<noCmdBold>
command 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
<CmdBold>*param*<noCmdBold> output,
call your Cisco technical support
representative and provide the
representative with the gathered
information. show logg
-Copy the error message exactly as it
appears on the console or in the system
log. Call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Verify that the card is not out of memory.

Contact your Cisco technical support
representative if the problem persists.

--

Copy the error message exactly as it

appears on the console or in the system
log. Call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log. Call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

As this error message indicates, the Ether

basecaps failed to process an IIR message
related to a bundle interface. Normally,
such errors are propagated back to the
virtual interface owner (Bundle Mgr) so that
it can take appropriate action. However, in
the case of a basecaps or IIR process
restart there is no mechanism available to
propagate the error back. Hence, it is
possible that the basecaps is out of sync
with the configuration. It is appropriate to
restart the ether_caps_partner process in
an attempt to recover, or if this fails, to
Restart the ether_caps_partner process in detach and re-attach the physical member
an attempt to recover, or if this fails,
interface that the error was reported on.
detach and re-attach the physical member Providing the Ether basecaps, driver
interface that the error was reported on by Ethernet, Bundle-mgr, and IIR tracing may
unconfiguring and reconfiguring the bundle provide more information for the DEs to
member id.
investigate the cause of this failure.
Copy the error message exactly as it
appears on the console or in the system
log. Call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log. Call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show ethernet
driver trace<noCmdBold> command 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
<CmdBold>show ethernet driver
trace<noCmdBold> output, call your Cisco
technical support representative and
provide the representative with the
gathered information. Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
-Copy the error message exactly as it
appears on the console or in the system
log. Call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log. Call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log. Call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log. Call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

Copy the error message exactly as it

appears on the console or in the system
log. If the problem persists, call your Cisco
technical support representative and
provide the representative with the
gathered information.
-Make sure there is enough memory
available. Contact your representative if
the problem persists.

--

Copy the error message exactly as it

appears on the console or in the system
log. Call your Cisco technical support
representative and provide the
representative with the gathered
information.

--

This error message indicates that a

configuration failure has occured, and so
reconfiguration is required. If the MAC
Check HSRP/VRRP configuration associated address shown is not seen in the
with this bundle interface or children
configuration of both HSRP and VRRP, or it
subinterface for the unicast MAC address
is unclear how to reconfigure the protocols
shown. If the unicast MAC address is
so that the unicast MAC address in
configured, reconfiguration of HSRP of
question is not used, then additional
VRRP should be considered.
support should be requested.

If the message recurs, copy the error

As the error message indicates an Ethernet
message exactly as it appears on the
capsulation process failed in its event loop.
console or in the system log, call your
Normally the process should restart and
Cisco technical support representative and recover. If this message is seen repeatedly
provide the representative with the
it is recommended that you contact the
gathered information.
DEs for further assistance.

This error message indicates that one of

the Ethernet capsulation processes failed
If the message recurs, copy the error
to initialize correctly. Normally, it is
message exactly as it appears on the
expected that the process should restart
console or in the system log, call your
and continue to function normally.
Cisco technical support representative and Providing the trace output to the DEs may
provide the representative with the
allow them to determine the cause of the
gathered information.
failure.
No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

Copy the error message exactly as it

appears on the console or in the system
log. Issue the <CmdBold>show
logg<noCmdBold> command 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
<CmdBold>show logg<noCmdBold>
output, call your Cisco technical support
representative and provide the
representative with the gathered
information. Copy the error message
exactly as it appears on the console or in
the system log. Issue the <CmdBold>show
ethernet driver trace<noCmdBold>
command 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 <CmdBold>show ethernet driver
trace<noCmdBold> output, call your Cisco
technical support representative and
provide the representative with the
gathered information.
-No action is required.

--

No action is required.

--

No action is required.

--

No action is required.

--

Restart the driver process that reported the

error. If the error is reported again then
reloading the linecard may allow it to
recover, but it will impact all traffic on that
node. Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This error message indicates that the driver

was unable to initialize the named physical
Ethernet interface. The interface will not be
usable until this condition is recovered. The
requested tech support information should
allow the development engineers to
pinpoint the cause of the problem.

If the error is reported again then reloading

the linecard may allow it to recover, but it
will impact all traffic on that node. Copy
the error message exactly as it appears on
the console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

This error message indicates that the driver

was unable to register for statistics
collection. The driver will exit and restart
upon failure in order to recover. The ouput
of the error message and requested tech
support information should allow the
development engineers to pinpoint the
cause of the problem.

Such errors are not expected, and probably

indicate an out-of-resource condition, or an
inconsistency in the system state. Wait for
any likely transient root problems to
subside, and attempt to repeat the
operation. If the message recurs, copy the
error message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.

The error message is most likely to be

encountered in an out-of-resource
situation, or a bug in the system. More
details on the root cause of the error
should be available from 'show ethernet
trace location ' and 'show statsd manager
trace'

Such errors are not expected, and probably

indicate an an inconsistency in the system
state or loaded IF-MIB and ETHERLIKE-MIB
DLLs. Determine if there is an initialization
issue with the IF-MIB as well. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

The error message is most likely to be

encountered in a DLL version mismatch or
error situation. More details on the root
cause of the error should be available from
'sh snmp mib dll'

As this error message indicates, the MTU

could not be applied on this interface. This
error message is likely to be generated if
the user attempts to configure an MTU that
is either too small or too large for any
Choose a more appropriate MTU to
configured protocols on the interface to
configure on the interface considering the handle. The solution is for the user to
MTU requirements of any L3 protocols that simply choose a more appropriate MTU
are configured on the interface.
value.

'shutdown' and 'no shutdown' the affected

interface, this should allow the state
machine to recover its operational state.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This error message indicates that the driver

was unable to correctly process an event in
the state FSM. The interface may not be
usable until this condition is recovered.

If the remote AC has changed state then

this message is expected. If the remote AC
hasn't changed state and this condition
isn't expected then this may indicate a
problem, Copy the error message exactly
as it appears on the console or in the
system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

This is part of the propagate remote-down

feature. The state of the local AC interface
is being updated to reflect the line status of
the remote AC.

If SF/SD-BER alarm is seen: Link quality

degraded beyond configured threshold.
Check if the peer device is injecting error
frames or otherwise check if the cable is
faulty.

--

The driver process is restarted

automatically, hence no user intervention
should be required. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

An error occurred during the initialization of

the generic Ethernet library. Normally the
driver process will exit and restart to
recover from any transient problems.

The driver process will attempt to recover

automatically, hence no user intervention
should be required. If the message recurs,
copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This error message indicates that the driver

was unable to create some or all physical
Ethernet interfaces. No physical ethernet
interfaces managed by the process
generating this error message will be
usable until this condition is recovered, and
the generic Ethernet library will attempt
recovery periodically. In the case of
continual failure, the requested tech
support information should allow the
development engineers to pinpoint the
cause of the problem.

This condition will only affect statistics

collection for some MAC addresses on this
interface. If the number of MAC accounting
addresses programmed, which can be
checked using 'show mac-accounting',
seems small and this issue is still hit this
may indicate a system error, Copy the error
message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

The IOX Ether design is to allow the

customer to use the full H/W MTU range
If 802.1Q or QinQ support is required on
available. The side effect of this is that the
the interface, then it is recommended that user could end up configuring an MTU that
either the configured interface MTU is
impacts 802.1Q or QinQ functionality. If
reduced by 4 or 8 bytes, or the subthey require this functionality then they
interface MTU is reduced by 4 or 8 bytes to should take one of the action above. If they
ensure that all frames are within the H/W
don't require 802.1Q or QinQ support then
limits.
they can simply ignore this message.

This error indicates that the 1p OC12-chds1 PLIM process detected an error
If the message recurs, copy the error
condition. This does not mean the PLIM
message exactly as it appears on the
hardware is in fault always. The message
console or in the system log, call your
will inform the severity. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

This error indicates that the 1p OC12-chds1 PLIM process detected an error
If the message recurs, copy the error
condition. This does not mean the PLIM
message exactly as it appears on the
hardware is in fault always. The message
console or in the system log, call your
will inform the severity. Report this to
Cisco technical support representative and Engineering. Use Topic to search for a
provide the representative with the
similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

This error indicates that the 1p OC12-chds1 PLIM process detected an error
condition during initialization. Process will
If the message recurs, copy the error
restart and hopefully recover. This does not
message exactly as it appears on the
mean the PLIM hardware is in fault always.
console or in the system log, call your
The message will inform the severity.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This error indicates that the 1p OC12-chds1 PLIM multilink platform dependent
component detected an error condition.
The message will inform the severity. The
output of the following commands will be
helpful: - show plim-info multilink interface
multilink - show plim-info multilink location
summary Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

This error indicates that the 1p OC12-chds1 PLIM multilink component detected an
error condition in pulse mesage processing.
The message will inform the severity. The
output of the following commands will be
helpful: - show plim-info multilink interface
multilink - show plim-info multilink location
summary Report this to Engineering. Use
Topic to search for a similar DDTS. If you
find none, write a DDTS for this problem.

If the message recurs, copy the error

An unexpected value for the encap length
message exactly as it appears on the
is provided, resulting a failure of inserting
console or in the system log, call your
an encap string into the encap table.
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and
provide the representative with the
gathered information.
--

For a given interface handle, the SHIM

If the message recurs, copy the error
information is not found in the shared
message exactly as it appears on the
memory, resulting a failure of inserting an
console or in the system log, call your
encap string into the encap table. Report
Cisco technical support representative and this to Engineering. Use Topic to search for
provide the representative with the
a similar DDTS. If you find none, write a
gathered information.
DDTS for this problem.

An unexpected encap type is found trying

If the message recurs, copy the error
to extract the SHIM information, resulting a
message exactly as it appears on the
failure of inserting an encap string into the
console or in the system log, call your
encap table. Report this to Engineering.
Cisco technical support representative and Use Topic to search for a similar DDTS. If
provide the representative with the
you find none, write a DDTS for this
gathered information.
problem.

Restarting the process in question should

result in a full resync of all data. If the
message recurs, copy the error message
exactly as it appears on the console or in
the system log, call your Cisco technical
support representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Copy the error message exactly as it

appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.

If the message recurs, copy the error

message exactly as it appears on the
console or in the system log, call your
Cisco technical support representative and Report this to Engineering. Use Topic to
provide the representative with the
search for a similar DDTS. If you find none,
gathered information.
write a DDTS for this problem.
Copy the error message exactly as it
appears on the console or in the system
log, call your Cisco technical support
representative and provide the
representative with the gathered
information.

Report this to Engineering. Use Topic to

search for a similar DDTS. If you find none,
write a DDTS for this problem.

Please collect the console log and following

traces: show cef trace loc <> show cef
platform trace [common|ipv4] all loc <>
show adjacency hardware trace loc <>
show bundle trace all loc <> show im trace
loc <> Most of the time, these are
harmless transient messages, caused by
the delay in FIB and AIB processes learning
about new interface. If the errors persist,
report to your technical support
representative.
--

Please collect the console log and the CLI

output. <CLI> <RP> show cef </RP>
<LC> show cef location <> show cef trace
location <> show cef platform trace
common all location <> show cef platform
trace ipv4 all location <> show im trace
location <> show bundle trace location <>
show adjacency hardware trace location
<> </LC> <TECH> show tech cef show
version show install summary </TECH>
</CLI> Also notice if the error message is
transient or persistent. Report to your
technical support representative.

Collect information mentioned in:

http://wwwindeployment.cisco.com/wiki/bin/view/Main/I
Pv4IPv6#IPv4_IPv6 http://wwwindeployment.cisco.com/wiki/bin/view/Main/M
PLS Report this to Engineering. Use Topic to
search for a similar DDTS. If you find none,
write a DDTS for this problem..

Please collect the console log and following

traces: show cef trace loc <slot number>
show cef platform trace [common|ipv4] all
loc <slot number> show adjacency
hardware trace loc <slot number> show
bundle trace all loc <slot number> show
im trace loc <slot number> Most of the
time, these are harmless transient
messages, caused by the delay in FIB and
AIB processes learning about new
interface. If the errors persist, report to
your technical support representative.

This is an error in the CPP FIB IPv4.

Examine the traceback and \ output of
show tech-support for clues. Use Topic to
search for a \ similar DDTS. If you find
none, write a DDTS for this problem. Please
refer to the wiki for trouble shooting steps:
http://zed.cisco.com/confluence/display/GS
RTR/Thor+IPv4

Please collect the console log and following

traces: show cef trace loc <slot number>
show cef platform trace [common|ipv4] all
loc <slot number> show adjacency
hardware trace loc <slot number> show
bundle trace all loc <slot number> show
im trace loc <slot number> Most of the
time, these are harmless transient
messages, caused by the delay in FIB and
AIB processes learning about new
interface. If the errors persist, report to
your technical support representative.

This is an error in the CPP FIB IPv4.

Examine the traceback and \ output of
show tech-support for clues. Use Topic to
search for a \ similar DDTS. If you find
none, write a DDTS for this problem. Please
refer to the wiki for trouble shooting steps:
http://zed.cisco.com/confluence/display/GS
RTR/Thor+IPv4

Please collect the console log, FIB traces

(show cef trace loc <>), FIB platform trace
(show cef platform trace [common|ipv4] all
loc <>). Also notice if the error message is
transient or persistent. If the errors persist,
report to yo